Quote:
Originally Posted by Benjamin Buford
I really can't see all the problems/complaints people are having with ADE page numbers... these synthetic page numbers are the only useful way of having page numbers at all with something as dynamic as a completely user-formattable ebook combined with a variety of ereader screen sizes. If page numbers would depend on ebook formatting, you could put away with page numbers as well. Page numbers are not some decoration, but a tool to find passages in a book, and ADE page numbers provide that, on every variety of ereader or e-reading app, and for every single ebook on this planet.
I like ADE page numbers! They are useful and practical. They are universal. They work, always.
|
I can't agree more. this is the only way if you want to give references to locations in a book to someone else reading either a paper edition or on a different reader (5/6/7/9/?" screen) or with different settings: margins, font, line spacing... Even a very faint difference in font rendering can change reader's pagination. I remember a case where line-cut position was different in a Windows application only depending on active anti-aliasing option alone (none, standard antialiasing or ClearType) because some characters were rendered with a pixel more or less.
Those that are irritated when page number don't match screen count don't need page number at all, bookmarks are enough for individual use, and screen number are useless for shared use.