[
https://issues.apache.org/jira/browse/NUTCH-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated NUTCH-910:
------------------------------------
Fix Version/s: (was: 1.0.0)
unset fix version -- 1.0.0 has already been released and therefore can't have
any open issues.
We *may* potentially roll a Nutch 1.3 that this could fit into (honestly I
would call it Nutch 1.2.1 as I don't think there's much 1.x dev going on, or
folks willing to maintain it) but until that time I'm leaving it as unset.
> Cached.jsp has a bug with encoding
> ----------------------------------
>
> Key: NUTCH-910
> URL: https://issues.apache.org/jira/browse/NUTCH-910
> Project: Nutch
> Issue Type: Bug
> Components: web gui
> Affects Versions: 1.0.0
> Environment: Any enironment
> Reporter: Attila Pados
> Priority: Minor
> Original Estimate: 0.03h
> Remaining Estimate: 0.03h
>
> cached.jsp
> Pages that has a non default encoding, or not utf-8 etc, the cached content
> is displayed screwed. This is quite annoying, but doesn't harm critically
> functionality.
> add : Metadata parseData = bean.getParseData(details).getParseMeta();
> original : Metadata metaData = bean.getParseData(details).getContentMeta();
> replace: String encoding = (String)
> parseData.get("CharEncodingForConversion");
> In the cached jsp, the encoding variable is tried to retrieved from the wrong
> metadata source, contentMeta, which doesn't include this value.
> It resides in the parseMetadata instead.
> First line is not a replacement above, it has to be added. Original metadata
> is needed there for other things.
> Then below, the encoding value line has to be changed, that is a replacement.
> This fix is for 1.0 nutch version, i didn't found an issue in the list that
> would cover this, just a mail found with google, on a mailing list that
> refered to it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
