Hi Guys, I am really getting a gas out of this thread. Well, I decided to do some research and look into the HowTos and FAQs. I do now understand the complaint about ambiguity. It is there the pages of the PG site. Actually, even contradictory all on the same page. Source: http://www.gutenberg.org/wiki/Gutenberg:HTML_FAQ 1) H.3. Can I submit a HTML version without a plain ASCII version? You can submit it, but the Posting Team will then consider whether we should also make an ASCII, or perhaps ISO-8859 or Unicode version of it. We really do want our texts to be viewable by everybody, under every circumstances, and we do not want to start posting texts that are in any way inaccessible to anyone. See also the FAQ [G.17] "Why is PG so set on using Plain Vanilla ASCII?" Yet, 2) [H.4.]5. Requirement: HTML and plain-text Project Gutenberg does publish well-formatted, standards compliant HTML. However, we insist that a plain text version be available for all HTML documents we publish (even if images or formatting are absent), except when ASCII can't reasonably be used at all, for example with Arabic, or mathematical texts. So the answer should be generally NO! I have found other such confusing correlations. Furthermore, from the statements here there seem to be policies in place which are not mentioned. AFAIK: TEI is not mentioned. Yes, It is not in the FAQs or HowTos. So the FAQs and HowTos must be updated to mirror the commonly used policies and practices, and be more consistent. I have one question though. What if one has went through the work of producing a ePub, mobi, HTML and text files that conform to PG requirements, can they be submitted to PG? The reason I ask is that, as can be seen for the posts on this list production is moving more to the production directly of mobi and epub formats. These formats more or less contain HTML already. If they follow the guidelines for good ebooks. The HTML should fit PG requirments for HTML. With the above said all PG now needs is a conversion tool to create a plain text version. regards Keith.