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 lilypond-devel on 8-1 . There I wrote:
With this patch pdfs generated by lilypond are much bigger,
but if you include more than two of them in a TeX document and
feed the pdfs to ghostscripts pdfwrite device, the resulting
pdf is much smaller. The files produced by ghostscript can
then be processed by pdfsizeopt.py for even better results.
One example: notation.pdf of lilypond 2.19.16
28.0 MB original size
300.0 MB built with --bigpdf enabled
5.9 MB as above + postprocessing with gs
4.3 MB as above + postprocessing with gs and pdfsizeopt
I think that already is pretty clear.
A day later, in the message to James Lowe, I published statistics about
the "one page with 4 small snippets" TeX document I attached to that
message:
Then translate test.tex to pdf with
lualatex --shell-escape test
gs -sDEVICE=pdfwrite -o testtmp.pdf test.pdf
pdfsizeopt.py --use-multivalent=no testtmp.pdf testfinal.pdf
dir test*pdf --sort=time | tac
With line 23 "\def\lilyparms{ }" I get
-rw-r--r-- 1 knut users 173538 9. Jan 11:53 test.pdf
-rw-r--r-- 1 knut users 157303 9. Jan 11:53 testtmp.pdf
-rw-r--r-- 1 knut users 149945 9. Jan 11:53 testfinal.pdf
With line 23 "\def\lilyparms{ --bigpdf }" I get
-rw-r--r-- 1 knut users 879441 9. Jan 11:55 test.pdf
-rw-r--r-- 1 knut users 63359 9. Jan 11:55 testtmp.pdf
-rw-r--r-- 1 knut users 59437 9. Jan 11:55 testfinal.pdf
The original patch to running.itely included:
+@item -b, --bigpdfs
+Generate really big pdf files with as less as possible
+optimization of font data.
cu,
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
