Thread: Oeps - UI error (page numbers again)
View Single Post
Old 07-02-2008, 07:11 AM   #10
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by JSWolf View Post
In Mobipocket's software, page numbers are BROKEN! So don't expect Bookeen to FIX it for you. It's an underlying bug based on the way Mobipocket doies think with 64k blocks. The only way to actually get working page numbers and a number of other bugs fixed is for Mobipocket to scrap their reading software and start over from the ground up which I don't think will ever happen. So as for page numbers, they'll never be fully working/bug free.
FBReader have working page numbers in mobi files if working means useful. They did that by not insisting on that paging forward once should update the page number with one.

The reason the page number works so strange is probably that they have used file position and that includes the markup. So if you have an html file with a lot of heading and other invisible markup in the beginning things will work very bad. This has nothing to do with 64K blocks.
tompe is offline   Reply With Quote