[
https://issues.apache.org/jira/browse/TIKA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170579#comment-15170579
]
Nick Burch commented on TIKA-1877:
----------------------------------
Posting the whole modified tika mimetypes file isn't ideal - it's hard for us
to see what has changed and what hasn't, especially given the file's large
size. Would you be able to post a patch/diff showing just your changes, to help
us review and possibly spot the issue?
(I tried diff'ing it to trunk, but got such a large number of changes I
couldn't see what was supposed to be your change amongst them)
Ideally, also, it would be easier if you could write a short junit unit test
showing the detection issue. That's generally much quicker and easier to test
with, as well as having the bonus of proving a check to ensure that post-fix it
stays fixed!
> On updating the tika-mimetypes.xml to detect .fts file format, tika detector
> does not return anything
> -----------------------------------------------------------------------------------------------------
>
> Key: TIKA-1877
> URL: https://issues.apache.org/jira/browse/TIKA-1877
> Project: Tika
> Issue Type: Bug
> Components: mime
> Reporter: Prasad Nagaraj Subramanya
> Priority: Minor
> Attachments:
> 4E8D6B46E2366D7063DE3926AF0F976A0DCCD57A7E3B53B7D54768F16DD23984,
> tika-mimetypes.xml
>
>
> The match value for .fts file format in tika-mimetypes.xml is "SIMPLE =
> T".
> Tika detected a .fts file as application/octet-stream. On verifying the
> header I found the value to be "SIMPLE = T"(just 16 spaces
> before = and T)
> I tried the following changes-
> Change 1) Updated the existing match value. But the build failed
> Change 2) Added a new match value <match value="SIMPLE = T"
> type="string" offset="0"/> after the existing one.
> But now, tika returns empty value. It neither identifies the file as .fts nor
> as application/octet-stream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
