The images are now included in this patch for lilypond-git and also in a
pull-request to the lilypond-extra repo. (From the CG I got the
impression that they only went in lilypond-extra, but on second glance
it appears that they live in both places.)
https://codereview.appspot.com/193140043/
David's concerns are very specific to the Lilypond documentation, not
covering the general case. Many programs simply can't process PS output
at all, so the suggestion to collect PS data that gets reduced later on
is not applicable.
The only valid alternative is to make Lilypond natively
Reviewers: ,
Message:
Please review. A demo showing the desired result can be found here:
http://clairnote.org / lilypond-web-demo2/
(just remove the two spaces in the url)
Things should look the same in IE8 and IE9 as in other browsers.
I will also need to add some images to the
On 14.01.2015 08:15, lemzw...@googlemail.com wrote:
Hmm. I can't find in your description that `--bigpdfs' creates *big*
output files that get later reduced to small one by running ghostscript
again.
https://codereview.appspot.com/194090043/
No? Have a look at the patch sent to
Knut, *your* patch set has this, but James's version (in patch set 2)
misses it.
https://codereview.appspot.com/194090043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2015/01/14 08:42:27, lemzwerg wrote:
Knut, *your* patch set has this, but James's version (in patch set 2)
misses it.
Yes that's true. I thought this was a 'lost in translation' error. So we
have:
+Generate really big pdf files with as less as possible
+optimization of font data.
