cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Schwarz" <>
Subject Re: FOP with embeded SVG doesn't render at correct size in Cocoon
Date Fri, 05 Mar 2004 02:38:11 GMT
Here's an example xml that produces the problems (svg:use url failure for 
FOP versions of fop/batik jars and scaling problem for Cocoon versions of 
fop/batik jars):

if you call it bar.xml:

<?xml version="1.0" encoding="UTF-8"?>
<fo:root xmlns:svg="" 
<fo:simple-page-master margin-right="0.5in" margin-left="0.5in" 
margin-bottom="0.5in" margin-top="0.5in" page-width="8.5in" 
page-height="11.5in" master-name="all">
<fo:region-body margin-bottom="0.25in" margin-top="0.25in"/>
<fo:region-before extent="0.25in"/>
<fo:page-sequence master-reference="all">
<fo:flow flow-name="xsl-region-body">
<fo:block text-align="center">
<fo:instream-foreign-object text-align="center">
<svg:svg xmlns:xlink="" width="6in" height="6in" 
viewBox="0 0 1400 1400">
  <svg:g style="stroke:green;fill:green" id="greenRect"><svg:rect x="0" 
y="0" width="100" height="100"/></svg:g>
  <svg:g id="yellowGreenRect">
    <svg:rect x="0" y="0" width="200" height="200" 
      <svg:use transform="translate(400,400)" xlink:href="#greenRect"/>
<svg:rect x="0" y="0" width="1600" height="1600" 
<svg:use xlink:href="#yellowGreenRect"/>

<map:match pattern="bar.pdf">
      <map:generate src="bar.xml"/>
      <map:serialize type="fo2pdf" />


>On 03.03.2004 22:20, J.Pietschmann wrote:
>>Joerg Heinicke wrote:
>>>It's the 0.20.5 release, but built with our Batik 1.5. I guess the FOP 
>>>people must clarify if this made any sense or not. IIRC we had the 
>>>released Fop jar in our CVS and got complaints for problems with Batik 
>>>after Batik update. So we rebuilt Fop with this new Batik and the 
>>>problems seemed to be gone.
>>Odd. If it compiles, it shouldn't complain about missing methods
>>at run time. There may be behaviour changes though, has someone
>>checked the Batik change log?
>I guess no, at least I didn't it. But our CVS contains a sample with an 
>image and this works for me after my recent commit for the image path that 
>was wrong: Probably it 
>happens only for embedded SVG?
>I searched for some more messages on this issue, but they always end at the 
>same place:
>Batik has changed an interface and broke the dependency of FOP on it. The 
>Cocoon dev thread ended with the question of downgrading. But as you said: 
>"If it compiles, it shouldn't complain about missing methods at run time."

Learn how to help protect your privacy and prevent fraud online at Tech 
Hacks & Scams.

View raw message