| 1 |
On 5/11/2011 12:02 PM, Nikos Chantziaras wrote: |
| 2 |
> On 05/11/2011 06:53 PM, Nikos Chantziaras wrote: |
| 3 |
>> On 05/11/2011 06:42 PM, Dale wrote: |
| 4 |
>>> That was quick: |
| 5 |
>>> |
| 6 |
>>> root@fireball / # grep LC_ALL /etc/env.d/* |
| 7 |
>>> root@fireball / # |
| 8 |
>>> |
| 9 |
>>> Guess that is not in env.d anywhere. :/ |
| 10 |
>> |
| 11 |
>> Then I guess you can create it on your own. See: |
| 12 |
>> |
| 13 |
>> http://www.gentoo.org/doc/en/guide-localization.xml#doc_chap3 |
| 14 |
> |
| 15 |
> Heh, according to the guide I linked to, setting LC_ALL is a bad idea |
| 16 |
> :-D So I guess the grep should have been: |
| 17 |
|
| 18 |
The only problem with LC_ALL is that it overrides all of the other LC_* |
| 19 |
variables. When looking for locale information for a given category, the |
| 20 |
order is: |
| 21 |
|
| 22 |
LC_ALL -> LC_{COLLATE|CTYPE|MESSAGES|TIME|NUMERIC|MONETARY} -> LANG |
| 23 |
|
| 24 |
(glibc adds a bunch of other LC_* variables from a POSIX draft that |
| 25 |
never got formalized.) |
| 26 |
|
| 27 |
Setting just LANG= and setting just LC_ALL= have the same ultimate |
| 28 |
result: every localization category uses the same locale. The difference |
| 29 |
is that setting LC_ALL means you can't turn around and redefine, say, |
| 30 |
just LC_TIME to use some other locale's format. |
| 31 |
|
| 32 |
--Mike |
Archives