View Single Post
Old 11-25-2007, 06:37 PM   #13
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 kovidgoyal View Post
The mobipocket reader software is designed to run in extremely CPU limited environments, which is why it does not do proper layouting and pagination.
The big problem is that they allow the user to change the font size in very small increments any time they wish on basically all the different platforms they support. Recalculating the number of pages every time the user changes the font size is a real problem. Most eBook readers precompute from a limited set of sizes. Sony has only 3 for example and takes a big hit the first time you select one that has not been used on that book before. Connect prepages all 3 sizes. Ebookwise prepages its 2 sizes. This is the real reason. MobiPocket devices are the same approximate power as eBook devices these days although that was not always the case.

Mobi tends to tack on changes to their software while they really need a full re-write.

Dale
DaleDe is offline   Reply With Quote