[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Fwd: Re: [kde-linux] Wrong language detection in KDE since 3.1
From:       "Erik K. Pedersen" <erik () binghamton ! edu>
Date:       2003-03-29 8:50:00
[Download RAW message or body]

The discussion below scares me. I want to run KDE programs in Danish and 
command line programs in English. The great unification schemes advocated by 
the mostly monolingual redhat staff is taking this possibility away. When I 
installed redhat 8.0 KDE_LANG no longer had an effect, and all programs were 
in Danish. I really hope the KDE-developers don't go along with something 
where KDE only can choose language through the LANG variable.

I hope there are somebody on this list who can assure me I can continue to do 
what I want.

Erik

Am Friday 28 March 2003 21:58 schrieb Lukáš Tinkl:
> Dne pá 28. března 2003 17:01 Ingo Klöcker napsal(a):
> > Why is KDE's behavior wrong? Let's have a look at the man page for
> > locale(7):
> > =====
> > If the second argument to setlocale() is empty string, "", for the
> > default  locale, it is determined using the following steps:
> > 1. If there is a non-null environment variable LC_ALL, the value of
> >    LC_ALL is used.
> > 2. If an environment variable with the same name as one of the
> >    categories above exists and is non-null, its value is used for that
> >    category.
> > 3. If there is a non-null environment variable LANG, the value of LANG
> >    is used.

So the correct preference order is:

LANG
LC_MESSAGES
LC_ALL

> > According to the aforementioned man page to following change would
> > correct KDE's language determination:
> > =====
> > -      langs << QFile::decodeName( ::getenv("LC_CTYPE") );
> > -      langs << QFile::decodeName( ::getenv("LC_MESSAGES") );
> >        langs << QFile::decodeName( ::getenv("LC_ALL") );
> > +      langs << QFile::decodeName( ::getenv("LC_MESSAGES") );
> >        langs << QFile::decodeName( ::getenv("LANG") );

Doesn't this do prefefence on LC_ALL?!? Looks wrog to me.

Chris

-------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]