--- Comment #3 from Matthias Reischenbacher <matthias8...@gmx.at> ---
I think I had a similar issue when upgrading my application to fop trunk. Not
setting the system id (in FOUserAgent.resolveURI) for the "data" scheme worked
around the issue. I was under the impression that the source of the problem was
batik and the recent changes in fop just uncovered that, but that might be
different in this case. If anyone wants to take a closer look, I can try to
provide an additional test cases.
You are receiving this mail because:
You are the assignee for the bug.