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.
OK, I can certainly see that.
But I would respectfully suggest that if it's effectively causing the
"fop" shell script to fail when executed within a stock
Unix-based environment to break, it may make sense to look for
other/additional approaches to resolving this problem.
I'll have to noodle around with this and see what I can come up with that
preserves the sensitivity to embedded spaces in file names while
addressing the failure to correctly build the command (at least under
Solaris).
-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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
