This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Query about lang_ab field of LC_ADDRESS
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 23 Sep 2013 22:49:34 -0400
- Subject: Re: [RFC] Query about lang_ab field of LC_ADDRESS
- Authentication-results: sourceware.org; auth=none
- References: <CAHdAataNmctX06oNkGxMbmAT=0QPSFN+qOgnA8Egtu5qJ-r9kg at mail dot gmail dot com>
I've answered my own question, so I thought I would share the answer.
Adding a three-letter code to lang-ab generates an error message.
I've fixed this issue where necessary, like in the recently submitted
Chinese locales.
On Sat, Sep 21, 2013 at 11:00 AM, Chris Leonard
<cjlhomeaddress@gmail.com> wrote:
> I see a mix of cases in existing locales for ISO-639 three letter
> language codes with respect to lang_ab of LC_ADDRESS (which is
> supposed to be a two letter code).
>
> In some cases, the lang_ab is left blank (because there is no
> two-letter code for the lang).
>
> In some cases, the three letter code is inserted (in spite of the fact
> that it should only be two letters long).
>
> Which is the more correct behaviour?
>
> cjl