Bug#693446: libc-bin: C.UTF-8 locale shows bogus dates
On Fri, Nov 16, 2012 at 03:46:55PM +0000, Thorsten Glaser wrote:
> Package: libc-bin
> Version: 2.13-35
> Severity: important
>
> Hi!
>
> Reporting against libc-bin as that’s where this locale comes from:
> tg@freewrt:~ $ dpkg -S /usr/lib/locale/C.UTF-8
> libc-bin: /usr/lib/locale/C.UTF-8
>
> Verified to exist in sid (2.13-36).
>
> tg@freewrt:~ $ LC_ALL=C.UTF-8 perl -MPOSIX -e 'print strftime('\''%a %b %e %X %Y'\'', localtime())."\n";'
> Fri Nov 16 03:42:25 PM 2012
>
> Wrong. But the C locale is right:
>
> tg@freewrt:~ $ LC_ALL=C perl -MPOSIX -e 'print strftime('\''%a %b %e %X %Y'\'', localtime())."\n";'
> Fri Nov 16 15:42:26 2012
>
> I think I know where this one comes from:
>
> tg@freewrt:~ $ LC_ALL=en_US.UTF-8 perl -MPOSIX -e 'print strftime('\''%a %b %e %X %Y'\'', localtime())."\n";'
> Fri Nov 16 03:42:32 PM 2012
> tg@freewrt:~ $ LC_ALL=en_GB.UTF-8 perl -MPOSIX -e 'print strftime('\''%a %b %e %X %Y'\'', localtime())."\n";'
> Fri Nov 16 15:42:36 2012
Indeed, LC_TIME has been written using en_US.UTF-8 as an example.
> 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. It's the goal to have *only* the encoding set to UTF-8, but
there are always some small issues like this one slipping in.
> Can we please get this fixed in wheezy?
>
That will be fixed in the next upload.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: