[
https://issues.apache.org/jira/browse/TIKA-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224661#comment-14224661
]
Nick Burch commented on TIKA-1486:
----------------------------------
I think we have a slightly expanded mimetype format, handling a few extra kinds
of matches to the original, which might explain some bits, eg the custom Tika
namespace and the rexegp matches
I fixed the two duplicates in r1641628, and the DITA subtype in r1641630,
thanks for that!
> Minor issues with the Tika MIME type magic file
> -----------------------------------------------
>
> Key: TIKA-1486
> URL: https://issues.apache.org/jira/browse/TIKA-1486
> Project: Tika
> Issue Type: Improvement
> Components: detector
> Affects Versions: 1.6
> Reporter: Andrew Jackson
> Priority: Minor
>
> I've started running some routine tests on format information held in a
> number of tools, including
> [Tika|http://www.digipres.org/formats/sources/tika/issues/]. This uncovered a
> number of minor issues when working with the tika-mimetypes.xml file:
> * Duplicate MIME type application/gzip-compressed for type application/gzip.
> * Duplicate MIME type image/vnd.dwg for type image/vnd.dwg.
> * Error when parsing XML: Namespace prefix tika on link is not defined, line
> 169, column 15
> * Format application/dita+xml;format=task has itself as a supertype!
> * Glob '^owl$' for entry application/rdf+xml does not appear to be a valid
> filename specification.
> * Glob '^rdf$' for entry application/rdf+xml does not appear to be a valid
> filename specification.
> With the last two, it's really a matter of consistency. The other
> full-filename globs do *not* use the ^ and $ start and end markers, but owl
> and rdf do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
