URL: <https://savannah.gnu.org/bugs/?67329>
Summary: [troff] make `\?` handle unrecognized escape
sequences "normally"
Group: GNU roff
Submitter: gbranden
Submitted: Wed 16 Jul 2025 05:41:10 PM GMT
Category: Core
Severity: 1 - Wish
Item Group: Feature change
Status: Postponed
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 16 Jul 2025 05:41:10 PM GMT By: G. Branden Robinson <gbranden>
Our documentation says:
... Since comparands
protected with \? are read in copy mode, they need not even be
valid groff syntax. The escape character is still lexically
recognized, however, and consumes the next character.
Since the material bracketed by `\?` escape sequences is read in copy mode,
several interpolations take place, such as `\n`, `\*`, and `\V`.
Given that `\?` does not therefore switch the formatter into some sort of
"scrupulously literal" state, it would be more consistent for unsupported
escape sequences to be handled as they are normally; the escape character is
discarded and the next character output as-is.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67329>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
