PostScript fonts

The lines between the first and last ``=='' tell which TFM files are for PostScript fonts (or more accurately, non-PK fonts). The ordering of lines doesn't matter; they are used by to build a list of PostScript fonts. In a non-default config file the first ``=='' can be replaced by ``=+''; this tells to update the current list rather than delete it and build a new one. Each line specifies a TFM name, a printer font name, an optional download file, a screen font name, an encoding entry and an optional style. Note that most of the lines in the Default file contain ``raw'' TFMs for corresponding virtual fonts; see section [*]. If a DVI file uses PostScript fonts, the TFM names get converted into printer font names when printing the file on a PostScript printer. allows non-resident PostScript fonts to be downloaded on demand. The Utopia lines at the end of the Default file have an extra string (starting with ``<'') after the printer font name. This specifies the file to be downloaded if the corresponding font is used; see section [*] for more information. The screen font names are used when viewing a DVI file with PostScript fonts, and when printing the file on a non-PostScript printer. If you are unsure about which screen font would best match a particular PostScript font, you must still specify something (such as ``?''). If can't find a specified screen font it will warn you and use the system font instead. To obtain the best results when viewing or printing a DVI file with PostScript fonts you must get the matching screen fonts. Each screen font can appear in a certain style defined by a set of flags: ``b'' for bold, ``i'' for italic, ``u'' for underline, ``o'' for outline, ``s'' for shadow, ``c'' for condense and ``e'' for extend. If the style is not specified then uses the font's plain style. An encoding entry is the name of a user-defined encoding file (or ``nil'' if the TFM file and screen font use the same encoding). Section [*] discusses encoding files.