|
From: David G. <go...@us...> - 2002-08-02 03:14:58
|
Adam Chodorowski wrote: > That will not work, since the point is that I want the bibliographic > fields not display only for *some* output formats. The output files > that are intended to be standalone (for example PDF or simple HTML) > should contain the fields, but the files intended for tight > integration into a website should not. > > So the bibliographic information needs to be there in the input; I > just want to disable it in some (one, actually) of the output > formats. It definitely sounds like a custom solution or a templating system is called for. I'd much rather see the beginnings of a new, comprehensive templating system than start down the path of adding questionable features to html4css1.py. In any case, if that one option *is* all you really need, you can easily derive a new writer from html4css1.py (that's what pep_html.py does). > I'm also tinkering with the idea to write plaintext (no, this > isn't as silly as it would seem ;-)) and AmigaGuide writers. Not silly at all. Plaintext would be welcome; a *reStructuredText* writer would be *very* welcome indeed! -- 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/ |