From: Aaron G. <fl...@sh...> - 2007-12-31 06:16:13
|
Thanks! If anyone has any ideas for a quick-and-dirty hack to make in markdown.py to make it act normal I would really appreciate it. I played around for 20 minutes never got anywhere! I think maybe it's not exactly in the _get_right_tag, it seems that something before that part is acting different. `block` contains stuff I don't see if it were to be going over something like <foo />. Aaron On Dec 30, 2007, at 7:45 PM, Waylan Limberg wrote: > Thanks for the report Aaron. I see you reported this in the bug > tracker too - which will make sure we don't forget it. I'll look into > this when I get a chance. > > On Dec 30, 2007 6:04 AM, Aaron Gyes <fl...@sh...> wrote: >> Hi, >> >> I was looking to use this markdown module (the 1.7RC1 at the moment) >> on some strings that also have mako template tags in them. They >> basically look like this: >> >> <%def .... /> >> <%page .... /> >> % for x in foo: >> ... >> % endfor >> >> Anyways, I figured I might need to do something special for the >> strange '%' flow control structures, but I assumed that like the >> other >> markdown implementations it would ignore the other stuff like HTML >> tags, but it's totally choking. Here's a "test case": >> >> <%foo /> >> >> Heading >> ======= >> >> >> Simply returns the entire thing as-is. I'm guessing it never thought >> whatever kind of tag that was there ended up closing. >> >> Can I fix this through the API somehow? >> >> Aaron Gyes >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Python-markdown-discuss mailing list >> Pyt...@li... >> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss >> > > > > -- > ---- > Waylan Limberg > wa...@gm... |