> We are now beginning to run into trouble with the established toolchain
> (particularly for print output), and there isn't much new development
> happening, so I'd like to start trying out XML-based toolchains. To do
> that, we need to move to a DocBook version that is available as both SGML
> (processed by OpenJade) and XML, which is the case for 4.x. We can
> convert SGML to XML automatically, so there are no syntax implications.
I've had good luck processing XML through both toolchains, and would
find it VERY useful if there was the ability to quickly pull in
PostgreSQL content into other in-house documents via an XMLInclude
rather than a hacked checkout, file munge, etc.
I vote for having valid XML in the system itself with each file having a
valid DTD specification.
This has the added benefit of allowing an XSL transform to function on a
single document fairly easily which enables people such as Josh who
don't normally write documentation to quickly validate their changes
with nothing but a webbrowser, a very short set of instructions, and the
URL to the docbook XSLs.
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.asc