Re: display of utf-8 messages in exmh-2.8.0

 Belatedly:
| > New versions of Tk are almost certainly using new XFT font handling
| >instead of old-style XLFD fonts. Exmh itself doesn't or didn't have
| >very good (or really any) handling of XFT fonts and Tk's handling of
| >XFT font names is in general rather limited (you can't specify many
| >XFT attributes).
| 
| I admit that X font handling I've always viewed as a nightmare,
| and the newer XFT stuff didn't really help matters.  But the Tk
| documentation said you could still use the older XLFD names for fonts.
| You _can_, but for reasons I can't really fathom if you specified a
| semicondensed XLFD name you don't get it; you get some other font.

 If Tk is really using XFT fonts, I would not trust whatever it does
to map from XLFD names to XFT names. Tk has some serious oddities with
XFT fonts (for example, regardless of what you ask for you always get
*some* XFT font, even if what you asked for doesn't exist).

| FWIW, I didn't find this patch necessary to get UTF-8 stuff; you just
| need to make sure you end up getting an "iso10646" font.

 My experience was that it was much easier to find an XFT font that
actually has a reasonably complete set of Unicode glyphs than it was
to find an XLFD font. Or at least it was much easier to get things to
render right via XFT, since some fonts are available through both paths.

	- cks