Quote:
Originally Posted by willus
Interesting. Do you know if it is the joining technique or just the sheer size of the PDF that reduces performance? You used pdfsam to join the files? Could you try jpdftweak also? Or could you try an overnight conversion that does it all in one piece (though as I recall this segfaulted k2pfdopt--so maybe just half of it?) to see how that compares? What would be best would be an A-B comparison between something produced only with k2pdfopt vs. something put together with various joining tools.
|
Sorry for the late reply, I get mail notifications about new posts each week.
Soooo.. the path I took to process the pdf was kind of the only one I could follow, I was not able to use k2pdfopt on the whole PDF without the crash, and even at half of the file the final PDF would still be a fraction of the whole size so it wouldn't tell us much even if the pdf worked better on the kindle, maybe the device is just not "enough" to process PDF's bigger than a certain size.
Also, pdfsam was the only one that worked for me to join the files, as jpdftweak didn't do anything, even after allowing up to 2GB of RAM to java applications, I waited eons and had no output.
Anyway, out of curiosity I am still converting the pdf with the latest version of k2pdfopt, let's see out it fares.
...played around, apparently by enabling "text reflow" disables "native pdf output", I realized it only later. By keeping text reflow disabled I could convert in native mode (albeit slow since only on one core) and the final size not only is very similar to the original file (200mb vs 250mb of your splitter command line batch some pages ago) but I retain color and text quality is better.
Have yet to test on the kindle tho, I just started assembling my 3d printer which arrived just now :P