>
> Why do you not write about this issue to the fop-users list? This is
> not really a development issue.
>
> On Fri, Dec 18, 2009 at 11:27:31AM -0600, Brian Mackey wrote:
>>
>> I'm not a batch file programmer, but glancing at fop.bat, the last line:
>> &qu
I just blew out about 4 hours trying to get fop.bat to run in the
command prompt programmatically in windows. Turns out that the
problem was the fop.bat file itself. It references a file "fop.xconf"
by appending current directory + "\conf\fop.xconf". This turns out to
be a programming killing fea
