| 1 |
Mark Knecht wrote: |
| 2 |
|
| 3 |
> You may be correct about setting all of this in 02locale. I noticed |
| 4 |
> that the Gentoo formatting stuff for vi is treating LC_ALL and |
| 5 |
> LC_COLLATE differently than LINGUAS. The manual seems to say set |
| 6 |
> system wide stuff in 02locale and user stuff in your own account. |
| 7 |
|
| 8 |
They are different. |
| 9 |
|
| 10 |
LINGUAS is a build-time hint for localized programs that lists which |
| 11 |
languages you want translations for. It has no effect at run-time other |
| 12 |
than ensuring that your selected languages are available. |
| 13 |
|
| 14 |
The LC_* variables, and LANG, are run-time settings that tell the C |
| 15 |
library which locale to use. LC_COLLATE, for example, tells vi how to |
| 16 |
sort things alphabetically. |
| 17 |
|
| 18 |
Just as an aside, I see frequent warnings not to set LC_ALL because it's |
| 19 |
"dangerous", but that seems like a vast overreaction to me. LC_ALL is a |
| 20 |
global setting that overrides all of the other LC_ variables with a |
| 21 |
single setting. The "danger" is that you cannot then individually |
| 22 |
override the behavior, say to use a different currency or sorting |
| 23 |
format, but IMO the people who need to do that are the exception, and |
| 24 |
would clearly know how to do it. |
| 25 |
|
| 26 |
For a single user system with a single locale where all the LC_* |
| 27 |
variables have the same value anyway, setting LC_ALL to "en_US" and |
| 28 |
settings the other half-dozen LC_* variables to "en_US" has the same effect. |
Archives