Please compile your docbooklint suggestions on this thread, and I'll
submit one list of suggestions to Dave.
On Fri, 2006-11-10 at 16:26 -0500, David Malcolm wrote:
[apologies for broad cross-posting]
I wanted to do a bit of checking of DocBook XML files beyond just DTD
validation, and couldn't find a tool to so this (is there one?), so I've
hacked one together (GPL license, python implementation)
In the spirit of "release early, release often", the code is in public
and the mailing list for the project is:
archives and subscription info)
So far all it does is verify that text inside a <computeroutput> element
has been properly line-wrapped , but the framework is hopefully clean
enough to be expanded to cover other checks people might want to
implement that aren't so easy to do with DTDs, for instance:
- enforcing naming policies for node ids
etc - any other ideas? Patches welcome.
Hopefully this will be of use to various projects with DocBook
 I ran into some problems where line-endings of screen dumps in my
DocBook files got garbled, and verbatim monospace rendering was looking
terrible: the tool detects this now.
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
| gpg key: AD0E0C41