Thanks for your answer, and your suggestion to use buildhtml.
However, buildhtml is meant for bulk processing.
My experience, at least with DocFactory, is of writing 1 document at a
time, and checking along wether it is clean and conform to the expected
When document is Ok, I transfer it to the web.With the conf as it is
designed now, I have to transfer a 1st time from the output directory to my
proper nested directory, and then to the web. This is making the redaction
process heavier, especially for non programmer-collaborators.
On Tue, Oct 05, 2004 at 09:53:48AM +0200, Pierre-Yves Delens wrote:
> I am working on a hierarchic set of documentation-help rst-html files.
> I would find easy and natural , for such a docFactory 'Project', to get
> html outputted file straight into the same folder as the original txt
> because my txt tree and my html tree are the same.
> However I would need to keep the conf file cnetralized of course, the same
> for the whole set.
> Did I mis this possibility of working in your tool as it is ?
> If NOT, isn't this a suggestion for a feature interesting for
> out there ?
What about docutils/tools/buildhtml.py? How close does it come to
doing what you need? See docutils/README.txt for instructions on
how to run it on the documentation that comes with the Docutils
distribution. And, I believe that the command line flage --config=
will enable you to specify your config file, if it is not in the