Follow-up Comment #12, bug #60655 (project groff): Hi Dave,
I don't see much fragility in what you are using now, the postscript language "build artifacts" are unlikely to change in any meaningful way which will stop your current workflow from continuing to work. Perhaps a general user who has a similar requirement, if they ask the best way to do it, we could point them to diffing the -Z output to avoid problems with diffing postscript output. Just as you had to learn how to read the groff postscript language to understand the diffs, they may find it easier to learn the groff intermediate format which is much simpler than the postscript language. I agree a user is unlikely to retain ancient -Z files, but in the use case you posited, they would still have the original troff input, so before making any amendments they could produce a -Z file, then make the changes and generate another -Z file which can be diffed to make sure nothing had changed. After all, an ancient groff postscript file may have many differences if changes have been made to grops, that do not alter the actual rastered content on the page. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60655> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/