[jira] [Commented] (TIKA-2810) Back off to tagsoup when xml parser fails on Tika xhtml in tika-eval

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (TIKA-2810) Back off to tagsoup when xml parser fails on Tika xhtml in tika-eval

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/TIKA-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736317#comment-16736317 ]

Hudson commented on TIKA-2810:
------------------------------

UNSTABLE: Integrated in Jenkins build tika-2.x-windows #374 (See [https://builds.apache.org/job/tika-2.x-windows/374/])
TIKA-2810 -- handle bad tags more robustly (tallison: rev 517adc9d7056e90f48d132e27bfe3f44b8453338)
* (edit) tika-eval/src/main/java/org/apache/tika/eval/AbstractProfiler.java
* (edit) tika-eval/src/test/java/org/apache/tika/eval/SimpleComparerTest.java
* (edit) CHANGES.txt
* (edit) tika-eval/src/main/java/org/apache/tika/eval/util/ContentTags.java


> Back off to tagsoup when xml parser fails on Tika xhtml in tika-eval
> --------------------------------------------------------------------
>
>                 Key: TIKA-2810
>                 URL: https://issues.apache.org/jira/browse/TIKA-2810
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>             Fix For: 2.0.0, 1.21
>
>
> On TIKA-2791, we added extraction of structure tags.  If there's a parse failure on Tika's xhtml, we initially backed off to treat the full xhtml as if it were a string of text that happened to include markup.  
> It would be better to back off to the html parser so that content comparisons can still work accurately even if there is a tag failure: <b><i></b></i>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)