On 6/24/07, Hartmut Holzgraefe <[EMAIL PROTECTED]> wrote:
Hannes Magnusson wrote:
> Hi all
>
> I've upgraded all our translations, and english, to Docbook5.
>
> We are hitting few bugs here and there both in libxml2 (xmllint) and
> Docbook itself regarding validation of our files so there are few
> bogus warnings. Some of these warnings are however correct and I am
> working on fixing them but would appreciate any help I can get.
>
> There are two new test targets, test_xsd and test_rng, the recommended
> test target by Docbook is test_rng - but xmllint doesnt like the rng
> so much so we recommend test_xsd as it seems to have the lowest bug
> count :)
>
> So, the freeze is now officially over \o/

given the amount of problems that i see right now wouldn't it
have been a better idea to commit this into a separate branch
first to test to iron out the problems and only then merge it
to head?

It would had and that is what I wanted. It was discussed briefly on
IRC but conclusion was not to.
I've been fixing the remaining issues all day long and am almost finished now.


Right now all of the test targets return different error information
to me, the test_xsd target producing the shortest list but at
the same time the most useless one (file:line info against .manual.xml
instead of the original source file) and especially the default
target for a simple "make" completely fails.

The short version: entities do not inherit their parents namespaces,
therefor we need to "build the manual twice", i.e. first generate
.manual.xml and then validate it.

The DTD has the same bug as the XSD had (which Gwynne already fixed),
the RNG warnings are bogus and are caused by a bug in xmllint.
I recommend you use the test_xsd target.

The default make target, html, uses the DSSSL voodoo.
I am planning on switching to XSL build soonish, unless you could have
a look at the DSSSLs?


And that is only for the en tree, i haven't even started to
look into the de tree failures ...

Gwynne is looking into the internal docs and trying to fix those
errors, if you build --without-internals everything is fine.


-Hannes

Reply via email to