Quote:
Originally Posted by llasram
That's not really a format issue so much as an "implementation" issue -- the font Sony bundled just has more glyphs than the one Adobe bundled. Is the @font-face rule with a 'res://' src insufficient for you, or would you like to see specific support for that? Will embedding a font in each book still be not an answer once Calibre has support for it and can just embed your default font selections automatically?
I can see how this might be an issue, as Adobe doesn't seem to cache any pagination information to help it jump into a flow more easily. I admit that I'm not sure what could be done here on Calibre's part.
Well then lets make EPUB more usable :-). I'd much much much rather put time into EPUB usability improvements than fixes to the all-but-dead LRF generator.
-Marshall
|
I have nothing against the *format*. The implementation on the Sony is buggy and, in my case, almost unusable. I cannot read non-fully-justified texts, because it messes with my ADD and draws my eyes to the space gaps on the right. It essentially halves my reading speed, and bothers me no end. It's slow, it crashes my sony about three times more than normal, and the books are bigger, on average, which means I can fit less on the device.
Concerning the Calibre conversion, it leaves out a number of the functions I require, as far as I can tell, like --force-page-break-before-tag (which is _not_ the same as a chapter) and setting fonts at the command line (--serif-family).
All of this essentially means that, as of now, and until Sony fixes some things, ePub cannot stand in for LRF for me, and I suspect a number of folks using Calibre, especially the thousands that don't have a 505 or up.