Add Korean (ko) translation#6
Conversation
78e864e to
f7c7139
Compare
3113cb4 to
5703765
Compare
|
Thanks for your work on translating flexcyon, would check this in a bit before merging. |
bladeacer
left a comment
There was a problem hiding this comment.
I have taken a look at the PR. It is really good aside from a small set of minor adjustments which can be made. Will be merging this to a separate branch before I cherry pick to both master and staging. Thanks for your efforts once again @OneVth , if you would like after this and #7 I can add you as a collaborator. I will also gladly credit you for your contributions :D.
|
lgtm. |
|
Thank you! Since this is on ko-translation-1.4.0 for now — once the Korean translation lands on the main branch, I'd be glad to be added as a collaborator. I'd like to keep working on the Korean docs going forward :D |
|
I have cherry picked to staging and master, as well as sent a collaborator invite. |
Adds Korean (ko) translation, as discussed in #5.
Overview
kolanguage (hugo.toml + i18n/ko.yaml)hugo buildpasses clean (EN 255 / KO 254 / ZH 254)Addressing feedback from #5
content/ko/_index.mdthat the docs are translated from English and the English version takes precedence.Style Settings를), as discussed in Korean (ko) translation #5.masteras you suggested; the 2.0 updates will follow in a later PR once the en/zh 2.0 docs are out.Terminology
Korean terms follow Obsidian's official Korean UI translations, so the docs match what Korean users actually see in the app. For example: Heading → 제목, Callout → 콜아웃, Callout Metadata → 콜아웃 메타데이터, Canvas → 캔버스, Status Bar → 상태바, Title Bar → 타이틀바, Inline Title → 인라인 제목, Indicator → 인디케이터.
The following are kept in English:
"all-blue"), CSS variables (var(--...)), class names (markdown-callout), URL anchors, and link paths are never translated.Note: some plugin UIs (e.g. BRAT) always display in English regardless of Obsidian's language setting, so terms referring to those UIs are kept in English even where an Obsidian translation exists.
Notes on the English source
While translating, I came across a few things in the English docs that may need your input. These are about the English source, not the translation:
title.font-sizespans in the Smaller/Small/Medium/Large examples render at sizes that look very close to each other. Flagging in case it's unintentional.Usage:label above the code block is present on some pages and absent on others that share the same structure — present on the text-variant style pages (title/combined-styling page 13–24), absent on the colour/font pages (bg-styling page 2–9, combined-styling page 2–9 and 25–27, content-styling page 15–17, title-styling page 2–9 and 31–33). Flagging in case it's unintentional.Manual review — Done section by section (see checklist below).