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.
Joerg,
Sorry for the delay in replying...
On 28.02.2004 19:18, Steve Schwarz wrote:
Thanks for the info.
I tried replacing the Cocoon jars: batik-all-1.5.jar fop-0.20.5.jar
with the FOP 0.20.5 jars (fop.jar batik.jar) in that case no SVG is
rendered at all because there is a problem with use
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:
?xml version=1.0 encoding=UTF-8?
fo:root xmlns:svg=http://www.w3.org/2000/svg;
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
On 28.02.2004 19:18, Steve Schwarz wrote:
Thanks for the info.
I tried replacing the Cocoon jars: batik-all-1.5.jar fop-0.20.5.jar
with the FOP 0.20.5 jars (fop.jar batik.jar) in that case no SVG is
rendered at all because there is a problem with use and url(#), even
though the reference is
Thanks for the info.
I tried replacing the Cocoon jars: batik-all-1.5.jar fop-0.20.5.jar
with the FOP 0.20.5 jars (fop.jar batik.jar) in that case no SVG is rendered
at all because there is a problem with use and url(#), even though the
reference is resolved within the same svg element (and
Same FOP version? Do you imply other Cocoon versions are working?
Nope, I'm implying FOP standalone with the same FOP version as Cocoon
uses works correctly :^)
ok
It looks like when invoked through Cocoon FOP is still reserving the
right amount of space (based on the svg with/height
Torsten Curdt wrote:
Can anyone tell me how the Cocoon fop and batik jar files are
generated and how that is different from the jars supplied with FOP?
THere were some Cocoon releases which shipped with a different
Batik jar than the corresponding FOP release, partly due to
interface changes in
I've got a weird problem generating pdfs using FOP from xml containing
SVG; but only when processed through Cocoon (2.1.2). Generation directly
with FOP is problem free.
Same FOP version? Do you imply other Cocoon versions are working?
cheers
--
Torsten
Hi
I've got a weird problem generating pdfs using FOP from xml containing
SVG; but only when processed through Cocoon (2.1.2). Generation directly
with FOP is problem free.
Same FOP version? Do you imply other Cocoon versions are working?
Nope, I'm implying FOP standalone with the same FOP
Hi Steve:
I think it would be fine if you can upgrade to Cocoon 2.1.4. Also if you
cannot find the answer here, you can also search or ask in the user list
of FOP:
http://xml.apache.org/fop/maillist.html
or Batik:
http://xml.apache.org/batik/mailList.html
If I will be able to help, I will post
11 matches
Mail list logo