OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] draft.watermark.image and catalog.xml


Richard Hamilton wrote:
> Marcel,
> I'm using fop 0.94, and as far as I can tell it doesn't support
> catalogs.  At least, I can't get it to support catalogs, and I can't
> find any documentation that describes how to set it up for catalogs.

The documentation about embedding FOP [1] gives indication on how to
override the default URI resolver to use one based on catalogs, for
instance. This requires a little bit of Java skills since you have to
call FOP programmatically. I’m not sure this is possible to override the
URI resolver by just using the command line.
I’ve never experimented with that myself, so you will get better help on
the fop-users mailing list [2]. Anyway this is becoming very
FOP-specific now :)

[1] http://xmlgraphics.apache.org/fop/0.94/embedding.html#fop-factory
[2] http://xmlgraphics.apache.org/fop/maillist.html#fop-user


> However, fop does go out to the URL to grab the graphic, if you don't
> mind the extra delay.
> The other choice would be to set the draft.watermark.image parameter in
> your customization to the local path of the file.
> Neither solution is ideal, but both work.
> Dick Hamilton
> http://rlhamilton.net
> On Sun, 2008-05-11 at 23:26 -0700, mjatromp wrote:
>> Bob, thanks for the quick reply. Unfortunately I am using FOP at this point.
>> Can anyone tell me what the best way is using FOP? Is there a commandline
>> based way or should I use FOP factory?
>> Marcel
>> --
>> Bob Stayton wrote:
>>> 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
>>> bobs@sagehill.net
>>> ----- Original Message -----
>>> From: "mjatromp" <marcel_nabble@tromp.org>
>>> To: <docbook-apps@lists.oasis-open.org>
>>> 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.

Vincent Hennebert                            Anyware Technologies
http://people.apache.org/~vhennebert         http://www.anyware-tech.com
Apache FOP Committer                         FOP Development/Consulting

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]