View Single Post
Old 04-24-2010, 05:00 AM   #3
pepak
Guru
pepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura aboutpepak has a spectacular aura about
 
Posts: 610
Karma: 4150
Join Date: Mar 2008
Device: Sony Reader PRS-T3, Kobo Libra H2O
Quote:
Originally Posted by ficbot View Post
I am wondering if it might be better to just copy the HTML into an RTF file and convert THAT in the future?
Certainly not. RTF is, if anything, even worse to get into a "clean state" than HTML. What I would recommend is to stick to XHTML (because the extra limitations over basic HTML allow for easier automatic conversions), and with a very limited version of it - the fewer tags you use, the less likely you are to encounter problems. If you want an inspiration, download this:
http://www.pepak.net/files/e-books/u...ble_people.zip
It produces a file which is reasonably simple to convert to any format I tried.

Quote:
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 would recommend HTML. Unfortunately, you will need to descend to the roots and do all coding yourself - if you use some graphical editors, the result will likely be poor.

Quote:
I just want one base file which is fine that I can re-convert forever and ever.
HTML+CSS is a good solution, as is, with certain limitations, XML+XSLT. You may also want to look at my H2LRF, which I use for precisely the task you want - one source format which I can easily (read: changing one parameter of the command, or changing one source file for all books) convert to any format.
pepak is offline   Reply With Quote