> I think it looks fine.
That's good, since I checked it in yesterday ;-)
> Your change made me think of the following problem: What if readers
> or writers want to throw warnings ("LaTeX writer doesn't support
> row-spans in tables") or errors ("Document does not begin with an
> RFC-2822 header; it is not a PEP")?
Not a problem. Some Writer-specific transforms already do that.
> Should these messages be handled through the Docutils' standard
> reporting system?
> Might this even be a use case for categories?
Not really. The purpose of categories was to allow for a dotted-name
hierarchy of configuration sets (report/halt threshold levels, debug
flag, and output stream). So for example, if you were debugging the
HTML writer's code, you could set the debug flag just for the
"writers.html4css1" category, and get only those debug messages, or
set the debug flag of "writers" in general, to get debug messages from
all writers. Categories were the equivalent of Python's "logging"
package's Filter objects.
However, configuration support for categories was never added,
therefore they were never used. In practice, categories were never
needed. A single set of reporter configuration settings suffices.
This was inspired by features of Java's log4j, as was Python's
"logging" package. I wonder if the logging package's Filters are ever
used by anyone though, or if that's unneeded functionality too.
> Should system_message nodes generated by reader or writer
> components be inserted into the document?
David Goodger <http://python.net/~goodger>