This is the mail archive of the
mailing list for the glibc project.
Re: Should glibc provide a builtin C.UTF-8 locale?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Cc: Mike Frysinger <vapier at gentoo dot org>
- Date: Tue, 17 Feb 2015 09:42:06 -0500
- Subject: Re: Should glibc provide a builtin C.UTF-8 locale?
- Authentication-results: sourceware.org; auth=none
- References: <54DB8243 dot 3050903 at redhat dot com> <20150217111943 dot GI544 at vapier>
On 02/17/2015 06:19 AM, Mike Frysinger wrote:
>> Is this the right way forward? Or should we tell the distributions
>> that it is their responsibility to ship and always provide a C.UTF-8?
> i don't see a problem with an initial launch where C.UTF8 is just another
> external locale that needs to be generated. tooling already has to deal with it
> not existing for (1) backwards compatibility and (2) portability to systems that
> lack it entirely. if it turns out to be a problem, or we can get the data/size
> tradeoff to work, then we can always land an update later that makes it builtin.
That's a good point. I think we should move it forward like that then.