xml-rpc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Redman <...@ergotech.com>
Subject Re: DO NOT REPLY [Bug 6763] - XMLWriter doesn't escape enough characters
Date Fri, 01 Mar 2002 00:14:43 GMT
 From a position of complete ignorance, and without reading the spec. can 
someone clarify for me what this means?

The part of the spec quoted here says that you can't used binary chars, 
however "&#0005" seems to meet the requirement of the spec in that it 
matches "the production for Char".

Regardless of whether xmlrpc should be doing the escaping, it seems to me 
that I should be able to send a String that would be invalid XML by 
escaping each character - the resulting string seems to be valid.  This is 
philosphically the same as sending new line characters as "\\n" in human 
readable strings.

Is this the case or is it required that anything that may have a non-Char 
in it be base64 encoded?


On 2002.02.28 16:48:25 -0700 bugzilla@apache.org wrote:
> Comments from John Wilson <tug@wilson.co.uk>, author of the MinML parser:
> "
> This isn't a bug. You just can't legally have a Unicode character with
> the
> value 5 in a well formed XML document. Escaping it as &#0005; makes no
> difference.
> The relevant part of the spec is Section 4.1 Character and Entity
> References
> "Well-Formedness Constraint: Legal Character
> Characters referred to using character references must match the
> production
> for Char. "
> MinML currently and erroneously allows this - I'm in process of
> tightening
> it's checking and it will soon reject it.
> "

Jim Redman
(505) 662 5156

View raw message