On Mon, Jul 29, 2024 at 11:09 AM Werner LEMBERG <w...@gnu.org> wrote:
> This means that it would be sufficient to make the Cairo backend also > create logging output. In case I'm not missing something this > shouldn't be too hard to add. > Can this be done? If one were to log all the calls and arguments to Cairo functions and then write a corresponding program to replay them later, would they get the same PDF as from a direct binding? A similar idea had occurred to me to use postscript scripting to scrape off the result of the render and use that as a basis for this loggin concept. I've used this before to turn postscript (from dvips) back into TeX source, and it's one of these things that gets you 80% of the way very quickly. Now, because programming in postscript is not a very modern thing to do, I would think it'd be nicer to interject Cairo calls than doing this, largely because more of the community working on lilypond will be able to update this part of the code as well, which seems of paramount importance. But still, at least as curiosity, I figured I would mention it. -- Luca Fascione
