Re: Tiger bug in NSXMLParser?

Tom Harrington wrote:
> In article <oster-21267B.20023929042008@[EMAIL PROTECTED]
>,
>  David Phillip Oster <oster@[EMAIL PROTECTED]
> wrote:
> 
>> 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.
> 
> NSXML is also surprisingly flexible when it comes to doing Xpath lookups

> on do***ents with default namespaces.  As in, you can leave the 
> namespaces out of the lookup path and still get results.
> 
It sure is. I've used it and it works quite nicely.