[GUI Plugin] Count Pages

[BetterRed]

Page Counts for ebooks are an utter nonsense, it's akin to measuring fuel consumption of ICE vehicles in bushels of hay a week.

A better measure would be time to read.

BR

[JimmXinu]

Originally Posted by Glsparks2

Since Calibre Version 9 creates a Pages column, I notice that the page count generated by this plugin is frequently much different that the Calibre page count. For example an epub has 364 pages per the plugin and 241 per Calibre. This is not a big deal since I realize that both are estimates but wonder if there are plans to modify the plugin to near-match Calibre's estimate.

Not trying to be snide about it, but why would that be useful?

Calibre's already counting pages that way. Count Pages producing the same number would be just a duplication of effort.

[DNSB]

Originally Posted by BetterRed

Page Counts for ebooks are an utter nonsense, it's akin to measuring fuel consumption of ICE vehicles in bushels of hay a week.

A better measure would be time to read.

BR

Word count divided by 52,000 and words divided by 48,000 gives me a decent result for reading time using the KoboTouch driver.

[theducks]

IMHO Counting Pages just gives you a COMPARISON as long as you use the same algorithm for all.
Calibre added its page count because it now has a spine view that is scaled to a count and could not rely on you having the Count Pages PI

[Sirtel]

Originally Posted by BetterRed

Page Counts for ebooks are an utter nonsense, it's akin to measuring fuel consumption of ICE vehicles in bushels of hay a week.

A better measure would be time to read.

BR

Time to read is absolutely worthless for me, as I often read in stops and starts, pausing for a few seconds or a few minutes and then continuing. Page count (based on characters per page) gives me an estimate how long the book is.

[DNSB]

For me, I use Count Pages page count to get an idea of how long the book is and I use the numbers I generate from the word count to get an idea of how long it will take me to read the book assuming that ~15% of my reading time will not be productive.

[fogice]

Originally Posted by BetterRed

A better measure would be time to read.

I used to think that, and configured my system to include TTR in the subtitle so it shows up on my Kindle. But some books are breezy reads, and some are dense slogs. I use page count (fine-tuned by using a selection of my paper books).

[DNSB]

Originally Posted by fogice

I use page count (fine-tuned by using a selection of my paper books).

The problem with page count based on paper books is that almost every paper edition has a different page count. I have one book in MMPB (2 editions), TPB and hardcover. All 4 have different page counts. Different page sizes, different fonts, different font sizes, minor changes in line spacing and margins and the page count varies from 289 to 378 pages.

[Wiggo]

In Germany, ePubs usually follow a specific paper edition.

[fogice]

Originally Posted by DNSB

The problem with page count based on paper books is that almost every paper edition has a different page count. I have one book in MMPB (2 editions), TPB and hardcover. All 4 have different page counts. Different page sizes, different fonts, different font sizes, minor changes in line spacing and margins and the page count varies from 289 to 378 pages.

I agree with everything you said. I used the pagecounts for about 20 books, tried the different available calculation methods, and iterated until the difference between calculated and "actual (for my books)" was minimized, and that's good enough for my usage.

[Leilu]

Hello,

Could you add an option to fetch page counts from Babelio, a mostly french database? I've found that Babelio is generally more accurate about page counts for french physical book editions than Goodreads.

Similarly to how it works for Goodreads, the plugin could use the Babelio ID fetched via the babelio_db plugin.

Here is a book example: https://www.babelio.com/livres/Erika...-plait/1864688 In the html code, the page count is consistently found in the "livre_refs" class. I guess a quick regex would be sufficient to fetch the number of pages.

Thank you.

[drawson1]

I use this plugin all the time to estimate book sizes ... but I NEVER use "Pages". I just count WORDS, which should be both correct and consistent between editions. The plugin does include a word-count algorithm that supports multiple locales.

It did take a few weeks of usage to get to the point where I could relate the word count to the reading time and my experience with other books.

I've added a custom column with the "Words" data - I can highly recommend this approach.

[kiwidude]

Release Notes
https://github.com/kiwidude68/calibr...t_pages-1.14.6

Unlike all the other plugin releases today which are being done for translation updates, this adds one new feature - support for downloading from babelio.com as requested above.

[JSWolf]

delete post

[DNSB]

Originally Posted by JSWolf

You should not be fixing the output warning. Others in this thread told me that when I fixed the output warning and posted the fixed version. In fact, it was removed. So maybe this version will also be removed.

Why would it be removed? If done properly using r for raw strings such as file paths and other literal strings and escape sequences for special characters (yes, also normal characters for those who are feeling a questionable love for octal, hexadecimal and Unicode characters set individually), there are no issues back to Python 1.5.

It also may be that I simply have more trust in @kiwidude having tested his modifications with multiple calibre/python versions instead of this version works with calibre 9 so all must be okay.