Same here. That's why I said earlier, that you should use the PDF Transcoder (not FOP itself) if you can live without XSL-FO, because if you need XSL-FO (which I don't know) then you've got bad luck because there's currently no work-around. The CVS HEAD code is our code currently being redesigned and it will probably not work for any real-life application at the moment.
I've just verified the following with success: - Download Batik 1.5.1 (http://xml.apache.org/batik/) - Extract the SVG from the FO file into a plain SVG file. - On the command-line say: java -jar batik-rasterizer.jar -m application/pdf pieUnicode.svg (This uses FOP's PDF Transcoder to convert SVG to PDF. No XSL-FO involved.) Produces a nice PDF with spaces respected. If you need to integrate that in a Java application, then look at the Transcoder documentation here: http://xml.apache.org/batik/rasterizerTutorial.html http://cvs.apache.org/viewcvs.cgi/xml-fop/examples/embedding/java/embedding/ExampleSVG2PDF.java?rev=HEAD On 23.12.2004 12:07:50 Saptarshi Sen wrote: > Hi, > I tried to download the latest Code from > http://cvs.apache.org/snapshots/xml-fop/xml-fop_20041223052817.tar.gz and > then did a build on it. While converting the fo file into a PDF, I get the > error: > > Exception in thread "main" java.lang.OutOfMemoryError > <<no stack trace available>> > > Attaching the fo file. What could be the possible reason? > > Thanks, > Saptarshi. > > P.S. I performed the build using the "build.bat" file from FOP 0.20.5; The > build was successful. Could this have anything to do with this error? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
