I suppose that having the Javascript in a different snippet and including
it in the original snippet won't work since the textile filter will be
applied to all the complete snippet output. I'm right?
/AITOR
On 9/5/07, Jonathan Métillon <[EMAIL PROTECTED]> wrote:
>
>
> >
> > Let me correct : when I posted my message about snippets, I did not
> > actually test it because I already had converted all my form to pure
> > HTML and simply deactivated Textile filter.
> >
> > But now I have another form, which is still using Textile. And I
> > included my snippet, containing the JavaScript. And the JavaScript is
> > again f***d up! So I added the <notextile>...</notextile> tag and it
> > looks better, but one character remains converted: it's & (the
> > ampersand) that is converted to &
> >
> > And I really need it because I can't use the JavaScript AND operator
> > (&&)! Do you know how to stop Textile from escaping the ampersand?
> >
> > Thank you.
> >
> > Jonathan
> >
> >
> >
> > Have you tried wrapping the code in a CDATA tag? Textile might ignore
> that.
> >
> > Sean
> Hi Sean,
>
> I just tried and the <![CDATA[ was converted to <![CDATA[
>
> If I combine CDATA and notextile, I still have & converted to &
> _______________________________________________
> Radiant mailing list
> Post: [email protected]
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
