[NUTCH-1558] CharEncodingForConversion in ParseData's ParseMeta, not in ParseData's ContentMeta

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 1.8
• Component/s: parser
• Patch Info: Patch Available
• Assignee: Chris A. Mattmann
• Reporter: Chris A. Mattmann
• Created: 17/Apr/13 14:16
• Updated: 13/Mar/24 14:51
• Resolved: 15/Nov/13 17:56

Description

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