You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Nick Burch (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/13 16:03:39 UTC

[jira] [Resolved] (TIKA-840) OOXML parser content type setting

     [ https://issues.apache.org/jira/browse/TIKA-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Burch resolved TIKA-840.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
    
> OOXML parser content type setting
> ---------------------------------
>
>                 Key: TIKA-840
>                 URL: https://issues.apache.org/jira/browse/TIKA-840
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.0
>            Reporter: Nick Burch
>            Assignee: Nick Burch
>             Fix For: 1.1
>
>
> At the moment, some of the OOXML parsers set a content type, and others don't. Those that do always set the base type, no matter the contents
> Instead, the detection logic should be re-used where possible within the parsers, with overriding only needed for things like protected files
> (Once fixed, a few parts of the ooxml tests around types that are currently commented out can be re-enabled)

--
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