[aaiss0927]

Add the eight missing Korean (ko) translations that restore key parity with the English locale:

File	Key	English	Korean
dag.json	versions.pathOccurrences_one	{{count, number}} change shares this path	변경 {{count, number}}개가 이 경로를 공유합니다
dag.json	versions.pathOccurrences_other	{{count, number}} changes share this path	변경 {{count, number}}개가 이 경로를 공유합니다
dag.json	versions.pathOccurrencesAtLeast_one	At least {{count, number}} change shares this path	변경 {{count, number}}개 이상이 이 경로를 공유합니다
dag.json	versions.pathOccurrencesAtLeast_other	At least {{count, number}} changes share this path	변경 {{count, number}}개 이상이 이 경로를 공유합니다
hitl.json	response.selectAtLeastOne	Select at least one option	옵션을 하나 이상 선택하세요
browse.json	xcom.columns.timestamp	Timestamp	타임스탬프
common.json	dagDetails.bundleVersion	Bundle Version	번들 버전
components.json	sort	sort	정렬

Notes:

• The first five keys were added to the English locale after the currently open Korean batch PR i18n(ko): Add missing translations (Oct 23) #75415 branched: versions.pathOccurrences* by UI: Show Dag version diff occurrence count on the path instead of a column #75433 and response.selectAtLeastOne by Require a selection before responding to a multiple-choice HITL request #75643 — so they are not covered by that PR. This PR intentionally contains only keys outside i18n(ko): Add missing translations (Oct 23) #75415's scope and does not overlap it (same de-duplication approach as i18n(ko): add missing translations(Jul 17) #70005). related: i18n(ko): Add missing translations (Oct 23) #75415
• The last three keys were added to the English locale by UI: Fix labels that render as raw translation keys #75326, after this branch was cut; included per @yuseok89's review suggestion (branch rebased onto latest main accordingly). Re-checked against i18n(ko): Add missing translations (Oct 23) #75415: the remaining ko gaps are still exactly the set it fills — no overlap.
• _one/_other share the same Korean string, following the existing ko locale convention (e.g. versions.summary_one/_other).
• The pathOccurrences* strings are the tooltip on the ×N badge in the Dag Versions diff, shown when several changes are merged into one row because they share a path. The badge appears only for users without Dag code read access (values-redacted mode); the AtLeast variant is used when the diff was truncated by the max-changes limit (×N+).
• selectAtLeastOne is the validation message in the Human-in-the-loop response form when no option of a multiple-choice request is selected.
• xcom.columns.timestamp is the XCom list column header; dagDetails.bundleVersion is the row label in the Dag details panel (wording matches the existing versionDetails.bundleVersion = "번들 버전"); sort is the aria-label of the sort toggle in data-table headers.

---

Screenshots

Validation message when no option of a multiple-choice HITL request is selected (response.selectAtLeastOne):

Tooltip on the ×3 badge in the Dag Versions diff, viewed without Dag code read access (versions.pathOccurrences_other):

Truncated diff (Max changes = 1): the ×3+ badge with the lower-bound tooltip (versions.pathOccurrencesAtLeast_other). The English "At least 3 changes" summary line is summaryAtLeast, which is covered by #75415:

The three #75326 keys are single-word labels — the XCom Timestamp column header, the Bundle Version row in Dag details, and a screen-reader-only sort aria-label — so no dedicated screenshots for them.

---

Test

breeze ui check-translation-completeness --language ko

On this branch (rebased onto main, so the #75326 keys are in the en baseline) the eight keys are no longer reported: hitl.json and browse.json 100%, dag.json missing 22 → 18, common.json 12 → 11, components.json 7 → 6. The remaining 38 missing / 13 unused keys are exactly the set being handled by #75415, so ko coverage reaches 100% once both PRs land.

cc @onestn @noeunkim

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Claude Fable5

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[yuseok89]

Looks good to me, thanks, the translations read well and stay consistent with the existing ko terms. Since #75326 three new keys landed in en, and it would be nice to add them here as well.

[yuseok89]

@choo121600, could you take a look at this one and #75415 when you have a moment? Both fill in missing ko keys without overlapping.

[aaiss0927]

Thanks for the review @yuseok89! Done — added the three keys that landed with #75326:

• browse.json → xcom.columns.timestamp = "타임스탬프" (same wording as dashboard.json)
• common.json → dagDetails.bundleVersion = "번들 버전" (consistent with the existing versionDetails.bundleVersion in components.json)
• components.json → sort = "정렬" (the TableList sort-button aria-label)

Also re-checked against #75415 — still no overlap: the remaining ko gaps are exactly the ones it fills.

[choo121600]

Thanks for contributiion :)