I am invoking a text extractor with these lines in a Perl/CGI script: 
my $doctotextcmd = "no-frills %a %d %f";

`"doctotext.exe --fix-xml --unzip-cmd = $doctotextcmd $success[0] > te
+mp.txt"`;

[download]
With corrupt docx files, I get no results. The script works fine with un-corrupt docx files. When I run the script from a Windows command line, it also give me an error but runs anyway and produces usable result.

Is there a way to allow the CGI/Perl script to continue in the Web environment despite the error? Below is the command line I'm invoking successfully locally. 

Command-prompt>doctotext.exe --fix-xml --unzip-cmd = "no-frills %a %d 
+%f" intro.docx > temp.txt

[download]
Here's the output from the command line: 
Executing no-frills.exe intro.docx C:\Users\socrtwo\AppData\Local\Temp
+\2 word\do
cument.xml >&2
file(s) not foundExecuting rmdir /S /Q C:\Users\socrtwo\AppData\Local\
+Temp\2
Using ODF/OOXML parser.
Executing no-frills.exe intro.docx C:\Users\socrtwo\AppData\Local\Temp
+\3 word\do
cument.xml >&2
file(s) not foundExecuting rmdir /S /Q C:\Users\socrtwo\AppData\Local\
+Temp\3

[download]
The script is invoked here. The full relevant section (not any commercial code like I posted last time, sorry!) can be seen here on pastebin. The MS Office converter can be downloaded here. Note I don't think the version of the version of doctotext converter I'm using has been released by the authors to the general public yet, just to me who is sponsoring the development.

++++Update+++

Very oddly, the command line app, DocToText is very sensitive to spaces for some reason. This really didn't work after all for corrupt files, but continued to work for uncorrupt ones: 

Command-prompt>doctotext.exe --fix-xml --unzip-cmd = "no-frills %a %d 
+%f" intro.docx > temp.txt

[download]
But this did with the corrupt and un-corrupt files: 
Command-prompt>doctotext.exe --fix-xml --unzip-cmd="no-frills %a %d %f
+" intro.docx > temp.txt

[download]
Thanks for the help!

In reply to Error Suppresses Output from CGI Script That Runs Fine from the Command Line by socrtwo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.