You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "John Mastarone (Updated) (JIRA)" <ji...@apache.org> on 2012/01/11 04:35:39 UTC

[jira] [Updated] (TIKA-839) TikaException with testPPT.potm in Tika GUI / CLI

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

John Mastarone updated TIKA-839:
--------------------------------

    Attachment: testPPT.potm
                TIKA-839.patch

OOXMLParserTest update, and new valid potm file.
                
> TikaException with testPPT.potm in Tika GUI / CLI
> -------------------------------------------------
>
>                 Key: TIKA-839
>                 URL: https://issues.apache.org/jira/browse/TIKA-839
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.1
>         Environment: Windows 7
>            Reporter: John Mastarone
>         Attachments: TIKA-839.patch, testPPT.potm
>
>
> Attempting to open the testPPT.potm file found in the parsers' test-documents folder in a latest build of Tika will result in a TikaException, itself 'Caused by: org.apache.xmlbeans.XmlException: error: The document is not a presentation@http://schemas.openxmlformats.org/presentationml/2006/main: document element namespace mismatch expected "http://schemas.openxmlformats.org/presentationml/2006/main" got "http://schemas.openxmlformats.org/presentationml/2006/3/main"'.  I opened this file in MS Office 2007, and it said that it was a file created with a beta version of Office, and that it would updated the next time it was saved to a more up-to-date format.  I made the contents look like that of the other Office 2007 presentation documents in the test-documents folder, and added this file and its mime type to the OOXMLParserTest class, and then had no problems with the .potm file. I'll attach a patch shortly.

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