The problem seems to be the webservice. In the context of the
webserver, the XML document is able to read out the encoding
correctly. But if a client gets the XML document through a web service
call, the XML document does not contain any correct special
characters. What must be done to solve my problem?
Martin Honnen - 24 Jan 2008 14:35 GMT
> The problem seems to be the webservice. In the context of the
> webserver, the XML document is able to read out the encoding
> correctly. But if a client gets the XML document through a web service
> call, the XML document does not contain any correct special
> characters. What must be done to solve my problem?
I have never understood why you need a web service if you want to return
an XML document. Consider to simply use a HTTP handler on the server
which returns the XML document as needed.
As for the web service problem, there is
microsoft.public.dotnet.framework.aspnet.webservices.

Signature
Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
Andy Fish - 24 Jan 2008 16:44 GMT
i would guess that your problem is to do with the HTTP encoding. Probably
your web service is sending a HTTP header specifying UTF-8 encoding (which
obviously doesn't match up with the XML document)
you might need to use a network monitor like ethereal to figure out what is
actually going over the wire
FWIW with my current application, we use utf-8 wherever possible (certainly
for all XML files and HTTP traffic) because it minimises these sort of
issues
Andy
> The problem seems to be the webservice. In the context of the
> webserver, the XML document is able to read out the encoding
> correctly. But if a client gets the XML document through a web service
> call, the XML document does not contain any correct special
> characters. What must be done to solve my problem?