{ "mode": "man", "parameter": "gropdf", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/gropdf/1/json", "generated": "2026-09-04T00:09:24Z", "sections": { "Name": { "content": "gropdf - groff output driver for Portable Document Format\n", "subsections": [] }, "Synopsis": { "content": "gropdf [-dels] [-F font-directory] [-I inclusion-directory] [-p paper-format] [-u [cmap-\nfile]] [-y foundry] [file ...]\n", "subsections": [ { "name": "gropdf --help", "content": "" }, { "name": "gropdf -v", "content": "" }, { "name": "gropdf --version", "content": "" } ] }, "Description": { "content": "The GNU roff PDF output driver translates the output of \u001b]8;;man:troff(1)\u001b\\troff(1)\u001b]8;;\u001b\\ into Portable Document For‐\nmat. Normally, gropdf is invoked by \u001b]8;;man:groff(1)\u001b\\groff(1)\u001b]8;;\u001b\\ when the latter is given the “-T pdf” option.\n(In this installation, ps is the default output device.) Use groff's -P option to pass any\noptions shown above to gropdf. If no file arguments are given, or if file is “-”, gropdf\nreads the standard input stream. Output is written to the standard output stream.\n\nSee section “Font installation” below for a guide to installing fonts for gropdf.\n", "subsections": [] }, "Options": { "content": "--help displays a usage message, while -v and --version show version information; all exit\nafterward.\n", "subsections": [ { "name": "-d", "content": "PDF.\n", "flag": "-d" }, { "name": "-e", "content": "", "flag": "-e" }, { "name": "-F _", "content": "files; name is the name of the device, usually pdf.\n", "flag": "-F" }, { "name": "-I _", "content": "-I may be specified more than once; each dir is searched in the given order. To\nsearch the current working directory before others, add “-I .” at the desired place;\nit is otherwise searched last.\n", "flag": "-I" }, { "name": "-l", "content": "", "flag": "-l" }, { "name": "-p _", "content": "Set the physical dimensions of the output medium. This overrides the papersize, pa‐\nperlength, and paperwidth directives in the DESC file; it accepts the same arguments\nas the papersize directive. See \u001b]8;;man:grofffont(5)\u001b\\grofffont(5)\u001b]8;;\u001b\\ for details.\n", "flag": "-p" }, { "name": "-s", "content": "ment. Ghostscript's ps2pdf complains about this line if it is included, but works\nanyway.\n", "flag": "-s" }, { "name": "-u", "content": "gropdf normally includes a ToUnicode CMap with any font created using text.enc as the\nencoding file, this makes it easier to search for words which contain ligatures. You\ncan include your own CMap by specifying a cmap-file or have no CMap at all by omitting\nthe argument.\n", "flag": "-u" }, { "name": "-y _", "content": "Set the foundry to use for selecting fonts of the same name.\n", "flag": "-y" } ] }, "Usage": { "content": "The input to gropdf must be in the format output by \u001b]8;;man:troff(1)\u001b\\troff(1)\u001b]8;;\u001b\\. This is described in\n\u001b]8;;man:groffout(5)\u001b\\groffout(5)\u001b]8;;\u001b\\. In addition, the device and font description files for the device used must\nmeet certain requirements: The resolution must be an integer multiple of 72 times the\nsizescale. The pdf device uses a resolution of 72000 and a sizescale of 1000.\n\nThe device description file must contain a valid paper format; see \u001b]8;;man:grofffont(5)\u001b\\grofffont(5)\u001b]8;;\u001b\\. gropdf\nuses the same Type 1 Adobe PostScript fonts as the grops device driver. Although the PDF\nStandard allows the use of other font types (like TrueType) this implementation only accepts\nthe Type 1 PostScript font. Fewer Type 1 fonts are supported natively in PDF documents than\nthe standard 35 fonts supported by grops and all PostScript printers, but all the fonts are\navailable since any which aren't supported natively are automatically embedded in the PDF.\n\ngropdf supports the concept of foundries, that is different versions of basically the same\nfont. During install a Foundry file controls where fonts are found and builds groff fonts\nfrom the files it discovers on your system.\n\nEach font description file must contain a command\n\ninternalname psname\n\nwhich says that the PostScript name of the font is psname. Lines starting with # and blank\nlines are ignored. The code for each character given in the font file must correspond to the\ncode in the default encoding for the font. This code can be used with the \\N escape sequence\nin troff to select the character, even if the character does not have a groff name. Every\ncharacter in the font file must exist in the PostScript font, and the widths given in the\nfont file must match the widths used in the PostScript font.\n\nNote that gropdf is currently only able to display the first 256 glyphs in any font. This\nrestriction will be lifted in a later version.\n\ngropdf can automatically include the downloadable fonts necessary to print the document.\nFonts may be in PFA or PFB format.\n\nAny downloadable fonts which should, when required, be included by gropdf must be listed in\nthe file /usr/share/groff/1.23.0/font/devpdf/download; this should consist of lines of the\nform\n\nfoundry font filename\n\nwhere foundry is the foundry name or blank for the default foundry. font is the PostScript\nname of the font, and filename is the name of the file containing the font; lines beginning\nwith # and blank lines are ignored; fields must be separated by tabs (spaces are not al‐\nlowed); filename is searched for using the same mechanism that is used for groff font metric\nfiles. The download file itself is also sought using this mechanism. Foundry names are usu‐\nally a single character (such as ‘U’ for the URW foundry) or empty for the default foundry.\nThis default uses the same fonts as ghostscript uses when it embeds fonts in a PDF file.\n\nIn the default setup there are styles called R, I, B, and BI mounted at font positions 1\nto 4. The fonts are grouped into families A, BM, C, H, HN, N, P, and T having members in\neach of these styles:\n\nAR AvantGarde-Book\nAI AvantGarde-BookOblique\nAB AvantGarde-Demi\nABI AvantGarde-DemiOblique\nBMR Bookman-Light\nBMI Bookman-LightItalic\nBMB Bookman-Demi\nBMBI Bookman-DemiItalic\nCR Courier\nCI Courier-Oblique\nCB Courier-Bold\nCBI Courier-BoldOblique\nHR Helvetica\nHI Helvetica-Oblique\nHB Helvetica-Bold\nHBI Helvetica-BoldOblique\nHNR Helvetica-Narrow\nHNI Helvetica-Narrow-Oblique\nHNB Helvetica-Narrow-Bold\nHNBI Helvetica-Narrow-BoldOblique\nNR NewCenturySchlbk-Roman\nNI NewCenturySchlbk-Italic\nNB NewCenturySchlbk-Bold\nNBI NewCenturySchlbk-BoldItalic\nPR Palatino-Roman\nPI Palatino-Italic\nPB Palatino-Bold\nPBI Palatino-BoldItalic\nTR Times-Roman\nTI Times-Italic\nTB Times-Bold\nTBI Times-BoldItalic\n\nThere is also the following font which is not a member of a family:\n\nZCMI ZapfChancery-MediumItalic\n\nThere are also some special fonts called S for the PS Symbol font. The lower case greek\ncharacters are automatically slanted (to match the SymbolSlanted font (SS) available to Post‐\nScript). Zapf Dingbats is available as ZD; the “hand pointing left” glyph (\\[lh]) is avail‐\nable since it has been defined using the \\X'pdf: xrev' device control command, which reverses\nthe direction of letters within words.\n\nThe default color for \\m and \\M is black.\n\ngropdf understands some of the device control commands supported by \u001b]8;;man:grops(1)\u001b\\grops(1)\u001b]8;;\u001b\\.\n", "subsections": [ { "name": "\\X'ps: invis'", "content": "Suppress output.\n" }, { "name": "\\X'ps: endinvis'", "content": "Stop suppressing output.\n\n\\X'ps: exec gsave currentpoint 2 copy translate n rotate neg exch neg exch translate'\nwhere n is the angle of rotation. This is to support the align command in \u001b]8;;man:pic(1)\u001b\\pic(1)\u001b]8;;\u001b\\.\n" }, { "name": "\\X'ps: exec grestore'", "content": "Used by \u001b]8;;man:pic(1)\u001b\\pic(1)\u001b]8;;\u001b\\ to restore state after rotation.\n\n\\X'ps: exec n setlinejoin'\nwhere n can be one of the following values.\n\n0 = Miter join\n1 = Round join\n2 = Bevel join\n\n\\X'ps: exec n setlinecap'\nwhere n can be one of the following values.\n\n0 = Butt cap\n1 = Round cap, and\n2 = Projecting square cap\n\n\\X'ps: ... pdfmark'\nAll the pdfmark macros installed by using -m pdfmark or -m mspdf (see documentation in\npdfmark.pdf). A subset of these macros are installed automatically when you use -Tpdf\nso you should not need to use “-m pdfmark” to access most PDF functionality.\n\ngropdf also supports a subset of the commands introduced in present.tmac. Specifically it\nsupports:-\n\nPAUSE\nBLOCKS\nBLOCKE\n\nWhich allows you to create presentation type PDFs. Many of the other commands are already\navailable in other macro packages.\n\nThese commands are implemented with groff X commands:-\n" }, { "name": "\\X'ps: exec %%%%PAUSE'", "content": "The section before this is treated as a block and is introduced using the current\nBLOCK transition setting (see “\\X'pdf: transition'” below). Equivalently, .pdfpause\nis available as a macro.\n" }, { "name": "\\X'ps: exec %%%%BEGINONCE'", "content": "Any text following this command (up to %%%%ENDONCE) is shown only once, the next\n%%%%PAUSE will remove it. If producing a non-presentation PDF, i.e. ignoring the\npauses, see GROPDFNOSLIDE below, this text is ignored.\n" }, { "name": "\\X'ps: exec %%%%ENDONCE'", "content": "This terminates the block defined by %%%%BEGINONCE. This pair of commands is what im‐\nplements the .BLOCKS Once/.BLOCKE commands in present.tmac.\n\nThe mom macro package already integrates these extensions, so you can build slides with mom.\n\nIf you use present.tmac with gropdf there is no need to run the program \u001b]8;;man:presentps(1)\u001b\\presentps(1)\u001b]8;;\u001b\\ since\nthe output will already be a presentation PDF.\n\nAll other ps: tags are silently ignored.\n\nOne \\X device control command used by the DVI driver is also recognised.\n\n\\X'papersize=paper-format'\nwhere the paper-format parameter is the same as that to the papersize directive. See\n\u001b]8;;man:grofffont(5)\u001b\\grofffont(5)\u001b]8;;\u001b\\. This means that you can alter the page size at will within the PDF\nfile being created by gropdf. If you do want to change the paper format, it must be\ndone before you start creating the page.\n\ngropdf supports several more device control features using the pdf: tag. Some have counter‐\npart convenience macros that take the same arguments and behave equivalently.\n\n\\X'pdf: pdfpic file alignment width height line-length'\nPlace an image of the specified width containing the PDF drawing from file file of de‐\nsired width and height (if height is missing or zero then it is scaled proportion‐\nally). If alignment is -L the drawing is left-aligned. If it is -C or -R a line-\nlength greater than the width of the drawing is required as well. If width is speci‐\nfied as zero then the width is scaled in proportion to the height.\n" }, { "name": "\\X'pdf: xrev'", "content": "Toggle the reversal of glyph direction. This feature works “letter by letter”, that\nis, each letter in a word is reversed left-to-right, not the entire word. One appli‐\ncation is the reversal of glyphs in the Zapf Dingbats font. To restore the normal\nglyph orientation, repeat the command.\n\n\\X'pdf: markstart /ANN-definition'" }, { "name": "\\X'pdf: markend'", "content": "Macros that support PDF bookmarks use these calls internally to start and stop (re‐\nspectively) the placement of the bookmark's hot spot; the user will have called\n“.pdfhref L” with the text of the hot spot. Normally, these are never used except\nfrom within the pdfmark macros.\n" }, { "name": "\\X'pdf: marksuspend'", "content": "" }, { "name": "\\X'pdf: markrestart'", "content": "If you use a page location trap to produce a header or footer, or otherwise interrupt\na document's text, you need to use these commands if a PDF hot spot crosses a trap\nboundary; otherwise any text output by the trap will be marked as part of the hot\nspot. To prevent this error, place these device control commands or their correspond‐\ning convenience macros .pdfmarksuspend and .pdfmarkrestart at the start and end of the\ntrap macro, respectively.\n\n\\X'pdf: pagename name'\nAssign the current page a name. All documents bear two default names, ‘top’ and ‘bot‐\ntom’. The convenience macro for this command is .pdfpagename.\n\n\\X'pdf: switchtopage when name'\nNormally each new page is appended to the end of the document, this command allows\nfollowing pages to be inserted at a ‘named’ position within the document (see pagename\ncommand above). ‘when’ can be either ‘after’ or ‘before’. If it is omitted it de‐\nfaults to ‘before’. It should be used at the end of the page before you want the\nswitch to happen. This allows pages such as a TOC to be moved to elsewhere in the\ndocument, but more esoteric uses are possible. The convenience macro for this command\nis .pdfswitchtopage.\n\n\\X'pdf: transition feature mode duration dimension motion direction scale bool'\nwhere feature can be either SLIDE or BLOCK. When it is SLIDE the transition is used\nwhen a new slide is introduced to the screen, if BLOCK then this transition is used\nfor the individual blocks which make up the slide.\n\nmode is the transition type between slides:-\n\nSplit - Two lines sweep across the screen, revealing the new page. The lines\nmay be either horizontal or vertical and may move inward from the edges of the\npage or outward from the center, as specified by the dimension and motion en‐\ntries, respectively.\nBlinds - Multiple lines, evenly spaced across the screen, synchronously sweep\nin the same direction to reveal the new page. The lines may be either horizon‐\ntal or vertical, as specified by the dimension entry. Horizontal lines move\ndownward; vertical lines move to the right.\nBox - A rectangular box sweeps inward from the edges of the page or outward\nfrom the center, as specified by the motion entry, revealing the new page.\nWipe - A single line sweeps across the screen from one edge to the other in the\ndirection specified by the direction entry, revealing the new page.\nDissolve - The old page dissolves gradually to reveal the new one.\nGlitter - Similar to Dissolve, except that the effect sweeps across the page in\na wide band moving from one side of the screen to the other in the direction\nspecified by the direction entry.\nR - The new page simply replaces the old one with no special transition effect;\nthe direction entry shall be ignored.\nFly - (PDF 1.5) Changes are flown out or in (as specified by motion), in the\ndirection specified by direction, to or from a location that is offscreen ex‐\ncept when direction is None.\nPush - (PDF 1.5) The old page slides off the screen while the new page slides\nin, pushing the old page out in the direction specified by direction.\nCover - (PDF 1.5) The new page slides on to the screen in the direction speci‐\nfied by direction, covering the old page.\nUncover - (PDF 1.5) The old page slides off the screen in the direction speci‐\nfied by direction, uncovering the new page in the direction specified by direc‐\ntion.\nFade - (PDF 1.5) The new page gradually becomes visible through the old one.\n\nduration is the length of the transition in seconds (default 1).\n\ndimension (Optional; Split and Blinds transition styles only) The dimension in which\nthe specified transition effect shall occur: H Horizontal, or V Vertical.\n\nmotion (Optional; Split, Box and Fly transition styles only) The direction of motion\nfor the specified transition effect: I Inward from the edges of the page, or O Outward\nfrom the center of the page.\n\ndirection (Optional; Wipe, Glitter, Fly, Cover, Uncover and Push transition styles\nonly) The direction in which the specified transition effect shall moves, expressed in\ndegrees counterclockwise starting from a left-to-right direction. If the value is a\nnumber, it shall be one of: 0 = Left to right, 90 = Bottom to top (Wipe only), 180 =\nRight to left (Wipe only), 270 = Top to bottom, 315 = Top-left to bottom-right (Glit‐\nter only) The value can be None, which is relevant only for the Fly transition when\nthe value of scale is not 1.0.\n\nscale (Optional; PDF 1.5; Fly transition style only) The starting or ending scale at\nwhich the changes shall be drawn. If motion specifies an inward transition, the scale\nof the changes drawn shall progress from scale to 1.0 over the course of the transi‐\ntion. If motion specifies an outward transition, the scale of the changes drawn shall\nprogress from 1.0 to scale over the course of the transition\n\nbool (Optional; PDF 1.5; Fly transition style only) If true, the area that shall be\nflown in is rectangular and opaque.\n\nThis command can be used by calling the macro .pdftransition using the parameters de‐\nscribed above. Any of the parameters may be replaced with a \".\" which signifies the\nparameter retains its previous value, also any trailing missing parameters are ig‐\nnored.\n\nNote: not all PDF Readers support any or all these transitions.\n\n\\X'pdf: background cmd left top right bottom weight'" }, { "name": "\\X'pdf: background off'", "content": "\\X'pdf: background footnote bottom'\nproduces a background rectangle on the page, where\n\ncmd is the command, which can be any of “page|fill|box” in combination. Thus,\n“pagefill” would draw a rectangle which covers the whole current page size (in\nwhich case the rest of the parameters can be omitted because the box dimensions\nare taken from the current media size). “boxfill”, on the other hand, requires\nthe given dimensions to place the box. Including “fill” in the command will\npaint the rectangle with the current fill colour (as with \\M[]) and including\n“box” will give the rectangle a border in the current stroke colour (as with\n\\m[]).\n\ncmd may also be “off” on its own, which will terminate drawing the current box.\nIf you have specified a page colour with “pagefill”, it is always the first box\nin the stack, and if you specify it again, it will replace the first entry. Be\naware that the “pagefill” box renders the page opaque, so tools that “water‐\nmark” PDF pages are unlikely to be successful. To return the background to\ntransparent, issue an “off” command with no other boxes open.\n\nFinally, cmd may be “footnote” followed by a new value for bottom, which will\nbe used for all open boxes on the current page. This is to allow room for\nfootnote areas that grow while a page is processed (to accommodate multiple\nfootnotes, for instance). (If the value is negative, it is used as an offset\nfrom the bottom of the page.)\n\nleft\ntop\nright\nbottom are the coordinates of the box. The top and bottom coordinates are the minimum\nand maximum for the box, since the actual start of the box is groff's drawing\nposition when you issue the command, and the bottom of the box is the point\nwhere you turn the box “off”. The top and bottom coordinates are used only if\nthe box drawing extends onto the next page; ordinarily, they would be set to\nthe header and footer margins.\n\nweight provides the line width for the border if “box” is included in the command.\n\nThe convenience macro for this escape sequence is .pdfbackground. An sboxes macro\nfile is also available; see \u001b]8;;man:grofftmac(5)\u001b\\grofftmac(5)\u001b]8;;\u001b\\.\n" }, { "name": "Macros", "content": "gropdf's support macros in pdf.tmac define the convenience macros described above. Some fea‐\ntures have no direct device control command counterpart.\n\n.pdfinfo /field content ...\nDefine PDF metadata. field may be be one of Title, Author, Subject, Keywords, or an‐\nother datum supported by the PDF standard or your reader. field must be prefixed with\na slash.\n" }, { "name": "Importing graphics", "content": "gropdf supports only the inclusion of other PDF files for inline images. Such a PDF file\nmay, however, contain any of the graphic formats supported by the PDF standard, such as\nJPEG/JFIF, PNG, and GIF. Any application that outputs PDF can thus be used to prepare files\nfor embedding in documents processed by groff and gropdf.\n\nThe PDF file you wish to insert must be a single page and the drawing must just fit inside\nthe media size of the PDF file. In \u001b]8;;man:inkscape(1)\u001b\\inkscape(1)\u001b]8;;\u001b\\ or \u001b]8;;man:gimp(1)\u001b\\gimp(1)\u001b]8;;\u001b\\, for example, make sure the canvas\nsize just fits the image.\n\nThe PDF parser gropdf implements has not been rigorously tested with all applications that\nproduce PDF. If you find a single-page PDF which fails to import properly, try processing it\nwith the \u001b]8;;man:pdftk(1)\u001b\\pdftk(1)\u001b]8;;\u001b\\ program.\npdftk existing-file output new-file\nYou may find that new-file imports successfully.\n" }, { "name": "TrueType and other font formats", "content": "gropdf does not yet support any font formats besides Adobe Type 1 (PFA or PFB).\n" } ] }, "Font installation": { "content": "The following is a step-by-step font installation guide for gropdf.\n\n• Convert your font to something groff understands. This is a PostScript Type 1 font in PFA\nor PFB format, together with an AFM file. A PFA file begins as follows.\n%!PS-AdobeFont-1.0:\nA PFB file contains this string as well, preceded by some non-printing bytes. In the fol‐\nlowing steps, we will consider the use of CTAN's \u001b]8;;https://ctan.org/tex-archive/fonts/brushscr\u001b\\BrushScriptX-Italic\u001b]8;;\u001b\\ font in PFA format.\n\n• Convert the AFM file to a groff font description file with the \u001b]8;;man:afmtodit(1)\u001b\\afmtodit(1)\u001b]8;;\u001b\\ program. For\ninstance,\n$ afmtodit BrushScriptX-Italic.afm text.map BSI\nconverts the Adobe Font Metric file BrushScriptX-Italic.afm to the groff font description\nfile BSI.\n\nIf you have a font family which provides regular upright (roman), bold, italic, and bold-\nitalic styles, (where “italic” may be “oblique” or “slanted”), we recommend using R, B, I,\nand BI, respectively, as suffixes to the groff font family name to enable groff's font fam‐\nily and style selection features. An example is groff's built-in support for Times: the\nfont family name is abbreviated as T, and the groff font names are therefore TR, TB, TI,\nand TBI. In our example, however, the BrushScriptX font is available in a single style\nonly, italic.\n\n• Install the groff font description file(s) in a devpdf subdirectory in the search path that\ngroff uses for device and font file descriptions. See the GROFFFONTPATH entry in section\n“Environment” of \u001b]8;;man:troff(1)\u001b\\troff(1)\u001b]8;;\u001b\\ for the current value of the font search path. While groff\ndoesn't directly use AFM files, it is a good idea to store them alongside its font descrip‐\ntion files.\n\n• Register fonts in the devpdf/download file so they can be located for embedding in PDF\nfiles gropdf generates. Only the first download file encountered in the font search path\nis read. If in doubt, copy the default download file (see section “Files” below) to the\nfirst directory in the font search path and add your fonts there. The PostScript font name\nused by gropdf is stored in the internalname field in the groff font description file.\n(This name does not necessarily resemble the font's file name.) If the font in our example\nhad originated from a foundry named Z, we would add the following line to download.\nZ→BrushScriptX-Italic→BrushScriptX-Italic.pfa\nA tab character, depicted as →, separates the fields. The default foundry has no name: its\nfield is empty and entries corresponding to it start with a tab character, as will the one\nin our example.\n\n• Test the selection and embedding of the new font.\nprintf \"\\\\f[BSI]Hello, world!\\n\" | groff -T pdf -P -e >hello.pdf\nsee hello.pdf\n", "subsections": [] }, "Environment": { "content": "GROFFFONTPATH\nA list of directories in which to seek the selected output device's directory of de‐\nvice and font description files. If, in the download file, the font file has been\nspecified with a full path, no directories are searched. See \u001b]8;;man:troff(1)\u001b\\troff(1)\u001b]8;;\u001b\\ and\n\u001b]8;;man:grofffont(5)\u001b\\grofffont(5)\u001b]8;;\u001b\\.\n\nGROPDFNOSLIDE\nIf set and evaluates to a true value (to Perl), gropdf ignores commands specific to\npresentation PDFs, producing a normal PDF instead.\n\nSOURCEDATEEPOCH\nA timestamp (expressed as seconds since the Unix epoch) to use as the output creation\ntimestamp in place of the current time. The time is converted to human-readable form\nusing Perl's gmtime() function and recorded in a PDF comment.\n\nTZ The time zone to use when converting the current time to human-readable form; see\n\u001b]8;;man:tzset(3)\u001b\\tzset(3)\u001b]8;;\u001b\\. If SOURCEDATEEPOCH is used, it is always converted to human-readable form\nusing UTC.\n", "subsections": [] }, "Files": { "content": "/usr/share/groff/1.23.0/font/devpdf/DESC\ndescribes the pdf output device.\n\n/usr/share/groff/1.23.0/font/devpdf/F\ndescribes the font known as F on device pdf.\n\n/usr/share/groff/1.23.0/font/devpdf/U-F\ndescribes the font from the URW foundry (versus the Adobe default) known as F on de‐\nvice pdf.\n\n/usr/share/groff/1.23.0/font/devpdf/download\nlists fonts available for embedding within the PDF document (by analogy to the ps de‐\nvice's downloadable font support).\n\n/usr/share/groff/1.23.0/font/devpdf/Foundry\nis a data file used by the groff build system to locate PostScript Type 1 fonts.\n\n/usr/share/groff/1.23.0/font/devpdf/enc/text.enc\ndescribes the encoding scheme used by most PostScript Type 1 fonts; the encoding di‐\nrective of font description files for the pdf device refers to it.\n\n/usr/share/groff/1.23.0/tmac/pdf.tmac\ndefines macros for use with the pdf output device. It is automatically loaded by\ntroffrc when the pdf output device is selected.\n\n/usr/share/groff/1.23.0/tmac/pdfpic.tmac\ndefines the PDFPIC macro for embedding images in a document; see \u001b]8;;man:grofftmac(5)\u001b\\grofftmac(5)\u001b]8;;\u001b\\. It is\nautomatically loaded by troffrc.\n", "subsections": [] }, "Authors": { "content": "gropdf was written and is maintained by \u001b]8;;mailto:deri@chuzzlewit.myzen.co.uk\u001b\\Deri James\u001b]8;;\u001b\\.\n\nSee also\n/usr/share/doc/groff-base/sboxes/msboxes.ms\n/usr/share/doc/groff-base/sboxes/msboxes.pdf\n“Using PDF boxes with groff and the ms macros”, by Deri James.\n\npresent.tmac\nis part of \u001b]8;;https://bob.diertens.org/corner/useful/gpresent/\u001b\\gpresent\u001b]8;;\u001b\\, a software package by Bob Diertens that works with groff to pro‐\nduce presentations (“foils”, or “slide decks”).\n\n\u001b]8;;man:afmtodit(1)\u001b\\afmtodit(1)\u001b]8;;\u001b\\, \u001b]8;;man:groff(1)\u001b\\groff(1)\u001b]8;;\u001b\\, \u001b]8;;man:troff(1)\u001b\\troff(1)\u001b]8;;\u001b\\, \u001b]8;;man:grofffont(5)\u001b\\grofffont(5)\u001b]8;;\u001b\\, \u001b]8;;man:groffout(5)\u001b\\groffout(5)\u001b]8;;\u001b\\\n\ngroff 1.23.0 31 March 2024 gropdf(1)", "subsections": [] } }, "flags": [], "examples": [], "see_also": [] }