gbranden pushed a commit to branch master
in repository groff.

commit e581a4f7f014beaf4ce4511e935c15c9b2f75165
Author: G. Branden Robinson <[email protected]>
AuthorDate: Fri May 8 21:32:14 2026 -0500

    [doc,man]: Clarify, sync font description stuff.
    
    * Continue terminological reform: employ term "advance width".
    * Fix misnomer: "bit mask" becomes "bit pair".  Why do people
      characterize all bit vectors as "masks"?
    * Break Texinfo input lines in convenient places for roffing and
      diffing.
---
 doc/groff.texi.in    | 31 ++++++++++++++++++++++---------
 man/groff_font.5.man |  8 +++++---
 2 files changed, 27 insertions(+), 12 deletions(-)

diff --git a/doc/groff.texi.in b/doc/groff.texi.in
index ed5d6e11f..5efebdace 100644
--- a/doc/groff.texi.in
+++ b/doc/groff.texi.in
@@ -24485,7 +24485,8 @@ as they are in @acronym{AT&T} device-independent
 
 The
 @var{width}
-subfield gives the width of the glyph.
+subfield gives the advance width of the glyph;
+recall @ref{Artificial Fonts}.
 The
 @var{height}
 subfield gives the height of the glyph
@@ -24521,13 +24522,24 @@ to add after a slanted glyph
 to be followed by a subscript;
 it should be less than the italic correction.
 
-For fonts used with typesetters, the @var{type} field gives a featural
-description of the glyph: it is a bit mask recording whether the glyph
-is an ascender, descender, both, or neither.  When a @code{\w} escape
-sequence is interpolated, these values are bitwise or-ed together for
-each glyph and stored in the @code{nr} register.  In font descriptions
-for terminals, all glyphs might have a type of zero, regardless of their
-appearance.
+For fonts used with typesetters,
+the
+@var{type}
+field gives a featural description of the glyph:@:
+it is a bit pair recording whether the glyph is an ascender,
+descender,
+both,
+or neither.
+When a
+@code{\w}
+escape sequence is interpolated,
+these values are bitwise or-ed together
+for each glyph and stored in the
+@code{ct}
+register.
+In font descriptions for terminals,
+all glyphs might have a type of zero,
+regardless of their appearance.
 
 @table @code
 @item 0
@@ -24549,7 +24561,8 @@ parentheses in some fonts.
 
 The
 @var{index}
-field is an integer that uniquely identifies a glyph within the font;
+field is an integer
+that uniquely identifies a glyph within the font;
 any integer is accepted as input,@footnote{that is,
 any integer parsable
 by the C standard library's
diff --git a/man/groff_font.5.man b/man/groff_font.5.man
index a6c04565f..9d0af7ee3 100644
--- a/man/groff_font.5.man
+++ b/man/groff_font.5.man
@@ -857,7 +857,8 @@ as they are in AT&T device-independent
 .P
 The
 .I width
-subfield gives the width of the glyph.
+subfield gives the advance width of the glyph.
+.\" recall @ref{Artificial Fonts}.
 .
 The
 .I height
@@ -907,7 +908,7 @@ For fonts used with typesetters,
 the
 .I type
 field gives a featural description of the glyph:
-it is a bit mask recording whether the glyph is an ascender,
+it is a bit pair recording whether the glyph is an ascender,
 descender,
 both,
 or neither.
@@ -959,7 +960,8 @@ parentheses in some fonts.
 .P
 The
 .I index
-field is an integer that uniquely identifies a glyph within the font;
+field is an integer
+that uniquely identifies a glyph within the font;
 any integer is accepted as input,
 (that is,
 any integer parsable

_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit

Reply via email to