Re: [docbook-apps] XInclude and Graphics

["Bob Stayton" <bobs@sagehill.net>]

This is a Xerces issue.  The resolver.jar is used for catalog entries, so it
does not process XIncludes. The XInclude processor has to keep track of the
current xml:base and add new xml:base attributes as it imports text.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Georges Schmitz" <georges.schmitz@heitec.de>
To: "Bob Stayton" <bobs@sagehill.net>; "docbook-apps"
<docbook-apps@lists.oasis-open.org>
Sent: Thursday, June 23, 2005 1:28 AM
Subject: Re: [docbook-apps] XInclude and Graphics


> Hi Bob,
>
> thanks a lot for you filing the bug on libxml2. I'm glad you are
> handling this for me.
>
> Concerning Xalan, does this behavior depend on Xerces directly or on
> resolver.jar? If I'm not completely wrong, resolver.jar was initiated by
> Norman Walsh?
>
> Thanks,
> Georges
>
> Bob Stayton wrote:
>
> >Hi George,
> >There is no question that the xml:base attribute that xmllint puts on the
> ><section> element is wrong.  A nested relative xml:base attribute is
always
> >relative to the container element's xml:base.  In the xmllint output, it
> >should be just:
> >
> ><section xml:base="s-central-open-invoices.xml">
> >
> >And by using xsl:message statements in a section template, I confirmed
that
> >the Xerces parser with XInclude is getting it wrong as well.  I think
your
> >tests confirm that when the xml:base attribute is correct, then the
> >stylesheet does the right thing.  It is impossible for the stylesheet to
> >compensate for incorrectly generated xml:base values.
> >
> >I also find it hard to believe that both parsers are inserting the same
> >xml:base value, but the evidence is pretty plain.  I'm going to file a
bug
> >report on libxml2 to see if this can get fixed.
> >
> >Bob Stayton
> >
> >
>
>
>