[ https://issues.apache.org/jira/browse/TIKA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546190#comment-16546190 ]
Gerard Bouchar commented on TIKA-2673: -------------------------------------- If anyone wants to replicate the experiment with a different setting, I cannot provide our version of nutch, but here is [the node script I used to fetch pages in chrome|https://gist.github.com/GerardBouchar/3ef6ff9de8f0f1b06656c0d8275c0757] and get the detected charset. > 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, image-2018-07-13-11-28-16-657.png > > > 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)