[
https://issues.apache.org/jira/browse/TIKA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350335#comment-16350335
]
Tim Allison edited comment on TIKA-1599 at 2/2/18 1:42 PM:
-----------------------------------------------------------
What say we do a fresh eval on our current corpus and then do a clean cut over
to JSoup for Tika 2.0 if the results are promising?
Big question: are we willing to move to DOM for HTML. SAX is not yet available
in JSoup (https://github.com/jhy/jsoup/issues/824).
was (Author: [email protected]):
What say we do a fresh eval on our current corpus and then do a clean cut over
to JSoup for Tika 2.0 if the results are promising?
> Switch from TagSoup to JSoup
> ----------------------------
>
> Key: TIKA-1599
> URL: https://issues.apache.org/jira/browse/TIKA-1599
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 1.7, 1.8
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Priority: Minor
> Attachments: TIKA-1599-crazy-files.tar.gz,
> tagsoup_vs_jsoup_reports.zip
>
>
> There are several Tika issues related to how TagSoup cleans up HTML
> ([TIKA-381], [TIKA-985], maybe [TIKA-715]), but TagSoup doesn't seem to be
> under active development.
> On the other hand I know of several projects that are now using
> [JSoup|https://github.com/jhy/jsoup], which is an active project (albeit only
> one main contributor) under the MIT license.
> I haven't looked into how hard it would be to switch this dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
