Quote:
Originally Posted by wingmongyee
Often, when I speak to a friend about a book I'm reading, he will ask how many pages in the book. Before using KePubs, I could never answer him clearly, and could only give him approximate numbers. Now, I give him the exact number of pages; I just show him a page of the book with my current font size, and explain there are x pages at that size. That gives him a much more accurate idea of the size of the book.
|
To get that number, you need to open each chapter, see how many pages are in each and add them up. Then change the font size, margins, line spacing or even the justification and do it again. You actually do that? That's going to take a fair amount of time for a 30 chapter book.
The Adobe method, used in any ereader or app that uses the Adobe RMSDK and ADE, is a fixed number for the book and is independent of the reading settings used. And consistent across all of these plus other things produce it as well (e.g. Count Pages plugin in calibre). As an approximation of the length of a book, I find it much more useful.
And I understand how the paging works, so I do understand how much time it will take me to finish a chapter from the pages left in it. Of course, I think the chapter graph in kepubs is great, and it is almost enough to convert me, but, I'm not that great a fan of the per-chapter page numbering.