Bug#284137: locale -a reports misleading values for UTF-8 locales

["Guillermo S. Romero" <gsromero@alumnos.euitt.upm.es>]

Hi:

gotom@debian.or.jp (2004-12-05 at 0100.56 +0900):
> So?  Denis already explained the reason nicely.  And I can't
> understand why it's related with "locale -a".

Denis said I have to use UTF-8 so Xlib works, ignoring what locale -a
report, and you say utf8 is the right value, but that will make Xlib
not work. Denis reasoning:

  The name listed in /usr/share/i18n/SUPPORTED is en_GB.UTF-8 and it
is displayed when running 'dpkg-reconfigure locales', so you should
use this one.

And yours:

  Glibc uses "canonical locale name" with lower-case, hyphen-removed
...  So using canonical name is the right way.

So what I am asking is if Xlib should use utf8 following your
reasoning or locale -a should report UTF-8 so it's output is useful
and users do not set env vars wrongly. You both are explaining the
reasons for each problem, closing or wanting to close the bugs, but
providing different solutions.

Or in other words, which is the unified value for all apps in a Debian
system, that all apps should support (technical issue) and also report
(cosmetic issue), and thus which of the two bugs it the right one,
maybe expanding to other parts of the Debian system, so they also
match.

Regards,

GSR