T1ERR_SCAN_FONT_FORMAT
(-5): A Multiple Master Font was attempted
to be loaded. These are not supported by t1lib.
T1ERR_SCAN_FILE_OPEN_ERR
(-4): This value indicates that the Type
1 font file could not be opened by the parser. It usually does not mean that
the file does not exist because this problem would have shown up at the time
the font database had been built. It is more likely a permission problem.
Anyhow, the C library variable errno
should be examined for getting
an idea of what the problem was.
T1ERR_SCAN_OUT_OF_MEMORY
(-3): A Type 1 font program required
more than 262144 bytes of VM. This is a limit imposed by t1lib because
it usually means there goes something wrong. Typical values of VM
consumption are between 30000 and 60000 bytes depending on the fonts'
complexity. If this limit really does not suffice the constant
MAXTRIAL
(defined in lib/type1/fontfcn.c
) may be set to some
larger value.
T1ERR_SCAN_ERROR
(-2): An error occurred during scanning the font
file. It usually means that the font file is damaged or does not comply to
the conventions of Type 1 font files. For example, an encountered token might
have been too long. Another reason could be, a literal name follows a literal
name where a number was expected. There is no way to recover from this
error. One last resort could be to disassemble the font (e.g., using
t1disasm
from the t1utils
package) and scan the resulting
human-readable file for possible violations of the Type 1 font format
specifications. However, some knowledge about the format is in force.
T1ERR_SCAN_FILE_EOF
(-1): A premature end of file was encountered
during parsing. The file is damaged.