Follow-up Comment #6, bug #53413 (project groff):
> And `generally' using `.hy 48' is a bad idea. Values of
> `.hy' are always bound to the currently selected hyphenation
> patterns.
Yes, but the entire reason .hy 48 produces erroneous output is that the
hyphenation patterns were not crafted with this setting in mind. This strikes
me as a failure of the hyphenation patterns, not of the user's .hy selection.
The proposed patch (haphazardly) addresses that, but for English only.
Werner's point, in comment #1, is that it's imprudent to fix a problem for one
language that ships with groff while leaving the same problem in the others.
I suppose it's a philosophical question whether it's better to partially fix a
shortcoming but create an inconsistency between languages (what this patch
does), or maintain consistency and address the shortcoming in the
documentation (the status quo). Werner also declined to make this call in
comment #1. And I'm not a groff developer, so it's not really my place to
have an opinion, either. But I hope this clarifies the issue.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53413>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
_______________________________________________
bug-groff mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-groff
