View Single Post
Old 04-26-2008, 04:27 PM   #28
IceHand
Linux User
IceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavensIceHand is a rising star in the heavens
 
IceHand's Avatar
 
Posts: 323
Karma: 13682
Join Date: Aug 2007
Location: Germany
Device: Kindle 3
Quote:
Originally Posted by nrapallo View Post
No, the height split!

After the pi processing, your bash script splits the resulting image in three vertically. I am speculating that, in general, splitting be three or four would be the optimal way to view on a ereader screen. Can you try splitting by four vetically for a directory of pdf and compare with your first results (splitting by three vertically)? Is the large white margin issue lessened with the split by four?
I'm sorry, I was confused there for a second (and edited my post, but you'd already quoted me so I changed it back).
Anyway, yes, splitting by four gives very good results concerning the left and right border – the text size is rather large though (see attached image).

It would be great if the pi algorithm would have an option to specify the page width and height in pixels and optimise the line breaks accordingly. The size of the text could then be defined by changing the image density (dpi) with pdftoppm. Right now there's no difference when viewing it with my Cybook, because the number of characters/words per line will always be the same (well of course the text will look fuzzy if the density is set too low).
Attached Thumbnails
Click image for larger version

Name:	cybook_pi2.png
Views:	629
Size:	41.2 KB
ID:	12410  

Last edited by IceHand; 04-26-2008 at 04:42 PM.
IceHand is offline   Reply With Quote