-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extract text from doc files(windows10 64) #96
Comments
have you declared the path to your antiword.exe file in the PATH global variable ? |
@zzzwx thanks for your reply,antiword does not support Windows. |
@SHocker-Yu i am using it on windows (7 and 10) |
@zzzwx appreciate for your kind reply. |
@SHocker-Yu what do you mean by "flash back" ? here are the steps I followed to make it work on windows : 0/ modify textract/lib/extractors/doc.js to fix a bug reported in a github issue
1/ download windows binary2/ add antiword directory to Windows' PATH environnement variable=> at this point it worked but only when the path to the doc file contained no spaces 3/ modify textract/lib/extractors/doc.js again to add quotes so that it reads the input path as is
=> at this point it worked for every paths 4/ modify textract/lib/extractors/doc.js one last time to manage UTF8 encoding of output text
=> and after that it worked well all the time :) hope this helps you |
@zzzwx I really appreciate for your kind,so sorry about my pool English,'flash back' means 'crash',these days i had to work all day ,and reply you so late,really sorry, i have readed your reply,and i will try it and then tell you the result. |
@zzzwx It works!Thank you so much!!! |
FYI, I've implemented the changes from above across a few different commits the last few months (sorry so slow!). |
Published as |
Hi @dbashford , thank you for your work |
"DOC extraction requires antiword be installed, link, unless on OSX in which case textutil (installed by default) is used."
OS: windows10 64
I installed antiword.exe failed,and i don't konw how to do with this problem...
The text was updated successfully, but these errors were encountered: