Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.groff.bug > #1584
| From | Dave <INVALID.NOREPLY@gnu.org> |
|---|---|
| Newsgroups | gnu.groff.bug |
| Subject | [bug #57448] groff will not break a line at a hard hyphen following some letter combinations |
| Date | 2019-12-23 07:50 -0500 |
| Message-ID | <mailman.1305.1577105443.1979.bug-groff@gnu.org> (permalink) |
| References | (1 earlier) <20191219-231340.sv93188.76941@savannah.gnu.org> <20191219-220856.sv93119.28405@savannah.gnu.org> <20191220-043627.sv93119.51933@savannah.gnu.org> <20191222-233745.sv93188.73578@savannah.gnu.org> <20191223-065039.sv93119.93277@savannah.gnu.org> |
Follow-up Comment #5, bug #57448 (project groff):
> If the kerning in front of the hyphen is removed (with '\&'),
> the expected result is there.
Well, not if the expected result is for kerning and line-breaking to
simultaneously work. :)
If one needs a workaround, a better one is to add a zero-width breakpoint (\:)
after the hyphen.
But the greater trick is figuring out all the places such a \: is needed. In
groff's default font set -- with relatively few kern pairs that have a hyphen
as the second character -- the problem is limited in scope. But for installed
fonts with a larger set of kern pairs, the bug could crop up in unexpected
places. (And there is nothing magical about two characters: any number of
kerned characters before a hyphen triggers the bug.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57448>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Back to gnu.groff.bug | Previous | Next | Find similar
[bug #57448] groff will not break a line at a hard hyphen following some letter combinations Dave <INVALID.NOREPLY@gnu.org> - 2019-12-23 07:50 -0500
csiph-web