bug-groff
[Top][All Lists]
Advanced

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

[bug #57594] sync groff hyphenation-pattern files with upstream TeX vers


From: Dave
Subject: [bug #57594] sync groff hyphenation-pattern files with upstream TeX versions
Date: Mon, 13 Jan 2020 20:40:55 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0

URL:
  <https://savannah.gnu.org/bugs/?57594>

                 Summary: sync groff hyphenation-pattern files with upstream
TeX versions
                 Project: GNU troff
            Submitted by: barx
            Submitted on: Mon 13 Jan 2020 07:40:53 PM CST
                Category: Macro - others
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

Groff's hyphenation files are copied from their TeX counterparts.  About a
year ago, Werner Lemberg wrote on the groff email list
(http://lists.gnu.org/archive/html/groff/2018-11/msg00071.html):

    "Please update all pattern files from the data in the `tex-hyphen'
repository, for example,

   
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/patterns/tex/hyph-sv.tex

    (and applying the necessary massaging for groff)."

There appears to be no systematic way to refresh these groff files when
updates are made on the TeX side.  If groff has some sort of "release
checklist," perhaps making appropriate updates to these pattern files could be
added to that.

(These files would have to be updated anyway as part of the fix for bug
#57556, but I am filing it as a separate bug because fixing 57556 will be
significantly more work and thus may get deferred, whereas this is probably
straightforward.  But also, 57556 is a one-time fix, whereas this bug includes
an ongoing synchronization aspect, so it's worth tracking separately.)




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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