Quote:
Originally Posted by DNSB
Yes. The only page measurements with any reliability and consistency between devices are the Adobe Synthetic Page Number algorithm for ePubs and Amazon APNX for Kindle format. For ePub, using the ASPN algorithm will give the same page number regardless of screen size, font size, line spacing, margins etc. Other methods of determining pages that use screens to measure pages have the sole advantage that you get 1 page per screen so your page count will vary with font size, line spacing, margins, basically anything that changes the amount of text that will fit on a screen.
Please note that both the consistent algorithms will give page numbers anywhere on the page.
Even though I will admit to be very amused by people worrying about the page numbers on a reflowable format where font size, line spacing, margins etc. are more or less under the users control.
The only use I have for the CountPages plugin is to give me an approximate idea of how long it will take to read a book. You may want to check many previous threads on page counts such as How does the kobo calculate book page counts? from 2015. |
I am new to ereaders so I am getting used to the flow of things. When reading a physical book, I can see how long I have left in the book and can see how many pages are left until the next chapter. As compared to an ebook, if the ereader is telling me that my physical ~1,200 page book is actually 3,000 pages, that trips me up and doesn't give me a good sense of my pacing in the book.
Is the better way to tackle this to look at time until next chapter/time until book is complete? Could you explain that a bit more and how this plugin allows you to use that?
----
Also sorry for double posting, I completely missed that my posts are on mod approval since I'm new here and thought I had accidentally deleted my original message.