Thanks Thomas, Yes, I've tried jing too and it worked, although I am a little bit concerned that it didn't have any development activity since, I believe, 2008. And, being a Java tool, it was considerably slower than xmllint - I wanted to avoid adding another Java tool in our toolchain unless absolutely necessary.
But RNG validation was not the only issue we've faced with DB5 and libxml2: we also actively use entities, and libxml2 currently loses namespace declarations when it goes from parsing the "main" document into parsing an entity. This would have required updating all our entities to declare namespaces on each and every element inside an entity... I've decided to give a shot at fixing libxml2, but haven't found the time to do so yet. Regards, Alexey. On Thursday, September 12, 2013 09:55:19 AM Thomas Schraitle wrote: > Hi Alexey, > > On Mon, 9 Sep 2013 10:47:42 -0700 > > Alexey Neyman <[email protected]> wrote: > > Yes, we are using DocBook 4 at this time; we've tried to move to DB5 > > but decided against it for now - primarily because of libxslt's > > issues with RelaxNG validation and namespace handling issues. > > You mean probably libxml2/xmllint (the XML parser) which have > issues, not libxslt/xsltproc (the XSLT processor). :) > > I know some problems with xmllint's RNG validation -- it never worked > for me. For this reason, I use Jing which gives you far better > validation results. Try Jing instead of xmllint. :)
