groff-commit
[Top][All Lists]
Advanced

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

[groff] 08/10: doc/groff.texi: Fix content and style nits.


From: G. Branden Robinson
Subject: [groff] 08/10: doc/groff.texi: Fix content and style nits.
Date: Fri, 5 Aug 2022 03:52:25 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit 70edf590db3be6800262e273641bef0d5804b1b9
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Aug 4 23:54:24 2022 -0500

    doc/groff.texi: Fix content and style nits.
    
    - Revise leader/table of contents example.
    - Migrate terminology: "escape" -> "escape sequence".
    - Fix grammar nits (use plurals more consistently).
    - Move misplaced modifiers (the dread "only").
    - Bump document date.
    
    * man/groff.7.man:
    * man/groff_diff.7.man: Sync.
---
 doc/groff.texi       | 60 ++++++++++++++++++++++++++++------------------------
 man/groff.7.man      |  2 +-
 man/groff_diff.7.man | 15 +++++++------
 man/groff_font.5.man |  4 ++--
 4 files changed, 44 insertions(+), 37 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index 2e6a1325a..073fa98b3 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -468,7 +468,7 @@ developing GNU and promoting software freedom.''
 @title groff
 @subtitle The GNU implementation of @code{troff}
 @subtitle Edition 1.23.0
-@subtitle June 2022
+@subtitle August 2022
 @author Trent@tie{}A.@: Fisher
 @author Werner Lemberg
 @author G.@tie{}Branden Robinson
@@ -8089,12 +8089,13 @@ sensible places without hyphens.
 @cindex disabling hyphenation (@code{\%})
 @cindex hyphenation, disabling (@code{\%})
 To tell GNU @code{troff} how to hyphenate words as they occur in input,
-use the @code{\%} escape, also known as the @dfn{hyphenation character}.
-Each instance within a word indicates to GNU @code{troff} that the
-word may be hyphenated at that point, while prefixing a word with this
-escape prevents it from being otherwise hyphenated.  This mechanism
-affects only that occurrence of the word; to change the hyphenation of a
-word for the remainder of input processing, use the @code{hw} request.
+use the @code{\%} escape sequence; it is the default @dfn{hyphenation
+character}.  Each instance within a word indicates to GNU @code{troff}
+that the word may be hyphenated at that point, while prefixing a word
+with this escape prevents it from being otherwise hyphenated.  This
+mechanism affects only that occurrence of the word; to change the
+hyphenation of a word for the remainder of input processing, use the
+@code{hw} request.
 
 @cindex @code{\X}, followed by @code{\%}
 @cindex @code{\Y}, followed by @code{\%}
@@ -8962,17 +8963,20 @@ is recognized; any excess is ignored.
 
 @cindex table of contents
 @cindex contents, table of
-For a table of contents, to name an example, tab stops may be defined so
-that the section number is one tab stop, the title is the second with
-the remaining space being filled with a line of dots, and then the page
-number slightly separated from the dots.
+A table of contents, for example, may define tab stops after a section
+number, a title, and a gap to be filled with leader dots.  The page
+number follows the leader, after a right-aligned final tab stop wide
+enough to house the largest page number occurring in the document.
 
 @Example
-.ds entry 1.1\tBackground\a\t12
-.lc .
-.ta 1i 5i +.25i
-\*[entry]
-    @result{} 1.1  Foo..........................................  12
+.ds entry1 19.\tThe Prophet\a\t98
+.ds entry2 20.\tAll Astir\a\t101
+.ta .5i 4.5i +.5iR
+.nf
+\*[entry1]
+\*[entry2]
+    @result{} 19.  The Prophet.............................   98
+    @result{} 20.  All Astir...............................  101
 @endExample
 
 @c ---------------------------------------------------------------------
@@ -12376,8 +12380,8 @@ sequences used to obtain them.  In the previous 
example, @samp{|} and
 same positions, so the comparands are equal.  If @samp{.ft@tie{}I} had
 been added before the @samp{.ie}, they would differ: the first @samp{|}
 would produce an italic @samp{|}, not a roman one.  Motions must match
