xinclude, difference html vs pdf output. docbook-v5

[Dave Pawson <davep@dpawson.co.uk>]

source file layout

x from which ant is used to build the files
x/part1/
     file1
     file2
x/part2
     file1
     file2  etc

images are referred to using
<imagedata xml:id="fig08-1" fileref="images/fig8-1.png" format="PNG"/>
I.e. relative to x/part1 etc

All chapters are included using xInclude
Hence after expansion I see xml:id="hiview"
xml:base="part1/file1.xml">

In the custom layer for html and fo I have
<xsl:param name="img.src.path" select="'/styles/xslfo/'"/>
So I expect all images to be referred to relative to that directory?


1. When processed through to HTML the html reads
<img src="/styles/xslfo/images/fig8-7.png"
Exactly as I expect

2. Notes read 
<img alt="[Note]" src="/styles/docbook/images/note.png">

For the PDF I see
<fo:external-graphic width="auto" height="auto" content-width="36pt"
src="url(/styles/docbook/images/warning.png)"/>
which is fine
But...
<fo:external-graphic src="url(/styles/xslfo/part1/images/fig12-2.png)"

So there is a difference, HTML to PDF.
The pdf output is using the path consisting of the img.src.path + the
prefix of the xml:base + the relative path of the graphic.

/styles/xslfo/   param
part1/             from xml:base????
images/fig12-2.png  from the source XML


I don't mind either way, but it would be nice to be consistent?
I.e. use xml:base for html and pdf, or ignore it...
I will have to go through an intermediate step of stripping out
the base if it is processed




-- 

regards 

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk