[bug #66165] `\X` escape sequence should not map ASCII to special characters

[G. Branden Robinson]

Update of bug #66165 (group groff):

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

    _______________________________________________________

Follow-up Comment #8:


commit a1ced0efe59519afa0aa00e049b7ef6f3627260f
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sat Sep 7 20:01:10 2024 -0500

    Revert "[troff]: \X maps some basic Latin chars to specs."
    
    This reverts commit dcae60b0fb1ad3fa3314fdfdbecb973961a40410.
    
    Reverting the change better simulates copy mode, which is eventually
    where we want to take `\X`'s interpretation of its delimited argument.
    There's simply no convenient infrastructure for that in "input.cpp" yet.
    
    Output drivers that need to distinguish characters in device extension
    commands destined for "document text" from those intended for
    "application text" (or some other external purpose, like constructing a
    shell command for execution) have to use out-of-band means to achieve
    this distinction.  Documentation of recommended practices for achieving
    this are being hashed out and will soon, it is hoped, be documented.
    
    Fixes <https://savannah.gnu.org/bugs/?66165>.  Thanks to Deri James for
    the report.




    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature