Follow-up Comment #1, bug #67363 (group groff):

Utter madness.

In manual pages, just switch adjustment and hyphenation off globally for
everyone without supporting any way to switch it back on, and be done with it,
then delete all the fragile, overengineered, and likely bug ridden code in the
macro sets related to it.

I believe that's the only sustainable option.  You are obviously in way over
your head and have produced such a massive amount of regressions with the
groff-1.23 release that it has taken me two years to sort it all out.  I'm now
almost done; only three regressions remain to be dealt with, and one (simple)
feature improvement where mandoc needs to catch up.  And i got these massive
amounts of dysfunctionality even though i switch off whatever overengineering
i can.  I have no idea what users may be suffering who actually try to _use_
any of that overengineered stuff.

I believe the only chance to get all this into a better shape and make it less
painful and more stable is massively cutting back on the complexity and the
overengineering such that you get a better chance of actually understanding
what you are doing.  Piling more and more and more useless complication on top
is not buying you anything but lots of bugs, and dealing with that is very
painful for any downstream system that cares about software quality and
reliability.  I don't think it's fair to build more and more elaborate castles
in the sky and let downstreams sort out the consequences and suffer the
resulting havoc.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67363>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to