[bug #60233] doc/groff.texi: ambiguity in .tkf documentation

[Dave]

Follow-up Comment #3, bug #60233 (project groff):

Three more points:

* Comment #2 quoted the manual text as it appeared in the original submission
back in March, but since then an October commit (5380e8ad
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=5380e8ad>) changed
"point size" to "type size."

* The code snippet points out that the case of S2 <= S1 remains undocumented.
** S1 == S2 is a legitimate use case if one wants only a specific type size
affected, and that this (again, assuming I'm reading the code right) uses N1
as the adjustment, effectively discarding N2, ought to be documented.
** The case of S2 < S1 is technically an error (the user is specifying a
maximum less than the minimum), so documenting this is perhaps less important.
 But it does seem notable that groff doesn't treat it as an error condition,
silently using N1 here also.

* While we're in the neighborhood: the concept introduction accurately says,
"'Track kerning' expands or reduces the space between glyphs."  But the
description of the .tkf request itself uses sloppier wording, saying "the
width of every glyph is increased."  .tkf does not alter the width any glyphs,
only the amount of space between them.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60233>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/