[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: Dave
Subject: [bug #62593] clarify description of end-of-sentence detection
Date: Sat, 18 Jun 2022 18:17:26 -0400 (EDT)

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

[comment #7 comment #7:]
> A "space" as I'm proposing to use it can always be discarded
> at a break and a horizontal motion cannot be.

True but slightly misleading: most of the things groff now deems horizontal
motions are not breakpoints, so groff would only break there if there were
_also_ a space (or a \:) adjacent to it, which will rarely be the case.  So
drawing a distinction that doesn't have much real-world application seems like
it maybe doesn't serve readers best, and also might imply a breakability that
these characters don't have.

Further, terms like "figure space" are well known outside groff, and it serves
readers knowledgeable about typography to use the terms standard in the art.

I'd be interested in others' views about this, but terminology discussions on
the list have shown a tendency to move in the direction of holy wars. 
(Regardless, although the discussion arose here, it's not really on topic for
this bug.)

> The following exercise helped push me in this direction.

Essentially moot, since I get your point, but I don't understand this example:
with adjusting turned off, whether there is "space" at the end of an output
line is invisible.  And this snippet's terminal output has no lines with
trailing space characters.


Reply to this item at:


Message sent via Savannah

reply via email to

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