On Wed, Mar 1, 2017 at 8:47 PM, Silas Berger <silas.berger@students.unibe.ch> wrote:
Hi everyone,
Iâm currently experiencing problems with PipeableOSProcess. Iâm using a
command to run a third party tool, which reads a txt file and returns an XML string. In my collection, this works fine for about 75 out of 100 txt files, but fails on the remaining 25 ones. However, the tool itself doesnât fail. It works fine, if I issue the commands directly from a Terminal.
Hereâs an example of a command string that works:
/Users/silas/Documents/ExtendedEggShell/Moose6.0/ExtendedEggShell/tools/mac/parsecit/bin/citeExtract.pl -m extract_all /Users/silas/Documents/ExtendedEggShell/Moose6.0/ExtendedEggShell/examplePDFsFromList/Ache00aScriptingCoordStyles.pdf.txt
And hereâs an example of one that doesnât work.
/Users/silas/Documents/ExtendedEggShell/Moose6.0/ExtendedEggShell/tools/mac/parsecit/bin/citeExtract.pl -m extract_all /Users/silas/Documents/ExtendedEggShell/Moose6.0/ExtendedEggShell/examplePDFsFromList/Ardi97aSchemeTeaching.pdf.txt
This is how I apply these commands through PipeableOSProcess:
xml := (PipeableOSProcess command: cmdString) output.
For the first command, xml is a large XML string, for the second command,
itâs just an empty string. Sorry I don't know the answers your seek - but just to clarify something. How significant is that empty string return? cheers -ben