[
https://issues.apache.org/jira/browse/TIKA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546231#comment-16546231
]
Sebastian Nagel commented on TIKA-2673:
---------------------------------------
Ok, this should set the declared encoding (after a look into
o.a.tika.parser.txt.Icu4jEncodingDetector). TIKA-431 deprecates the usage of
Metadata.CONTENT_ENCODING to hold the charset. After TIKA-974 is done one has
to parse the charset out from Metadata.CONTENT_TYPE. And thanks for evaluation
results, I'll plan to fetch the URLs again to reproduce the test as I need a
reliable charset detection as precondition for language detection.
> 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)
