A catalog is applied when a file is actually being opened. In the case of
images, the image file is not opened by the XSL stylesheet, so the catalog
does not come into play during that stage. The XSLT process just copies the
URL string out to the FO file. It is the FO processor that then opens the
graphics file, so the catalog machinery needs to be set up on the FO
processor for that to work.
Example 18.2 in this section of my book shows how to add it to XEP (in this
example, for resolving SVG DTDs):
http://www.sagehill.net/docbookxsl/SVGimages.html#SvgDtd
I don't know how to do it with FOP.
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
----- Original Message -----
From: "mjatromp" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, May 10, 2008 11:27 AM
Subject: [docbook-apps] draft.watermark.image and catalog.xml
Hi,
I have set up catalog.xml and resolver to point to a local docbook-ns-xsl
install. This works perfect except for the image references like
draft.watermark.image: they still point to
http://docbook.sourceforge.net/release/images/.
What is the proper way to make references in params resolve?
Marcel
--
--
View this message in context:
http://www.nabble.com/draft.watermark.image-and-catalog.xml-tp17166155p17166155.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]
