[GUI Plugin] Count Pages

[JimmXinu]

I'm reasonable certain that this discussion has happened before. Repeatedly. And that we've all agreed to disagree amicably.

I'm much more interested in "Yes, this fix works" or "No, it doesn't" so I know whether to release it or not.

[JSWolf]

Originally Posted by JimmXinu

I'm reasonable certain that this discussion has happened before. Repeatedly. And that we've all agreed to disagree amicably.

I'm much more interested in "Yes, this fix works" or "No, it doesn't" so I know whether to release it or not.

I don't disagree with releasing the fix. I just disagree with pBook page numbers for eBooks. Users can use whatever page number they want. I'm just putting in my 2 cents as to why not to use pBook page numbers.

[CRussel]

Originally Posted by JimmXinu

New Test Version

2025-10-09
- Update for goodreads.com site change

The site has changed to sending all the book data as a big Javascript data structure instead of HTML.

Fixed. THANK YOU.

[JimmXinu]

Release Notes:
https://github.com/kiwidude68/calibr..._pages-v1.14.0

[1.14.0] - 2025-10-10
Fixed
- Goodreads page count web scraping broken from website changes.
Changed
- Updated translations

[alva]

i now get the pages from good reads again but the reading index values stay empty

[JimmXinu]

Are you referring to the Gunning Fog Index?

When I configure that to run, I do get an error in the job log:

Traceback (most recent call last):
  File "calibre_plugins.count_pages.jobs", line 211, in do_statistics_for_book
  File "calibre_plugins.count_pages.statistics", line 379, in get_text_analysis
  File "calibre_plugins.count_pages.nltk_lite.textanalyzer", line 22, in __init__
ModuleNotFoundError: No module named 'copy_reg\r'

Also reported in https://github.com/kiwidude68/calibr...ins/issues/139

That '\r' is the problem.

CP bundles a partial Natural Language Toolkit (NLTK) library. Part of that is a data structure that's been stored with python's 'pickle' (nltk_lite/english.pickle).

Long story short, .git needs to be told *.pickle is binary.

[JimmXinu]

Release Notes:
https://github.com/kiwidude68/calibr..._pages-v1.14.1

[1.14.1] - 2025-10-14
Fixed
- nltk_lite/english.pickle needs to be binary, windows eol treatment broke it.

[alva]

Originally Posted by JimmXinu

Are you referring to the Gunning Fog Index?

That and the Flesh index.

It works again after the update thanks a lot

[Waylander]

Count Pages plugin is now working again, many thanks to JimmXinu for updating it.

I know I've asked this question before, but is there any chance that the PW6 might get Calibre-set page numbers, as previous Kindle models did?

[finch6]

Great, working again for me too!! Thanks Devs!

Any chance we could get Hardcover.app as a source?

[JSWolf]

Originally Posted by Waylander

Count Pages plugin is now working again, many thanks to JimmXinu for updating it.

I know I've asked this question before, but is there any chance that the PW6 might get Calibre-set page numbers, as previous Kindle models did?

What you do is set a column for the the page number. Then you use that column to generate the page number when you send a KF8 eBook to your Kindle.

Go to Preferences > Plugins > Device Interface plugins > Kindle 2/3/4/Touch Device Interface. Click Customise plugin. Type the name of the custom column you set up for the count pages plug-in page numbers.

The column name I use is #pages.

[shamanNS]

PW6 being a MTP device isn't using that device plugin.
Calibre's MTP plugin was relatively recently updated to generate apnx files.

[Waylander]

Originally Posted by shamanNS

PW6 being a MTP device isn't using that device plugin.
Calibre's MTP plugin was relatively recently updated to generate apnx files.

I didn't know! I'm deleting and resending all my books now. I know there're strong disagreements about whether these page numbers from physical books even make sense for an ebook given the number of different display permutations, but I'm afraid for me it's a hangover from my print-dominant days, and for me it just doesn't feel right without page numbers, so I'm very pleased to hear about this update.

[shamanNS]

IMHO page count makes sense only if it's based on constant criteria ( = number of characters). Then it's useful for comparing multiple books.

[JSWolf]

Originally Posted by shamanNS

IMHO page count makes sense only if it's based on constant criteria ( = number of characters). Then it's useful for comparing multiple books.

That's how ADE/RMSDK Page numbers work. RMSDK page numbers used 1024 compressed characters per page. It's very useful for figuring out how long a book is. Print page numbers are useless.

So what you can do is convert Kindle eBooks to ePub, get the ADE page count and then delete the ePub. Use that page number for calibre to do the Kindle page numbers.