Which XSL-FO processor are you using? I'm guessing those error messages are coming
from the XSL-FO processor and not the XSL stylesheet.
Setting draft.mode to anything but 'no' causes the stylesheet to load into the XSL-FO
file the extra page-masters that are needed for displaying the draft watermark image
in the background. If there are no draft instances, those page-masters are never
used, so there should not be such an error reported. I believe it was FOP that
checked for the existence of the image when the XSL-FO file is parsed, not when the
image is used. I consider that to be a bug in the XSL-FO processor, not the
stylesheet. Other processors don't report it.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "mike 675" <[email protected]>
To: <[email protected]>
Sent: Tuesday, September 20, 2011 8:04 AM
Subject: [docbook-apps] Draft mode: Missing image error affects all PDF builds
Using the watermark feature for draft docs:
My book has a status="draft" attribute.
In my PDF customization layer I enter the following parameters:
<xsl:param name="draft.mode">maybe</xsl:param>
<xsl:param name="draft.watermark.image">../images/draft.png</xsl:param>
Problem: Error messages about missing draft.png are now generated when I
export *any* book to PDF, regardless of whether a status attribute is set on
the book.
This is obviously caused by the graphic not being available in a common
folder accessible to all.
But I think this is a bug. The errors should not be generated if draft mode
has not been turned on in the source XML, by using status="draft".
--
View this message in context:
http://old.nabble.com/Draft-mode%3A-Missing-image-error-affects-all-PDF-builds-tp32501074p32501074.html
Sent from the docbook apps mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
