tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Krugler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TIKA-564) Support returning original markup in BoilerpipeContentHandler
Date Wed, 01 Dec 2010 00:43:16 GMT

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

Ken Krugler updated TIKA-564:
-----------------------------

    Attachment: TIKA-564.patch

Patch sponsored by Mashlogic - thanks!


> Support returning original markup in BoilerpipeContentHandler
> -------------------------------------------------------------
>
>                 Key: TIKA-564
>                 URL: https://issues.apache.org/jira/browse/TIKA-564
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 0.8
>            Reporter: Ken Krugler
>            Assignee: Ken Krugler
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: TIKA-564.patch
>
>
> Currently the BoilerpipeContentHandler emits all non-boilerplate text (as defined by
Boilerpipe) as a series of <p>xxx</p> text blocks, without any markup.
> But if you need to find URLs in these blocks, or section headers, then the original markup
has to be preserved.
> Unfortunately Boilerpipe currently assumes that you have the ability to replay the input
stream, and parse it a second time to match up text with what's been extracted (e.g. see HTMLHighlighter),
but with Tika that's not easy to do - the interface is a ContentHandler, so you don't have
the original inputstream to spool out.
> Instead I plan to record the minimum SAX events, and replay those.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message