Follow-up Comment #5, bug #66392 (group groff): [comment #4 comment #4:] > So lines hyphenate and break differently with the fix to bug #66387 > applied--not globally across the document, but in certain environments. > > Does this break backward compatibility? [...] > With GNU _troff_, the answer is yes. I got pretty far along with > a change to _me_(7), but then decided a better approach would be > to simply do stuff behind the scenes inside the package and the > localization files to essentially copy environment 0's > hyphenation language to environments 1 and 2. [...] > I aim to do something similar for _ms_.
This ticket was closed when the above was written. But I'm not sure from the
above whether plans are still afoot to modify either -ms or -me in light of
this.
"I aim to" implies there are still -ms changes coming (which would be out of
scope for this -me ticket).
For -me, I'm not sure if the "better approach" is something still on the
table, or was rejected in light of my comment #3.
That comment speaks of behavior that has been consistent for decades. In
contrast, the change in .hla scope will certainly catch some -me users
(including this one) off guard. However, .hla is now "documented to work this
way," the criterion I stated in comment #3. So should e.tmac go out of its
way to accommodate this change?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66392>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
