### Installing the Bluesky versions of the CM fonts

This is a specialised case of installing a font, but it comes easier than most, since the font metrics are installed in every (La)TeX system before you even start. Indeed, most recent systems will have the Type 1 fonts themselves already installed, so that the job is already done, and all you need is to start using them: so the first thing to do is to just try it. On a system that uses dvips (most systems nowadays do), try the sequence:

      latex sample2e
      dvips -Pcmz -Pamz -o sample2e.ps sample2e

at a “command prompt” (shell, in a Unix-style system, “DOS box” in a Windows system).

If the command works at all, the console output of the command will include a sequence of Type 1 font file names, listed as `<cmr10.pfb>` and so on; this is dvips telling you it’s including the Type 1 font, and you need do no more.

If the test has failed, you need to install your own set of the fonts.

The CTAN directories listed below contain compressed archives of the Type 1 files for various architectures, both for the Computer Modern fonts and for the AMS fonts of mathematical and other useful things. Download the archives that are appropriate for your architecture, and extract the files — you only actually need the contents of the pfb directories, since you already have the fonts installed in the “ordinary” way, so that the TFM files are already present. (You don’t need the PostScript font metric — AFM and PFM — files in any case.)

The files should go into your local `texmf` tree (texmf.local, texmf-local, localtexmf, or whatever). Create directories at offsets fonts/type1/bluesky/cm and fonts/type1/bluesky/ams, and copy the `pfb` files into them.

Now you need to tell dvips, PDFTeX, etc., that the fonts are available. This is done by use of a map file, which lists font name (as TeX understands it), font name (as it appears in the type 1 file itself), and where the program will find the file. Map files are provided in the download bundles for the AMS fonts; for the CM fonts, map files are available separately.

The set of map files includes files `config.*`; each of these contains an instruction to load a single map file. For ordinary use, you instruct dvips to load the “detailed” map of the CM fonts by use of the command:

      dvips -Pcmz myfile

The same can be done with the AMS fonts, and you may invoke both sets of fonts with:

      dvips -Pcmz -Pamz myfile

Alternatively, the contents of config.cmz and config.amz could be combined into a single file, perhaps config.bluesky, loaded by the command

      dvips -Pbluesky myfile

Remember, after all such changes, the file-name database must be refreshed.

`AMS fonts`
  Browse fonts/amsfonts/ps-type1/
`CM fonts`
  Browse fonts/cm/ps-type1/bluesky/
`CM font maps`
  fonts/cm/ps-type1/bluesky-contrib/dvips (gzipped tar, browse)

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