gbranden pushed a commit to branch master
in repository groff.
commit a3072b2e479f5759ae4899fa8c25726d217e77d4
Author: G. Branden Robinson <[email protected]>
AuthorDate: Mon Nov 3 00:21:45 2025 -0600
[doc,man]: Improve page geometry material.
Clarify. Favor present tense over future. Syncronize man page and
Texinfo.
---
doc/groff.texi.in | 42 ++++++++++++++++++++++++++----------------
man/roff.7.man | 22 +++++++++++-----------
2 files changed, 37 insertions(+), 27 deletions(-)
diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index 7c0f33cb3..d6f79abb1 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -6351,22 +6351,32 @@ see @ref{Line Layout} and
@cindex break, page
@cindex page ejection
@cindex ejection, page
-Vertical spacing has an impact on page-breaking decisions. Generally,
-when a break occurs, the formatter moves the drawing position to the
-next text baseline automatically. If the formatter were already writing
-to the last line that would fit on the page, advancing by one vee would
-place the next text baseline off the page. Rather than let that happen,
-@code{roff} formatters instruct the output driver to eject the page,
-start a new one, and again set the drawing position to one vee below the
-page top; this is a @dfn{page break}.
-
-When the last line of input text corresponds to the last output line
-that fits on the page, the break caused by the end of input will also
-break the page, producing a useless blank one. Macro packages keep
-users from having to confront this difficulty by setting ``traps''
-(@pxref{Traps}); moreover, all but the simplest page layouts tend to
-have headers and footers, or at least bear vertical margins of at least
-one vee.
+Vertical spacing has an impact on page-breaking decisions.
+Generally,
+when a break occurs,
+the formatter automatically moves the drawing position
+to the next text baseline.
+If the formatter were already writing
+to the last line that fits on the page,
+advancing by one vee would place the next text baseline off the page.
+Rather than let that happen,
+@code{roff}
+formatters instruct the output driver to eject the page,
+start a new one,
+and again place the drawing position one vee below the page top;
+this is a
+@dfn{page break}.
+
+When the last line of input text
+corresponds to the last output line that fits on the page,
+the break caused by the end of input also breaks the page,
+producing a useless blank one.
+Macro packages keep users from having to confront this difficulty
+by setting ``traps''
+(@pxref{Traps});
+moreover,
+all but the simplest page layouts tend to have headers and footers,
+or at least bear vertical margins of at least one vee.
@c END Keep parallel with subsection "Page geometry" of roff(7).
diff --git a/man/roff.7.man b/man/roff.7.man
index 2d8a738b4..9ab827f5d 100644
--- a/man/roff.7.man
+++ b/man/roff.7.man
@@ -625,30 +625,30 @@ Vertical spacing has an impact on page-breaking decisions.
.
Generally,
when a break occurs,
-the formatter moves the drawing position to the next text baseline
-automatically.
+the formatter automatically moves the drawing position
+to the next text baseline.
.
-If the formatter were already writing to the last line that would fit on
-the page,
+If the formatter were already writing
+to the last line that fits on the page,
advancing by one vee would place the next text baseline off the page.
.
Rather than let that happen,
.I roff
formatters instruct the output driver to eject the page,
start a new one,
-and again set the drawing position to one vee below the page top;
+and again place the drawing position one vee below the page top;
this is a
-.I page break.
+.I "page break."
.
.
.P
-When the last line of input text corresponds to the last output line
-that fits on the page,
-the break caused by the end of input will also break the page,
+When the last line of input text
+corresponds to the last output line that fits on the page,
+the break caused by the end of input also breaks the page,
producing a useless blank one.
.
-Macro packages keep users from having
-to confront this difficulty by setting \[lq]traps\[rq];
+Macro packages keep users from having to confront this difficulty
+by setting \[lq]traps\[rq];
.\" (@pxref{Traps});
moreover,
all but the simplest page layouts tend to have headers and footers,
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
