Keyword indexing for Word documents (doc / docx)

ctgraham · March 1, 2017, 9:21pm

Currently external applications for fulltext indexing are driven by MIME type, via settings in config.inc.php.

pkp/ojs/blob/dfd84aa0242ce30ea75207b27a2fe945b113a4ef/config.TEMPLATE.inc.php#L361-L371


; PDF
; index[application/pdf] = "/usr/bin/pstotext -enc UTF-8 -nopgbrk %s - | /usr/bin/tr '[:cntrl:]' ' '"
; index[application/pdf] = "/usr/bin/pdftotext -enc UTF-8 -nopgbrk %s - | /usr/bin/tr '[:cntrl:]' ' '"

; PostScript
; index[application/postscript] = "/usr/bin/pstotext -enc UTF-8 -nopgbrk %s - | /usr/bin/tr '[:cntrl:]' ' '"
; index[application/postscript] = "/usr/bin/ps2ascii %s | /usr/bin/tr '[:cntrl:]' ' '"

; Microsoft Word
; index[application/msword] = "/usr/bin/antiword %s"
; index[application/msword] = "/usr/bin/catdoc %s"

I’ve found that both doc and docx documents are matched as “application/msword” in our RHEL-based systems. I haven’t found an instance of catdoc or antiword which handles both doc and docx in the same executable. I’ve resorted to a shell script which runs an extended file test, and then passes processing to catdoc or to docx2txt, respectively.

How are others dealing with this (or avoiding the problem)?