Quote:
Originally Posted by HarryT
Sorry, but both the Gen3 and the PC version have exactly the same page numbering bugs.
Try this:
Create a book from an HTML file and go to page "100" in it. Make a note of where that page starts. Now add a hyperlink to a point near the bottom of page "100".
Now, if you jump to that hyperlink the point which was previously near the bottom of the page will be right at the top, but the PC version of the Mobi reader will still tell you that you're looking at page 100. Which is the "real" page 100 - the one that you get to by paging through the book, or the one that you get to by jumping to that hyperlink? Different pages are being displayed, so they can't both be the same page, and yet Mobi reader will tell you that both are "page 100".
All versions of the Mobi reader do this. No Mobi device - free or otherwise - does real pagination. Page numbers are an estimates, whether they tell you this or not. This is obvious if you play around with hyperlinks in books.
That's the way that the Mobi readers have always worked. Page numbers are nothing more than estimates based on file position.
|
Ok. Mobipocket Reader was free. Cybook cost $350. I don't much mind page number bugs in free software. I do mind it in $350 devices.
Personally, I find it useless in it's present state; and the fact they have it leads one to believe it would be easy to add page numbers to the books since the numbers are already being calculated.
A specific page begins with a specific line and ends with a specific line. The fact that you can place a link somewhere in the middle of the page and put that part at the top doesn't change the concept that it's the middle of the page, and further down a new page begins. A link to a specific page number (as in go to page number feature) should go to the top of the page. The number of fixed pages can (theoretically) be calculated, it has nothing to do with the fact that portions of two pages can be displayed at one time. This has never confused me, I don't see the problem.