Further information that I could garner on this. I wrote a program to
read the Response header from the server and this is the result:
Message = GET http://www.sumpurn.com/com.sumpurn.web/index.html HTTP/1.0
HTTP/1.1 200 OK
Date: Mon, 14 Dec 2009 10:30:06 GMT
Server: Apache/2.0.63 (CentOS)
X-Cocoon-Version: 2.2.0-dev
Set-Cookie: JSESSIONID=07213F0EE92415A0E5B8B4D3BCDA0107;
Content-Length: 9665
Connection: close
Content-Type: text/html; charset=ISO-8859-1

Clearly, the charset is not getting set to UTF-8 in spite of settings that I
did in forrest.properties, web.xml forrest.xconf, sitemap.xmap (xml
serializer and html serializer).

  What settings I could be missing?

Best wishes

-----Original Message-----
From: Dr. Praveen Bhatia [mailto:praveen.bha...@sumpurn.com] 
Sent: Monday, December 14, 2009 5:59 PM
To: user@forrest.apache.org
Subject: UTF-8 setting for Japanese characters

   On my forrest 0.8 based website, I have done settings for UTF-8 to make a
Japanese website.
   On local tomcat and jetty, it works fine showing the Japanese characters
correctly. (My machines is Japanese Vista m/c)

   The problem is when it is uploaded on to the shared server (linux with
tomcat apache), the browser is not seeing them as UTF-8 encoded for display.
The correct UTF-8 Japanese characters can however be seen if the browser
encoding is chosen for EACH page to UTF-8 again and again. (The html file
generated is also having a meta data as follows:
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 So generation seems to be ok till here. 

   This behavior is observable on my forrest website www.sumpurn.com  (or
www.sumpurn.com/com.sumpurn.web/index.html) where we will first get garbled
data, but it would become OK if for EACH page the browser encoding is set to
UTF-8 (The characters are entirely in Japanese UTF-8 ....)

   I followed all the instructions given in forrest for UTF-8 and the
instructions given in cocoon website
http://cocoon.apache.org/2.2/1366_1_1.html#theory for UTF-8. However, I am
yet unable to make it work. My gut feeling is that apache server's http
header is sending non-UTF encoding to the browser, and that needs to be set
via forrest/cocoon/apache tomcat.

  Could someone please guide me as to what other settings are required to be

Best wishes