Re: [Lilypond-auto] Issue 3317 in lilypond: Create a standalone PDF backend

[lilypond]

Comment #3 on issue 3317 by address@hidden: Create a standalone PDF backend
http://code.google.com/p/lilypond/issues/detail?id=3317

I am not overenthused with the idea of passing this through Cairo since PDF  
offers a lot of possibilities likely not inherently supported by Cairo.

Writing PDF directly is quite feasible: we have a few functions defined in  
PostScript (ps/music-drawing-routines.ps) that would warrant rewriting in  
Scheme instead: there is little point to delegating stuff to the PostScript  
programming layer.  The functionality offered by PDF is quite the same as  
that of PostScript (just with different names and without the programming  
layer), so if one gets rid of that (and Cairo would not offer a programming  
layer either), much of the PDF creation job is copying the PostScript  
backend and modifying the primitive names, then adding headers and stuff.

I have my doubts that going through Cairo would provide us with the same  
amount of control over rasterization, PDF inclusion, and other stuff.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings