Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!decwrl!shelby!neon!rokicki
From: rokicki@Neon.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.text.tex
Subject: dvips/PostScript fonts
Message-ID: <1991Jan10.222637.5450@Neon.Stanford.EDU>
Date: 10 Jan 91 22:26:37 GMT
Organization: Computer Science Department, Stanford University
Lines: 25

> I can define the Adobe fonts I want to use in TeX just fine.  However, when
> I dvips the result, I run into the brick wall that I (and Nick Nystrom, also)

You want to get the latest dvips from labrea and use that.  (If you just
want the documentation, you can ftp ~labrea:pub/dvips.ps.Z and print that.)

In general, if you use a PostScript font, you must mention it in the file
psfonts.map so dvips knows it is a PostScript font and doesn't try to
generate a PK file using MF.

The font finding strategy is as follows.

Dvips sees font foo in a document.  It first searches for a vf file called
foo.vf.  If it can find that, it uses that and doesn't need a foo.pk file.
(The foo.vf file will almost certainly call other fonts; for these just
call this paragraph recursively.)  If a vf file doesn't exist, dvips checks
to see if the font is one that was mentioned in psfonts.map.  If it was,
then dvips knows it is a PostScript font, so it reads the foo.tfm file and
does the appropriate things.  If it's not mentioned in psfonts.map, dvips
tries to open a PK file, perhaps guessing a bit up and down from the desired
size if the desired size isn't found.  If this fails, then it calls MF.

You can use dvips -d-1 to track what dvips is doing . . .

-tom