groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 16/24: [docs]: Fix content nits.


From: G. Branden Robinson
Subject: [groff] 16/24: [docs]: Fix content nits.
Date: Tue, 27 Dec 2022 04:22:45 -0500 (EST)

gbranden pushed a commit to branch master
in repository groff.

commit 4ea64eeb36210494ebf8cfab00dd6b3fce89874e
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Dec 25 17:33:46 2022 -0600

    [docs]: Fix content nits.
    
    * Clarify discussion of end-of-input interaction with last possible
      output line.
    * Make claim about AT&T troff's special character repertoire more
      scrupulously correct.  Annotate in comments.
---
 doc/groff.texi  | 25 ++++++++++++++++---------
 man/groff.7.man |  9 +++++++--
 man/roff.7.man  |  4 ++--
 3 files changed, 25 insertions(+), 13 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index 35d6da2f4..10c5729de 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5752,12 +5752,13 @@ place the next text baseline off the page.  Rather than 
let that happen,
 start a new one, and again set the drawing position to one vee below the
 page top; this is a @dfn{page break}.
 
-When the last line of input text is also the last output line that can
-fit on the page, the break caused by the end of input will also break
-the page, producing a useless blank one.  Macro packages keep users from
-having to confront this difficulty by setting ``traps'' (@pxref{Traps});
-moreover, all but the simplest page layouts tend to have headers and
-footers, or at least bear vertical margins larger than one vee.
+When the last line of input text corresponds to the last output line
+that fits on the page, the break caused by the end of input will also
+break the page, producing a useless blank one.  Macro packages keep
+users from having to confront this difficulty by setting ``traps''
+(@pxref{Traps}); moreover, all but the simplest page layouts tend to
+have headers and footers, or at least bear vertical margins larger than
+one vee.
 
 
 @c =====================================================================
@@ -6765,9 +6766,15 @@ double quote.
 
 In GNU @code{troff}'s @acronym{AT&T} compatibility mode, these
 characters remain available as @code{\(rs} and @code{\(dq},
-respectively.  @acronym{AT&T} @code{troff} did not define these special
-characters, but any of its descendants can be made to support them.
-@xref{Device and Font Description Files}.
+respectively.  @acronym{AT&T} @code{troff} did not consistently define
+these special characters,
+@c It seems that AT&T troff never recognized \(rs, though DWB 3.3
+@c defined \(bs as an alias of "\" on its "Latin1" device, in
+@c deliberate(?) collision with the Bell System logo identifier.  It
+@c also defined \(dq for several devices (pcl, Latin1, nroff, ...) along
+@c with \(aq.
+but its descendants can be made to support them.  @xref{Device and Font
+Description Files}.
 
 If even that is not feasible, options remain.  To obtain a literal
 escape character in a macro argument, you can simply type it if you
diff --git a/man/groff.7.man b/man/groff.7.man
index 646c87488..cbb8327b1 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -1570,8 +1570,13 @@ respectively.
 .
 AT&T
 .I troff \" AT&T
-did not define these special characters,
-but any of its descendants can be made to support them.
+did not consistently define these special characters,
+.\" It seems that AT&T troff never recognized \(rs, though DWB 3.3
+.\" defined \(bs as an alias of "\" on its "Latin1" device, in
+.\" deliberate(?) collision with the Bell System logo identifier.  It
+.\" also defined \(dq for several devices (pcl, Latin1, nroff, ...)
+.\" along with \(aq.
+but its descendants can be made to support them.
 .
 See
 .MR groff_font @MAN5EXT@ .
diff --git a/man/roff.7.man b/man/roff.7.man
index 9c8b817d1..efc177355 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -611,8 +611,8 @@ this is a
 .
 .
 .P
-When the last line of input text is also the last output line that can
-fit on the page,
+When the last line of input text corresponds to the last output line
+that fits on the page,
 the break caused by the end of input will also break the page,
 producing a useless blank one.
 .



reply via email to

[Prev in Thread] Current Thread [Next in Thread]