Once you have a prepared Type 1 font, either direct from CTAN or the like, or having “prepared” it yourself, you can get on with installation.
The procedure is merely an extension of that for packages, etc., so much of what follows will be familiar:
texmftree (the advice about installing non-standard things applies here, too). The following list gives reasonable destinations for the various files related to a font family ‹fname›:
.pfb, .pfa .../fonts/type1/<foundry>/<fname> .tfm .../fonts/tfm/<foundry>/<fname> .vf .../fonts/vf/<foundry>/<fname> .sty, .fd .../tex/latex/<fname> .map .../fonts/map/dvips/<foundry>
but if you are lucky, you will be starting from a distribution from
CTAN and there is a corresponding
using this TDS-file saves the bother of deciding where to put
your files in the TDS tree.
dvips, pdfTeX and other maps:
updmap-sys --enable Map <fname>.mapas root. (If you can use
updmap-sys— do; if not — presumably because your (La)TeX system was set up by someone else — you have to fall back on plain
updmap, but be aware that it’s a potent source of confusion, setting up map sets that might be changed behind your back.)
updmap.cfg, using the shell command
initexmf --edit-config-file updmapadding a line at the end:
Map <fname>.mapfor each font family ‹fname› you are adding to the system. Now generate revised maps with the shell command
initexmf --mkmapsThis, and other matters, are described in MiKTeX “advanced” documentation.
Both processes (preparing and installing a font) are very well (and thoroughly) described in Philipp Lehman’s guide to font installation, which may be found on CTAN.
FAQ ID: Q-instt1font