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 form-encoding to utf-8
- set URIEncoding to utf-8
- and include a class like SetCharacterEncodingFilter to set request
character encoding
regards
Thomas
Am 29.09.2010 12:36, schrieb 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' -
http://www.fileformat.info/info/unicode/char/0635/index.htm) comes out
as it has been entered.
Does this mean that this (default) ISO-8859-1 container encoding does
cater for UTF-8 correctly? Otherwise, would you mind expanding on your
webapps/examples/WEB-INF/classes/filters/SetCharacterEncodingFilter.java
suggestion (I'm not much of a Java expert, either ;-))?
OTOH, I don't see any difference between cocoon running in either
Tomcat or the shipped Jetty.
Kind regards,
Ron
On 29/09/2010 12:11, Thomas Markus wrote:
thats right but you are bound to ISO-8895-1
we use UTF-8 in all stages with my comments.
regards
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org
