[
https://issues.apache.org/jira/browse/TIKA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049308#comment-15049308
]
Markus Jelsma commented on TIKA-1599:
-------------------------------------
Hello - we rely on Tika for our content extraction framework, similar to
Boilerpipe. All we use is the parser delegating SAX events to our
ContentHandlers. If i could signal Tika to use JSoup or any other
implementation i can probably find the issues, e.g. TIKA-1808 and some other
issues i reported.
The extraction framework relies on unit tests for over 750 real world web
pages. I am quite sure most subtle differences between the parsers are going to
break at least some tests, hopefully uncovering the differences or improvements
of JSoup over TagSoup.
> 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
>
> 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
(v6.3.4#6332)
