On Thu, Jul 08, 2004 at 01:38:58PM -0500, Branden Robinson wrote: > retitle 254650 xterm: document utf8Fonts resource in NEWS.Debian or FAQ > tag 254650 + moreinfo > thanks > > Hi Thomas, > > Can you supply me with some text to provide here? I'm not completely sure > I understand the problem, and until I do I don't know whether this is more > of a FAQ issue and/or a NEWS.Debian issue. > > I'm thinking of something structured like: > > If you <...>, then you need to <... utf8Fonts ...> instead of <...> or > undesirable behavior <...> will result. > > It *sounds* like the kind of hyperaggressive wildcard problem that results > in the following: yes - it's another example of that. The wide-character widget hierarchy for xterm has something like xterm.vt100.utf8Fonts.font versus the users' expected xterm.vt100.font The former (utf8Fonts) overwrites the latter when UTF-8 mode is selected (after the resources are evaluated, of course). The utf8fonts should be ISO-10646 fonts, not ISO-8859-1. The wildcard xterm*font sets both resources to the same value. Wildcards have their place, but generally not before the last level, e.g., xterm*vt100.font makes it work with/without the toolbar option. That's specific enough that it doesn't introduce a problem. (The other way to do this overwriting, by using entirely different names for the resources was too ugly to contemplate ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgpzC7KQ2M0Gn.pgp
Description: PGP signature