Quote:
Originally Posted by kevin_boone
It occurs to me that another problem with large collections is that, although I have many thousands of documents I might want to read, only a handful are in formats that the PRS can read well. Most are in plain text or HTML. The PRS can't read HTML natively at all, I believe, and plain text is hit-and-miss. The PRS can't reflow a text document that has been formated with hard line-breaks, so reading them is often very ugly.
All this means is that I have to filter all my books before putting them on the PRS anyway. Generally I convert everything to LRF format, via HTML, including plain text, which I heuristically strip the line formatting from.
The ability to dump 4000 books on my PRS and to be sure of being able to read them is certainly something I'd welcome. But for this to work, in addition to improving the filesystem and the navigation, the PRS would have to be a whole lot better at reading things other than LRF and ePub.
Or so it seems to me.
|
What do you mean, plain txt is hit or miss? That's the format of choice for me. With rtf running a distant second. I do dump .html files to .txt mostly.
As for the hard line breaks, I do have scripts to deal with that, but I have found that the best way is to get .lits, explode them with clit, and then dump the .html to .txt. I preserve the formatting and it looks quite pleasant and readable to me.
I never convert to LRF, I think LRF looks ugly compared to plain txt, and I don't feel the need to convert my vast collection into a format that can't be read natively or easily by other devices.
Please believe me when I say that I have no problem navigating my collection. Anyone who says otherwise, I challenge them to say that they've done it and had a problem. Anything else is just fear mongering.