translation: add Korean (ko) locale - #3633
Open
hankimis wants to merge 1 commit into
Open
Conversation
Adds a complete Korean translation of all 14 locale files
(4,232 keys) and registers `ko` alongside the existing languages.
Verified mechanically against the English source:
- key sets are identical (0 missing, 0 extra) in every file
- the set of `{{interpolations}}` in each string matches the source
- `<Tag>` markup and `$t(...)` references match the source
- formula `example` strings, function names (SUM, ARRAYJOIN, ...) and
error identifiers (ForeignKeyNotFound, ...) are left untranslated
- key order follows the English files, and the serialization is
byte-identical in style to the existing locale files
Terminology was kept consistent throughout: 베이스 (base), 스페이스 (space),
테이블 (table), 레코드 (record), 필드 (field), 뷰 (view), 집계 (rollup),
조회 (lookup), 연결 (link), 협업자 (collaborator), 첨부파일 (attachment),
자동화 (automation), 휴지통 (trash).
Besides the locale files, `ko` is added in the three places that hold the
locale list: next-i18next.config.js, src/lib/app-proxy.ts and the
LanguagePicker component.
|
|
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.
What
Adds a complete Korean (
ko) translation for all 14 locale files — 4,232 keys — and registerskoas a selectable language.Korean was the only major East Asian language missing (
zhandjaare both present), and there is currently no partialkofolder to conflict with.Files
packages/common-i18n/src/locales/ko/*.json— the translation (14 files)apps/nextjs-app/next-i18next.config.js—'ko'added toi18n.localesapps/nextjs-app/src/lib/app-proxy.ts—'ko'added tolocalesapps/nextjs-app/src/features/app/components/LanguagePicker.tsx—{ key: 'ko', title: '한국어' }Those three files are the only places in the repo that carry the locale list (verified by grepping for an existing locale code).
crowdin.ymlmaps with%two_letters_code%, so the folder namekois correct.Verification
Checked mechanically against the English source, for every file:
{{interpolations}}in each string matches the source string<Tag>markup and$t(...)references match the sourceIntentionally left untranslated: formula
examplestrings, function names (SUM,ARRAYJOIN, …), error identifiers (ForeignKeyNotFound, …), and product names (Teable, Vercel, AI Gateway, OpenRouter, Ollama).Terminology
Kept consistent throughout:
Sentences addressed to the user use polite form (존댓말); labels and buttons use noun form, matching Korean UI convention.
Context
Translated while self-hosting Teable for a Korean team, so the high-traffic surfaces (grid, field editors, view config, space/base management) were read in context rather than translated key-by-key in isolation. Happy to adjust any wording.