i18n: add Korean (ko-KR) translation - #3024
Closed
moduvoice wants to merge 1 commit into
Closed
Conversation
Added i18n/locales/ko-KR.json with a full Korean translation (1,401 keys, 100% parity with en.json) and registered ko-KR in config/i18n.ts. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
gameroman
added
i18n
Member
|
Looks like there is already #2933 open |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
This adds Korean (ko-KR) translation support — to help Korean-speaking users use this open-source project more comfortably in their own language.
(한국 사람들의 오픈소스 이용에 도움이 되게 하기 위해서 한글화 작업을 하였습니다.)
Changes
Added i18n/locales/ko-KR.json, a full Korean translation of every key in en.json (1,401 leaf keys, 100% coverage). ko-KR was already registered in config/i18n.ts's locale list; only the translation file itself was missing.
Testing
Verified en.json and ko-KR.json have identical flattened key sets (1401/1401, no missing/extra keys).
Ran pnpm vp run i18n:check ko-KR — no missing keys.
Ran pnpm vp run i18n:report — 0 missing / 0 unused / 0 dynamic keys across all locales.
Ran pnpm vp run lint — 0 errors.
Ran pnpm vp run i18n:schema — schema.json unchanged, as expected since en.json was not modified.
Ran pnpm test:types — passes.
Manually verified in the running dev app (switched language to 한국어) that the UI renders correctly in Korean across the homepage, settings page, and a package page.