[ 
https://issues.apache.org/jira/browse/TIKA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041233#comment-17041233
 ] 

Tim Allison commented on TIKA-3048:
-----------------------------------

On the file you shared with us, I still got garbage with the 
UniversalEncodingDetector and the Icu4jEncodingDetector.

I got "在一天中一个漆黑的夜晚,有两只死了的牡蛎出来玩� � 们背对背面对对方�" when I told the charset detector 
to "just use UTF8" with this:

{noformat}
<properties>
    <!-- Explicitly request default parsers -->
    <parsers/>
    <encodingDetectors>
        <encodingDetector 
class="org.apache.tika.detect.NonDetectingEncodingDetector">
            <params>
                <param name="charset" type="string">UTF-8</param>
            </params>
        </encodingDetector>
    </encodingDetectors>
</properties>
{noformat}

> Tika unable to parse html files with non UTF-8 charset
> ------------------------------------------------------
>
>                 Key: TIKA-3048
>                 URL: https://issues.apache.org/jira/browse/TIKA-3048
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.9
>            Reporter: Akash
>            Priority: Major
>         Attachments: ChineseFile.html
>
>
> Tika is returning junk characters when parsing chinese characters present 
> inside html file. Html file have charset mentioned as GB2312 explicitly.
> <head><meta http-equiv=Content-Type content="text/html; charset=gb2312"><meta 
> name=Generator content="Microsoft Word 15 (filtered medium)">
>  
> If we remove this charset from the html meta tag, then parsing works fine.
>  
> Similar issue is observed for Arabic, Russain, Korean, Japanese, Hungarian 
> and Spanish languages.
> Charset mentioned for each languages - 
> Hungarian - iso-8859-1
> Chinese - gb2312
> Spanish - iso-8859-1
> Russian - koi8-r
> Korean - ks_c_5601-1987
> Japanese - iso-2022-jp
> Arabic - windows-1256



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to