Microsoft Typography | Developer... | OpenType specification | OpenType tables | The gasp table | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This table contains information which describes the preferred rasterization techniques for the typeface when it is rendered on grayscale-capable devices. This table also has some use for monochrome devices, which may use the table to turn off hinting at very large or small sizes, to improve performance. At very small sizes, the best appearance on grayscale devices can usually be achieved by rendering the glyphs in grayscale without using hints. At intermediate sizes, hinting and monochrome rendering will usually produce the best appearance. At large sizes, the combination of hinting and grayscale rendering will typically produce the best appearance. If the 'gasp' table is not present in a typeface, the rasterizer may apply default rules to decide how to render the glyphs on grayscale devices. The 'gasp' table consists of a header followed by groupings of 'gasp' records:
Each GASPRANGE record looks like this:
There are two flags for the rangeGaspBehavior flags:
The set of bit flags may be extended in the future.The four currently defined values of rangeGaspBehavior would have the following uses:
The records in the gaspRange[] array must be sorted in order of increasing rangeMaxPPEM value. The last record should use 0xFFFF as a sentinel value for rangeMaxPPEM and should describe the behavior desired at all sizes larger than the previous record's upper limit. If the only entry in 'gasp' is the 0xFFFF sentinel value, the behavior described will be used for all sizes.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Microsoft Typography | Developer... | OpenType specification | OpenType tables | The gasp table | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||