docbook-apps

Hi!

I'm customizing the stylesheet for the title page of a book; everything
works fine except for an annoying
detail: it contains an external-graphics tag which does not take the
'img.src.path' variable into account.
I use the Maven jdocbook plugin which uses Xalan, FOP and Docbook XSLT
1.70.1.
I'm sure the img.src.path is set properly by the jdocbook plugin: it is used
by the imagedata tags I've put in
my document.

Does somebody have any idea of what is going on?

Thanks,
JM


------------------------------
<xsl:template name="book.titlepage.recto">
<fo:block>
<fo:table table-layout="fixed" width="175mm">
<fo:table-column column-width="175mm"/>
<fo:table-body>
<fo:table-row>
<fo:table-cell text-align="center">
<fo:block font-family="Helvetica"
font-weight="bold" font-size="32pt" padding-before="10mm">
<xsl:value-of select="bookinfo/title"/>
</fo:block>
<fo:block font-family="Helvetica"
font-size="22pt" padding-before="10mm">
<xsl:value-of select="bookinfo/subtitle"/>
</fo:block>
<fo:block font-family="Helvetica"
font-size="12pt" padding="10mm">
<xsl:value-of
select="bookinfo/releaseinfo"/>
</fo:block>
<fo:block>
<fo:external-graphic
src="target/staging/images/images/cover.tif"/>
</fo:block>
</fo:table-cell>
</fo:table-row>
<fo:table-row>
<fo:table-cell text-align="left">
<fo:block>
<fo:external-graphic
src="target/staging/images/images/ionic-logo.tif"/>
</fo:block>
</fo:table-cell>
</fo:table-row>
</fo:table-body>
</fo:table>
</fo:block>
</xsl:template>
------------------------------
--
View this message in context: http://www.nabble.com/img.src.path-not-taken-into-account-tf4346860.html#a12384169
Sent from the docbook apps mailing list archive at Nabble.com.

jmf! <jmf@ionicsoft.com>, 2007-08-29 03:05 -0700:

> I'm customizing the stylesheet for the title page of a book; everything
> works fine except for an annoying
> detail: it contains an external-graphics tag which does not take the
> 'img.src.path' variable into account.
> I use the Maven jdocbook plugin which uses Xalan, FOP and Docbook XSLT
> 1.70.1.

Version 1.70.1 was released over a year ago; the current version
is 1.73.1. If possible, please test with 1.73.1 and see if you can
reproduce this problem with that.

--Mike

Hi!

>> I'm customizing the stylesheet for the title page of a book; everything
>> works fine except for an annoying
>> detail: it contains an external-graphics tag which does not take the
>> 'img.src.path' variable into account.
>> I use the Maven jdocbook plugin which uses Xalan, FOP and Docbook XSLT
>> 1.70.1.
>>
> Version 1.70.1 was released over a year ago; the current version
> is 1.73.1. If possible, please test with 1.73.1 and see if you can
> reproduce this problem with that.
>
I've tested with 1.72.0 and 1.73.1, to no avail. I've also tried to
launch xalan by hand instead of relying to the jdocbook plugin: the
result is the same.

I can fix by changing the external-graphic tag and specifying to use
img.src.path manually, like this:
<fo:external-graphic src="{$img.src.path}/images/ionic-logo.tif"/>

Thanks!
JM

Jean-Marc François <jmf@ionicsoft.com>, 2007-08-29 23:11 +0200:

> I've tested with 1.72.0 and 1.73.1, to no avail. I've also tried to launch
> xalan by hand instead of relying to the jdocbook plugin: the result is the
> same.
>
> I can fix by changing the external-graphic tag and specifying to use
> img.src.path manually, like this:
> <fo:external-graphic src="{$img.src.path}/images/ionic-logo.tif"/>

There was recently another report on this list of problems with
img.src.path, so I hope we can get this figured out.

Can you provide a copy of your DocBook XML source document? Or
some other document/test case with which you can reproduce the
problem?

If possible, could you please create open a bug here:

http://docbook.sf.net/tracker/submit/bug

And then attach/upload your DocBook source there, as well as the
customization layer (if any) that you're using.

Or if your document or test case is short enough, you might prefer
to just post it here as an attachment to a message. Or feel free
to e-mail it to me directly if you want.

I've already tried unsuccessfully to reproduce this problem using
several test cases I have. Perhaps your source exposes a problem
that the test cases I've tried so far don't.

--Mike

--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/