On Mon, Jan 19, 2004 at 09:19:25PM -0800, Adam Megacz wrote: > > "Daniel L. Rall" <[EMAIL PROTECTED]> writes: > > Here's a patch to > > add that ability back in for Unicode encodings, encodings which I > > believe XML parsers are required to support by the XML specification. > > There are quite a few XML-RPC endpoints that don't use "real" XML > parsers.
Then they're not proper XML-RPC endpoints -- the spec indicates the data is transmitted as XML, and this is a basic part of the spec. Dave finally got around to taking out the claim that strings should only be ASCII (which would be pretty absurd in the face of the XML RFCs): http://www.xmlrpc.com/spec Look for the update at the bottom (2003/06/30). Anyway, the patch was designed to allow it to maintain the existing behavior, if the encoding is set to ISO-8859-1 (well, actually it'll just transform the multibyte characters to question marks, but I fail to see how that's worse than failing outright). The current behavior allows for bytes with the high bit set, which isn't correct XML, but I imagine it'd generally work despite that; this allows either that approach or one where the encoding for the strings is something like UTF-8. We use XML-RPC for data which includes characters from other languages; and I don't see the point in base64 encoding and decoding all our textual data when XML provides a convenient way to transmit it. cheers -- Ed -- +=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-= | Ed Korthof | [EMAIL PROTECTED] | 650-228-2527 | +=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=
