Re: [docbook-apps] XIncludes with relative paths (libxml + WinXP).

[Georges Schmitz <georges.schmitz@heitec.de>]

Hi Bob,

thank you for the hint, you made me "rethink" the command, it was actually:

    xmllint.exe --noent --valid  --recover  --xinclude -o resolved.xml 
"file:///D:/BAZL/doc/de/ml/ml-main.xml"

[I used an absolute uri path for the input file, this was because of me 
playing around with catalog files some months ago and there were 
constellations where resolver.jar wouldn't work with saxon in my 
intended way, if the absolute path was not used (don't remember anymore 
what exactly went wrong at that time).]

But - ahaaa - reading your message, I said to myself: 'there was a time, 
that XIncludes used to work in libxml ..., what was different then?': 
the input path!

with the following command, resolving works fine:
    xmllint.exe --noent --valid  --recover  --xinclude -o resolved.xml 
ml-main.xml

Nevertheless, should the behavior of libxml with absolute input paths 
not be considered a bug? Or does the interpretation of base paths 
change, when an absolute path is provided instead of a simple file 
(using the current path)?

Regards,
Georges

Bob Stayton wrote:

>Hi George,
>I'm not able to duplicate your problem with relative XIncludes in xmllint
>20619.  Can you provide more details of the command you are using and the
>directory setup?
>
>Bob Stayton
>
>  
>

>----- Original Message ----- 
>From: "Georges Schmitz" <georges.schmitz@heitec.de>
>To: "docbook-apps" <docbook-apps@lists.oasis-open.org>
>Sent: Wednesday, June 15, 2005 7:11 AM
>Subject: [docbook-apps] XIncludes with relative paths (libxml + WinXP).
>
>
>  
>
>>Using libxml 20619 und WinXP, I have a problem when it comes to
>>resolve XIncludes with relative paths. The absolute path, that libxml
>>is building internally seems not to fit libxml's own needs (uri
>>convention), because the file prefix is only written with 1 "/"
>>instead of 3.
>>
>>My main file is stored in "D:\BAZL\doc\de\ml", the chapter
>>"ch-metadata.xml" is also stored at this place, so the following
>>xinclude instruction should work:
>>
>> >>>>>>>>>>>>>
>>    <book><title>Title</title>
>>
>>    ...
>>      <xi:include xmlns:xi="http://www.w3.org/2003/XInclude";
>>                  href="ch-metadata.xml"
>>                  parse="xml">
>>        <xi:fallback>
>>          <para><emphasis role="bold">FIXME:  missing xinclude content
>>          (metadata)</emphasis></para>
>>        </xi:fallback>
>>      </xi:include>
>>
>>    ...
>><<<<<<<<<<<<<
>>
>>Validating the document with xmllint shows the error message:
>>
>>    I/O error : failed to load external entity
>>"file%3A/D%3A/BAZL/doc/de/ml/ch-metadata.xml"
>>
>>    
>>