Re: Tiger bug in NSXMLParser?

In article <vv3pe5-k8h.ln1@[EMAIL PROTECTED]
>,
 Lorenzopt <lorenzo@[EMAIL PROTECTED]
> wrote:

> What options does one have if parsing an XML do***ent fails due to 
> malformed content? If one does not control the XML source, what can be
done?

* File bug re****ts with the owner of the XML source.

* Make the completion of _your_ contracts contingent on the quality of 
your system's inputs. (Too late now, but something to remember the next 
time you agree to take on a job.)

* Find another supplier.

* Produce a good error message, so when your data vendor stops supplying 
good data, your customers know to complain to your supplier, not you. 
(They'll complain to you anyway.)

Of these, the first one is the most im****tant: clearly, your supplier 
hasn't already noticed his bug, or he would have fixed it.