Re: encoding problem

Hi Marc,

on which configuration did you test kSOAP? WTK? ME4SE? An actual phone /=20
Emulator? If so, which one?

Is an <?xml version=3D"1.0" encoding=3D"????"?> String included in the SO=
AP message?=20
Can you verify how exactly the Umlauts are encoded in the message? Someti=
mes the=20
declared and actual encoding do not match... :( also, &auml; etc. will no=
t work=20
because it is HTML-Specific----

Best regards
Stefan


Marc Logemann wrote:

> THe point is, my J2SE test client is working perfectly and displays eve=
rything correct. My
> kSoap client gives back garbage for chars like =F6 or =E4 (german speci=
al chars).
>=20
> i read the archives and found the UTF8 method parm for the streams in H=
ttpTransport, but even when adding
> them, the result is the same (everything else would be crazy anyway).
>=20
> I must admint encoding is my weakest area, so i have these questions:
>=20
> 1. Do i have to decode the string on webservice side with getBytes("UTF=
8") ? Done that and got
> even more crazy stuff back.

No. Setting the "utf-8" param for HttpTransport should be sufficient.

> 2. Why must i do anything at all? If server and client understand UTF8?

A