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 called portrait.
Alternatively, a document might be designed for ledger or A3 paper. Since the intended paper size in these cases 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. It is hoped that this special will become standard over time for TeX previewers and other printer drivers. Some LaTeX packages, e. In this case, you need not and should not attempt to override it manually.
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.
If the -L0 command line option or L0 config file command is specified, the first special wins—this was the behavior of Dvips prior to the release. It has three possible parameters:. For example:. If both hsize and vsize are zero you must still specify units! 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.
The best match found from the paper size information in the configuration file is used. The dimensions must match within 5bp. If nothing matches, a warning is printed and the first paper size with zero dimensions is used; this should be the unknown paper size definition mentioned below, resulting in the actual dimensions being used. So paper size entries should typically specify both.
When using a paper size that is not already defined in config. This is useful with multi-page output that will be processed further. Notwithstanding the above, the default letter and a4 paper size definitions in config.
Not executing any page size definition at all confuses PostScript conversion programs such as ps2pdf , so we want to execute one if we can. The letterSize and A4Size paper size definitions are now synonyms for letter and a4. 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 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 :.
Dvips supports inclusion of PostScript figure files e. 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. If within the first few dozen lines there is a line like.
If the file contains instead a line like. Dvips needs it at the beginning. You can move it with that same text editor, or a simple script. This can usually find the correct bounding box automatically; it works best with Ghostscript.
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. 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 to import the graphic into a LaTeX document. For LaTeX2e, you can use the epsf, graphics or graphicx packages, but the last is recommended—it has the most flexible syntax, and is briefly described here.
If you are still using LaTeX 2. Depending on your system, a suitable driver setup may already be present, so that LaTeX automatically produces DVI files suitable for Dvips. 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:.
Now, save your changes and run LaTeX and Dvips; the output should have your graphic positioned at precisely the point you indicated, occupying the proper amount of space.
PostScript graphics have their origin in the lower left corner. Therefore, in TeX, a graphic will occupy a box that extends far above the line where it is put in, but has depth zero below it. For plain TeX, add a line like this near the top of your input file:. If you are using LaTeX 2. In any case, the above only needs to be done once, no matter how many figures you plan to include.
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 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:.
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. That is, put. 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. If you set both, both will be honored, but the aspect ratio of the included graphic may necessarily be distorted, i.
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:. 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. This downloads the PostScript file filename. Values are in big points, and may be fractional. Desired width and height of the resulting figure in the output, in tenths of big points to the inch ; may be fractional. If both rwi and rhi are nonzero, the picture is scaled, possibly losing aspect ratio. If only one of rwi and rhi is nonzero, the picture is scaled, preserving aspect ratio.
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. 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 the name of an included PostScript file ends with.
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. Of course, the command to be executed can be anything, including using a file conversion utility such as tek2ps or whatever is appropriate.
Schematically, this looks like:. The size at which you are using the font, in PostScript points TeX big points. The designsize of the font, again in PostScript points. This should match the value in the TFM file tfmname. The character code of the first character used from the font, specified as two ASCII hexadecimal characters, e. An arbitrary number of ASCII hexadecimal digits specifying which characters following and including hex-start are used.
This is treated as a bitmap. 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. These standard headers are the. If you want to peruse one of the standard header files, read the. In order to get a particular graphic file to work, a certain font or header file might need to be sent first.
For instance, to ensure that foo. 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. The header also special allows for specifying some additional code that should be inserted into the PostScript document before and after the file itself, as follows:. This will insert pre code just before foo. It is required to use the balanced braces in all of the arguments, including the header , when using this extended syntax.
This allows, for instance, dynamic headers, where some of the content depends on settings from the user in La TeX. Another application is the inclusion of graphics inside the PostScript header, so that they can be reused throughout the document, as with logs. That avoids including the same graphic several times. This extended syntax has one additional feature.
You can include headers when you run Dvips, as well as from your document see the previous section. See Configuration file commands. These files are called header. 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. Therefore, if your document uses very large fonts or very large included figures, Dvips might take it upon itself to split the output into unwanted sections.
For simple graphics, or just for experimentation, literal PostScript code can be included. This command can take many forms because it has had a torturous history; any of the following will work:. This feature may be used to include PostScript comments, for example. An example of the proper use of literal specials can be found in the file rotate. You can download literal PostScript header code in your TeX document, for use with for example literal graphics code that you include later.
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. The single argument to bop-hook is the physical page number; the first page gets zero, the second one, etc. None of the other hooks are passed arguments. 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:.
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. Dvips has support for producing hypertext PostScript documents.
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 Ghostscript installation. 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. The printout for a run should look something like this:. Your TeX distribution may make those fonts available in a separate optional package e. Failing that, commercial versions of the Computer Modern fonts are available from Blue Sky; public domain versions, in particular, the lm and cm-super font families, are available from CTAN and in TeX distributions.
The ps2pdf that comes with Ghostscript version 6. Current recommendations are GNU Ghostscript 6. Also, the Adobe distillers prior to 2.
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. This works because the default behavior is to substitute a blank for a missing character, i. With the public domain fonts, you will probably have to use a character code in the range to since these fonts duplicate the first 32 characters starting at to avoid MS-DOS problems.
Adobe seems not to offer the article any more, but copies are available elsewhere:. We need only define some specials; Arthur Smith apsmith aps. They are instructions to DVI processors only. For example,. By the way, this is for illustration. Links to an arbitrary external file. Interactively, a viewer is spawned to read the file according to the file extension and your mailcap file see the Xdvi documentation.
Defines a base URL that is prepended to all the name targets. Typically unnecessary, as the name of the DVI file being read is used by default. 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.
To use these fonts, you need do nothing beyond what is mentioned in the installation procedure see Installation. This chapter is therefore relevant only if you are installing new PostScript fonts not supplied with Dvips. A virtual font is an optional additional file that can specify special ways to construct the characters. 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. 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. In English, the only common ligatures are fi, fl, ff, ffi, and ffl. See 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. 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 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. For example, cmr Metafont actually outputs generic font GF files, e. 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.
For more information: The primary document on virtual fonts is Donald E. Knuth, TUGboat 11 1 , Apr. The vftovp and vptovf programs convert a VF file to a human-readable VPL virtual property list format and back again. See vftovp invocation in Web2c , and 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 Encodings. This corresponding TFM is created when you run vptovf. You can expand virtual fonts into their base fonts with DVIcopy see dvicopy invocation in Web2c.
This feature helps to reduce the size of Japanese virtual fonts. Nor does it specify how much space that character occupies; that information is in a metric file see Metric files. TeX implicitly assumes a particular encoding for the fonts you use with it. 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.
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 Making a font available. PostScript represents encodings as a sequence of character names called an encoding vector.
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. This is the encoding of the fonts that originated with Dvips, such as ptmr. The distribution includes many other encoding files; for example, 8r. To dvips, bitmapped fonts do not have any notion of linguistics; they are simply a vector of glyphs.
By comparison, PostScript fonts are required to contain an encoding vector that at least provides glyph names; these names can permit PostScript and PDF viewers to extract legible text from Postscript and PDF output. Unlike previous versions, dvips versions and later add glyph naming information to Type 3 bitmapped fonts if they can locate such information as an Encoding vector. This provides some support for search, for copy and paste, and even some limited support for accessibility. To do this, dvips must find encoding information for the bitmapped fonts.
It does this by first searching for a font-specific encoding file; for instance, for cmr10, it will search for dvips-cmr If it does not find such a file, it will search for a dvips-all.
The specific syntax of an encoding file is unspecified, except that it must be a PostScript fragment that leaves exactly one object on the operand stack.
This is different from the encoding files used to define encodings for PostScript fonts, described earlier. Normally that object is just an array of names; in this case, that array is used as the encoding vector for the font.
Alternatively, the object can be a procedure that, when executed, leaves a legal encoding vector on the stack. This second option is made available to support future enhancements that may add additional constructs to the font dictionary to enhance the interpretation of font characters.
The dvips-all. The format is just a sequence of font names, one per line, each terminated by a colon, followed by the encoding to use for those files. As part of its operation, to enable heuristics in PostScript and PDF viewers to properly identify word breaks and column gutters, dvips also generates a modified font bounding box and a modified font coordinate system. 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. 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. The basic PostScript operator for imaging characters is show. This will eventually wind up in the Dvips output as the equivalent of this PostScript operation:.
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. You must have an AFM file for any font you install. 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 PostScript font installation , for pointers to the prebuilt fonts.
Installation of a PostScript font proceeds in three steps. See Font concepts , for descriptions of the various files involved. This reads the file Times-Roman. To use the font in TeX, you first run. You should then install the virtual font file ptmr. Using these raw fonts is not recommended; there are no raw fonts in the prebuilt PostScript fonts distributed along with Dvips.
You can also make more complex virtual fonts by editing ptmr. This has already been done for the prebuilt fonts. You can now do things like this in TeX:. You could also say. For example, it includes all the Adobe characters such as the Polish ogonek and the French guillemots. See 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.
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! Next: psfonts. 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. Afm2tfm allows you to specify a different encoding for a PostScript font for a general introduction to encodings, see Encodings.
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.
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.
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. 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.
Afm2tfm generates these files from two encodings: one for TeX and one for PostScript. The TeX encoding is used to map character numbers to character names while the PostScript encoding is used to map each character name to a possibly different number. In combination, you can get access to any character of a PostScript font at any position for TeX typesetting.
In the default case, when you specify none of the -t , -p , or -T options, Afm2tfm uses a default TeX encoding which mostly corresponds to the Computer Modern text fonts and the PostScript encoding found in the AFM file being read. The reencoding is also sometimes called a remapping. The PostScript encoding works in reverse, by looking in the encoding vector for the name and then yielding the corresponding number.
The combined mapping of 19 to shows up explicitly in the VF file and also implicitly in the fact that the properties of PostScript character appear in position 19 of the TFM file for the virtual font. The default encoding of the distributed fonts e.
These definitions will not work with the Computer Modern fonts for the relevant accents. They are already part of the distributed psfonts. Here is a skeletal example:. These encoding files are downloaded as part of changing the encoding at the PostScript level see the previous section. Then there must be a matching right bracket ]. All names are case-sensitive.
Any ligature or kern information is given as a comment. This ligature and kern information is given in groups of words: each group is terminated by a space and a semicolon and unless the semicolon is at the end of a line another space. To specify a ligature, specify the names of the pair of characters, followed by the ligature operation as in Metafont , followed by the replacing character name. This works just like in Metafont.
Besides the reencodings described in the previous section, Afm2tfm can do other manipulations. You can also create a small caps font with a command such as. This will generate a set of pseudo-small caps mapped into the usual lowercase positions and scaled down to 0.
You can also specify the scaling as something other than the default 0. It is unfortunately not possible to increase the width of the small caps independently of the rest of the font. If you want a really professional looking set of small caps, you need to acquire a small caps font. Afm2tfm writes to standard output the line you need to add to psfonts. The TFM file thus created is raw because it omits ligature and kern information, and does no character remapping; it contains only the character information in the AFM file in TFM format, which is the form that TeX understands.
For text fonts, this means printable ASCII characters will work ok, but little else, because standard PostScript fonts have a different encoding scheme than the one that plain TeX expects see Encodings. Although the encodings agree for most printable ASCII characters, other characters such as ligatures and accents vary.
Until Afm2tfm 8. See Changing PostScript encodings. Slant characters to the right by slant. If slant is negative, the letters slope to the left or they might be upright if you start with an italic font. Use tex-enc for the target TeX encoding of the font. Ligature and kern information may also be specified in file. Use ps-tex-enc for both the PostScript and target TeX encodings of the font. Use only those characters specified in the TeX encoding, and no others.
By default, Afm2tfm tries to include all characters in the input font, even those not present in the TeX encoding it puts them into otherwise-unused positions, arbitrarily.
This font handles accented letters and retains proper kerning. The psfonts. Each line has the format:. See Special font effects , for a complete list of font effects. This allows you access to characters that may be present in the Type 1 font file, but not encoded by default—most of the preaccented characters, for example.
An example:. For more details, see the 8r. You may notice that the same syntax is used for downloading encoding vectors and Type 1 font files. Similarly, the name of the Type 1 font file itself must have extension. In addition, Dvips scans the font to determine its memory usage, just as it does for other header files see Header files.
See Option details. Adobe Multiple Master fonts, such as Minion, cannot be partially downloaded. Dvips supports one-pass multi-color printing of TeX documents on any color PostScript device. To access these macros simply add to the top of your plain TeX file the command:.
For LaTeX2e, these examples are not applicable. These macros provide two basic kinds of color macros: ones for local color changes a few words, a single symbol and one for global color changes the whole document. All the color names use a mixed case scheme to avoid conflicts with other macros. There are 68 predefined colors, with names taken primarily from the Crayola crayon box of 64 colors, and one pair of macros for the user to set his own color pattern see User-definable colors.
The comments in this file also show a rough correspondence between the crayon names and Pantones. Nonetheless, this option works well for creating small EPSF files for equations or tables or the like. Note, of course, that dvips output is resolution dependent and thus does not make very good EPSF files, especially if the images are to be scaled; use these EPSF files with a great deal of care.
Run as a filter. Read the. The standard input must be seekable, so it cannot be a pipe. If you must use a pipe, write a shell script that copies the pipe output to a temporary file and then points dvips at this file.
This option also disables the automatic reading of the PRINTER environment variable, and 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 this option if you want both. This is useful when dvips is driving the printer directly instead of working through a spooler, as is common on extremely small systems.
Causes dvips to shift non-printing characters to higher-numbered positions. This may be useful sometimes. Prepend file name as an additional header file. This header file gets added to the PostScript userdict. Make each section be a separate file. Using this option tells dvips to place each section into a separate file; the new file names are created replacing the suffix of the supplied output file name by a three-digit sequence number.
This option is most often used in conjunction with the -S option which sets the maximum section length in pages. For instance, some phototypesetters cannot print more than ten or so consecutive pages before running out of steam; these options can be used to automatically split a book into ten-page sections, each to its own file. Download only needed characters from Type 1 fonts. This is the default in the current release. Some debugging flags trace this operation. You can also control partial downloading on a per-font basis, via the psfonts.
Print crop marks. This option increases the paper size which should be specified, either with a paper size special or with the -T option by a half inch in each dimension. It translates each page by a quarter inch and draws cross-style crop marks. It is mostly useful with typesetters that can set the page size automatically. This option causes comments in included PostScript graphics, font files, and headers to be removed. This is sometimes necessary to get around bugs in spoolers or PostScript post-processing programs.
Use of this flag can cause some included graphics to fail, since the PostScript header macros from some software packages read portions of the input stream line by line, searching for a particular comment. This option has been turned off by default because PostScript previewers and spoolers have been getting better. The last page printed will be the first one numbered num Default is the last page in the document.
Use mode as the Metafont device name for path searching and font generation. This overrides any value from configuration files. With the default paths, explicitly specifying the mode also makes the program assume the fonts are in a subdirectory named mode. Turns off the automatic font generation facility. If any fonts are missing, commands to generate the fonts are appended to the file missfont. Turns off structured comments; this might be necessary on some systems that try to interpret PostScript comments in weird ways, or on some PostScript printers.
This will disable the use of Omega extensions when interpreting DVI files. By default, the additional opcodes and are recognized by dvips as Omega or pTeX extensions and interpreted as requests to set 2-byte characters. By default, the additional opcodes and are recognized by dvips as pTeX extensions and interpreted as requests to set 3-byte characters, and as request to change the typesetting direction. The only drawback is that the virtual font array will at least temporarily require or more positions instead of the default positions, i.
If you find this unacceptable or encounter another problem with the Omega or pTeX extensions, you can switch off the pTeX extension by using -noptex , or both by using -noomega but please do send a bug report if you find such problems - see the bug address in the AUTHORS section below. The output will be sent to file name If no file name is given i.
If the first character of the supplied output file name is an exclamation mark, then the remainder will be used as an argument to popen ; thus, specifying! Move the origin by a certain amount. The offset is a comma-separated pair of dimensions, such as. The origin of the page is shifted from the default position of one inch down, one inch to the right from the upper left corner of the paper by this amount. The first page printed will be the first one numbered num.
Default is the first page in the document. Pages not specified will not be printed. Multiple -pp options may be specified or all pages and page ranges can be specified with one -pp option. Sets up the output for the appropriate printer. This is implemented by reading in config. Note that config. If that variable exists, and a corresponding configuration file exists, that configuration file is read in.
Run in quiet mode. Don't chatter about pages converted, etc. Run securely. The config file option is z. This causes the file to not be truly conformant, and is thus not recommended, but is useful if you are driving the printer directly and don't care too much about the portability of the output. This option is most commonly used with the -i option; see that documentation above for more information.
0コメント