-in orientation and magnitude to within the applicable horizontal or
-vertical motion quantum of the device, after rounding.  @samp{.if
+in orientation and magnitude to within the applicable horizontal and
+vertical motion quanta of the device, after rounding.  @samp{.if
 "\u\d"\v'0'"} is false even though both comparands result in zero net
 motion, because motions are not interpreted or optimized but sent as-is
 to the output.@footnote{Because formatting of the comparands takes place
@@ -12579,7 +12583,7 @@ produce no output.
 subsequent to the request's conditional expression.  @code{\@}} should
 appear on a line with other occurrences of itself as necessary to match
 @code{\@{} sequences.  It can be preceded by a control character,
-spaces, and tabs.  Input after any quantity of @code{\@}} sequence on
+spaces, and tabs.  Input after any quantity of @code{\@}} sequences on
 the same line is processed only if all of the preceding conditions to
 which they correspond are true.  Furthermore, a @code{\@}} closing the
 body of a @code{while} request (discussed below) must be the last such
@@ -12687,10 +12691,10 @@ the @code{while} request's @dfn{body}.
 GNU @code{troff} treats the body of a @code{while} request similarly to
 that of a @code{de} request (albeit one not read in copy
 mode@footnote{@xref{Copy Mode}.}), but stores it under an internal name
-and deletes it when it exits.  The operation of a macro containing a
-@code{while} request can slow significantly if the @code{while} body is
-large.  Each time the macro is executed, the @code{while} body is parsed
-and stored again.
+and deletes it when the loop finishes.  The operation of a macro
+containing a @code{while} request can slow significantly if the
+@code{while} body is large.  Each time the macro is executed, the
+@code{while} body is parsed and stored again.
 
 @Example
 .de xxx
@@ -12707,7 +12711,7 @@ and stored again.
 @noindent
 An often better solution---and one that is more portable, since
 @acronym{AT&T} @code{troff} lacked the @code{while} request---is to
-instead write a recursive macro.  It will only be parsed
+instead write a recursive macro.  It will be parsed only
 once.@footnote{unless you redefine it}
 
 @Example
@@ -12871,9 +12875,9 @@ interpreted---without disturbing that state when it is 
finished.
 @Defreq {de1, name [@Var{end}]}
 The @code{de1} request defines a macro to be interpreted with
 compatibility mode disabled.  When @var{name} is called, compatibility
-mode enablement status is saved, and when @var{name} finishes, it is
-restored.  Observe the extra backlash before the interpolation of
-register @samp{xxx}; we'll explore this subject in @ref{Copy Mode}.
+mode enablement status is saved; it is restored when the call completes.
+Observe the extra backlash before the interpolation of register
+@samp{xxx}; we'll explore this subject in @ref{Copy Mode}.
 
 @Example
 .nr xxx 12345
@@ -18138,7 +18142,7 @@ The form of the @var{metrics} field is as follows.
 There must not be any spaces, tabs, or newlines between these
 @dfn{subfields} (which have been split here into two lines only for
 better legibility).  The subfields are in basic units expressed as
-decimal integers.  Unspecified subfields default to be@tie{}@code{0}.
+decimal integers.  Unspecified subfields default to@tie{}@code{0}.
 Since there is no associated binary format, these values are not
 required to fit into the C language data type @samp{char} as they are in
 @acronym{AT&T} device-independent @code{troff}.
diff --git a/man/groff.7.man b/man/groff.7.man
index 85f28670b..fa960e0e4 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -1185,7 +1185,7 @@ and tabs.
 .
 Input after any quantity of
 .esc }
-sequences on the same line is only processed if all the preceding
+sequences on the same line is processed only if all the preceding
 conditions to which they correspond are true.
 .
 Furthermore,
diff --git a/man/groff_diff.7.man b/man/groff_diff.7.man
index 862d3bf62..0c53f7d82 100644
--- a/man/groff_diff.7.man
+++ b/man/groff_diff.7.man
@@ -1930,11 +1930,13 @@ A device's default stroke and fill colors are not 
necessarily the same.
 .
 .TP
 .BI .de1\~ xx\~yy
-Similar to
-.BR .de ,
-but compatibility mode is switched off during execution.
+Define a macro to be interpreted with compatibility mode disabled.
 .
-On entry, the current compatibility mode is saved and restored at exit.
+When
+.I xx
+is called,
+compatibility mode enablement status is saved;
+it is restored when the call completes.
 .
 .
 .TP
@@ -3588,7 +3590,8 @@ request similarly to that of a
 .B de
 request
 (albeit one not read in copy mode),
-but stores it under an internal name and deletes it when it exits.
+but stores it under an internal name and deletes it when the loop
+finishes.
 .
 The operation of a macro containing a
 .B while
@@ -3608,7 +3611,7 @@ lacked the
 .B while
 request\[em]is to instead write a recursive macro.
 .
-It will only be parsed once (unless you redefine it).
+It will be parsed only once (unless you redefine it).
 .
 To prevent infinite loops,
 the default number of available recursion levels is 1,000 or somewhat
diff --git a/man/groff_font.5.man b/man/groff_font.5.man
index c44de0321..855e1692a 100644
--- a/man/groff_font.5.man
+++ b/man/groff_font.5.man
@@ -802,8 +802,8 @@ or newlines between these
 .
 which are in basic units expressed as decimal integers.
 .
-Unspecified subfields default to
-.RB be\~ 0 .
+Unspecified subfields default
+.RB to\~ 0 .
 .
 Since there is no associated binary format,
 these values are not required to fit into the C language data type



reply via email to

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