URL: <https://savannah.gnu.org/bugs/?66165>
Summary: commit dcae60b0fb1ad3fa3314fdfdbecb973961a40410 has wrong assumption Group: GNU roff Submitter: deri Submitted: Tue 03 Sep 2024 08:08:47 PM UTC Category: Core Severity: 3 - Normal Item Group: Feature change Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any Planned Release: None _______________________________________________________ Follow-up Comments: ------------------------------------------------------- Date: Tue 03 Sep 2024 08:08:47 PM UTC By: Deri James <deri> It assumes that all \X parameters end up as meta-data but this not the case, troff has no knowledge of the purpose of the data. For example, grops accepts:- \X'ps: exec code' Where "code" can be a postscript program:- [derij@pip Branden (master)]$ echo "\X'/R { moveto 0 SC 3 -1 roll X widthshow Y } def'"|test-groff -Z| grep "^x X " x X /R { moveto 0 SC 3 \[u2010]1 roll X widthshow Y } def Sometimes the "data" is a filename:- [derij@pip Branden (master)]$ echo ".PSPIC -L dark-red.eps"|test-groff -Z|grep "x X " x X ps: invis x X ps: endinvis x X ps: import dark\[u2010]red.eps 0 0 81 96 81000 Since troff cannot know what the data is going to be used for it is unsafe for troff to change the data in this way. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?66165> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature