Use set-encoding action in your pipeline:
<map:pipeline> <map:act type="set-encoding"> <map:parameter name="form-encoding" value="utf-8"/> </map:act> .... </map:pipeline>
OK, I got it working now. Thank you for your hints!
For the small example: I had to add "<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>" to the form generating pipe, so the HTML page was interpreted as UTF-8. Only then the browser would send form data also as UTF-8!
That's what browsers are expected to do.
Instead of that META-hack you'd better use a correct HTTP header. Configure your serializer with mime-type like:
<map:serializer name="html"
mime-type="text/html; charset=utf-8"
logger="sitemap.serializer.html"
pool-grow="2" pool-max="64" pool-min="2"
src="org.apache.cocoon.serialization.XMLSerializer">
<doctype-public>-//W3C//DTD XHTML 1.0 Strict//EN
</doctype-public>
<doctype-system>http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
</doctype-system>
<omit-xml-declaration>yes</omit-xml-declaration>
<omit-namespaces>yes</omit-namespaces>
<encoding>UTF-8</encoding>
</map:serializer>UTF-8 in mime-type will put the charset information into HTTP header, and <encoding/> will take care of the correct file encoding.
The <omit-xml-declaration/> will make MSIE to use its standards compliance rendering mode.
I'm using to generally change _every_ serializer to use utf-8 only for easier standardisation.
-- Volkmar W. Pogatzki
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
