[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: G. Branden Robinson
Subject: [bug #62593] clarify description of end-of-sentence detection
Date: Mon, 6 Jun 2022 17:46:44 -0400 (EDT)

Update of bug #62593 (project groff):

                Category:                    Core => General                


Follow-up Comment #1:

[comment #0 original submission:]
> Another "bookmark" bug report; Ingo already suggested this in email
(http://lists.gnu.org/r/groff/2022-06/msg00030.html), but that message might
easily get lost in the deluge of that highly active thread.
> In Ingo's words:
> the documentation is indeed slightly fuzzy regarding this point; "info
groff" tells me:
>   5.1.2 Sentences
>   ---------------
>   [...]
>   GNU 'troff' does this by flagging certain characters (normally '!',
>   '?', and '.') as potentially ending a sentence.  When GNU 'troff'
>   encounters one of these "end-of-sentence characters" at the end of a
>   line, or one of them is followed by two spaces on the same input line,
>   it appends an inter-word space followed by an inter-sentence space in
>   the formatted output.
>   [...]
> Branden, please consider improving the words "followed by two spaces".
> Anything like
>   followed by two ordinary space characters ("  ")
>   followed by two unescaped space characters ("  ")
> might do.
> You might also consider saying "at the end of an input line" rather than
just "at the end of a line".

I've been thinking about this while the discussions rage, and I'll consider
them, but I've been chewing over the idea of discarding as many "space" terms
as possible in favor of "motions".

So, e.g., 

\| 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.

while elsewhere discussing the fact that motions are never discarded except at
the end of an output line (horizontal) or page (vertical).

Setting "category" to "general" because I'm not certain we don't discuss
sentence endings in non-"core" documents (like manuals for macro packages). 
(I do recall that we try to keep the gory details out of those.)

Thanks for your help tracking the flaming paddles I've chosen to juggle!


Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]