[bug #63074] [troff] support expression of arbitrary byte sequences in device control commands

[G. Branden Robinson]

Follow-up Comment #36, bug #63074 (group groff):

Getting closer.


commit c4259eb20a66ab9da95741f6cc01d626b3abe632 (HEAD -> master,
origin/master, origin/HEAD)
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Sun Sep 15 06:08:23 2024 -0500

    [troff]: Refactor.
    
    `\X` reads its delimited argument in interpretation mode and the
    `device` request reads its argument in copy mode.  We want parity in
    special character handling for these formatter instructions, but one
    works with tokenized input and the other with tokens that happen to be a
    sequence of ordinary characters.  (In other words, in `\X'\[em]` and
    `.device \[em]`, the escape sequence "knows" that it is dealing with a
    the valid special character named "em", whereas the request merely
    handles '\', '[', 'e', 'm', and ']' in series.)  This change is in
    service of the grueling march toward resolution of
    <https://savannah.gnu.org/bugs/?63074>.
    
    * src/roff/troff/input.cpp (map_special_character_for_device_output):
      New function handles all of the potential special (including
      composite) character identifier rewriting formerly in...
    
      (encode_special_character_for_device_output): ...this function, which
      now simply calls the foregoing after extracting the special character
      identifier from the `charinfo` of the current token.




    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature