| Thomas Dickey 2005-10-28, 8:48 pm |
| marco.chiarandini@gmail.com wrote:
> The UTF-8 is selected but the entry is shaded like the feature is not
> available.
man xterm
-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.
"prevents" means that the menu is disabled, and it ignores the escape
sequence that would do this.
However, if the locale doesn't match, xterm won't be getting incoming
data encoded as UTF-8. That's one problem (sounds more likely).
Another problem is that just setting the utf8 resource doesn't guarantee
that fonts are setup. That's what the uxterm script does.
It's also possible that xterm's locale resource is set (again - see the
manpage):
locale (class Locale)
Specifies how to use luit, an encoding converter between UTF-8
and locale encodings. The resource value (ignoring case) may
be:
true
xterm will use the encoding specified by the users'
LC_CTYPE locale (i.e., LC_ALL, LC_CTYPE, or LANG variables)
as far as possible. This is realized by always enabling
UTF-8 mode and invoking luit in non-UTF-8 locales.
and that could be a different reason why the UTF-8 mode is turned on.
> I found another strange behaviour: if I launch xterm from an xterm the
> charachters are fine.
> Using fvwm and launching xterm from the menu instead I have the
> unwanted behaviour describd. I still cannot understand which are the
> config files read in this case. It seems that none of the
> ~/.Xdefaults, ~/.Xresources or ~/.tcshrc affects xterm when launched by
> an xterm shell. I am lost!
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
|