RE: [xsl] Best way to include code samples

["Evan Lenz" <elenz@xxxxxxxxxxx>]

I made the assumption that you needed to manipulate and/or generate the
escaped XML elements using XSLT. Since you don't, then yes, a CDATA section
is the obvious thing to use.

Evan Lenz
XYZFind Corp.

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Larry
> Garfield
> Sent: Thursday, August 16, 2001 12:19 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: [xsl] Best way to include code samples
>
>
> > -----Original Message-----
> > I still intend to get it working. Please let me know
> > what you end up doing.
> >
> > Mark
>
> It turns out that CDATA did what I needed it to do.  What I ended up with
> was this:
>
> <para role="pre"><![CDATA[<smallscreenignore>
>    <img src="bigpic.gif" height="600" width="450" />
> </smallscreenignore>]]></para>
>
> (The file is conforming DocBook.)  The CDATA ends up escaping everything
> inside it, which is good.  Then my XSLT script catches <para> and turns it
> into <p>, but turns <para role="pre"> into <pre>.  So the final output is:
>
> <pre>&lt;smallscreenignore&gt;
> 	&lt;img src="bigpic.gif" height="600" width="450" /&gt;
> &lt;/smallscreenignore&gt;</pre>
>
> Which is exactly what I needed.
>
> I'm still going to look through the examples you and others
> suggested when I
> get the chance, just for educational purposes.
>
> --Larry Garfield
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list