This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
Re: Propose we allow locales without country codes.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Chris Leonard <cjlhomeaddress at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Keld Simonsen <keld at keldix dot com>, Petr Baudis <pasky at ucw dot cz>, libc-locales at sourceware dot org, Andreas Jaeger <aj at suse dot com>, Adam Conrad <adconrad at 0c3 dot net>
- Date: Mon, 25 Nov 2013 13:59:50 -0500
- Subject: Re: Propose we allow locales without country codes.
- Authentication-results: sourceware.org; auth=none
- References: <52936433 dot 1040808 at redhat dot com> <CAHdAatZi6G=7onOB0fKv1Be6fiwipEFmddG2GhmH+KJqOZHHGw at mail dot gmail dot com>
On 11/25/2013 10:19 AM, Chris Leonard wrote:
> On Mon, Nov 25, 2013 at 9:52 AM, Carlos O'Donell <carlos@redhat.com> wrote:
>> Community,
>>
>> I'm proposing we allow locales without country codes in order
>> to accept international languages without country codes as
>> valid locales e.g. eo.
>>
>> The infrastructure in glibc appears to support locales without
>> country codes. We don't know what issues might crop up downstream.
>> We should just fix downstream as new locales without country codes
>> are created.
>>
>> Does anyone object to this? Does anyone see any serious problems?
>>
>> Cheers,
>> Carlos.
>
>
> It is worth noting that Debian/Ubuntu downstreams seem to use
> lang-only locales to solve the lang-eo issue, so there is some
> indication that this will work. I'd love to know what Redhat does.
We don't ship any locales that lack geographic region with the obvious
exception of POSIX, and i18n (ISO/IEC 14652).
Given that POSIX and i18n work it must mean that downstream tools can
consume a locale without geographic region.
Either way I assume your comments mean you are in support of my proposal?
Cheers,
Carlos.