View Single Post
Old 05-20-2007, 02:37 AM   #11
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by kovidgoyal
Another important point is that LRF is not a good archival format. Like PDF it needs to know the screen geometry and DPI for best results. You really don't want to have to put in all that work you do in cleaning it up on the LRF.

HTML or some dedicated XML semantic format is much better for archival. The proofreading work should go in there, not at the LRF stage.
I completely agree with you. The other downside of LRF is that it's Sony Reader specific. I don't know what I'll be reading my eBooks on in 10 years time, but whatever it is it may not be able to read LRF. That's why I always store books in their original format.

Note that BD's "native" format is XML - whenever I work on a book I store that too. Having that, I can generate a wide range of different book formats from it.
HarryT is offline   Reply With Quote