From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: /etc/locale vs /etc/env.d/02locale?
Date: Thu, 16 Jun 2011 09:45:57 -0700 [thread overview]
Message-ID: <BANLkTi=9ydzLaFTm9vrO-iL438i-BQ5t0Q@mail.gmail.com> (raw)
In-Reply-To: <itdaij$sm6$1@dough.gmane.org>
On Thu, Jun 16, 2011 at 9:22 AM, Nikos Chantziaras <realnc@arcor.de> wrote:
> On 06/16/2011 06:45 PM, Mark Knecht wrote:
>>
>> Is there a simple explanation concerning the difference between the
>> two locales I have seen on Gentoo machines?
>>
>> 1) /etc/locale, as specified in the installation documents
>>
>> 2) /etc/env.d/02locale as has been discussed on the list recently
>
> There is no /etc/locale. I assume you mean /etc/locale.gen.
I did. thanks.
> That one only
> contains the locales for glibc. You should not specify env vars there. You
> only list raw locales. Mine for example has these contents:
>
> en_US ISO-8859-1
> en_US.UTF-8 UTF-8
>
As does mine.
> /etc/env.d/02locale is of a different format. It's executed as a script, so
> you set your locale-specific env vars there. You only need LANG actually,
> and possibly LC_COLLATE. The whole contents of mine:
>
> LANG="en_US.UTF-8"
> LC_COLLATE="C"
>
I had the first line but not the second which I've added.
I think the root of my question is really the (possibly) unfortunately
use of the word 'locale' for the glibc stuff. I understand the concept
of locales for the system and users, but why does glibc need locales
which are possibly different from those in use on a system by users?
I can make up reasons, like someone from Japan logs into my server to
do work and needs something to use Japanese locales, but he could
likely set those up in .bashrc or something. What is glibc doing with
them?
Thanks,
Mark
next prev parent reply other threads:[~2011-06-16 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 15:45 [gentoo-user] /etc/locale vs /etc/env.d/02locale? Mark Knecht
2011-06-16 16:22 ` [gentoo-user] " Nikos Chantziaras
2011-06-16 16:45 ` Mark Knecht [this message]
2011-06-16 16:54 ` Nikos Chantziaras
[not found] ` <BANLkTikP=J_NeFs-LhYb3RPANhDr74+icg@mail.gmail.com>
2011-06-16 16:23 ` [gentoo-user] " Mark Knecht
2011-06-16 16:47 ` [gentoo-user] " Nikos Chantziaras
2011-06-16 16:56 ` [gentoo-user] " YoYo Siska
[not found] ` <BANLkTimqq_f+69OMmDeZGwvBvX349xUCtg@mail.gmail.com>
2011-06-18 0:50 ` [gentoo-user] " walt
2011-06-18 1:35 ` Nikos Chantziaras
2011-06-18 1:46 ` Peter Humphrey
2011-06-18 21:03 ` walt
2011-06-19 20:46 ` Walter Dnes
2011-06-19 21:47 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=9ydzLaFTm9vrO-iL438i-BQ5t0Q@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox