| 1 |
On Sun, 15 Jul 2012 13:36:29 -0700, Mark Knecht wrote: |
| 2 |
|
| 3 |
> > /etc/locale.gen defines which locales are supported on your system. |
| 4 |
> > |
| 5 |
> > /etc/env.d/02locale defines which of these locale you are actually |
| 6 |
> > using by setting LANG and LC_* environment variables. Files |
| 7 |
> > in /etc/env.d/ end up in /etc/profile.env (by running the env-update |
| 8 |
> > command), which is evaluated from /etc/profile and as such by every |
| 9 |
> > shell. If you want different settings for your user, override that |
| 10 |
> > stuff in your ~/.bash_profile. |
| 11 |
|
| 12 |
> So to check my understanding of your answer (and thanks for the |
| 13 |
> answer!) unless a locale is defined in /etc/locale.gen, and then |
| 14 |
> locale-gen has also been run, then that locale is not even available |
| 15 |
> to be evaluated by /etc/profile. |
| 16 |
|
| 17 |
The default, if you have not edited /etc/locale.gen, is to install all |
| 18 |
locales. They are built when glibc is emerged, so they will all be |
| 19 |
available if you do nothing. /etc/locale.gen enables you to configure |
| 20 |
which locales are built, local-gen enables you to apply the new setting |
| 21 |
without recompiling glibc. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
A good pun is its own reword. |
Archives