RE: Non-well-formed HTML in XSL

> -----Original Message-----
> From: Mike Brown [mailto:mike@xxxxxxxx]
> http://www.w3.org/TR/xslt#section-Introduction
> 
>   "A transformation expressed in XSLT describes rules for 
> transforming a 
>   source tree into a result tree"
> 
> http://www.w3.org/TR/xslt#output
> 
>   "An XSLT processor may output the result tree as a sequence 
> of bytes, 
>   although it is not required to be able to do so"
> 
> http://www.w3.org/TR/xslt#conformance
> 
>   "A conforming XSLT processor must be able to use a 
> stylesheet to transform a 
>   source tree into a result tree as specified in this 
> document. A conforming 
>   XSLT processor need not be able to output the result in XML 
> or in any other 
>   form."

Ok so how does all of this explain how you can have output
HTML or Text? I mean neither of those can be described as XML
unless we talk XHTML - which we're not. 

While we're on this one reason I've had to use D-O-E recently
is to accept a small amount of HTML as an argument for example...
<xsl:param name="itemsephtml" select="'&lt;img
src=&quot;/wdp/images/spc.gif&quot; alt=&quot;&quot;
height=&quot;1&quot;&gt;'"/>
which used to be
<xsl:param name="itemsephtml"><img src="/wdp/images/spc.gif" alt=""
height="1"/></xsl:param>
but I found when I passed a parameter with a text more or less similar
to the <img tag the <xsl:copy-of/> that I used to use to show
the parameter no longer worked so I was forced to this solution with
<xsl:value-of D-O-E/>

Any suggestion how I could have acheived my aim in a more XSL manner
would be most welcome.

Richard Mitchell
Software Development Manager
http://www.vbnonline.com/
 

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