feat(i18n): complete Korean error translations (43 → 233 keys)#6353
Merged
Conversation
After #6349, ko/errors.ftl shipped 43 of the 233 api-error-* keys; the remaining 190 resolved to the raw message-key literal for Korean clients because a non-English Fluent bundle is built from that language alone with no English fallback resource. Translate the remaining 190 messages, preserving every Fluent placeholder, and restructure the file to mirror en/errors.ftl exactly (same section comments, same key order). The 43 prior human-reviewed translations are reused verbatim.
Contributor
|
@houko I won't open a PR right away. I'll probably have a couple more changes once I start using the Korean interface this week. Moving forward, I'll submit a PR for the Korean i18n every once in a while (weekly, monthly, or whenever I feel there’s enough content for a single PR). |
…register api-error-memory-not-enabled: 사전 메모리 → 능동적 메모리. '사전' reads as dictionary / prior, distorting 'proactive'; 능동적 메모리 matches the dominant rendering already shipped in the dashboard ko.json (memory.proactive_memory). api-error-tool-invoke-disabled / api-error-tool-requires-agent: normalize the trailing imperative from -하세요 to the catalog-dominant formal -하십시오.
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.
Summary
Completes the Korean (
ko) error-message catalog introduced in #6349.That PR wired
kointolibrefang-types::i18n(theKO_FTLresource,SUPPORTED_LANGUAGES, andftl_source), butko/errors.ftlshipped only 43 of the 233api-error-*keys.The other 190 error codes therefore resolved to the raw message-key literal for Korean clients:
ErrorTranslator::t_argsreturns the key string when its bundle has no match, and a non-English bundle is built from that language's FTL alone with no English fallback resource.So a Korean client hitting, say,
api-error-provider-not-foundsaw the literalapi-error-provider-not-foundrather than a message.This brings
ko/errors.ftlto full parity withen/errors.ftl— 233 of 233 keys.Changes
api-error-*messages to Korean.en/errors.ftlexactly — same section comments, same key order — so future drift is a one-line diff against the English source.{ $var }placeholder byte-for-byte.secrets.env,base_url,model_id,[tool_invoke] allowlist,manifest.json,http:///https://,.zip).not found → 찾을 수 없습니다,Failed to X → X하는 데 실패했습니다,Invalid → 유효하지 않은 …입니다,cron expression → 크론 표현식).Verification
ko233 ↔en233 — 0 missing, 0 extra.{ $var }multiset matches the English source for all 233 keys — 0 mismatches.crates/librefang-types/src/i18n.rs::all_languages_have_same_keyscontinues to hold forko(the 8 critical keys are present and translated).Notes
i18n.rsregistration — merge this after feat(i18n): UI Korean translation #6349.