gbranden pushed a commit to branch master
in repository groff.
commit 790a9c656f7465f863d22257b68dbd671c73c0b1
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Nov 24 20:20:59 2022 -0600
doc/groff.texi: Clarify a point.
Characters are copied "as-is" to output glyphs. The two _correspond_,
with much supplementary information in the case of the latter (type
size, slant, color, ...).
---
doc/groff.texi | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index eab61fbb4..5d4c3aaf3 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5024,13 +5024,13 @@ Barnum.
``Barnum'' doesn't begin a sentence! What to do? Let us meet our first
@dfn{escape sequence}, a series of input characters that give
-instructions to GNU @code{troff} instead of being copied as-is to output
-device glyphs.@footnote{This statement oversimplifes; there are escape
-sequences whose purpose is precisely to produce glyphs on the output
-device, and input characters that @emph{aren't} part of escape sequences
-can undergo a great deal of processing before getting to the output.}
-An escape sequence begins with the backslash character @code{\} by
-default, an uncommon character in natural language text, and is
+instructions to GNU @code{troff} instead of being used to construct
+output device glyphs.@footnote{This statement oversimplifes; there are
+escape sequences whose purpose is precisely to produce glyphs on the
+output device, and input characters that @emph{aren't} part of escape
+sequences can undergo a great deal of processing before getting to the
+output.} An escape sequence begins with the backslash character @code{\}
+by default, an uncommon character in natural language text, and is
@emph{always} followed by at least one other character, hence the term
``sequence''.
_______________________________________________
Groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
