[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: Wed, 15 Jun 2022 01:55:39 -0400 (EDT)

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

[comment #3 comment #3:]
> > \| 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.

But they're excellent fits for the renaming because they're equivalent to
'\h@1m/6u@' and '\h@1m/12u@' respectively. 

Yes, but I'm seriously mulling withdrawing support for that.  It's a GNU
extension that no one seems to use.

Unicode supports more space glyphs than we have escape sequences for; see
U+2000 to u+200B.

If someone wants to define customized horizontal motion (non-breaking space),
it is easy to do so.  And that seems to me more properly the province of the
document author than the provider of the output device (driver) anyway.

$ cat EXPERIMENTS/nineteen-twelfths.groff
.char \[fnord] \h'19m/12u'
Check out my\[fnord]custom space width.


Reply to this item at:


Message sent via Savannah

reply via email to

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