public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: /etc/locale vs /etc/env.d/02locale?
Date: Thu, 16 Jun 2011 19:47:52 +0300	[thread overview]
Message-ID: <itdc32$7pe$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTinPXJUwj_94fecSWO6A+nJOJX0JvQ@mail.gmail.com>

On 06/16/2011 07:23 PM, Mark Knecht wrote:
> On Thu, Jun 16, 2011 at 9:00 AM, Paul Hartman
> <paul.hartman+gentoo@gmail.com>  wrote:
>> On Thu, Jun 16, 2011 at 10:45 AM, Mark Knecht<markknecht@gmail.com>  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
>>
>> I'm not near a Gentoo machine right now, but off the top of my head IIRC:
>>
>> /etc/locale.gen contains a list of locales to be compiled when glibc
>> is emerged. These will be available to be used.
>>
>> /etc/env.d/02locale specifies which of those locales you actually want
>> to use for the system-wide default (the LC variables)
>
> Thanks for the response Paul.
>
> Does that mean that the /etc/locale.gen is used only by glibc and not
> really by the system? If so, what is glibc doing with these beyond
> letting me system run programs?

It allows you to have locales to use in /etc/env.d/02locale ;-)  If you 
want to set LANG=en_US.UTF-8 in 02locale, you of course need the files 
for that specific locale/encoding.  To get them, you need to write 
"en_US.UTF-8 UTF-8" in locale.gen.  Not sure why you're not getting the 
comments in your locale.gen, but here there are, at the top of the file:

# /etc/locale.gen: list all of the locales you want to have on your system
#
# The format of each line:
# <locale> <charmap>
#
# Where <locale> is a locale located in /usr/share/i18n/locales/ and
# where <charmap> is a charmap located in /usr/share/i18n/charmaps/.
#
# All blank lines and lines starting with # are ignored.
#
# For the default list of supported combinations, see the file:
# /usr/share/i18n/SUPPORTED
#
# Whenever glibc is emerged, the locales listed here will be automatically
# rebuilt for you.  After updating this file, you can simply run 
`locale-gen`
# yourself instead of re-emerging glibc.




  reply	other threads:[~2011-06-16 17:11 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
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     ` Nikos Chantziaras [this message]
2011-06-16 16:56     ` 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='itdc32$7pe$1@dough.gmane.org' \
    --to=realnc@arcor.de \
    --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