fop -d -c fopConfiguration.xml -xml work\A.xml -xsl
SLT\22Headingpdf.xsl -pdf work\a.pdf fop -d -c
fopConfiguration.xml -xml work\B.xml -xsl
SLT\22Headingpdf.xsl -pdf work\b.pdf fop -d -c
fopConfiguration.xml -xml work\C.xml -xsl
SLT\22Headingpdf.xsl -pdf work\c.pdf fop -d -c
fopConfiguration.xml -xml work\D.xml -xsl
SLT\22Headingpdf.xsl -pdf work\d.pdf ...
fop -d -c fopConfiguration.xml -xml work\Z.xml -xsl
SLT\22Headingpdf.xsl -pdf work\z.pdf
That is, running my XSLT script on the individual index files.
The first entry works, and creates my first PDF file (a.pdf),
but FOP exits the batch file after running the first entry -
the later lines are never run.
So, two questions:
(1) Can I prevent FOP from exiting the batch file?
(2) Or, should I be asking this question on another list, and
if so, which one?
Generally, as David Lee showed dramatically in a Balisage paper last week,
using shell script languages to control this kind of processing pipeline is
really bad news. You're much better off with say XProc or xmlsh or ant.
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--