Re: Bug#261000: console-tools: de_DE.UTF-8@euro does not get caught as UTF-8
On Sat, Jul 24, 2004 at 02:53:53PM +0200, Kilian Krause wrote:
> Hi Denis,
>
> > > > > Maybe it's sufficient to have only .UTF-8 locales and the @euro can be
> > > > > obsoleted.
> > > >
> > > > Absolutely.
> > >
> > > Thus, does such a bug already exist filed against the locales package?
> >
> > I don't think so.
> > Maybe you could discuss this issue on the debian-glibc mailing list
> > first.
> > Anyway, is there any problem related to console-tools, or should this
> > bugreport be closed or reassigned to the locales package?
>
> well, let's say that i'd wish (for console-tools) to have a more
> meaningful errormsg (as no other program was/is complaining about that
> setting so far). So either make the output go 2>/dev/null or at least
> let the user know that having an "export ..." in /etc/environment is BAD
> by either locales or console-tools.
> If someone can give me a helping hand to take this to debian-glibc, i'd
> be happy to help, but all on my own i feel somewhat too bad prepared to
> just walk up there and tell ".UTF-8@euro is OBSOLETE, so remove it and
> leave only .UTF-8 in".
[Please respect the Mail-Followup-To debian-glibc and Kilian Krause]
Debian-glibc folks,
XFree86 had to be patched to accept .UTF-8@euro locales, other
applications like console-tools seem to have trouble too with these
locales. Of course those applications should be fixed, relying on
locale names is deeply broken, but .UTF-8@euro and .UTF-8 locales are
identical, so why are .UTF-8@euro needed at all?
It seems that many European people are confused and believe that if
both locales exist, .UTF-8@euro does provide some extra fonctionnality
over .UTF-8.
In order to prevent useless duplicates, I believe that .UTF-8@euro
locales should be removed from the locales.config maintainer script
(but not from /usr/share/i18n/SUPPORTED).
In this bugreport, there had also been discussions regarding
/etc/environment. This file is undocumented (or its documentation is not
visible), maybe a comment should be added by the locales package when
this file is created? This comment should explain that this file is
not sourced by script shells, and should only consist of comments and
lines in the form variable=value.
Denis
Reply to: