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 2012/07/08 16:14:34 UTC

[jira] [Resolved] (TIKA-458) Specify HTMLHandler via Context

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

Jukka Zitting resolved TIKA-458.
--------------------------------

    Resolution: Won't Fix

Resolving as Won't Fix due to lack of activity and the fact that the existing IdentityHtmlMapper class already gives a client full access to the underlying SAX events.
                
> Specify HTMLHandler via Context
> -------------------------------
>
>                 Key: TIKA-458
>                 URL: https://issues.apache.org/jira/browse/TIKA-458
>             Project: Tika
>          Issue Type: New Feature
>          Components: parser
>    Affects Versions: 0.7
>            Reporter: Julien Nioche
>         Attachments: TIKA-458.patch
>
>
> One of the recent changes on Tika is the possibility to specify a custom HTMLMapper via the Context - which I think is an elegant mechanism. I was wondering whether there would be a reason NOT to be able to do the same for the HTMLHandler and if nothing is passed via the Context, rely on the current implementation. This would give more control to the user on what to do with the SAX events while at the same time preserving the functionality by default.

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