You can detect the encoding using the icu4j utility. This is something already done in the gadgets server. See oHttpResponse.detectEncoding
On Fri, Aug 1, 2008 at 4:50 AM, Jacky Wang (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/SHINDIG-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Jacky Wang updated SHINDIG-487: > ------------------------------- > > Attachment: fix-socialapi-post-unicode-bug.patch > > Parses the request according to its charset. > Sets response's charset to "UTF-8". > > > > Fix encoding bugs > > ----------------- > > > > Key: SHINDIG-487 > > URL: https://issues.apache.org/jira/browse/SHINDIG-487 > > Project: Shindig > > Issue Type: Bug > > Components: RESTful API (Java) > > Environment: Windows XP, China as region, Chinese as prefer > language > > Reporter: Jacky Wang > > Attachments: fix-socialapi-post-unicode-bug.patch > > > > Original Estimate: 0.25h > > Remaining Estimate: 0.25h > > > > For the input requests, we can't pre-determine its character encoding, > thus we need to parse the input according to HttpServletRequest. > > If the HttpServletRequest doesn't have this header, we'll use "UTF-8" as > default value. > > For all outbound response, since they're under Shindig's control, we'll > set their CharacterEncoding to "UTF-8". > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
