Just guessing: You are on Unix and you don't have the display variable set
when you run cocoon?
If this is the case, either point the display variable to your X environment
or, if you don't have one search in the cocoon docu for headless.
Christoph
-Original Message-
From: Irving
I am on windows XP using cocoon-2.0.4. I understand the headless issue
and that is not my problem.
On the same box, I use the same version of fop (0.20.4), and the command
line fop.bat file renders it perfectly. Running inisde cocoon gives me
the error that I outlined below.
Irv
Schaper,
On Mon, 2003-06-23 at 15:27, Irving Salisbury III wrote:
ERROR (2003-06-23) 08:02.42:903 [sitemap.serializer.fo2pdf.fop]
(/medicaid/sequence/first/pdf) Thread-10/PDFRenderer: svg graphic could
not be built: null
If you use batik for rendering SVGs you need an X-Server running or Java
I am running this on windows XP. Do I still need to do this?
Irv
Torsten Spindler wrote:
On Mon, 2003-06-23 at 15:27, Irving Salisbury III wrote:
ERROR (2003-06-23) 08:02.42:903 [sitemap.serializer.fo2pdf.fop]
(/medicaid/sequence/first/pdf) Thread-10/PDFRenderer: svg
Irving Salisbury III wrote:
I have embedded an SVG image into my xsl:fo document. It renders fine
when using command line fop. However, when I put it in a cocoon
pipeline, I am getting the following error:
ERROR (2003-06-23) 08:02.42:903 [sitemap.serializer.fo2pdf.fop]
...
I am using a third partly library that does things like url(
#someReference), so I can't get around it.
Why is this not a bug, it seems like something that should be supported,
and batik even has a bug fix in 1.5b4 (that happens to break the library
code for me)
Irv
J.Pietschmann wrote:
Irving Salisbury III wrote:
I am using a third partly library that does things like url(
#someReference), so I can't get around it.
Why is this not a bug, it seems like something that should be supported,
and batik even has a bug fix in 1.5b4 (that happens to break the library
code for me)
Thanks for the info. I will go down another path with this.
Irv
J.Pietschmann wrote:
Irving Salisbury III wrote:
I am using a third partly library that does things like url(
#someReference), so I can't get around it.
Why is this not a bug, it seems like something that should be
supported,
