URL: <https://savannah.gnu.org/bugs/?66675>
Summary: valid .char definition provoking erroneous error
Group: GNU roff
Submitter: barx
Submitted: Thu 16 Jan 2025 03:54:17 PM CST
Category: Core
Severity: 3 - Normal
Item Group: Incorrect behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Thu 16 Jan 2025 03:54:17 PM CST By: Dave <barx>
From at least groff 1.19.2 through 1.23, this command produced nothing on
stdout or stderr:
echo '.char \[unhappy] :-(' | groff
This is as it should be: the code merely defines a perfectly legitimate
character and does nothing with it.
The latest groff build produces two diagnostics on stderr:
troff:<standard input>:1: error: special character 'unhappy' is invalid:
Unicode special character sequence has non-hexadecimal digit 'n'
troff:<standard input>:1: error: bad character definition
This erroneous error was introduced sometime after August 11. I blame an
overzealous [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=d29abf70a
commit d29abf70a].
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66675>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
