You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2013/04/17 16:17:15 UTC

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

Chris A. Mattmann created NUTCH-1558:
----------------------------------------

             Summary: 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.7


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira