Lee>1. PG has no standards for submission of HTML (other than the obvious one that it must be valid HTML), and no one can code to a non-existent standard. The problem isn't that PG has no standards for HTML, the problem is that the WWers tell them to you after you have attempted to post to PG, and that those standards are different than given in the FAQ: http://www.gutenberg.org/wiki/Gutenberg:HTML_FAQ Lee>1. Develop a consensus HTML coding style for PG. Heck, it doesn't even need to be a consensus, a mandate from TPTB would serve just as well, but a consensus is more likely to be adopted. Just so long as PG follows the same set of rules for the PG tools which generate HTML, including the HTML that gets put into the generated "EPUB" and "MOBI" files. Lee>2. Build a small set of individuals who are familiar with PG's HTML coding style and could review HTML submissions. For example, I'm familiar enough with the use of HTML for encoding e-books that I'll bet I could judge whether a file is acceptable in less than 10 minutes. You could call this group of examiners "white washers" for lack of a better term. Set them first to take a good hard look at the "HTML" code being generated by the PG tool set, and have them fix that first. Secondly I would hope that the WWers wouldn't be accepting "HTML" based "on form," when that "HTML" produces books which are unreadable in practice. Lead by example.