Update of bug #57556 (group groff):
Summary: Enforce left and right minimums as required by
hyphenation patterns => [troff] enforce left and right minimums as required by
hyphenation patterns
_______________________________________________________
Follow-up Comment #11:
[comment #10 comment #10:]
> [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?
>
> I want to revise my comment #7 answer to this by zooming out.
Since that comment is over 3 years old, I'll advise anyone just joining us of
bug #55070 (already mentioned a couple of times), and also my straw-man
proposal that attacks at least some of the
>
> From a design standpoint, a weakness of the current .hy mechanism is that
> it's attempting to control two different things:
> 0 What hyphenation limitations are encoded into the active hyphenation
> patterns
> 0 What hyphenation restrictions the document author wants
> This tension is especially observable in a multilingual document: the values
> of both 1 and 2 above might change over the course of the document, and not
> necessarily in tandem.
Right.
Also, the "suppress hyphenation before a vertical position trap" flag reveals
a subdivision of your second category. It's a restriction the author might
want to configure, but separately from others like "don't hyphenate between
the 2nd and 3rd letters of a word even the patterns permit it".
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57556>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
