public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] locales questions
Date: Tue, 5 Dec 2006 12:08:50 -0800	[thread overview]
Message-ID: <5bdc1c8b0612051208s14c6d247r66afb928b8bd3be5@mail.gmail.com> (raw)
In-Reply-To: <200612042112.32836.bo.andresen@zlin.dk>

Bo,
   Hi. I'm sure you're frustrated with me. Sorry. I really am reading
these docs but there seem to be things I'm not quite understanding or
things missing from the docs. Probably it's just me. Sorry.

On 12/4/06, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> On Monday 04 December 2006 20:33, Mark Knecht wrote:
> [SNIP]
> >    Reading the localization and quick install guides I've become a bit
> > more confused. The localization guide says the LC_* settings are done
> > in /etc/env.d/02locale but this doesn't exist here, not even after
> > running locale-gen:
> [SNIP]
>
> Setting LANG in 02locale is preferred over setting LC_ALL since that allows
> you to override it with LC_ALL on the command line. And no, it isn't
> generated automatically. You must create this file by yourself. After that
> you need to run `env-update && source /etc/profile`.

OK, so I've now created 02locale by hand. However I cannot find a
document that clearly states what an English only speaker/reader who
lives in the U.S. would prefer here. Trying to follow the Eupean
centric example on the web page I now have:

lightning ~ # cat /etc/env.d/02locale
LC_ALL="en"
LANG="en"
lightning ~ #

I hope that's OK. I think the changes took hold:

lightning ~ # env-update && source /etc/profile
>>> Regenerating /etc/ld.so.cache...
lightning ~ # env | grep -i LC_
LC_ALL=en
lightning ~ #

I've added

LINGUAS="en"

to my make.conf file as required.

>
> > The current contents of locales.build are shown here. Seems fairly
> > generic but what do I know? ;-)
> >
> > lightning ~ # cat /etc/locales.build
> [SNIP]
> > en_US/ISO-8859-1
> > en_US.UTF-8/UTF-8
> > lightning ~ #
>
> The syntax of locale.gen is more strict than the syntax of locales.build. The
> above is valid for locales.build. In locale.gen it must be:
>
> # cat /etc/locale.gen
> en_US ISO-8859-1
> en_US.UTF-8 UTF-8
>
> You must create that file and remove locales.build manually before running
> locale-gen. locale-gen told you that if you bothered to read it...:

I promise - I read that 10 times. It just doesn't read to me that I
need to do it by hand even though it seems to say so. Sorry!

>
> [SNIP]
> >  * You should upgrade your /etc/locales.build to /etc/locale.gen
> >  * and then remove /etc/locales.build when you're done.
> >
> >  * Automatically importing locales from /etc/locales.build ...
> >  * You really should do this yourself ...
> [SNIP]
>
> Finally `locale -a` will show you valid values for LANG and LC_*.
>
> # locale -a
> en_US
> en_US.utf8

OK, but in my case it's still not working quite right:

lightning etc # cat /etc/locale.gen
en_US ISO-8859-1
en_US.UTF-8 UTF-8
lightning etc # cat /etc/env.d/02locale
LC_ALL="en"
LANG="en"
lightning etc # env-update && source /etc/profile
>>> Regenerating /etc/ld.so.cache...
lightning etc # locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
en_US
en_US.utf8
lightning etc #

So, I think I still have work to do here.

Again, thanks very much for the help and sorry for being so dense about this.

Cheers,
Mark

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-12-05 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 18:30 [gentoo-amd64] locales questions Mark Knecht
2006-12-04 18:44 ` Bo Ørsted Andresen
2006-12-04 19:33   ` Mark Knecht
2006-12-04 20:12     ` Bo Ørsted Andresen
2006-12-05 20:08       ` Mark Knecht [this message]
2006-12-05 20:22         ` Bo Ørsted Andresen
2006-12-05 21:27           ` Mark Knecht
2006-12-05 21:59             ` Bo Ørsted Andresen

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=5bdc1c8b0612051208s14c6d247r66afb928b8bd3be5@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-amd64@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