RE: form encoding issues

2010-09-29 Thread Robby Pelssers
Not sure as for how to do this with Cocoon2.1.x but with Cocoon2.2 you need to set following properties in the META-INF/cocoon.properties - org.apache.cocoon.containerencoding=utf-8 org.apache.cocoon.formencoding=utf-8 Hope this gets you looking in the right

Re: form encoding issues

2010-09-29 Thread Thomas Markus
Hi, check out request character encoding. For tomcat look at http://confluence.atlassian.com/display/DOC/Configuring+Tomcat%27s+URI+encoding and in your tomcat installation at webapps/examples/WEB-INF/classes/filters/SetCharacterEncodingFilter.java that worked for me regards Thomas Am

Re: form encoding issues

2010-09-29 Thread Ron Van den Branden
Hi again, Thank you very much for the quick help; meanwhile I think I found an answer in a post on cocoon-dev: http://markmail.org/message/nm6bnvqztbee4s5o. There is stated that apparently (and counter-intuitively, IMO), 'request parameters are always decoded using ISO-8859-1 ', and that

Re: form encoding issues

2010-09-29 Thread Andre Juffer
On 09/29/2010 12:43 PM, Ron Van den Branden wrote: Hi again, Thank you very much for the quick help; meanwhile I think I found an answer in a post on cocoon-dev: http://markmail.org/message/nm6bnvqztbee4s5o. There is stated that apparently (and counter-intuitively, IMO), 'request parameters

Re: form encoding issues

2010-09-29 Thread Thomas Markus
thats right but you are bound to ISO-8895-1 we use UTF-8 in all stages with my comments. regards Thomas Am 29.09.2010 11:43, schrieb Ron Van den Branden: Hi again, Thank you very much for the quick help; meanwhile I think I found an answer in a post on cocoon-dev:

Re: form encoding issues

2010-09-29 Thread Ron Van den Branden
Hi Thomas, I'm not much of an expert in encoding matters, and could indeed be happy with ISO-8859-1 instead of UTF-8. However, testing with ISO-8859-1 set as container-encoding, even Arabic input is passed through correctly: ص (Arabic letter 'sad' -

Re: form encoding issues

2010-09-29 Thread Ron Van den Branden
Hi Andre, On 29/09/2010 12:01, Andre Juffer wrote: Actually, Tomcat does, but Jetty does not (by default, UTF8). According to specification, servlet engine are suppose to decode using ISO-8859-1 by default. I don't see any difference between both. And lo: changing the (over-eager?)

Re: form encoding issues

2010-09-29 Thread Thomas Markus
hi, that arabic character should fail with latin1. we see a difference between jetty and tomcat (6.0). tomcat follows specs (see Andre's mail) and uses iso per default. you can switch completely to UTF-8 with: - send html content in utf-8 - set container-encoding to utf-8 - set

Re: form encoding issues

2010-09-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron, On 9/29/2010 5:43 AM, Ron Van den Branden wrote: There is stated that apparently (and counter-intuitively, IMO), 'request parameters are always decoded using ISO-8859-1 ', and that consequently 'container_encoding should always be

Re: form encoding issues

2010-09-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, On 9/29/2010 7:05 AM, Thomas Markus wrote: hi, that arabic character should fail with latin1. we see a difference between jetty and tomcat (6.0). tomcat follows specs (see Andre's mail) and uses iso per default. you can switch

Re: form encoding issues

2010-09-29 Thread Barbara Slupik
Hello I followed the instruction here http://cocoon.apache.org/2.2/1366_1_1.html . For cocoon-2.1.11 I set init-param param-namecontainer-encoding/param-name param-valueUTF-8/param-value /init-param init-param param-nameform-encoding/param-name