View Single Post
Old 09-21-2006, 12:57 PM   #17
vvv
Zealot
vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.vvv once ate a cherry pie in a record 7 seconds.
 
Posts: 137
Karma: 1936
Join Date: Aug 2006
Device: iLiad, Librie, REB1100, GEB2150, GEB1150, etc
Quote:
Originally Posted by scotty1024
I appreciate the Librie's ability to re-size fonts on the fly but you know? The pages breaks get all silly on you when you use that feature. Some times there is no substitute for using a proper tool to reflow the document when you change something manifest like the primary font size.
There is a fundamental error in Librie (lrf) format: the pages are defined as static objects instead of to be dynamic ones. Such an approach is ok for comics (it was the initial idea of lrf-format) but it is not suitable for e-books. So, if you want a nice-looking e-book, all the pages have to be pre-parsed for chosen font sizes (as it is done in BookDesigner Librie module, modes "simple" and "advanced"). But in this case you cannot change the Librie magnification because the formatting is static.
On the other side, an e-book can be made without pre-parsing. In this case the magnification option will work properly but the page breaks can occur at any place.
In general, all these lrf problems are due to the only reason: they tried to invent a pdf-like format. But because such a format type is not suitable for e-books, the above problems appear.

Last edited by vvv; 09-21-2006 at 01:04 PM.
vvv is offline   Reply With Quote