[
https://issues.apache.org/jira/browse/TIKA-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-2673.
-------------------------------
Resolution: Fixed
Assignee: Tim Allison
Fix Version/s: 2.0.0
1.19
[~gbouchar], many, many thanks for this fantastic work!
I made the decision to remove the FullStandardEncodingDetector and the
StandardICU4JEncodingDetector because we try to keep encoding detectors
composable. I was actually wondering if we should pull out the BOM detection
into a separate detector, but let's leave it as is for now.
Please do check that I got the updates right in both master and branch_1x
(which we'll use for Tika 1.19).
Again, many, many thanks!
> 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
> Assignee: Tim Allison
> Priority: Major
> Fix For: 1.19, 2.0.0
>
> 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)
