Subject: RE: [xsl] [XSLT] xsl:message output encoding ? From: Kevin Rodgers <kevin.rodgers@xxxxxxx> Date: Thu, 21 Apr 2005 11:45:29 -0600 |
Michael Kay writes: > I don't think that using the same format as the principal output makes very > much sense - why should it be the same? However, I can see an argument for > providing some control. Some people only ever use xsl:message for simple > text messages, in which case escaping < and > doesn't make much sense; but > if you use it to output chunks of XML, like > > <xsl:message>Value of $tree: <xsl:copy-of select="$tree"/></xsl:message> > > then using the XML output method makes much more sense. Exactly. Is there any way to achieve that in XSLT 2.0? My situation is even simpler, since I want to include a hard-coded <tree root="tap"> start tag (not an arbitrary XML fragment). -- Kevin
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] [XSLT] xsl:message output, Michael Kay | Thread | RE: [xsl] [XSLT] xsl:message output, Michael Kay |
RE: [xsl] write out xml *with* tags, Maria Amuchastegui | Date | RE: [xsl] Java Transformation, Aron Bock |
Month |