>> On /Mon Aug 27 15:55:56 GMT 2007/, *Andrew Bloom* wrote: >> >> if you are using textile you can either disable it, or wrap the >> content that shouldnt be processed in <notextile> ... </notextile> >> blocks. > > Excellent, I didn't know about that <notextile>. And is there also > <nomarkdown> and <nosmartypants>? > > I still prefer to use a snippet, against wrapping the code in > <notextile><nomarkdown><nosmartypants>...</notextile></nomarkdown></nosmartypants> > > > > :-D > > Also using a snippet, I don't have to touch the extension hard code. > > Jonathan
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 _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
