Luis Filipe Nassif commented on TIKA-1599:

Hi [~talli...@mitre.org],

Moving to DOM could lead to higher memory usage and maybe bring memory problems 
like those we had experienced with the Office DOM parsers. But given all the 
problems of TagSoup, I think it is worth doing a new evaluation to see if we 
can get more content and the lost metadata back (from your previous test).

> 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

Reply via email to