View Single Post
Old 05-14-2008, 02:01 PM   #59
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by TallMomof2 View Post
Plus page numbers are irrelevant because if you change font size, bold the font or even change the font, the page numbering changes. Until Mobi fixes the page numbering bug, a progress bar is the only thing that is close to accurate.
I think calling it a bug is a bit of a misnomer but it can be viewed as an important feature. You are correct in that it is a difficult problem. This is why Kindle uses a reference number that is actually and arbitrary 128 characters for access. It does not matter what font changes or sizes are made the number of characters is constant.

The real bug in Mobi is trying to show page numbers at all since they are impossible for them to maintain accurately as the engine is now written. The cybook does not display the numbers while some other mobi implementations attempt to display the page numbers but then goes awry when you do jumps.

Microsoft Reader really is the only one that supports user loadable fonts and then does page numbers and it is done as a background task and can take a significant amount of time to get the numbers into the pages. It is not remembered so you spend the time again and again if you resize or otherwise change the document page size.

Sony does it ahead of time and only supports 3 sizes and a fixed font type. If you bypass the computer rendering you will pay the price of waiting until it finishes the rendering the first time you open the book and again if you change the font size.

eBookwise precomputes the sizes when the file is built.

PDF uses a similar strategy of precomputing when the book is built and will be off if you change form portrait to landscape or at least it doesn't math the viewing screen at all.

Dale
DaleDe is offline   Reply With Quote