This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
So THAT'S what CDATA is for...]
- To: xsl-list <xsl-list at lists dot mulberrytech dot com>
- Subject: [xsl] So THAT'S what CDATA is for...]
- From: owner-xsl-list at lists dot mulberrytech dot com (by way of MulberryTechnologies List Owner)
- Date: Wed, 7 Feb 2001 17:50:19 -0500
- Reply-To: xsl-list at lists dot mulberrytech dot com
Reply-To: "Michael Beddow" <m.beddow@ntlworld.com>
From: "Michael Beddow" <m.beddow@ntlworld.com>
To: <xsl-list@lists.mulberrytech.com>
Subject: So THAT'S what CDATA is for...
Date: Wed, 7 Feb 2001 20:53:54 -0000
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Hope this doesn't count as cross-posting, but the following sentence
from a new post on xml-dev just knocked me off my chair:
> A business partner has asked that we use CDATA sections for all
element
> content so they don't have to worry about handling special
characters.
So the Real World has spoken. Forget about all those encoding and
escaping headaches we grapple with so often: use CDATA for all element
content and kiss your problems goodbye!
Michael
------------------------------------------
Michael Beddow
http://www.mbeddow.net/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list