This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: disable-output-escaping
- From: Wendell Piez <wapiez at mulberrytech dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 01 Jul 2002 11:52:21 -0400
- Subject: RE: [xsl] disable-output-escaping
- Reply-to: xsl-list at lists dot mulberrytech dot com
Mike,
Whatever your user is typing into needs to be smart enough to escape
characters not allowed in XML into representations XML does allow.
It's really no different from (although not so complex as) having a
mechanism to turn "July 1" into "01-07" if that's what your processor needs.
What if they type in:
<hey! this is my tag --not!>
into the interface? :->
Whatever software is picking up this data could wrap it as
<![CDATA[<hey! this is my tag --not!>]]>
and then you'd be home free. Except for having to catch when they type the
string ']]>'. It might be easier to do a pass to turn & into & amp ; (but
no spaces) and < into & lt ;.
Note: this really isn't an XSL question, but has to do with the basic rules
of what's XML (and what only claims to be).
Cheers,
Wendell
At 11:21 AM 7/1/2002, you wrote:
The & is a character that could be entered by the user, I have no control
over what they enter. It is a dynamic process. I need to tell the XML
parser to treat any text entered by the user as text.
======================================================================
Wendell Piez mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list