Request to unify Korean locale slug as “ko” (remove redundant “_KR”)

Hello Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/.,

I’d like to request unifying the Korean WordPress localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ slug to simply `ko`, instead of `#ko_KR`.

According to international language standards such as IETF BCP 47, the primary language subtag `”ko”` is already sufficient to indicate Standard Korean as spoken in South Korea. The `”KR”` regional subtag is unnecessary unless differentiating between variants, such as North Korean (`ko_KP`) or other dialectal forms (e.g., Yanbian Korean).

GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. already uses `”ko”` as the language slug, and many parts of the WordPress translation infrastructure (e.g., `html_lang_attributesms` in 6.8.x) reflect this with `ko-KR`. Unifying under the base `”ko”` would:

• Reflect established international standards
• Reduce redundancy
• Clarify that this locale refers to the standard form of Korean
• Allow for clean differentiation if variants are ever needed in the future

Please consider this change to improve consistency and alignment with global practices.

Thank you for your time and consideration.

Best regards,
@kimjiwoon

—

• [IETF BCP 47](https://tools.ietf.org/html/bcp47) (Language Tag Standard)
• [CLDR Language Codes](https://cldr.unicode.org/)
• [Wikipedia: Korean language](https://en.wikipedia.org/wiki/Korean_language)
• https://en.wikipedia.org/wiki/IETF_language_tag

#request