+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+N\bNA\bAM\bME\bE
+ grops - PostScript driver for groff
+
+S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
+ g\bgr\bro\bop\bps\bs [ -\b-g\bgl\blv\bv ] [ -\b-b\bb_\bn ] [ -\b-c\bc_\bn ] [ -\b-w\bw_\bn ] [ -\b-F\bF_\bd_\bi_\br ] [
+ _\bf_\bi_\bl_\be_\bs... ]
+
+D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
+ g\bgr\bro\bop\bps\bs translates the output of GNU t\btr\bro\bof\bff\bf to PostScript.
+ Normally g\bgr\bro\bop\bps\bs should be invoked by using the groff com-
+ mand with a -\b-T\bTp\bps\bs option. (Actually, this is the default
+ for groff.) If no files are given, g\bgr\bro\bop\bps\bs will read the
+ standard input. A filename of -\b- will also cause g\bgr\bro\bop\bps\bs to
+ read the standard input. PostScript output is written to
+ the standard output. When g\bgr\bro\bop\bps\bs is run by g\bgr\bro\bof\bff\bf options
+ can be passed to g\bgr\bro\bop\bps\bs using the g\bgr\bro\bof\bff\bf -\b-P\bP option.
+
+O\bOP\bPT\bTI\bIO\bON\bNS\bS
+ -\b-b\bb_\bn Workaround broken spoolers and previewers. Nor-
+ mally g\bgr\bro\bop\bps\bs produces output that conforms the Docu-
+ ment Structuring Conventions version 3.0. Unfortu-
+ nately some spoolers and previewers can't handle
+ such output. The value of _\bn controls what g\bgr\bro\bop\bps\bs
+ does to its output acceptable to such programs. A
+ value of 0 will cause grops not to employ any
+ workarounds. Add 1 if no %\b%%\b%B\bBe\beg\bgi\bin\bnD\bDo\boc\bcu\bum\bme\ben\bnt\btS\bSe\bet\btu\bup\bp and
+ %\b%%\b%E\bEn\bnd\bdD\bDo\boc\bcu\bum\bme\ben\bnt\btS\bSe\bet\btu\bup\bp comments should be generated;
+ this is needed for early versions of TranScript
+ that get confused by anything between the %\b%%\b%E\bEn\bnd\bdP\bPr\bro\bo-\b-
+ l\blo\bog\bg comment and the first %\b%%\b%P\bPa\bag\bge\be comment. Add 2 if
+ lines in included files beginning with %\b%!\b! should
+ be stripped out; this is needed for Sun's pageview
+ previewer. Add 4 if %\b%%\b%P\bPa\bag\bge\be, %\b%%\b%T\bTr\bra\bai\bil\ble\ber\br and %\b%%\b%E\bEn\bnd\bd-\b-
+ P\bPr\bro\bol\blo\bog\bg comments should be stripped out of included
+ files; this is needed for spoolers that don't
+ understand the %\b%%\b%B\bBe\beg\bgi\bin\bnD\bDo\boc\bcu\bum\bme\ben\bnt\bt and %\b%%\b%E\bEn\bnd\bdD\bDo\boc\bcu\bum\bme\ben\bnt\bt
+ comments. Add 8 if the first line of the
+ PostScript output should be %\b%!\b!P\bPS\bS-\b-A\bAd\bdo\bob\bbe\be-\b-2\b2.\b.0\b0 rather
+ than %\b%!\b!P\bPS\bS-\b-A\bAd\bdo\bob\bbe\be-\b-3\b3.\b.0\b0; this is needed when using
+ Sun's Newsprint with a printer that requires page
+ reversal. The default value can be specified by a
+
+ b\bbr\bro\bok\bke\ben\bn _\bn
+
+ command in the DESC file. Otherwise the default
+ value is 0.
+
+ -\b-c\bc_\bn Print _\bn copies of each page.
+
+ -\b-g\bg Guess the page length. This generates PostScript
+ code that guesses the page length. The guess will
+
+
+
+Groff Version 1.08 30 December 1993 1
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ be correct only if the imageable area is vertically
+ centered on the page. This option allows you to
+ generate documents that can be printed both on let-
+ ter (8.5x11) paper and on A4 paper without change.
+
+ -\b-l\bl Print the document in landscape format.
+
+ -\b-F\bF_\bd_\bi_\br Search the directory _\bd_\bi_\br/\b/d\bde\bev\bv_\bn_\ba_\bm_\be for font and
+ device description files; _\bn_\ba_\bm_\be is the name of the
+ device, usually p\bps\bs.
+
+ -\b-w\bw_\bn Lines should be drawn using a thickness of _\bn thou-
+ sandths of an em.
+
+ -\b-v\bv Print the version number.
+
+U\bUS\bSA\bAG\bGE\bE
+ There are styles called R\bR, I\bI, B\bB, and B\bBI\bI mounted at font
+ positions 1 to 4. The fonts are grouped into families A\bA,
+ B\bBM\bM, C\bC, H\bH, H\bHN\bN, N\bN, P\bP and T\bT having members in each of these
+ styles:
+
+ A\bAR\bR AvantGarde-Book
+
+ A\bAI\bI AvantGarde-BookOblique
+
+ A\bAB\bB AvantGarde-Demi
+
+ A\bAB\bBI\bI AvantGarde-DemiOblique
+
+ B\bBM\bMR\bR Bookman-Light
+
+ B\bBM\bMI\bI Bookman-LightItalic
+
+ B\bBM\bMB\bB Bookman-Demi
+
+ B\bBM\bMB\bBI\bI Bookman-DemiItalic
+
+ C\bCR\bR Courier
+
+ C\bCI\bI Courier-Oblique
+
+ C\bCB\bB Courier-Bold
+
+ C\bCB\bBI\bI Courier-BoldOblique
+
+ H\bHR\bR Helvetica
+
+ H\bHI\bI Helvetica-Oblique
+
+ H\bHB\bB Helvetica-Bold
+
+
+
+Groff Version 1.08 30 December 1993 2
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ H\bHB\bBI\bI Helvetica-BoldOblique
+
+ H\bHN\bNR\bR Helvetica-Narrow
+
+ H\bHN\bNI\bI Helvetica-Narrow-Oblique
+
+ H\bHN\bNB\bB Helvetica-Narrow-Bold
+
+ H\bHN\bNB\bBI\bI Helvetica-Narrow-BoldOblique
+
+ N\bNR\bR NewCenturySchlbk-Roman
+
+ N\bNI\bI NewCenturySchlbk-Italic
+
+ N\bNB\bB NewCenturySchlbk-Bold
+
+ N\bNB\bBI\bI NewCenturySchlbk-BoldItalic
+
+ P\bPR\bR Palatino-Roman
+
+ P\bPI\bI Palatino-Italic
+
+ P\bPB\bB Palatino-Bold
+
+ P\bPB\bBI\bI Palatino-BoldItalic
+
+ T\bTR\bR Times-Roman
+
+ T\bTI\bI Times-Italic
+
+ T\bTB\bB Times-Bold
+
+ T\bTB\bBI\bI Times-BoldItalic
+
+ There is also the following font which is not a member of
+ a family:
+
+ Z\bZC\bCM\bMI\bI ZapfChancery-MediumItalic
+
+ There are also some special fonts called S\bSS\bS and S\bS. Zapf
+ Dingbats is available as Z\bZD\bD and a reversed version of
+ ZapfDingbats (with symbols pointing in the opposite direc-
+ tion) is available as Z\bZD\bDR\bR; most characters in these fonts
+ are unnamed and must be accessed using \\b\N\bN.
+
+ g\bgr\bro\bop\bps\bs understands various X commands produced using the \\b\X\bX
+ escape sequence; g\bgr\bro\bop\bps\bs will only interpret commands that
+ begin with a p\bps\bs:\b: tag.
+
+ \\b\X\bX'\b'p\bps\bs:\b: e\bex\bxe\bec\bc _\bc_\bo_\bd_\be'\b'
+ This executes the arbitrary PostScript commands in
+
+
+
+Groff Version 1.08 30 December 1993 3
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ _\bc_\bo_\bd_\be. The PostScript currentpoint will be set to
+ the position of the \\b\X\bX command before executing
+ _\bc_\bo_\bd_\be. The origin will be at the top left corner of
+ the page, and y coordinates will increase down the
+ page. A procedure u\bu will be defined that converts
+ groff units to the coordinate system in effect.
+ For example,
+
+ .\b.n\bnr\br x\bx 1\b1i\bi
+ \\b\X\bX'\b'p\bps\bs:\b: e\bex\bxe\bec\bc \\b\n\bnx\bx u\bu 0\b0 r\brl\bli\bin\bne\bet\bto\bo s\bst\btr\bro\bok\bke\be'\b'
+
+ will draw a horizontal line one inch long. _\bc_\bo_\bd_\be
+ may make changes to the graphics state, but any
+ changes will persist only to the end of the page.
+ Any definitions will also persist only until the
+ end of the page. If you use the \\b\Y\bY escape sequence
+ with an argument that names a macro, _\bc_\bo_\bd_\be can
+ extend over multiple lines. For example,
+
+ .\b.n\bnr\br x\bx 1\b1i\bi
+ .\b.d\bde\be y\by
+ p\bps\bs:\b: e\bex\bxe\bec\bc
+ \\b\n\bnx\bx u\bu 0\b0 r\brl\bli\bin\bne\bet\bto\bo
+ s\bst\btr\bro\bok\bke\be
+ .\b..\b.
+ \\b\Y\bYy\by
+
+ is another way to draw a horizontal line one inch
+ long.
+
+ \\b\X\bX'\b'p\bps\bs:\b: f\bfi\bil\ble\be _\bn_\ba_\bm_\be'\b'
+ This is the same as the e\bex\bxe\bec\bc command except that
+ the PostScript code is read from file _\bn_\ba_\bm_\be.
+
+ \\b\X\bX'\b'p\bps\bs:\b: d\bde\bef\bf _\bc_\bo_\bd_\be'\b'
+ Place a PostScript definition contained in _\bc_\bo_\bd_\be in
+ the prologue. There should be at most one defini-
+ tion per \\b\X\bX command. Long definitions can be split
+ over several \\b\X\bX commands; all the _\bc_\bo_\bd_\be arguments
+ are simply joined together separated by newlines.
+ The definitions are placed in a dictionary which is
+ automatically pushed on the dictionary stack when
+ an e\bex\bxe\bec\bc command is executed. If you use the \\b\Y\bY
+ escape sequence with an argument that names a
+ macro, _\bc_\bo_\bd_\be can extend over multiple lines.
+
+ \\b\X\bX'\b'p\bps\bs:\b: m\bmd\bde\bef\bf _\bn _\bc_\bo_\bd_\be'\b'
+ Like d\bde\bef\bf, except that _\bc_\bo_\bd_\be may contain up to _\bn def-
+ initions. g\bgr\bro\bop\bps\bs needs to know how many definitions
+ _\bc_\bo_\bd_\be contains so that it can create an appropri-
+ ately sized PostScript dictionary to contain them.
+
+
+
+Groff Version 1.08 30 December 1993 4
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ \\b\X\bX'\b'p\bps\bs:\b: i\bim\bmp\bpo\bor\brt\bt _\bf_\bi_\bl_\be _\bl_\bl_\bx _\bl_\bl_\by _\bu_\br_\bx _\bu_\br_\by _\bw_\bi_\bd_\bt_\bh [ _\bh_\be_\bi_\bg_\bh_\bt ]'\b'
+ Import a PostScript graphic from _\bf_\bi_\bl_\be. The argu-
+ ments _\bl_\bl_\bx, _\bl_\bl_\by, _\bu_\br_\bx, and _\bu_\br_\by give the bounding box
+ of the graphic in the default PostScript coordinate
+ system; they should all be integers; _\bl_\bl_\bx and _\bl_\bl_\by
+ are the x and y coordinates of the lower left cor-
+ ner of the graphic; _\bu_\br_\bx and _\bu_\br_\by are the x and y
+ coordinates of the upper right corner of the
+ graphic; _\bw_\bi_\bd_\bt_\bh and _\bh_\be_\bi_\bg_\bh_\bt are integers that give
+ the desired width and height in groff units of the
+ graphic. The graphic will be scaled so that it has
+ this width and height and translated so that the
+ lower left corner of the graphic is located at the
+ position associated with \\b\X\bX command. If the height
+ argument is omitted it will be scaled uniformly in
+ the x and y directions so that it has the specified
+ width. Note that the contents of the \\b\X\bX command
+ are not interpreted by t\btr\bro\bof\bff\bf; so vertical space for
+ the graphic is not automatically added, and the
+ _\bw_\bi_\bd_\bt_\bh and _\bh_\be_\bi_\bg_\bh_\bt arguments are not allowed to have
+ attached scaling indicators. If the PostScript
+ file complies with the Adobe Document Structuring
+ Conventions and contains a %\b%%\b%B\bBo\bou\bun\bnd\bdi\bin\bng\bgB\bBo\box\bx comment,
+ then the bounding box can be automatically
+ extracted from within groff by using the s\bsy\by request
+ to run the p\bps\bsb\bbb\bb command.
+
+ The -\b-m\bmp\bps\bs macros (which are automatically loaded
+ when g\bgr\bro\bop\bps\bs is run by the groff command) include a
+ P\bPS\bSP\bPI\bIC\bC macro which allows a picture to be easily
+ imported. This has the format
+
+ .\b.P\bPS\bSP\bPI\bIC\bC _\bf_\bi_\bl_\be [_\bw_\bi_\bd_\bt_\bh [_\bh_\be_\bi_\bg_\bh_\bt]]
+
+ _\bf_\bi_\bl_\be is the name of the file containing the illus-
+ tration; _\bw_\bi_\bd_\bt_\bh and _\bh_\be_\bi_\bg_\bh_\bt give the desired width
+ and height of the graphic. The _\bw_\bi_\bd_\bt_\bh and _\bh_\be_\bi_\bg_\bh_\bt
+ arguments may have scaling indicators attached; the
+ default scaling indicator is i\bi. This macro will
+ scale the graphic uniformly in the x and y direc-
+ tions so that it is no more than _\bw_\bi_\bd_\bt_\bh wide and
+ _\bh_\be_\bi_\bg_\bh_\bt high.
+
+ \\b\X\bX'\b'p\bps\bs:\b: i\bin\bnv\bvi\bis\bs'\b'
+ \\b\X\bX'\b'p\bps\bs:\b: e\ben\bnd\bdi\bin\bnv\bvi\bis\bs'\b'
+ No output will be generated for text and drawing
+ commands that are bracketed with these \\b\X\bX commands.
+ These commands are intended for use when output
+ from t\btr\bro\bof\bff\bf will be previewed before being processed
+ with g\bgr\bro\bop\bps\bs; if the previewer is unable to display
+ certain characters or other constructs, then other
+
+
+
+Groff Version 1.08 30 December 1993 5
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ substitute characters or constructs can be used for
+ previewing by bracketing them with these \\b\X\bX com-
+ mands.
+
+ For example, g\bgx\bxd\bdi\bit\btv\bvi\bie\bew\bw is not able to display a
+ proper \\b\(\b(e\bem\bm character because the standard X11
+ fonts do not provide it; this problem can be over-
+ come by executing the following request
+
+ .\b.c\bch\bha\bar\br \\b\(\b(e\bem\bm \\b\X\bX'\b'p\bps\bs:\b: i\bin\bnv\bvi\bis\bs'\b'\\b\
+ \\b\Z\bZ'\b'\\b\v\bv'\b'-\b-.\b.2\b25\b5m\bm'\b'\\b\h\bh'\b'.\b.0\b05\b5m\bm'\b'\\b\D\bD'\b'l\bl .\b.9\b9m\bm 0\b0'\b'\\b\h\bh'\b'.\b.0\b05\b5m\bm'\b''\b'\\b\
+ \\b\X\bX'\b'p\bps\bs:\b: e\ben\bnd\bdi\bin\bnv\bvi\bis\bs'\b'\\b\(\b(e\bem\bm
+
+ In this case, g\bgx\bxd\bdi\bit\btv\bvi\bie\bew\bw will be unable to display
+ the \\b\(\b(e\bem\bm character and will draw the line, whereas
+ g\bgr\bro\bop\bps\bs will print the \\b\(\b(e\bem\bm character and ignore the
+ line.
+
+ The input to g\bgr\bro\bop\bps\bs must be in the format output by
+ t\btr\bro\bof\bff\bf(1). This is described in g\bgr\bro\bof\bff\bf_\b_o\bou\but\bt(1). In addition
+ the device and font description files for the device used
+ must meet certain requirements. The device and font
+ description files supplied for p\bps\bs device meet all these
+ requirements. a\baf\bfm\bmt\bto\bod\bdi\bit\bt(1) can be used to create font
+ files from AFM files. The resolution must be an integer
+ multiple of 72 times the s\bsi\biz\bze\bes\bsc\bca\bal\ble\be. The p\bps\bs device uses a
+ resolution of 72000 and a sizescale of 1000. The device
+ description file should contain a command
+
+ p\bpa\bap\bpe\ber\brl\ble\ben\bng\bgt\bth\bh _\bn
+
+ which says that output should be generated which is suit-
+ able for printing on a page whose length is _\bn machine
+ units. Each font description file must contain a command
+
+ i\bin\bnt\bte\ber\brn\bna\bal\bln\bna\bam\bme\be _\bp_\bs_\bn_\ba_\bm_\be
+
+ which says that the PostScript name of the font is _\bp_\bs_\bn_\ba_\bm_\be.
+ It may also contain a command
+
+ e\ben\bnc\bco\bod\bdi\bin\bng\bg _\be_\bn_\bc_\b__\bf_\bi_\bl_\be
+
+ which says that the PostScript font should be reencoded
+ using the encoding described in _\be_\bn_\bc_\b__\bf_\bi_\bl_\be; this file should
+ consist of a sequence of lines of the form:
+
+ _\bp_\bs_\bc_\bh_\ba_\br _\bc_\bo_\bd_\be
+
+ where _\bp_\bs_\bc_\bh_\ba_\br is the PostScript name of the character, and
+ _\bc_\bo_\bd_\be is its position in the encoding expressed as a deci-
+ mal integer. The code for each character given in the
+
+
+
+Groff Version 1.08 30 December 1993 6
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ font file must correspond to the code for the character in
+ encoding file, or to the code in the default encoding for
+ the font if the PostScript font is not to be reencoded.
+ This code can be used with the \\b\N\bN escape sequence in t\btr\bro\bof\bff\bf
+ to select the character, even if the character does not
+ have a groff name. Every character in the font file must
+ exist in the PostScript font, and the widths given in the
+ font file must match the widths used in the PostScript
+ font. g\bgr\bro\bop\bps\bs will assume that a character with a groff
+ name of s\bsp\bpa\bac\bce\be is blank (makes no marks on the page); it
+ can make use of such a character to generate more effi-
+ cient and compact PostScript output.
+
+ g\bgr\bro\bop\bps\bs can automatically include the downloadable fonts
+ necessary to print the document. Any downloadable fonts
+ which should, when required, be included by g\bgr\bro\bop\bps\bs must be
+ listed in the file /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt/\b/d\bde\bev\bvp\bps\bs/\b/d\bdo\bow\bwn\bnl\blo\boa\bad\bd;
+ this should consist of lines of the form
+
+ _\bf_\bo_\bn_\bt _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+
+ where _\bf_\bo_\bn_\bt is the PostScript name of the font, and _\bf_\bi_\bl_\be_\b-
+ _\bn_\ba_\bm_\be is the name of the file containing the font; lines
+ beginning with #\b# and blank lines are ignored; fields may
+ be separated by tabs or spaces; _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be will be searched
+ for using the same mechanism that is used for groff font
+ metric files. The d\bdo\bow\bwn\bnl\blo\boa\bad\bd file itself will also be
+ searched for using this mechanism.
+
+ If the file containing a downloadable font or imported
+ document conforms to the Adobe Document Structuring Con-
+ ventions, then g\bgr\bro\bop\bps\bs will interpret any comments in the
+ files sufficiently to ensure that its own output is con-
+ forming. It will also supply any needed font resources
+ that are listed in the d\bdo\bow\bwn\bnl\blo\boa\bad\bd file as well as any needed
+ file resources. It is also able to handle inter-resource
+ dependencies. For example, suppose that you have a down-
+ loadable font called Garamond, and also a downloadable
+ font called Garamond-Outline which depends on Garamond
+ (typically it would be defined to copy Garamond's font
+ dictionary, and change the PaintType), then it is neces-
+ sary for Garamond to appear before Garamond-Outline in the
+ PostScript document. g\bgr\bro\bop\bps\bs will handle this automatically
+ provided that the downloadable font file for Garamond-
+ Outline indicates its dependence on Garamond by means of
+ the Document Structuring Conventions, for example by
+ beginning with the following lines
+
+ %\b%!\b!P\bPS\bS-\b-A\bAd\bdo\bob\bbe\be-\b-3\b3.\b.0\b0 R\bRe\bes\bso\bou\bur\brc\bce\be-\b-F\bFo\bon\bnt\bt
+ %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btN\bNe\bee\bed\bde\bed\bdR\bRe\bes\bso\bou\bur\brc\bce\bes\bs:\b: f\bfo\bon\bnt\bt G\bGa\bar\bra\bam\bmo\bon\bnd\bd
+ %\b%%\b%E\bEn\bnd\bdC\bCo\bom\bmm\bme\ben\bnt\bts\bs
+
+
+
+Groff Version 1.08 30 December 1993 7
+
+
+
+
+
+
+
+
+GROPS(1) BSD Reference Manual GROPS(1)
+
+
+ %\b%%\b%I\bIn\bnc\bcl\blu\bud\bde\beR\bRe\bes\bso\bou\bur\brc\bce\be:\b: f\bfo\bon\bnt\bt G\bGa\bar\bra\bam\bmo\bon\bnd\bd
+
+ In this case both Garamond and Garamond-Outline would need
+ to be listed in the d\bdo\bow\bwn\bnl\blo\boa\bad\bd file. A downloadable font
+ should not include its own name in a %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btS\bSu\bup\bp-\b-
+ p\bpl\bli\bie\bed\bdR\bRe\bes\bso\bou\bur\brc\bce\bes\bs comment.
+
+ g\bgr\bro\bop\bps\bs will not interpret %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btF\bFo\bon\bnt\bts\bs comments. The
+ %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btN\bNe\bee\bed\bde\bed\bdR\bRe\bes\bso\bou\bur\brc\bce\bes\bs, %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btS\bSu\bup\bpp\bpl\bli\bie\bed\bdR\bRe\bes\bso\bou\bur\brc\bce\bes\bs,
+ %\b%%\b%I\bIn\bnc\bcl\blu\bud\bde\beR\bRe\bes\bso\bou\bur\brc\bce\be, %\b%%\b%B\bBe\beg\bgi\bin\bnR\bRe\bes\bso\bou\bur\brc\bce\be and %\b%%\b%E\bEn\bnd\bdR\bRe\bes\bso\bou\bur\brc\bce\be com-
+ ments (or possibly the old %\b%%\b%D\bDo\boc\bcu\bum\bme\ben\bnt\btN\bNe\bee\bed\bde\bed\bdF\bFo\bon\bnt\bts\bs, %\b%%\b%D\bDo\boc\bcu\bu-\b-
+ m\bme\ben\bnt\btS\bSu\bup\bpp\bpl\bli\bie\bed\bdF\bFo\bon\bnt\bts\bs, %\b%%\b%I\bIn\bnc\bcl\blu\bud\bde\beF\bFo\bon\bnt\bt, %\b%%\b%B\bBe\beg\bgi\bin\bnF\bFo\bon\bnt\bt and %\b%%\b%E\bEn\bnd\bd-\b-
+ F\bFo\bon\bnt\bt comments) should be used.
+
+F\bFI\bIL\bLE\bES\bS
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt/\b/d\bde\bev\bvp\bps\bs/\b/D\bDE\bES\bSC\bC
+ Device description file.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt/\b/d\bde\bev\bvp\bps\bs/\b/_\bF
+ Font description file for font _\bF.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt/\b/d\bde\bev\bvp\bps\bs/\b/d\bdo\bow\bwn\bnl\blo\boa\bad\bd
+ List of downloadable fonts.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt/\b/d\bde\bev\bvp\bps\bs/\b/t\bte\bex\bxt\bt.\b.e\ben\bnc\bc
+ Encoding used for text fonts.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/t\btm\bma\bac\bc/\b/t\btm\bma\bac\bc.\b.p\bps\bs
+ Macros for use with g\bgr\bro\bop\bps\bs; automatically loaded by
+ t\btr\bro\bof\bff\bfr\brc\bc
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/t\btm\bma\bac\bc/\b/t\btm\bma\bac\bc.\b.p\bps\bsp\bpi\bic\bc
+ Definition of P\bPS\bSP\bPI\bIC\bC macro, automatically loaded by
+ t\btm\bma\bac\bc.\b.p\bps\bs.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/t\btm\bma\bac\bc/\b/t\btm\bma\bac\bc.\b.p\bps\bso\bol\bld\bd
+ Macros to disable use of characters not present in
+ older PostScript printers; automatically loaded by
+ t\btm\bma\bac\bc.\b.p\bps\bs.
+
+ /\b/u\bus\bsr\br/\b/s\bsh\bha\bar\bre\be/\b/t\btm\bma\bac\bc/\b/t\btm\bma\bac\bc.\b.p\bps\bsn\bne\bew\bw
+ Macros to undo the effect of t\btm\bma\bac\bc.\b.p\bps\bso\bol\bld\bd.
+
+ /\b/t\btm\bmp\bp/\b/g\bgr\bro\bop\bps\bs_\bX_\bX_\bX_\bX_\bX_\bX
+ Temporary file.
+
+S\bSE\bEE\bE A\bAL\bLS\bSO\bO
+ a\baf\bfm\bmt\bto\bod\bdi\bit\bt(1), g\bgr\bro\bof\bff\bf(1), t\btr\bro\bof\bff\bf(1), p\bps\bsb\bbb\bb(1), g\bgr\bro\bof\bff\bf_\b_o\bou\but\bt(5),
+ g\bgr\bro\bof\bff\bf_\b_f\bfo\bon\bnt\bt(5), g\bgr\bro\bof\bff\bf_\b_c\bch\bha\bar\br(7)
+
+
+
+
+
+Groff Version 1.08 30 December 1993 8
+
+
+
+
+
projects / unix-history / commitdiff