Bug#102120: tetex-bin: sparse docs for making PDF [with PATCH]
Alan -
>Ghostscript versions greater than 6.00 will embed Type 1 fonts.
>Current recommendations are GNU Ghostscript 6.51 (not yet packaged for
>Debian, but on the way) or Aladdin Ghostscript 7.0.
>
>Could you modify the patch to reflect this?
Here 'tis.
- Jim Van Zandt
--- texk/dvipsk/dvips.texi-orig Sat Oct 31 22:45:06 1998
+++ texk/dvipsk/dvips.texi Mon Jun 25 19:33:54 2001
@@ -1047,8 +1047,8 @@
can use the @samp{-t} option twice, once for the paper type, and once
for @samp{landscape}.
-@item -T @var{hsize,vsize}
-@opindex -T @var{hsize,vsize}
+@item -T @var{hsize},@var{vsize}
+@opindex -T @var{hsize},@var{vsize}
Set the paper size to (@var{hsize},@var{vsize}), a comma-separated pair
of dimensions such as @samp{.1in,-.3cm} (@pxref{papersize special}). It
overrides any paper size special in the DVI file.
@@ -2683,7 +2683,7 @@
@menu
-* Hypertext caveats:: Bitmaps poorly supported, psi.
+* Hypertext caveats:: Font quality, missing character psi.
* Hypertext specials:: The details on the specials.
@end menu
@@ -2695,19 +2695,66 @@
@cindex Computer Modern in PostScript
@cindex hypertext and bitmap fonts
-If you intend to go all the way to PDF, you will probably want to use
-PostScript fonts exclusively, since the Adobe PDF readers are extremely
-slow when dealing with bitmap fonts. Commercial versions of the
-Computer Modern fonts are available from Blue Sky; public domain
-versions are available from CTAN sites (for CTAN info,
-@pxref{unixtex.ftp,,, kpathsea, Kpathsea}) in:
+@cindex hypertext caveats
+@cindex embedding Type 1 fonts
+@cindex PDF files, font quality
+If you intend to go all the way to PDF, you may want to use the standard
+35 PostScript fonts exclusively, since other fonts are embedded as
+bitmaps by default. The Adobe PDF readers are extremely slow when
+dealing with bitmap fonts and the results look terrible on the screen.
+Printouts will probably look fine, but may not take full advantage of a
+high-resolution printer. Alternatively, you can have your fonts
+embedded as Type 1 scalable outlines. The resulting PostScript files
+may be larger, but can be effectively rasterized at any resolution.
+They can also be converted to PDF files that can be used effectively at
+any screen or printer resolution.
+
+To get the TeX fonts embedded in the PostScript file as Type 1 fonts,
+add @samp{-Ppdf} to the dvips command line switches. The printout
+for a run should look something like this:
+
+@example
+ dvips report -Ppdf -o report.ps
+ This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
+ ' TeX output 2001.06.15:0837' -> report.ps
+ <tex.pro><alt-rule.pro><texc.pro><texps.pro><special.pro>.
+ <cmbx9.pfb><cmsy6.pfb><cmsy7.pfb><cmr5.pfb><cmex10.pfb><cmr9.pfb>
+ <cmmi7.pfb><cmsy10.pfb><cmmib10.pfb><cmmi10.pfb><cmti10.pfb>
+ <cmr7.pfb><cmbx10.pfb><cmr10.pfb><cmti9.pfb><cmr12.pfb><cmbx12.pfb>
+ [1] [2<mean1.ps>] [3<bounce1-00.ps>] [4]
+@end example
+
+An entry like "<cmr10.pfb>" indicates success: dvips found the Computer
+Modern Roman 10 point font in a PostScript Font Binary file, translated
+it to an ASCII encoding, and embedded it. You can confirm this by
+examining the PostScript output file, looking for the section starting
+@code{%%BeginFont: CMR10} followed by an entry @code{/FontType 1 def}.
+
+The @samp{-Ppdf} option requires that the relevant outline (@file{.pfa}
+or @file{.pfb}) files be installed (@pxref{Font concepts}). For
+example, the @file{cmr10} file might be in
+@file{/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb}. Your TeX
+distribution may make those fonts available in a separate optional
+package (e.g. "tetex-extra" in a Debian system). Failing that,
+commercial versions of the Computer Modern fonts are available from Blue
+Sky; public domain versions are available from CTAN sites (for CTAN
+info, @pxref{unixtex.ftp,,, kpathsea, Kpathsea}) in:
@example
fonts/postscript/bakoma
fonts/postscript/paradissa
@end example
+
@noindent You may need to modify these fonts; see
@url{http://xxx.lanl.gov/faq/bakoma.html}.
+You can convert a PostScript file to PDF using @code{distill}, which
+comes with Adobe Acrobat, or @code{ps2pdf}, which comes with
+Ghostscript. The @code{ps2pdf} that comes with @code{Ghostscript}
+version 6.0 or earlier will not embed Type 1 fonts. Current
+recommendations are GNU Ghostscript 6.51 or Aladdin Ghostscript 7.0.
+You can check the fonts in a PDF file with Acrobat Reader by selecting
+the menu entries @samp{File|Document Info|Fonts}.
+
@cindex psi character missing
@cindex trailing spaces, dropped
@cindex spaces, dropped trailing
@@ -2728,6 +2775,16 @@
duplicate the first 32 characters starting at 192 to avoid MS-DOS
problems.
+For more information on the use of TeX to produce PDF files, see the
+article "Creating quality Adobe PDF files from TeX with DVIPS" by
+Kendall Whitehouse of Adobe. Adobe seems not to offer the article any
+more, but copies are available elsewhere, such as
+@url{http://www.math.hawaii.edu/~ralph/MathOnWeb/TeXPDF.html} or
+@url{http://www.utdallas.edu/~cantrell/online/543e.html}. You may also
+want to check "Notes on converting (La)TeX documents to robust PDF using
+Rokicki's dvips and Acrobat Distiller" by Timothy P. Van Zandt, at
+@url{http://www.emrg.com/texpdf.htmlhttp://zandtwerk.insead.fr/tex2pdf.html}.
+
@node Hypertext specials
@subsection Hypertext specials
@@ -3236,7 +3293,7 @@
@end example
@item
-Insert an entry for the font in @file{psfonts.map} (@xref{psfonts.map}):
+Insert an entry for the font in @file{psfonts.map} (@pxref{psfonts.map}):
@example
rptmr Times-Roman <ptmr8a.pfa
@end example
Reply to: