gbranden pushed a commit to branch master
in repository groff.
commit dd956f4e4831f668a76a62112e7a99a472c4e522
Author: G. Branden Robinson <[email protected]>
AuthorDate: Sun Dec 25 17:24:59 2022 -0600
doc/groff.texi: Fix style and markup nit.
* Clarify meaning of "productive" input lines.
* Set a word with Texinfo @slanted command instead of @dfn when
introducing but not formally defining it.
---
doc/groff.texi | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index 3710f2ec1..35d6da2f4 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -8082,14 +8082,14 @@ To clearly present the next couple of requests, we must
introduce the
concept of ``productive'' input lines. A @dfn{productive input line} is
one that directly produces formatted output. Text lines produce output,
as do control lines containing requests like @code{tl} or escape
-sequences like @code{\D}. Macro calls are not themselves productive,
-but their interpolated contents can be; macro calls may therefore be
-@emph{indirectly} productive. An empty request, and requests and escape
-sequences that define registers or strings or alter the formatting
-environment (such as typeface changes) are @emph{not} productive. The
-output line continuation escape sequence @code{\c} ``connects'' two
-input lines that would otherwise be counted separately. @xref{Line
-Continuation}.
+sequences like @code{\D}. Macro calls are not @emph{directly}
+productive, and thus not counted, but their interpolated contents can
+be. Empty requests, and requests and escape sequences that define
+registers or strings or alter the formatting environment (as with
+changes to the size, face, height, slant, or color of the type) are
+not productive. The output line continuation escape sequence @code{\c}
+``connects'' two input lines that would otherwise be counted separately.
+@xref{Line Continuation}.
@Example
@c .ll 56n
@@ -8307,8 +8307,8 @@ request in the absence of a hyphenation language is an
error.
The request is ignored if there are no parameters.
@endDefreq
-These are known as hyphenation @emph{exceptions} in the expectation that
-most users will avail themselves of automatic hyphenation; these
+These are known as hyphenation @slanted{exceptions} in the expectation
+that most users will avail themselves of automatic hyphenation; these
exceptions override any rules that would normally apply to a word
matching a hyphenation exception defined with @code{hw}.
_______________________________________________
Groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
