Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm
Message-Id: <200011210644.GAA08714@gnkhelp308.greenock.uk.ibm.com>
From: "Wouter Cloetens" <wcloeten@raleigh.ibm.com>
To: "soap-dev@xml.apache.org" <soap-dev@xml.apache.org>
Date: Tue, 21 Nov 2000 00:44:53 +0500
Reply-To: "Wouter Cloetens" <wcloeten@raleigh.ibm.com>
Priority: Normal
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: Character encodings

FYI, my proposed MIME attachment change has full, tested, support for a wide range of 
MIME-supported character sets, both on the client and the server side. It will default to 
UTF-8 on both ends, but will understand other encoding (iso-latin-x, dbcs etc) charsets.

You're right, it's important, I've been whining about the same thing for ages. ;-)

bfn, Wouter

On Tue, 21 Nov 2000 12:42:11 +0900, Masatake Wada wrote:

>I rewrote the non-ascii character patch for current CVS.
>
>It seems everyone have forgotten about i18n...but I think
>it is important.
>
>Regards,
>
>Masatake Wada
>wada@techno-infinitus.co.jp

--
http://www.workspot.net/~zombie/soap/
My opinions are irrelevant. They will be assimilated by my employer.