Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Unnecessary kerning<br />
between two scripts (e.g. a<br />
Cyrillic and a Latin letter<br />
with each other) is ignored<br />
at export time, minimizing<br />
the risk for this error..<br />
out of date. In this case, recalculating the features by clicking<br />
on the circled arrow button in the bottom left corner of the<br />
Features tab in File > Font Info will do.<br />
GPOS feature ‘kern’ causes overflow of oset to a subtable.<br />
The kerning structure is too complicated and causes the<br />
glyph positioning table in the font to become to0 large. An<br />
OpenType table must not be larger than 64 kilobytes. Cleaning<br />
up and compressing kerning may help. Try the respective<br />
functions from the gear menu of the Kerning window<br />
(Window > Kerning). Also check for unnecessary kerning pairs.<br />
Very small values (below 5) are usually superfluous and can<br />
be deleted.<br />
Invalid token. Most likely one of the class names starts with<br />
a whitespace character, or there is a whitespace between the<br />
at sign (@) and the class name in the feature code, or there is<br />
a whitespace character in a glyph name, or there are invalid<br />
non-ASCII characters elsewhere in the feature code.<br />
Lookup type dierent from previous rules in this lookup block.<br />
You tried to mix contextual and non-contextual positioning<br />
rules, probably in the ‘kern’ feature.<br />
makeotf<strong>Glyphs</strong>. The most probable cause is a glyph name<br />
containing invalid characters.<br />
makeotf<strong>Glyphs</strong> [FATAL] line too long. Most likely, a glyph<br />
name was too long. Glyph names should not be more than<br />
122 characters long.<br />
not in range −32767 .. 32767 (text was “…”). At least one node or<br />
anchor in the font is out of bounds. A coordinate value must<br />
not exceed ± 32,767. Open the <strong>Glyphs</strong> file in a text editor and<br />
<br />
<br />
glyph needs to be fixed. If you do not find anything this way,<br />
try the number in the brackets of the error message.<br />
Positioning values are allowed only in the marked glyph<br />
sequence, or after the final glyph node when only one glyph node<br />
is marked. The syntax of a contextual positioning rule in the<br />
‘kern’ feature is faulty. At least one glyph name must be<br />
marked with a single dumb quote ('), and the number value<br />
should come right after the marked glyph, not at the end as in<br />
other positioning rules.<br />
Premature end of input. Most likely, one of the glyphs has<br />
a bad name. Check if there is a glyph name that contains an<br />
<br />
<strong>Glyphs</strong> <strong>Handbook</strong>, May <strong>2013</strong> 79
Change language