[PATCH v2] localedata: update LC_ADDRESS and LC_NAME for ko_KR

[Arjun Shankar]

Hi Jiho,

Thank you for the explanation!

> Your translation and understanding are correct. The modern South Korean
> addressing system (Road Name Address) strictly follows the Large-to-Small
> hierarchy. The English version of the Korea Post site is unfortunately
> less detailed, but the Korean page I linked is the official standard.
> My proposed postal_fmt aligns with these official lines.
>
> To clarify the two formats you found: the second one represents the
traditional
> "Lot Number-based" address system. While it is still understood and
> used in some contexts, the first one—the "Road Name-based" address
system—has
> been the official government standard in South Korea since 2014. My patch
> prioritizes this modern "Road Name" hierarchy as it is the format
officially
> recommended by Korea Post and the Ministry of the Interior and Safety.

Understood.

I just noticed that we are now missing a %c (Country). It's mentioned in
the commit message but not in the change itself. I don't know where that
should go in the new format. I can see that the translation of the postal
service's page you linked to doesn't mention it either. What do you suggest?

> > This also drops %t, the separator between the family and given names.
> > Is this intentional?
>
> Yes, this is intentional. While it is common to use spaces when
> transliterating Korean names into the Latin alphabet (e.g., "Hong
Gildong"),
> it is the standard orthographic rule in the Korean language (Hangul) to
> write the family name and given name together without any spaces
> (e.g., "홍길동").
>
> Since this locale (ko_KR) is primarily intended for native script usage,
> removing the %t separator is necessary to provide a natural and correct
> representation for Korean users.

That makes sense. OK!

> > I am not quite sure if all this metadata is still being maintained in
> > comments this way. ... I'm neutral about this part
>
> I updated the revision and date comments to maintain consistency with
> the existing style of the file. However, if the current glibc policy
> prefers omitting these in favor of git logs, I am happy to remove
> those specific lines in a version 3 patch.
>
> Please let me know if you would like me to submit a v3 with the
> metadata comments removed.

Let's keep it.

For the v3 with "%c", it would be great if you could separate the
notes/salutation from the git commit body so that tooling knows what to
exclude from the commit message. At least my git tooling assumes that the
email's subject line becomes the commit subject, and the email body up to
the "---" line becomes the commit message. I often put my notes after the
"---" so they don't get picked up and put into the commit message. Here's
an example:
https://inbox.sourceware.org/libc-alpha/20260116202016.3863129-1-arjun@redhat.com/

Cheers,
Arjun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20260428/8287abdc/attachment.htm>