After deep searching I found that all information were on the mail list,
but very distributed.
I think that the subject 'International characters in Tomcat/Cocoon'
would be good to describe in FAQ (is very common question).
Maybe the content below can be good startup point.
How to setup Tomcat/Cocoon/Java to support fully Unicode (UTF-8)?
1. Problem - unicode characters in xsp/etc code.
add file.encoding to your JVM (for IBM -Dfile.encoding=UTF-8)
2. Problem - request parameters (for xsp/xsl/etc.):
a) use always
<xsp-request:get-parameter name="yourparamname" form-encoding="UTF-8"
container-encoding="UTF-8"/>
b) add filter to web.xml
below is a part of mail "RE: Tomcat and Unicode parameters in URLs ???"
From: Larry Isaacs
>>>>
In order to deal with request parameters in an incoming request, you must
tell Tomcat what encoding to use, *before* processing the parameters.
This is done by calling the request.setCharacterEncoding() method that was
added in Servlet 2.3. As long as you call this before calling methods
like request.getParameter(), the proper encoding will be applied.
One way to do this without modifying your application itself is to use a
Filter that looks at incoming requests and decides what encoding should be
used -- perhaps by looking at the <code>Accept-Language</code> header, or
based on attributes you have stored in the current session that indicate
what the user will be supplying. A very simple example of such a filter
is included in the "/examples" webapp shipped with Tomcat 4 -- the source
code for this filter is in file SetCharacterEncodingFilter.java in the
$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters subdirectory.
This example is fairly simpleminded -- you just configure a filter
initialization parameter that is used to set the encoding for all requests
-- but you can use it as a starting point for more sophisticated
processing by subclassing it and overriding the selectEncoding() method.
This filter can be enabled by copying the appropriate class file to your
own WEB-INF/classes directory, and adding a filter definition to your
web.xml file:
<filter>
<filter-name>Character Encoding Filter</filter-name>
<filter-class>filters.SetCharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
</filter>
Then, you select which requests this filter applies to with a filter
mapping -- the "/*" pattern says apply it to *all* requests:
<filter-mapping>
<filter-name>Character Encoding Filter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
With filter mappings like this, you can be more selective about which URLs
it applies to by using a more precise URL pattern, or apply different
filters to different URLs -- all without affecting your servlets or JSP
apges at all. The syntax for the <url-pattern> element in a filter
mapping is the same as that used for a servlet mapping.
Be sure to put these elements in the correct places in your web.xml file
to maintain the element order that is required by the DTD.
>>>>>
I'm sure that it can be done simpler/better. Probably there are still
some other problems which I didn't find. Post comments, ideas.
Tomasz
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
