[
https://issues.apache.org/jira/browse/TIKA-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved TIKA-746.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1)
1.0
There was a backwards compatibility issue with existing
client binaries that used the previous create() methods in
MimeTypesFactory. I restored those methods as wrappers around
the new ones in revision 1189126.
Overall the solution looks good to me, so resolving as fixed for 1.0.
> Support custom mime types
> -------------------------
>
> Key: TIKA-746
> URL: https://issues.apache.org/jira/browse/TIKA-746
> Project: Tika
> Issue Type: Improvement
> Components: mime
> Affects Versions: 0.10
> Reporter: Nick Burch
> Assignee: Nick Burch
> Fix For: 1.0
>
>
> As discussed over the summer
> <http://lucene.472066.n3.nabble.com/Appending-Mime-Types-td3266434.html>
> there are legitimate cases for wanting to load in extra, custom mimetypes
> (and their matching rules) to Tika
> Discussions seem to conclude that the built in tika-mimetypes file should be
> used for common and public mimetypes, and people wanting to support
> additional public formats should open an issue to have them in the main file.
> People who want only a very restricted set of mimetypes can use a custom tika
> config with a limited, smaller mimetypes file
> For people who want to load one or two extra, likely custom mimetypes, we
> should provide a service loading system to pull in the extra mimetypes. This
> allows for the regular mimetypes file to be used for most files, and the
> extra custom ones merged in as needed. It also allows for a custom parser to
> provide the mimetype detection for the specific custom formats it handles
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
