Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 77627 invoked from network); 5 Mar 2004 02:38:23 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 02:38:23 -0000 Received: (qmail 81905 invoked by uid 500); 5 Mar 2004 02:38:03 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 81858 invoked by uid 500); 5 Mar 2004 02:38:03 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 81843 invoked from network); 5 Mar 2004 02:38:02 -0000 Received: from unknown (HELO hotmail.com) (64.4.17.60) by daedalus.apache.org with SMTP; 5 Mar 2004 02:38:02 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 4 Mar 2004 18:38:11 -0800 Received: from 66.58.21.90 by lw11fd.law11.hotmail.msn.com with HTTP; Fri, 05 Mar 2004 02:38:11 GMT X-Originating-IP: [66.58.21.90] X-Originating-Email: [saschwarz@hotmail.com] X-Sender: saschwarz@hotmail.com From: "Steve Schwarz" To: dev@cocoon.apache.org Bcc: Subject: Re: FOP with embeded SVG doesn't render at correct size in Cocoon Date: Fri, 05 Mar 2004 02:38:11 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 05 Mar 2004 02:38:11.0952 (UTC) FILETIME=[E706EF00:01C4025A] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Joerg, 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: sitemap: Thanks, Steve > >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: http://127.0.0.1:8888/samples/fop/misc/minimal.pdf. Probably it >happens only for embedded SVG? > >I searched for some more messages on this issue, but they always end at the >same place: >http://archives.real-time.com/pipermail/cocoon-devel/2003-September/thread.html#19117 >http://koala.ilog.fr/batik/mlists/batik-dev/archives/threads.html#03368 > >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." > >Joerg _________________________________________________________________ Learn how to help protect your privacy and prevent fraud online at Tech Hacks & Scams. http://special.msn.com/msnbc/techsafety.armx