On Thu, May 15, 2014 at 12:57:04PM +0200, Zygmunt Krynicki wrote: > Package: src:eglibc > Severity: wishlist > Tags: l10n > > Reading the gettext(3) man page I see the following fragment: > > If the LANGUAGE environment variable is set to a nonempty value, > and the locale is not the "C" locale, the value of LANGUAGE is > assumed to contain a colon separated list of locale names. The > functions will attempt to look up a translation of msgid in each > of the locales in turn. This is a GNU extension. > > This part works as expected. I would like to propose that the same > special-case behavior is used when the locale is "C.UTF-8" as it is > becoming the de-facto "better C" and it is unexpected to see, for > example, translated gettext messages when using such locale.
Until the C.UTF-8 locale is integrated directly into glibc instead of being provide like a standard locale, it's not going to be something easy to do. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140518223300.gc5...@hall.aurel32.net
