Joerg,
At 02:51 AM 4/3/2007, you wrote:
can it be just a problem of source resolving? PDF and JPG/PNG
serializers suffered from the lack of being able to resolve
relative paths for ages. This was only recently fixed in the FOP
NG block on trunk for PDF, but I don't know of any fix for Batik.
Marc, are you implying that if I use absolute URIs that'll work?
Worth a try, for sure. (And something I should have thought of. :-)
Absolute URIs should work without any problem.
Thanks, I'll definitely try that the next time I get my hands on it.
(Tonight, I hope.)
The actual problem with old FOP was the integration in Cocoon - or
more specific the injection of Cocoon's source resolver into FOP.
This was of particular interest when you wanted to include
dynamically generated images from another Cocoon pipeline.
If it is easier for Batik to inject Cocoon's source resolver or even
easier to just set the base URI - I have no idea and have never
tried to investigate it. Including other resources was more often a
need with FOP than with Batik.
Understood. (Does anyone have a clue of how to check on the issue in Batik?)
Cheers,
Wendell
======================================================================
Wendell Piez mailto:[EMAIL PROTECTED]
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
