Tim Allison commented on TIKA-2592:

bq. Do you have a testcorpus or are you crawling the web Tim Allison?
We have 1 TB of govdocs1 and a slice of CommonCrawl (oversampled for binaries) 
hosted by Rackspace (thank you, Rackspace!!!).


We use it to run regression tests with the {{tika-eval}} module before releases.

If it would help you to help us, I'll be happy to give you access to the vm. :D

> HTML with charset unicode handled as utf-16 instead utf-8
> ---------------------------------------------------------
>                 Key: TIKA-2592
>                 URL: https://issues.apache.org/jira/browse/TIKA-2592
>             Project: Tika
>          Issue Type: Bug
>    Affects Versions: 2.0, 1.16, 1.17
>            Reporter: Andreas Meier
>            Priority: Major
>         Attachments: TestCharsetUnicodeHTML.html, 
> TestHTMLCharsetArabicCP1256.html, TestHTMLCharsetCP1256.html, 
> fix-for-TIKA2592-contributed-by-Andreas-Meier.patch
> HTML files are detected as utf-16 when meta content is set to "unicode".
> {code:XML}
> <meta http-equiv="Content-Type" content="text/html; charset="unicode">
>  {code}
> Shouldn't the default be utf-8?
> The attached sample file is shown correctly in:
> Chromium Version 55.0.2883.75
> Firefox 50.1.0
> IE 11
> I am aware that there is no charset "unicode" (available character encodings: 
> [http://www.iana.org/assignments/character-sets/character-sets.xhtml|http://www.iana.org/assignments/character-sets/character-sets.xhtml])
> Unfortunately there are many wrong encodings used out there.
> All unknown encodings should be validated or at least be set to default utf-8.
> Regards 
> Andreas

This message was sent by Atlassian JIRA

Reply via email to