>If I understand correctly, such *VT100*font resources are no longer used
>and are now replaced by *VT100.utf8fonts resources (preferably). But this
>doesn't seem to be the case. Indeed, if I do the following:
Not exactly. When xterm starts, it first uses whatever the X resources resolve
*VT100.font to, then if it is setup for UTF-8, overlays that with whatever the
*VT100.utf8fonts.font corresponds to. If "*VT100*font" is used as a pattern
in the UXTerm app-defaults file, that overrides (but has the same general effect)
as the combination of resources in the XTerm app-defaults file.
I won't argue about whether "duplicated" is the proper term.
It seems that the point of confusion is actually the use of the "locale" resource.
Since your locale is POSIX, and (not mentioned in the report) the locale resource
is probably "medium", the xterm manpage tells what happens:
medium
xterm will follow users' LC_CTYPE locale only for UTF-8,
east Asian, and Thai locales, where the encodings were not
supported by conventional 8bit mode with changing fonts.
For other locales, xterm will use conventional 8bit mode.
So it resets the utf8 resource (as you may see by looking for the checkmark
by the "UTF-8" in the control-right-mouse menu).
--
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
Attachment:
signature.asc
Description: Digital signature