Add Korean (ko) locale - #1444
Open
moduvoice wants to merge 1 commit into
Open
Conversation
Translate all admin UI strings in config/locales/en.yml to Korean, matching key structure and Rails i18n interpolation tokens.
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
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.
Korean (ko) translation PR body template
Motivation
This adds Korean (
ko) translation support — to help Korean-speaking users use thisopen-source project more comfortably in their own language.
한국 사람들의 오픈소스 이용에 도움이 되게 하기 위해서 한글화 작업을 하였습니다.
Changes
config/locales/ko.yml(new file, 417 lines) with a full Korean translation of the admin UI, mirroring the structure ofconfig/locales/en.ymlexactly.Spina::Engineis a standardRails::Enginewith no customi18n.load_pathor locale allowlist, soconfig/locales/**/*.ymlis auto-discovered the same way it already is for the repo's other 18 locale files (nl, de, fr, ru, zh-CN, etc.).Spina.config.localesis a separate, unrelated concept — it configures which locales page content is translated into (Spina::TranslatedContent, page/resource translation UI), not which admin-UI languages are available. Admin UI language selection follows the host app'sI18n.default_locale, same as every other existing locale file in this directory.spina.languagesmap (used to render language names in the page-translation UI) was translated to Korean for all 16 existing entries, deliberately omitting a self-referentialkoentry to matchen.yml's own omission ofenfrom... (actually en.yml does includeen, matching exactly — key sets are identical, no additions or omissions beyond parity).Testing
en.ymlandko.ymlvia a Ruby/YAML script (YAML.load_file+ recursive key flattening): 359/359 leaf keys present in both, 0 missing, 0 extra.%{...}interpolation token matches exactly between correspondingen/kokeys: 0 mismatches.*_htmlkey: 0 mismatches.spina.languageskey set matchesen.ymlexactly (16 keys, same set, nokoself-entry in either file).YAML.load_file(no syntax errors).git diff --statagainstmain):config/locales/ko.yml, 417 insertions, no other files modified.%{subject}을(를)).