On 12/4/06, Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote:
On Monday 04 December 2006 19:30, Mark Knecht wrote:
>    I don't understand locales, or not really. I get that they say
> something about where the machine is running and what character
> set/sets the machine should use, but that's as far as I go with it.
> It's never been much of a problem.
[SNIP]
> Solution: To properly set the locale charset make sure the LC_*
> environment variables are set. Normally the distribution setup tools
> take care of this.
>
>    I'm going back looking at the Gentoo Quick Install Guide. It talks
> about locales.build and locales.gen for recent version of glibc.
> Section 2.37 at
[SNIP]

It's properly covered in the Gentoo Localization Guide [1]. You need to
move/convert your locales.build to a locale.gen, run `locale-gen` and make
sure it doesn't generate any errors and set LANG in /etc/env.d/02locale...

If you need help you will have to post the contents of locale.gen and the
output of `locale-gen`.

[1] http://www.gentoo.org/doc/en/guide-localization.xml

--
Bo Andresen

Hi Bo,
  First, thanks in advance. I really appreciate all your help. I
think I'll ask a few questions as I go along, if that's OK. Thanks
again.

  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:

lightning etc # ls /etc/env.d/
00basic         10libx11                  50gconf
75emul-linux-x86-compat
02distcc        10xkeyboard-config        50glib2                90games
03opengl        15openmotif-2.2           50gtk2                 99fltk-1.1
04multilib      20java                    50ncurses
99gentoolkit-env
05binutils      20java-config             50qtdir3               99libstdc++
05compiler      30java-finalclasspath     60gstreamer-0.10       binutils
05gcc           45emul-linux-x86-qtlibs   60gstreamer-0.8        gcc
05portage.envd  45kdepaths-3.5            60ladspa               java
08nspr          45qt3                     70less
08nss           50emul-linux-x86-gtklibs  75emul-linux-x86-base
lightning etc #

The current contents of locales.build are shown here. Seems fairly
generic but what do I know? ;-)

lightning ~ # cat /etc/locales.build
# This file names the list of locales to be built when glibc is installed.
# The format is <locale>/<charmap>, where <locale> is a locale from the
# /usr/share/i18n/locales directory, and <charmap> is name of one of the files
# in /usr/share/i18n/charmaps/. All blank lines and lines starting with # are
# ignored. Here is an example:
# en_US/ISO-8859-1

en_US/ISO-8859-1
en_US.UTF-8/UTF-8
lightning ~ #

I ran locale-gen. No error messages:

lightning ~ # locale-gen
* 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 ...

* Generating 2 locales (this might take a while) with 1 jobs
*  (1/2) Generating en_US.ISO-8859-1 ...                           [ ok ]
*  (2/2) Generating en_US.UTF-8 ...                                   [ ok ]
* Generation complete
lightning ~ #

  Unfortunately there is no locale.gen file generated:

lightning etc # ls -la /etc/locale.gen
ls: cannot access /etc/locale.gen: No such file or directory
lightning etc #

lightning etc # updatedb
lightning etc # slocate locale.gen
/usr/share/man/man5/locale.gen.5.gz
lightning etc #

locale-gen seems to read locales.build, I think:

lightning etc # locale-gen -l
en_US.ISO-8859-1
en_US.UTF-8
lightning etc #

  So far it seems like this isn't working for me. I'll wait for some
feedback and keep reading.

Thanks,
Mark

--
[email protected] mailing list

Reply via email to