I recently responded to a question on this mailing list with a subject of "ESQL and utf-8 encoding". The following is from that response:
"We experienced a similar problem with the character encoding on the http request processed by Cocoon. We also were attempting to use UTF-8 encoding but found that the encoding would always default to ISO-8859-1. Looking at the request in a debugger, we found that the actual http request wrapped by the Cocoon HttpRequest did not have the character encoding properly set. We corrected this by modifying CocoonServlet to set the character encoding on the wrapped request to the form-encoding value specified in the web.xml. In order to set the character encoding, we needed to use the 2.3 version of the servlet jar. This solved our encoding problems for page display and for request parameter interpretation." I haven't dealt with the URLEncode Transformer - in our application we were specifically dealing request parameters and page display of various languages. However, maybe the explanation above will provide a new basis of thought for you and give you something to at least experiment with. One additional point - with the tweaks above, I now have both the container-encoding and form-encoding parameter values set to UTF-8. Good luck. Theresa Dominique Galland wrote: >I have carefully read the Wiki >http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlight &value=container-encoding <http://wiki.apache.org/cocoon/RequestParameterEncoding?action=highlight &value=container-encoding> >but I have still a problem with parameter encoding >Pages are serialized in UTF-8 >URL are encoded with the URLEncode Transformer >Tomcat container-encoding is ISO-8859-1 >Tomcat form-encoding is UTF-8 >It works well for form parameters but not for encoded URL's that contains non ASCII Characters in their parameters >Those URL are correctly displayed by the browser but on submit the parameters decoding fails. >If I change Tomcat container-encoding to UTF-8 (just for trying) it works with the URL's but not for the form parameters >I dont understand the difference and how I can specify and encoding which works in both cases. >Does someone have an idea. ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
