Bug#284137: locale -a reports misleading values for UTF-8 locales
At Sat, 4 Dec 2004 16:44:55 +0100,
Guillermo S. Romero <gsromero@alumnos.euitt.upm.es> wrote:
> gotom@debian.or.jp (2004-12-04 at 2317.58 +0900):
> > So the question falls back to "it's worthwhile to record user
> > requested locale name into locale-archive file". I think it's
> > overkill to support "user requested name UTF-8". Moreover, if an
> > application needs to check locale availability, such application
> > everytime needs to parse both canonical name and user requested
> > (non-canonical name). So I think this wishlist is not acceptable.
> >
> > If you have objection from the technical point of view, please let us
> > know. Otherwise, I would like to close this report to avoid
> > increasing a lot of glibc wishlist.
>
> If you use utf8 instead of UTF-8 in the env vars, you start getting
> "locale not supported by Xlib" errors, and that is the reason I have
> filled this bug, because it was the logical thing to do after the
> first bug I filed related to utf8 vs UTF-8.
>
> So please see bug #282715 filed against xlibs-data and named
> "locale.alias contents do not match with typical LANG or LC_* values",
> so we can decide which of all the advices I have got is the most
> correct, and which of the two bugs is the one that should be kept
> open.
So? Denis already explained the reason nicely. And I can't
understand why it's related with "locale -a".
Regards,
-- gotom
Reply to: