On 26 May, David Puryear wrote:
> Hi all,
> 
> Thanks to everyone, I got few different answers to this. I used answer from 
> Manoj Srivastava <[EMAIL PROTECTED]> who wrote:
> 
>         From my .bash_vars file:
> ================================================================
> LANG=en_US
> export LANG
> LC_ALL=C
> export LC_ALL
> ================================================================
>     
>From the info documentation:

"    The simplest way for the user to choose a locale is to set the
environment variable `LANG'.  This specifies a single locale to use for
all purposes."

And further on:

"`LC_ALL'
     This is not an environment variable; it is only a macro that you
     can use with `setlocale' to set a single locale for all purposes.

`LANG'
     If this environment variable is defined, its value specifies the
     locale to use for all purposes except as overridden by the
     variables above."


So LC_ALL will override every other locale setting. I did some testing
and can just confirm that. So you can also delete the LANG=en_US line.

Little Test:
bash$ export LANG=de_DE
bash$ date
Don Mai 29 04:32:13 CEST 1997
bash$ export LC_ALL=fr_FR
bash$ date
jeu mai 29 04:32:31 CEST 1997

Most likely the locales C is similar (or even equal) to en_US, so you
don't get any drawbacks (the docs on this matter are unusual thin for
linux).

But I need German locales. The locales support doesn't seem to be
broken in general. date for example does respect the locales.
But any perlscript I start does show a error (examples from the doc
directory or *inst script from debian packages).

So I decided to file a bugreport against perl 5.004-1. Let's see if
someone with better abilities can solve this.

BTW: even perl -v gives out the warnings about missing locales

I suppose something has changed from libc5 to libc6 in locales support.
Most likely perl uses some non-offical feature from libc5 which doesn't
exist on libc6 any more.

Ciao,
        Martin


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Reply via email to