Change page numbers

[DNSB]

Originally Posted by Frenzie

as to whether it's actually displaying the proper page number or not, what is part of which page, etc.

Are we trying to revive the page number wars? I have one academic text in 3 editions in the corporate library. All are 3rd edition. The original hardcover, the paperback and the re-issue of the hardcover do not have the same number of pages.

[Frenzie]

Originally Posted by DNSB

Are we trying to revive the page number wars?

I've never experienced these page number wars you speak of, but I shouldn't think what I said to be terribly controversial. It still allows for the obvious best of both worlds approach of including it in the flow of the text as well as at the bottom of the page, for example. Not to mention making it a simple toggle switch.

If the page numbers are different anyway, then naturally there's no value to trying to make "paper" numbers display at the bottom on a digital screen. But that sounds like a case of a bad paperback and a bad reissue, hardly as a problem with page numbers per se. I have encountered an odd reissue myself,[1] but never a bad paperback. (Assuming we're talking about academic publications.) I've also encountered a few academic EPUB publications that use the paper page in the flow of the text method. I liked those.

[1] Perhaps not precisely a reissue, but the content was exactly the same except that it was missing the references at the end of each chapter. Absolutely stupefying.

[DNSB]

Originally Posted by Frenzie

If the page numbers are different anyway, then naturally there's no value to trying to make "paper" numbers display at the bottom on a digital screen. But that sounds like a case of a bad paperback and a bad reissue, hardly as a problem with page numbers per se. I have encountered an odd reissue myself,[1] but never a bad paperback. (Assuming we're talking about academic publications.) I've also encountered a few academic EPUB publications that use the paper page in the flow of the text method. I liked those.

The content is pretty much identical between the three variants other than correcting a couple of typos that the original included on an errata sheet. The paperback has smaller pages and slightly smaller font size so the content takes more pages. The re-issue uses a different body font and slight format changes so it's page count is slightly lower than the original.

I would not refer to any of them as "bad". Smaller pages in the paperback (actually closer to a small trade paperback size) edition are going to require more pages or a significantly smaller body font size to keep the page numbering somewhat consistent. Even the change in the body font in the re-issue was enough to change the total page count.


There have been several rather heated discussions about page numbering in ebooks with some posters wanting a "golden" page numbering system so the page numbers in any edition of either pbooks or ebooks would be consistent.

[Knightreader]

My personal problem with counting "one page per page turn" is the drastic difference between the total page count in the footer of my Kobo with a higher font size and the total page count via the "count pages" plugin in Calibre. Calibre says 470 pages total but the ebook on the Forma shows a total number of 620 pages. That's a bit crazy but it's the current state with the new firmware. I wish to choose by myself which counting I prefer, the "one page per turn" or an algorithm count.

[geek1011]

Originally Posted by Knightreader

My personal problem with counting "one page per page turn" is the drastic difference between the total page count in the footer of my Kobo with a higher font size and the total page count via the "count pages" plugin in Calibre. Calibre says 470 pages total but the ebook on the Forma shows a total number of 620 pages. That's a bit crazy but it's the current state with the new firmware. I wish to choose by myself which counting I prefer, the "one page per turn" or an algorithm count.

Yes, and for me, I had all my readers more or less matched (ePubViewer, modded Lithium on Android, my fork of Foliate, a few tools I wrote, and I could also estimate paper pages relatively well).

One thing I might try doing as well as try page maps is to see if it is possible to show the current koboSpan, as that would solve most of my issues with the new numbering (and a few more).

[JSWolf]

Originally Posted by Knightreader

My personal problem with counting "one page per page turn" is the drastic difference between the total page count in the footer of my Kobo with a higher font size and the total page count via the "count pages" plugin in Calibre. Calibre says 470 pages total but the ebook on the Forma shows a total number of 620 pages. That's a bit crazy but it's the current state with the new firmware. I wish to choose by myself which counting I prefer, the "one page per turn" or an algorithm count.

If you have the estimated page count, you are getting the ADE page count. If not, you're getting some pBook page count that's totally off the rails for an eBook.

[Knightreader]

Originally Posted by JSWolf

you are getting the ADE page count.

That's what I see in Calibre with the "Count Pages" plug-in.

But the new firmware gives back ONLY the one-per-page-turn-count for kepub files. No other options. For some user it's perfect, but I prefer the Adobe count. Don't have problems with 2 or 3 same page numbers with turning pages. Would be nice to get more options for the display.

[davidfor]

Originally Posted by Knightreader

But the new firmware gives back ONLY the one-per-page-turn-count for kepub files. No other options. For some user it's perfect, but I prefer the Adobe count. Don't have problems with 2 or 3 same page numbers with turning pages. Would be nice to get more options for the display.

