Apple Advanced Typography
||This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (November 2009)|
|Operating system||OS X|
Apple Advanced Typography (AAT) is Apple Inc.'s computer software for advanced font rendering, supporting internationalization and complex features for typographers, a successor to Apple's little-used QuickDraw GX font technology of the mid-1990s. It is a set of extensions to the TrueType outline font standard, with smartfont features similar to the OpenType font format that was developed by Adobe and Microsoft, and the open source Graphite. It also incorporates concepts from Adobe's "multiple master" font format, allowing for axes of traits to be defined and morphing of a glyph independently along each of these axes. AAT font features do not alter the underlying typed text; they only affect the characters' representation during glyph conversion.
Significant features of AAT currently include:
- Several degrees of ligature control
- Keshideh justification and joiners
- Cross-stream kerning (required for Nasta'liq Urdu, for example)
- Indic vowel rearrangement
- Independently controllable substitution of:
- Glyph variation axes
AAT and OpenType in OS X
As of Mac OS X 10.5 Leopard, partial support for OpenType is available. As of 2011, support is limited to Western and Arabic scripts. If a font has AAT tables, they will be used for typography. If the font does not have AAT tables but does have OpenType tables, they will be used to the extent that the system supports them.
This means that many OpenType fonts for Western or Middle Eastern scripts can be used without modification on Mac OS X 10.5, but South Asian scripts such as Thai and Devanagari cannot. These require AAT tables for proper layout.
AAT does not support language-specific shaping—that is, changing how glyphs are processed depending on the human language they are being used to represent, a feature supported by OpenType. For a single font to cover two languages with different shaping requirements but a common script—for example, Arabic and Urdu—it would be necessary for two sets of shaping tables to be included in the font, and for the user (or some other high-level mechanism, such as markup) to inform the glyph processor which to use. There is also no provision in AAT for the relative positioning of two glyphs via anchor points, which would allow the positioning of one diacritic relative to another, for example. The correct stacking of multiple diacritics can easily be done in AAT, but requires a different technique.
|This section does not cite any references or sources. (November 2009)|
AAT first requires the text to be turned entirely into glyphs before text layout occurs. Operations on the text take place entirely within the glyph layer.
The core table used in the AAT layout process is the "morx" table. This table is divided into a series of chains, each further divided into subtables. The chains and subtables are processed in order. When each subtable is encountered, the layout engine compares flags in the subtable against control flags, generally derived from user settings. This determines whether or not the subtable is processed.
The set of available features in the font is made accessible to the user via the "feat" table. This table provides pointers to the localizable strings that can be used to describe a feature to the end user and the appropriate flags to send to the text engine if the feature is selected. Features can be made invisible to the user by the simple expedient of not including entries in the "feat" table for them. Apple uses this approach, for example, to support required ligatures.
Subtables may perform non-contextual glyph substitutions, contextual glyph substitutions, glyph rearrangements, glyph insertions, and ligature formation. Contextual actions are sensitive to the surrounding text. They can be used, for example, to automatically turn an s into a medial s anywhere in a word except at its end.
The "morx" subtables for non-contextual glyph substitutions are simple mapping tables between the glyph substituted and its substitute. The others all involve the use of finite state machines.
For the purposes of processing the finite state machine, glyphs are organized into classes. A class may be small, containing only a single glyph (for something like ligature formation), or it may include dozens glyphs or even more. A special class is automatically defined for any glyph not included in any of the explicit classes. Special classes are also available for the end of the glyph stream and glyphs deleted from the glyph stream.
Beginning with a start-of-text state, the layout engine parses the text, glyph by glyph. Depending on its current state and the class of the glyph it encounters, it will switch to a new state and possibly perform an appropriate action. The process continues until the glyph stream is exhausted.
The use of finite state machines allows "morx" tables to be relatively small and to be processed relatively quickly. They also provide considerable flexibility. Inasmuch, however, as Apple's font tools require the generation of "morx" tables via raw state table information, they can be difficult to produce and debug. The font designer is also responsible for making sure that "morx" subtables are ordered correctly for the desired effect.
Since AAT operates entirely with glyphs and never with characters, all the layout information necessary for producing the proper display resides within the font itself. This allows fonts to be added for new scripts without requiring any specific support from the OS. Third parties can produce fonts for scripts not officially supported by Apple, and they will work with Mac OS X. On the other hand, this also means that every font for a given script requires its own copy of the script's shaping information in its own "morx" tables.
Other AAT tables (or AAT-specific extensions to standard TrueType tables) allow for context-sensitive kerning, justification, and ligature splitting. AAT also supports variation fonts, in which a font's shape can vary depending on a scaled value supplied by the user. Variation fonts are similar to Adobe's defunct Multiple master fonts, where the endpoints are defined and any medial value is valid. With this, the user can then drag sliders in the user interface to make glyphs taller or shorter, to make them fatter or thinner, to increase or decrease the size of the serifs, and the like, all independently of one another. Glyphs may even have their fundamental shapes radically altered. There is nothing like this in OpenType.
Other AAT tables an also have point-size dependent effects; for example, at 12 points, the horizontal and vertical strokes can be of similar width, but at 300 points, the stroke width variation could be quite great.
In practice, few AAT fonts use any features of the technology other than those available through the "morx" table. Zapfino, Hoefler Text, and Skia are fonts that ship with Mac OS X that illustrate a variety of AAT's capabilities.
AAT for Indic scripts
For Indic scripts, the only features that are necessary are glyph reordering and substitution; AAT supports both of these. As noted above, OpenType fonts for Indic scripts require AAT tables to be added before they will function properly on OS X. However, this applies only to software dependent on the system support of OpenType. Programs that provide their own implementation of OpenType will render Indic properly with OpenType fonts. (They may, however, not render Indic fonts with AAT tables correctly.)
- Apple typography
- Graphite (SIL) technology on MS Windows and Linux
- List of typographic features
- ICU Layout Engine – Overview
- TrueType Reference Manual, Chapter 6, Introduction to AAT
- TrueType Reference Manual, Chapter 6
- See the majuscule Q in the first illustration.
- TrueType Reference Manual, Chapter 6, § titled 'Variation Axis Tags'
- About Apple Advanced Typography Fonts, Apple's developer documentation
- Font tools - a set of command-line tools to work with fonts
- Advanced Typography with Mac OS X (in PDF format) ((Broken Link))
- An example of an AAT table
- Fontforge documentation
- Discussion on AAT used in Persian fonts