Follow-up Comment #1, bug #68537 (group groff): Unfortunately, Deri's fix from the other bug breaks our "doc/ms.ms.in" document.
Most of the document output diff is spurious changes due to adjustment parity,
but the first few hunks make the problem clear.
$ ./build/test-groff -t -rLL=80n -ms -T utf8 -P -c build/doc/ms.ms >|ms.1.txt
$ git stash pop
...
$ git diff
diff --git a/tmac/s.tmac b/tmac/s.tmac
index 4052368d8..f862a1517 100644
--- a/tmac/s.tmac
+++ b/tmac/s.tmac
@@ -864,7 +864,7 @@ .de pg@end-text
.vs \n[fn@sep-dist]u
.nr fn@sep-dist \n[.v]
.ev
-.nr fn*text-num 0 1
+.nr fn*text-num 0
.nr fn*note-num 0 1
.nr fn*open 0
.\" Handle initialition tasks deferred until par module is set up.
@@ -884,6 +884,7 @@ .de @FS
.FS-MARK \\$@
.ie \\n[.$] .fn*do-FS "\\$1" no
.el \{\
+. nr ft*text-num +1
. ie \\n[fn*text-num]>\\n[fn*note-num] .fn*do-FS \\n+[fn*note-num]
. el .fn*do-FS
.\}
$ ./build/test-groff -t -rLL=80n -ms -T utf8 -P -c build/doc/ms.ms >|ms.2.txt
$ diff -U0 ms.[12].txt
--- ms.1.txt 2026-07-17 16:44:25.478399338 -0500
+++ ms.2.txt 2026-07-17 16:44:34.662374003 -0500
@@ -88 +88 @@
-The ms macros are the oldest surviving package for roff systems.[1] Whereas
man
+The ms macros are the oldest surviving package for roff systems.[0] Whereas
man
@@ -124,3 +124,3 @@
- [1] While manual pages are older, early ones used macros supplanted by the
man
-package of Seventh Edition Unix (1979). ms shipped with Sixth Edition
(1975)
-and was documented by Mike Lesk in a Bell Labs internal memorandum.
+While manual pages are older, early ones used macros supplanted by the man
pack‐
+age of Seventh Edition Unix (1979). ms shipped with Sixth Edition (1975)
and
+was documented by Mike Lesk in a Bell Labs internal memorandum.
@@ -377 +377 @@
-Only the simplest document lacks a title.[2] As its level of sophistication
(or
+Only the simplest document lacks a title.[0] As its level of sophistication
(or
@@ -389,2 +389,2 @@
- [2] Distinguish a document title from “titles”, which are what roff
systems
-call headers and footers collectively.
+Distinguish a document title from “titles”, which are what roff
systems call
+headers and footers collectively.
@@ -869 +869 @@
-pre arguments is a GNU extension.[3]
+pre arguments is a GNU extension.[0]
@@ -875,4 +875,4 @@
-│ weight——followed by post in the
previous font │
-│ style without intervening space, and preceded
by │
-│ pre similarly. Without arguments, ms styles
sub‐ │
-│ sequent text in bold until the next
paragraphing, │
+│ weight——followed by post in the
previous font │
+│ style without intervening space, and preceded
by │
+│ pre similarly. Without arguments, ms styles
sub‐ │
+│ sequent text in bold until the next
paragraphing, │
@@ -881 +881 @@
-│ .R [text [post [pre]]] As B, but use the roman style (upright text
of │
+│ .R [text [post [pre]]] As B, but use the roman style (upright text
of │
@@ -888 +888 @@
-│ .BI [text [post [pre]]] As B, but use a bold italic or bold oblique
style │
+│ .BI [text [post [pre]]] As B, but use a bold italic or bold oblique
style │
@@ -892,2 +892,2 @@
-│ .CW [text [post [pre]]] As B, but use a constant‐width (monospaced)
roman │
-│ typeface instead of bold. This is a
Research │
+│ .CW [text [post [pre]]] As B, but use a constant‐width (monospaced)
roman │
+│ typeface instead of bold. This is a
Research │
@@ -896 +896 @@
-│ .BX [text] Typeset text and draw a box around it. On
termi‐ │
+│ .BX [text] Typeset text and draw a box around it. On
termi‐ │
@@ -898,2 +898,2 @@
-│ ing is used instead. If you want text to
contain │
-│ space, use unbreakable space or horizontal
motion │
+│ ing is used instead. If you want text to
contain │
+│ space, use unbreakable space or horizontal
motion │
@@ -902,3 +902,3 @@
-│ .UL [text [post]] Typeset text with an _underline_. On
terminals, │
-│ text is bracketed with underscores (“_”).
post, │
-│ if present, is set after text with no
intervening │
+│ .UL [text [post]] Typeset text with an _underline_. On
terminals, │
+│ text is bracketed with underscores (“_”).
post, │
+│ if present, is set after text with no
intervening │
@@ -914,5 +914,5 @@
- [3] This idiosyncrasy arose through feature accretion; for example,
the B
-macro in Sixth Edition Unix ms (1975) accepted only one argument, the text to
be
-set in boldface. By Version 7 (1979) it recognized a second argument; in
1990,
-groff ms added a “pre” argument, placing it third to avoid breaking
support for
-older documents.
+This idiosyncrasy arose through feature accretion; for example, the B macro
in
+Sixth Edition Unix ms (1975) accepted only one argument, the text to be set
in
+boldface. By Version 7 (1979) it recognized a second argument; in 1990,
groff
+ms added a “pre” argument, placing it third to avoid breaking support for
older
+documents.
@@ -934,4 +934,4 @@
-│ .LG Set subsequent text in larger type (2
points │
-│ larger than the current size) until the next
type │
-│ size, paragraphing, or heading macro call.
Call │
-│ the macro multiple times to enlarge the type
size │
+│ .LG Set subsequent text in larger type (2
points │
+│ larger than the current size) until the next
type │
+│ size, paragraphing, or heading macro call.
Call │
+│ the macro multiple times to enlarge the type
size │
@@ -940 +940 @@
-│ .SM Set subsequent text in smaller type (2
points │
+│ .SM Set subsequent text in smaller type (2
points │
@@ -942,2 +942,2 @@
-│ size, paragraphing, or heading macro call.
Call │
-│ the macro multiple times to reduce the type
size │
+│ size, paragraphing, or heading macro call.
Call │
+│ the macro multiple times to reduce the type
size │
@@ -950 +950 @@
- pre and post arguments are typically used to simplify the attachment
of
+ pre and post arguments are typically used to simplify the attachment
of
@@ -952 +952 @@
-quence \% that would ordinarily start text must start pre instead to have
the
+quence \% that would ordinarily start text must start pre instead to have
the
@@ -958 +958 @@
- │ found one C language found one C language key‐ │
+ │ found one C language found one C language key‐ │
@@ -964 +964 @@
-You can use the output line continuation escape sequence \c to achieve the
same
+You can use the output line continuation escape sequence \c to achieve the
same
@@ -970 +970 @@
- │ found one C language found one C language key‐ │
+ │ found one C language found one C language key‐ │
@@ -979,2 +979,2 @@
-font family to Courier by setting \*[FAM] to “C”. You can then use
all four
-style macros above, returning to the default family (Times) with “.ds FAM
T”.
+font family to Courier by setting \*[FAM] to “C”. You can then use
all four
+style macros above, returning to the default family (Times) with “.ds
FAM T”.
@@ -997 +997 @@
- groff ms also offers strings to begin and end super‐ and
subscripting.
+ groff ms also offers strings to begin and end super‐ and
subscripting.
@@ -1014,2 +1014,2 @@
-for instance, you can use a bullet glyph (\[bu]) for unordered lists, a
number
-(or auto‐incrementing register) for numbered lists, or a word or
phrase for
+for instance, you can use a bullet glyph (\[bu]) for unordered lists, a
number
+(or auto‐incrementing register) for numbered lists, or a word or phrase
for
@@ -1017 +1017 @@
-ter PI before calling IP, you can later reorder the items in the list
without
+ter PI before calling IP, you can later reorder the items in the list
without
@@ -1077,2 +1077,2 @@
- In the enumerated list example, we created a register step with the nr
re‐
-quest, initializing it to zero and setting its auto‐increment to 1. Each
time
+ In the enumerated list example, we created a register step with the nr
re‐
+quest, initializing it to zero and setting its auto‐increment to 1. Each
time
@@ -1082 +1082 @@
- In the glossary example, observe how the IP macro places the definition
on
+ In the glossary example, observe how the IP macro places the definition
on
@@ -1084 +1084 @@
-there are a few workarounds we illustrate by modifying the example. First,
you
+there are a few workarounds we illustrate by modifying the example. First,
you
@@ -1086 +1086 @@
-you could apply the \p escape sequence to force a break. The space
following
+you could apply the \p escape sequence to force a break. The space
following
@@ -1088,4 +1088,4 @@
-the paragraph text on the same line as the term or label (if it fits)
then
-breaks the line. Finally, you may append a horizontal motion to the mark
with
-the \h escape sequence; using the same amount as the indentation ensures
that
-the mark is too wide for groff to treat it as “fitting” on the same line
as the
+the paragraph text on the same line as the term or label (if it fits)
then
+breaks the line. Finally, you may append a horizontal motion to the mark
with
+the \h escape sequence; using the same amount as the indentation ensures
that
+the mark is too wide for groff to treat it as “fitting” on the same line
as the
@@ -1136,2 +1136,2 @@
-You can indent a region of text while otherwise formatting it normally.
Such
-indented regions can be nested; change \n[PI] before each call to vary
the
+You can indent a region of text while otherwise formatting it normally.
Such
+indented regions can be nested; change \n[PI] before each call to vary
the
@@ -1148 +1148 @@
- This feature enables you to easily line up text under hanging and
indented
+ This feature enables you to easily line up text under hanging and
indented
@@ -1173,4 +1173,4 @@
-On occasion, you may want to keep several lines of text, or a region of a
docu‐
-ment, together on a single page, preventing an automatic page break within
cer‐
-tain boundaries. This can cause a page break to occur earlier than it
normally
-would. For example, you may want to keep two paragraphs together, or a
para‐
+On occasion, you may want to keep several lines of text, or a region of a
docu‐
+ment, together on a single page, preventing an automatic page break within
cer‐
+tain boundaries. This can cause a page break to occur earlier than it
normally
+would. For example, you may want to keep two paragraphs together, or a
para‐
@@ -1180,3 +1180,3 @@
- You can alternatively specify a floating keep: if a keep cannot fit on
the
-current page, ms holds it, allowing material following the keep (in the
source
-document) to fill the remainder of the current page. When the page breaks
by
+ You can alternatively specify a floating keep: if a keep cannot fit on
the
+current page, ms holds it, allowing material following the keep (in the
source
+document) to fill the remainder of the current page. When the page breaks
by
@@ -1196 +1196 @@
-of the next page. Use floating keeps to house large graphics or tables that
do
+of the next page. Use floating keeps to house large graphics or tables that
do
@@ -1208,3 +1208,3 @@
- As an alternative to the keep mechanism, the ne request forces a page
break
-if there is not at least the amount of vertical space specified in its
argument
-remaining on the page. One application of ne is to reserve space on the
page
+ As an alternative to the keep mechanism, the ne request forces a page
break
+if there is not at least the amount of vertical space specified in its
argument
+remaining on the page. One application of ne is to reserve space on the
page
@@ -1224,3 +1224,3 @@
-“Typeface and decoration” above. ms draws box lines close to the text
they en‐
-close so that they are usable within paragraphs. When boxing entire
paragraphs
-thus, you may improve their appearance by calling B1 after the first
paragraph‐
+“Typeface and decoration” above. ms draws box lines close to the text
they en‐
+close so that they are usable within paragraphs. When boxing entire
paragraphs
+thus, you may improve their appearance by calling B1 after the first
paragraph‐
@@ -1239 +1239 @@
-If you want a boxed keep to float, enclose the B1 and B2 calls within a pair
of
+If you want a boxed keep to float, enclose the B1 and B2 calls within a pair
of
@@ -1242,5 +1242,5 @@
- Displays turn off filling; lines of verse or program code are shown
with
-their lines broken as in the source document without requiring br requests
be‐
-tween lines. Displays can be kept on a single page or allowed to break
across
-pages. The DS macro begins a kept display of the layout specified in its
first
-argument; non‐kept displays are begun with dedicated macros
corresponding to
+ Displays turn off filling; lines of verse or program code are shown
with
+their lines broken as in the source document without requiring br requests
be‐
+tween lines. Displays can be kept on a single page or allowed to break
across
+pages. The DS macro begins a kept display of the layout specified in its
first
+argument; non‐kept displays are begun with dedicated macros
corresponding to
@@ -1271 +1271 @@
-│ .DS R .RD │ Begin right‐aligned display. This
is a │
+│ .DS R .RD │ Begin right‐aligned display.
This is a │
@@ -1277,4 +1277,4 @@
- groff ms inserts the distance stored in \n[DD] before and after each pair
of
-display macros; this is a Berkeley extension. This distance replaces any
adja‐
-cent inter‐paragraph distance or subsequent spacing prior to a section
heading.
-The DI register is a GNU extension; its value is an indentation applied to
dis‐
+ groff ms inserts the distance stored in \n[DD] before and after each pair
of
+display macros; this is a Berkeley extension. This distance replaces any
adja‐
+cent inter‐paragraph distance or subsequent spacing prior to a section
heading.
+The DI register is a GNU extension; its value is an indentation applied to
dis‐
@@ -1285,2 +1285,2 @@
- The display distance applies even in footnotes (discussed below), which
may
-cause a footnote with a display at its end to “emptily” spill to the next
page.
+ The display distance applies even in footnotes (discussed below), which
may
+cause a footnote with a display at its end to “emptily” spill to the
next page.
@@ -1331,2 +1331,2 @@
-and eqn. Mark text meant for preprocessors by enclosing it in pairs of
tokens
-as follows, with nothing between the dot and the macro name.
Preprocessors
+and eqn. Mark text meant for preprocessors by enclosing it in pairs of
tokens
+as follows, with nothing between the dot and the macro name.
Preprocessors
@@ -1339 +1339 @@
-│ .TS [H] Demarcate a table to be processed by the tbl
pre‐ │
+│ .TS [H] Demarcate a table to be processed by the tbl
pre‐ │
@@ -1341,4 +1341,4 @@
-│ table rows (often column headings) at the top of
each │
-│ new page the table spans, if applicable; calling
the │
-│ TH macro marks the end of such rows. The GNU
tbl(1) │
-│ man page provides a comprehensive reference to
the │
+│ table rows (often column headings) at the top of
each │
+│ new page the table spans, if applicable; calling
the │
+│ TH macro marks the end of such rows. The GNU
tbl(1) │
+│ man page provides a comprehensive reference to
the │
@@ -1347,2 +1347,2 @@
-│ .PS h v PS marks the start of a pic(1) preprocessor
diagram; │
-│ .PE either of PE or PF ends it, the latter with
“flyback” │
+│ .PS h v PS marks the start of a pic(1) preprocessor
diagram; │
+│ .PE either of PE or PF ends it, the latter with
“flyback” │
@@ -1350 +1350 @@
-│ manually or with a program such as xfig(1). h and
v │
+│ manually or with a program such as xfig(1). h
and v │
@@ -1354,3 +1354,3 @@
-│ .EQ [align [label]] Demarcate mathematics to be processed by the eqn
pre‐ │
-│ .EN processor. ms centers the equation by default;
align │
-│ can be C, L, or I to (explicitly) center,
left‐align, │
+│ .EQ [align [label]] Demarcate mathematics to be processed by the eqn
pre‐ │
+│ .EN processor. ms centers the equation by default;
align │
+│ can be C, L, or I to (explicitly) center,
left‐align, │
@@ -1360,2 +1360,2 @@
-│ .[ Demarcate a bibliographic citation to be processed
by │
-│ .] the refer preprocessor. The GNU refer(1) man
page │
+│ .[ Demarcate a bibliographic citation to be processed
by │
+│ .] the refer preprocessor. The GNU refer(1) man
page │
@@ -1367 +1367 @@
- When refer emits collected references (as might be done on a “Works
Cited”
+ When refer emits collected references (as might be done on a “Works
Cited”
@@ -1393 +1393 @@
- The following is an example of how to set up a table that may print
across
+ The following is an example of how to set up a table that may print
across
@@ -1410 +1410 @@
-Attempting to place a multi‐page table inside a keep can lead to unpleasant
re‐
+Attempting to place a multi‐page table inside a keep can lead to
unpleasant re‐
@@ -1421,2 +1421,2 @@
-This input formats a labelled equation. We used the SN-NO-DOT string to
base
-the equation label on the current heading number, giving us more flexibility
to
+This input formats a labelled equation. We used the SN-NO-DOT string to
base
+the equation label on the current heading number, giving us more flexibility
to
@@ -1441 +1441 @@
- groff options run preprocessors on the input: -e for eqn, -p for pic, -R
for
+ groff options run preprocessors on the input: -e for eqn, -p for pic, -R
for
@@ -1461,2 +1461,2 @@
-A footnote is typically anchored to a place in the text with a mark, which is
a
-small integer,[4] a symbol,† or arbitrary user‐specified text.
+A footnote is typically anchored to a place in the text with a mark, which
is a
+small integer,[0] a symbol,† or arbitrary user‐specified text.
@@ -1467 +1467 @@
-│ \** Place an automatic number, an automatically updated numeric
foot‐ │
+│ \** Place an automatic number, an automatically updated numeric
foot‐ │
@@ -1469 +1469 @@
-│ number it produces increments by one. Automatic numbers start
at │
+│ number it produces increments by one. Automatic numbers start
at │
@@ -1474 +1474 @@
- Enclose the footnote text in FS and FE macro calls to set it at the
nearest
+ Enclose the footnote text in FS and FE macro calls to set it at the
nearest
@@ -1480,4 +1480,4 @@
-│ .FS [mark] Begin a footnote. The FS-MARK hook (see below) is called
with │
-│ any supplied mark argument, which is then also placed at
the │
-│ beginning of the footnote text. If mark is omitted, the
next │
-│ pending automatic number enqueued by interpolation of
the * │
+│ .FS [mark] Begin a footnote. The FS-MARK hook (see below) is called
with │
+│ any supplied mark argument, which is then also placed at
the │
+│ beginning of the footnote text. If mark is omitted, the
next │
+│ pending automatic number enqueued by interpolation of the
* │
@@ -1489,3 +1489,3 @@
- You may not desire automatically numbered footnotes in spite of their
conve‐
-nience. You can indicate a footnote with a symbol or other text by
specifying
-its mark at the appropriate place (for example, by using \[dg] for the
dagger
+ You may not desire automatically numbered footnotes in spite of their
conve‐
+nience. You can indicate a footnote with a symbol or other text by
specifying
+its mark at the appropriate place (for example, by using \[dg] for the
dagger
@@ -1493,2 +1493,2 @@
-as arguments to FS or as part of the footnote text to disambiguate their
corre‐
-spondence. You may wish to use \*{ and \*} to superscript the mark at the
an‐
+as arguments to FS or as part of the footnote text to disambiguate their
corre‐
+spondence. You may wish to use \*{ and \*} to superscript the mark at the
an‐
@@ -1498,3 +1498,3 @@
-performed when the FS macro is called. It is passed the same arguments as
FS
-itself. An application of FS-MARK is anchor placement for a hyperlink
refer‐
-ence, so that a footnote can link back to its referential context. By
default,
+performed when the FS macro is called. It is passed the same arguments as
FS
+itself. An application of FS-MARK is anchor placement for a hyperlink
refer‐
+ence, so that a footnote can link back to its referential context. By
default,
@@ -1511 +1511 @@
- [4] like this numeric footnote
+like this numeric footnote
@@ -1542,3 +1542,3 @@
- Footnotes can be safely used within keeps and displays, but you should
avoid
-using automatically numbered footnotes within floating keeps. You can
place a
-second \** interpolation between a \** and its corresponding FS call as long
as
+ Footnotes can be safely used within keeps and displays, but you should
avoid
+using automatically numbered footnotes within floating keeps. You can place
a
+second \** interpolation between a \** and its corresponding FS call as long
as
@@ -1548,2 +1548,2 @@
- Footnote text is formatted as paragraphs are, using analogous
parameters.
-The registers FI, FPD, FPS, and FVS correspond to PI, PD, PS, and VS,
respec‐
+ Footnote text is formatted as paragraphs are, using analogous
parameters.
+The registers FI, FPD, FPS, and FVS correspond to PI, PD, PS, and VS,
respec‐
@@ -1552,2 +1552,2 @@
- The FF register controls the formatting of automatically numbered
footnote
-paragraphs, and those for which FS is given a mark argument, at the bottom of
a
+ The FF register controls the formatting of automatically numbered
footnote
+paragraphs, and those for which FS is given a mark argument, at the bottom
of a
@@ -1560 +1560 @@
-│ rounded by square brackets (on terminals). The footnote
para‐ │
+│ rounded by square brackets (on terminals). The footnote
para‐ │
@@ -1563 +1563 @@
-│ 1 As 0, but set mark as regular text, and follow an automatic
num‐ │
+│ 1 As 0, but set mark as regular text, and follow an automatic
num‐ │
@@ -1570,4 +1570,4 @@
- The default footnote line length is 11/12ths of the normal line length
for
-compatibility with the expectations of historical ms documents; you may wish
to
-set \*[FR] to 1 to align with contemporary typesetting practices. In
the
-past,[5] an FL register was used for the line length in footnotes; however,
set‐
+ The default footnote line length is 11/12ths of the normal line length
for
+compatibility with the expectations of historical ms documents; you may wish
to
+set \*[FR] to 1 to align with contemporary typesetting practices. In
the
+past,[0] an FL register was used for the line length in footnotes; however,
set‐
@@ -1575 +1575 @@
-line length in multi‐column arrangements.[6]
+line length in multi‐column arrangements.[0]
@@ -1577,2 +1577,2 @@
- [5] Unix Version 7 ms, its descendants, and groff ms prior to version
1.23.0
- [6] You could reset it after each call to 1C, 2C, or MC.
+Unix Version 7 ms, its descendants, and groff ms prior to version 1.23.0
+You could reset it after each call to 1C, 2C, or MC.
@@ -1591,4 +1591,4 @@
- Prefer \*[FR] over \n[FL] in contemporary documents. The footnote
line
-length is effectively computed as “column‐width * \*[FR]”. If you
require an
-absolute footnote line length, recall that roff formatters evaluate numeric
ex‐
-pressions strictly from left to right, without operator precedence
(parentheses
+ Prefer \*[FR] over \n[FL] in contemporary documents. The footnote
line
+length is effectively computed as “column‐width * \*[FR]”. If you
require an
+absolute footnote line length, recall that roff formatters evaluate numeric
ex‐
+pressions strictly from left to right, without operator precedence
(parentheses
@@ -1601,2 +1601,2 @@
-Changes to the footnote length ratio \*[FR] take effect with the next
footnote
-written in single‐column arrangements, but on the next page in
multiple‐column
+Changes to the footnote length ratio \*[FR] take effect with the next
footnote
+written in single‐column arrangements, but on the next page in
multiple‐column
@@ -1607,4 +1607,4 @@
-groff ms provides several strings that you can customize for your own
purposes,
-or redefine to adapt the macro package to languages other than English. It
is
-already localized for Czech, German, French, Italian, Polish, Russian,
Spanish,
-and Swedish. Load the desired localization macro package after ms; see
the
+groff ms provides several strings that you can customize for your own
purposes,
+or redefine to adapt the macro package to languages other than English. It
is
+already localized for Czech, German, French, Italian, Polish, Russian,
Spanish,
+and Swedish. Load the desired localization macro package after ms; see
the
@@ -1639 +1639 @@
- The default for \*[ABSTRACT] includes font selection escape sequences to
set
+ The default for \*[ABSTRACT] includes font selection escape sequences to
set
@@ -1659,2 +1659,2 @@
-Some of the special character escape sequences used in this document are
listed
-below. The minus sign glyph can also be accessed by the shorthand \−.
These
+Some of the special character escape sequences used in this document are
listed
+below. The minus sign glyph can also be accessed by the shorthand \−.
These
@@ -1684 +1684 @@
-ms’s default page layout arranges text in a single column with the page
number
+ms’s default page layout arranges text in a single column with the page
number
@@ -1690 +1690 @@
-There are multiple ways to produce headers and footers. One is to define
the
+There are multiple ways to produce headers and footers. One is to define
the
@@ -1692 +1692 @@
-and LF, CF, and RF to set the left, center, and right footers. This
approach
+and LF, CF, and RF to set the left, center, and right footers. This
approach
@@ -1695,2 +1695,2 @@
- Another method is to call macros that set headers or footers for
odd‐ or
-even‐numbered pages. Each such macro takes a delimited argument
separating the
+ Another method is to call macros that set headers or footers for
odd‐ or
+even‐numbered pages. Each such macro takes a delimited argument separating
the
@@ -1698,2 +1698,2 @@
-the neutral apostrophes (') shown below with any character not appearing in
the
-header or footer text.[7] These macros are Berkeley extensions.
+the neutral apostrophes (') shown below with any character not appearing in
the
+header or footer text.[0] These macros are Berkeley extensions.
@@ -1708,3 +1708,3 @@
- [7] ", #, and $ are also good choices because groff handles delimiters
in
-other contexts such as conditional and numeric expressions, where digits
0–9 and
-punctuation characters like +, -, *, /, &, and : are meaningful.
+", #, and $ are also good choices because groff handles delimiters in other
con‐
+texts such as conditional and numeric expressions, where digits 0–9 and
punctua‐
+tion characters like +, -, *, /, &, and : are meaningful.
@@ -2160 +2160 @@
- │ pdfmom[8] ‐‐roff ‐ms ‐rPDFFEAT=1 file.ms > file.pdf
│
+ │ pdfmom[0] ‐‐roff ‐ms ‐rPDFFEAT=1 file.ms > file.pdf
│
@@ -2163 +2163 @@
-Running an ms document with nroff, is only a single pass, so the above
advice
+Running an ms document with nroff, is only a single pass, so the above
advice
@@ -2166 +2166 @@
-All of the PDF features mentioned in this document can be disabled if the
groff
+All of the PDF features mentioned in this document can be disabled if the
groff
@@ -2171,2 +2171,2 @@
- [8] The command can be shortened to pdfms ‐rPDFFEAT=1 ... if you have
created
-a link to the pdfmom command called pdfms.
+The command can be shortened to pdfms ‐rPDFFEAT=1 ... if you have
created a
+link to the pdfmom command called pdfms.
@@ -2187,3 +2187,3 @@
-groff ms was written without reusing AT&T or Berkeley code. Since it takes
ad‐
-vantage of GNU troff’s extensions, it cannot be used with AT&T troff.
groff ms
-supports features described above as Berkeley and Research Tenth Edition
Unix
+groff ms was written without reusing AT&T or Berkeley code. Since it takes
ad‐
+vantage of GNU troff’s extensions, it cannot be used with AT&T troff.
groff ms
+supports features described above as Berkeley and Research Tenth Edition
Unix
@@ -2192,4 +2192,4 @@
- The internals of groff ms differ from those of AT&T and Berkeley ms.
Docu‐
-ments that depend upon undocumented behavioral details of those
implementations
-might not format as expected with groff ms. It therefore defines the
register
-GS, which AT&T and Berkeley do not use, as 1. A document can test its value
to
+ The internals of groff ms differ from those of AT&T and Berkeley ms.
Docu‐
+ments that depend upon undocumented behavioral details of those
implementations
+might not format as expected with groff ms. It therefore defines the
register
+GS, which AT&T and Berkeley do not use, as 1. A document can test its value
to
@@ -2198 +2198 @@
- The error‐handling policy of groff ms is to detect and report errors,
rather
+ The error‐handling policy of groff ms is to detect and report errors,
rather
@@ -2201 +2201 @@
- Research Tenth Edition Unix supported P1/P2 macros to bracket code
examples;
+ Research Tenth Edition Unix supported P1/P2 macros to bracket code
examples;
@@ -2204 +2204 @@
- groff ms does not work in GNU troff’s AT&T compatibility mode. If
loaded
+ groff ms does not work in GNU troff’s AT&T compatibility mode. If
loaded
@@ -2207 +2207 @@
- Multiple line spacing is not supported. Use a larger vertical spacing
in‐
+ Multiple line spacing is not supported. Use a larger vertical spacing
in‐
@@ -2210,2 +2210,2 @@
- groff ms uses the same header and footer defaults in both nroff and
troff
-modes as AT&T ms does in troff mode; AT&T’s default in nroff mode is to
put the
+ groff ms uses the same header and footer defaults in both nroff and
troff
+modes as AT&T ms does in troff mode; AT&T’s default in nroff mode is to put
the
@@ -2216,2 +2216,2 @@
-cause a reset of formatting parameters, and may change the indentation; they
do
-so not by incrementing or decrementing it, but by setting it absolutely.
This
+cause a reset of formatting parameters, and may change the indentation; they
do
+so not by incrementing or decrementing it, but by setting it absolutely.
This
@@ -2221,4 +2221,4 @@
- AT&T ms interpreted the values of the registers PS and VS in points, and
did
-not support the use of scaling units with them. groff ms interprets values
of
-the registers PS, VS, FPS, and FVS equal to or larger than 1,000 (one
thousand)
-as decimal fractions multiplied by 1,000.[9] This threshold makes use of a
scal‐
+ AT&T ms interpreted the values of the registers PS and VS in points, and
did
+not support the use of scaling units with them. groff ms interprets values
of
+the registers PS, VS, FPS, and FVS equal to or larger than 1,000 (one
thousand)
+as decimal fractions multiplied by 1,000.[0] This threshold makes use of a
scal‐
@@ -2237,2 +2237,2 @@
- [9] Register values are converted to and stored as basic units. See
“Measure‐
-ments” in the groff Texinfo manual or in groff(7).
+Register values are converted to and stored as basic units. See
“Measurements”
+in the groff Texinfo manual or in groff(7).
@@ -2258 +2258 @@
-different format to it if desired.[10]
+different format to it if desired.[0]
@@ -2260,4 +2260,4 @@
- The AT&T ms manual documents registers CW and GW as setting the default
col‐
-umn width and “intercolumn gap”, respectively, and which applied when
MC was
-called with fewer than two arguments. groff ms instead treats MC without
argu‐
-ments as synonymous with 2C; there is thus no occasion for a default
column
+ The AT&T ms manual documents registers CW and GW as setting the default
col‐
+umn width and “intercolumn gap”, respectively, and which applied when
MC was
+called with fewer than two arguments. groff ms instead treats MC without
argu‐
+ments as synonymous with 2C; there is thus no occasion for a default
column
@@ -2267 +2267 @@
- The AT&T ms manual did not document the QI register; Berkeley and groff
ms
+ The AT&T ms manual did not document the QI register; Berkeley and groff
ms
@@ -2272,2 +2272,2 @@
-Several macros described in the Unix Version 7 ms documentation are
unimple‐
-mented by groff ms because they are specific to the requirements of
documents
+Several macros described in the Unix Version 7 ms documentation are
unimple‐
+mented by groff ms because they are specific to the requirements of
documents
@@ -2276,2 +2276,2 @@
-eral document type formats (EG, IM, MF, MR, TM, TR), were meaningful only
in
-conjunction with the use of certain document types (AT, CS, CT, OK, SG),
stored
+eral document type formats (EG, IM, MF, MR, TM, TR), were meaningful only
in
+conjunction with the use of certain document types (AT, CS, CT, OK, SG),
stored
@@ -2279,4 +2279,4 @@
-definition over time (UX). To compatibly render historical ms documents
using
-these macros, we advise your documents to invoke the rm request to remove
any
-such macros it uses and then define replacements with an authentically
typeset
-original at hand.[11] For informal purposes, a simple definition of UX
should
+definition over time (UX). To compatibly render historical ms documents
using
+these macros, we advise your documents to invoke the rm request to remove
any
+such macros it uses and then define replacements with an authentically
typeset
+original at hand.[0] For informal purposes, a simple definition of UX
should
@@ -2298,7 +2298,7 @@
- [10] If you redefine the ms PT macro and desire special treatment of
certain
-page numbers (like “1”), you may need to handle a non‐Arabic page
number format,
-as groff ms’s PT does; see the macro package source. groff ms aliases
the PN
-register to %.
- [11] Removal beforehand is necessary because groff ms aliases these
macros
-with a diagnostic one; you want to reorient the aliased name before
(re‐)popu‐
-lating the macro.
+If you redefine the ms PT macro and desire special treatment of certain
page
+numbers (like “1”), you may need to handle a non‐Arabic page number
format, as
+groff ms’s PT does; see the macro package source. groff ms aliases the PN
reg‐
+ister to %.
+Removal beforehand is necessary because groff ms aliases these macros with a
di‐
+agnostic one; you want to reorient the aliased name before
(re‐)populating the
+macro.
Kicking this out past 1.25. I think I know how to work around this for Deri's
groff-pdf-features.ms document.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68537>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
