Quote:
Originally Posted by frabjous
Why not? Something has to do the rendering, and so long as we're talking an e-Ink screen, where you don't scroll, but view a page at a time, and switch displays a page at a time, the rendering is done in pages. Why not just upload .tex source, have the rendering engine on the machine itself--TeX is not that resource-intensive as all that
|
It's still an order of magnitude more intensive than, for example, the ePub rendering engine Abobe use, however. It's not optimised for low-power devices, as a format. (And yes, that's important...even ePub is more expensive to render than LRX's)
More, again, it has little to do with ebooks. As you yourself note, it output's PDF's, and solves precisely the same problems PDF's do, and PDF's are a format for
books, not for
reading. Using a PDF and not having to expensively render the page layout as well as the text itself in the first place by using a PDF makes a lot more sense, if you demand fixed page layouts.
If I can't change the font size and have the page reflow on the fly, quickly; I don't want to mess arround with it, spending an hour+ easily per-book when perfect formatting isn't that important to me.