On 09.01.2015 10:38, James Lowe wrote:
On 08/01/15 19:10, Knut Petersen wrote:
On 08.01.2015 19:10, James wrote:
On 08/01/15 12:18, Knut Petersen wrote:
So here is Version 2
================
I fixed a few issues with version 1, added a command line option
--bigpdf / -b, and documented that option in the german and english
versions of usage.pdf .
The patch is based on the current git master of lilypond now.
cu,
Knut
This is now being handled in Tracker issue
I think the easiest way to test the code thoroughly is to apply the patch,
do a full build, and then change
"bool bigpdfs = false"
in global-vars.cc to "bool bigpdfs = true" and do a full build again.
Postprocess the doc pdfs according to
gs -sDEVICE=pdfwrite -o outgs.pdf notation.pdf
pdfsizeopt --use-multivalent=no outgs.pdf outfinal.pdf
and verify that everything went ok.
running gs was trivial, but pdfsizeopt? where do I get that *easily*.
Seems that Google's own instructions are out of date or don't work
(error 404 links) and there are a ton of other files that I need to
download (or check that I have) to make sure all the dependencies are
met for pdfsizeopt.
Yes, their install instructions were not updated to the v2 libexec. Use
something like:
DIR=pdfsizeopt
mkdir $DIR
cd $DIR
wget -O pdfsizeopt.py http://pdfsizeopt.googlecode.com/git/pdfsizeopt.single
chmod 700 pdfsizeopt.py
wget https://pdfsizeopt.googlecode.com/files/pdfsizeopt_libexec_linux-v2.tar.gz
gzip -cd pdfsizeopt_libexec_linux-v2.tar.gz | tar -xvf -
# We have our own gs, so remove this one
rm pdfsizeopt_libexec/gs
cu,
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel