[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 01/01: doc/groff.texi: Further adjust .ss documentation.
From: |
G. Branden Robinson |
Subject: |
[groff] 01/01: doc/groff.texi: Further adjust .ss documentation. |
Date: |
Mon, 1 Jun 2020 09:33:54 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit 1b35343a5c7ddc3f972c086aab6a1794f16d9446
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Mon Jun 1 19:15:42 2020 +1000
doc/groff.texi: Further adjust .ss documentation.
Incorporate further feedback from Dave Kemper in Savannah #54101.
Make unambiguous that the newline-or-two-spaces-after-a-sentence rule is
an _input_ convention.
---
doc/groff.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/groff.texi b/doc/groff.texi
index 3b6f475..eae5300 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -6443,7 +6443,8 @@ if there are no arguments.
@cindex minimal inter-word spacing
@cindex space, between words
The first argument, the inter-word space size, is a minimum; if
-adjusted, it may increase.
+automatically adjusted (@pxref{Manipulating Filling and Adjusting}), it
+may increase.
@cindex inter-sentence spacing, additional
@cindex additional inter-sentence spacing
@@ -6472,8 +6473,8 @@ space that always precedes it may be.
If a second argument is never given to the @code{ss} request, GNU
@code{troff} separates sentences as @acronym{AT&T} @code{troff} does.
-In GNU @code{troff}, as in @acronym{AT&T} @code{troff}, a sentence
-should always be followed by either a newline or two spaces.
+In input to GNU @code{troff}, as with @acronym{AT&T} @code{troff}, a
+sentence should always be followed by either a newline or two spaces.
@cindex discardable horizontal space
@cindex space, discardable, horizontal
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 01/01: doc/groff.texi: Further adjust .ss documentation.,
G. Branden Robinson <=