Leszek Gawron wrote:
Gregor J. Rothfuss wrote:
Leszek Gawron wrote:
Berin Loritsch wrote:
In order to set encoding standards for your mime-type you have to
include the character-encoding after the mime-type. Ex:
text/html;encoding=utf-8
You probably mean 'charset' parameter [1].
Without the encoding clue, most browsers assume whatever is the default
for that browser. In the U.S. it is typically iso-8859-latin. This
bit
us yesterday as we had to make that change to support special
characters
again--this time with Cocoon.
What do you propose?
<map:serializer name="text"
src="org.apache.cocoon.serialization.TextSerializer"
mime-type="text/plain" logger="sitemap.serializer.text">
<encoding>utf-8</encoding>
</map:serializer>
+1 for adding ;charset=utf-8.
Vadim
[1] http://www.rfc-editor.org/rfc/rfc2854.txt
