gbranden pushed a commit to branch master
in repository groff.
commit 7c844c881ff1b1c4e748f0f40039d9f3e984e145
Author: G. Branden Robinson <[email protected]>
AuthorDate: Fri May 30 23:43:02 2025 -0500
doc/groff.texi.in: Expand description of `\p`.
Explain what I think is its idiomatic application, thanks to the late W.
Richard Stevens.
---
doc/groff.texi.in | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 216ed23a6..73e38b6a8 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -8449,6 +8449,30 @@ sequence is itself neither a break nor a space of any
kind; it can thus
be placed in the middle of a word to cause a break at the end of that
word.
+@code{\p} is typically used for fine-tuning of typeset output
+late in the document revision process.
+One of its applications is prevention of a break
+after an explicit hyphen when this occurs in an undesired place,
+such as at the end of a verso page,
+or before a displayed figure.
+The hyphenation mode can be configured to prevent breaks
+after
+@emph{automatically}
+placed hyphens,
+but not explicit ones
+(@pxref{Manipulating Hyphenation}).
+What one can do in this scenario
+is place @code{\p} at the end of the word
+@emph{before}
+the one that breaks undesirably.
+
+@Example
+.ll 1.375i
+The next data were out-of-band. \" breaks after "out-"
+.br
+The next data were\p out-of-band. \" breaks after "were"
+@endExample
+
Breaking with immediate adjustment can produce ugly results since GNU
@code{troff} doesn't have a sophisticated paragraph-building algorithm,
as @TeX{} has, for example. Instead, GNU @code{troff} fills and adjusts
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
