[Top][All Lists]

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

[bug #57616] explicit hyphenation given in tmac/hyphenex.us violated

From: Dave
Subject: [bug #57616] explicit hyphenation given in tmac/hyphenex.us violated
Date: Mon, 27 Jan 2020 23:28:17 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0

Follow-up Comment #2, bug #57616 (project groff):

Now meet the word "freeloaders."  hyphenex.us gives exactly one legal
breakpoint for the word:

$ grep '^  free' /usr/share/groff/current/tmac/hyphenex.us

But groff gives it more than one:

$ printf ".hy 4\n.ll 1u\n%s\n" freeloaders | nroff 2> /dev/null | sed '/^$/d'

While both of those are reasonable breakpoints, the explicit hyphenation in
hyphenex.us should disallow the second one.  (This is arguably a bug in the
hyphenex.us list, but that file originates in TeX, so its bugs must be
addressed there.)

So the "distraughtly" and "freeloaders" examples seem to invoke the same bug
-- in both cases, groff is adding a breakpoint that is not specified in
hyphenex.us -- but they also have some notable differences:

* For "freeloaders," groff breaks the word the same way with .hy values of 1,
4, 8, and 12.  As mentioned in comment #1, ".hy 1" and ".hy 4" give different
results for "distraughtly."
* Unlike "distraughtly," groff broke "freeloaders" the same way (for all
relevant .hy values) in 1.22.3, before the fix for bug #53196 (commit
4b299723) was applied.  So that fix did not introduce the general bug.


Reply to this item at:


  Message sent via Savannah

reply via email to

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