[bug #62593] clarify description of end-of-sentence detection

[Dave]

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

[comment #1 comment #1:]
> I've been chewing over the idea of discarding as many "space"
> terms as possible in favor of "motions".

Hmm, I wonder if that's another case of veering into being technically correct
at the expense of some clarity to the average reader (a la replacing "single
quote" with "neutral apostrophe" in a coding context*).  Sure, theoretically
all spaces (horizontal or vertical) are motions, but especially for horizontal
spacing, it seems like users will more naturally think of something like \0 as
a space the width of a digit, rather than a horizontal cursor motion of that
magnitude.

> \| Unbreakable 1/6 em (“thin”) space glyph; zero‐width in nroff.
> 
> might become the following
> 
> \| 1/6 em motion (“thin space”); zero-width in nroff.

\| and \^ seem the poorest fit for this renaming since they _can_ be defined
as glyphs in the font.

> Setting "category" to "general" because I'm not certain we
> don't discuss sentence endings in non-"core" documents (like
> manuals for macro packages).

Good point.  I didn't intend to limit the scope, but was thinking only of the
scope of Ingo's original comment.


* I commented on this in response to a recent commit, but after a fruitless
hour scouring savannah, the groff list, and private email to you, failed to
unearth my comment.  So maybe I only imagined it.


    _______________________________________________________

Reply to this item at:

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

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