Beta testers for calibre 9 needed - Page 16

JSWolf · 01-07-2026, 05:16 PM

Quote:

Originally Posted by Karellen

Thank you

Yea, but I prefer this method for the copyright page.
I am not aware of any functional differences between the two methods.

Functionally no difference. Codewise, a big difference. One uses less code. The other uses more code. One follows the rule of keep it simple. The other does not.

DNSB · 01-07-2026, 06:32 PM

Quote:

Originally Posted by JSWolf

Functionally no difference. Codewise, a big difference. One uses less code. The other uses more code. One follows the rule of keep it simple. The other does not.

Jon, in case you missed the title of the thread, it is for discussing the beta testing of calibre 9. It is not for your endless kvetching that other people choices in editing ebooks does not agree with your choices.

kovidgoyal · 01-07-2026, 11:25 PM

Released new beta 8.99.4. It has only minor bug fixes, as reported by various people since the last beta.

* Re-organize shelf preferences and make the templates for line1 and line 2
* Fix a regression where copying from editor would convert nbsp to normal space
* Bookshelf: Respect tweaks for enter and double click actions
* Update pages column of restoring book/fmt, deleting fmt, editing fmt via editor
* Add an option to redo page counts even for unchanged books when clicking the recount pages button

nqk · 01-08-2026, 03:32 AM

Quote:

Originally Posted by kovidgoyal

* Update pages column of restoring book/fmt, deleting fmt, editing fmt via editor

Thank you.

Now the page count is different from how the viewer counts it? Even for books with no publisher page count, the viewer pages are quite different from the new page count result.

kovidgoyal · 01-08-2026, 04:23 AM

Quote:

Originally Posted by nqk

Thank you.

Now the page count is different from how the viewer counts it? Even for books with no publisher page count, the viewer pages are quite different from the new page count result.

yes, they are different. Changing the viewer page count to match the column is rather dangerous since the go to location (by position) function in the viewer uses these counts so if the user happens to have saved some position numbers, using them on a book with a changed page count will go to an incorrect location. Users *shouldnt* have been doing this, as the viewer provides both reference mode and CFI based locations for more robustness, but no way to be certain they have not. Therefore, I have not changed the viewer algorithm.

un_pogaz · 01-08-2026, 05:08 AM

Also, since the Page Column use a simplification of render emulation, when the viewer use the real formating to acount of it count, theirs values will always be different.
We could use the render of the viewer, but the performance of such things make it out of the question. And this will miss the mark that Page Column is just a quick average estimation for side-to-side comparaison, never intended to be "accurate" (for whatrvre that mean on refloawble).

---

Else
@Kovid, I'm considering adding a system of custom emblem (but only render the first that match), but before work on it, I ask you:
What would be the best behavior to take in the case if the three emblem are visible (custom, pin and device)?

nqk · 01-08-2026, 05:45 AM

Thank you. I understood the situation. The good thing for me is that most of my books have built-in publisher page numbers, and it is now counted (which I had to manually enter). The built-in publisher pagination is supported by many readers, including Calibre, Koreader, Moon Reader...

kovidgoyal · 01-08-2026, 07:42 AM

Quote:

Originally Posted by un_pogaz

@Kovid, I'm considering adding a system of custom emblem (but only render the first that match), but before work on it, I ask you:
What would be the best behavior to take in the case if the three emblem are visible (custom, pin and device)?

You would put them side my side, halving their size. That way you can allow up to two emblems. Or you can put them at the bottom and top of the spine (not above and below it, that way you also get two emblems, but with larger size).

un_pogaz · 01-08-2026, 08:04 AM

Quote:

Originally Posted by kovidgoyal

You would put them side my side, halving their size. That way you can allow up to two emblems. Or you can put them at the bottom and top of the spine (not above and below it, that way you also get two emblems, but with larger size).

I will experiment with that, maybe option, thanks.

DisabledReader · 01-09-2026, 04:11 AM

