Re: bug in e4x? missing = in XML attribute

This is a multi-part message in MIME format.
--------------010109030004050908030600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Martin Honnen wrote:
> Leni wrote:
>> Hi, I think I may have encountered a bug in e4x parsing related to a 
>> 3-byte sequence of UTF-8.
>>
>> The reason I think it's a bug is that it seems unreasonable that the 
>> test case XML is parsable by the DOM parser but not the e4x parser.
>>
>> Before filing in bugzilla I thought I would post here to see if anyone 
>> has another explanation for the behaviour.
>>
>> An email describing the problem with a test case is attached.
> 
> Can you post the XML you are trying to parse?

Test-case xml is attached.

I also have a question about a workaround I was considering using:

var serializer = new XMLSerializer();
var str = serializer.serializeToString(req.responseXML);
var xml = new XML(str);

By running the DOM's XML through the XMLserialzer to make a string then 
giving that to the e4x parser at least it parses.

But XMLserialiser turns that three-byte UTF-8 sequence into a '(' 
character.  So two more questions:
a) can someone offer a pointer to how XMLserializer is supposed
    to behave when there is a 3-byte UTF-8 sequence in the content
    of an element?
b) can anyone suggest any other workaround?

The real-world thing I am trying to do is get a UTF-8 encoded Atom feed 
coming from Google into an e4x XML object.

Leni.

--------------010109030004050908030600
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dev-tech-xml mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xml

--------------010109030004050908030600--