Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
10 Error Handling<br />
10.1 GLYPH NAMES<br />
The most common source of problems are bad glyph names.<br />
Make sure all your glyph names:<br />
<br />
hyphen (-) or period (.),<br />
<br />
<br />
even at the end,<br />
<br />
Not adhering to these guidelines may yield an error message<br />
at export time like ‘There is a problem with a glyph named:’,<br />
followed by the bad glyph name and a descriptive explanation<br />
of the problem within brackets, e.g., ‘The glyph name should<br />
not contain any space character.’ Such error messages can also<br />
occur when trying to compile the OpenType feature code in<br />
the Features tab of File > Font Info.<br />
You can find bad names by searching for space (or other<br />
invalid characters) in the search field of the Font view (Cmd-F).<br />
10.2 FONT NAMES<br />
If your error message only entails a POSIX path to a file called<br />
‘FontMenuNameDB’, set between brackets (e.g., ‘[/Users//Library/Application Support/<strong>Glyphs</strong>/Temp//FontMenuNameDB]’), then there probably is an<br />
invalid character in the font name or style name. You can use<br />
spaces, but as of yet, no non-ASCII characters.<br />
<strong>Glyphs</strong> <strong>Handbook</strong>, May <strong>2013</strong> 77
Change language