[
https://issues.apache.org/jira/browse/TIKA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170969#comment-15170969
]
Namitha Sanjeeva Ganiga edited comment on TIKA-1877 at 2/28/16 8:39 AM:
------------------------------------------------------------------------
I also noted this same issue..
>From the descriptions on the .fits file format, looks like there are 20 spaces
>from "=" to "T". Tika parser is behaving the same now.
<match value="SIMPLE = T" type="string" offset="0"/>
If we check the file that has been classified as octet-stream, we see that
there are 16 spaces between "=" and "T". (That is why it is getting classified
as octet-stream and not application/fits.
The question then would be , if the files( like the ones attached, that has 16
spaces) need to be classified into application/fits? As the file is similar to
a fits file which is already classified as application/fits.
Reference :
http://fits.gsfc.nasa.gov/standard30/fits_standard30.pdf
https://tools.ietf.org/html/rfc4047
was (Author: [email protected]):
I also noted this same issue..
>From the descriptions on the .fits file format, looks like there are 20 spaces
>from "=" to "T". Tika parser is behaving the same now.
<match value="SIMPLE = T" type="string" offset="0"/>
If we check the file that has been classified as octet-stream, we see that
there are 16 spaces between "=" and "T". (That is why it is getting classified
as octet-stream and not application/fits.
The question then would be , if the files( like the ones attached, that has 16
spaces) need to be classified into application/fits?
Reference :
http://fits.gsfc.nasa.gov/standard30/fits_standard30.pdf
https://tools.ietf.org/html/rfc4047
> 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)
