Pages field in Calibre 9 vs Count Pages plugin results

[mikespub]

After upgrading to Calibre 9 and forcing recalculation of all book pages, I noticed that the pages field calculated natively can be significantly different from the pages count given by the Count Pages plugin - sometimes by a little, but sometimes by factor 2 or more.

This can be quite confusing if you use the page count anywhere in the main view or book details.

Are there any plans to align the methodologies used to calculate those values in future versions of Calibre and/or Count Pages?

Thanks

[kovidgoyal]

No, no plans. Pick one and use it.

[Dal Bhat]

Originally Posted by mikespub

...I noticed that the pages field calculated natively can be significantly different from the pages count given by the Count Pages plugin...

as well as significantly different from the pages of the book on a Kindle.

I've turned them both off from displaying.

[Sirtel]

Originally Posted by Dal Bhat

as well as significantly different from the pages of the book on a Kindle.

I've turned them both off from displaying.

AFAIK the "official" page count on a Kindle (meaning, for direct downloads from Amazon) is based on a paper edition. Both Calibre and the Count Pages plugin use other methods.

There is no such thing as the one true page count for reflowable ebooks; it depends on the method you use, and there are many different methods. So it's a matter of picking a method that suits you.

My Kobos use a different method each - the Sage with kepubs uses 1 screen = 1 page, the Libra with epubs uses the Adobe system. And in calibre I use the Count Pages plugin based on characters per page.

It's all approximate anyway.

[JSWolf]

Has the bug in KePub been fixed where it's not always 1 screen = 1 page?

[Uncle Robin]

Originally Posted by Sirtel

AFAIK the "official" page count on a Kindle (meaning, for direct downloads from Amazon) is based on a paper edition.

Yes, Amazon explicitly lists it under an icon of a book labelled "print edition". I prefer the "Count Pages" values, but for those who use KOReader(I know you don't) it now offers a "stable pages" option that uses a character-per-page count set by the user, besides the 1 page = 1 screen default.

[bdub]

This is why I prefer word count over pages. Pages depend on the size of the page, the font and font size, and spacing. One page on my 6" KOBO with Lexend is going to be different than on a 7" Kindle with a different font, font size, and different spacing. And for print books, it's going to be different between mass market paperback, paperback, and hardcover.

I figure I read about 100k words a week, so I use word count to get an idea for how long a book will take me to read before deciding to read it.

I'm good with Calibre calculating out pages for display purposes.

[Sirtel]

Originally Posted by bdub

This is why I prefer word count over pages. Pages depend on the size of the page, the font and font size, and spacing.

Not always. The Adobe page count doesn't, for example, it's fixed. Neither does the characters per page method. 1 screen = 1 page does, yes.

[Sirtel]

Originally Posted by JSWolf

Has the bug in KePub been fixed where it's not always 1 screen = 1 page?

No idea. I don't have the page count displayed on my Kobos when I'm reading.