Here's my theory:
As the debug-enabled versions imported Word docs fine, too, Windows NT
must not set default locale until you try to print something (by
calling *printf function). So in non-debug versions, a *printf is never
called, and it hits the isprint with an undefined locale. And with debug
versions, there are lots of calls to *printf, which sets the locale to a
default of C and then manages the isprint fine.
In CVS, someone has recently modified it to not even bother with the
isprint test block. That version should work, too. I figure Caolan should
make the final decision on how to handle this (keep the isprint test
[using setlocale] or just remove the block [it is just a sanity check]?).
Also, there is a version of Word which outputs RTF with a .doc label. I
have encountered this, and the importer said it was normal text causing
me to inspect it, recognize the RTF, and then use the RTF importer
explicitly. If we keep a test which recognizes that the file is text, we
can automate that process for the user. wv says it's text, so try RTF, and
if that doesn't work, maybe we could just feed it to the text importer.
Anyway, Thomas, thanks for your help in figuring out exactly what was
going wrong.
Justin