On Sat, Dec 03, 2005 at 03:31:21PM +0100, Jan Willem Stumpel wrote: > >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? yes. > >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' -u8 > > 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. Then I'm missing something (I don't know what). When I checked this, I ran the ncurses test program, which shows me the displayed characters for various ranges of codes. Those all looked correct (though my main purpose in that test was to ensure that xterm was loading the proper fonts, if it weren't in UTF-8 mode, I would have noticed the effect you mention immediately). Usually I don't think of input (output accounts for most of the work), but checking now (select/paste between uxterm and xterm started as above), both directions are reading input as expected. It is possible that some keyboard difference is accounting for the problem, but I don't know how to advise you there. Still, you might be able to perform a similar check and see if select/paste of some text works properly. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgp6gRw0KfPKF.pgp
Description: PGP signature