Re: Bug#693446: libc-bin: C.UTF-8 locale shows bogus dates
On Sun, Nov 18, 2012 at 08:47:10PM +0000, Thorsten Glaser wrote:
> Aurelien Jarno dixit:
>
> >Indeed, LC_TIME has been written using en_US.UTF-8 as an example.
>
> Ah, okay.
>
> >> Can we please have the C.UTF-8 locale be a copy of the C locale
> >> with *only* the encoding set to UTF-8, nothing else changed?
> >
> >History has shown that writing such a locale is not as easy as you
> >think.
>
> Right, especially as it’s kinda hard to take ‘C’ as base
> when it’s the absence of localisation in most cases…
>
There is no C locale in the definitions, so you can't use it as a base.
If you want to have a C.UTF-8 locale, you have to write a locale
definition which is already almost 400000 lines long. One has to take
parts from existing locales. Expect issues there.
Oh and if you think we should just not provide LC_TIME entries in the
locale definition, you get bug #661878.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: