bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Reduce size of *TeX generated pdfs, Version 2


From: James Lowe
Subject: Re: [PATCH] Reduce size of *TeX generated pdfs, Version 2
Date: Fri, 09 Jan 2015 09:38:55 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

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.

I've already spent 25 minutes trying to find out how to get this python
script to run and haven't yet.

Hardly 'trivial'.

It passes make, make check and a full make doc, but is a there another
way to test this with something I don't have to dance through hoops to run?

James




reply via email to

[Prev in Thread] Current Thread [Next in Thread]