[jira] [Resolved] (NUTCH-1558) CharEncodingForConversion in ParseData's ParseMeta, not in ParseData's ContentMeta

[Julien Nioche (JIRA)]

     [ 
https://issues.apache.org/jira/browse/NUTCH-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien Nioche resolved NUTCH-1558.
----------------------------------

    Resolution: Won't Fix

see comments

> CharEncodingForConversion in ParseData's ParseMeta, not in ParseData's 
> ContentMeta
> ----------------------------------------------------------------------------------
>
>                 Key: NUTCH-1558
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1558
>             Project: Nutch
>          Issue Type: Bug
>          Components: parser
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 1.8
>
>
> This patch from GitHub user ysc fixes two bugs related to character encoding:
> * CharEncodingForConversion in ParseData's ParseMeta, not in ParseData's 
> ContentMeta
> * if http response Header Content-Type return wrong coding，then get coding 
> from the original content of the page
> Information about this pull request is here: http://s.apache.org/VOP



--
This message was sent by Atlassian JIRA
(v6.1#6144)