XML sometimes takes programming (was crossing guard)
jenglish@f... (Joe English) writes: >I don't find it surprising that existing XML parsers >insist on treating their input as XML. I don't find it surprising. I do find it inconvenient when I have to work with tools that insist on turning my markup into escaped characters and stuffing it into an XML documents. I guess the nearest comparison I can find is a broken parser that insisted on wrapping all external entities in CDATA sections since heck, they might contain angle brackets. >Perhaps what you want is a parser for a language _similar_ to >XML, or a buggy XML parser that misimplements <![CDATA[...]]> >section parsing. I'm actually writing one, and this kind of case is exactly the kind of situation it should help solve: http://lists.xml.org/archives/xml-dev/200303/msg00568.html My original point in this thread was simply that these kinds of problems can be created by supposedly data-oriented applications just as easily as by document-oriented power markup creators. -- Simon St.Laurent Ring around the content, a pocket full of brackets Errors, errors, all fall down! http://simonstl.com -- http://monasticxml.org
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format