bug-groff
[Top][All Lists]
Advanced

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

[bug #61734] [man] localize like other packages


From: Dave
Subject: [bug #61734] [man] localize like other packages
Date: Fri, 11 Mar 2022 20:36:48 -0500 (EST)

Follow-up Comment #9, bug #61734 (project groff):

I too have muddied the waters by bringing up separate issues without clearly
delineating them.

To frame the discussion, I'd say the places groff's e.tmac needs to work, in
order of importance, are
0 within groff
0 in legacy troff
0 in other troffs

I suspect Heirloom has the largest market share of the third category, but, as
you note, is also the most problematic in terms of implementing noncompatible
extensions.

So, taking these issues in my proposed order:

0 Groff itself will misbehave here if \\n[\\*[locale]*hyphenation-mode-trap]
is undefined.  Maybe with a stock installation, this is impossible (I haven't
tried to find a way to induce it), but surely a user can define new locales or
hack groff's initialization files locally, in such a way to leave the
localization register undefined.  It doesn't seem like defaulting .hy to 0
rather than 6 in these instances is right.
0 This is where we seem to be on solidest ground: as you note, legacy troff
won't know a .do request, and will thus ignore that line.
0 This may, ultimately, be an unwinnable game of whack-a-mole, since existing
troff implementations can always change, or new ones be created, over time. 
But a starting point might be to test whether the .g register is defined. 
This will surely break at least Heirloom in its not-actually-compatible "groff
compatibility mode," but I'm willing to call that an Heirloom bug: don't claim
groff compatibility if you don't actually offer it.

Let me know if I've gone astray anywhere.  (If there end up being further
changes to be made, it probably warrants a new bug report: this one only
concerned the -man package, though the resolving commit did try to sneak -me
in the door as a +1.)

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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