[
https://issues.apache.org/jira/browse/TIKA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828386#comment-15828386
]
Hudson commented on TIKA-2240:
------------------------------
SUCCESS: Integrated in Jenkins build tika-2.x #202 (See
[https://builds.apache.org/job/tika-2.x/202/])
TIKA-2240 -- improve mime detection for .wri files (tallison: rev
161b122ba9cbb06d6bd34623837ec26956d2dc22)
* (edit) tika-app/src/test/java/org/apache/tika/mime/TestMimeTypes.java
* (edit) tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml
* (add)
tika-test-resources/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)
