Hello!
Yesterday I updated from glibc-2.4-r1 to glibc-2.4-r2. Since then,
I've got problems with my UTF-8 locale. I suppose, that is because
the UTF-8 denomination seems to have changed from .UTF-8 to .utf8:
[10:17:42 [EMAIL PROTECTED]:~] $ 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
de_DE
de_DE.utf8
[EMAIL PROTECTED]
en_US
en_US.utf8
Before glibc-2.4-r2, it used to be "de_DE.UTF-8" and nto "de_DE.utf8".
I'm also concerned about those first 3 error messages reg. LC_CTYP,
LC_MESSAGES and LC_COLLATE.
Now, when I start some program like vncserver (actually: perl), I get:
[10:18:31 [EMAIL PROTECTED]:~] $ vncserver -help
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "de_DE.utf8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
usage: vncserver [:<number>] [-name <desktop-name>] [-depth <depth>]
[-geometry <width>x<height>]
[-pixelformat rgbNNN|bgrNNN]
<Xvnc-options>...
vncserver -kill <X-display>
That's also especially annoying with KDE programs (I normally
use Gnome). There, when I enter a "special character" like the
German "ö", I only see 2 empty blocks: ?? But that seems only
to affect my local display, it's send out just fine. As an example,
please see
<http://groups.google.de/group/de.test/msg/4eacf9dd61807ad2?dmode=source>
Well - what to do now?
Thanks,
Alexander Skwar
--
If a 6600 used paper tape instead of core memory, it would use up tape
at about 30 miles/second.
-- Grishman, Assembly Language Programming
--
[email protected] mailing list
