On 1/19/2012 5:06 PM, Jim Adcock wrote:
You can submit either *one* HTML or *one* TEI or *one* RST file. In no case has anybody been posting multiple HTML files.
Heck, you could probably even post *one* z.m.l. file, just so long as it has a .txt extension ;-). If you did, you couldn't also post an impoverished text file, but in that case there wouldn't be any need would there?
Well we are getting down to Clinton-esc Parsing, but in that case allow me to post *one* HTML which includes CPP conditional processing statements (or the equivalent) such that it is "allowed" to magically split into three Hydra Heads and generate separate targeted "Big HTML", EPUB, and MOBI versions just like RST is allowed to do.
This horse doesn't yet seem to be dead, so... The three basic rules for making ePub-ready HTML files: 1. Don't specify styles inside the HTML document, either inline or in the <head>. Do include a link to an external style sheet with the name "pg.css". 2. Use HTML elements only as designed; no tag abuse. 3. Use a standardized set of classification attributes ("class='standard'"). Help contribute to building a standard library of attribute values. Be willing to compromise in the naming of the attributes; standardization is more important than "correctness". If you were to follow these rules you would have exactly what you are asking for: a single HTML file that would satisfy all three purposes. The conditional processing system would be implemented by the application of various external style sheets. ePub and the two Kindle formats could simply be generated using two (or three if .kf8 needs it) different style sheet files. You could even distinguish between "21 inch monitor" HTML files and "3.7 inch monitor" HTML files by serving different style sheets according to the user's preferences. For example, it would be a simple thing to do to serve "little screen" HTML files from "m.gutenberg.org" and "big screen" HTML files from "www.gutenberg.org".