Follow-up Comment #7, bug #57556 (project groff):
[comment #6 comment #6:]
> Design question: since a minimum hyphenation mode can be
> _computed_ based upon this characteristic of the pattern
> files, should reading such a pattern file effectively set .hy?
Yes, if you want to fix this bug as outlined in the last paragraph of comment
#0. :-)
What alternative design do you have in mind? troff could make the left and
right minimum values available to the user (in registers, for instance), and
then require the user to compute a .hy value based on this data (not a
straightforward matter before bug #55070 is addressed), but I see little value
to that approach unless someone feels it's important to continue to allow
users to use .hy values that are incompatible with their language's
hyphenation data.
Or am I misunderstanding the question?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57556>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
