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] [Commented] (NUTCH-1558) CharEncodingForConversion in
ParseData's ParseMeta, not in ParseData's ContentMeta
[ https://issues.apache.org/jira/browse/NUTCH-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634068#comment-13634068 ]
Chris A. Mattmann commented on NUTCH-1558:
------------------------------------------
Patch is available at the attached link referenced. This is part 1 of the patch. If there are no objections in 48 hours, I will commit this to trunk with credit to Github user ysc.
> 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