Re: Tiger bug on NSXMLParser?
Re: Tiger bug on NSXMLParser?
- Subject: Re: Tiger bug on NSXMLParser?
- From: "Lorenzo Thurman" <email@hidden>
- Date: Tue, 29 Apr 2008 08:27:31 -0500
Have you tried loading the data first, and then parsing it? Does the data
> > look reasonable, i.e. can you convert it to an NSString using the expected
> > encoding?
> >
>
I tried loading the XML into an NSString using
initWithContentsOfURL:encoding:error using Latin1 encoding. Under Leopard,
the XML is read in just fine. I can output the resulting string in the
debugger and it looks good and is parsed just fine. Under Tiger, the string
is just a bunch of unicode escape sequences and results in another empty
document error after running through NSXMLParser. I'm running on PPC with
10.4.11, if that matters at all.
--
"My break-dancing days are over, but there's always the funky chicken"
--The Full Monty
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden