You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/12/27 04:33:52 UTC
[jira] [Resolved] (TIKA-1110) Incorrectly declared SUPPORTED_TYPES
in ChmParser.
[ https://issues.apache.org/jira/browse/TIKA-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-1110.
---------------------------------
Resolution: Fixed
Assignee: Jukka Zitting
Thanks, Vadim! I committed your patch (with spaces instead of tabs) in revision 1553617.
I also made a few follow-up improvements (and added a test case) in revisions 1553618 and 1553619 to make the integration with AutoDetectParser work more smoothly.
> Incorrectly declared SUPPORTED_TYPES in ChmParser.
> --------------------------------------------------
>
> Key: TIKA-1110
> URL: https://issues.apache.org/jira/browse/TIKA-1110
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.3, 1.4
> Reporter: Andrzej Bialecki
> Assignee: Jukka Zitting
> Fix For: 1.5
>
> Attachments: TIKA-1110.patch
>
>
> [This link|http://www.iana.org/assignments/media-types/application/vnd.ms-htmlhelp] assigns the official mime type for these files to "application/vnd.ms-htmlhelp". In the wild there are also two other types used:
> * application/chm
> * application/x-chm
> tika-mimetypes.xml uses the correct official mime type, but ChmParser declares that it supports only "application/chm". For this reason content that uses the official mime type (e.g. coming via Detector or parsed using AutoDetectParser, or simply declared in metadata) fails to parse due to unknown mime type.
> The fix seems simple - ChmParser should declare also all of the above types in its SUPPORTED_TYPES.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)