head 1.7; access; symbols pkgsrc-2026Q2:1.6.0.12 pkgsrc-2026Q2-base:1.6 pkgsrc-2026Q1:1.6.0.10 pkgsrc-2026Q1-base:1.6 pkgsrc-2025Q4:1.6.0.8 pkgsrc-2025Q4-base:1.6 pkgsrc-2025Q3:1.6.0.6 pkgsrc-2025Q3-base:1.6 pkgsrc-2025Q2:1.6.0.4 pkgsrc-2025Q2-base:1.6 pkgsrc-2025Q1:1.6.0.2 pkgsrc-2025Q1-base:1.6 pkgsrc-2024Q4:1.4.0.46 pkgsrc-2024Q4-base:1.4 pkgsrc-2024Q3:1.4.0.44 pkgsrc-2024Q3-base:1.4 pkgsrc-2024Q2:1.4.0.42 pkgsrc-2024Q2-base:1.4 pkgsrc-2024Q1:1.4.0.40 pkgsrc-2024Q1-base:1.4 pkgsrc-2023Q4:1.4.0.38 pkgsrc-2023Q4-base:1.4 pkgsrc-2023Q3:1.4.0.36 pkgsrc-2023Q3-base:1.4 pkgsrc-2023Q2:1.4.0.34 pkgsrc-2023Q2-base:1.4 pkgsrc-2023Q1:1.4.0.32 pkgsrc-2023Q1-base:1.4 pkgsrc-2022Q4:1.4.0.30 pkgsrc-2022Q4-base:1.4 pkgsrc-2022Q3:1.4.0.28 pkgsrc-2022Q3-base:1.4 pkgsrc-2022Q2:1.4.0.26 pkgsrc-2022Q2-base:1.4 pkgsrc-2022Q1:1.4.0.24 pkgsrc-2022Q1-base:1.4 pkgsrc-2021Q4:1.4.0.22 pkgsrc-2021Q4-base:1.4 pkgsrc-2021Q3:1.4.0.20 pkgsrc-2021Q3-base:1.4 pkgsrc-2021Q2:1.4.0.18 pkgsrc-2021Q2-base:1.4 pkgsrc-2021Q1:1.4.0.16 pkgsrc-2021Q1-base:1.4 pkgsrc-2020Q4:1.4.0.14 pkgsrc-2020Q4-base:1.4 pkgsrc-2020Q3:1.4.0.12 pkgsrc-2020Q3-base:1.4 pkgsrc-2020Q2:1.4.0.10 pkgsrc-2020Q2-base:1.4 pkgsrc-2020Q1:1.4.0.6 pkgsrc-2020Q1-base:1.4 pkgsrc-2019Q4:1.4.0.8 pkgsrc-2019Q4-base:1.4 pkgsrc-2019Q3:1.4.0.4 pkgsrc-2019Q3-base:1.4 pkgsrc-2019Q2:1.4.0.2 pkgsrc-2019Q2-base:1.4 pkgsrc-2014Q4:1.2.0.22 pkgsrc-2014Q4-base:1.2 pkgsrc-2014Q3:1.2.0.20 pkgsrc-2014Q3-base:1.2 pkgsrc-2014Q2:1.2.0.18 pkgsrc-2014Q2-base:1.2 pkgsrc-2014Q1:1.2.0.16 pkgsrc-2014Q1-base:1.2 pkgsrc-2013Q4:1.2.0.14 pkgsrc-2013Q4-base:1.2 pkgsrc-2013Q3:1.2.0.12 pkgsrc-2013Q3-base:1.2 pkgsrc-2013Q2:1.2.0.10 pkgsrc-2013Q2-base:1.2 pkgsrc-2013Q1:1.2.0.8 pkgsrc-2013Q1-base:1.2 pkgsrc-2012Q4:1.2.0.6 pkgsrc-2012Q4-base:1.2 pkgsrc-2012Q3:1.2.0.4 pkgsrc-2012Q3-base:1.2 pkgsrc-2012Q2:1.2.0.2 pkgsrc-2012Q2-base:1.2 pkgsrc-2012Q1:1.1.0.8 pkgsrc-2012Q1-base:1.1 pkgsrc-2011Q4:1.1.0.6 pkgsrc-2011Q4-base:1.1 pkgsrc-2011Q3:1.1.0.4 pkgsrc-2011Q3-base:1.1 pkgsrc-2011Q2:1.1.0.2; locks; strict; comment @# @; 1.7 date 2026.07.19.08.05.45; author adam; state Exp; branches; next 1.6; commitid 8ozLSHQntfS9PeOG; 1.6 date 2025.01.11.15.30.22; author ktnb; state Exp; branches; next 1.5; commitid zixZMMfTm63H55FF; 1.5 date 2025.01.10.03.42.15; author ktnb; state dead; branches; next 1.4; commitid vCZDmZhCHPCScTEF; 1.4 date 2019.04.01.16.48.37; author ryoon; state Exp; branches; next 1.3; commitid J5Od7aCJklJHpFhB; 1.3 date 2015.01.08.09.02.27; author wiz; state dead; branches; next 1.2; commitid fHmnCSKzORDOsc5y; 1.2 date 2012.05.31.09.24.53; author fhajny; state Exp; branches; next 1.1; 1.1 date 2011.07.19.21.09.38; author tez; state Exp; branches 1.1.2.1; next ; 1.1.2.1 date 2011.07.19.21.09.38; author sbd; state dead; branches; next 1.1.2.2; 1.1.2.2 date 2011.07.21.04.24.07; author sbd; state Exp; branches; next ; desc @@ 1.7 log @groff: updated to 1.24.1 VERSION 1.24.1 ============== This release corrects bugs in the groff 1.24.0 release, adds automated test scripts, revises a misleading diagnostic message, and improves documentation. There are no new features. VERSION 1.24.0 ============== Noteworthy incompatible changes ------------------------------- * If your roff(7) documents follow any of the requests `cf`, `hpf`, `hpfa`, `mso`, `msoquiet`, `nx`, `open`, `opena`, `so`, `soquiet`, or `trf` with a comment after their file name argument, and did not place that comment immediately after the file name, you are likely to get a diagnostic message resembling the following. warning: cannot open macro file 'e.tmac ': No such file or directory Or, less likely, the formatter will open the wrong file, one with spaces at the end of its name. That is because these requests are now able to process file names containing space characters. (This change also makes the request syntax consistent with that of `ds`, `as`, and others.) A quick fix is to place the comment escape sequence as early as possible. For example, we would change: .mso e.tmac \" Load Eric Allman's package. to: .mso e.tmac\" Load Eric Allman's package. to tell the formatter to load the "e.tmac" file rather than "e.tmac ". See the items below for further details. * If your roff(7) documents specify a file name that starts with a neutral double quote (") to any of the requests `cf`, `hpf`, `hpfa`, `mso`, `msoquiet`, `nx`, `open`, `opena`, `so`, `soquiet`, or `trf`, you are likely to get a diagnostic message, or the formatter will open a file of the same name except for the leading neutral double quote. That is because these requests are now able to process file names containing leading space characters. (This change also makes the request syntax consistent with that of `ds`, `as`, and others.) The solution is to add an additional neutral double quote to the start of the file name argument. For example, we would change: .so "5150".lrc to: .so ""5150".lrc to tell the formatter to read a file named '"5150".lrc', where the neutral single quotes bracket the file name. * groff mdoc(7)'s font customization feature, undocumented but analogous to that of 4.4BSD mdoc, now expects the strings that designate font names to be precisely that: font _names_ (or abstract styles, or mounting positions), rather than arbitrary *roff syntax. (String interpolations remain acceptable, as long as what they interpolate is a valid argument to the `ft` request or `\f[xxx]` escape sequence.) * Support for terminal devices using the CCSID 1047 (EBCDIC) encoding has been withdrawn. See below for motivation and a workaround. troff ----- * troff now recognizes an -S option, which "locks" safer mode, rejecting any subsequent specification of -U on the command line with an error diagnostic. * The `cf` request is now disabled in safer mode; as with `pi` and `sy`, you must specify troff's "unsafe mode" option `-U` to use it. Alternatively, use the `trf` request, available since groff 0.6 (circa 1990), to embed a file in GNU troff's output while discarding characters (most C0 and C1 controls) that are invalid as GNU troff input--and incidentally also undefined in GNU troff output. * The `hpfcode` request now emits an error when used, advising of its planned withdrawal, but then proceeds with normal behavior. The documented replacement mechanism, the `hcode` request, has existed since groff 1.02 (June 1991) at the latest. * The `mso` request no longer attempts to open a macro file named, say, "tmac.s" if "s.tmac" was specified as the argument and not found, nor vice versa. This feature was a convenience for some old AT&T troff installations, but few of those remain in the field, and of those that we know to survive, few use a macro file naming convention for which this feature is any help. (DWB 3.3 and Solaris do not, and we think other System V troffs don't, either. Only Plan 9 troff does.) `mso` now simply processes the macro search path for a file name matching the request argument, and succeeds or fails depending on an exact match. If you desire this functionality for portability (keeping in mind that `mso` is itself a groff extension), consider the following. .\" Load the ms package, whatever it might be named. .\" troffs without groff extensions must know its full path. .if !\n(.g .so /path/to/tmac.s .\" The following requests do nothing on non-GNU troffs. .do msoquiet s.tmac\" If file present, defines `LP` macro. .do if !d LP .msoquiet tmac.s * GNU troff no longer accepts nonpositive page lengths. Attempting to set one with the `pl` request clamps the page length to the vertical motion quantum as `ll` does with the horizontal motion quantum in AT&T and GNU troffs. * GNU troff no longer accepts a newline as a delimiter for the parameterized escape sequences `\A`, `\b`, `\o`, `\w`, `\X`, and `\Z`. * GNU troff no longer accepts C0 controls or Latin-1 Supplement characters in identifiers. We prohibit C0 controls to make the language less tolerant of unreadable input, and Latin-1 Supplement code points to enable us to pivot to reading UTF-8-encoded input in a future release. (Thus, we plan for Latin-1 Supplement characters to again be accepted in identifiers, but only as components of multibyte UTF-8 sequences.) * The `color`, `cp`, `kern`, `linetabs`, and `vpt` requests now interpret arguments with negative values as instructions to disable the corresponding feature, using the *roff integer-to-Boolean conversion idiom instead of the C/C++ one. Thus, if you invoke these requests with a register interpolation as an argument, the outcome agrees with an `if` test of the register's value. * GNU troff now implements saturating rather than wrapping integer arithmetic. Where before overflow would cause an error diagnostic and abort evaluation of the expression, the formatter now emits a warning diagnostic in the "range" category and continues evaluation. * GNU troff now strips a leading neutral double quote from the argument to the `cf`, `hpf`, `hpfa`, `lf`, `mso`, `msoquiet`, `nx`, `pi`, `pso`, `so`, `soquiet`, `sy`, and `trf` requests, and the second argument to the `open` and `opena` requests, allowing it to contain embedded leading spaces. * GNU troff now accepts space characters in the argument to the `cf`, `hpf`, `hpfa`, `lf`, `mso`, `msoquiet`, `nx`, `so`, `soquiet`, and `trf` requests, and the second argument to the `open` and `opena` requests. See "soelim" below. * The foregoing two changes make the syntax of the listed requests consistent with that of `ds`, `as`, and others that take arguments that the formatter reads to the next newline. * The "number" warning category has been withdrawn. The diagnostic that formerly used it has been promoted to an error. * The "el" warning category has been withdrawn. If enabled (which it was not by default), the formatter would emit a diagnostic if it inferred an imbalance between `ie` and `el` requests. Unfortunately its technique wasn't reliable and sometimes spuriously issued these warnings, and making it perfectly reliable did not look tractable. We recommend using brace escape sequences `\{` and `\}` to ensure that your control flow structures remain maintainable. * The "right-brace" warning category has been withdrawn. If enabled (which it was not by default), the formatter would emit a diagnostic in exactly one circumstance: when a numeric expression was expected (as, for instance, the second argument to an `nr` request) but a right brace escape sequence `\}` was encountered instead. This diagnostic still issues, but it is now an error. * GNU troff now performs some limited processing/transformation of the argument to the `\X` escape sequence and its counterpart `device` request, to address the requirement that some documents have to pass metadata that must encode non-ASCII characters in device extension commands. (For example, a document author may desire a document's section headings containing non-ASCII code points to appear correctly in PDF bookmarks. Further, GNU troff encodes its output page description language only in ASCII.) This change is expected to be of significance mainly to developers of output drivers for groff; groff_diff(7) describes the transformations. If you have been using `\X` or `.device` to pass ASCII data to the output driver as a device extension command and require that it remain precisely as-is, use the `\!` escape sequence or `output` request, and prefix your data with "x X ", the device-independent troff means of expressing a device extension command (see groff_out(5)). * In nroff mode (in other words, when producing output for devices that claim to be terminals), the formatter now reports warning diagnostics regarding certain output problems using units of lines (vertically) and character cells [ens] (horizontally) instead of inches (or the unit configured with the `warnscale` request) to describe the drawing position where the problem occurred. * The device-independent page description language produced by GNU troff now reports unbreakable spaces (those produced with the `\~` escape sequence) as word boundaries with the documentary 'w' command, just as it does for regular breakable spaces. * A new request, `hydefault`, and read-only register, `.hydefault`, manage the default automatic hyphenation mode of an environment. This resolves a long-standing problem of *roff formatting. When processing input like this, .nh and we temporarily shut off automatic hyphenation, .hy the foregoing request would not do exactly what we expect. AT&T and other troffs apply a hyphenation mode of 1 to the final input line (and subsequent ones), rather than restoring the mode in use before the `nh` request. Apart from overturning user expectations, for GNU troff "1" is not an appropriate mode for its English hyphenation patterns. (For example, "alibi" would break as "ali-bi" instead of "al-ibi" after this argumentless `hy` invocation.) With updates to groff's localization files accompanying this release, the foregoing input now works as desired. * A new read-only, string-valued register, `.trap`, interpolates the name of the next page location trap after the drawing position. * New registers `.it`, `.itc`, and `.itm` are available. These read-only (and, in the case of `.itm`, string-valued) registers report the number of lines remaining in a pending input trap, a Boolean indication of whether that pending input trap honors output line continuation (cf. the `it` and `itc` requests), and the name of the macro associated with the pending input trap, respectively. * A new request, `pchar`, reports to the standard error stream details of any class or ordinary, special, or indexed character arguments. * A new request, `pcolor`, reports to the standard error stream details of each color name specified as an argument, including its color space identifier and channel value assignments. Without arguments, all defined colors are listed. (A device's default stroke and/or fill colors, "default", are not listed since they are immutable and their details unknown to the formatter.) * A new request, `pcomposite`, reports to the standard error stream the list of configured composite character mappings. * A new request, `pfp`, reports to the standard error stream the list of occupied font mounting positions and the corresponding abstract style name or font information. * A new request, `pftr`, reports to the standard error stream the list of configured font translations. * A new request, `phw`, reports to the standard error stream the list of hyphenation exceptions associated with the current hyphenation language. * A new request, `pline`, reports to the standard error stream the list of output nodes (an internal data structure) corresponding to the pending output line. The list is empty if no such nodes exist. * The `pm` request now interprets any arguments as a sequence of macro, string, or diversion names, and reports their contents. * The `pnr` request now additionally reports the autoincrementation amount and interpolation format of each register (if it is not string-valued). * The `pnr` request now accepts arguments. It treats each as identifying a register and reports its properties to the standard error stream. * A new request, `pstream`, reports to the standard error stream the name of each stream opened with the `open` or `opena` requests, the name of the file backing it, and its mode (writing or appending). * The `ptr` request has been renamed to `pwh` (mnemonic: "Print WHen traps will spring"). As a rule, debugging requests starting with `p` correspond to a request name that manipulates the objects reported on when the `p` is removed. However, `ptr` had nothing to do with the `tr` request. The only exceptions to the stated rule of `p`-removal are now `line`, `m`, and `stream`, none of which are request names. * The `hla` request, when invoked with no arguments, now clears the hyphenation language, disabling automatic hyphenation. * The read-only registers `.m` and `.M` now interpolate "default" when the default color is selected as the stroke or fill color, respectively, rather than interpolating nothing. * Numeric expression contexts that accept the `z` and `u` scaling units, such as the `ps` request and `\s` escape sequence, now also accept `p` and `s`. * troff's `-c` command-line option now also removes the `color` request's ability to enable multi-color output. eqn --- * The "gifont" primitive replaces "gfont" as the means of configuring the global italic face in preprocessed equations. "gfont" remains recognized as a synonym for backward compatibility. The new name is intended to ease acquisition of the eqn language in light of GNU eqn's thirty-year-old extensions "gbfont" and "grfont". * New parameters tunable with the GNU eqn "set" primitive, "half_space" and "full_space", enable a document to configure the space widths produced by the eqn tokens '^' and '~', respectively. Previously, their widths were determined by the "thin_space" and "thick_space" parameters used to tune GNU eqn's automatic spacing computations. * The new "reset" primitive restores a named parameter to its default. groff ----- * The groff command now encodes the fate of failing processes in the pipeline it constructs and runs so that this information cannot be confused with groff's own error conditions (such as a usage error, which now produces an exit status of 2). See the section "Exit status" of groff(1) for details. * groff now passes the -S option to pic and troff if it is specified. nroff ----- * nroff now recognizes the -a, -D, -I, and -Z options and passes them to groff. * nroff now supports clustered options ("-tzms", for example) as groff, troff, and other GNU getopt-using programs do. pic --- * A new command, `polygon`, supports drawing polygons using arbitrary vertices. The command furthermore accepts the `fill[ed]` modifier. You can address a polygon's vertices and the midpoints of its edges with the new `.v[er[tex]]` and `.mid[point]` syntax suffixed to an object identifier, analogously to the existing compass point and `.c[enter]` feature. Thanks to Duncan Losin. * pic's -S option now "locks" safer mode, rejecting any subsequent specification of -U on the command line with an error diagnostic. soelim ------ * soelim no longer requires embedded space characters in `so` arguments to be backslash-escaped. (It continues to support that syntax, even though neither the AT&T nor GNU troff formatters ever have.) You can now embed a sequence of leading spaces in the argument by prefixing it with a with a neutral double quote character ("), which the program discards. These changes are to better align this program's parsing rules with the language of the formatter; consider the `ds` and `as` requests. Macro packages -------------- * Keith Marshall's pdfmark package is no longer distributed with groff, but is now separately maintained. Please visit for the latest version. * mom version 2.6 is distributed with this release. It supports multi-line headings. Thanks to Peter Schaffter. * The device-specific macro files loaded by "troffrc" automatically on startup, such as "html.tmac", no longer perform font translations for some font names used by varieties of AT&T troff ('C', 'Hb', 'HX', and several others). These names are not portable: in AT&T troff, the font repertoire, like the special character repertoire, was device-dependent. Since groff 1.23.0, GNU troff diagnoses attempts to use nonexistent font names. We recommend addressing such portability issues wherever suits you: (1) in a document, perhaps by using `ie` and `el` requests and the `.g` register to test whether the formatter claims support for groff extensions, then `ie` and `el` again with the `F` groff conditional expression operator to check for font availability, and to perform font remappings with the groff `ftr` request as desired; (2) doing so in your "troffrc" file; or (3) by modifying these macro files similarly. Users of the "dvi" and "lbp" output devices should be aware that these devices don't supply full families of monospaced fonts (and never have). See grodvi(1) and grolbp(1) for lists of font names supported by each device. The legacy names are retained for the "pdf" and "ps" devices for this release; however, use of them prompts one warning in the "font" category from the formatter per deprecated name. We expect to withdraw support for the names completely in a future groff release. See gropdf(1) and grops(1) for lists of font names supported by each device. * Hyperlink support is now enabled by default on PDF and terminal devices for an (man) and doc (mdoc) documents. Instructions and commented code for disabling it are in the "man.local" and "mdoc.local" files. * The `PDFPIC` macro implemented in the "pdfpic.tmac" macro file now uses identify(1) (from ImageMagick/GraphicsMagick) and file(1), if available, to attempt to determine the dimensions of an image to be embedded in a PDF document. See also the item regarding gropdf(1) below. Thanks to Deri James. * The an (man) package now supports use of its hyperlink macros (`UR`, `UE`, `MT`, and `ME`) in paragraph tags (that is, on the next line after a `TP` macro call). Use of the `MR` man page cross reference macro in a tag was already supported in groff 1.23.0. * The behavior of the an (man) package's `SY` and `YS` macros has been expanded to enable greater user control over vertical spacing and to make them convenient for synopsizing C language functions, not just commands. `SY` no longer puts vertical space on the output, and initially breaks the output line _only_ if it is encountered repeatedly without a preceding `YS` call. The computed indentation of synopsis lines after the first now also includes the width of anything already on the output line, so that you can precede the `SY` call with, for instance, the C language data type used for the return value in a function prototype. The `SY` macro now accepts an optional second argument. This second argument is typeset in bold, replaces the fixed-width space that is appended to the synopsis keyword in `SY`'s single-argument form, and is used in computation of the indentation of non-initial synopsis lines. However, this computed indentation can now also be overridden with that of the previous synopsis item. To do this, give any argument to the `YS` macro call "closing" the synopsis whose indentation you want to reuse. When you're done with such a grouped synopsis, leave the argument off the final `YS` call. In a "Synopsis" section of a man page, existing synopses consisting of a single item require no migration. This is the most common case. For others, where before you would write... .SY mv .I source .I destination .YS . .SY mv .I source \&.\|.\|.\& .I destination-directory .YS ...you would now write the following. .SY mv .I source .I destination .YS . .P .SY mv .I source \&.\|.\|.\& .I destination-directory .YS (That is, simply add a paragraphing macro.) And where before you would write... .SY mv .B \-h . .SY mv .B \-\-help .YS ...you would now write the following. .SY mv .B \-h .YS . .SY mv .B \-\-help .YS (That is, simply add `YS` after the first synopsis item.) Likely the biggest benefit of these changes is that it is now much easier to format C function prototypes with these macros. Here's how we would synopsize a somewhat complex standard C library function. .B "#include " .P .B void *\c .SY bsearch ( .BI const\~void\~*\~ key , .BI const\~void\~*\~ base , .BI size_t\~ nmemb , .BI int\~(* compar )\c .B (const\~void\~*, const\~void\~*)); .YS * The an (man), doc (mdoc), and doc-old (mdoc-old) macro packages have changed the default line length when formatting on terminals from 78n to 80n. The latter is a vastly more common device configuration, but that line length had been avoided since the groff 1.18 release in July 2002 (prior to that, the line length was 65n, as in AT&T nroff), for an undocumented reason. That reason appears to have been the interaction of bugs in GNU tbl(1) with an aspect of grotty(1)'s design. Those bugs have been resolved. A man(1) program can still instruct groff to format for any desired line length by setting the `LL` register on {g,n,t}roff's command line. * The an (man) and doc (mdoc) macro packages use slightly different vertical margins than previously, to align more closely with the traditional implementations of these packages. Per man(7) in the AT&T Unix System III manual (June 1980), the text area was 6.5 by 10 inches (on typesetters). When formatting for terminals with continuous rendering disabled (by default, it is enabled), the page footer now sets one line higher than before. * The an (man) and doc (mdoc) macro packages have added additional registers `BP`, `PO`, and `TS` for user configuration of man page rendering at formatting time. As noted in groff_man(7) and groff_mdoc(7), documents should never manipulate these. * The an (man) and doc (mdoc) macro packages now support a `BP` register to configure the ("base") paragraph inset amount; that is the amount used by man(7) for paragraphs not within an `RS`/`RE` relative inset, and in mdoc(7) for all paragraphs. Formerly, the `IN` register configured this amount with other indentation and inset amount parameters used by man(7). (In mdoc(7), it had no other purpose.) The base paragraph indentation default is now 5n, corresponding to that used by historical man(7) and mdoc(7) implementations going back to Unix Version 7 (1979) and 4.3BSD-Reno (1990), respectively. * The an (man) and doc (mdoc) macro packages now support a `PO` register to configure the page offset used by the formatter. * The an (man) macro package now supports a `TS` register to configure the minimum space required between the tag of a `TP` paragraph and its body. (If the width of the tag's formatted text plus this space exceeds the paragraph indentation, the line is broken after the tag.) This parameter, formerly hard-coded as `1n`, now defaults to `2n`. * The an (man) macro package's `IP` macro no longer honors the formerly hard-coded 1n tag separation noted in the previous item. This means that the first argument to the `IP` macro can abut the text of the paragraph with no intervening space. If you use a word instead of punctuation or a list enumerator for `IP`'s first argument, consider migrating to `TP`. * The "an-ext.tmac" macro file, loaded automatically by the an (man) macro package, no longer defines `DS` and `DE` macros. It had defined them as empty (undocumentedly) since groff 1.20 (2009). * The doc (mdoc) macro package's `Mt` macro now sets its argument in roman, not italics (or whatever the string `doc-Pa-font` was configured to use). A new string, `doc-Mt-font`, for use in "mdoc.local" files and similar, supports configuration of this face. * The doc (mdoc) macro package now performs font family switches inline (that is, on the same output line) to Courier much less frequently when formatting for typesetters, affecting the `Ar`, `Cm`, `Er`, `Fa`, `Fd`, `Fl`, `Fn`, `Ft`, `Ic`, `Li`, and `Nm` macros. This change was made to reduce the ambiguity of space widths when typesetting the monospaced Courier and proportional Times fonts adjacently. Bear in mind that you can use the "mdoc.local" file to customize the font used to render nearly any mdoc(7) macro's arguments; this mechanism has been in place since 1992. * The doc (mdoc) macro package's `Ql` macro now operates more simply; it no longer (ever) quotes its arguments when formatting for typesetters. In practice, it does not seem difficult to distinguish even single characters in Courier from those in Times. (If it is, an _explicit_ quoting macro like `Sq` or `Dq` should be used.) * The doc (mdoc) macro package's `Lk`, `Mt`, and `Xr` macros now produce hyperlinks on HTML, PDF, and terminal devices. See above regarding hyperlink support being enabled by default. * The doc (mdoc) macro package now honors the `U` register and `MF` string as the an (man) package does. * The new macro file "koi8-r.tmac" supports the KOI8-R character encoding, which supports the new Russian locale for groff. * The m (mm) macro package now uses a 3v bottom margin rather than 2v. (Using the default type size and vertical spacing, the result is a half-inch margin, just like the existing top margin.) When formatting for terminals, content aligned to the bottom of the page (footers, footnotes, `BS`/`BE` bottom blocks, and similar) now sets one line higher than before. Further, the margin between the body text and any page footers is now 2v, like that between the body text and page headers, not 1v. * The m (mm) macro package's `Limsp` register (a GNU extension) has been removed; see the item regarding the `LI` macro below. * The m (mm) macro package's `Le` register now defaults to `1`, consistently with the `Lf`, `Lt`, and `Lx` registers of similar purpose, but inconsistently with DWB 3.3 mm. Explicitly assigning the `Le` register in a document's preamble works as it always has. * The m (mm) macro package's `AST` macro (a GNU extension) is deprecated, warns upon usage, and is slated for withdrawal in a future release. Assign to the new string `Abstract` instead. * The m (mm) macro package's `ISODATE` macro (a GNU extension) is deprecated, warns upon usage, and is slated for withdrawal in a future release. Assign to the new register `Isodate` instead. * The m (mm) macro package's `EPIC` macro (a GNU extension) now interprets its "width" argument in ens by default, and its "height" argument in vees, instead of basic units, for consistency with the rest of the package. * Similarly, the m (mm) macro package's `PIC` macro (a GNU extension) now interprets an argument to its `-I` option in ens instead of ems by default. * The m (mm) macro package no longer superscripts _and_ brackets a reference mark (the `Rf` string). Instead, the new `Rfstyle` register controls its formatting. The default, 0, selects bracketing in nroff mode and superscripting in troff mode. Set `Rfstyle` to 3 in a document to obtain groff mm's previous mark formatting behavior. * The m (mm) macro package's `Li` register now defaults to 5 ens (not 6) to align with the `Pi` register default. * The m (mm) macro package's `Li` register now configures the text indentation of items in `RL` lists (as it long has for `AL` lists) instead of hard-coding a value of 6 ens as DWB 3.3 mm does. * The m (mm) macro package's `BVL` (a GNU extension) and `VL` macros' first arguments are now optional. If omitted, the paragraph indentation amount (register `Pi`) is used for list items' text indentations. * The m (mm) macro package's `DL` macro now uses the `EM` string as the mark instead of an em dash special character literal. (The latter remains the default definition of the `EM` string.) * The m (mm) macro package's `DS` macro now interprets its third argument (a right-hand indentation) in ens by default, for consistency with the rest of the package. This is a difference from DWB mm (which passed the value unprocessed to the `ll` request, which itself uses ems), and groff mm's own historical behavior, which used basic units. * The m (mm) macro package's `HU` macro now supports an optional second argument as a GNU extension. It corresponds to the optional third argument of the `H` macro. * The m (mm) macro package's `IND` macro (a GNU extension), now calls `SK` only if no `TXIND` macro is defined, instead of performing this action as part of the fallback when no `TYIND` macro is defined. * The m (mm) macro package now supports a user-definable hook macro `AFX`, which if defined is called by `AF` in lieu of the latter's normal operation. Applications include customization of letterhead. * The m (mm) macro package now supports a user-definable hook macro `RPX`, which if defined is called by `RP` in lieu of the latter's normal operation (breaking the page [potentially], and formatting the reference list caption string `Rp`). * The m (mm) macro package's `LI` macro now interprets its second argument as a Boolean value indicating whether a space should separate the list item mark from its prefix (the first argument). Thus, where you formerly specified "2" to indicate no such separation, you would now use "0", matching the semantics of the former `Limsp` register. "2" continues to be recognized and handled as before, but prompts a warning; migrate your documents. * The m (mm) macro package now supports an `Aumt` string to suppress the appearance of positional arguments to the `AU` macro in the document heading used by memorandum types 0-3 and 6. By default, all such arguments appear, except the second (author initials). For example, a value of "3 4" more accurately reproduces London & Reiser's 1978 paper describing the porting of Unix to the VAX-11/780. * The m (mm) macro package now supports an `Rpfmt` string specifying the `LB` macro arguments that the package uses to format the items in an `RP` reference list. * The m (mm) macro package now supports the `E` register as DWB mm did. * The m (mm) macro package now supports DWB mm's `Rg` string. * The m (mm) macro package's `nP` macro now behaves more like DWB mm's. It applies a temporary indentation to the second output line of a paragraph to align it with the start of the paragraph text (not the tag/label) in the first, and resets the paragraph counter when the first- or second-level section heading number increments. * The m (mm) macro package's `Iso` register is now named `Isodate` to make its meaning less ambiguous. The old name remains as an alias. * The m (mm) macro package's `Rpe` register is now named `Rpej` for better symmetry with `Ej`. The old name remains as an alias. * The m (mm) macro package has renamed several strings to make their purposes less obscure; they determine the content of captions, not list items. `Licon` -> `Captc` `Liec` -> `Capec` `Liex` -> `Capex` `Lifg` -> `Capfg` `Litb` -> `Captb` The old names remain as aliases. * The m (mm) macro package has renamed the `Tcst` string to `Tcstatus` to make its purpose less obscure. The old name remains as an alias. * The m (mm) macro package recognizes new register names `Ftnum` and `Rfnum` for the automatically incrementing footnote and reference counters. The old, DWB-compatible but cryptic, names `:p` and `:R` remain supported. * The s (ms) macro package now sets the vertical spacing register defaults for normal (`VS`) and footnote (`FVS`) text to 120% of the type size configured in the `PS` and `FPS` registers, respectively, rather than 2 points larger, to comport with generally accepted typesetting principles. Thus, when formatting a document with a type size of 20 points, the vertical spacing now defaults to 24 points rather than 22. * The s (ms) macro package now subtracts one vee from the footer trap location computed using the `FM` register. When using the default `FM` value of `1i`, this makes the size of the margin from the footer baseline to the bottom of the page 3 vees or one half-inch, consistently with that between the header baseline and the page top. While a bug fix, and consistent with DWB 3.3 ms, this computation is inconsistent with Seventh Edition Unix ms and Heirloom Doctools ms. When formatting for terminals, footers now set one line higher than before. The size of the footnote area is not affected; instead there is a 1v smaller margin between its bottom and the footer baseline. Output drivers -------------- * grohtml(1), the (X)HTML output driver, supports a new `-k` command- line option that takes a mandatory argument, either "ascii" or "utf-8", which it recognizes case-insensitively. This feature configures representation of character entities in the output. Based on work by TANAKA Takuji. * gropdf(1), the PDF output driver, now allows embedding of JFIF/JPEG and JPEG 2000 image file formats. If PerlMagick is installed, many more image file formats, including PNG, PAM, and GIF, can be embedded. See also the item regarding `PDFPIC` above. Thanks to Deri James. * gropdf now supplies its own "SS" (slanted symbol) font to improve rendering of documents requiring slanted lowercase Greek letters, such as those employing the eqn(1) preprocessor. groff supplies the font in PFB format, and gropdf automatically embeds it, as it is not a standard PDF font. Formerly, groff's "pdf.tmac" file defined fallback characters for lowercase Greek letters, applying a slant of 16 degrees to the upright glyphs available in the standard symbol font "S". That technique produced glyphs slightly larger than those in grops's "SS" font. Thanks to Deri James. * gropdf now subsets embedded fonts by default, meaning that it stores only the glyphs a document actually uses. Font subsetting usually reduces the size of the PDF gropdf creates. Thanks to Deri James. * gropdf supports a new `--opt` command-line option, permitting a few features, including font subsetting, to be selectively enabled. Thanks to Deri James. * gropdf now emits PDFs that conform to the PDF 1.7 standard (also known as ISO 32000). Its new `--pdfver` command-line option permits production of PDF 1.4-conformant output instead. Thanks to Deri James. * gropdf supports a new `pdf: pagenumbering` device extension command and `pdfpagenumbering` convenience macro, allowing control of the page numbers in a PDF reader's overview panel. It is common for a document to number early pages with Roman numerals and then restart page enumeration at decimal 1 for its main matter. Thanks to Deri James. * gropdf now offers its own implementations of the "pdfmark" macro package's "pdfhref" and other macros, supporting internal (bookmarks, named destinations) and external (URL) hyperlinks, and the specification of hotspots for link text. For example, when bundling multiple man pages into a collection, as the supplied groff-man-pages.pdf document and the Linux man-pages project do, references to man pages within the collection are supported with internal hyperlinks, and those outside with external ones. Thanks to Deri James. * gropdf now supports characters outside the Unicode Basic Latin subset in bookmarks, named destinations, and external hyperlinks. (They must be encoded using groff's Unicode special character escape sequences; the preconv preprocessor is helpful to simply this requirement.) Thanks to Deri James. * gropdf now recognizes a `GROPDF_OPTIONS` environment variable, interpreting it as a space-separated list of command-line options. Explicit command-line options override any settings from this environment variable. You can use this variable to obviate passing options to gropdf via groff's `-P` option. Thanks to Deri James. * grops(1), the PostScript output driver, now supports fonts encoded using UTF-16. Indicate the encoding by including the string "-UTF16-" within the font's name as specified by the "internalname" directive in its font description file. Thanks to TANAKA Takuji. * The PostScript output driver grops(1) no longer accepts spaces as field separators in its "download" file; this is so that spaces can appear in font file names, and to better align the syntax of this file with that used by gropdf(1). The download file for grops shipped by groff has long used tabs rather than spaces for field separation. * The PostScript output driver grops(1)'s macro file "ps.tmac" no longer defines fallback special characters `\[S ,]` and `\[S ,]` to simulate support for what Unicode calls LATIN {CAPITAL,SMALL} LETTER S WITH COMMA BELOW. The file's definition constructed these glyphs by overstriking the Basic Latin "S" (or "s") with a cedilla accent, which is regarded as less orthographically acceptable than in the past. A user's document or macro file can still do exactly what "ps.tmac" used to. .fchar \[S ,] \o'S\[ac]' .hcode \[S ,]s .fchar \[s ,] \o's\[ac]' .hcode \[s ,]s * The PostScript output driver grops(1) once again accepts a file name containing slashes as a document prolog or resource (such as a font to be downloaded into the document). This is a restoration of groff 1.22.4 and earlier behavior; groff's 1.23.0 change of not accepting a file name containing slashes as an encoding or font description remains in place. (We impose this restriction because the output driver interprets the contents of these files; it does not interpret the PostScript prolog or resource files.) * grotty(1) now supports devices recognizing ECMA-48/ISO 6429 SGR 38 and 48 escape sequences that select RGB colors using 8 bits per color channel. A new command-line option, `-t`, configures emission of these escape sequences instead of the SGR 30-37 and 40-47 sequences supporting 3- or 4-bit color. Thanks to Deri James. Example: $ groff -T utf8 -P -t <s. * The localization macro files now set up an appropriate hyphenation mode default. For Chinese and Japanese, this is zero. * If groff programs have their current time overridden by the SOURCE_DATE_EPOCH environment variable, then that time is always displayed in UTC. That environment variable is normally only set when specifically requesting build systems to produce reproducible output, and it is useful for reproducibility test harnesses to vary the TZ environment variable and ensure that it does not affect the output of the build; those harnesses have no way to set TZ=UTC only for groff programs. People setting SOURCE_DATE_EPOCH are likely to be more in the "system programmer" camp as described in the release notes for 1.23.0, so it is easier to defend time-zone-invariant output to them. In all other cases, the current time remains displayed in local time. Thanks to Colin Watson. * The minimum version of Perl required to build groff is now 5.8 (18 July 2002), incremented from 5.6.1. * groff now looks for the Netpbm program pamcut(1) rather than pnmcut(1). Per its developers, the former was introduced in 2001 ago and the latter withdrawn in 2009. * The Makefile macro `DEVICE` has been renamed to `DEFAULT_DEVICE`; be aware if your builds don't use "ps" as the default output device. * The groff_diff(7) man page no longer contains examples. They remain in groff's Texinfo manual. * groff's Texinfo manual now adapts its content to the groff command prefix configured at build time. If the build is configured without a leading "g"--omitting it has been groff's default for many years, possibly forever--then our Texinfo manual now omits that prefix when mentioning the affected commands (all replacements for AT&T troff commands). This way, if you select a command prefix, say "limbo", and rebuild the Texinfo manual, the manual reflects the prefix used by your build configuration, and talks about "limboeqn", "limbotroff", "limborefer", and so on. @ text @$NetBSD: patch-configure,v 1.6 2025/01/11 15:30:22 ktnb Exp $ Add g prefix to some commands. --- configure.orig 2026-03-14 07:53:44.000000000 +0000 +++ configure @@@@ -45327,8 +45327,7 @@@@ $as_echo "$PAGE$message" >&6; } g= { $as_echo "$as_me:${as_lineno-$LINENO}: checking for existing troff installation" >&5 $as_echo_n "checking for existing troff installation... " >&6; } - if test "`(echo .tm '|n(.g' | tr '|' '\\\\' | troff -z -i 2>&1) \ - 2>/dev/null`" = 0 + if test true then { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 $as_echo "yes" >&6; } @ 1.6 log @groff: fixed missing gnu directory and g prefixed commands @ text @d1 1 a1 1 $NetBSD$ d3 1 a3 1 * Add g prefix to some commands d5 1 a5 1 --- configure.orig 2023-07-05 20:58:35.000000000 +0000 d7 1 a7 1 @@@@ -28823,9 +28823,7 @@@@ printf "%s\n" "$PAGE" >&6; } d9 2 a10 2 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for existing troff installation" >&5 printf %s "checking for existing troff installation... " >&6; } d13 4 a16 5 - then + if test true; then { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5 printf "%s\n" "yes" >&6; } g=g @ 1.5 log @groff: forgot to remove the configure patch from cvs @ text @d1 1 a1 1 $NetBSD: patch-configure,v 1.4 2019/04/01 16:48:37 ryoon Exp $ d5 1 a5 1 --- configure.orig 2018-12-23 14:34:25.000000000 +0000 d7 11 a17 9 @@@@ -23841,7 +23841,7 @@@@ $as_echo "$PAGE" >&6; } { $as_echo "$as_me:${as_lineno-$LINENO}: checking for existing troff installation" >&5 $as_echo_n "checking for existing troff installation... " >&6; } - if test "x`(echo .tm '|n(.g' | tr '|' '\\\\' | troff -z -i 2>&1) 2>/dev/null`" = x0; then + if test true; then { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 $as_echo "yes" >&6; } g=g @ 1.4 log @Update to 1.22.4 Changelog: VERSION 1.22.4 ============== Troff ----- o The `hy' request has been extended. Value 16 enables hyphenation before the last character, and value 32 enables hyphenation after the first character. PDFPIC ------ o PDFPIC has been corrected so the behaviour is the same whether you use the PostScript or PDF drivers. However, this means that any documents which were written using the old behaviour will not be rendered correctly if using the PDF driver with the new version. The change would mean that documents which relied on the previous behaviour are likely to have a gap underneath the image which was not there before. If you see this effect there are three ways you can restore the previous behaviour: Add the line ".nr PDFPIC_NOSPACE 1" to the document before the first call to .PDFPIC. If it is just a single document which exhibits this behaviour you can run groff adding "-rPDFPIC_NOSPACE=1" to the command line. If you have many documents which rely on the previous behaviour you can set an environment variable "export GROFF_PDFPIC_NOSPACE=1" which will restore the previous behaviour for all runs. Note that this change has no effect if you were using .PDFPIC with the PostScript driver--only if you used it with the PDF driver. Gropdf ------ o Type 1 font loading is fixed to handle newer Ghostscript versions. o Handling of glyphs above position 255 is improved to allow many more glyphs to be used. o New macros .pdftransition and .pdfpause are introduced to allow creation of presentation slides. Partially backward-compatible with present.tmac, specifically the PAUSE, BLOCKS and BLOCKE commands. Supports all the transition types introduced in PDF v1.5 (see the gropdf man page). Miscellaneous ------------- o A new 'configure' option --with-compatibility-wrappers controls how groff compatibility wrappers for vendor-provided non-GNU macro sets are installed (see ./configure --help). o eqn2graph, grap2graph, and pic2graph now attempt to adapt to very old installed versions of the ImageMagick and GraphicsMagick programs "convert". They search the output of convert's "-help" option, and use "-trim" if that string is found; otherwise, the old "-crop 0x0" method (which produces incompatible results on versions that _do_ support "-trim") is used. The programs emit a warning to standard error if the search fails and the old method is used. o eqn2graph no longer supports the "-unsafe" option. It did nothing. o groffer now supports the output of XHTML. Use the "--xhtml" or "--mode=xhtml" command-line options to generate it. o Much work has been done, and is ongoing, to make groff's man pages better examples for man page writers to follow. groff_man(7) itself has been expanded and largely rewritten to more precisely document the macro package's behavior and to be more helpful and accessible to man page writers who may never read any other groff documentation. @ text @d1 1 a1 1 $NetBSD$ @ 1.3 log @Update to 1.22.3: VERSION 1.22.3 ============== Gxditview --------- o X11 resources for `gxditview', which were previously installed in /usr/X11/lib/X11/app-defaults no matter which `prefix' was set, are now installed in appresdir=$prefix/lib/X11/app-defaults. If `appresdir' is not a standard X11 resource directory, the environment variable XFILESEARCHPATH should be set to this path. The standard default directories depends on the system `libXt'. Common directories include: /usr/lib/X11/app-defaults /usr/share/X11/app-defaults /etc/X11/app-defaults Note that if the option `--with-appresdir' is passed to `configure', the `prefix' will not be added to `appresdir'. Glilypond --------- o This new preprocessor (contributed by Bernd Warken) allows embedding of code for GNU LilyPond (http://www.lilypond.org), a music typesetter. The data gets automatically processed and embedded as EPS images. Gperl ----- o Bernd Warken contributed a new preprocessor to handle Perl code that can be evaluated and then processed by groff. Gpinyin ------- o Another preprocessor from Bernd Warken to pretty-print Pinyin syllables like `guo2wang2' as `guówáng'. Pdfroff ------- o The pdfroff utility script now activates its `--no-toc-relocation' option by default, unless a request similar to: .if !\n[PHASE] .tm pdfroff-option:set toc_relocation=enabled is invoked during input file processing; (`.if !\n[PHASE] ...' ensures that the effect of the `.tm' request is restricted to the document setup phase of processing, as pdfroff sets it to 1 or 2 in the output phase, but leaves it unset in the setup phase). The bundled `spdf.tmac' macro package, which implicitly activates `-mpdfmark' for `ms' macro users, ensures that TOC relocation is appropriately enabled, when the `.TC' macro is invoked. Macro Packages -------------- o The -mom macro package now has full support for eqn, pic, and tbl, as well as captioning and labelling of pdf images and preprocessor output. Lists of Figures, Equations, and Tables can now be autogenerated. PDF_IMAGE has a new FRAME option. o A French introduction to the -me macro package has been added (file `meintro_fr.me'). o In -mdoc, command %C is now available, providing a city or place reference. VERSION 1.22.2 ============== Tbl --- o The character `#' can now be used as an eqn delimiter within tables. Eqn --- o A GNU extension delim on has been added to reactivate delimiters which have been disabled with `delim off'. VERSION 1.22.1 ============== (There was no release 1.22.) Groff ----- o A new option `-j' has been added to call the `chem' preprocessor. Tbl --- o Improved line numbering support. Macro Packages -------------- o Support for the `refer' preprocessor has been added to the -mm macro package. o In -me, the `TH' macro was changed for compatibility with line number support in tables. `bl' now works inside of blocks. The behaviour of centered blocks has been improved. Line numbering support has been improved. o The -mom macro package has reached version 2.0, focusing on PDF output with gropdf (using the new `pdfmom' wrapper script). See the file `version-2.html' of the -mom documentation for a list of the many changes. o Some generic Unicode fallback characters (mainly Roman numerals) have been added. Gropdf ------ o A new driver for generating PDF output directly, contributed by Deri James . Note that this driver is written in Perl, thus you need a working Perl installation to run this output device. Pdfmom ------ o A new wrapper around groff that facilitates the production of PDF documents from files formatted with the -mom macros. VERSION 1.21 ============ Troff ----- o The new `lsm' request specifies a macro to be invoked when leading spaces in an input line are encountered (which are removed then). Number registers `lsn' and `lss' hold the number of removed leading spaces and the corresponding horizontal space, respectively. o There is a new warning category `file', enabled by default. The `mso' request emits warnings in this category when the requested macro file does not exist. o The new `class' request assigns a short name to a set of characters which can be referred to in the `cflags' request. This is especially useful to control line-breaking and hyphenation rules in CJK languages. o Three new values for the `cflags' request have been added, which are needed for proper CJK support. 128 prohibit before but allow break after character 256 prohibit after but allow break before character 512 allow break before and after character Tbl --- o A new global option `nowarn' suppresses warnings if tables are longer than the current line width. Afmtodit -------- o New option `-o' to specify the name of the output file. Macro Packages -------------- o A new macro `%U' has been added to the mdoc package to indicate a URL reference within an .Rs/.Re environment. o Rudimentary support for the Japanese script has been added, most suitable for man page handling as output by grotty. The file `ja.tmac' contains the necessary setup to allow line breaks before and after CJK characters (with proper exceptions). Note, however, that no inter-character spacing is implemented yet -- this usually causes many warnings about bad line breaks. @ text @d1 1 a1 1 $NetBSD: patch-configure,v 1.2 2012/05/31 09:24:53 fhajny Exp $ d3 1 a3 6 Fix many temporary file handling issues, including in pdfroff (resolves CVE-2009-5044 / SA44999) Patches copied from: http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/groff/groff-1.20.1-owl-tmp.diff?rev=1.2 Modified for pkgsrc and excluded a documentaion change to doc/groff.texinfo that changes a `makeinfo' is too old warning into a fatal error. d5 1 a5 1 --- configure.orig 2009-01-09 14:25:52.000000000 +0000 d7 1 a7 3 @@@@ -11598,18 +11598,6 @@@@ _ACEOF { $as_echo "$as_me:$LINENO: result: $PAGE" >&5 $as_echo "$PAGE" >&6; } d9 2 a10 2 -{ $as_echo "$as_me:$LINENO: checking for existing troff installation" >&5 -$as_echo_n "checking for existing troff installation... " >&6; } d12 4 a15 50 - { $as_echo "$as_me:$LINENO: result: yes" >&5 -$as_echo "yes" >&6; } - g=g - else - { $as_echo "$as_me:$LINENO: result: no" >&5 -$as_echo "no" >&6; } - g= - fi - { $as_echo "$as_me:$LINENO: checking for prefix of system macro packages" >&5 $as_echo_n "checking for prefix of system macro packages... " >&6; } sys_tmac_prefix= @@@@ -12937,33 +12925,12 @@@@ if $ac_need_defaults; then test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers fi -# Have a temporary directory for convenience. Make it in the build tree -# simply because there is no reason against having it here, and in addition, -# creating and moving files from /tmp can sometimes cause problems. -# Hook for its removal unless debugging. -# Note that there is a small window in which the directory will not be cleaned: -# after its creation but before its name has been assigned to `$tmp'. +# Create a temporary directory, and hook for its removal unless debugging. +tmp="`mktemp -dt cs.XXXXXXXXXX`" || exit $debug || { - tmp= - trap 'exit_status=$? - { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status -' 0 - trap '{ (exit 1); exit 1; }' 1 2 13 15 -} -# Create a (secure) tmp directory for tmp files. - -{ - tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` && - test -n "$tmp" && test -d "$tmp" -} || -{ - tmp=./conf$$-$RANDOM - (umask 077 && mkdir "$tmp") -} || -{ - $as_echo "$as_me: cannot create a temporary directory in ." >&2 - { (exit 1); exit 1; } + trap 'exit_status=$?; rm -rf -- "$tmp" && exit $exit_status' EXIT + trap '{ (exit $?); exit $?; }' HUP INT QUIT PIPE TERM } # Set up the scripts for CONFIG_FILES section. @ 1.2 log @Bypass a troff check in configure to stop introducing an unneeded g-prefix on SunOS, brings PLIST consistency across operating systems. @ text @d1 1 a1 1 $NetBSD: patch-configure,v 1.1 2011/07/19 21:09:38 tez Exp $ @ 1.1 log @Fix many temporary file handling issues, including in pdfroff (resolves CVE-2009-5044 / SA44999) Patches copied from: http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/groff/groff-1.20.1-owl-tmp.diff?rev=1.2 Modified for pkgsrc and excluded a documentaion change to doc/groff.texinfo that changes a `makeinfo' is too old warning into a fatal error. Added patch to make pdfroff.sh use -dSAFER See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538338 for details. @ text @d1 1 a1 1 $NetBSD$ d12 20 a31 1 @@@@ -12937,33 +12937,12 @@@@ if $ac_need_defaults; then @ 1.1.2.1 log @file patch-configure was added on branch pkgsrc-2011Q2 on 2011-07-21 04:24:07 +0000 @ text @d1 49 @ 1.1.2.2 log @Pullup ticket #3477 - requested by tez textproc/groff security fix Revisions pulled up: - textproc/groff/Makefile 1.58 - textproc/groff/distinfo 1.15 - textproc/groff/patches/patch-config.guess 1.1 - textproc/groff/patches/patch-configure 1.1 - textproc/groff/patches/patch-contrib_eqn2graph_eqn2graph.sh 1.1 - textproc/groff/patches/patch-contrib_gdiffmk_tests_runtests.in 1.1 - textproc/groff/patches/patch-contrib_grap2graph_grap2graph.sh 1.1 - textproc/groff/patches/patch-contrib_groffer_perl_groffer.pl 1.1 - textproc/groff/patches/patch-contrib_groffer_perl_roff2.pl 1.1 - textproc/groff/patches/patch-contrib_pdfmark_pdfroff.man 1.1 - textproc/groff/patches/patch-contrib_pdfmark_pdfroff.sh 1.1 - textproc/groff/patches/patch-contrib_pic2graph_pic2graph.sh 1.1 - textproc/groff/patches/patch-doc_fixinfo.sh 1.1 - textproc/groff/patches/patch-doc_groff.info-2 1.1 - textproc/groff/patches/patch-gendef.sh 1.1 - textproc/groff/patches/patch-src_roff_groff_pipeline.c 1.1 --- Module Name: pkgsrc Committed By: tez Date: Tue Jul 19 21:09:40 UTC 2011 Modified Files: pkgsrc/textproc/groff: Makefile distinfo Added Files: pkgsrc/textproc/groff/patches: patch-config.guess patch-configure patch-contrib_eqn2graph_eqn2graph.sh patch-contrib_gdiffmk_tests_runtests.in patch-contrib_grap2graph_grap2graph.sh patch-contrib_groffer_perl_groffer.pl patch-contrib_groffer_perl_roff2.pl patch-contrib_pdfmark_pdfroff.man patch-contrib_pdfmark_pdfroff.sh patch-contrib_pic2graph_pic2graph.sh patch-doc_fixinfo.sh patch-doc_groff.info-2 patch-gendef.sh patch-src_roff_groff_pipeline.c Log Message: Fix many temporary file handling issues, including in pdfroff (resolves CVE-2009-5044 / SA44999) Patches copied from: http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/groff/groff-1.20.1-owl-tmp.diff?rev=1.2 Modified for pkgsrc and excluded a documentaion change to doc/groff.texinfo that changes a `makeinfo' is too old warning into a fatal error. Added patch to make pdfroff.sh use -dSAFER See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538338 for details. @ text @a0 49 $NetBSD$ Fix many temporary file handling issues, including in pdfroff (resolves CVE-2009-5044 / SA44999) Patches copied from: http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/groff/groff-1.20.1-owl-tmp.diff?rev=1.2 Modified for pkgsrc and excluded a documentaion change to doc/groff.texinfo that changes a `makeinfo' is too old warning into a fatal error. --- configure.orig 2009-01-09 14:25:52.000000000 +0000 +++ configure @@@@ -12937,33 +12937,12 @@@@ if $ac_need_defaults; then test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers fi -# Have a temporary directory for convenience. Make it in the build tree -# simply because there is no reason against having it here, and in addition, -# creating and moving files from /tmp can sometimes cause problems. -# Hook for its removal unless debugging. -# Note that there is a small window in which the directory will not be cleaned: -# after its creation but before its name has been assigned to `$tmp'. +# Create a temporary directory, and hook for its removal unless debugging. +tmp="`mktemp -dt cs.XXXXXXXXXX`" || exit $debug || { - tmp= - trap 'exit_status=$? - { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status -' 0 - trap '{ (exit 1); exit 1; }' 1 2 13 15 -} -# Create a (secure) tmp directory for tmp files. - -{ - tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` && - test -n "$tmp" && test -d "$tmp" -} || -{ - tmp=./conf$$-$RANDOM - (umask 077 && mkdir "$tmp") -} || -{ - $as_echo "$as_me: cannot create a temporary directory in ." >&2 - { (exit 1); exit 1; } + trap 'exit_status=$?; rm -rf -- "$tmp" && exit $exit_status' EXIT + trap '{ (exit $?); exit $?; }' HUP INT QUIT PIPE TERM } # Set up the scripts for CONFIG_FILES section. @