From kb@cs.umb.edu Thu Dec 5 12:42:23 1996 Received: from CS.Stanford.EDU (CS.Stanford.EDU [171.64.64.64]) by Xenon.Stanford.EDU (8.8.4/8.8.4) with ESMTP id MAA09185 for <rokicki@xenon.Stanford.EDU>; Thu, 5 Dec 1996 12:42:19 -0800 (PST) Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by CS.Stanford.EDU (8.8.2/8.7.1) with SMTP id MAA09293 for <rokicki@CS.Stanford.EDU>; Thu, 5 Dec 1996 12:39:19 -0800 (PST) Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA22207 (5.65c/IDA-1.4.4 for <rokicki@CS.Stanford.EDU>); Thu, 5 Dec 1996 15:41:08 -0500 From: "K. Berry" <kb@cs.umb.edu> Received: (from kb@localhost) by terminus.cs.umb.edu (8.8.0/8.8.0) id PAA07211; Thu, 5 Dec 1996 15:40:11 -0500 (EST) Date: Thu, 5 Dec 1996 15:40:11 -0500 (EST) Message-Id: <199612052040.PAA07211@terminus.cs.umb.edu> To: rokicki@CS.Stanford.EDU Subject: 562 Content-Length: 162529 Status: RO
That's good news about dvips 562. I hope I'll be able to integrate everything back into dvipsk for the upcoming web2c 7.0 release.
Oh, finally, I am looking for a program that will let me (for relatively simple documents) generate fair-looking TeX and HTML (and man as well,
My recommendation: Write your manual in Texinfo. You can generate DVI files with texinfo.tex, HTML with texi2html (http://wwwcn.cern.ch/dci/texi2html/), plain ASCII, and Info format for Emacs/Info. There's a texi2roff, too, but I've never been able to bring myself to write a manual badly enough to be able to generate a man page from it.
prep.ai.mit.edu/pub/gnu/texinfo-3.9.tar.gz ...
I will append my current dvipsk manual, which started life as your dvips manual. I've been faithful about updating it with your changes (except I didn't do 560alpha and obviously haven't done 562 yet). I and others have also added a lot of additional text/explanation/index entries/you name it.
Except for the installation section, I suspect we could converge on basically the same manual if you adopt Texinfo.
\input texinfo
@dircategory TeX @direntry * DVI-to-Postscript: (dvips). Translating TeX DVI files to PostScript. * afm2tfm: (dvips)Invoking afm2tfm. Making Type 1 fonts available to TeX. * dvips: (dvips)Invoking dvips. DVI-to-PostScript translator.
This document is based on `dvips.tex' by Tomas Rokicki. It is in the public domain.
The Dvips program has a number of features that set it apart from other PostScript drivers for TeX. This rather long section describes the advantages of using Dvips, and may be skipped if you are just interested in learning how to use the program. See section Installation, for details of compilation and installation.
The Dvips driver generates excellent, standard PostScript, that can be included in other documents as figures or printed through a variety of spoolers. The generated PostScript requires very little printer memory, so very complex documents with a lot of fonts can easily be printed even on PostScript printers without much memory, such as the original Apple LaserWriter. The PostScript output is also compact, requiring less disk space to store and making it feasible as a transfer format.
Even those documents that are too complex to print in their entirety on a particular printer can be printed, since Dvips will automatically split such documents into pieces, reclaiming the printer memory between each piece.
The Dvips program supports graphics in a natural way, allowing PostScript graphics to be included and automatically scaled and positioned in a variety of ways.
Printers with any resolution are supported, even if they have different resolutions in the horizontal and vertical directions. High resolution output is supported for typesetters, including an option that compresses the bitmap fonts so that typesetter virtual memory is not exhausted. This option also significantly reduces the size of the PostScript file and decoding in the printer is very fast.
Missing fonts can be automatically generated if Metafont exists on the system, or fonts can be converted from GF to PK format on demand. If a font cannot be generated, a scaled version of the same font at a different size can be used instead, although Dvips will complain loudly about the poor aesthetics of the resulting output.
Users will appreciate features such as collated copies and support for `tpic', `psfig', `emtex', and `METAPOST'; system administrators will love the support for multiple printers, each with their own configuration file, and the ability to pipe the output directly to a program such as `lpr'. Support for MS-DOS, OS/2, and VMS in addition to Unix is provided in the standard distribution, and porting to other systems is easy.
One of the most important features is the support of virtual fonts, which add an entirely new level of flexibility to TeX. Virtual fonts are used to give Dvips its excellent PostScript font support, handling all the font remapping in a natural, portable, elegant, and extensible way. Dvips even comes with its own Afm2tfm program that creates the necessary virtual fonts and TeX font metric files automatically from the Adobe font metric files.
Source is provided and freely distributable, so adding a site-specific feature is possible. Adding such features is made easier by the highly modular structure of the program.
There is really no reason to use another driver, and the more people use Dvips, the less time will be spent fighting with PostScript and the more time will be available to create beautiful documents. So if you don't use Dvips on your system, get it today.
Tom Rokicki wrote and maintains the original Dvips program.
(A copy of this chapter is in the distribution file `dvipsk/INSTALL'.)
Installing Dvips is mostly the same as installing any Kpathsea-using program. Therefore, for the basic steps involved, see section `Installation' in Kpathsea. (A copy is in the file `kpathsea/INSTALL'.)
For solutions to common installation problems and information on how to report a bug, see the file `kpathsea/BUGS' (see section `Bugs' in Kpathsea). For solutions to Dvips-specific problems, see section Debug options.
Dvips does require some additional installation, detailed in the sections below. Also, to configure color devices, see section Color device configuration.
Dvips has its own configuration files: a file `config.ps' for
sitewide defaults, and a file `config.printer' for each
printer (output device). Since these are site-specific, make
install does not create them; you must create them yourself.
(These Dvips configuration files are independent of the Kpathsea onfiguration file `texmf.cnf' (see section `Config files' in Kpathsea).
Dvips configuration files contents and searching are described fully in section Dvips configuration files. The simplest way to create a new configuration file is to copy and modify the file `dvipsk/contrib/config.proto', seasoning with options to your taste from section Dvips configuration files. Here is `config.proto' for your reading pleasure:
To use PostScript fonts with TeX and Dvips, you need both metric files (`.tfm' and `.vf') and the outlines (`.pfa' or `.pfb'). See section Font concepts.
To support the basic PostScript font set, the recommended (and simplest)
approach is to retrieve @url{ftp://ftp.tug.org/tex/psfonts.tar.gz} and
unpack it in your $(fontdir) directory
(`/usr/local/share/texmf/fonts' by default). This archive contains
metrics, outlines, and bitmaps (for previewing) for the 35 de facto
standard fonts donated by URW and the additional high-quality freely
available PostScript fonts donated by Adobe, Bitstream, and URW,
including geometrically-created variants such as oblique and small caps.
`CTAN:/fonts/psfonts' contains support for many additional fonts for which you must buy outlines (Adobe, Bigelow & Holmes, Monotype, Softkey, Y&Y). `psfonts.tar.gz' is a small extract from this directory. (For CTAN info, see section `unixtex.ftp' in Kpathsea; a copy is in the top-level file `INSTALL'.)
If you have a commercial Unix system, it may have come with PostScript fonts. If so, you can make them available to Dvips by (1) copying or linking them with appropriate filenames; and (2) running Afm2tfm (see section Making a PostScript font available) to make TFM and VF metrics for TeX and Dvips to use. Also check `psfonts.map' to be sure the fonts are listed there (see section `psfonts.map': PostScript font catalog); it contains everything contained in `psfonts.tar.gz' and most fonts that come with Unix systems, but your particular supplier may have come up with something new.
Following are locations for vendor-supplied fonts. Please mail @email{tex-k@mail.tug.org} if you find fonts elsewhere on your system.
The NeXT system supplies more fonts than any others, but there's a lot of overlap.
Finally, if you have an Hewlett-Packard printer, you should be able to get Type 1 font files for the standard 35 fonts from HP, if the freely available URW Type 1's do not satisfy for whatever reason. The phone number for HP Printer Drivers is (in the United States) 303-339-7009. The driver set to ask for is Adobe Type Manager 2.51, and the disk set number is `MP210en3'. Mentioning anything other than Microsoft Windows when you ask for the driver set will likely lead to great confusion on the other end.
Ghostscript is a PostScript interpreter freely available to end-users, written by Peter Deutsch. It can read the PostScript produced by Dvips and render it on your monitor, or for another device (e.g., an Epson printer) that does not support PostScript, or in PDF format. The latest version is available via @url{http://www.cs.wisc.edu/~ghost/index.html} and @url{ftp://ftp.cs.wisc.edu/pub/ghost/aladdin/}.
There is also a somewhat older version of Ghostscript available under the GNU General Public License, free to everyone. You can get that from @url{ftp://prep.ai.mit.edu/pub/gnu/}.
The program Ghostview, written by Tim Theisen, provides typical previewing capabilities (next page/previous page, magnification, etc.). It requires Ghostscript to run, and files in structured Postscript, specifically with `%%Page' comments (no `N' in `config.ps'). You can get Ghostview from the same places as Ghostscript.
You've gone through all the trouble of installing Dvips, carefully read all the instructions in this manual, and still can't get something to work. The following sections provide some helpful hints if you find yourself in such a situation.
For details on effective bug reporting, common installation problems,
and MakeTeXPK problems, see section `Bugs' in Kpathsea.
The `-d' flag to Dvips helps in tracking down certain errors. The
parameter to this flag is an integer that tells what errors are
currently being tracked. To track a certain class of debug messages,
simply provide the appropriate number given below; if you wish to track
multiple classes, sum the numbers of the classes you wish to track. To
track all classes, you can use -1. Another useful value is
3650, which tracks everything having to do with file searching
and opening.
Some of these debugging options are actually provided by Kpathsea (see section `Debugging' in Kpathsea).
The classes are:
stat calls
If you are not getting any output at all, even from the simplest one-character file (for instance, `\ \bye'), then something is very wrong. Practically any file sent to a PostScript laser printer should generate some output, at the very least a page detailing what error occurred, if any. Talk to your system administrator about downloading a PostScript error handler. (Adobe distributes a good one called `ehandler.ps'.)
It is possible, especially if you are using non-Adobe PostScript, that your PostScript interpreter is broken. Even then it should generate an error message. Dvips tries to work around as many bugs as possible in common non-Adobe PostScript interpreters, but doubtless it misses a few. PowerPage Revision 1, Interpreter Version 20001.001, on a Mitsubishi Shinko CHC-S446i color thermal dye sublimation printer is known to be unable to print with any but builtin fonts.
If Dvips gives any strange error messages, or compilation on your machine generated a lot of warnings, perhaps the Dvips program itself is broken. Try using the debug options to determine where the error occurred (see section Debug options).
It is possible your spooler is broken and is misinterpreting the structured comments. Try the `-N' flag to turn off structured comments and see what happens.
If some documents come out inverted or too small, probably your spooler is not supplying an end of job indicator at the end of each file. (This commonly happens on small machines that don't have spoolers.) You can force Dvips to do this with the `-F' flag (or `F' config file option), but this generates files with a terminating binary character (control-D). You can also try using the `-s' flag (or `s' config file option) to enclose the entire job in a save/restore pair. See section Command-line options, and section Dvips configuration files.
If your printer returns error messages, the error message gives very good information on what might be going wrong. One of the most common error messages is `bop undefined'. This is caused by old versions of Transcript and other spoolers that do not properly parse the setup section of the PostScript. To fix this, turn off structured comments with the `-N' option, but it'd be best to get your spooling software updated.
Another error message is `VM exhausted'. Some printers indicate this error by locking up, others quietly reset. This is caused by Dvips thinking that the printer has more memory than it actually does, and then printing a complicated document. To fix this, try lowering the `m' parameter in the configuration file; use the debug option to make sure you adjust the correct file.
Other errors may indicate you are trying to include graphics that don't nest properly in other PostScript documents, among other things. Try the PostScript file on a QMS PS-810 or other Adobe PostScript printer if you have one, or Ghostscript (see section Ghostscript installation); it might be a problem with the printer itself.
This is usually caused by incorrectly specifying the amount of memory the printer has in the configuration file; see the previous section.
The most common problem with including graphics is an incorrect bounding box (see section The bounding box comment). Complain to whoever wrote the software that generated the file if the bounding box is indeed incorrect.
Another possible problem is that the figure you are trying to include does not nest properly; there are certain rules PostScript applications must follow when generating files to be included. The Dvips program includes work-arounds for such errors in Adobe Illustrator and other programs, but there are certainly applications that haven't been tested.
One possible thing to try is the `-K' flag which strips the comments from an included figure. This might be necessary if the PostScript spooling software does not read the structured comments correctly. Use of this flag will break graphics from some applications, though, since some applications read the PostScript file from the input stream, looking for a particular comment.
Any application which generates graphics output containing raw binary (not ASCII hex) will probably fail with Dvips.
Dvips reads a DVI file as output by (for example) TeX, and converts it to PostScript, taking care of builtin or downloaded PostScript fonts, font reencoding, color, etc. These features are described in other chapters in this document.
There many ways to control Dvips' behavior: configuration files, environment variables, and command-line options.
To use Dvips at its simplest, simply type
dvips foo
where `foo.dvi' is the output of TeX that you want to print. If Dvips has been installed correctly, the document will probably roll out of your default printer.
If you use fonts that have not been used on your system before, they may be automatically generated; this process can take a few minutes, so progress reports appear by default. The next time that document is printed, these fonts will have been saved in the proper directories, so printing will go much faster. (If Dvips tries to endlessly generate the same fonts over and over again, it hasn't been installed properly. See section `Unable to generate fonts' in Kpathsea.)
Many options are available (see the next section). For a brief summary of available options, just type
dvips --help
Dvips has a plethora of command line options. Reading through this section will give a good idea of the capabilities of the driver.
Here is a handy summary of the options; it is printed out when you run Dvips with no arguments or with the standard `--help' option.
Many of the parameterless options listed here can be turned off by suffixing the option with a zero (`0'); for instance, to turn off page reversal, use `-r0'. Such options are marked with a trailing `*'.
PRINTER environment variable; use `-P$PRINTER' after the
`-f' to read it anyway. It also turns off the automatic sending of
control-D if it was turned on with the `-F' option or in the
configuration file; use `-F' after the `-f' to send it anyway.
MakeTeXPK, the invocation is appended to a file
`missfont.log' (by default) in the current directory. You can then
execute the log file to create the missing files after fixing the
problem.
If the current directory is not writable and the environment variable or
configuration file value `TEXMFOUTPUT' is set, its value is used.
Otherwise, nothing is written. The name `missfont.log' is
overridden by the `MISSFONT_LOG' environment variable or
configuration file value.
popen; thus, specifying `|lpr' as
the output file will automatically queue the file for printing as usual.
`-o' disables the automatic reading of the PRINTER
environment variable, and turns off the automatic sending of control-D.
See the `-f' option for how to override this.
O value--some printers vary widely from run to run.
If your printer offsets every other page consistently, instead of every
page, your best recourse is to use `bop-hook' (see section PostScript hooks).
PRINTER is checked. If that variable exists, and a corresponding
`config.printer' file exists, it is read.
See section Configuration file searching.
\special
(via ``', see section Dynamic creation of PostScript graphics files) and config files
(via the `E' option, see section Configuration file commands), pipes as
output files, and opening of any absolute filenames.
mtpk or gsftopk or pstopk or some combination
thereof to generate the required bitmap fonts; these programs are
supplied with Dvips. The bitmap must be put into `psfonts.map' as
the downloadable file for that font. This is useful only for those
fonts for which you do not have real outlines, being downloaded to
printers that have no resident fonts, i.e., very rarely.
Dvips looks for many environment variables, to define search paths and
other things. The path variables are read as needed, after all
configuration files are read, so they override values in the
configuration files. (Except for TEXCONFIG, which defines where
the configuration files themselves are found.)
See section `Path specifications' in Kpathsea, for details of interpretation of path and other environment variables common to all Kpathsea-using programs. Only the environment variables specific to Dvips are mentioned here.
DVIPSFONTS
DVIPSHEADERS
DVIPSMAKEPK
MakeTeXPK program with the MAKETEXPK environment
variable; see section `MakeTeX script arguments' in Kpathsea.
DVIPSSIZES
PRINTER
PRINTER to determine the output destination in any way.)
TEXCONFIG
TEXPICTS
TEXINPUTS is looked for. See section `Supported file formats' in Kpathsea.
This section describes in detail the Dvips-specific `config.*' device configuration files, which override the `texmf.cnf' configuration files generic to Kpathsea which Dvips also reads (see section `Config files' in Kpathsea).
For information about installing these files, including a prototype file you can copy, see section `config.ps' installation.
The Dvips program loads many different configuration files, so that parameters can be set globally across the system, on a per-device basis, or individually by each user.
PRINTER. If it exists, then
`config.$PRINTER' is loaded (if it exists).
Because the `.dvipsrc' file is read before the printer-specific
configuration files, individual users cannot override settings in the
latter. On the other hand, the TEXCONFIG path usually includes
the current directory, and can in any case be set to anything, so the
users can always define their own printer-specific configuration files
to be found before the system's.
A few command-line options are treated specially, in that they are not overridden by configuration files:
The purpose of these special cases is to (1) minimize the chance of having a mismatched mode and resolution (which `MakeTeXPK' cannot resolve), and (2) let command-line options override config files where possible.
Most of the configuration file commands are similar to corresponding command line options, but there are a few exceptions. When they are the same, we omit the description here.
As with command line options, many may be turned off by suffixing the letter with a zero (`0').
Within a configuration file, empty lines, and lines starting with a space, asterisk, equal sign, percent sign, or pound sign are ignored. There is no provision for continuation lines.
system(3); can be used to get
the current date into a header file for inclusion, for instance.
Possibly dangerous; this may be disabled, in which case a warning will
be printed if the option is used (and warnings are not suppressed).
DVIPSHEADERS overrides this.
%! Hey, we're PostScript /Times-Roman findfont 30 scalefont setfont 144 432 moveto vmstatus exch sub 40 string cvs show pop showpageThe number printed by this file is the total memory free; it is usually best to tell Dvips that the printer has slightly less memory, because many programs download permanent macros that can reduce the memory in the printer. Some systems or printers can dynamically increase the memory available to a PostScript interpreter, in which case this file might return a ridiculously low number; for example, the NeXT computer and Ghostscript. In these cases, a value of one million works fine.
o |lpr -Pfoo
PKFONTS, TEXPKS, GLYPHFONTS, and TEXFONTS
environment variables override this. See section `Supported file formats' in Kpathsea.
TEXPICTS and then
TEXINPUTS environment variables override this.
TFMFONTS and then
TEXFONTS environment variables overrides this. This path is used
for resident fonts and fonts that can't otherwise be found.
Most TeX documents at a particular site are designed to use the standard paper size (letter size in the United States, A4 in Europe). The Dvips program can be customized either sitewide or for a particular printer.
But many documents are designed for other paper sizes. For instance, you may want to design a document that has the long edge of the paper horizontal. This can be useful when typesetting booklets, brochures, complex tables, or many other documents. This type of paper orientation is called landscape orientation (the default orientation is portrait). Alternatively, a document might be designed for ledger or A3 paper.
Since the intended paper size is a document design decision, not a printing decision, such information should be given in the TeX file and not on the Dvips command line. For this reason, Dvips supports a `papersize' special. It is hoped that this special will become standard over time for TeX previewers and other printer drivers.
The format of the `papersize' special is
\special{papersize=width,height}
width is the horizontal size of the page, and height is the vertical size. The dimensions supported are the same as for TeX; namely, in (inches), cm (centimeters), mm (millimeters), pt (points), sp (scaled points), bp (big points, the same as the default PostScript unit), pc (picas), dd (didot points), and cc (ciceros).
For a US letter size landscape document, the papersize would be:
\special{papersize=11in,8.5in}
An alternate specification of landscape:
\special{landscape}
This is supported for backward compatibility, but it is hoped that
reventually the papersize comment will dominate.
Of course, such a \special only informs Dvips of the desired
paper size; you must also adjust \hsize and \vsize in your
TeX document typeset to those dimensions.
The papersize special must occur somewhere on the first page of
the document.
The `@' command in a configuration file sets the paper size defaults and options. The first `@' command defines the default paper size. It has three possible parameters:
@ [name [hsize vsize]]
If `@' is specified on a line by itself, with no parameters, it instructs Dvips to discard all previous paper size information (possibly from another configuration file).
If three parameters are given, with the first parameter being a name and the second and third being a dimension (as in `8.5in' or `3.2cc', just like in the `papersize' special), then the option is interpreted as starting a new paper size description, where name is the name and hsize and vsize define the horizontal and vertical size of the sheet of paper, respectively. For example:
@ letterSize 8.5in 11in
If both hsize and vsize are zero (you must still specify units!) then any page size will match. If the `@' character is immediately followed by a `+' sign, then the remainder of the line (after skipping any leading blanks) is treated as PostScript code to send to the printer, presumably to select that particular paper size:
@ letter 8.5in 11in @+ %%BeginPaperSize: Letter @+ letter @+ %%EndPaperSize
After all that, if the first character of the line is an exclamation point, then the line is put in the initial comments section of the final output file; else, it is put in the setup section of the output file. For example:
@ legal 8.5in 14in @+ ! %%DocumentPaperSizes: Legal @+ %%BeginPaperSize: Legal @+ legal @+ %%EndPaperSize
When Dvips has a paper format name given on the command line, it looks for a match by the name; when it has a `papersize' special, it looks for a match by dimensions. The first match found (in the order the paper size information is found in the configuration file) is used. If nothing matches, a warning is printed and the first paper size is used. The dimensions must match within a quarter of an inch. Landscape mode for all paper sizes is automatically supported.
If your printer has a command to set a special paper size, then give dimensions of `0in 0in'; the PostScript code that sets the paper size can refer to the dimensions the user requested as `hsize' and `vsize'; these will be macros defined in the PostScript that return the requested size in default PostScript units. Virtually all of the PostScript commands you use here are device-dependent and degrade the portability of the file; that is why the default first paper size entry should not send any PostScript commands down (although a structured comment or two would be okay). Also, some printers want `BeginPaperSize' comments and paper size setting commands; others (such as the NeXT) want `PaperSize' comments and they will handle setting the paper size. There is no solution I could find that works for both (except maybe specifying both).
The Perl 5 script `contrib/mkdvipspapers' in the distribution directory may help in determining appropriate paper size definitions.
If your printers are configured to use A4 paper by default, the configuration file (probably the global `config.ps' in this case) should include this as the first `@' command:
@ A4size 210mm 297mm @+ %%PaperSize: A4
so that A4size is used as the default, and not A4 itself;
thus, no PostScript a4 command is added to the output file,
unless the user explicitly says to use paper size `a4'. That is,
by default, no paper size PostScript command should be put in the
output, but Dvips will still know that the paper size is A4 because
`A4size' is the first (and therefore default) size in the
configuration file.
Executing the `letter' or `a4' or other PostScript operators cause the document to be nonconforming and can cause it not to print on certain printers, so the default paper size should not execute such an operator if at all possible.
Some printers, such as the Hewlett-Packard HP4si, have multiple paper
trays. You can set up Dvips to take advantage of this using the
bop-hook PostScript variable (see section PostScript hooks).
For example, suppose you have an alternate tray stocked with letterhead
paper; the usual tray has the usual paper. You have a document where
you want the first page printed on letterhead, and the remaining pages
on the usual paper. You can create a header file, say
`firstletterhead.PS', with the following (PostScript) code
(bop-hook is passed the current physical page number, which
starts at zero):
/bop-hook { dup 0 eq { alternatetray } { normaltray } ifelse } def
where alternatetray and normaltray are the appropriate commands to select the paper trays. On the 4SI, alternatetray is `statusdict begin 1 setpapertray end' and normaltray is `statusdict begin 0 setpapertray end'.
Then, include the file with either
Dvips supports inclusion of PostScript figure files (e.g., Encapsulated PostScript), downloading other header files (e.g., fonts), including literal PostScript code, and hypertext.
Scaling and including PostScript graphics is a breeze--if the PostScript file is correctly formed. Even if it is not, however, the file can usually be accommodated with just a little more work.
The most important feature of a good PostScript file from the standpoint of including it in another document is an accurate bounding box comment. Every well-formed PostScript file has a comment describing where on the page the graphic is located, and how big that graphic is.
This information is given as the lower left and upper right corners of the box just enclosing the graphic, and is thus referred to as the bounding box. These coordinates are given in the default PostScript units (there are precisely 72 PostScript units to the inch, like TeX big points) with respect to the lower left corner of the sheet of paper.
To see if a PostScript file has a bounding box comment, just look at the first few lines of the file. PostScript files are standard ASCII, so you can use any text editor to do this. If within the first few dozen lines there is a line like
%%BoundingBox: 25 50 400 300
(with any reasonable numbers), chances are very good that the file is Encapsulated PostScript and will work easily with Dvips. If the file contains instead a line like
%%BoundingBox: (atend)
the file is still probably Encapsulated PostScript, but the bounding box is given at the end of the file. Dvips needs it at the beginning. You can move it with that same text editor, or a simple script. (The bounding box is given in this way when the program that generated the PostScript couldn't know the size in advance, or was too lazy to compute it.)
If the document lacks a `%%BoundingBox:' altogether, you can determine one in a couple of ways. One is to use the `bbfig' program distributed with Dvips in the `contrib' directory. This can usually find the correct bounding box automatically; it works best with Ghostscript.
If the comment looks like this:
%%BoundingBox: 0 0 612 792
the graphic claims to take up an entire sheet of paper. This is usually a symptom of a bug in the program that generated it.
The other is to do it yourself: print the file. Now, take a ruler, and make the following measurements (in PostScript units, so measure in inches and multiply by 72): From the left edge of the paper to the leftmost mark on the paper is llx, the first number. From the bottom edge of the paper to the bottommost mark on the paper is lly, the second number. From the left edge of the paper to the rightmost mark on the paper is urx, the third number. The fourth and final number, ury, is the distance from the bottom of the page to the uppermost mark on the paper.
Once you have the numbers, add a comment of the following form as the second line of the document. (The first line should already be a line starting with the two characters `%!'; if it is not, the file probably isn't PostScript.)
%%BoundingBox: llx lly urx ury
Or, if you don't want to modify the file, you can simply write these numbers down in a convenient place and give them in your TeX document when you import the graphic, as described in the next section.
If the document does not have such a bounding box, or if the bounding box is given at the end of the document, or the bounding box is wrong, please complain to the authors of the software package that generated the file.
Once the figure file has a bounding box comment (see the previous section,) you are ready it the graphic into a TeX document. Many packages for using EPS files exist. One distributed with Dvips is the files `epsf.tex' (for plain TeX) and `epsf.sty' (for LaTeX). For plain TeX, add a line like this near the top of your input file:
\input epsf
If your document is in LaTeX, add the `epsf' style option, as in:
\documentstyle[12pt,epsf]{article}
(The above only needs to be done once, no matter how many figures you plan to include.)
Now, at the point you want to include a file, enter a line such as:
\epsffile{foo.eps}
If you are using LaTeX, you may need to add \leavevmode
immediately before the \epsffile command to get certain
environments to work correctly. If your file does not have a bounding
box comment, you can supply the numbers as determined in the previous
section, in the same order they would have been in a normal bounding box
comment:
\epsffile[100 100 500 500]{foo.ps}
Now, save your changes and run TeX and Dvips; the output should have your graphic positioned at precisely the point you indicated, occupying the proper amount of space.
The \epsffile macro typesets the figure as a TeX \vbox
at the point of the page that the command is executed. By default, the
graphic will have its `natural' width (namely, the width of its bounding
box). The TeX box will have depth zero and its natural height. By
default, the graphic will be scaled by any DVI magnification in effect,
just as is everything else in your document. See the next section for
more information on scaling.
If you want TeX to report the size of the figure as a message on your terminal when it processes each figure, give the command:
\epsfverbosetrue
Usually, you will want to scale an EPSF figure to some size appropriate for your document, since its natural size is determined by the creator of the EPS file.
The best way to do this is to assign the desired size to the TeX
\epsfxsize or \epsfysize variables, whichever is more
convenient for you. That is, put
\epsfxsize=dimen
right before the call to \epsffile. Then the width of the TeX
box will be dimen and its height will be scaled proportionately.
Similarly, you can set the vertical size with
\epsfysize=dimen
in which case the height will be set and the width scaled proportionally.
If you set both, both will be honored, but the aspect ratio of the included graphic may necessarily be distorted, i.e., its contents stretched in one direction or the other.
You can resize graphics in a more general way by redefining the
\epsfsize macro. \epsffile calls this with two
parameters: the natural horizontal and vertical sizes of the PostScript
graphic. \epsfsize must expand to the desired horizontal size,
that is, the width of the \vbox. Schematically:
\def\epsfsize#1#2{body}
Some useful definitions of body:
\epsfxsize to the same value it had before the macro
was called.
\hsize. (In LaTeX, use \textwidth
instead of \hsize.)
\hsize, scale to
\hsize, otherwise use the natural width.
For compatibility with other PostScript drivers, it is possible to turn off the default scaling of included figures by the DVI magnification with the following TeX command:
\special{! /magscale false def}
Use of this command is not recommended because it will make the
\epsffile graphics the "wrong" size if global magnification is
being used, and it will cause any PostScript graphics to appear
improperly scaled and out of position if a DVI to DVI program is used to
scale or otherwise modify the document.
DVI magnification is not applied to any output from code you write in `bop-hook' or its ilk (see section PostScript hooks),
By default, clipping is disabled for included EPSF images. This is because clipping to the bounding box dimensions often cuts off a small portion of the figure, due to slightly inaccurate bounding box arguments. The problem might be subtle; lines around the boundary of the image might be half their intended width, or the tops or bottoms of some text annotations might be sliced off. If you want to turn clipping on, just use the command
\epsfclipon
and to turn clipping back off, use
\epsfclipoff
The basic special for file inclusion is as follows:
\special{psfile=filename.ps [key=value] ... }
This downloads the PostScript file `filename.ps' such that the current point will be the origin of the PostScript coordinate system. The optional key=value assignments allow you to specify transformations on the PostScript.
The possible keys are:
The dimension parameters are all given in PostScript units. The `hscale' and `vscale' are given in non-dimensioned percentage units, and the rotation value is specified in degrees. Thus
\special{psfile=foo.ps hoffset=72 hscale=90 vscale=90}
will shift the graphics produced by file `foo.ps' right by one inch and will draw it at 0.9 times normal size. Offsets are given relative to the point of the special command, and are unaffected by scaling or rotation. Rotation is counterclockwise about the origin. The order of operations is to rotate the figure, scale it, then offset it.
For compatibility with older PostScript drivers, it is possible to change the units that `hscale' and `vscale' are given in. This can be done by redefining `@scaleunit' in `SDict' by a TeX command such as
\special{! /@scaleunit 1 def}
The `@scaleunit' variable, which is by default 100, is what `hscale' and `vscale' are divided by to yield an absolute scale factor.
PostScript is an excellent page description language--but it does tend to be rather verbose. Compressing PostScript graphics files can reduce them by factor of five or more. For this reason, if a the name of an included PostScript file ends with `.Z' or `.gz', Dvips automatically runs `gzip -d'. For example:
\epsffile[72 72 540 720]{foo.ps.gz}
Since the results of such a command are not accessible to TeX, if you use this facility with the `epsf' macros, you need to supply the bounding box parameter yourself, as shown.
More generally, if the filename parameter to one of the graphics inclusion techniques starts with a left quote (``'), the parameter is instead interpreted as a command to execute that will send the actual file to standard output. For example:
\special{psfile="`gnuplot foo"}
to include `screendump.ps'. Of course, the command to be executed can be anything, including using a file conversion utility such as `tek2ps' or whatever is appropriate. This feature can be disabled with the `-R' command-line option or `R' configuration option.
You can use any font available to TeX and Dvips within a graphics
file by putting a %*Font: line in the leading commentary of the
file. Schematically, this looks like:
%*Font: tfmname scaledbp designbp hex-start:hex-bitstring
Here is the meaning of each of these elements:
MetaPost's output figures contain lines like this for bitmap fonts used in a MetaPost label (see section `MetaPost' in Web2c).
Header files are bits of PostScript included in the output file; generally they provide support for special features, rather than producing any printed output themselves. You can explicitly request downloading header files if necessary for some figure, or to achieve some special effect.
Dvips includes some headers on its own initiative, to implement features
such as PostScript font reencoding, bitmap font downloading, handling of
\special's, and so on. These standard headers are the
`.pro' files (for "prologue") in the installation directory
`$(psheaderdir)'; they are created from the `.lpro' ("long
prologue") files in the distribution by stripping
comments, squeezing blank lines, etc., for maximum efficiency. If you
want to peruse one of the standard header files, read the `.lpro'
version.
The PostScript dictionary stack will be at the `userdict' level when header files are included.
In order to get a particular graphic file to work, a certain font or
header file might need to be sent first. The Dvips program provides
support for this with the `header' \special. For instance,
to ensure that `foo.ps' gets downloaded:
\special{header=foo.ps}
As another example, if you have some PostScript code that uses a PostScript font not built into your printer, you must download it to the printer. If the font isn't used elsewhere in the document, Dvips can't know you've used it, so you must include it in the same way, as in:
\special{header=putr.pfa}
to include the font definition file for Adobe Utopia Roman.
You can include headers when you run Dvips, as well as from your document (see the previous section). To do this, run Dvips with the option `-P header'; this will read the file `config.header', which in turn can specify a header file to be downloaded with the `h' option. See section Configuration file commands.
You can arrange for the same file to serve as a `-P' config file and the downloadable header file, by starting the lines of PostScript code with a space, leaving only the `h' line and any comments starting in the first column. As an example, see `contrib/volker/config.*'. (These files also perform useful functions: controlling duplex/simplex mode on duplex printers, and setting various screen frequencies; `contrib/volker/README' explains further.)
Dvips tries to avoid overflowing the printer's memory by splitting the output files into "sections" (see the `-i' option in section Option details). Therefore, for all header files, Dvips debits the printer VM budget by some value. If the header file has, in its leading commentary a line of the form
%%VMusage: min max
then max is used. If there is no %%VMusage line, then
the size (in bytes) of the header file is used as an approximation.
Illustrations (figure files) are also checked for %%VMusage line.
You can include literal PostScript code in your document in several ways.
" special: Literal PostScript
For simple graphics, or just for experimentation, literal PostScript
code can be included. Simply use a \special beginning with a
double quote character `"'; there is no matching closing `"'.
For instance, the following (simple) graphic:
was created by typing:
\vbox to 100bp{\vss % a bp is the same as a PostScript unit
\special{" newpath 0 0 moveto 100 100 lineto 394 0 lineto
closepath gsave 0.8 setgray fill grestore stroke}}
You are responsible for leaving space for such literal graphics, as with
the \vbox above.
Generally, Dvips encloses specials in a PostScript save/restore pair, guaranteeing that the special will have no effect on the rest of the document. The `ps' special, however, allows you to insert literal PostScript instructions without this protective shield; you should understand what you're doing (and you shouldn't change the PostScript graphics state unless you are willing to take the consequences). This command can take many forms because it has had a torturous history; any of the following will work:
\special{ps:text}
\special{ps::text}
\special{ps::[begin]text}
\special{ps::[end]text}
(with longer forms taking precedence over shorter forms, when they are present). `ps::' and `ps::[end]' do no positioning, so they can be used to continue PostScript literals started with `ps:' or `ps::[begin]'.
\special{ps: plotfile filename}
inserts the contents of filename verbatim into the output (except for omitting lines that begin with %). An example of the proper use of literal specials can be found in the file `rotate.tex', which makes it easy to typeset text turned in multiples of 90 degrees.
\special
You can download literal PostScript header code in your TeX document,
for use with (for example) literal graphics code that you include later.
The text of a \special beginning with an `!' is copied into
the output file. A dictionary SDict will be current when this
code is executed; Dvips arranges for SDict to be first on the
dictionary stack when any PostScript graphic is included, whether
literally (the `"' special) or through macros (e.g.,
`epsf.tex').
For example:
\special{! /reset { 0 0 moveto} def}
Besides including literal PostScript at a particular place in your document (as described in the previous section), you can also arrange to execute arbitrary PostScript code at particular times while the PostScript is printing.
If any of the PostScript names bop-hook, eop-hook,
start-hook, or end-hook are defined in userdict,
they will be executed at the beginning of a page, end of a page, start
of the document, and end of a document, respectively.
When these macros are executed, the default PostScript coordinate system and origin is in effect. Such macros can be defined in headers added by the `-h' option or the `header=' special, and might be useful for writing, for instance, `DRAFT' across the entire page, or, with the aid of a shell script, dating the document. These macros are executed outside of the save/restore context of the individual pages, so it is possible for them to accumulate information, but if a document must be divided into sections because of memory constraints, such added information will be lost across section breaks.
The single argument to bop-hook is the physical page number; the
first page gets zero, the second one, etc. bop-hook must leave
this number on the stack. None of the other hooks are passed arguments.
As an example of what can be done, the following special will write a light grey `DRAFT' across each page in the document:
\special{!userdict begin /bop-hook{gsave 200 30 translate
65 rotate /Times-Roman findfont 216 scalefont setfont
0 0 moveto 0.7 setgray (DRAFT) show grestore}def end}
Using bop-hook or eop-hook to preserve information across
pages breaks compliance with the Adobe document structuring conventions,
so if you use any such tricks, you may also want to use the `-N'
option to turn off structured comments (such as `%%Page').
Otherwise, programs that read your file will assume its pages are
independent.
To finish off this section, the following examples of literal PostScript are presented without explanation:
\def\rotninety{\special{ps:currentpoint currentpoint translate 90
rotate neg exch neg exch translate}}\font\huge=cmbx10 at 14.4truept
\setbox0=\hbox to0pt{\huge A\hss}\vskip16truept\centerline{\copy0
\special{ps:gsave}\rotninety\copy0\rotninety\copy0\rotninety
\box0\special{ps:grestore}}\vskip16truept
\vbox to 2truein{\special{ps:gsave 0.3 setgray}\hrule height 2in
width\hsize\vskip-2in\special{ps:grestore}\font\big=cminch\big
\vss\special{ps:gsave 1 setgray}\vbox to 0pt{\vskip2pt
\line{\hss\hskip4pt NEAT\hss}\vss}\special{ps:0 setgray}%
\hbox{\raise2pt\line{\hss NEAT\hss}\special{ps:grestore}}\vss}
Some caveats are in order, however. Make sure that each gsave is
matched with a grestore on the same page. Do not use save
and restore; they can interact with the PostScript generated by
Dvips if care is not taken. Try to understand what the above macros are
doing before writing your own. The \rotninety macro especially
has a useful trick that appears again and again.
Dvips has support for producing hypertext PostScript documents. If you specify the `-z' option, the `html:' specials described below will be converted into `pdfmark' PostScript operators to specify links. Without `-z', `html:' specials are ignored.
The resulting PostScript can then be processed by a distiller program to make a PDF file. (It can still be handled by ordinary PostScript interpreters as well.) Various versions of both PC and Unix distillers are supported; Ghostscript includes limited distiller support (see section Ghostscript installation).
Macros you can use in your TeX document to insert the specials in the first place are available from `CTAN:/support/hypertex'. For CTAN info, see section `unixtex.ftp' in Kpathsea.
This hypertext support (and original form of the documentation) was written by Mark Doyle and Tanmoy Bhattacharya as the `dvihps' program. You can retrieve their software and additional documentation via the CTAN reference above. You may also be interested in the Java previewer IDVI, available at @url{http://www.win.tue.nl/~dickie/idvi}, and/or in @url{http://www.emrg.com/texpdf.html}, which describes the process of making PDF files from TeX files in more detail.
Mail archives for the original hyperTeX project are at @url{http://math.albany.edu:8800/hm/ht/}.
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, see section `unixtex.ftp' in Kpathsea) in:
fonts/postscript/bakoma fonts/postscript/paradissa
You may need to modify these fonts; see @url{http://xxx.lanl.gov/faq/bakoma.html}.
Also, the Adobe distillers prior to 2.1 drop trailing space characters
(character code 32) from strings. Unfortunately, the PostScript fonts
use this character code for characters other than space (notably the
Greek letter psi in the Symbol font), and so these characters are
dropped. This bug is fixed in version 2.1.
If you can't upgrade, One workaround is to change all the trailing
blanks in strings to a character code that isn't in the font. This works
because the default behavior is to substitute a blank for a missing
character, i.e., the distiller is fooled into substituting the right
character. For instance, with the Blue Sky fonts, you can globally
replace ` )' with `\200)' (with sed, for example) and
get the desired result. With the public domain fonts, you will probably
have to use a character code in the range 128 to 191 since these fonts
duplicate the first 32 characters starting at 192 to avoid MS-DOS
problems.
Current support for the World Wide Web in the TeX system does not involve modifying TeX itself. We need only define some specials; Arthur Smith (@email{apsmith@aps.org}), Tanmoy Bhattacharya, and Paul Ginsparg originally proposed and implemented the following:
html:<a href="xurl"> html:<a name="name"> html:</a> html:<img src="xurl"> html:<base href="xurl">
Like all TeX \special's, these produce no visible output, and
are uninterpreted by TeX itself. They are instructions to DVI
processors only.
Here, xurl is a standard WWW uniform resource locator (URL), possibly extended with a `#type.string' construct, where type is `page', `section', `equation', `reference' (for bibliographic references), `figure', `table', etc. For example,
\special{html:<a href="http://www.maths.tcd.ie/~tim/ch1.dvi#equation.1.1">}
is a link to equation (1.1) in an example document by Tim Murphy.
See @url{http://www.w3.org/hypertext/WWW/Addressing/Addressing.html} for a precise description of base URL's. (That itself is a URL, in case you were wondering.)
Descriptions of the \special's:
\special{html:<a href="http://www.tug.org/">}\TeX\ Users
Group\special{html:</a>}
The user will be able to click on the text `TeX Users
Group' while running Xdvi and get to the TUG home page. (By the way,
this is for illustration. In practice, you most likely want to use
macros to insert the \special commands; reference above.)
\special{html:<a name="#paradise">}Paradise\special{html:</a>}
is exactly where you are right now.
This will resolve an `href="paradise"'.
name targets.
Typically unnecessary, as the name of the DVI file being read is used by
default.
The `img' and `base' tags are not yet implemented in Dvips or the NeXTSTEP DVI viewer.
Dvips supports the use of PostScript fonts in TeX documents. To use a PostScript font conveniently, you need to prepare a corresponding virtual font; the program Afm2tfm, supplied with Dvips, helps with that.
All the necessary support for the standard 35 PostScript fonts (`AvantGarde-Book' through `ZapfDingbats'), plus other freely or commonly available PostScript fonts is available along with Dvips. To use these fonts, you need do nothing beyond what is mentioned in the installation procedure (see section Installation). This chapter is therefore relevant only if you are installing new PostScript fonts not supplied with Dvips. (Or if you're curious.)
The information needed to typeset using a particular font is contained in two files: a metric file that contains shape-independent information and a glyph file that contains the actual shapes of the font's characters. A virtual font is an optional additional file that can specify special ways to construct the characters. TeX itself (or LaTeX) look only at the metric file, but DVI drivers such as Dvips look at all three of these files.
An encoding file defines the correspondence between the code numbers of the characters in a font and their descriptive names. Two encoding files used together can describe a reencoding that rearranges, i.e., renumbers, the characters of a font.
A metric file describes properties of the font that are independent of what the characters actually look like. Aside from general information about the font itself, a metric file has two kinds of information: information about individual characters, organized by character code, and information about sequences of characters.
The per-character information specifies the width, height, depth, and italic correction of each character in the font. Any might be zero.
In addition to information on individual characters, the metric file specifies kerning, i.e., adding or removing space between particular character pairs. It further specifies ligature information: when a sequence of input characters should be typeset as a single (presumably different) "ligature" character. For example, it's traditional for the input `fi' to be typeset as `fi', not as `fi' (with the dot of the `i' colliding with `f'). (In English, the only common ligatures are fi, fl, ff, ffi, and ffl.)
Different typesetting systems use different metric file formats:
tftopl program (see section `tftopl invocation' in Web2c) that comes with TeX to transform a TFM
file into a human-readable "property list" (`.pl') file. You can
also edit a PL file and transform it back to a TeX-readable TFM with
the companion program pltotf (see section `pltotf invocation' in Web2c). Editing metrics by hand is not something you're likely to want
to do often, but the capability is there.
The Afm2tfm program distributed with Dvips converts an AFM file to a TFM file and performs other useful transformations as well. See section Invoking Afm2tfm.
Although a metric file (see the previous section) contains information about the spatial and other properties of the character at position 75, say, it contains nothing about what the character at position 75 actually looks like. The glyphs--the actual shapes of the letterforms in a font--are defined by other files, which we call glyph files. TeX itself only reads the TFM file for a font; it does not need to know character shapes.
A glyph file is a file that defines the shapes of the characters in a font. The shapes can be defined either by outlines or by bitmaps.
PostScript fonts are defined as outline fonts: Each character in the font is defined by giving the mathematical curves (lines, arcs, and splines) that define its contours. Different sizes of a character are generated by linearly scaling a single shape. For example, a 10-point `A' is simply half the size of a 20-point `A'. Nowadays, outline fonts usually also contain hints---additional information to improve the appearance of the font at small sizes or low resolutions.
Although various kinds of PostScript outline fonts exist, by far the most common, and the only one we will consider, is called Type 1. The glyph files for Postscript Type 1 fonts typically have names ending in `.pfa' ("printer font ASCII") or `.pfb' ("printer font binary").
In contrast, glyph files for Computer Modern and the other standard TeX fonts are bitmap fonts, generated from Metafont (`.mf') descriptions. The Metafont program distributed with TeX generates bitmaps from these descriptions.
The glyph files for TeX bitmap fonts are usually stored in packed font (PK) files. The names of these files end in `.nnnpk', where nnn is the resolution of the font in dots per inch. For example, `cmr10.600pk' contains the bitmaps for the `cmr10' font at a resolution of 600dpi. (On DOS filesystems, it's more likely `dpi600\cmr10.pk'.)
Metafont actually outputs generic font (GF) files, e.g.,
`cmr10.600gf', but the GF files are usually converted immediately
to PK format (using the gftopk utility that comes with TeX)
since PK files are smaller and contain the same information. (The GF
format is a historical artifact.)
A virtual font is constructed by extracting characters from one or more existing fonts and rearranging them, or synthesizing new characters in various ways. The explanation in this manual is intended to suffice for understanding enough about virtual fonts to use them with Dvips. It isn't a reference manual on virtual fonts. For more information: The primary document on virtual fonts is Donald E. Knuth, TUGboat 11(1), Apr. 1990, pp. 13--23, "Virtual Fonts: More Fun for Grand Wizards" (`CTAN:/info/virtual-fonts.knuth'; for CTAN info, see section `unixtex.ftp' in Kpathsea). (Don't be intimidated by the subtitle.)
A virtual font (`.vf') file specifies, for each character in the
virtual font, a recipe for typesetting that character. A VF file, like
a TFM file, is in a compressed binary format. The vftovp and
vptovf programs convert a VF file to a human-readable VPL
(virtual property list) format and back again. See section `vftovp invocation' in Web2c, and section `vptovf invocation' in Web2c.
In the case of a PostScript font f being used in a straightforward way, the recipe says: character i in the VF font is character j in font f. The font f is called a base font. For example, the VF file could remap the characters of the PostScript font to the positions where TeX expects to find them. See section Encodings.
Since TeX reads only TFM files, not VF's, each VF must have a
corresponding TFM for use with TeX. This corresponding TFM is
created when you run vptovf.
Every font, whatever its type, has an encoding, that specifies the correspondence between "logical" characters and character codes. For example, the ASCII encoding specifies that the character numbered 65 (decimal) is an uppercase `A'. The encoding does not specify what the character at that position looks like; there are lots of ways to draw an `A', and a glyph file (see section Glyph files) tells how. Nor does it specify how much space that character occupies; that information is in a metric file (see section Metric files).
TeX implicitly assumes a particular encoding for the fonts you use
with it. For example, the plain TeX macro \', which typesets
an acute accent over the following letter, assumes the acute accent is
at position 19 (decimal). This happens to be true of standard TeX
fonts such as Computer Modern, as you might expect, but it is not true
of normal PostScript fonts.
It's possible but painful to change all the macros that assume particular character positions. A better solution is to create a new font with the information for the acute accent at position 19, where TeX expects it to be. See section Making a PostScript font available.
PostScript represents encodings as a sequence of 256 character names called an encoding vector. An encoding file (`.enc') gives such a vector, together with ligature and kerning information (with which we are not concerned at the moment). These encoding files are used by the Afm2tfm program. Encoding files are also downloaded to the PostScript interpreter in your printer if you use one of them in place of the default encoding vector for a particular PostScript font.
Examples of encodings: the `dvips.enc' encoding file that comes with Dvips in the `reencode' directory is a good (but not perfect) approximation to the TeX encoding for TeX's Computer Modern text fonts. This is the encoding of the fonts that originated with Dvips, such as `ptmr.tfm'. The distribution includes many other encoding files; for example, `8r.enc', which is the base font for the current PostScript font distribution, and three corresponding to the TeX mathematics fonts: `texmext.enc' for math extensions, `texmital.enc' for math italics, and `texmsym.enc' for math symbols.
The output of Dvips is a program in the PostScript language that instructs your (presumably PostScript-capable) printer how to typeset your document by transforming it into toner on paper. Your printer, in turn, contains a PostScript interpreter that carries out the instructions in this typesetting program.
The program must include the definition of any PostScript fonts that you use in your document. Fonts built into your printer (probably the standard 35: `Times-Roman', `ZapfDingbats', ...) are defined within the interpreter itself. Other fonts must be downloaded as pfa or pfb files (see section Glyph files) from your host (the computer on which you're running Dvips).
You may be wondering exactly how a PostScript interpreter figures out what character to typeset, with this mass of metrics, glyphs, encodings, and other information. (If you're not wondering, skip this section ...)
The basic PostScript operator for imaging characters is
show. Suppose you've asked TeX to typeset an `S'. This will
eventually wind up in the Dvips output as the equivalent of this
PostScript operation:
(S) show
Here is how PostScript typesets the `S':
/S.
/S as a key in a dictionary named
CharStrings, another mandatory entry in a font dictionary.
S in CharStrings is the equivalent of a
series of standard PostScript commands like `curveto',
`lineto', `fill', and so on. These commands are executed to
draw the character. There can also be hint information that helps
adapt the character to low-resolution rasters. (See section Glyph files.)
The commands are actually represented in a more compact way than
standard PostScript source; see the Type 1 book for details.
This method for typesetting characters is used in both Level 1 and Level 2 PostScript. See the PostScript reference manuals for more information.
To make a PostScript font available in a TeX document, you need to install the font on your system and then define it within the document. Once you have installed the font, of course, it is available for any document thereafter and you don't need to reinstall it. You must have an AFM file for any font you install. Unless the font is built into your printer, you must also have a PFA or PFB file.
In the following examples, we use the font `Times-Roman' to illustrate the process. But you should use the prebuilt fonts for Times and the other standard fonts, rather than rebuilding them. The prebuilt fonts are made using a more complicated process than that described here, to make them work as well as possible with TeX. So following the steps in this manual will not generate files identical to the distributed ones. See section PostScript font installation, for pointers to the prebuilt fonts.
Installation of a PostScript font proceeds in three steps. See section Font concepts, for descriptions of the various files involved.
afm2tfm to create a TFM file for the original font,
and the VPL form of the virtual font.
vptovf to generate a VF and TFM file for the virtual font
from the VPL file.
The simplest invocation of Afm2tfm to make virtual fonts goes something like this:
afm2tfm Times-Roman -v ptmr rptmr
This reads the file `Times-Roman.afm', and produces two files as output, namely the virtual property list'file `ptmr.vpl', and the "raw" font metric file `rptmr.tfm'. To use the font in TeX, you first run
vptovf ptmr.vpl ptmr.vf ptmr.tfm
You should then install the virtual font file `ptmr.vf' where Dvips will see it and install `ptmr.tfm' and `rptmr.tfm' where TeX and Dvips will see them.
Using these raw fonts is not recommended; there are no raw fonts in the prebuilt PostScript fonts distributed along with Dvips. But nevertheless, that's how Afm2tfm presently operates, so that's what we document here. The `r' prefix convention is likewise historical accident.
You can also make more complex virtual fonts by editing `ptmr.vpl' before running `vptovf'; such editing might add the uppercase Greek characters in the standard TeX positions, for instance. (This has already been done for the prebuilt fonts.)
Once the files have been installed, you're all set. You can now do things like this in TeX:
\font\myfont = ptmr at 12pt \myfont Hello, I am being typeset in 12-point Times-Roman.
Thus, we have two fonts, one actual (`rptmr', which is analogous to the font in the printer) and one virtual (`ptmr', which has been remapped to the standard TeX encoding (almost)), and has typesetting know-how added. You could also say
\font\raw = rptmr at 10pt
and typeset directly with that, but then you would have no ligatures or kerning, and you would have to use Adobe character positions for special letters like The virtual font `ptmr' not only has ligatures and kerning, and most of the standard accent conventions of TeX, it also has a few additional features not present in the Computer Modern fonts. For example, it includes all the Adobe characters (such as the Polish ogonek and the French guillemots). The only things you lose from ordinary TeX text fonts are the dotless `j' (which can be hacked into the VPL file with literal PostScript specials if you have the patience) and uppercase Greek letters (which just don't exist unless you buy them separately). See section Reencoding with Afm2tfm.
As a final step you need to record information about both the virtual font and the original font (if you ever might want to use it) in the `psfonts.map' file (see section `psfonts.map': PostScript font catalog). For our example, you'd insert the following into `psfonts.map':
rptmr Times-Roman <ptmr8a.pfa
Of course, Times-Roman is already built in to most every
printer, so there's no need to download any Type 1 file for it. But if
you are actually following these instructions for new fonts, most likely
they are not built in to the printer.
These PostScript fonts can be scaled to any size. Go wild! Using PostScript fonts, however, does use up a great deal of the printer's memory and it does take time. You may find downloading bitmap fonts (possibly compressed, with the `Z' option) to be faster than using the built-in PostScript fonts.
The Afm2tfm program converts an AFM file for a PostScript font to a TFM file and a VPL file for a corresponding virtual font (or, in its simplest form, to a TFM file for the PostScript font itself). The results of the conversion are affected by the command-line options and especially by the reencodings you can specify with those options. You can also obtain special effects such as an oblique font.
An alternative to Afm2tfm for creating virtual fonts is Alan Jeffrey's
fontinst program, available from
`CTAN:fonts/utilities/fontinst' (for CTAN info,
see section `unixtex.ftp' in Kpathsea).
Afm2tfm allows you to specify a different encoding for a PostScript font (for a general introduction to encodings, see section Encodings). The `-t' options changes the TeX encoding, `-p' changes the PostScript encoding, and `-T' changes both simultaneously, as detailed in the sections below.
To build a virtual font with Afm2tfm, you specify the `-v' or `-V' option. You can then specify an encoding for that virtual font with `-t tex-enc'. (`-t' is ignored if neither `-v' nor `-V' is present.) Any ligature and kerning information you specify in tex-enc will be used in the VPL, in addition to the ligature and kerning information from the AFM file.
If the AFM file has no entry for a character specified in tex-enc, that character will be omitted from the output VPL.
The `-t' option is likely to be needed when you have a PostScript font corresponding to a TeX font other than a normal text font such as Computer Modern. For instance, if you have a PostScript font that contains math symbols, you'd probably want to use the encoding in the `texmsym.enc' file supplied with Dvips. (For a start; to actually get usable math fonts, you have to define much more than just an encoding.)
By default, Afm2tfm uses the encoding it finds in the AFM file. You can specify a different PostScript encoding with `-p ps-enc'. This makes the raw TFM file (the one output by Afm2tfm) have the encoding specified in the encoding file ps-enc. Any ligature or kern information specified in ps-enc is ignored by Afm2tfm, since ligkern info is always omitted from the raw TFM.
If you use this option, you must also arrange to download ps-enc as part of any document that uses this font. You do this by adding a line like the following one to `psfonts.map' (see section `psfonts.map': PostScript font catalog):
zpopr Optima "MyEncoding ReEncodeFont" <myenc.enc
Using `-p' is the only way to access characters in a PostScript font that are neither encoded in the AFM file nor constructed from other characters. For instance, Adobe's `Times-Roman' font contains the extra characters `trademark' and `registered' (among others); these can only be accessed through such a PostScript reencoding.
In fact, the `8r' base encoding used for the current PostScript font distribution (available at @url{ftp://ftp.tug.org/tex/psfonts.tar.gz}) does do this reencoding, for precisely this reason.
The option `-T enc-file' is equivalent to `-p enc-file -t enc-file'. If you make regular use of a private non-standard reencoding `-T' is usually a better idea than the individual options, to avoid unexpected inconsistencies in mapping otherwise. An example of when you might use this option is a dingbats font: when you have a TeX encoding that is designed to be used with a particular PostScript font.
The Afm2tfm program creates the TFM and VF files for the vi