Re: Tiger bug in NSXMLParser?

David Phillip Oster wrote:
> In article 
> <lazloman-8633C4.20184029042008@[EMAIL PROTECTED]
>,
>  Can I Get a Word In <lazloman@[EMAIL PROTECTED]
> wrote:
> 
>> tidy re****ted about 300 errors. That gave me the idea to try 
>> NSXMLDo***ent, since it has the tidyXML option. This actually works. 
>> Here's the code:
>>
>>
>>    NSXMLDo***ent* theDoc = [[[NSXMLDo***ent alloc] 
>> initWithContentsOfURL:[NSURL URLWithString:urlString] 
>> options:NSXMLDo***entTidyXML error:&err] autorelease];
>>    NSData* xmlData = [theDoc XMLData];
>>    NSXMLParser* parser = [[[NSXMLParser alloc] initWithData:xmlData] 
>> autorelease];
>>    [parser setDelegate:self];
>>    [parser parse];   
>>
>> I'm happy again.
> 
> I'm not. XML is supposed to be an all-or-nothing deal. If "tidy" says 
> there are errors, then a valid XML parser shouldn't parse it. A valid 
> parser SHOULD return an error in this case.
> 
> Oh well, maybe NSXMLDo***ent is in some weird HTML compatibility mode.

Isn't that what the NSXMLDo***entTidyXML option is for? Cleaning up bad 
XML? Leopard's NSXMLParser must be doing something similar since it 
parses the XML just fine, whereas Tiger's implementation of NSXMLParser 
may be more standard fails accordingly. I suppose there is always the 
possibility that Leopard could get the parsing wrong in more complex 
XML, possibly leading to more problems, but I appreciate the extra 
effort in Leopard and wish it had been passed down to Tiger. It would 
have saved me some time.