Re: [docbook-apps] DocBook HTML and MHT Conversion Issues

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

Just to follow up on this, if you are using DocBook5, then the stripNS mode 
used to process a DB5 document with the current stylesheets also adds an 
absolute path xml:base to the root element of your document before 
processing it.  Actually, only Saxon currently does this because it 
requires a processor extension to fetch the uri of the document being 
processed.  When keep.relative.image.uris is set to zero (the default), 
then images are resolved relative to that xml:base.

If you process a DB5 document with the experimental stylesheets I posted 
information about yesterday, then the stripNS mode is not necessary because 
the document is processed with DB5-matching templates.  So absolute 
xml:base is added, and no absolute uris are generated, regardless of the 
keep.relative.image.uris parameter.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Bob Stayton" <bobs@sagehill.net>
To: "Chris Chiasson" <chris@chiasson.name>; "Mauritz Jeanson" 
<mj@johanneberg.com>
Cc: <docbook-apps@lists.oasis-open.org>; "Miller, Ray (Centech)" 
<Ray.Miller@va.gov>
Sent: Wednesday, October 04, 2006 1:42 PM
Subject: Re: [docbook-apps] DocBook HTML and MHT Conversion Issues


> Chris,
> It isn't always the case when you process a file with Saxon (and Xerces 
> and the Jakarta XML commons resolver) that it writes out full paths for 
> images. Can you provide more information?
> Is this with a DocBook 5 document?
> Have you tried setting  the parameter keep.relative.image.uris to 1 (zero 
> is the default)?
>
> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs@sagehill.net
>
>
> ----- Original Message ----- 
> From: "Chris Chiasson" <chris@chiasson.name>
> To: "Mauritz Jeanson" <mj@johanneberg.com>
> Cc: <docbook-apps@lists.oasis-open.org>; "Miller, Ray (Centech)" 
> <Ray.Miller@va.gov>
> Sent: Wednesday, October 04, 2006 11:59 AM
> Subject: Re: [docbook-apps] DocBook HTML and MHT Conversion Issues
>
>
>> When I process with Saxon (and Xerces and the Jakarta XML commons
>> resolver), it writes the full file:///absolute/path/ url to image
>> files into my html, xhtml, and fo output. This is not a big deal for
>> fo output, but messes up html and xhtml if they are served on a web
>> server. Furthermore, if the files are moved to another directory after
>> being created, the absolute references break (this happens as part of
>> my Ant build process, where the build directory is a different
>> directory from the destination).
>>
>> On 10/4/06, Mauritz Jeanson <mj@johanneberg.com> wrote:
>>> > -----Original Message-----
>>> > From: chris.chiasson@gmail.com
>>> >
>>> > this is happening because Saxon is writing full paths into
>>> > your html files
>>> > xsltproc won't do this
>>>
>>>
>>> What paths are you referring to? Image paths? I'm curious since I 
>>> haven't
>>> noticed any differences between Saxon and xsltproc. Can you please
>>> elaborate?
>>>
>>> /MJ
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> -- 
>> http://chris.chiasson.name/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>>
>>
>>
>