View Single Post
Old 02-22-2012, 06:47 AM   #241
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,732
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
@Kogs - now you have really confused me .

So you are saying that you download an ePub from KoboBooks, and when you open it on your Kobo it displays a page count of X. And X is based around how many screen turns that book will take (based around some "regular" font size setting on the device)? And if you increase your font size, that number X stays the same, it just takes more "turns" per "page"?

Then if you instead download an Amazon mobi file to calibre, convert to ePub and put that book on your device... you would instead get a page count of Y rather than X?

So where does the Count Pages plugin come into this? And where is the Kobo getting its page count from? To me page count can only come from one of:
(1) estimating based on the content of the ePub (which should give you similar counts no matter where the ePub came from)
(2) some special piece of metadata inserted into the ePub (which you should be able to find if that was the case).
(3) some sort of external metadata file (like the APNX file the Kindle uses).

But in cases 2 & 3, what does it do for books not from the KoboBooks store? Does it "fallback" to (1)?

Confused
kiwidude is offline   Reply With Quote