Quote:
Originally Posted by kovidgoyal
In order to paginate a reflowable format like HTML or LRF, what's needed is that the reader software has to essentially render the whole book in one pass and save layout information (basically how many lines fit on a page at the current base font size).
The more complex the markup the longer it takes to do this. Without CSS HTML is actually simpler than LRF, so I'm not surprised that FBReader manages to paginate quickly.
Does the eb1150 software pre-paginate when transferring to the device? SONY's connect software does that and so you wont notice any slowdown if you use it, but if you transfer books directly, using a SD card for example, you see the slowdown.
|
The eb1150 pre-paginates both choices when the document is created. Sony does this as well when you use connect to get your book but the other tools do not do this for Sony thus the hit the first time you change font sizes. A similar problem exists in Digital Editions but even worse since the pagination isn't saved to you take the hit every time you change font sizes. This can be a significant problem as you point out and I think that the epub standard ignores it.
Dale