On 24 Jan 2008, at 10:53, Jochen Wiedmann (JIRA) wrote:
[ https://issues.apache.org/jira/browse/XMLRPC-152?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=12562013#action_12562013 ]
Jochen Wiedmann commented on XMLRPC-152:
----------------------------------------
I do not consider this a bug.
The encoding parameter was never intended to affect parsing the
servers response. The server must certainly be free to choose his
own encoding.
My impression is that you have a quite different problem: I would
assume that the server produces invalid XML.
The XML spec does talk about the case in which the consumer has
information about the encoding of the document other than that in the
XML declaration. See http://www.w3.org/TR/REC-xml/#sec-guessing-with-
ext-info (Note this is non Normative, though).
This is why the designers of the SAX API provided for the user to
make the parser use a specific encoding. In this case it is not an
error if the document has an XML declaration with a different
encoding specified (the declaration encoding is ignored) See http://
www.w3.org/TR/REC-xml/#NT-EncodingDecl (which is Normative).
IT would, therefor, seem logical to allow the user to force the
encoding used to process the request from a client or the response
from the server.
However I do agree with your analysis of the problem presented here.
The guy's server is broken. It should either produce UTF-8 or have an
XML declaration specifying iso8859-1 encoding.
John Wilson
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
