Many thanks for your comments, I'll try to respond more fully in October.
Meanwhile, I'll respond on a couple of matters:
1. Regarding the math usage, I have part of a document, with the math
stuff, built with LyX and the rest with ReSt. I'm almost through
merging these now, but this is not an approach I would recommend. Since
doing this, I've come across TeXaide. this involves working through the
clipboard, but it is something I would explore for any other project.
2. In the FAQ, regarding extension usage, I see:
It's ".txt". Some people would like to use ".rest" or ".rst" or
".restx", but why bother? ReStructuredText source files are meant to be
readable as plaintext, and most operating systems already associate
".txt" with text files. Using a specialized filename extension would
require that users alter their OS settings, which is something that many
users will not be willing or able to do.
It seems to me, at least for Windows users, there is a benefit in using
a distinct extension in that with the Explorer one can click on the file
to execute docfactory. Clicking on a .txt file typically initiates
Notepad or, in my case SciTE.
David Goodger wrote:
> [Colin J. Williams]
> > I am slowly fighting my way through DocFactory, which is a great
> > tool as far as it goes.
> > 1. It would really help if there were an index to the various docs,
> > as with Python.chm
> Patches are welcome!
> > 2. Tables are a real problem.
> How so?
> > There is a CSV directive which might be helpful, but I haven't
> > yet sorted out how to specify line breaks, as with a chunk of
> > Python code.
> The CSV-table directive is meant for copy & paste (or file inclusion)
> from CSV sources. It's not really meant for original data entry.
> > 3. It would be nice if the editor incorporated ^W for window closing
> > and a re based Find and Replace, so that one can Find "^" to
> > replace with ".. ". To comment out code.
> You can comment out an entire block with a single ".." and
> Put the ".." on the first line by itself,
> then indent everything you'd like to
> comment out, like this paragraph.
> Blank lines and further indentation is
> OK too.
> > 5. It would help table building if there were a constructor
> > available on the screen with DocFactory like that available with
> > Netscape (Mozilla). The wxPython megagrid example appears be
> > more capable than is needed for table specifying and filling.
> Good idea. Again, patches are welcome.
> > 6. There is an ocasional need, which I have, to enter math
> > expresions - something like TexAide would help, but this outputs
> > LaTex, I don't know how that fits with the need to produce
> > HTML. [http://www.mathtype.com/en/]. It involves working through
> > the clipboard and then removing the superfluous stuff.
> Many people have asked for math markup, but as yet nobody has done the
> work necessary for a robust solution. As Felix pointed out, question
> 2.14 in the FAQ summarizes this issue: