[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: MSIE XSLT vs. XT XSLT
> > <xsl:template match="lastname"> > <xsl:text disable-output-escaping="yes"> > <var name='lastname'> > <string></xsl:text><xsl:value-of select="."/> > <xsl:text disable-output-escaping="yes"></string> > </var></xsl:text> > </xsl:template> > > > Can someone tell me why MSIE behaves in this manner? > No, but I don't really blame it when faced with code like that. What on earth is wrong with the perfectly sanitary: <xsl:template match="lastname"> <var name='lastname'> <string><xsl:value-of select="."/></string> </var> </xsl:template> Disable-output-escaping is a horible kludge to be used only as a last resort. It forces the processor to serialize the text as XML, meaning that you can't pass the XML to another process without reparsing it, and it generally obfuscates your code. XSLT processors aren't even obliged to take any notice of it. Mike Kay *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
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
|