Version 19 of Xft support

Updated 2004-08-26 12:43:58 by lwv

The Xft library provides support for antialiased TrueType fonts, full Unicode, and an unbraindamaged font selection mechanism for X11.

It relies on fontconfig [L1 ], FreeType [L2 ], and the X Render extension (although it will still work if XRender is not available on the server). Xft 2.0 is included in most recent Linux distributions (circa May 2003). Mozilla, Qt, and GTk have all been updated to use Xft.

Experimental support for Xft in Tk 8.5 has been committed to the CVS HEAD (31 May 2003). See also patch #535541 [L3 ]. There are still (31 May 2003) a few quirks and bugs to be worked out, but overall it works pretty well.

To enable Xft support, run:

    sh ./configure --enable-xft
    make clean
    make

Many thanks to Keith Packard for contributing the original code. Blame Joe English for the stuff that doesn't work right yet.


KPV I for one don't particularly like antialiased fonts--I find them fuzzy and hard to read. Joel on Software essay Three Wrong Ideas From Computer Science [L4 ] talks about the fallacy of antialiased fonts.

JE Note that Joel constructed the "evidence" that antialiased fonts look bad by taking a screenshot of text in a bitmapped font and running it through Corel PHOTO-PAINT. This is like using Turner's colorized version of The Maltese Falcon to demonstrate that black and white movies are superior. If the antialiasing is done by the font rasterizer (where it's supposed to be done), the results are much better.

IDG I don't like them either. But then, I don't like syntax-colouring editors, so I'm clearly a weirdo!

DKF: I think he's not quite on the ball over AA fonts. More exactly, non-AA fonts are great if you require a font of exactly the size they provide (often the case for GUIs where font sizes can be controlled fairly well) but are awful if you're after some other size of font and the system has to fall back on its own rasterizer. (Previewing printable documents is one of the cases when you'll probably hit this problem.)

JH Some systems provide controllable lower boundaries for the use of AA fonts, which is the best solution. Small text is crisp while larger text gets AAed. OS X provides this for sure, but perhaps there is a way to allow better control for this on the unix side in Tk?

AKA: You guys are so totally wrong it hurts. Any screen design that uses pixels as a design element is flawed. Pixels are artefacts. Sane screen should try to hide the fact that (todays) screens are pixelized. For paper output, this happened when 300 dpi printers got affordable, ca. 1988. With LCD screens, we're at 150 dpi now and should really forget about pixels RSN.

DKF: FWIW, I'm happy to let the system pick whether to AA a font or not. With higher res screens of at least 24-bits deep, it's no longer a major issue.


Category Discussion