Bug#748215: gettext(3) should special case both C and C.UTF-8 wrt LANGUAGE lookup
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.
-- System Information:
Debian Release: jessie/sid
APT prefers utopic-updates
APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.0-24-generic (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Reply to: