I assumed fop-users would not be appropriate because I felt this was a
code issue. Though, as you have explained this bug was introduced by
Altova and I much appreciate your explanation. I'll re-direct the
problem to them.
On Fri, Dec 18, 2009 at 12:40 PM, Simon Pepping wrote:
> Brian,
>
> Why
Brian,
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:
> "%JAVACMD%" %JAVAOPTS% %LOGCHOICE% %LOGLEVEL% -
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
