Follow-up Comment #2, bug #66732 (group groff): [comment #1 comment #1:] > This _may_ be due to a deliberate change. But I'm going to hide the > salami and ask you to run the `pev` request in your failing environment
Ah.
$ cat 66732
.ll 20n
.hy 4
My text contains the word antidisestablishmentarianism.
.pev
.br
.ev 1
.ll 20n
.hy 4
My text contains the word antidisestablishmentarianism.
.tm ----------------------------------------
.pev
$ groff-latest -Tascii -z 66732 2>&1 | egrep -i '^---|language'
hyphenation language code: en
----------------------------------------
hyphenation language code: (none)
hyphenation mode: 4 (on, not allowed within last two characters) [no
hyphenation language]
hyphenation language code: en
> If it is what I think it is, it's a consequence of another bug fix.
Bug #66387, I accuse YOU.
> But, since you steered right into it, probably another "NEWS" item.
I think more significant is _where_ I steered into it, which was in a footnote
generated by the -me package's .(f and .)f macros. I came this >< close to
opening this as a -me bug--ultimately steered away by the fact that e.tmac has
changed little since August, and that running a new groff with an old e.tmac,
or vice versa, changed nothing.
And you even warned me about this land mine in your last comment to bug
#66392, though I didn't grasp it at the time because the change to
hyphenation-language handling was theoretical at that point. It's harder to
ignore after being slapped in the face with it.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66732>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
