[ https://issues.apache.org/jira/browse/TIKA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Burch resolved TIKA-1877. ------------------------------ Resolution: Fixed Fix Version/s: 1.13 Patch applied, with a slight tweak to rename the test file to better match our naming standards. Thanks! > 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 > Fix For: 1.13 > > Attachments: > 3DEE2CE70CAD248DC8A46C2D0BD0BD6C21AACE54AC958264773390B39C8AF079, > 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)