Update of bug #66653 (group groff):

                  Status:             In Progress => Fixed
             Open/Closed:                    Open => Closed
         Planned Release:                    None => 1.24.0

    _______________________________________________________

Follow-up Comment #31:


commit c642f5fc7e1a274e89598aa54aa5199e4b7796d0
Author: G. Branden Robinson <[email protected]>
Date:   Thu Sep 18 00:22:55 2025 -0500

    [troff]: Regression-test Savannah #66653.
    
    * src/roff/groff/tests/asciify-composite-nodes-correctly.sh: Do it.
    
    * src/roff/groff/groff.am (groff_TESTS): Run test.
    
    Also drop ersatz '(C)' copyright symbol from "groff.am".  Software
    developers have long labored under the no-longer-correct misconception
    that omitting a copyright symbol from one's notice was a fatal defect
    that effectively placed the work in the public domain.  That stopped
    being true as of 1 March 1989.[1]  Further, prior to guidance issued by
    the U.S. Copyright Office in the decades since, the use of "(C)" as a
    substitute for a copyright sign _may not have sufficed_ to prevent the
    copyright notice from being regarded as defective.  The Copyright
    Office, then and now, prefers the abbreviation "copr." when © is
    typographically unavailable.[1]  Nowadays, its advice is that "c" (note
    lowercase) is an "acceptable variant", that _may_ retain the efficacy of
    the copyright notice.  The word "copyright", spelled out in full, also
    suffices per that resource, and is already present in this notice.
    
    [1] https://www.copyright.gov/circs/circ03.pdf

commit ee2011b6c921b3e04ebb5b7d58383049cdd75a04
Author: G. Branden Robinson <[email protected]>
Date:   Thu Sep 18 03:40:15 2025 -0500

    tmac/fallbacks.tmac: Fix Savannah #66653.
    
    * tmac/fallbacks.tmac: Define different fallbacks for accented
      non-Latin-1 Latin characters, using one ordering for nroff-mode
      devices and another for troff-mode devices.  We assume that the former
      can't constructively overstrike and the latter can.
    
      On troff-mode devices, it can make sense to use the `asciify` request
      to serialize special characters in device extension commands, and in
      that case we want to write the base glyph before any combining ones.
    
      On non-constructively overstriking devices, the last character written
      at the drawing position "wins"; we want that to be the base glyph.
    
    Fixes <https://savannah.gnu.org/bugs/?66653>.  Thanks to Deri James for
    pushing device extension commands to the limit, exposing this defect.




    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to