[ http://issues.apache.org/jira/browse/TOMAHAWK-620?page=comments#action_12453643 ] Jocelyn Carfantan commented on TOMAHAWK-620: --------------------------------------------
The problem seems that if not using UTF-8 as character-encoding, the javascript 'text' is encoded like the html one. But the JavaScript don't use the same convention for character 'decoding'. e.g. for character 'รด' in ISO-8859-1 the encoding for HTML will be 'ô' but for javascript it's '\u00F4'. I think that HtmlResponseWriterImpl (or DefaultAddResource) must dissociate the HTML code from Javascript code when encoding. > Inline JavaScript does not get the same character encoding as the page > ---------------------------------------------------------------------- > > Key: TOMAHAWK-620 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-620 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: ExtensionsFilter > Affects Versions: 1.1.3 > Environment: Windows 2000, Tomcat 5.5 > Reporter: Mikael Skogstrom > > The change TOMAHAWK-282 addressed a problem where inline JavaScript wasn't > encoded with the current character encoding. The correction was present in > version 1.1.2. But the code is heavily reorganized in version 1.1.3 and the > correction seems to have been purged in the process. > The bug displays itself in JavaScript alert boxes, where foreign characters > are represented with their encoding number instead of the actual character. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
