On Wed, Feb 19, 2003 at 11:32:26AM -0500, Jeff Garzik wrote: > > TBH there are really two problems here. > > In my opinion, Red Hat 8's UTF8 support definitely needs work... ssh > into a redhat box and run "man <blah>", and watch it display poorly > due to incorrect UTF8 assumptions. There are clearly many cases of > "I assume everybody is 100% UTF8", which is flat out wrong.
If one ssh'es into a RHL 8.0 box from a machine that is running in a terminal that is not UTF-8 capable, yes you're going to see problems. RHL 8.0 is doing what it has been asked to do (as you log in, LANG is going to be set to the system-wide default, or the user default as stored in ~/.i18n). ssh does not transmit the current locale of the machine you're coming from (nor should it - it could be different if you're coming from a Solaris box into a RHL 8.0 box). > That said... in a modern POSIX environment with standard > locale-related environment variables, I would hope that xterm takes > those environment settings into account. If you don't like doing > that unconditionally for all xterm platforms, a POSIXly-correct build > option would certainly work. It's not correct to use the environment variables directly to infer the charmap of a locale, IMHO. One should use setlocale() to properly load the locale, then nllanginfo(CODESET) to get the charmap. Unfortunately, there is no standard for the naming of charmaps across UNIX platforms, so you have to have a mapping from platform charmap name to UTF-8 flag. Cheers, Matt [EMAIL PROTECTED] -- Matt Wilson Manager, Base Operating Systems Red Hat, Inc. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
