Quote:
Originally Posted by Tuna
I thought it's been established that LaTeX is not suitable for e-readers because of the large installation size and relatively heavy processor demands? Did I also read that it requires full parsing of the entire document to do 'jump to' navigation? The other component missing seems to be editors tools - most of the ones I've seen are closer to programming environments than DTP tools.
Annoyingly my '505 has just run out of juice, but I'm fairly certain that the PDF books I've read on it have not been rendered faithfully, with odd effects as you zoom and rotate them. Simple issues like border removal suggest that PDF is not a 'solved problem' when it comes to display on relatively low resolution and size screens. Which really is the whole point of this discussion.
|
1) I thought the opposite was the case in the discussion above.
2) The full
two-pass parsing is not a deficiency of the program, but an arguable necessity of the task... though there could be other ways (look for the destination anchor only when the user "clicks" the link--however that would mean it would take twice as long to go to a page a chapter later in the book, than one two chapters later... and for large books, particular those with thousands of pages, this could get ugly fast).
3) There is no genuine need (or, I personally think) reason to use LaTeX (or anything like it) directly on eBook readers. Use a format that allows both reflow (i.e.: ePub [HTML]) and fixed formats (i.e.: PDF) in a single file, with some intelligent autodetection as to which the user might best best off with, but ultimately permitting manual override/selection as to which to view.
PDF rendering issues on the Sony PRS-505 sound bizarre to me. I've never encountered anything as such to date, and I basically only read PDFs... many generated by me in occasionally unorthodox ways.
Let me know more about this when your batteries are charged, I guess.
- Ahi