[yuseok89]

Changes (Oct 1)

• Most new strings follow existing translations in the Korean locale, keeping the same wording and tone.
• Spacing in the time range options is aligned. 지난 12 시간 and 지난 24 시간 become 지난 12시간 and 지난 24시간, matching every other number-unit pair in the Korean locale and the guideline in locales/ko.md. 지난 주 becomes 지난주, which is a single word in Korean.

The Korean locale is now 100% complete (1160/1160).

Changes (Oct 6)

While this PR was waiting to be merged, 70 more keys landed on main, so I merged main and translated them.

• The new strings cover the Dag version comparison tab, the paused Dag options in the trigger dialog, Dag folders, the match-anywhere search setting and the connection type fields section.
• Drain in the paused Dag options reuses the existing 완료 후 일시 중지 from the Dags list, since it has the same meaning there.
• Terms new to the Korean locale in the version comparison tab are Provenance as 출처, Operation as 변경 유형 (its values are added, changed and removed) and Observed state as 관측된 상태.
• No existing strings are changed.

The Korean locale is now 100% complete (1226/1226).

Changes (Oct 12)

While this PR was waiting, more keys landed on main, so I merged main again and translated them.

• The new strings cover loop iterations, the Execution tab on the Dag run page, the recent tasks setting on the Dags list and the skipped info in the mark-as dialog.
• Terms new to the Korean locale are Iteration as 반복, Invocation as 호출, Whole expansion as 전체 확장 and Execution as 실행 항목, to keep it apart from 실행, which is already used for Dag runs.
• The three new strings that count items now use {{count, number}}, following UI: Group digits of counters in translated strings #74296.
• Ellipses are unified to three dots (...), which the Korean locale already used in more places than …. Four existing placeholders change from … to ....

The Korean locale is now 100% complete (1273/1273).

---

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

• Yes (please specify the tool below)
  • Claude Code (Opus 5.5)

---

• 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]

Gentle ping @choo121600. While this was waiting, 70 more keys landed on main, so I merged main and translated them as well (see "Changes (Oct 6)" in the description). The Korean locale is back to 100%. Could you take a look when you have a moment? Thanks!

[yuseok89]

Gentle ping @choo121600. I merged the latest main again, translated the new keys and aligned the counters with #74296 (see "Changes (Oct 12)" in the description). The Korean locale is back to 100%. Could you take a look when you have a moment? Thanks!

[choo121600]

Oops, I missed this! Thanks!