View Single Post
Old 10-25-2020, 06:37 PM   #1819
willus
Fuzzball, the purple cat
willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.
 
willus's Avatar
 
Posts: 1,303
Karma: 11087488
Join Date: Jun 2011
Location: California
Device: iPad
Quote:
Originally Posted by ioo View Post
My target device is an 8th generation Kindle. If I do not use -n but instead use the following:

-dev k2 -fs 12 -wrap- -bp m -ac 0.009 -col 3 -ws 0.2 -fc-

I am able to achieve good results in terms of cutting up the paragraphs while preserving the paragraph structure and removing the white space.

This approach however generated images which do not look good on my Kindle (the fonts are not smooth) and it take away text searching capabilities.
Maybe you can post an example of your source? It should be keeping the text searching by default if you have MuPDF. Not sure what to say about the fonts--again, if you could post some examples of both the source and converted PDF, that would help the most.


Quote:
Originally Posted by ioo View Post
I did try the -n option but the resulting pdf is extremely slow to respond on the target device. It basically renders the kindle frozen for minutes. Is this due to the processor not being able to handle the formatting that is added to the pdf file? If I use the original pdf it is responsive. Is my analysis here correct- that the kindle can't handle the added formatting or do you think there is another issue?

I presume you found a version with MuPDF so that -n works? In that case, yes, your analysis is probably correct. The -n option can put more strain on the particular PDF reader. It's typically faster to display a bitmapped PDF.


Quote:
Originally Posted by ioo View Post
To address this, I then tried to use calibre to convert the -n pdf to mobi format but after 1 day of processing a single k2pdfopt file I gave up. Are you aware of this approach working for others? It seems that Calibre will process the original pdf but not the one outputted by k2pdfopt

You might want to read through this page.

Quote:
Originally Posted by ioo View Post
I did notice something strange. If I do not use the -n and generate a pdf with images, then use calibre to convert it to the mobi format, the fonts looks slightly more smooth. I do not understand how this would work as k2pdfopt has already created the images. How can converting a series of images from pdf to mobi improve the fonts?

I thought maybe the issue was I am using the wrong -dev which outputs images of a certain resolution then maybe calibre is correcting it and resizing the images? Perhaps this can account for the improvement in image quality?

I am using -dev 2 which states it is for Kindle 1-5 however I have an 8th generation kindle. Is this correct or should I use a different -dev?

Calibre states that the "Kindle" profile has a resolution of 525x640 however online I see the resolution for my device to be 600X800. If I use -dev 2 what will the output resolution of the images be?
Using -dev k2 should be about right. It will actually use 560 x 735 pixels because the kindle doesn't necesarily use all of that 600x800 screen real-estate to display the text. You can go to this page and post screen shots from your kindle and I'll recommend to you the best settings for it. If you could post the pre-calibre and post-calibre PDFs, that might help explain things. To see a list of all device dimensions known by k2pdfopt:


k2pdfopt -dev "?"
willus is offline   Reply With Quote