Update of bug #64484 (group groff):
Status: In Progress => Fixed
Open/Closed: Open => Closed
Planned Release: None => 1.24.0
_______________________________________________________
Follow-up Comment #34:
commit 991677794ee58ae236c5888f8ed65cc96c065ff0
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date: Tue Nov 19 18:42:36 2024 -0600
[groff]: Regression-test Savannah #64484.
* src/roff/groff/tests/device-request-passes-most-escape-sequences.sh:
Do it.
* src/roff/groff/groff.am (groff_TESTS): Run test.
Test fails at this commit.
commit cba317296a9e835e44a3792b52232dce81d53407
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date: Tue Nov 19 18:55:54 2024 -0600
[troff]: Fix Savannah #64484.
This change restores groff 1.23.0's handling of characters in `device`
request arguments, except that {1} special character escape sequences
are interpreted (except for composite special characters, a planned
future development) and {2} unprintable character codes such as ASCII 2
are no longer emitted in GNU troff output by this means.
* src/roff/troff/input.cpp (device_request): Refactor and revise
argument interpretation. Reconstitute an encoded unbreakable space
code point as its escape sequence (spelled with the default escape
character). Throw warning in category "syntax" if a valid but
unprintable input character is encountered. Throw warning in category
"syntax" if an escape sequence other than `\[` is encountered. (A
reconstituted `\~` is not warned about.)
* src/roff/troff/troff.1.man (Warnings): Document additional
circumstances under which warnings in "syntax" category are thrown.
Fixes <https://savannah.gnu.org/bugs/?64484>.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64484>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
