Glo Inaccurate page count...

[CatherineStewart]

So my side-loaded epubs will say at the bottom I'm on page 65 of 580. But it takes anywhere from 2-5 page turns for it to actually go up a page (page 66 of 580) depending on the book. Is it my formatting in calibre that is doing this? How can I get an accurate page count?

[PeterT]

The page count # is based on 1024 characters per page; not on the number of page clicks you see on the device.

[davidfor]

And exactly how many page clicks (presses? turns?) are needed depends on the font size, margins and line spacing used.

[piratepanda]

This is the most useless feature ever. Why don't they just increase or decrease the page count accordingly? The current behaviour makes page numbers useless.

[davidfor]

It is the standard page numbering when reading an epub with ADE. The desktop version of ADE does the same thing and other ereaders do as well. Personally, I like it as the page numbering doesn't change with screen size, font size or other settings.

Kobo also has the kepub reader. This does do page per screen no matter the other settings. If you put the epubs on as .kepub.epub, it uses this reader.

[GreatCanadian]

Originally Posted by davidfor

If you put the epubs on as .kepub.epub, it uses this reader.

How is that done? I didn't know you could do that.

GC

[davidfor]

See http://www.mobileread.com/forums/sho...d.php?t=193294

[GreatCanadian]

Thanks. Appreciate it!

GC

[rashkae]

The pager number count is far from useless. To start with, it is the same numbering scheme used on all Adobe Digital Editions based e-book readers.. a reference to page 155 on your book will be the same as page 155 on your friend's Sony reader, regardless of font / margin preferences.

For another, the total size of books (in pages) is relatively accurate, (with some variance for the amount of html code used you don't see and compression.) A 600 page book will have twice as much text to read as a 300 page book.

[CatherineStewart]

Hmmm. I don't really like that method of pages per chapter. I like total book page count and would rather it be accurate per page turn not characters per page. I wonder if there is another work around? Not a big deal but would be nice.

[guma]

There is, unfortunately, no easy workaround. Theoretically you could manipulate the epub in calibre or sigil and insert page breaks, but this requires a complex script and would be valid only for 1 set of font and margin settings on the KOBO.

I too would love to see an option that lets you chose whether standardized page counts (1024 characters per page) or the number of screens on device (according to the font and margin settings used) are displayed.

I can understand the arguments for setting-independent page counts in electronic books. But (1) my personal preference would be for screen counts (since I do not require fixed page numbers for recreational reading) and (2) I cannot find two devices actually giving the same page counts on my epubs (all of these readers that do not count screens, e.g. KOBO vs. calibre reader vs. some andoid epub reader the name of which I forgot).

[davidfor]

Originally Posted by guma

I can understand the arguments for setting-independent page counts in electronic books. But (1) my personal preference would be for screen counts (since I do not require fixed page numbers for recreational reading) and (2) I cannot find two devices actually giving the same page counts on my epubs (all of these readers that do not count screens, e.g. KOBO vs. calibre reader vs. some andoid epub reader the name of which I forgot).

You need to compare two ADE based readers. The ADE desktop does it the same way as Kobo devices for epub. The calibre viewer definitely doesn't. It uses the same sort of rule but its calculation is different. I have read what it is but don't remember. The Android reader won't be ADE based, so unless they have it reproduces the calculation, it won't have the same page numbering. The "Count Pages" plugin for calibre has options for how to calculate the number of pages. One is using the ADE algorithm.

Nowadays, I don't pay much attention to the current page number. I tend to use the percentage read with the total pages. That gives me a good idea how far I am through the book.

[davidfor]

Originally Posted by CatherineStewart

Hmmm. I don't really like that method of pages per chapter. I like total book page count and would rather it be accurate per page turn not characters per page. I wonder if there is another work around? Not a big deal but would be nice.

That's one of the reasons I don't use it. That plus the book title is always on the screen. But, I like the reading stats that it shows.

Changing the numbering scheme is a very popular request. Kobo haven't done anything yet. And I am not expecting them to.

[DNSB]

Originally Posted by PeterT

The page count # is based on 1024 characters per page; not on the number of page clicks you see on the device.

Correct me if I am wrong on this but my impression is that ADE uses 1024 compressed characters which means the character count on a "page" can vary depending on how compressible the data happens to be. I may be very wrong here (it's happened once or twice ) and if someone has a better read on the algorithm, I'll be happy to learn I'm wrong.

Regards,
David

[PeterT]

Ah yes... See http://bookclubs.barnesandnoble.com/...ng/td-p/691602 for instance.

Thanks for the correction!