Sick of Amazon Kindle books without Page Numbers... - Page 12

Tex2002ans · 04-05-2016, 06:37 AM

Edit Note: Turns out in the few hours I had the tab open and typed up this post, a lot more posts were made. I will have to read/absorb/incorporate those in a later post. Sorry if I missed you or your insights.

Quote:

Originally Posted by JSWolf

Sorry, but page numbers do make sense. Have you not been reading about ADE page numbers? ADE page numbers are exactly the same with the same eBook on any screen size, font size, margins, font, line-height, etc. What page numbers are you talking about?

I suspect a lot of the wording is getting confused because of multiple simultaneous usages of the word "page".

Many people use the word page to refer to "physical pages", while others mean "screens" (as in what text shows up on the screen of their device), and others are using it to mean the auto-calculated number of "pages" by ADE/Kindle.

In this case, MikeB1972 clearly meant the ADE-case.

Quote:

Originally Posted by MikeB1972

If you are switching between ADE readers and know the page number you were on, it's close enough to manually synch the readers. Probably useful enough if you have multiple readers from different manufacturers (and read the same book on multiple devices).

Paragraph number would of course be handier

I wrote about this in the forums before, but in my experience, I found a search for 4 words can typically lead you to an exact location anywhere within a book. I find this to be a much more "neutral" way of searching across different devices/formats of the same book.

A few times I was told by professors that the 3- or 4-word method is unwieldy, but I don't see much difference between saying:

"Turn to page 123" and "Turn to page 123, where he says, 'the wind blew westward'."

Students reading (that specific version) the physical book spend time turning to 123, and the digital students search for "the wind blew" or "the wind blew westward". Everyone reaches the same spot whether they have Physical/EPUB/MOBI/PDF/HTML/whatever!

Quote:

Originally Posted by MikeB1972

Except with a paper edition you can track down an old version, that isn't possible with ebooks.

I agree. Typically you can only get your hands on the "latest and greatest" version of the ebook. Typically Amazon/B&N/whoever is trying to make these things so "user-friendly", and they don't offer any sort of method to even get to the older versions.

Ebooks typically go through a handful of minor versions (such as fixing a few typos, fixing a broken link, fixing CSS, compressing images, [...]), medium overhauls (inserting higher quality images), or they may go through major overhauls (cleaning up a ton of absolutely crappy code... which is what I do in many cases).

To my knowledge, specific versions of ebooks are not marked in any sort of standard way, and there doesn't seem to be any sort of hashed database of different versions of ebooks (and heaven forbid the big publishers would ever pull something like this. This isn't even bringing into the discussion of DRM mucking up hashing systems).

