Kenneth Roper wrote:
> Firstly, thanks for everyone's suggestions, this is a very helpful list!
>
> Unfortunately, I am no further forward.
>
> Changing the encoding of the sitemap.xmap and the web.xml file has no
> effect.
>
> Changing the encoding of the xhtml serializer looked like I was on the
> right track, but unfortunately doesn't work:
>
> I have a this string in my db:
>
> "ÄäÖöÜüß"
>
> It is displayed on an html page generated by a cocoon pipeline.
>
> If I change my serializer definition in my sitemap and add this:
> <encoding>ISO-8859-1</encoding>
> The above string appears in my browser (and in the page source) as 7
> question marks, i.e. "???????"
>
> If I change the encoding back to this:
> <encoding>UTF-8</encoding>
> I can then see my original string correctly. However, if I post this
> string back to my application, my application receives the string as
> first detailed in the original post (i.e. "ÄäÖöÜüß").
>
> There is obviously a difference in encoding (or something) between text
> coming from the server to the browser, and the text posted from the
> browser back to the server.
>
> Any more ideas?
So it looks like the string is in UTF-8. In this case, you should make
sure everything is working in UTF-8. Use request.setEncoding("UTF-8") in
your action/generator/XSP, delete any encoding attribute from the XML
prolog in XML files (UTF-8 is the default) and see if it makes any
difference.
I have no other ideas, but to confirm you that i18n is a PITA ;-)
Ugo
--
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
