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

[G. Branden Robinson]

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

[comment #17 comment #17:]
> The point I was _trying_ to make with that: Space is only ever discarded if
it becomes a line break point.  Nonbreaking space by definition can never be a
break point.  So saying "horizontal motion cannot be [discarded]" is only
meaningful if it _can_ in fact be a break point; thus, making such an
observation might be read to imply that it can be.
> 
> But that was a reply to a bug comment; the actual wording added to the
manual makes this clear, saying the space represented by \~ "is discarded from
the end of an output line if a break is forced."  (It's less clear why someone
would specify a nonbreaking space and then force a break right after it, but
that's neither here nor there.)

The only case I've been able to think of was following the horizontal motion
with a vertical one, maybe to point some kind of arrow at the end of the
horizontal motion.  And even for that, I've had trouble coming up with a
practical application for it.

The best I can do is somewhat whimsical, but there's no law against using
groff for whimsical literature.


$ cat EXPERIMENTS/trailing-motion.groff
The flowers will start growing here.\h'1i'\v'1v'\[ua]
$ nroff EXPERIMENTS/trailing-motion.groff | cat -s
The flowers will start growing here.
                                              ↑




    _______________________________________________________

Reply to this item at:

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

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