Please tell us what database are you using? And what encoding the database is?

This looks like a conflict between the database encoding and the application.

Antonio Gallardo.

El Miércoles, 18 de Septiembre de 2002 08:41, Kenneth Roper escribió:
> 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?
>
> Thanks again.
> Kenneth
>
>
> ---------------------------------------------------------------------
> 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]>

---------------------------------------------------------------------
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]>

Reply via email to