Hi, The real problem here is that the api with batik has been changing. The batik.jar that comes with FOP is from the build-all target and when that was done depends on what version of FOP you are using. FOP uses a number of internal api's which have been subject to change from version 1.0 -> now. We at FOP are trying to keep the version of batik to the latest offical release but this isn't always practical.
Unfortunately the best I can offer at the moment is to wait for a release of FOP after the final batik 1.5 release. Keiron. On 2002.03.14 23:43 Joe Mihalich wrote: > > Hello, > > I have a few questions regarding the relationship between > FOP and Batik. > This may be a message for the FOP list, but I'll try here > first. > > From what I understand from reading docs on the xml > apache web site, > FOP has "extended" batik in some fashion and added a PDF > transcoder > Along with a few other classes. > > Here are my questions: > > 1) when you download the FOP binaries, you get most of the batik > binaries > in a batik.jar file. However, there is a new class in > org.apache.batik.gvt > called GraphicsNodeRendereContext. This file does not show up in the > batik 1.5 beta download. Wouldn't the FOP developers have checked these > files into the batik cvs tree in the gvt project? > > > 2) I'm confused in that, it seems the only way to convert SVG > files to PDF files > is to download the FOP library and run the rasterizer from the FOP > batik.jar > and point the class path to the fop.jar and crimson-parser.jar files. > It seems > logical, that at some point here, I should be able to download the > batik-1.x > binary, and the FOP 0.x binary, and run the rasterizer from the batik > downloads > jar file. That would assume that the batik engine is looking for > transcoder classes > dynamically, without import statements. > > It just seems weird that I have to do one of the following to support > the file formats > we need: > > a) use the batik binaries to convert svg to png, and jpg's. and use the > separate > fop library for converting svg to pdf. Not that two VM's would be > needed since > the batik binaries are different > > b) use the FOP binaries to do all conversion from svg to png,jpg, pdf. > Note that this is > risky as well in it's current phase because, I don't see any > indication of what "version" > of batik the fop binaries are based on. > > > Any clarification would be appreciated. > > Thanks, > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
