gbranden pushed a commit to branch master
in repository groff.
commit 27ab75d024aea5a294b2448cb67b59abf9db10cb
Author: G. Branden Robinson <[email protected]>
AuthorDate: Wed Dec 10 16:35:18 2025 -0600
doc/groff.texi.in: Sync with groff_diff(7).
Parallelize line breaks between our Texinfo manual and groff_diff(7).
---
doc/groff.texi.in | 50 +++++++++++++++++++++++++++++++++++++-------------
1 file changed, 37 insertions(+), 13 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 89fc41f71..936929aa3 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -20434,19 +20434,43 @@ Hello!
@endExample
@cindex @code{\s}, incompatibilities with @acronym{AT&T} @code{troff}
-Normally, the syntax form @code{\s}@var{n} accepts only a single
-character (a digit) for @var{n}, consistently with other forms that
-originated in @acronym{AT&T} @code{troff}, like @code{\*}, @code{\$},
-@code{\f}, @code{\g}, @code{\k}, @code{\n}, and @code{\z}. In
-compatibility mode only, a non-zero@tie{}@var{n} must be in the range
-4--39. Legacy documents relying upon this quirk of parsing@footnote{The
-Graphic Systems C/A/T phototypesetter (the original device target for
-@acronym{AT&T} @code{troff}) supported only a few discrete type sizes
-in the range 6--36 points, so Ossanna contrived a special case in the
-parser to do what the user must have meant. Kernighan warned of this in
-the 1992 revision of CSTR@tie{}#54 (�2.3), and more recently, McIlroy
-referred to it as a ``living fossil''.} should migrate to another
-@code{\s} form.
+Normally,
+the syntax form
+@code{\s}@var{n}
+accepts only a single character
+(a digit)
+for
+@var{n},
+consistently with other forms that originated in
+@acronym{AT&T}
+@code{troff}, @c AT&T
+like
+@code{\*},
+@code{\f},
+@code{\g},
+@code{\k},
+@code{\n},
+and
+@code{\z}.
+In compatibility mode only,
+a non-zero@tie{}@var{n}
+must be in the range 4--39.
+Legacy documents relying upon this quirk of parsing@footnote{The
+Graphic Systems C/A/T phototypesetter
+(the original device target for
+@acronym{AT&T}
+@code{troff})
+supported only a few discrete type sizes
+in the range 6--36 points,
+so Ossanna contrived a special case in the parser
+to do what the user must have meant.
+Kernighan warned of this in the 1992 revision
+of CSTR@tie{}#54 (�2.3),
+and more recently,
+McIlroy referred to it as a ``living fossil''.}
+should migrate to another
+@code{\s}
+form.
@c BEGIN Keep in sync with groff_diff(7), subsection "Altered requests".
In compatibility mode,
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
