[
https://issues.apache.org/jira/browse/TIKA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350556#comment-16350556
]
Tim Allison commented on TIKA-1599:
-----------------------------------
>Tim, if attached file is what you are looking for, i've got about 80 specimens
>that came up when grepping for base64.
W00t! Thank you! That one should do...and, duh, grep for base64. Thank you!
>On topic, our parser on top of Tika relies on a custom ContentHandler
>implementation. We (my company) would not be too happy if we would have to
>rewrite the whole thing. Same goes for Apache Nutch.
Oh...that's good to know...so I guess we're back to the option of supporting
both Tagsoup and JSoup with users specifying via tika-config.xml which parser
to use?
> 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, consumentenbond.html,
> 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)
