Add a Korean translation to the Blog and Wallet (Wallet offers ko with no translation file; Blog doesn't offer it)

Dan decided 2026-10-15 to add a Korean translation, after #1205 (closed)'s live check found that Korean is offered but not translated (see #1206 (closed)).

Problem and intended result

  • The Wallet offers Korean: ko is in apps/wallet/i18n/settings.ts languages, apps/wallet/next-i18next.config.js and the switcher (apps/wallet/components/hooks/use-language-switch.ts, 🇰🇷). But apps/wallet/locales/ko/common_wallet.json does not exist. Choosing Korean shows English texts, except the login dialog (packages/smart-signer/locales/ko/smart-signer.json exists).
  • The Blog does not offer Korean (apps/blog/i18n/settings.ts languages lacks ko, and there is no apps/blog/locales/ko/). Yet apps/blog/next-i18next.config.js already lists ko. On peerverity, where both apps share one NEXT_LOCALE cookie (#1205 (closed)), a Korean choice in the Wallet leaves the Blog in English.

Intended result: Korean is a complete UI language in both apps, selectable from both switchers.

Required behavior

  • Create apps/wallet/locales/ko/common_wallet.json and apps/blog/locales/ko/common_blog.json. Translate every key of the English reference files (en, about 607 wallet keys and 733 blog keys) into Korean, with the same key structure and every interpolation placeholder ({{...}}), <Trans> tag and HTML/markdown fragment preserved exactly.
  • Check packages/smart-signer/locales/ko/smart-signer.json against its en file and fill any missing keys.
  • Add ko to the Blog's languages (apps/blog/i18n/settings.ts) and to the Blog's language switcher list (apps/blog/features/layouts/use-language-switch.ts LANGUAGES, 🇰🇷), in the same position the Wallet uses.
  • Translation guidance: Hive and blockchain terms follow the established Korean usage on hive.blog / Korean Hive communities where one exists. Keep product and token names untranslated: Hive, HIVE, HBD, Hive Power, Witness names, dApp names. Use polite, concise UI style (합니다/하세요 forms for actions and messages). Where a term has no settled Korean equivalent ("power down", "savings", "resource credits"), pick one rendering, use it consistently in both apps, and list those choices in the commit message for later review.

Acceptance criteria

  • pnpm --filter @hive/blog lint:translations and the wallet translation check (scripts/check-wallet-translations.js) report ko in sync with en: no missing or extra keys.
  • With the NEXT_LOCALE cookie set to ko, /trending in the Blog and /@<user>/transfers in the Wallet render Korean UI texts with <html lang="ko"> and the 🇰🇷 flag.
  • Korean is selectable from the Blog's language menu, and choosing it renders Korean.
  • No placeholder is lost. A string with {{count}}/{{username}} etc. in en has the same placeholders in ko, checked by a small unit or script test over both files.

Verification

The quick slot (translation checks, static). Blog and Wallet fixture specs with the cookie preset to ko. Live check on peerverity after promote. Translation quality has had no native-speaker review. Say so in the commit; that review is a follow-up for a human, not part of this issue.

Integration points

  • apps/wallet/locales/ko/common_wallet.json — new
  • apps/blog/locales/ko/common_blog.json — new
  • apps/blog/i18n/settings.ts languages — add ko
  • apps/blog/features/layouts/use-language-switch.ts LANGUAGES — add Korean

Scope boundary

#1206 (closed) (the Blog setting lang to a language it can't render) is separate and still needed for any other unsupported value. Other missing languages and native-speaker review are out of scope.