> You can specify "en_US.UTF-8" as your locale. Which implies > to me that xterm can recognize, from its environment, the > encoding, and act accordingly. Which only encourages the sort of bugs that many an autoconf script has had, that assumes because iconv() doesn't accept UTF-8 as a valid string that it has no UTF-8 support, when in fact, it does, and its called utf8 and utf-8. Maybe the encoding shouldn't be case sensitive, but it seems to be.
But FYI Thomas, the locale naming scheme is: language_territory.codeset@modifier So things like en_GB.ISO8859-1 or en_US.UTF-8 are quite legal. According to my docs, the codeset portion "represents the character set in use for the internal representation of text". Hope this helps. Kean _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
