Hi! On Sun, Jun 15, 2008 at 03:26:05PM -0600, Philip Guenther wrote: >[...]
>... >>> I found a workaround: >>> # ln -s /usr/share/locale/en_GB.ISO8859-1 >>> /usr/share/locale/en_US.UTF-8 >That seems like a really bad idea to me. UTF-8 and ISO8859-1 are >fundamentally different: UTF-8 uses variable-length characters while >ISO8859-* uses fixed-width (8bit) characters. Giving the locale calls >the same data for those two is likely to result in incorrect behavior >for all characters >127. Wouldn't it be better to simply not lie and >just set the locale to en_US.ISO8859-1? Doesn't work for me either: $ LANG=en_GB.ISO8859-1 perl -e 1 perl: warning: Setting locale failed. [...] $ LANG=en_GB.ISO-8859-1 perl -e 1 perl: warning: Setting locale failed. [...] >[...] >If nothing obvious sticks out, consider debugging further by checking >the environment seen by your .xsession (if you xdm) by adding a line >like this: > env > $HOME/.xsession-env.out >to it. Similarly, check the shell's environment by doing something >similar from your .profile. Oh, right. grepping .xsession or .xinitrc for LANG and LC_ could help too. >> I tried to figure out why this problem occurs and >> following to that I noticed that this perllocale >> warning only comes up when dropping a pkg_* directly >> in xterm. When using screen in an xterm and dropping >> pkg_* to it everything will work fine. Same for tty >> shells without X where everything works fine too. >Windows inside screen inherit their environment from the original >screen process. So, how do you start the initial (daemon) screen >process? From outside X, before running xinitrc? From your .xinitrc >or .xsession? From an xterm? Or it could be a login-shell vs. non-login shell difference. >> I don't know much about this terminal stuff, but if >> everything beside XTerm works fine, could it be that >> XTerm itself and not the locales are the problems' >> source? Maybe XTerm doesn't manage to pass on the >> locales correctly? >Something is setting LC_CTYPE to an unsupported value. That's the >program that needs to be fixed. Or OpenBSD could get more locale support *ducks*. (No, I'm not complaining so much, and I'm currently not up to having enough time and energy for coding it). >[...] Kind regards, Hannah.
