Follow-up Comment #24, bug #66392 (group groff): [comment #23 comment #23:] > I'm trying to get 1.24.0 toward a release and I am not anxious to > mediate a dispute between advocates of these three positions,
In terms of what's least disruptive for an imminent release, perhaps simplest
is to roll back the change making hyphenation language per-environment.
* As far as I can tell (correct me if I'm wrong), this doesn't disrupt any of
the new functionality targeted for 1.24. Nothing is listed as depending on
bug #66387.
* It doesn't regress anything, since this has been the status quo for a very
long time, probably since .hla was introduced.
* It allows the present bug (altering macro packages to accommodate the
change) to be postponed until after a release. So it actually reduces the
1.24 workload.
When the change is re-implemented for 1.25, it can be done in tandem with the
larger discussion that has sprung up here about how best to populate new
environments. And that can be done early in the release cycle, to give any
issues more time to shake out before a release.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66392>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
