On Fri, 2009-10-16 at 15:17 +0200, Simon Pepping wrote: > On Wed, Oct 14, 2009 at 09:02:56PM +0200, Simon Pepping wrote: > > On Tue, Oct 13, 2009 at 01:34:40PM -0700, Jack Bates wrote: > > > I originally posted to the Xerces list because I thought the question > > > was how to get Xerces to use the XML catalog, but Michael Glavassevich > > > replies that the question is actually, "how to get FOP to provide an XML > > > catalog to Xerces?" > > > > I believe that that is indeed the problem. There is no command-line > > option in FOP for setting an entityresolver on the parser, and there > > is no code in FOP that would do that. It should not be difficult to > > achieve, if someone takes the time to do it. > > I did that today. There is now an option -catalog, which adds a > catalog resolver for parsing the XML and XSLT files. You need to have > xml-commons-resolver in the classpath, except in java6, where it is > included.
Fantastic, thanks Simon! I tested with revision 828778, and after working around this issue, http://thread.gmane.org/gmane.text.xml.commons.devel/1313 - I successfully built a PDF with the following command, $ ./fop -catalog -xml icaatom.html -xsl icaatom.xsl icaatom.pdf I am running Java 6, so I removed the libxml-commons-resolver1.1-java package because, as you say, it's included Thanks again : ) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
