### Installing a Type 1 font

The process of installing a Type 1 font set is rather convoluted, but it may be separated into a modest set of stages.

- Acquire the font. A very small set of Type 1 fonts is installed in most PostScript printers you will encounter. For those few (whose use is covered by the basic PSNFSS package), you don’t need the Type 1 font itself, to be able to print using the font.

  For all the myriad other Type 1 fonts, to be able to print using the font you need the Type 1 file itself. Some of these are available for free (they’ve either been donated to the public domain, or were developed as part of a free software project), but the vast majority are commercial products, requiring you to spend real money.

- Acquire the fonts’ AFM files. AFM files contain information from the font foundry, about the sizes of the characters in the font, and how they fit together. One measure of the quality of a font-supplier is that they provide the AFM files by default: if the files are not available, you are unlikely to be able to use the font with (La)TeX.
- Rename the AFM files and the Type 1 files to match the Berry font naming scheme.
- Generate TeX metric files from the AFM files. The commonest tool for this task is fontinst; the package documentation helps, but other guides are available (see below). The simplest possible script to pass to fontinst is:

  >     \latinfamily{xyz}{}
  >     \bye

  where `xyz` is the Berry name of the font family. This simple script is adequate for most purposes: its output covers the font family in both T1 and OT1 font encodings. Nevertheless, with fancier fonts, more elaborate things are possible with fontinst: see the documentation for details.

  Fontinst also generates map files, and LaTeX font definition (`.fd`) files.

- Install the files, in your `texmf` tree. All the strictures about installing non-standard things apply here: be sure to put the files in the local tree. The list gives reasonable destinations for the various files related to a font whose Berry name is <bname>:

      .pfb,
      .pfa  .../fonts/type1/<foundry>/<bname>
      .tfm  .../fonts/tfm/<foundry>/<bname>
      .vf   .../fonts/vf/<foundry>/<bname>
      .fd   .../tex/latex/fontinst/<foundry>/<bname>

  The irregular things being `.map` files: in teTeX 3.0 and later, these should be placed according to the revised TDS as

      .map  .../fonts/map/dvips/<foundry>

  and in other (earlier) systems as

      .map  .../dvips/fontinst/<foundry>

- Regenerate the file indexes (as described in package installation).
- Update the dvips and other maps:
  - On a teTeX system earlier than version 2.0, edit the file $TEXMF/dvips/config/updmap and insert an absolute path for the lm.map just after the line that starts `extra_modules="` (and before the closing quotes).
  - On a teTeX version 2.0 (or later), execute the command

          updmap --enable Map <xyz>.map

  - On a MiKTeX system earlier than version 2.2, the “Refresh filename database” operation, which you performed after installing files, also updates the system’s “PostScript resources database”.
  - On a MiKTeX system, version 2.2 or later, update updmap.cfg which is described in MiKTeX online documentation. Then execute the command `initexmf --mkmaps`, and the job is done.

The whole process is very well (and thoroughly) described in Philipp Lehman’s guide to font installation, which may be found on CTAN.

`fontinst.sty`
  fonts/utilities/fontinst (gzipped tar, browse)
`Type 1 installation guide`
  info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf

This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font