Thank you, Ard
I already did that. But it doesn't change anything. I found this in my
web.xml in the WEB-INF folder of my cocoon-build:
<!--
Set encoding used by the container. If not set the ISO-8859-1 encoding
will be assumed.
Since the servlet specification requires that the ISO-8859-1 encoding
is used (by default), you should never change this value unless
you have a buggy servlet container.
-->
<init-param>
<param-name>container-encoding</param-name>
<param-value>ISO-8859-1</param-value>
</init-param>
Servlet-Container used is Tomcat 5.0.28
I switched the encoding parameter to UTF-8 to check whether it would
work, and it seems to. But still the coplets aren't encoded properly.
Then I saw that the whole page is encoded in ISO-8859-1, having been
serialized in HTML (as seen in the doctype of the page). So I looked
for the HTML-Serializer in my portal/sitemap.xmap and changed the
encoding of the html-serializer, too. no difference
these are the feed-adresses that I want to incorporate. both don't
have an encoding set (do RSS-feeds have to have that?) but they
clearly contain UTF-8 encoded characters.
http://www.industrial-technology-and-witchcraft.de/index.php/ITW/itw-rss20/
http://www.netzpolitik.org/feed/
so, I guess that somewhere along the line from generating to
serializing these feeds are messed with in a way that the encoding set
in the serializers has no effect whatsoever.
suggestions as to where this could be, anyone?
it would be greatly appreciated :)
regards, christian
2006/1/16, Ard Schrijvers <[EMAIL PROTECTED]>:
> Think you should have no problem at all when you just serialize everything as
> utf-8:
>
> <map:serializer logger="sitemap.serializer.xml" mime-type="text/xml"
> name="xml" pool-grow="4" pool-max="32" pool-min="4"
> src="org.apache.cocoon.serialization.XMLSerializer">
> <encoding>UTF-8</encoding>
> </map:serializer>
>
> AS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
