[
https://issues.apache.org/jira/browse/TIKA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192074#comment-13192074
]
Andrew Jackson commented on TIKA-849:
-------------------------------------
I'm not that familiar with the content handling infrastructure of Tika at
present, so I'm having trouble working out how to do this. I can see the
ePubParser delegating the content handling to the ePubContentParser which uses
an XHTMLContentHandler, but I don't really understand that code well enough to
see why it discards the <object> elements and lets the others through. Or
perhaps that filtering is done at a later stage?
In any case, I suppose we would need a new iBooksParser and a new
iBooksContentParser, based on the ePub code, but using a different
ContentHandler?
> Identify and parse the Apple iBooks format
> ------------------------------------------
>
> Key: TIKA-849
> URL: https://issues.apache.org/jira/browse/TIKA-849
> Project: Tika
> Issue Type: New Feature
> Components: mime, parser
> Affects Versions: 1.1
> Reporter: Andrew Jackson
> Attachments: ibooks-support.patch
>
>
> With the release of iBooks Author 1.0, Apple have created a new eBook format
> very similar to ePub. Tika could be extended to identify and parse this new
> format, re-using the existing ePub code wherever possible.
> I have created an initial patch, which I will attach to this issue.
--
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
