christian bindeballe wrote:
[...]
also, Marc Portier wrote: (see this thread, message-ID
<[EMAIL PROTECTED]>)
never change your container-encoding unless you have a servlet container
of which you can specify the used encoding applied in decoding of url's
and request parameters
[...]
Hi Christian,
what I've been writing about is not container-encoding. I was writing
about character encoding of the documents and about HTTP response header.
And to make even more confusion, there is also form-encoding,
url-encoding, document-encoding, transmission encoding, ...
As you are going to supply something for web browsers through HTTP, the
browsers will need something like
"Content-Type: text/html;charset=utf-8 "
in the HTTP response header. And this is given by the *second* line in
following serializer configuration:
<map:serializer name="xhtml"
mime-type="test/html; charset=utf-8"
logger="sitemap.serializer.xhtml"
pool-grow="2" pool-max="64" pool-min="2"
src="org.apache.cocoon.components.serializers.XHTMLSerializer">
<encoding>UTF-8</encoding>
<indent>no</indent>
</map:serializer>
Best way to test is from a very minimalistic sample application with
just this serializer configuration and a short pipeline with only
<map:sitemap>
<map:components>
<map:serializers default="xml">
<map:serializer name="xhtml"
mime-type="test/html; charset=utf-8"
logger="sitemap.serializer.xhtml"
pool-grow="2" pool-max="64" pool-min="2"
src="org.apache.cocoon.components.serializers.XHTMLSerializer">
<encoding>UTF-8</encoding>
<indent>no</indent>
</map:serializer>
</map:serializers>
</map:components>
<map:pipelines>
<map:pipeline>
<map:match pattern="netzpolitik">
<map:generate src="http://www.netzpolitik.org/feed"/>
<map:serialize/>
</map:match>
</map:pipeline>
</map:pipelines>
</map:sitemap>
Try this sample and play with "mime-type" and <encoding> and watch your
output.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
