[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: GOTCHA!
Subject: Re: GOTCHA! From: "Oren Ben-Kiki" <oren@xxxxxxxxxxxxx> Date: Thu, 14 Jan 1999 10:38:19 +0200 |
James Clark <jjc@xxxxxxxxxx> wrote: >It seems to work just fine to me. Given: > ><script>//<xsl:comment> ><![CDATA[ >document.write("<P>Hi <B>Oren</B>!") >]]> >//</xsl:comment></script> > >XT will output (correctly): > ><script>//<!-- > >document.write("<P>Hi <B>Oren</B>!") > >//--></script> As long as you don't write 'i--' in the JavaScript code, of course :-) It will work now, but will stop when you fix the <xsl:comment> bug. >> Any reason we have <xsl:comment> and not <xsl:cdata>? Any chance we may get >> <xsl:cdata>? > >I can't see how it would help you. > ><xsl:cdata>1 < 2</xsl:cdata> > >would produce > ><![CDATA[1 < 2]]> > >which would be treated by XML processors the same as > >1 & 2 > >but would not work in HTML. I would write: <script>//<xsl:cdata> for(i = 10; i >= 0; i--) { } //</xsl:cdata></script> Which would work - and wouldn't using <xsl:comment>. Note that here I _hope_ that "a[b[7]]>3" would be converted by the XSL processor to "a[b[7] ]>3" which doesn't break the code, unlike changing 'i--' into 'i- -'. This just leaves the problem of handling quotations inside XSL-generated JavaScript strings, which neither approach solves. Share & Enjoy, Oren Ben-Kiki XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: GOTCHA!, Oren Ben-Kiki | Thread | Re: GOTCHA!, James Clark |
Re: GOTCHA!, Oren Ben-Kiki | Date | Re: GOTCHA!, Oren Ben-Kiki |
Month |