|
From: David G. <go...@us...> - 2002-08-02 19:54:48
|
[In private correspondence, I asked Adam to describe the process he's using to generate his website pages, each a collection of subdocuments.] This is important for the following reasons: - If you're using Docutils to process multiple source text documents, then you combine the resulting HTML, you must be stripping off the <html>, <head>, etc. parts. So it should be easy to also remove the <table class="docinfo"> too, and a "--no-docinfo" option isn't necessary. - If you're combining multiple text sources first and then using Docutils to process that all at once, there's a different issue. Only the first subdocument's bibliographic field list will be interpreted as "docinfo", so the others will have to be removed somehow (they're just ordinary field_list elements now), and a "--no-docinfo" option wouldn't work. Either way, it looks like you'll need a custom solution, probably a "Reader" that understands the context of your site (the process behind it), and definitely a custom front end. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |