Type Network


Fonts primer / Overview


An old and stable font format

Before the introduction of variations in OpenType 1.8, the OpenType standard font format had evolved from Mac-specific TrueType to include Microsoft-specific TrueType, which merged with Adobe PostScript to form OpenType 1.0. OpenType can contain either TrueType or compressed PostScript (CFF), and it has since evolved into several web font formats, and ultimately into the WOFF standard.

This evolution has been possible because OpenType is based on the extendable Spline Font format (SFNT), originally developed by Apple and renamed TrueType in the late 1980s. This format allows tables to be added that don’t disturb preexisting applications and users, as well as allowing new things for new tables, and letting each operating system and application define which tables are required and which are optional.

So, from the original Mac TrueType to OpenType 1.8, the format has evolved with backward compatibility, adding tables to get to a different backward compatibility for Microsoft Windows, and another one for Adobe, resulting ultimately in a large set of tables involved for compatibility with all three of OpenType/TrueType’s owners. This section does not try to document the entire OpenType format before 1.8; that can be found elsewhere: see Apple, Adobe, and Microsoft.

Each example of each topic in this first section documents the way particular features in OpenType fonts work, and how each example would have been unachievable or impractical before variable fonts—in many cases, in variable fonts without parametric axes. This, we hope, will serve not only to highlight forward capabilities that are possible with our suggestions, but also to assure typographers on the web that there is a way for typographic  code on the web to fall back, since many conditions of the web—slow connections, older systems, and so on—will force the presentation to do so.