bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: G. Branden Robinson
Subject: [bug #53413] [PATCH] Add hyphenation patterns to use with US and hy=48
Date: Mon, 4 Jan 2021 02:22:25 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #13, bug #53413 (project groff):


[comment #12 comment #12:]
> [comment #11 comment #11:]
> > Probably, or at least en_US.tmac to keep the Commonwealthers from
screaming too loudly.
> 
> Groff already makes no distinction between US and UK English in its
hyphenation handling, so whatever screaming they want to do, it's over
something more fundamental than the name of the .tmac file.

That's true.  But it annoyed me so I created #59814.

> > The setup for English is handled by troffrc and hyphen{,ex}.us.
> > 
> > Unless I'm misunderstanding you.
> 
> I don't know, because I'm not sure I'm following you.
> 
> hyphen{,ex}.us, despite living in tmac/, aren't tmac files, so the default
.hy can't be set there.

That's true.  I reckon I would add '.hy 4' to my proposed new en.tmac file in
#59814.
 
> troffrc looks like it unconditionally sets the language to "us" and loads
those two hyphenation files.  So this might be a good place to go ahead and
set .hy as well, rather than creating a new .tmac file.

On the contrary, 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.

>  But I don't know how non-English groffs are set up (Do they skip troffrc
altogether?  Does the installation process modify this file to load different
hyphenation patterns?), so I'm probably not the best person to say.

Non-English groff is...not set up by default.  You have to hack your troffrc
or load one of the localizing tmac files yourself in a macro package or
document.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]