Adam Strzelecki wrote: >> This is a known problem. It will disappear when we'll upgrade >> * Our FOP 1 add-on to FOP 0.95+ (currently we use FOP 0.94). >> * Our JEuclid add-on to JEuclid 3.1 (currently we use JEuclid 3.0.3). > > Yeah, FOP 0.95+ also fixes problems with <auto-detect/> fonts in FOP, > so this update will be great addition to XXE. Now I must use custom > cooked version of FOP :(
OK. > Hussein, please keep in mind the problem from "[XXE] Cannot produce > PDF with FOP1 addon on Mac" thread, xalan.jar is missing by default in > FOP extension while it comes by default in FOP distro, normally it is > not used by with custom FOP configuration, like <auto-detect/> fonts, > Xalan seems to be used -> FOP needs URI$MalformedURIException from > Xalan.jar. It is a bit more complicated than this: --> Here are excerpts of the thread (~02/21/2008): --- HS to AS: Out of the box, the FOP1 add-on seems to work fine on Mac OS X 10.5. AS to HS: Deal, you're right. If I remove ~/.fop folder the crash no longer happens. But it crashes if FOP was used with any external font configuration. --- After that, we have released 3.8 (April 4, 2008): --- * Added an url attribute to the parameter configuration element. Example of use: <parameterGroup name="docb.toPS.FOPParameters"> <parameter name="configuration" url="true">fop.xconf</parameter> </parameterGroup> --- We have tested this of course. So in principle, we consider this problem closed. Of course, we'll reopen it if you can reproduce it with XXE v4 and our *unmodified* "Apache FOP 1.x XSL-FO processor plug-in" add-on.
