Hi, We wrote a Web service to put some information from forms on our
Web site into a SQL database. It works great. The only problem is that
when Germans visit our site and enter a name like "Dürkheim," the entry
shows up in our SQL table as "Drkheim."
I've verified that SQL (on the back end) and Apache/PERL (on the front end)
all support the extended ASCII characters. That leaves the C# web service
(or the interaction between it and the PERL script running on FreeBSD).
As you can see from the capture of the conversation between PERL/FreeBSD and
C#/IIS below, the "ü" shows up on the wire as 0xfc. Does anyone know
whether C# (Windows 2000) should deal correctly with that encoding, or how
to fix the problem? We are using SOAP::Lite on the PERL side.
Thanks,
BGU
0x0380 7269 6e67 222f 3e3c 4669 7273 745f 4e61 ring"/><First_Na
0x0390 6d65 2078 7369 3a74 7970 653d 2278 7364 me.xsi:type="xsd
0x03a0 3a73 7472 696e 6722 3e4a 6f65 fc3c 2f46 :string">Joeü</F
0x03b0 6972 7374 5f4e 616d 653e 3c46 6f72 6d5f irst_Name><Form_
BGU - 07 Nov 2005 19:49 GMT
I found a solution here,
http://cookbook.soaplite.com/
in the "Internationalization and encoding" section.
FYI,
BGU
> Hi, We wrote a Web service to put some information from forms on
> our Web site into a SQL database. It works great. The only problem is
[quoted text clipped - 18 lines]
> 0x03a0 3a73 7472 696e 6722 3e4a 6f65 fc3c 2f46 :string">Joeü</F
> 0x03b0 6972 7374 5f4e 616d 653e 3c46 6f72 6d5f irst_Name><Form_