|
@KoGs - I appreciate the effort but I'm afraid that isn't going to be sufficient. At the very best all I would be able to do based on that is come up with another "estimate", which is just going to be not overly dissimilar to what is computed already.
The APNX/page count functionality is primarily targeted at Kindle users, since it is the only way to get a page count for your own books to appear on the Kindle.
The secondary set of users is those who just want a way to within Calibre compare the relative sizes of different books. That's where I see Kobo users fitting in.
However unless someone can determine the exact formula applied to come up with the page count on the device, I don't see what value some other estimated number is going to add? Without that it isn't going to be any more "accurate" than the existing algorithm, at best it will just skew the numbers either up or down slightly. Which doesn't to me sound worth the effort.
On top of which, there is the very real difference between what constitutes a "screen" and what constitutes a "page". If I understand your post above, what you have provided are a "screen" worth of information. Now I know nothing about the Kobo, maybe it works differently to other devices, but on a Kindle at least the page count is not in any way related to the number of "screens" displayed.
What I could possibly do is expose the variables used in the calculation to allow a plugin user to tweak them. So if someone thinks the numbers are overall skewed in the wrong direction they could "fiddle" them to a different number of "characters per page" or whatever. However I see it as rearranging deck chairs on the Titanic in that it will just skew the numbers slightly up or down, and will still result in some books being significantly underestimated and others overestimated.
|