[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#261000: console-tools: de_DE.UTF-8@euro does not get caught as UTF-8



At Tue, 27 Jul 2004 01:13:14 +0200,
Denis Barbier wrote:
> > 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.

It's my mistake.  s/cs_ES@euro/cs_ES.UTF-8@euro/g.

> > 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.

I agree with dropping those locales from SUPPORTED.

> > 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.

Thanks!

Regards,
-- gotom



Reply to: