2 
( 
- 2 (
"
O As with macros, fonts need to be stored in a hierarchical structure in order to make maintenance feasible. ; The TDS specifies the following (except for PK and F GF files, which need additional structure, as detailed in the next sextion):
\ texmf/fonts/type/supplier/typeface/
is the type of font file:
4 font sources (METAFONT files, property lists, etc.).
TFM files.
virtual fonts.
Adobe font metrics.
PK files.
GF files.
= Type 1 fonts in PFA or PFB format or both.
: is the name of the font supplier or public. adobe, + monotype, and ams are " examples of supplier.
4 The public directory serves a practical4 purpose: it designates fonts which can be freely redistributed.
The name ams = is precisely defined: the ams typeface directory 9 contains only the fonts distributed by the AMS # in the ``amsfonts'' collection.
6 is the name of the typeface family. cm, 7 latex, euler, concrete, / bookman, and courier are examples of typeface.
0 The names cm and latex areF precisely defined, as follows. The cm typeface directory6 contains only the 75 fonts defined in Computers6 and Typesetting, Volume E. The latex? typeface directory contains only the fonts distributed with # LaTeX in the base distribution.
For example:
# texmf/fonts/tfm/public/cm/cmr10.tfm ' texmf/fonts/type1/adobe/utopia/putr.pfa
? For more information about font filenames, consult Filenames r for TeX fonts (see Section C, Related References for a complete reference). /
) The bitmaps for each font require special 9 attention. In addition to the name of the font, two more D characteristics are required to uniquely identify a bitmap font: theB type of device (i.e., mode) for which the font was created and the resolution of the bitmap.
# Following common practice, the TDS 4 segregates fonts with different device types (modes)E into separate directories. Consult modes.mf for recommended l mode names. (See Section C, Related References for a complete reference.)
B Two naming strategies are commonly used to identify the resolution@ of bitmap font files. On systems that allow long filenames, theI convention is to include the resolution in the filename (in fact, this is + how METAFONT itself names its output). For 5 example, the 300dpi bitmap of cmr10 is named 8 cmr10.300pk. On other systems, such as MS-DOS,6 the fonts are generally segregated into directories by? resolution. For example, the same 300dpi bitmap would be named 7 cmr10.pk in a directory named dpi300.
- Because the TDS cannot assume long filenames M (see Section 2.2, Constraints) / it must use the latter scheme for naming fonts. = Therefore, under the pk directory, the TDS specifies two more subdirectory levels:
s texmf/fonts/pk/mode/supplier/typeface/dpi/
< is the mode name which identifies the device type. This? is usually the name of the METAFONT mode used to build the PK file. & ljfour, cx, and 2 linotype are examples of mode.
< For fonts rendered as bitmaps by a program that does not5 distinguish between different output devices, the 8 mode name shall be that of the program (e.g.,& ps2pk, gsftopk).
C specifies the resolution of the font. The directory name shall ? consist of the string dpi followed by the numeric : value of the resolution in decimal. dpi300, . dpi329, and dpi1404 are examples of dpi.
5 GF files are stored in a parallel structure:
s texmf/fonts/gf/mode/supplier/typeface/dpi/ 9
; The TWG recognizes that the use of short filenames has many O disadvantages. The most vexing is that it results in the creation of dozens of ? different files with exactly the same name. At a typical site, H cmr10.pk will be the filename for Computer Modern Roman 10pt at$ 5--10 magnifications for 2--3 modes.
M There was considerable discussion about how to minimize the disadvantages of 3 this scheme. One result of that discussion was the @ decision to allow extensions to the basic naming scheme (such as> cmr10.300pk or font library files), provided that theE basic scheme is also supported. The following statement is the other result:
8 In a TDS-conformant installation, all PK files must contain D enough information to identify precisely how they were created; thisD includes mode, base resolution, and magnification used to create the font.
B This information is easy to supply: a simple addition to the localJ modes used for building the fonts with METAFONT will automatically provideD the required information. If you have been using a local modes fileA derived from (or that is, in fact) the complete modes.mf C distribution from CTAN, the required information is already in your ? PK files. If not, a simple addition based on the code o found in modes.mf (see Section C, Related References for a complete / reference) can be made to your local modes file " and the PK files rebuilt.