|TrueType and Type 1 fonts|
Is TrueType's superior behaviour on-screen going to mean Type 1 withers and dies? Or will Type 1's greater acceptance in the printing industry and Adobe's continually updated rasterizer mean that TrueType is remembered as a valiant, but too-late, contender for fontological supremacy?
In fact, both are now very firmly established and, with their 1996 announcement of OpenType, Microsoft and Adobe have jointly declared they intend neither to happen.
Let's compare them on the two basic criteria for scalable font technologies: outlines and hinting.
Graphic designers who use computers are much more familiar with the cubic Bézier curves throughout PostScript (and hence Type 1 fonts) than TrueType's quadratics. Designers routinely use cubic curves to represent all the curves they care to. (Adobe Illustrator, Macromedia Freehand and CorelDraw, to take probably the three commonest applications, use cubic curves exclusively.)
At first sight, Type 1's hints are pretty easy to understand. The specification advises the font designer to declare hints for all vertical and horizontal "stem-like features" (either a vstem or an hstem). These identify zones to Type 1 rasterizing programs, such as ATM and PostScript printers, so that (unspecified) special techniques may be applied to these parts during the outline-filling process.
Although a font with well-defined hints will certainly rasterize much better than one without, it is not possible to specify precisely which pixels will be turned on, even for a particular size and device. This is for two reasons: first, although Type 1 is an open format, Adobe does not publish the specification of the Type 1 rasterizer, so clones and updated versions of PostScript may not produce identical bitmaps; second, from time to time Adobe updates the behaviour of its rasterizer.
Because the same hint always performs the same function, hints are easy to extract from the font file to edit visually along with the outline.
Since the behaviour of the TrueType rasterizer is implicit in the TrueType specification, the font designer and hint programmer can be confident that the bitmaps they see during development will be replicated precisely on any TrueType rasterizers. This is most important for fonts intended for frequent use on low-resolution devices. (Unfortunately the Windows 95 and Apple renderers very occasionally do not quite match on every pixel. This is because Microsoft rewrote the rasterizer with a "full accuracy" curve-filling algorithm, which would ideally have been optionally activated by the font developer with a new instruction or table specification.)
As with any computer program, it is almost impossible to extract useful hinting information from TrueType fonts, beyond that encoded by the individual compiled instructions. So, to edit the hints of a TrueType font, you must learn this low-level programming language. In practice, most font editing programs completely ignore the hints in imported TrueType fonts, applying their own PostScript-style "autohints" instead.
TYPE*chimérique | TrueType Typography | TYPE*links