On another forum I've read that PDF books created in Adobe Acrobate may load up to 1 minute and turning of a page takes about 8 seconds.

But similar PDF files created in PDFCreator virtual printer load within 8 seconds and listing of pages takes 2 seconds.

I also have additional idea. PDFCreator allows to uncheck "Compression" option. PDF with text will be 3 times larger. But probably it will additionally speed up loading and saves batteries resources?

On another forum I've read that PDF books created in Adobe Acrobate may load up to 1 minute and turning of a page takes about 8 seconds.


Unless you know exactly why that happens, you may be worrying about the wrong thing.

If I include an illustration that is rendered by Acrobat, display time will depend entirely on the complexity of that image. That may be OK, if you're typesetting a p-book -- but for e-books you should not rely on the speed of the reader software. And when PDF files are targeted to iLiads, it's even possible to decide the best resolution for images to avoid resampling of image files. It takes some PDF know-how to do this, though.

Page 9 or 10 in the iLiad User Manual used to take very long time to display for the first time: with pre-rendering it's getting acceptable.

How would I go about optimizing childrens picture books that were scanned? I have downloaded some children's picture books and they take forever to turn pages. The ones I have tried reading so far include Mother Goose, the Cheerful Cricket and Humpty Dumpty.

http://www.loc.gov/rr/rarebook/digitalcoll/digitalcoll-children.html

I'd like to read these to my young son, but its not practical if it takes 8+ seconds for a page turn. Is there a way for me to optimize them to have normal page turns?

How would I go about optimizing childrens picture books that were scanned?

The usual route is to use pdf2ppm to convert the pdf into a series of images, imagemagick to rescale/resample the images to tiffs, then tiff2pdf to convert them back to pdf.

With those particular files you want to resample them to a lower resolution. NB when downsampling its usually better to start with a full colour image, so create colour ppms in the first stage not pgms.

The tools I mentioned above are available on linux/macports generally as parts of the poppler, imagemagick, and libtiff packages. You can probably get by with cygwin on windows. You can base your script on this post:

http://www.mobileread.com/forums/showpost.php?p=174394&postcount=22

You don't need the bit with 'pi' in that script, they're doing something different in that thread.