Re: Bug#261000: console-tools: de_DE.UTF-8@euro does not get caught as UTF-8
On Mon, Jul 26, 2004 at 12:22:14AM +0900, GOTO Masanori wrote:
> At Sat, 24 Jul 2004 22:46:21 +0200,
> Denis Barbier wrote:
[...]
> > 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).
>
> Correct, I agree with your observation. For example, ca_ES has three
> entries (ca_ES is appeared firstly in locales):
>
> ca_ES ISO-8859-1
> ca_ES.UTF-8 UTF-8
> ca_ES.UTF-8@euro UTF-8
> ca_ES@euro ISO-8859-15
>
> But ca_ES@euro is the same as ca_ES.
Hmmm, not sure we are speaking of the same issue, ca_ES and ca_ES@euro
have different encodings.
> In addition, I think it's good idea to remove @euro from SUPPORTED
> after sarge. The upstream cvs still has those locales, but it should
> be removed in the future propor period.
My post was about .UTF-8@euro only, they are redundant because they
have the same encoding as .UTF-8 ones. Other @euro locales use
ISO-8859-15, and are needed by many users.
I had a closer look, and those .UTF-8@euro locales are added by
debian/patches/locales-supported.dpatch, which means that they are
Debian specific. They were introduced in 2.3.1-12:
- debian/patches/locales-supported.dpatch: This dpatch addes many
locales especially for UTF-8 and ISO-8859-15, to display debconf
locale menu using SUPPORTED.orig.
(Closes: #135334, #154556, #177472, #99623, #130517)
They can either be dropped from SUPPORTED (maybe not a good idea because
of the near release), or filtered by locale-gen.
> > 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.
>
> I agreed, too. I want to clear the meaning of this file. pam_env
> uses this file, but I don't know this is really good way to define
> LANG environment variable.
Right, but this won't change before sarge is released.
> Moreover, it's good idea to describe: how to handle the basic
> environment variable (for example LANG) in debian.
>
> Denis, could you work this kind of issue if you have spare time?
I will try to.
Denis
Reply to: