This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [COMMITTED] Add lang_name to various locales.
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Sat, 23 Nov 2013 18:43:27 -0500
- Subject: Re: [COMMITTED] Add lang_name to various locales.
- Authentication-results: sourceware.org; auth=none
- References: <CAHdAata6P3JXzr7H5gCy7hnGM6kG_xKjMABPvkkv+Qpf-h5N6w at mail dot gmail dot com> <CAHdAatYPogD41S0v4UQnO3ouDx_ZP8YW-10hAJxYY1CLzuxGJw at mail dot gmail dot com> <52913B69 dot 7050603 at redhat dot com>
On Sat, Nov 23, 2013 at 6:34 PM, Carlos O'Donell <carlos@redhat.com> wrote:
> On 11/23/2013 06:24 PM, Chris Leonard wrote:
>> I reverted the bs_BA element of this patch. It generated an error I
>> did not expect when creating the non-UTF locale.
>
> That's odd. Any idea what's wrong?
>
> Cheers,
> Carlos.
>
Having added the comment for lang_name in Cyrillic, I believe it may
have been incompatible with creating the locale for
bs_BA/ISO-8859-2.
Why do we create a Cyrillic locale in a Latin only encoding? Note
this might be good for for Latin encoding of bs_BA@latin, but not sure
why a Cyrllic locale would need a Latin encoding.
I will investigate further, but felt I should quickly and simply
revert a small portion of the commit causing the issue while I look
into it.