.pk
files in its output. Even
PDFTeX will use .pk
files if it can see no alternative for
a font in the document it is processing.
Our remedy is to use
“Adobe Type 1”
versions of the fonts we need. Since Adobe are in the
business of selling Type 1 fonts, Reader was of course made
to deal with them really rather well, from the very beginning.
Of course, if your document uses nothing but fonts that came from
Adobe in the first place — fonts such as Times that
appear in pretty much every PostScript printer, or such as Adobe
Sabon that you pay extra for — then there’s no problem.
But most people use Computer Modern to start
with, and even those relative sophisticates who use something as
exotic as Sabon often find themselves using odd characters
from CM without really intending to do so. Fortunately, rather
good versions of the CM fonts are available from the AMS
(who have them courtesy of
Blue Sky Research and Y&Y).
Most modern systems have the fonts installed ready to use; and any
system installed less than 3 years ago has a dvips
configuration file ‘pdf
’ that signals the use of the
CM fonts, and also sets a few other parameters to improve
dvips’ output. Use this configuration as:
dvips -Ppdf myfile -o myfile.psThis may produce a warning message about failing to find the configuration file:
dvips: warning: no config file for `pdf'or something similar, or about failing to find a font file:
dvips: ! Couldn't find header file cmr10.pfbEither of these failures signals that your system doesn’t have the fonts in the first place. A way of using the fonts that doesn’t involve the sophistication of the
-Ppdf
mechanism is simply to load maps:
dvips -Pcmz -Pamz myfile -o myfile.psYou may encounter the same warning messages as listed above. If your system does not have the fonts, it won’t have the configuration file either; however, it might have the configuration file without the fonts. In either case, you need to install the fonts.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3