Hi,
Sorry to wake up a bit late, but I’d like to bring some precisions.
First, there’s no particular differences between the .tar.gz and the
.zip distribution files. In both, the fop shell script is in unix format
(lines ending with LF), while the fop.bat, fop.cmd and fop.js script
files are in
---Severe-Exceptions-on-Solaris-Box-tp16175972p16194929.html
Sent from the FOP - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
this message in context:
http://www.nabble.com/FOP-0.94-bin---Severe-Exceptions-on-Solaris-Box-tp16175972p16175972.html
Sent from the FOP - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Newkid wrote:
Support Cell,
Could you please advice what needs to be done to run the FOP 0.94 on a
solaris box? I have set the CLASSPATH; Convert the FOP.sh file for UNIX; etc
for all necessary files but when I tried to run FOP on Solaris it's showing
the below error:
Maybe your
John Brown wrote:
Newkid wrote:
Support Cell,
Could you please advice what needs to be done to run the FOP 0.94 on a
solaris box? I have set the CLASSPATH; Convert the FOP.sh file for UNIX; etc
for all necessary files but when I tried to run FOP on Solaris it's showing
the below error:
Matt Healy wrote:
I went back and checked the script, and found that IFS is being set just
to the newline character, and does not include spaces.
This is intentional: it avoids splitting directorie names which
contain spaces, which is rather common now especially on Windows.
J.Pietschmann
On Thu, 20 Mar 2008, J.Pietschmann wrote:
Matt Healy wrote:
I went back and checked the script, and found that IFS is being set just
to the newline character, and does not include spaces.
This is intentional: it avoids splitting directorie names which
contain spaces, which is rather common
