AFAIK this is a feature, not a bug. It standardizes output as UTF8, which should be able to represent any character data.
On Wed, Jul 21, 2010 at 12:36 PM, Gagandeep Singh (JIRA) <j...@apache.org>wrote: > MutableContent causing lossy content encoding > --------------------------------------------- > > Key: SHINDIG-1395 > URL: https://issues.apache.org/jira/browse/SHINDIG-1395 > Project: Shindig > Issue Type: Bug > Components: Java > Reporter: Gagandeep Singh > Assignee: Gagandeep Singh > Priority: Critical > > > MutableContent.getRawContentBytes and MutableContent.getContent are buggy > because they serialize the Document into a utf8 string disregarding the > original encoding of the page that is known to the HttpResponse object. > > Here is how it goes wrong for accel servlet: > > AccelServlet.doFetch -> > DefaulltResponseRewriterRegistry.rewriteHttpResponse -> > HttpResponseBUilder.create -> > new HttpResponse -> > HttpResponseBuilder.getResponse -> > MutableContent.getRawContentBytes() > > NOTE: This could also be problem with gadgets. Need to verify. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
