It is the purpose of the configuration file to setup search paths and font databases. The format of this file is quite simple and straightforward:
ENCODING=
is read in. The
remainder of the line is expected to be a list of searchpath
specifications for encoding files. No white space may appear
between =
and the path specification(s).
Multiple paths may be specified by separating
the single paths with colons.3 The path specification(s) may be
followed by any white space characters.
AFM=
is read in. The
remainder of the line is expected to be a list of searchpath
specifications for Adobe Font Metric files. No white space may
appear between =
and the path specification(s).
Multiple paths may be specified by separating
the single paths with colons. The path specification(s) may be
followed by any white space characters.
TYPE1=
is read in. The
remainder of the line is expected to be a list of searchpath
specifications for Type 1 font files. No white space may
space between =
and the path specification(s).
Multiple paths may be specified by separating
the single paths with colons. The path specification(s) may be
followed by any white space characters.
FONTDATABASE=
must specify a
colon-separated list of font database filenames on the remainder of the
line. No white space is allowed between =
and the path specification,
but trailing white space is allowed.
A configuration file may contain multiple path declarations of one type. In this case, a list of path elements is built internally in the same order that the specifications appear in the configuration file. For example, the statement
TYPE1=/usr/X11/fonts/Type1:/home/user/fonts/Type1is equivalent to the two statements
TYPE1=/usr/X11/fonts/Type1 TYPE1=/home/user/fonts/Type1
In order to specify paths that incorporate unusual characters like white
space or the path separator, it is possible to quote the path string element
using double quotes ``"
''. All characters after the leading quotation
mark are verbatim read to the path until the closing quotation mark
appears. The double quotes may also become part of a path
specification by using the escape sequence ``\"
''. Hence, the following
statement specifies a correct albeit somewhat unusual search path:
TYPE1=/usr/X11/fonts/Type1:"/home/user/My \"Best\" Fonts/Type1"
Here is an example of how a user could do the runtime setup:
Example:
Create a file, say, named t1.config
with the following
contents in your HOME-directory:
# This is a configuration file for t1lib These two lines are considered to be comments FONTDATABASE=/home/user/test/myprog/FontDataBase ENCODING=/usr/local/lib/fonts/type1/enc:. AFM=/usr/local/lib/fonts/type1/afm:. TYPE1=/usr/local/lib/fonts/type1/outlines:.After this, make the environment variable
T1LIB_CONFIG
point
to this file, i.e.,
setenv T1LIB_CONFIG ~/t1.config
tcsh
, or
export T1LIB_CONFIG=~/t1.config
bash
. Provided that the path specifications in the
configuration file are correct, the setup is done. When setting
T1LIB_CONFIG
in an interactive shell as described above, the shell does
the tilde expansion. Notice that t1lib never does tilde expansion.