RTF vs HTML---best way to convert my files?
I have been using HTML for my converted secure eReader files and this has lately been problematic. The HTML is very messy and has required numerous conversions---what was fine on the Sony was not fine on the Kindle, which was not fine on the Libre etc. etc. etc. I just want one basic file I can re-convert to any future format and read on all devices now. Presently, I want to convert to mobi and have an error-free file.
After going through a dozen HTML files, I found issues with line breaks, straight vs curly quotes and numerous inconsistencies. It seems I think all is fixed and then I find some other error. I am running it through Kompozer, copy and pasting the result from Firefox into a clean file, and I guess I just don't know enough about which problems to catch. I am wondering if it might be better to just copy the HTML into an RTF file and convert THAT in the future?
So what should I do? Copy and paste from firefox into Word and make them all RTF files, or develop some sort of HTML checklist I can use to verify---once and for all---the perfection of my files and then make HTML my archival format? I no longer buy secure eReader but I have about 200 files already and just don't have the heart to keep going through them all again every time I want to use a different reader (I review for Teleread and often test new ones). I just want one base file which is fine that I can re-convert forever and ever.
|