On Wednesday 27 September 2006 22:48, Bo Ørsted Andresen wrote:
> `locale-gen --config /etc/locale.gen` is run by pkg_postinst() of
> sys-libs/glibc.
Seems reasonable.
> What is the output of:
>
> # egrep -v '^#|^$' /etc/locale.gen
It just happened that emerge -e world had reached glibc as I read this, so I
waited for it to end and then paused the emerge. This is the result:
# egrep -v '^#|^$' /etc/locale.gen
en_GB
en_GB ISO-8859-1
en_GB ISO-8859-15
en_GB.UTF-8 UTF-8
I assume there's a typo there somewhere, but it seems to me to match the
examples given in /usr/share/i18n/SUPPORTED. I know the -15 variant isn't
supported (by what? It isn't clear), and I can remove it if necessary.
Output from glibc postinst:
* Generating 3 locales (this might take a while)
* (1/3) Generating en_GB ...
/usr/share/i18n/locales/en_GB:25: LC_IDENTIFICATION: unknown character in
field `address'
/usr/share/i18n/locales/en_GB:60: LC_MONETARY: unknown character in field
`currency_symbol' [ !! ]
* (2/3) Generating en_GB.ISO-8859-1 ...
cannot open locale definition file `ISO-8859-1': No such file or directory
[ !! ]
* (3/3) Generating en_GB.ISO-8859-15 ...
cannot open locale definition file `ISO-8859-15': No such file or directory
[ !! ]
* Bad entry in locale.gen: 'UTF-8 '; skipping
* Generation complete
After this, I get:
# locale -a
C
POSIX
en_GB
and I have to run locale-def again to re-create my locales, thus:
# localedef -c -i en_GB -f ISO-8859-15 en_GB.ISO-8859-15
# localedef -c -i en_GB -f ISO-8859-1 en_GB.ISO-8859-1
# localedef -c -i en_GB -f UTF-8 en_GB.UTF-8
(no errors reported)
Then:
# locale -a
C
POSIX
en_GB
en_GB.iso88591
en_GB.iso885915
en_GB.utf8
Thanks for pointing out the stage at which my locales are getting zapped; it
helped me this time by coincidence, but it would be good to find the
problem and fix it.
--
Rgds
Peter
--
[email protected] mailing list
