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

Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/09/14 13:22:00 UTC

[jira] [Updated] (TIKA-2726) Handle truncated ooxml more robustly

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

Tim Allison updated TIKA-2726:
------------------------------
    Attachment: C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65_1.19-pre-rc1.json
                C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65_1.18.json
                C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65.xlsm

> Handle truncated ooxml more robustly
> ------------------------------------
>
>                 Key: TIKA-2726
>                 URL: https://issues.apache.org/jira/browse/TIKA-2726
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>         Attachments: C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65.xlsm, C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65_1.18.json, C46JNLYFA3HSONOL3IF6LTQO3ZO5JI65_1.19-pre-rc1.json
>
>
> With the move from Tika 1.18 to 1.19, we're now failing to detect some truncated ooxmls more specifically than {{tika-ooxml}}.  In the attached example, which Excel is able to fix, in 1.18, this file is identified as {{application/vnd.ms-excel.sheet.macroenabled.12}}, and it is parsed without exception by the ooxml parser.  However, in 1.19, this is identified as {{tika-ooxml}} and then parsed by the Package parser.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)