CR/LF
And I'll bet that zooming on the device may appear to sort-of help in some cases, but there is still word spacing funkiness.
I find that the Reader does not like DOS-style CR/LF end-of-line markers in text files and renders TXT files in the way you have described. I have tested this using both TXT files written directly to an SD as well as loaded via the Connect software's import feature. You can test by stripping out the CR/LF EOL sequences with a text editor and reloading them onto the Reader.
Perhaps this is due to the Windows-only Connect application and the Linux-based Reader. Whatever the cause, it is irritating.
UPDATE:
So much for my previous CR/LF comments.
As it happens all of my TXT and RTF jaggy line formatting issues are due to hard returns. Some of my RTFs had hard returns after each 'sentence' element, some didn't. Those without render nicely on the Reader. No surprise. Same thing with TXT.
At least for myself, hard-return culling (similar to that used in the macros described earlier in the thread) works like a charm.
Last edited by jm ervin; 10-27-2006 at 03:08 AM.
|