Should glibc provide a builtin C.UTF-8 locale?
Carlos O'Donell
carlos@redhat.com
Tue Feb 17 14:42:00 GMT 2015
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.
> -mike
That's a good point. I think we should move it forward like that then.
Cheers,
Carlos.
More information about the Libc-alpha
mailing list