Thomas Dickey wrote:
[..] So the next question is how to use this information. From the commandline, I could type xterm -xrm '*locale:false' -u8 but of course that gets tedious. I generally have my $HOME/bin before other directories in $PATH, so it would be simple to write a shell script that wraps xterm, something like this (named "xterm"): #!/bin/sh /usr/bin/X11/xterm -xrm '*locale:false' -u8 "$@" That has the drawback (addressed by uxterm) of allowing someone with a non-UTF-8 locale to invoke xterm, making it do I/O in UTF-8 encoding. So I don't think that's what you want (though it was what Thomas Wolff requested).
Do you mean the author of the mined editor?
Supposing that your locale is set to a UTF-8 one such as de_DE.UTF-8, then xterm -xrm '*locale:true' -u8 will start xterm in UTF-8 mode (and due to the lack of parameter of the -u8 option, that cannot be turned off).
Your post gave me a lot to think about, especially about what luit is and when or why it is needed, but a quick reaction is: neither xterm -xrm '*locale:false' -u8 nor xterm -xrm '*locale:true' -u8give 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.
Regards, Jan