Since the exact handling of search path specifications at the several stages may appear somewhat confusing we shall summarize the exact rules now:
T1_Set...()
functions described above establishes a completely new respective path. Each
call of one of the T1_Add...()
functions extends the respective path
in the desired manner, or creates a new respective path if previously no
path existed.
T1_Set...()
or T1_Add...()
functions receives a
default value. This is ``.
'' for the file search paths and
./FontDataBase
for the font database.
T1_Set...()
and T1_Add...()
functions still
work as described under (1). Notice that this phase usually is not
accessible when using the standard initialization scheme. It only becomes
accessible if no fonts have been added during initialization.
T1_Set...()
may not
be called any longer. The T1_Add...()
functions extend the
current set of search paths. In particular, possibly existing default search
path elements, then, are not overwritten any longer because they might have
been used before to verify the existance of required files.
T1_AddFontDataBase()
will not only append the specified
file name to the existing list of databases, but will also immediately
locate the fonts specified therein and assign additional font IDs.