[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Tradeoffs of XML encoding by enclosing all content in CDATA blocks
Title: Tradeoffs of XML encoding by enclosing all content in CDATA blocks I pointed out to a client that they're seeing failures parsing XML because some of the element content that they're producing contains characters illegal in XML content, like "&" (unencoded). They acknowledged that should be fixed, but they also said they could instead enclose all content with CDATA blocks. That seems bizarre to me, but I'm not sure I can immediately come up with all the cogent arguments against that. Can someone summarize specifically why you should NOT do that?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
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
|