Update of bug #67372 (group groff):
Item Group: None => Feature change
Summary: [troff] \A and \w behavior change from 1.22.4 ->
1.23.0 => [troff] \A and \w behavior change from 1.22.4 -> 1.23.0 on invalid
input
_______________________________________________________
Follow-up Comment #21:
At the risk of jinxing it, it seems Ingo and I have reached a truce.
So I plan to proceed as follows, repeating comment #5.
1. I should document that if one wants AT&T-compatible treatment of
interpolated delimiters, one should use compatibility mode. The
language of our documentation should be broadened: groff's concept
of "input level" (or "interpolation depth" as I prefer to term it)
applies not just to the arguments of a delimited escape sequence,
but to the delimiters themselves.
2. I should see if I can make groff perfectly AT&T-compatible with
this input, in compatibility mode.
Neither of these have any impact on _mandoc_'s test suite (since one is just a
documentation issue and the other involves only compatibility mode, which
_mandoc_ does not exercise).
Next...
3. I should add test cases that force me to nail down the formatter's
behavior when using string interpolations to construct escape
sequences.
I plan to accompany those test cases with the change pitched in comment #11.
To keep the work manageable, I'll restrict my scope to the \[AbowXZ] since
those are the ones at issue.
But in principle, GNU _troff_ could be more aggressive about validating the
next character after the function selector with *any* escape sequence that
requires a delimiter.
I don't know if any of this is worth gating 1.24.0 on. Opinions?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67372>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
