[
https://issues.apache.org/jira/browse/NUTCH-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634183#comment-13634183
]
Ken Krugler commented on NUTCH-1558:
------------------------------------
I don't see the patch, but the HTML parsing support in Tika has similar support
for dealing with ambiguous charset identification/detection - is there any way
to leverage that?
> 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
