[bug #53413] [PATCH] Add hyphenation patterns to use with US and hy=48

[G. Branden Robinson]

Update of bug #53413 (project groff):

                  Status:               Need Info => Wont Fix               
             Assigned to:                    None => gbranden               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #16:

Hi Dave!

[comment #15 comment #15:]
> Is there anything further to be done for this bug?  There seems to be no
support for incorporating the patch in the initial submission, and all the
ancillary issues brought up have been spun off into their own reports.

Right.  I don't think there is.  Resolving.

I'm persuaded by Werner's position.  Next-generation hyphenation control
should absorb all the within-word positional parameterization of what is now
the hyphenation mode into separate requests that are coupled to hyphenation
pattern files; if someone tries to request hyphenation at positions that are
incompatible with the pattern files for the current language, the request
should be rejected with a diagnostic.

I interpret Bjarni's project in this ticket as being motivated by the
observation that the software gave him a knob to twist, so he twisted it. 
This is a reasonable desire; software should not expose nonsensical
configuration options.

Unfortunately due to technical debt, that is what we are doing today.

So until we get that next-generation hyphenation control, our answer to users
wanting to use .hy 48 with English must be "don't do that".  (Or we can point
them at a mountain named "write your own English hyphenation patterns".)

This is already documented in Git HEAD, and perhaps with .hy 4 in en.tmac
being loaded by default for English-localized users--_if_ I get that branch
merged in time for 1.23.0--people will be less tempted to fiddle with it.

> [comment #13 comment #13:]
> > I reckon I would add '.hy 4' to my proposed new en.tmac file in #59814.
> 
> That seems best given the design proposed in that bug.

Yup, and this is on the branch now as seen in the ticket.

> > I think we should have English localization per se done in a separate
> > file.  Its concerns are distinguishable from those in the rest of
troffrc.
> 
> Eh, well, they are as of when the 59814 patch is applied.  Before that, one
of troffrc's concerns was loading English hyphenation patterns.

Yes.  I use parallel brains to contemplate and discuss
currently-released-groff (1.22.4), Git HEAD, and my branch-in-development.  
It would be helpful to others if I mentioned which brain I was thinking with
in a given discussion.  :D

    _______________________________________________________

Reply to this item at:

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

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