Prepend a slash to tell Wagn to not interpret markup, e.g.:
{{inclusion}}
[[foo]]
(right now we use span and /span, an ugly kluge)
Tracking pages to fix once this is implemented:
relative names+description
wql+Samples - many inclusions
I see value in being able to make text monospaced (again, for documentation)
--John Abbe.....Mon Mar 10 15:15:25 PDT 2008
The inclusion and the links provide slightly different challenges. If, for any given card, the double ['s make it past initial rendering and into the cache, your work on links is done. On the other hand, if your double {'s make it past initial rendering, then the inclusions will still get rendered. So I think ['s should be handled pre-cache, and {'s should be handled post.
--Ethan McCutchen.....Tue Sep 16 13:11:01 -0700 2008
would like to deprecate the star-slash mockup. Maybe there's a tinymce monospace option? Doesn't seem wagny to do this with markup.
--Ethan McCutchen.....Wed Dec 10 15:32:30 -0800 2008
--John Abbe.....Wed Mar 25 16:42:33 -0700 2009
--John Abbe.....Wed Mar 25 17:23:37 -0700 2009
--John Abbe.....Wed Mar 25 17:41:38 -0700 2009
--Ethan McCutchen.....Wed Mar 25 20:39:24 -0700 2009
--John Abbe.....Thu Mar 26 02:33:52 -0700 2009
--Ethan McCutchen.....Thu Mar 26 10:18:24 -0700 2009
--John Abbe.....Thu Mar 26 11:34:14 -0700 2009
--John Abbe.....Thu Mar 26 11:47:23 -0700 2009