View previous topic :: View next topic |
Author |
Message |
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Thu Oct 30, 2003 9:45 pm Post subject: UTF-8 problem since last glibc update |
|
|
I used to have UTF-8 working very well. Then I went ~x86. I've been trying to get UTF-8 back to 100% since, but it hasn't worked, so now I come to you. I have done the Code: | localedef -v -c -i en_US -f UTF-8 /usr/share/locale/en_US.UTF-8 | . I have made my /etc/env.d/02locale say Code: | LANG="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
| . However, I still get this -every- time I run an emerge:
Code: | perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
|
Any suggestions? I'm recompiling glibc again right now...
Specs:
Kernel: Kernel 2.6 test6-mm4
GLIBC: glibc-2.3.2-r8
GCC: gcc-3.2.2-r2
USE flags: "3dnow alsa apache2 -apm breakme cdr -cjk crypt cups directfb emacs gb gd gnomedb gtk2 joystick mad mmx nls oggvorbis -pcmcia pda plotutils ppds python samba -sse svga tiff truetype usb videos wxWindows Xaw3d xml xml2 xv"
Hardware specs are in the sig. _________________ Registered Linux User #263260 |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Fri Oct 31, 2003 2:16 am Post subject: |
|
|
Help meeeeeeeeeeeee... Please? _________________ Registered Linux User #263260 |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Fri Oct 31, 2003 11:48 am Post subject: |
|
|
I don't want to be annoying, but I -will- keep bumping this. _________________ Registered Linux User #263260 |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Sat Nov 01, 2003 6:29 pm Post subject: |
|
|
I'm not gonna give up. _________________ Registered Linux User #263260 |
|
Back to top |
|
|
kallamej Administrator
Joined: 27 Jun 2003 Posts: 4975 Location: Gothenburg, Sweden
|
Posted: Sat Nov 01, 2003 9:04 pm Post subject: |
|
|
The locales are in /usr/share/i18n/locales on my system. _________________ Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Sun Nov 02, 2003 3:27 am Post subject: |
|
|
Behold, a brave soul replies. Yeah, I localedef'd into there with no visible results. But it was a good try! Thanks! _________________ Registered Linux User #263260 |
|
Back to top |
|
|
sa Guru
Joined: 10 Jun 2002 Posts: 450
|
Posted: Sun Nov 02, 2003 6:14 am Post subject: |
|
|
the arguments you used above for localedef look a little weird to me (not sure if you are supposed to put the full path): try
"localedef -c -f UTF-8 -i en_US en_US.UTF-8"
what does "locale -a | grep en_US" tell you? |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Sun Nov 02, 2003 1:51 pm Post subject: |
|
|
Code: |
Desktop root # localedef -a | grep en_US
en_US
en_US.iso88591
en_US.utf8
Desktop root #
|
Strange, isn't it. Maybe perl needs recompiling... _________________ Registered Linux User #263260 |
|
Back to top |
|
|
kallamej Administrator
Joined: 27 Jun 2003 Posts: 4975 Location: Gothenburg, Sweden
|
Posted: Sun Nov 02, 2003 5:46 pm Post subject: |
|
|
Hmm, does this page help anything. This seems to work for me: Code: | localedef -i sv_SE -f UTF-8 sv_SE.UTF-8 |
and then Code: | LC_CTYPE=sv_SE.UTF-8 xterm |
and the error messages I got before the localedef disappears. Note also that there is a difference between using the full path or not in the localdef command. _________________ Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Mon Nov 03, 2003 11:35 am Post subject: |
|
|
Hmm... I changed the values of "LC_CTYPE" etc to en_US.utf8 and the error went away. Now the only error I get is
Code: | Error: Locale not supported by Xlib.
Reverting to "C" locale |
_________________ Registered Linux User #263260 |
|
Back to top |
|
|
kallamej Administrator
Joined: 27 Jun 2003 Posts: 4975 Location: Gothenburg, Sweden
|
Posted: Mon Nov 03, 2003 12:27 pm Post subject: |
|
|
Well, according to the page I linked, that's because X only accepts UTF-8 as a valid name for UTF-8, whilst glibc is not so picky. _________________ Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
Back to top |
|
|
Roguelazer Veteran
Joined: 10 Feb 2003 Posts: 1233 Location: San Francisco, CA
|
Posted: Mon Nov 03, 2003 8:18 pm Post subject: |
|
|
So why does en_US.utf8 work with everything except Xlib and en_US.UTF-8 work with nothing?
[edit]Hmmm... Changed the values back to UTF-8. No more error messages from anything. Maybe my "emerge perl xfree glibc" fixed something. Maybe it was somethign else. Oh well.[/edit]
SOLVED! _________________ Registered Linux User #263260 |
|
Back to top |
|
|
kallamej Administrator
Joined: 27 Jun 2003 Posts: 4975 Location: Gothenburg, Sweden
|
Posted: Mon Nov 03, 2003 8:43 pm Post subject: |
|
|
Yeah, it's a good question why the UTF-8 setting didn't work right from the start. I had a similar problem once where my system thought that there was a trailing space in my locale setting, 'sv_SE '. Some nonsense editing of my 02locale solved it. _________________ Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
Back to top |
|
|
DumbAss Apprentice
Joined: 30 Sep 2003 Posts: 247 Location: 't Steen
|
Posted: Fri Jan 23, 2004 9:14 am Post subject: |
|
|
I got the same problem at the moment. I've been months without the error and then I removed the .UTF-8 from my 02locale because I wanted to emerge redhat-artwork. Then I changed the settings back and I got this error messages.
I'm gonna search for the spaces and maybe recompile perl. I'll let you know what the problem was. |
|
Back to top |
|
|
|