> give me (on my system) an xterm which understands UTF-8 by default > (without setting it manually). So I am still baffled. E.g., both > display UTF-8 e with sharp accent as A with tilde followed by an > 'at' sign. My locale is en_GB.UTF-8. So far my only solution is to > downgrade to version 200. xterm can be compiled with traces, which usually would show enough information in this situation to see what it is really doing. I'd set it up by (tarballs on my ftp area): ./configure --enable-widechars --enable-trace make ./xterm -xrm '*locale:false' -u8 The "Trace-parent.out" file contains the details for the vt100 initialization (as well as other stuff, of course). For instance if there were some conflicting resource definition, the trace file shows the actual resource value that xterm uses. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgpHazilx9JW6.pgp
Description: PGP signature