I'm sending this again since it did not get through the first time (I
couldn't find it in the mail archive).
Hi, I just installed glibc-2.2.4-2mdk with locales-it-2.3.1.2-4mdk, and
now several programs malfunction. For example several kde programs
(rpmdrake [ver. 1.3-52.1mdk], the kde control center, the kde panel
[both ver. 2.1.1-13mdk], to name a few) have lost (in whole or in part)
their internationalization and now are in english.
On the other hand 'man' (ver. 1.5i2-3mdk), every time it has to display
some error message, shows the following message: "Failed to open the
message catalog man on the path NLSPATH=<none>", but NLSPATH is set to
the (usual?) value of '/usr/share/locale/%l/%N'.
Each time 'perl' (ver 5.600-30mdk), starts, it gives the following
(long) error message:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "it_IT:it",
LC_ALL = (unset),
LC_MESSAGES = "it_IT",
LC_TIME = "it_IT",
LC_NUMERIC = "it_IT",
LC_CTYPE = "it_IT",
LC_MONETARY = "it_IT",
LC_COLLATE = "it_IT",
LANG = "it"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
My interpretation of these facts is that (quoted from the glibc 2.2.4
release notes)
The internal locale format has been changed (again, new in 2.2.4).
All locale information has to be regenerated with localedef. Simply
run
make localedata/install-locales
to install all the files. This might take a while and using the -j
option on SMP systems. If you are upgrading a live system with glibc
2.1 or before you will end up with two sets of the locale data in two
different places (the old data in /usr/share/locale, the new code in
/usr/lib/locale). Keep the old data around until all statically
linked applications which use locales are recompiled. Then remove the
files LC_CTYPE, LC_COLLATE, LC_NUMERIC, LC_MONETARY, LC_TIME, and
SYS_LC_MESSAGES in all subdirectories below /usr/share/locale.
but it appears that locales-??-2.3.1.2-4mdk already has these new files
in the old location, which breaks applications written with the old
locales in mind.
I even tried to download the most recent setup, initscripts and bash
rpms, but they didn't help.
My questions are:
1) Am I right or am I completely out of directions?
2) Is there any way around this problem (maybe a new build of locales-??
with both old and new locales in different directories) ?
Thanks for the attention and the patience.
--
Paolo Pedroni
[EMAIL PROTECTED]
