[jira] [Commented] (TIKA-2240) MS Write File

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828301#comment-15828301 ] 

Hudson commented on TIKA-2240:
------------------------------

SUCCESS: Integrated in Jenkins build Tika-trunk #1183 (See [https://builds.apache.org/job/Tika-trunk/1183/])
TIKA-2240 -- improve mime detection for .wri files (tallison: rev 00bb6f4ff28bf68935450966f25e8777367057e0)
* (edit) tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml
* (edit) tika-parsers/src/test/java/org/apache/tika/mime/TestMimeTypes.java
* (add) tika-parsers/src/test/resources/test-documents/testMSWriteFile.wri


> MS Write File
> -------------
>
>                 Key: TIKA-2240
>                 URL: https://issues.apache.org/jira/browse/TIKA-2240
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 2.0, 1.15
>
>         Attachments: 746255.doc
>
>
> We're currently identifying MS Write Files by suffix ".wri" in one place in our mime defs, but we're also using MS Write File's magic {{0x31be0000}} to identify the file as an MSWord (doc) file in a different definition.
> In govdocs1, there are a handful of .wri files with suffix .doc.  We're getting an Invalid Header exception for these files.
> I think it would be better to move their magic out of our .doc definition to the .wri definition and use the EmptyParser.
> Any objections?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)