Update of bug #68132 (group groff):

                  Status:             In Progress => Fixed
             Open/Closed:                    Open => Closed

    _______________________________________________________

Follow-up Comment #3:


commit 45afde2cbcc307f7b574d88205bc1cf0581ec161
Author: G. Branden Robinson <[email protected]>
Date:   Mon Mar 9 20:19:31 2026 -0500

    [troff]: Regression-test Savannah #68132.
    
    * src/roff/groff/tests/do-not-abort-applying-tr-request-to-non-char.sh:
      Do it.
    
    * src/roff/groff/groff.am (groff_TESTS): Run test.
    
    Test fails at this commit.

commit 9c4e2c8c6a26ebfb03865fb05dc121c77a553936
Author: G. Branden Robinson <[email protected]>
Date:   Mon Mar 9 21:14:19 2026 -0500

    [troff]: Fix Savannah #68132.
    
    * src/roff/troff/input.cpp (do_translate): Stop throwing assertions if
      one of the participants (source or destination) in a character
      translation is a non-character.  Historical documents like Ritchie's
      "C Reference Manual" from Sixth Edition Unix (1975) did things like
      `.tr ~\|`.  This is no longer a worthwhile idiom--if indeed it ever
      was, since strings were available even then, but especially not since
      1990 or so with GNU troff's `char` and related requests--but we should
      not abort the formatter on encountering them.  Actually _supporting_
      such translations, in compatibility mode only, is under consideration
      for groff 1.25.  Throw error when encountering `tr` requests that
      attempt to operate on non-characters outside of compatibility mode.
    
    Fixes <https://savannah.gnu.org/bugs/?68132>.  Thanks to Clem Cole for
    the report.  Problem introduced by me in 52025b06f5, 21 November, in the
    course of adding many assertions to GNU troff to try to smoke out
    transitions into invalid formatter state and code that should be
    unreachable but isn't.  This instance fooled me because we did nothing
    useful (nor consistent with AT&T troff behavior) with the non-character
    translation participant; see above regarding future plans.
    
    ANNOUNCE: Acknowledge Clem.




    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to