This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Query about lang_ab field of LC_ADDRESS


Keld,

I'm not quite sure I understand your response.

What do you recommend for a lang that only has a three-letter code?

If you put three letters in lang_ab, it causes an error message.

lang_term can be filled with three letter code.

On Tue, Sep 24, 2013 at 3:17 AM,  <keld@keldix.com> wrote:
> There ought to be entries for all the ISO 639 codes.
>
> Best regards
> keld
>
> On Mon, Sep 23, 2013 at 10:49:34PM -0400, Chris Leonard wrote:
>> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]