Thomas Dickey wrote:
I already responded to this in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318923
Yes.. but I did not understand it and I also had the impression
that in that thread, two different bugs were being discussed.
also see the manpage:
-u8 This option sets the utf8 resource. When utf8 is set, xterm
interprets incoming data as UTF-8. This sets the wideChars
resource as a side-effect, but the UTF-8 mode set by this
option prevents it from being turned off. If you must turn it
on and off, use the wideChars resource.
I am sorry, but this is very unclear to a non-expert like me.
This option and the utf8 resource are overridden by the -lc and
-en options and locale resource.
If I call from the command line
xterm -lc
or
xterm -lc [somelocale]
it says (version 204):
xterm: bad command line option "-lc"
and a new xterm does not appear.
If I call
xterm -en
or
xterm -en [some encoding]
no xterm starts, and there is no message.
Could you give a simple recipe (other than simply downgrading to
version 200) for somebody with a UTF-8 locale who just wants to
have xterm understand UTF-8 by default?
> That is, if xterm has been > compiled to support luit,
and the locale resource is not
``false'' this option is ignored. We recommend using the -lc
option or the ``locale: true'' resource in UTF-8 locales when
your operating system supports locale, or -en UTF-8 option or
the ``locale: UTF-8'' resource when your operating system does
not support locale.
The operating system is Debian Sid, which supports locales. Or do
you mean something else?
The default value for the locale resource is ``medium''. If
> you set it to ``false'', the -u8 option will work as you want.
I tried in ~/.Xresources
xterm*VT100*locale: false
and of course also
xterm*VT100*locale: true
and whatever I do, I cannot get UTF-8 by default in versions 202
and 204. Please tell what I do wrong.
Regards, Jan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
