Hi,
I'm stumbling on a character encoding issue (cocoon-2.1.10) and really
can't see why. Apparently, text input in a form is passed on in a wrong
encoding. I've set Cocoon's default encoding in all thinkable places as
UTF-8:
web.xml:
servlet
servlet-nameCocoon/servlet-name
!-- ..
direction.
Cheers,
Robby Pelssers
-Oorspronkelijk bericht-
Van: Ron Van den Branden [mailto:ron.vandenbran...@kantl.be]
Verzonden: wo 29-9-2010 11:11
Aan: users@cocoon.apache.org
Onderwerp: form encoding issues
Hi,
I'm stumbling on a character encoding issue (cocoon-2.1.10) and really
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
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
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
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:
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' -
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?)
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
-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
-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
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
12 matches
Mail list logo