[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 15/35: [docs]: Improve terminological discipline.
From: |
G. Branden Robinson |
Subject: |
[groff] 15/35: [docs]: Improve terminological discipline. |
Date: |
Mon, 25 Oct 2021 03:32:37 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit f2833a9fe6619c5fd0cc2b5f543d8a656992badb
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sat Oct 23 12:55:33 2021 +1100
[docs]: Improve terminological discipline.
* Say "escape sequence(s)" instead of "escape(s)".
* Clarify cardinality of matching of opening brace escape sequences.
* Tighten wording.
---
doc/groff.texi | 31 ++++++++++++++++---------------
man/groff.7.man | 18 +++++++++---------
2 files changed, 25 insertions(+), 24 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index b4deeb2..ac6cab4 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -11906,27 +11906,28 @@ requests may be interposed between the @code{ie}
branch and the
@cindex conditional block, end (@code{\@}})
@cindex block, conditional, begin (@code{\@{})
@cindex block, conditional, end (@code{\@}})
-@cindex brace escapes (@code{\@{}, @code{\@}})
-@cindex escapes, brace (@code{\@{}, @code{\@}})
-@cindex opening brace escape (@code{\@}})
-@cindex closing brace escape (@code{\@})}
-@cindex brace escape, opening (@code{\@})}
-@cindex brace escape, closing (@code{\@})}
+@cindex brace escape sequences (@code{\@{}, @code{\@}})
+@cindex escape sequences, brace (@code{\@{}, @code{\@}})
+@cindex opening brace escape sequence (@code{\@}})
+@cindex closing brace escape sequence (@code{\@})}
+@cindex brace escape sequence, opening (@code{\@})}
+@cindex brace escape sequence, closing (@code{\@})}
It is frequently desirable for a control structure to govern more than
one request, call more than one macro, span more than one input line of
-text, or mix the foregoing. The opening and closing brace escapes
-@code{\@{} and @code{\@}} perform such grouping. Brace escapes can be
-used outside of control structures, but when they are they have no
-meaning and produce no output.
+text, or mix the foregoing. The opening and closing brace escape
+sequences @code{\@{} and @code{\@}} perform such grouping. Brace escape
+sequences outside of control structures have no meaning and produce no
+output.
@code{\@{} should appear (after optional spaces and tabs) immediately
subsequent to the request's conditional expression. @code{\@}} should
appear on a line with other occurrences of itself as necessary to match
-@code{\@{} escapes. It can be preceded by a control character, spaces,
-and tabs. Input after a @code{\@}} escape on the same line is processed
-only if all of the preceding conditions to which the escapes correspond
-are true. Furthermore, a @code{\@}} closing the body of a @code{while}
-request (discussed below) must be the last such escape on an input line.
+@code{\@{} sequences. It can be preceded by a control character,
+spaces, and tabs. Input after any quantity of @code{\@}} sequence 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
+escape sequence on an input line.
@Example
A
diff --git a/man/groff.7.man b/man/groff.7.man
index 9edcefd..cae0b6a 100644
--- a/man/groff.7.man
+++ b/man/groff.7.man
@@ -971,7 +971,7 @@ and then the remainder of the line
.I anything
is interpreted as if it were an input line.
.
-Any number of spaces between arguments to requests serves only to
+Any quantity of spaces between arguments to requests serves only to
separate them;
leading spaces in
.I anything
@@ -998,14 +998,14 @@ call more than one macro,
span more than one text line,
or mix the foregoing.
.
-The opening and closing brace escapes
+The opening and closing brace escape sequences
.esc {
and
.esc }
perform such grouping.
.
-Brace escapes can be used outside of control structures,
-but when they are they have no meaning and produce no output.
+Brace escape sequences outside of control structures have no meaning and
+produce no output.
.
.
.P
@@ -1018,23 +1018,23 @@ immediately subsequent to the request's conditional
expression.
should appear on a line with other occurrences of itself as necessary to
match
.esc {
-escapes.
+sequences.
.
It can be preceded by a control character,
spaces,
and tabs.
.
-Input after a
+Input after any quantity of
.esc }
-escape on the same line is only processed if all the preceding
-conditions to which the escapes correspond are true.
+sequences on the same line is only processed if all the preceding
+conditions to which they correspond are true.
.
Furthermore,
a
.esc }
closing the body of a
.request .while
-request must be the last such escape on an input line.
+request must be the last such escape sequence on an input line.
.
.
.\" ====================================================================
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 15/35: [docs]: Improve terminological discipline.,
G. Branden Robinson <=