Even between stores, there may also even be tiny variations and differences between the same formats (Smashwords might run it through their "Meatgrinder", B&N might strip out a few CSS for no good reason, Amazon might strip out fonts, iTunes may need a tiny xml file for enabling fonts, maybe some other store does a Calibre conversion of your book, one store needs a cover of ###px x ###px, [...]).

In my experience, there are definitely many more minor variations of ebooks than their physical counterparts.

Side Note: I have even seen books go backwards in quality in later versions (in the case of "A Song of Ice and Fire" EPUBs that I purchased, the image quality became lower in a later version of the EPUB). I considered this a large downgrade (although they did fix a few typos + fix the CSS).

Quote:

Originally Posted by issybird

I'm in the very useful camp, myself. ADE page numbers are consistent, let me switch among my devices, and also allow me to calculate an accurate percentage for amount read, one that eliminates the extraneous.

Let me fix that for you: "Lets you switch between the same file on your ADE-based readers."*

ADE page numbers are only good across ADE-based devices, just as Kindle page numbers are only correct based on Kindle-based ereaders. Problems occur when you want to leave that specific ecosystem.

If you try to Kindle -> ADE, ADE -> Kindle, ADE -> other EPUB readers (there are a ton out there, particularly on Android), EPUB/Kindle -> other digital formats... those "page numbers" become worthless (just as "screen" numbering systems are worthless outside of those devices/settings).

I put ADE-numbering + Kindle-numbering in the same category (Byte Methods), and they have the same, although slightly different, pitfalls:

Categorization

I sort of came up with these categories while brainstorming tonight:

Page Numbers
- This is what is/has been used in physical books.
- Pro: It works well when there is only a single version of a book.
- Pro: It allows easy reference to ~300-800 words in a specific version of a specific book.
- Pro: You can easily/concisely cross-reference within your own book (in the case of an Index or text)
  - Example: "See the discussion on Page 38."
- Con: It only works on that very specific version of the book (Publisher, Year Printed, Edition #, Large Print, [...]).
"Screen" Numbers
- This is the method that was used in many earlier ereaders.
- This method would show you how many "screens" are left until the end of the book, and would change based on the font + font size + margins chosen on the device.
- Con: It fails dramatically when any of the variables (font + font size + margins + screen size) change, or if a different size device is used.
  - This alone makes it impossible to use for referencing.
- John F explained his journey with "screen numbers": https://www.mobileread.com/forums/sho...&postcount=151
Percentage
- While very helpful for gauging how far you are in an individual book, this is absolutely too broad + no good in referencing.
- Note: As JSWolf mentioned, 1% of a 20,000 word book = 200 words. 1% of a 200,000 word book = 2,000 words... Percentage is no good across books, it is only good for individual books. Combined with the time it took to reach a given percentage, it gives you a rough approximation of how long the entire book would take. As we also know, people read different books at different paces (for example, I read very dense non-fiction works... which take MUCH longer for me to read compared to fiction books).
Byte Method
- Pro: Doesn't matter what variables you use. Numbering is based on the HTML file itself.
- Note: See my "X characters of WHAT?" list in this post for some of the complications to consider: https://www.mobileread.com/forums/sho...85#post3290585
- Amazon/Kindle
  - 150 uncompressed bytes per "location"
  - Con: Because it is uncompressed, this method greatly inflates the "locations" count blows WAY out of control if the HTML is hideous (see examples below).
- ADE
  - 1024 compressed bytes per "page"
  - Pro compared to Kindle: Because it is compressed, this gets rid of a lot of the HTML cruft (hopefully the tags/overhead compresses well). This gives a slightly better approximation of actual displayed characters, and closer to physical page numbers.
    - If the code is clean, you can probably get a rough approximation of ~500 words per "page".
- Con: I find a huge problem with this method is that it doesn't deal with the actual displayed characters... all of the overhead is included, which can make/break the "page" calculation.
Paragraph Count
- Pro: This method would be neutral across all versions of the text.
  - Paragraph 10 in ebook = paragraph 10 in hard cover = paragraph 10 Large Print = paragraph 10 in horribly coded dreck.
- Con: As I mentioned in the "X characters of WHAT?", this may get thrown off if text is shifted around (for example, moving the TOC to the back of the book or footnotes getting moved to the end of a chapter), or if the functionality of whole parts of a book are shifted to other files (such as an NCX file instead of an actual TOC).
  - Note: Probably better to come up with some sort of per chapter or per subsection paragraphing system. (Sort of like the Bible: "Chapter: Verse")
Line Count
- Note: I would say this is a physical book thing. This has many of the pitfalls of the "Screen" numbering, or the physical book method with different variables (differences between Hard/Soft/Large Print, [...]).
Word Count
- Note: Depends heavily on what you count as a "word".
  - Do you count numbers as a word? There are quite a few differences between "word counts". For example, Microsoft Word/Sigil/Calibre all disagree and vary in "word count" by tiny margins.
- My personal thoughts on this method... I believe it is "too specific", and would lead to too many errors if trying to reference it.

Technical Details on the "Byte Method"

According to the MobileRead Wiki:

https://wiki.mobileread.com/wiki/Adob...s#Page_numbers
https://wiki.mobileread.com/wiki/Page...Implementation

The ADE automatic "page number" algorithm says each page 1024 compressed bytes and the Kindle goes by every 150 uncompressed bytes.

The problem I find with the Byte Methods is that the file may change (maybe more efficient/different code in the backend), but the text itself will not change.

As an example, let us look at three different versions of the same paragraph:

Example #1: Really bloated code for a single paragraph:

Quote:

Lessequibus quisciatem. Nam atem dest, consedignis ab ipicte experis dolupta sperchi liquunt, consequibus eatem quidemo corpor senihic tatemporum eliqui cusam fuga. Dia dunto cori od quaernat iusam

Example #2: Compared to this Calibre conversion (it takes those redundant "styles" and shifts them to the CSS file instead). This HTML + CSS (CSS not shown) makes it functionally equivalent to the above:

Quote:

Lessequibus quisciatem. Nam atem dest, consedignis ab ipicte experis dolupta sperchi liquunt, consequibus eatem quidemo corpor senihic tatemporum eliqui cusam fuga. Dia dunto cori od quaernat iusam

Example #3: And this would be a cleaner version:

Quote:

Lessequibus quisciatem. Nam atem dest, consedignis ab ipicte experis dolupta sperchi liquunt, consequibus eatem quidemo corpor senihic tatemporum eliqui cusam fuga. Dia dunto cori od quaernat iusam

The displayed text would be exactly the same for all three:

Quote:

Lessequibus quisciatem. Nam atem dest, consedignis ab ipicte experis dolupta sperchi liquunt, consequibus eatem quidemo corpor senihic tatemporum eliqui cusam fuga. Dia dunto cori od quaernat iusam

Displayed Characters: 197
Words: 27

Example #1: 3122 bytes
Example #1 (Kindle): 20.8 "locations"
Example #1 (1024 uncompressed): 3.05 "pages"
Example #1 (ADE)*: (rounded up to 1)

Example #2: 1186 bytes
Example #2 (Kindle): 7.9 "locations"
Example #2 (1024 uncompressed): 1.15 "pages"
Example #2 (ADE)*: (rounded up to 1)

Example #3: 227 bytes
Example #3 (Kindle): 1.51 "locations" (rounded up to 2)
Example #3 (1024 uncompressed): .22 "pages"
Example #3 (ADE)*: (rounded up to 1)

* Note: I am not too sure how to calculate the exact compressed byte count calculated by ADE, but they are all less than 1... there is a lot of repeat information in the HTML, and text compresses very well.

Pitfall of Byte Counts

Let us say in the future, Amazon decides to run their ebooks through a more efficient conversion program (maybe they figure out a way to generate code with less cruft, or maybe they come up with something like KFX did with "better typography", and they run all the old backlog files through the new conversion).

Example #2 might occur on a book with a Calibre conversion (the HTML itself might change, but the code will still be functionally equivalent).

Or in Example #3 (if I do a major overhaul of the hideous code backend).

The "locations" and ADE "page numbers" change, even though the text itself is exactly equivalent (and this is what is important when referencing or reading). People care about the actual DISPLAYED text, not any of that HTML backend.

Note: I don't know off the top of my head how HTML comments are handled (or metadata tags such as <title>, <head>, [...]) in the ADE/Kindle methods. Does all of that metadata count? Or is it just what is between <body> tags? I know that MOBI strips out all HTML comments.

John F · 04-05-2016, 08:05 AM

FWIW it's worth, my post with "one" was an attempted joke/jab at another discussion about the use of the word "one". Sorry for the obscure reference, I just assumed everyone reads every post and everyone would get the reference/joke/jab.

I hope the OP doesn't mind the OT post.**

** another reference to an obscure post/thread.

ApK · 04-05-2016, 08:46 AM

Quote:

Originally Posted by John F

FWIW it's worth, my post with "one" was an attempted joke/jab at another discussion about the use of the word "one". Sorry for the obscure reference, I just assumed everyone reads every post and everyone would get the reference/joke/jab.

Nope. But if you perhaps included a link to the thread in that message....

HarryT · 04-05-2016, 08:50 AM

That would indeed be helpful. Not everyone reads every thread on the board.

davidfor · 04-05-2016, 08:59 AM

Quote:

Originally Posted by HarryT

Why does the fact that some books have multiple editions make it any less useful, David? It would appear to be fairly self-evident that, if you give a page number as a reference, you have to specify which edition of the book you're referring to.

Yes, but the ebook publisher isn't going to create an ebook for every paper edition out there. People who are asking this are probably wanting to match the paper edition that is on their shelves.

For reference books, a page number and edition is probably useful. For fiction, not so much.

davidfor · 04-05-2016, 09:05 AM

Quote:

Originally Posted by latepaul

Is this something turned on in the kepub itself or in the reader options? I've not come across it on my Kobos but I don't check all the settings every time there's a firmware update.

The option to do full book page numbering for kepubs was added several firmware versions ago. At the same time, they added other options to display the location as pages, percentage or time to read. And a long press on the page number will change what is displayed. The options are on the second page of the Reading settings.

HarryT · 04-05-2016, 09:08 AM

Quote:

Originally Posted by davidfor

Yes, but the ebook publisher isn't going to create an ebook for every paper edition out there. People who are asking this are probably wanting to match the paper edition that is on their shelves.

OK, I guess there are people who would want that. Personally I use it for referencing, so I've no requirement to own the corresponding paper edition, but simply to know which paper edition it is. I find it an extremely useful facility. I couldn't use ebooks for academic purposes without it.

Solitaire1 · 04-05-2016, 04:20 PM

It seems that the issue with page numbers is that they can't be consistent, even on the same ebook on the same ereader, due to ebook formatting issues. Would a viable option be to include a marker (say a vertical bar on a line by itself) to indicate the top of a page, with everything between the bars considered one page regardless of the amount of text it contains (determined by the ebook formatting team)?

This would allow the ebook formatter to clearly indicate where each "page" begins regardless of the way the ebook is formatted. The ebook's formatting options wouldn't matter since the relative position of the "page bar" would be unchanged within the ebook. It would even allow an option for the "page bar" to be hidden if desired by the reader (if hidden the page would be formatted as if the bar didn't exist).

eschwartz · 04-05-2016, 04:24 PM

That sounds like a very needlessly complicated alternative to simply providing a Page-map or PageList.

Which as has already been indicated, is not the perfect solution it sounds like.
In fact, this whole discussion began with someone protesting that ebook publishers aren't using them^^ to curate page numbers -- so why would Yet Another Page Counting Method be any more likely to actually get used?

ApK · 04-05-2016, 04:25 PM

Quote:

Originally Posted by Tex2002ans

[..............]

Thinking about how frustrated I get when I type a whole two paragraphs and then lose it with an accidental keystroke, please tell me you compose in some other editor and then just paste all that into a forum message, right?

Solitaire1 · 04-05-2016, 04:33 PM

Quote:

Originally Posted by ApK

Thinking about how frustrated I get when I type a whole two paragraphs and then lose it with an accidental keystroke, please tell me you compose in some other editor and then just paste all that into a forum message, right?

I usually just compose my posts within the reply window and then post it to the thread. I've not had a problem doing that but I have considered writing my long posts in my word processor and then copying and pasting it to the reply window since the forum sometimes times out before I can put my post on the forum.

As far as composing a post, one option is to compose it in Notepad (if you are a Windows user) and then copy and paste it into the forum. It is also possible that you can do it with your word processor (and paste it as unformatted text to avoid any issues with the text). Then do any needed formatting within the window.

Solitaire1 · 04-05-2016, 04:38 PM

Quote:

Originally Posted by eschwartz

That sounds like a very needlessly complicated alternative to simply providing a Page-map or PageList.

Which as has already been indicated, is not the perfect solution it sounds like.
In fact, this whole discussion began with someone protesting that ebook publishers aren't using them^^ to curate page numbers -- so why would Yet Another Page Counting Method be any more likely to actually get used?

I think that the issue will be determined by the users. If enough users start to demand some sort of consistent page numbering system and start to turn away from ebooks that don't contain them, then I think there will be some movement on this issue. Otherwise, I don't think it will happen.

HarryT · 04-05-2016, 04:45 PM

Quote:

Originally Posted by Solitaire1

I think that the issue will be determined by the users. If enough users start to demand some sort of consistent page numbering system and start to turn away from ebooks that don't contain them, then I think there will be some movement on this issue. Otherwise, I don't think it will happen.

Pagemap/Pagelist files DO provide a consistent page numbering system. Have you read this thread properly? It's been explained in some considerable detail.

Angst · 04-05-2016, 04:54 PM

Quote:

Originally Posted by detayls

Five years ago Amazon added an optional feature that allows their readers to see a "real" page number. I wonder why nobody mentioned this. My original post was created in the hope of discovering why this feature is not used much.

Real page numbers

"The addition of real page numbers, however, is probably the most important, and most exciting, new feature in version 3.1. Up until now Kindle readers have suffered with “locations” in their e-books instead of pages. This makes sense, since e-books don’t actually have pages, but it can cause some trouble in a classroom setting or when you’re trying to figure out how much more you have to read in order to finish a book (“I’ll go to bed in a couple hundred more locations,” doesn’t quite roll off the tongue).

So, Amazon has now mapped page numbers from the physical edition of a book to its e-book counterpart, and that information now shows up on your Kindle. Amazon also lists the ISBN of of the edition used for the pagination information on the Kindle item’s product details for two reasons: first, to let people know the e-book has “real page” information and so that readers know which edition those page numbers come from."

I have a kindle white. How do I enable this feature? I can't seem to find it in the settings menu.

Thanks!

JSWolf · 04-05-2016, 05:25 PM

Quote:

Originally Posted by Tex2002ans

The ADE automatic "page number" algorithm says each page 1024 compressed bytes and the Kindle goes by every 150 uncompressed bytes.

The problem I find with the Byte Methods is that the file may change (maybe more efficient/different code in the backend), but the text itself will not change.

That is 100% incorrect that the file may change. The file is as it is unless it's changed by you. When have you ever had an eBook change without you changing it either downloading a newer version or making the changes yourself? If the eBook changes without you doing it, then there is a major issue someplace that needs sorting.

View Poll Results: How important are page numbers in Kindle Books?
Very important - I tend to avoid those books and forget the author	16	8.56%
Nice to have - I use them if they are there	57	30.48%
Not important at all - get over yourself.	114	60.96%
Voters: 187. You may not vote on this poll

04-05-2016, 04:24 PM	#174
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	That sounds like a very needlessly complicated alternative to simply providing a Page-map or PageList. Which as has already been indicated, is not the perfect solution it sounds like. In fact, this whole discussion began with someone protesting that ebook publishers aren't using them^^ to curate page numbers -- so why would Yet Another Page Counting Method be any more likely to actually get used? Last edited by eschwartz; 04-05-2016 at 04:27 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Page numbers gone in AZW3 books	Katsunami	Calibre	1	09-03-2013 11:25 AM
Kindle (AZW3/MOBI) ebooks with "real page numbers" to PDF with same page numbers?	abvgd	Conversion	2	05-24-2013 01:24 PM
Adding Page Numbers to books on Kindle?	jimwoods	Calibre	1	02-17-2013 04:06 AM
Glo Page Numbers on Side-loaded books	Davidsc	Kobo Reader	8	02-09-2013 07:00 PM
page numbers in ALL kindle books?	oecherprinte	Amazon Kindle	8	09-30-2011 11:23 AM

04-05-2016, 08:05 AM	#167
John F Grand Sorcerer Posts: 7,945 Karma: 70880793 Join Date: Feb 2009 Device: Kobo Clara 2E	FWIW it's worth, my post with "one" was an attempted joke/jab at another discussion about the use of the word "one". Sorry for the obscure reference, I just assumed everyone reads every post and everyone would get the reference/joke/jab. I hope the OP doesn't mind the OT post. another reference to an obscure post/thread.

04-05-2016, 08:50 AM	#169
HarryT eBook Enthusiast Posts: 85,544 Karma: 93383099 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	That would indeed be helpful. Not everyone reads every thread on the board.

04-05-2016, 04:20 PM	#173
Solitaire1 Samurai Lizard Posts: 14,924 Karma: 69500000 Join Date: Nov 2009 Device: NookColor, Nook Glowlight 4	It seems that the issue with page numbers is that they can't be consistent, even on the same ebook on the same ereader, due to ebook formatting issues. Would a viable option be to include a marker (say a vertical bar on a line by itself) to indicate the top of a page, with everything between the bars considered one page regardless of the amount of text it contains (determined by the ebook formatting team)? This would allow the ebook formatter to clearly indicate where each "page" begins regardless of the way the ebook is formatted. The ebook's formatting options wouldn't matter since the relative position of the "page bar" would be unchanged within the ebook. It would even allow an option for the "page bar" to be hidden if desired by the reader (if hidden the page would be formatted as if the bar didn't exist).

Advert

Advert