T1ERR_INVALID_FONTID
(10): An invalid font ID has been
specified. The exact meaning of this error depends on the specific
situation, in any case the operation requested cannot be realized with the
identified font. Possible reasons are:
no_fonts
.
T1ERR_INVALID_PARAMETER
(11): One or more of the parameters
specified to a function call were assigned invalid values. For example, a
size-value specified to a rastering function must always be T1_ConcatGlyphs()
cannot concatenate two glyphs if one of
them is the NULL
pointer.
T1ERR_OP_NOT_PERMITTED
(12): An operation that was not allowed
at that time has been requested. This error could result, for example,
if an application tries to set a new bitmap padding value after t1lib has been initialized.
T1ERR_ALLOC_MEM
(13): This error indicates that t1lib ran out
of memory and a memory allocation failed. This error should not appear.
T1ERR_FILE_OPEN_ERR
(14): A file that was needed could not be
opened by t1lib. The file might have been necessary for reading data or
writing data. For example, T1_WriteAFMFallbackFile()
returns this
value if the AFM file could not be opened for writing and
T1_LoadEncoding()
returns it if the encoding file specified as
argument could not be opened. Notice that there is no indication of the
reason why the file opening failed. The C library
variable errno
should be examined to analyze this further.
It should be mentioned that T1ERR_FILE_OPEN_ERR
is only set if a file
operation failed which was really in force. This means that at the time a
font is loaded a missing AFM file does not cause T1_errno
caused to
be set to T1ERR_FILE_OPEN_ERR
. This is because t1lib can
automatically recover from this by generating AFM information on the fly (at
the cost of computation time).
T1ERR_UNSPECIFIED
(15): This value indicates nothing apart from
that an error occurred and this error was not one the other errors. It can
be considered a fallback.
T1ERR_NO_AFM_DATA
(16): A function has been called which needs
AFM information and AFM information is not available, either because all
attempts to generate AFM data failed or because the flag T1_NO_AFM
has been specified as part of the flag for T1_InitLib()
.
T1ERR_X11
(17): An error in an X11 library function occured. This
could be caused by calling a function of the X11 interface without prior
initialization of the X11 interface via T1_SetX11Params()
.
T1ERR_COMPOSITE_CHAR
(18): A request to compose a composite
character could not be fulfilled without problems because at least one part
of the composite character was not found in the CharStrings
dictionary. This is bad because it indicates that font file and AFM file do
match. Further errors or unsatisfactory rastering results have to be
expected.
T1ERR_SCAN_ENCODING
(19): Scanning an encoding file failed. Since
t1lib uses a fallback approach--DVIPS-encoding is tried first and
afterwards t1lib-encoding--it is not clear at which place exactly a
failure occured. However, further hints about what t1lib thought about
the file in question may be found in the log file.
strerror()
, t1lib provides the function
const char *T1_StrError( int t1err)
t1err
. Usually, the argument should be directly specified as
T1_errno
. The memory where the returned string is stored is static in
t1lib so that it may not be free()
'd.