Skip to content

feat(i18n): add Korean (ko) translation#170

Merged
mgks merged 1 commit into
docmd-io:dev-0.8.10from
moduvoice:feat/i18n-ko
Jul 9, 2026
Merged

feat(i18n): add Korean (ko) translation#170
mgks merged 1 commit into
docmd-io:dev-0.8.10from
moduvoice:feat/i18n-ko

Conversation

@moduvoice

Copy link
Copy Markdown
Contributor

Motivation

This adds Korean (ko) translation support — to help Korean-speaking users use this
open-source project more comfortably in their own language.
(한국 사람들의 오픈소스 이용에 도움이 되게 하기 위해서 한글화 작업을 하였습니다.)

docmd already ships built-in UI strings for the documentation sites it generates
(sidebar/navigation labels, search, cookie consent, the git history widget, and the
threads discussion plugin), with translations for en, de, es, fr, ja, zh,
and hi. This PR adds the missing ko locale so Korean-language docs sites built with
docmd render their built-in UI chrome in Korean instead of falling back to English.

Changes

  • packages/ui/translations/ko.json — core theme strings (sidebar, search, 404 page,
    cookie consent, language/version switchers, etc.) — 44 keys
  • packages/plugins/search/i18n/ko.json — search plugin UI strings — 8 keys
  • packages/plugins/git/i18n/ko.json — git history widget strings — 11 keys
  • packages/plugins/threads/i18n/ko.json — threads/discussion plugin strings — 42 keys

No source/registration changes were needed: each package resolves translation files by
locale id at runtime (packages/ui/src/index.ts, and the equivalent loaders in the
search/git plugins), falling back to en for missing keys, so simply adding the
ko.json files is sufficient to enable the locale — the same pattern used by the
existing hi/zh/ja/de/es/fr locales.

Testing

  • Verified the ko key set is identical to the corresponding en.json in all four
    files (no missing/extra keys) via a small script comparing Object.keys.
  • Verified all {placeholder} tokens (e.g. {active}, {default}, {version},
    {n}) are preserved exactly in the Korean strings.
  • Validated all four files as well-formed JSON.
  • Manually reviewed each translated string for natural, idiomatic Korean phrasing
    consistent with the terminology used across the existing UI strings.

Add ko.json for the core UI theme (sidebar, search, 404, cookie
consent, language/version switchers) and for the search, git, and
threads plugins, following the existing locale pattern used by
en/de/es/fr/ja/zh/hi. All translation files are dynamically loaded
by locale id at runtime, so no additional registration was required.
@mgks mgks deleted the branch docmd-io:dev-0.8.10 July 9, 2026 06:01
@mgks mgks closed this Jul 9, 2026
@mgks mgks reopened this Jul 9, 2026
@mgks mgks merged commit 0e3fd89 into docmd-io:dev-0.8.10 Jul 9, 2026
mgks added a commit that referenced this pull request Jul 9, 2026
Add ko.json for the core UI theme (sidebar, search, 404, cookie
consent, language/version switchers) and for the search, git, and
threads plugins, following the existing locale pattern used by
en/de/es/fr/ja/zh/hi. All translation files are dynamically loaded
by locale id at runtime, so no additional registration was required.

Co-authored-by: moduvoice <moduvoicr77@gmail.com>
@mgks

mgks commented Jul 9, 2026

Copy link
Copy Markdown
Member

Thank you so much for the contribution. 🙏🏼

I deleted the dev branch without confirming the PR was made on it. But it's fixed now and the improvements are merged as well.

Users can now simply use the Korean translations by adding ko to their config.i18n.locale configs from 0.8.10 onwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants