i18n: add Korean (ko) translation#2197
Open
moduvoice wants to merge 2 commits into
Open
Conversation
Add a complete Korean localization (src/frontend/client/src/locales/ko/translation.json, 1892 keys matching the en/zh-Hans/ja file structure) and register it in the client i18next resources plus the two active language switchers (AccountSettings, UserPopMenu). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
com_ui_provider, com_ui_select_provider, com_ui_select_provider_first, and com_ui_select_search_provider used three different Korean words (제공자/서비스 제공자/공급자) for "provider" within the same UI panel (ModelPanel.tsx). Aligned all four to 제공업체, matching the term already used consistently in the 7 related api_errors messages.
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
1 participant
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) translation support — to help Korean-speaking users use thisopen-source project more comfortably in their own language.
한국 사람들의 오픈소스 이용에 도움이 되게 하기 위해서 한글화 작업을 하였습니다.
Changes
src/frontend/client/src/locales/ko/translation.jsonwith all 1892 leaf keys translated (0 missing / 0 extra vs.en/translation.json).koresource insrc/frontend/client/src/locales/i18n.ts.AccountSettings.tsxandUserPopMenu.tsx, mirroring the existingjaentries exactly.com_ui_*,com_endpoint_*,com_nav_*, etc.) reuse LibreChat's official Korean wording for consistency with the broader LibreChat ecosystem.com_knowledge.*,com_subscription.*,api_errors.*, workflow/agent/knowledge-base/workspace/channel strings, etc.) were freshly translated, using the existingzh-Hansandjatranslations as tone/terminology references.src/frontend/platform(the separate admin frontend) was intentionally left untouched — it has nokolocale infrastructure yet.Testing
ko/translation.jsonleaf keys ==en/translation.jsonleaf keys exactly (1892 == 1892, 0 missing, 0 extra).{{placeholder}}check: all interpolation placeholders match 1:1 betweenenandkofor every key..tsxdiffs for the language switcher were confirmed to exactly mirror the existingjaentries, with no unrelated changes.com_ui_*,api_errors,com_knowledge,com_subscription, andcom_agent*namespaces for translation quality and glossary adherence.