Sorry, the stuff in CVS needs more work wrt entities; I just haven't had
time lately. The server should be returning numerical entities instead
of XHTML entities, which is on my TODO list.
On Thu, 2003-05-29 at 02:23, Jeff Barr wrote:
> I am testing out this code and there are still some issues. My server
> is trying to return a string containing the folllowing encoded characters:
> If any of these characters are present in the returned string then
> the client (also using PHP XML-RPC) dies like this:
> XML error: undefined entity at line 10
> The characters appear to be properly encoded in the XML. Here's
> some debug output from the client:
> As an experiment, I stripped these characters out on the client
> side in xmlrpcmsg::parseResponse and I didn't get the undefined
> entity error.
> I believe that the server should insert entity declarations for
> these characters. Is this correct?
> ----- Original Message -----
> From: "Andres Salomon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 17, 2003 2:11 AM
> Subject: [phpxmlrpc] entity changes
> > Folks, I just committed some changes that address some longstanding issues
> > w/ this xmlrpc implementation, and multibyte characters from various
> > charsets. I'll be testing these changes some more this week, but if
> > anyone has dealt w/ entity issues in xml or xmlrpc, or has experience w/
> > another xmlrpc library, please look over the changes (see the ChangeLog
> > for additional details). The things that need addressing are:
> > a) does xmlrpcresp need to be fixed in a similar way?
> > b) should entity translation be done on the server or client? Are xmlrpc
> > servers expected to know how to handle things like é (or even
> > é)?
> > c) are there any entities that might be missing?
> > _______________________________________________
> > phpxmlrpc mailing list
> > [EMAIL PROTECTED]
> > http://lists.usefulinc.com/cgi-bin/mailman/listinfo/phpxmlrpc
> phpxmlrpc mailing list
> [EMAIL PROTECTED]
phpxmlrpc mailing list