ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@watson.ibm.com>
Subject Re: Character encodings
Date Mon, 06 Nov 2000 10:16:38 GMT
Hi Wada-san,

Do I understand correctly from your patch that you removed the UTF8
fixation from the code? That's the way it was originally I think, but
the UTF8 stuff was added because someone else pointed out it was 
broken without it for something else. I don't recall the details.

If this patch doesn't affect any of the other I18n situations that
we've come across so far I'd like to commit it. Can someone who's 
more I18n-aware than I am please check it out too? We really need
to identify at least one person who's keeping an eye on the code
(especially the v3 stuff) to make sure its I18n ok. Any volunteers?

Thanks,

Sanjiva.

----- Original Message ----- 
From: <wada@techno-infinitus.co.jp>
To: <soap-dev@xml.apache.org>; <mafoo@marcwell.se>
Sent: Sunday, November 05, 2000 3:07 AM
Subject: Re: Character encodings


> >> I am having trouble with character encodings in string parameters. I am 
> >> trying to return a string containing umlaut characters, for example a 
> >> char with code 214 is presented on the client side as two chars, 195 
> >> and 8211.
> 
> I had same trouble on japanese character and wrote a patch.
> this patch seems to works well for japanese character,and 
> and I think this may be effective for other non-ascii characters.
> 
> I hope this patch will help you.
> 
> ----------------------------
> Masatake Wada
> wada@techno-infinitus.co.jp
> ----------------------------
> 
> 


Mime
View raw message