From de62821973b0369f8e3586f7e8fd35d0aa1c838b Mon Sep 17 00:00:00 2001
From: Kat <65649991+00-kat@users.noreply.github.com>
Date: Sat, 28 Feb 2026 17:39:16 +1100
Subject: [PATCH] Rename ko.po back to ko_KR.po.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

While it was renamed from ko_KR.UTF-8.po to ko.po in #10976, @uhojin,
a Korean locale maintainer, notes [1] that “ko_KR [*South* Korean] makes
more sense in locale context just to avoid any potential confusion
between 한국어 vs 조선어”.

Despite ko_KP (North Korean) not being present in glibc (as of version
2.43), and the ISO639 maintainers expressing disapproval of ko_KP [2],
it is possible opinions may change in the future, and individual
opinions may be contested—disambiguating doesn't hurt.

[1]: https://github.com/ghostty-org/ghostty/pull/10976#discussion_r2861424171
[2]: https://github.com/ghostty-org/ghostty/pull/10976#discussion_r2861359240
---
 CODEOWNERS              | 2 +-
 po/{ko.po => ko_KR.po}  | 0
 src/os/i18n_locales.zig | 2 +-
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename po/{ko.po => ko_KR.po} (100%)

diff --git a/CODEOWNERS b/CODEOWNERS
index 71921d9a3..f377a73c6 100644
--- a/CODEOWNERS
+++ b/CODEOWNERS
@@ -177,7 +177,7 @@
 /po/id.po @ghostty-org/id_ID
 /po/it.po @ghostty-org/it_IT
 /po/ja.po @ghostty-org/ja_JP
-/po/ko.po @ghostty-org/ko_KR
+/po/ko_KR.po @ghostty-org/ko_KR
 /po/lt.po @ghostty-org/lt_LT
 /po/lv.po @ghostty-org/lv_LV
 /po/mk.po @ghostty-org/mk_MK
diff --git a/po/ko.po b/po/ko_KR.po
similarity index 100%
rename from po/ko.po
rename to po/ko_KR.po
diff --git a/src/os/i18n_locales.zig b/src/os/i18n_locales.zig
index 8cf62e390..7a7daf998 100644
--- a/src/os/i18n_locales.zig
+++ b/src/os/i18n_locales.zig
@@ -37,7 +37,7 @@ pub const locales = [_][:0]const u8{
     "ru",
     "uk",
     "pl",
-    "ko",
+    "ko_KR",
     "mk",
     "tr",
     "id",