[Bug: 21.5-b28] w3 fails on font-spatial-to-canonical

[Stephen J. Turnbull]

Aidan Kehoe writes:

 > Stephen, does it really bring value to also accept XLFDs on the XFT build?

Yes.  Existing X resource specifications should continue to work under
Xft.  Even if the font family is not available, we should use them for
hints at size.

The real problem though is that Xft just should not have been put into
the mainline because the people who wrote the original patches did a
poor job.  Nor is it entirely their fault.  Working with this stuff is
non-trivial because displays, consoles, and devices are not distinct
in the implementation.  When I have time I've been trying to unwind
the mess.

 > I get the feeling that using different X resources and separate
 > face and font handling function for the two builds would be cleaner
 > and more usable.

Proliferating resources with similar meaning is a bad idea, other
things being equal.

Nonetheless, where I wrote the code I did (xlwtabs).  I'm not happy
with the UI, the API, or the implementation, though (Ed Falk's work
isn't the greatest I've run into either, so working with the tabs and
the progress bar is pretty painful).

Among other things we should have a proper Xt converter for resources
that are definitely Xft fonts.