[android-developers] Re: SAXParser reports different name on SDK 0.9 from SDK 1.0

2008-10-01 Thread Chris Cicc
Hey Brad and Charlie, I thought I'd submit my source code for everyone's reference. At this point I'm very confident this is a bug. If it isn't I clearly don't know nearly as much about XML and text encoding as I think I do :-) The XML doc being passed in looks something like this: {

[android-developers] Re: SAXParser reports different name on SDK 0.9 from SDK 1.0

2008-10-01 Thread Charlie Collins
I think you guys are both saying the same thing, maybe? Unless I misunderstand, Chris says he is using & which is the ESCAPED ampersand, and Brad is saying to make sure you use the entities to escape special chars. I think we all agree you should use valid XML, or it will cause issues - but the r

[android-developers] Re: SAXParser reports different name on SDK 0.9 from SDK 1.0

2008-09-30 Thread Brad Gies
Chris, What you described doesn't seem like the proper behavior even for the XML special characters. But, I have to admit that I'm just getting into Unicode, so I don't know exactly what should happen. It does seem to me that if you are using the ampersand character and it's not in one of the sec