You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/07/06 15:27:00 UTC
[jira] [Commented] (TIKA-2673) HtmlEncodingDetector doesn't follow
the specification
[ https://issues.apache.org/jira/browse/TIKA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534992#comment-16534992 ]
Tim Allison commented on TIKA-2673:
-----------------------------------
[~gbouchar], thank you for contributing this! I won't have time to run the regression tests any time soon. Would you be ok if I added your StrictHtmlEncodingDetector to Tika now? Users would then be able to configure Tika to use it via tika-config.xml. If you're ok with this, is it ok if I add the Apache Software License 2.0 headers to your main class, test class and .tsv files?
Thank you, again!
> HtmlEncodingDetector doesn't follow the specification
> -----------------------------------------------------
>
> Key: TIKA-2673
> URL: https://issues.apache.org/jira/browse/TIKA-2673
> Project: Tika
> Issue Type: Bug
> Reporter: Gerard Bouchar
> Priority: Major
> Attachments: HtmlEncodingDetectorTest.java, StrictHtmlEncodingDetector.tar.gz
>
>
> This bug is linked to TIKA-2671, but does not concern metadata, but rather the bytes-based detection itself.
> While reading the specification, I collected a list of sample cases where HtmlEncodingDetector differs from the specification, and thus fails at detecting the right charset.
> I am attaching the test cases to this issue:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)