I use the Count Pages plugin so have created a custom column called Pages (#pages).
With the new Beta you have added an internal column called Pages (pages).

This has the potential of causing a great deal of confusion and probably many bug reports.

un_pogaz · 01-09-2026, 06:03 AM

Quote:

Originally Posted by DisabledReader

I use the Count Pages plugin so have created a custom column called Pages (#pages).
With the new Beta you have added an internal column called Pages (pages).

This has the potential of causing a great deal of confusion and probably many bug reports.

Confusion? Yes.
Bug reports? I don't think so.
In any case, I affraid we can do nothing to that.

JSWolf · 01-09-2026, 06:36 AM

Quote:

Originally Posted by un_pogaz

Confusion? Yes.
Bug reports? I don't think so.
In any case, I affraid we can do nothing to that.

It may be a good idea to rename the calibre page number column. Call is maybe Pages2.

BetterRed · 01-09-2026, 08:52 AM

Quote:

Originally Posted by JSWolf

It may be a good idea to rename the calibre page number column. Call is maybe Pages2.

Problem is Jon, people have been using the beta against their 'real' libraries - and they might have rejigged templates, plugboards, action chains, whatever accordingly.

If it were to be renamed I suggest space/Space would be a better name.

theducks · 01-09-2026, 11:32 AM

Quote:

Originally Posted by DisabledReader

I use the Count Pages plugin so have created a custom column called Pages (#pages).
With the new Beta you have added an internal column called Pages (pages).

This has the potential of causing a great deal of confusion and probably many bug reports.

You can change the column TITLE for your Pages. I just made mine read PagesPI (do not change the lookup: #pages. the # makes it different)

PI = PlugIn version

Sirtel · 01-09-2026, 11:44 AM

Quote:

Originally Posted by theducks

You can change the column TITLE for your Pages. I just made mine read PagesPI (do not change the lookup: #pages. the # makes it different)

PI = PlugIn version

Yeah. No need to change the lookup name. I named the column title of mine Pạges (a with a tiny underdot).

01-08-2026, 05:08 AM	#231
un_pogaz Chalut o/ Posts: 557 Karma: 718860 Join Date: Dec 2017 Device: Kobo	Also, since the Page Column use a simplification of render emulation, when the viewer use the real formating to acount of it count, theirs values will always be different. We could use the render of the viewer, but the performance of such things make it out of the question. And this will miss the mark that Page Column is just a quick average estimation for side-to-side comparaison, never intended to be "accurate" (for whatrvre that mean on refloawble). --- Else @Kovid, I'm considering adding a system of custom emblem (but only render the first that match), but before work on it, I ask you: What would be the best behavior to take in the case if the three emblem are visible (custom, pin and device)? Last edited by un_pogaz; 01-08-2026 at 05:27 AM.

01-09-2026, 04:11 AM	#235
DisabledReader Junior Member Posts: 8 Karma: 10 Join Date: Apr 2024 Location: England Device: Amazon Fire 7 (2022 Version) & FBReader Premium	I use the Count Pages plugin so have created a custom column called Pages (#pages). With the new Beta you have added an internal column called Pages (pages). This has the potential of causing a great deal of confusion and probably many bug reports. Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
calibre 5: Beta testers needed	kovidgoyal	Calibre	497	09-29-2020 01:58 AM
Beta testers needed	kovidgoyal	Calibre	75	08-18-2019 08:00 PM
Beta testers for calibre 3.0 needed	kovidgoyal	Calibre	598	07-09-2017 11:26 PM
Beta testers needed	kovidgoyal	Calibre	54	05-20-2016 01:34 PM
Beta testers for calibre 2.0 needed	kovidgoyal	Calibre	142	05-08-2015 05:44 AM

01-07-2026, 11:25 PM	#228
kovidgoyal creator of calibre Posts: 45,837 Karma: 28586150 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Released new beta 8.99.4. It has only minor bug fixes, as reported by various people since the last beta. * Re-organize shelf preferences and make the templates for line1 and line 2 * Fix a regression where copying from editor would convert nbsp to normal space * Bookshelf: Respect tweaks for enter and double click actions * Update pages column of restoring book/fmt, deleting fmt, editing fmt via editor * Add an option to redo page counts even for unchanged books when clicking the recount pages button

01-08-2026, 05:45 AM	#232
nqk Fanatic Posts: 591 Karma: 32228 Join Date: Feb 2012 Device: Onyx Boox Leaf	Thank you. I understood the situation. The good thing for me is that most of my books have built-in publisher page numbers, and it is now counted (which I had to manually enter). The built-in publisher pagination is supported by many readers, including Calibre, Koreader, Moon Reader...