Open Synaps3 opened 7 years ago
Seems that not only does antiword require extra configuration under windows but it fails to handle docx, which seems we cannot handle today.
The solution to this bug is to create c:\antiword\ and drop the file 8859-1.txt from the antiword root folder into it...
created a function to do this: https://github.com/ryscott5/eparTextTools/blob/master/working/readDocInitWindows_codeReview.r
Currently in code review.
The term list for word documents imported seems to be just the error message for antiword. Perhaps the calling string is OS dependent?