[GUI Plugin] Count Pages

[Comfy.n]

Originally Posted by Pendragn

Is there a way to customize the menu icon for Count Pages? I've customized my theme and icons for the rest of calibre, and I'd love to change the Count Pages icon to match

You want to create the following structure in your calibre config dir:

portable calibre:
"C:\CALIBRE_8\Calibre Settings\resources\images\Count Pages\count_pages.png"

for calibre main install, on Windows, this would be:
"C:\%appdata%\calibre\resources\images\Count Pages\count_pages.png"

[Pendragn]

Originally Posted by Comfy.n

You want to create the following structure in your calibre config dir:

portable calibre:
"C:\CALIBRE_8\Calibre Settings\resources\images\Count Pages\count_pages.png"

for calibre main install, on Windows, this would be:
"C:\%appdata%\calibre\resources\images\Count Pages\count_pages.png"

Thank you!

[JSWolf]

Due to a change in the version of Python in the new calibre beta, there is a warning that comes up when you run calibre in debug mode. If fixed this and I've upped the version to 1.14.5.

Here is the warning and the fix.

calibre_plugins.count_pages.statistics:415: SyntaxWarning: "\D" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\D"? A raw string is also an option.
calibre_plugins.count_pages.statistics:416: SyntaxWarning: "\D" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\D"? A raw string is also an option.

    get_cbz_page_count(r'''C:\Dev\Tools\eclipse\workspace\_Misc\misery-depot.zip''')
    get_cbr_page_count(r'''C:\Dev\Tools\eclipse\workspace\_Misc\misery-depot.cbr''')

[PeterT]

@jswolf please don't take this the wrong way. You're making a mountain out of a molehill here. The warning is in a section of code that is only executed when the plugin is being tested; it's a purely cosmetic message in the calibre log.

[JSWolf]

Originally Posted by PeterT

@jswolf please don't take this the wrong way. You're making a mountain out of a molehill here. The warning is in a section of code that is only executed when the plugin is being tested; it's a purely cosmetic message in the calibre log.

According to @DNSB, this is going to become an error in some newer version of Python. So why not get it sorted now rather then later?

Originally Posted by DNSB

Minor correction. Python 3.14.2 still supports that syntax but it is not going to be supported in some future version. This does give time to fix the plugins that use that form.

[Terisa de morgan]

Originally Posted by JSWolf

According to @DNSB, this is going to become an error in some newer version of Python. So why not get it sorted now rather then later?

Because generating a new version only for those 2 warnings when they aren't even an error in the new calibre version doesn't make sense (at least from my point of view).

[DNSB]

For me, given that at this time those errors are cosmetic only, it makes sense to fix the issue when a new release is made for other reasons. Looking at previous release dates, Python 3.15.0 is due for release on 2026-Oct-01 and that it is unlikely that calibre 10 would be released until the version is at least 3.15.2, we have a fair while before this becomes a real issue.

[JSWolf]

Originally Posted by DNSB

For me, given that at this time those errors are cosmetic only, it makes sense to fix the issue when a new release is made for other reasons. Looking at previous release dates, Python 3.15.0 is due for release on 2026-Oct-01 and that it is unlikely that calibre 10 would be released until the version is at least 3.15.2, we have a fair while before this becomes a real issue.

But, if the author is not running the beta and/or the warning is not reported, then it won't be fixed if any other change(s) is done to the plugin. Sop IMHO, it's best to get it fixed now instead of later.

[JSWolf]

Originally Posted by Terisa de morgan

Because generating a new version only for those 2 warnings when they aren't even an error in the new calibre version doesn't make sense (at least from my point of view).

It could be that someday these warnings could change into an error. Why not have it fixed before it becomes a problem?

[jackie_w]

deleted

[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.

[theducks]

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.

How did you configure (customize) the PI's page count rule?
FWIW I use the APNX mode and it says 553 while the new pages says 390
And if I use the calibre viewer mode it goes over 900

[DNSB]

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.

Which page count algorithm are you using with Page Count? Every algorithm produces different page counts. For me, I use the Adobe Synthetic Page Count algorithm just to have consistency. The one used to produce the Page column is pretty simple and designed for speed.

As for calibre's page counts? I open a book in the calibre ebook-viewer and the last page is labelled as 2069. Count Page (ASPN) gives me 2430 and calibre's Pages shows 2222.

Asides, worrying about page counts in a reflowable format is like arguing about how many angels can dance on the head of a pin. It may be fun but in the end nothing will be decided.

[Glsparks2]

Originally Posted by theducks

How did you configure (customize) the PI's page count rule?
FWIW I use the APNX mode and it says 553 while the new pages says 390
And if I use the calibre viewer mode it goes over 900

Ahh! It has been a decade, maybe, since I looked at that. I will check my settings and tweak them. Thank you!

[Glsparks2]

Originally Posted by DNSB

Which page count algorithm are you using with Page Count? Every algorithm produces different page counts. For me, I use the Adobe Synthetic Page Count algorithm just to have consistency. The one used to produce the Page column is pretty simple and designed for speed.

As for calibre's page counts? I open a book in the calibre ebook-viewer and the last page is labelled as 2069. Count Page (ASPN) gives me 2430 and calibre's Pages shows 2222.

Asides, worrying about page counts in a reflowable format is like arguing about how many angels can dance on the head of a pin. It may be fun but in the end nothing will be decided.

Agree! I had forgotten about the settings of the plugin. Thank you!