|
From: David G. <go...@py...> - 2002-12-20 01:50:59
|
David Abrahams wrote:
> As a mostly-outsider, my only comment is that the plethora of very
> similar-sounding tools is confusing. Is there anything to the idea
> of unifying html.py, pep2html.py, pep.py, and maybe even builhtml.py
> with some kind of command-line option to select behaviors?
A CVS-style command with subcommands could be constructed. For
example::
docutils html input.txt output.html
docutils latex ...
It gets tricky when you want to specify the input format and/or
context as well. One way is to use options::
docutils html --reader pep ...
Then the order of options becomes important. You have to specify
"--reader xyz" before you can specify an xyz-reader-specific option.
See <http://docutils.sf.net/spec/notes.html#front-end-tools> for more
thoughts on "partially qualified" and "unqualified" front ends.
--
David Goodger <go...@py...> 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/
|