On Thursday 12 October 2006 08:05, Thomas Schraitle wrote: > On Wednesday 11 October 2006 19:52, Sean Wheller wrote: > > On Wednesday 11 October 2006 13:49, Thomas Schraitle wrote: > > > fop or xep > > > > The package is dependant on fop. What does one do when one does > > manual installations of FOP :-) > > That's an interesting question. You probably mean, if you want to use > FOP from trunk, right? > > The RPM requires FOP from our distribution, which is 0.20.5, if I > remember correctly. You have to install this package due to the > package requirements. To use a different formatter, for example the > latest from FOP trunk, add the following line at the end to your ENV > file: > > export FOP=PATH_TO_FOP > > Replace PATH_TO_FOP to your executable from trunk. Hope this helps.
OK, I understand. I don't use the package system to configure fop. So I use the CLASSPATH installation method. echo $CLASSPATH /usr/share/saxon/saxon.jar:/usr/share/xml/docbook/stylesheet/nwalsh/current/extensions/saxon653.jar:/usr/share/fop/build/fop.jar:/usr/share/fop/lib/batik.jar:/usr/share/fop/lib/xalan-2.4.1.jar:/usr/share/fop/lib/xercesImpl-2.2.1.jar:/usr/share/fop/lib/JimiProClasses.jar:/usr/share/fop/lib/avalon-framework-cvs-20020806.jar:/usr/share/fop/lib/jai_core.jar:/usr/share/fop/lib/jai_codec.jar I will just make changes to suse-doc to suite. Thanks, -- Ask me about the Monkey. Sean Wheller Technical Author [EMAIL PROTECTED] +27-84-854-9408 http://www.inwords.co.za --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
