Tim Allison commented on TIKA-2592:

{quote}I already have a small testset I run tika against (~300k+ files), that 
is also the reason for the numerous tickets I created lately.
Great, and thank you!
{quote}Too many people and nightly builds stressing one vm may be too much.
As long as you aren't active during release cycles, we won't stress is much. :D


Finally, if you want to get involved with the tika-eval module and/or if you 
have any code you've found helpful in evaluating different runs or single runs, 
let us know! 

> 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: Improvement
>    Affects Versions: 2.0, 1.16, 1.17
>            Reporter: Andreas Meier
>            Priority: Minor
>             Fix For: 1.18, 2.0.0
>         Attachments: IANA Charset names.txt, 
> StandardCharsets_unsupported_by_IANA.txt, 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