There are outline versions of the CM fonts, but some publications and
organizations insist on specific fonts.
On 31 Jan 2003, David Kastrup wrote:
Giuseppe Greco [EMAIL PROTECTED] writes:
Or if you just want to do it for one file, not as the default for
the full installation, just use the following flag to dvips:
dvips -Ppdf myfile.dvi
or maybe (depending on what fonts you use)
dvips -Ppdf -G0 myfile.dvi
This works quite fine, but the result is not
so good as with pdflatex...
Which might mean a problem with something entirely unrelated to
the fonts (e.g., wrong papersize, problems with links, etc.).
Then your font map files for dvips are not appropriate for the set of
fonts you have installed.
It is very hard to know what is going on without more details. If the
problem is related to fonts, then it is useful to keep track of exactly
which fonts are being used. When dvips runs, it lists the font files:
$ dvips -P pdf story.dvi
This is dvips(k) 5.92a Copyright 2002 Radical Eye Software
(www.radicaleye.com)
' TeX output 2003.01.23:1320' - story.ps
tex.proalt-rule.protexc.prof7b6d320.enctexps.pro. cmr10.pfb
cmsl10.pfbcmbx10.pfb[1]
From this we see that the Type 1 versions of cmr10, cmsl10, and cmbx10
were used. If you can get the resulting pdf file to a computer running
*nix, then it is easy to check which fonts are actually used in a pdf
file.
$ pdffonts story.pdf
name type emb sub uni object ID
--- --- --- -
KGIMMU+CMBX10Type 1 yes yes no 10 0
NSPLPE+CMSL10Type 1 yes yes no 13 0
ZHKQYB+CMR10 Type 1 yes yes no 16 0
When you view the file with acroread, you can also get a list of the
fonts Alt+Ctl+F. Unfortunately, this isn't in a form that is easy to
paste into email, but you should see something like:
Original Font Type Used Font Type
CMBX10 Type 1 Custom Embedded Subset Type 1
CMBSL10Type 1 Custom Embedded Subset Type 1
CMR10 Type 1 Custom Embedded Subset Type 1
--
George White [EMAIL PROTECTED]
Head of St. Margarets Bay, Nova Scotia