For the record, the previous full book page numbering for kepubs did not use the Adobe algorithm. Adobe's method is basically dividing the size of the internal compressed files by 1024. Kobo's method for kepubs was used 320 words per page. These methods gave very different numbers.

[Frenzie]

Originally Posted by davidfor

Adobe's method is basically dividing the size of the internal compressed files by 1024. Kobo's method for kepubs was used 320 words per page.

The latter would give much slower yet almost equally inaccurate numbers. That sounds like an odd choice. (Unless it's done at creation time.)

[Terisa de morgan]

Originally Posted by davidfor

For the record, the previous full book page numbering for kepubs did not use the Adobe algorithm. Adobe's method is basically dividing the size of the internal compressed files by 1024. Kobo's method for kepubs was used 320 words per page. These methods gave very different numbers.

Is it possible to implement the method with kepubs with the CountPages plugin?

[davidfor]

Originally Posted by Frenzie

The latter would give much slower yet almost equally inaccurate numbers. That sounds like an odd choice. (Unless it's done at creation time.)

Kobo calculate the word count for each chapter the first time you open a book and store that. And if you watched the page count at that time, it turned wasn't fast. But, it works. When you reopen the book, it's fast. They also use the word count for the in-book stats.

[Knightreader]

Originally Posted by davidfor

the previous full book page numbering for kepubs did not use the Adobe algorithm. ... Kobo's method for kepubs was used 320 words per page. These methods gave very different numbers.

But the old Kobo method was closer to the number of pages calculated with the Count Pages plugin with ADE algorithm ... and closer to the total page count published by the publisher for the printed book.

My only problem is, personally, that I don't like the current page per turn count. And I can't choose another option except percent or remaining time. But now it's enough moaning about that ...

[Phil_C]

Originally Posted by Terisa de morgan

Is it possible to implement the method with kepubs with the CountPages plugin?

The Count Pages plugin gives you a count that can be placed in a calibre custom column. It does not change the way your Kobo will display page numbers in a book you are reading.

I, too, prefer the Adobe page count. For me, it is a more "realistic" count that approximates a typical print book and gives me a good feel for a book's length. Sometimes I am in the mood for a short read, sometimes a long read. That comes into play when I am choosing my next read.

I wanted to have this information somewhere in each book on the Kobo. With the help of some posts elsewhere in this forum and a bit of trial and error, I found a way to send the total page count for each book from calibre to the Kobo. The count appears on the Book Details page of each book.

This can be dome manually from within the Kobo Utilities plugin, but a better way is via a Metadata Plugboard that can automatically do the job when you send books to the Kobo. The code for either method looks like this...

{#pg_ct:|<p>Pages: |</p>}{comments}

...where my calibre custom column lookup name is #pg_ct.

[Terisa de morgan]

Originally Posted by Phil_C

The Count Pages plugin gives you a count that can be placed in a calibre custom column. It does not change the way your Kobo will display page numbers in a book you are reading.

I, too, prefer the Adobe page count. For me, it is a more "realistic" count that approximates a typical print book and gives me a good feel for a book's length. Sometimes I am in the mood for a short read, sometimes a long read. That comes into play when I am choosing my next read.

I wanted to have this information somewhere in each book on the Kobo. With the help of some posts elsewhere in this forum and a bit of trial and error, I found a way to send the total page count for each book from calibre to the Kobo. The count appears on the Book Details page of each book.

This can be dome manually from within the Kobo Utilities plugin, but a better way is via a Metadata Plugboard that can automatically do the job when you send books to the Kobo. The code for either method looks like this...

{#pg_ct:|<p>Pages: |</p>}{comments}

...where my calibre custom column lookup name is #pg_ct.

What you're telling is very similar to my method. I include the number of pages as book subtitle, so I can see it in the library. I would want to have, however, the kepub count (I prefer to be more in the range of the ereader, Adobe calculation says nothing to me aside of a mesure), without:

1. Create a column for words
2. Create an additional column that calculates words / 320
3. Change my kobo extended driver configuration for including as subtitle this new column

Anyway, I've read again David's post... and it is the old method, not how it's calculated now (on the fly), so it's not necessary either.

[Knightreader]

I also have a custom column (called #pages) in Calibre for the result of the Count Pages Plugin. I use the ADE algorithm because I tried all methods for various ebooks and compared it to the total page count provided by publishers. And the ADE algorithm gives back the best result for me(!).

In the KoboTouchExtended Plugin on the metadata tab I activated the subtitle with
"{#pages} Seiten" (it's in German for me) and so I find the calculated total page count in the library as subtitle and in the book detail information on the reader.