On Thu, Feb 20, 2003 at 06:32:56PM +0100, Gerd Knorr wrote: > Thomas Zander <[EMAIL PROTECTED]> writes: > > Conclusion; > > An xterm should be able to display chinese if man or ls outputs that, > > That works just fine if xterm and applications use the same charset. > And exactly thats why xterm should come up in utf-8 mode in UTF-8 > locales.
Ok, thanx for all that info :) (and I agree with your conclusion) I see that we were not completely talking about the same thing. I was talking about utf8 being used in manpages (the files) etc, and in filenames. You were not. The fact that locales can be changed is not relevant when the only thing being effected is the output stream of an app being displayed. > * If your xterm runs in non-utf8 mode and your shell runs in > de_DE.UTF-8 the display will be f*cked up as soon as someone uses > non-ascii characters. That is what happens if you ssh from your > Debian box into a fresh RedHat 8.0 system because the terminal > encoding isn't passed through to the other side. It's easy to fix > through, just set LC_CTYPE environment variable to something what > matches the encoding your terminal uses, de_DE for example. See? Whatever the solution its a bug in ssh, not X. I have the opinion that forwarding does not solve all problems (since one of the machines may not know about utf8) so ssh could better convert the data stream using the different locales at both sides. Sorry for the off-topic... At an attempt to get back on topic; I am wondering how xterm should handle different shells (using screen for example). The perfect-world-solution would be to ask the bash its env-var at every printf, but that may prove to not really be feasable.. In other words; to start xterm in utf-8 when the locale is utf8 seems to only be half the solution, since the shell started might just start a startup script that sets LANG to something different.. -- Thomas Zander _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
