[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #66323] grops should handle special character escape sequences in c
From: |
Dave |
Subject: |
[bug #66323] grops should handle special character escape sequences in certain device control commands |
Date: |
Sat, 12 Oct 2024 17:32:50 -0400 (EDT) |
Follow-up Comment #12, bug #66323 (group groff):
Comment #9 clarifies the scope and purpose of this bug.
Subsequent comments seem to identify several others.
Comment #10 talks about rendering differences between grops and gropdf. These
have not yet been root-caused, so they may be down to user error--but if so,
this may point to a documentation deficiency. In any case, it may help focus
discussion if this issue were a separate ticket.
Comment #11 raises several others:
* scrubbing a string is ill supported in current groff (bug #62264)
* mom is not scrubbing the argument to her .AUTHOR macro. This may be
dependent on the aforementioned #62264, but some of it may be currently
handleable.
* pdfmom sometimes exits with a 0 even if there's been an error
* "special characters aren't getting into 'grout' at all." I take it this is
a separate problem from the grops one that is now the focus of this ticket,
since grops takes grout as input.
Should any of the above be separate tickets (besides the one that already is)
so that they don't get lost in the deluge?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66323>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #66323] [mom] rendering differences between PostScript and PDF output?, (continued)
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), Deri James, 2024/10/11
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), anonymous, 2024/10/11
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), Dave, 2024/10/11
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), Peter Schaffter, 2024/10/11
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), Deri James, 2024/10/12
[bug #66323] [mom]: groff HEAD produces invalid postscript (that also crashes pdfmom), G. Branden Robinson, 2024/10/12
[bug #66323] grops should handle special character escape sequences in certain device control commands, G. Branden Robinson, 2024/10/12
[bug #66323] grops should handle special character escape sequences in certain device control commands, anonymous, 2024/10/12
[bug #66323] grops should handle special character escape sequences in certain device control commands, G. Branden Robinson, 2024/10/12
[bug #66323] grops should handle special character escape sequences in certain device control commands,
Dave <=
[bug #66323] [mom] rendering differences between PostScript and PDF output?, G. Branden Robinson, 2024/10/14
[bug #66323] [mom] rendering differences between PostScript and PDF output?, Deri James, 2024/10/14
[bug #66323] [mom] rendering differences between PostScript and PDF output?, G. Branden Robinson, 2024/10/14
[bug #66323] [mom] rendering differences between PostScript and PDF output?, Peter Schaffter, 2024/10/14
[bug #66323] [mom] rendering differences between PostScript and PDF output?, Deri James, 2024/10/14
[bug #66323] [mom] rendering differences between PostScript and PDF output?, anonymous, 2024/10/14
[bug #66323] [gropdf] rendering differences between PostScript and PDF output?, Deri James, 2024/10/14
[bug #66323] [gropdf] rendering differences between PostScript and PDF output?, G. Branden Robinson, 2024/10/14
[bug #66323] [gropdf] rendering differences between PostScript and PDF output?, anonymous, 2024/10/14
[bug #66323] [gropdf] rendering differences between PostScript and PDF output?, G. Branden Robinson, 2024/10/15