Dear All, On the top, thank you so much for the prompt response!
Let me allow to say what I've done so far.. I downloaded the fop-0.94-bin.tar and unzipped it in a windows machine. Then I moved the unzipped files to Solaris box inside folder /var/fop. Under it, when I tried to generate a test pdf by issuing the following command: fop -xml test.xml -xsl test.xsl -pdf test.pdf I got the first error "-bash: fop.sh: command not found". I have set the resepective PATH and it's gone but I got the second error like "No such file or directory". After fixing the second issues, I got the error which was related to FOP.sh i.e. IFS=^J is not an identifier. After doing some R N D, I got rid of the issue by changing the line 25 of fop.sh to: IFS="" export IFS At that time, I was successfully able to execute the fop.sh but NOT with parameter. In other approach of resolving the issue, I have taken the source file(fop.sh) and convert it using dos2unix command by hoping that it will do the magic as suggested in one of the thread. But all vain.. Please advice, what I have to do to get rid of it? Once again, thank you so much for your time and valuable comments! With Thanks! Newkid Matt Healy wrote: > > 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 now especially on Windows. > > How about this as an alternative, then: simply move the assignment to > (and export of) IFS to a point immediately *after* the evaluation of the > command-line arguments. In this way, the loop will appropriately > differentiate between the arguments, rather than failing to break the > evaluation of '"$@"' on the spaces between quoted values. > > In other words, rewrite: > > export IFS=" > " > for arg in "$@" ; do > . . . . > done > > as: > > for arg in "$@" ; do > . . . . > done > export IFS=" > " > > The content within the "for" loop appears to be space-friendly, since it's > using escaped double-quotes to build up the content of the "fop_exec_args" > variable from the values of "$arg", and no other potential file names are > being used in the loop. > > I think this should maintain the space-friendly nature of all of the > subsquent code, while letting the "for" loop parse the data in a way that > is compliant with Bourne shell under Solaris (and possibly other > platforms) where the current code does not. > > (Hopefully I haven't missed anything.... ;-) > > -mjh > -- > Matthew J. Healy > Computer Science & Information Technology Departments > Golisano College of Computing and Information Sciences, RIT > mailto:[EMAIL PROTECTED] > http://www.cs.rit.edu/~mjh > Voice: (585) 248-3425 > >> >> J.Pietschmann >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/FOP-0.94-bin---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]
