| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
only of an Element - rather than the html which just gets html escaped in the output anyway.
|
| |
|
|
|
|
| |
placeholder is an Elementtree Element.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Not only does this ensure that all output matches the output_format,
but it is nessecary to run in Python 3.
|
|
|
|
|
|
|
|
| |
Final fix to issue introduced in fix for #59. Weird stuff inside
angle brackets now also work in safe_mode='escape'. We just did the
same thing as with block html, let the (x)html searializer do the
escaping. Tests updated including the standalone test moved to match
the non-escape cases.
|
|
|
|
|
| |
Markdown markup inside angle bracktes now gets rendered properly
in all cases except when safe_mode='escape'. Also added tests.
|
|
|
|
|
|
| |
Replaced the unescape method I carlessly threw in the RawHtmlProcessor.
Unfortunetly, this reintroduces the bug just fixed in commit
425fde141f17973aea0a3a85e44632fe18737996 Sigh!
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Also optimized the code to bypass parsing when not in safe_mode and return
immediately upon failure rather than continue parsing when in safe_mode.
Note that in Python2.7+ more urls may fail than in older versions because
IPv6 support was added to urlparse and it apparently mistakenly identifies some
urls as IPv6 when they are not. Seeing this only applies to safe_mode now,
I don't really care.
|
| |
|
|
|
|
| |
chars (the set defined by JG in the syntax rules). All other backslashes are passed through unaltered by the parser. If extensions want to add to the escapable chars, they can append to the list at markdown.ESCAPED_CHARS.
|
|
|
|
| |
brackets in reference links. Now we do as well.
|
| |
|
|
|
|
| |
they are removed before escaping takes place. Related to issue #14.
|
|
|
|
| |
uppears that we are loosing escaped backslashes (both in the href and in the link label in the example given in issue 14.
|
|
|
|
| |
from tests/pl/Tests_2007/. Namely, improved simple reference links and fixed a small issue with titles in links.
|
|
|
|
| |
links; i.e., [this works]. Associated with and noted as missing when debuging Ticket 79.
|
|
|
|
| |
This matches the most recent version of markdown.pl among other implementations and allows links to work after editors do autolinebreak stuff to text.
|
|
|
|
| |
will match unicode characters when \w, \b, or \s is used. Also updated docs to reflect change.
|
|
|
|
| |
only officially support Python 3.1+ in the Python 3 series (we still support 2.4, 2.5 & 2.6 in the Python 2 series). If you really must use Python 3.0, we suggest using Python 3.1's 2to3 tool. See comment in source and Ticket 66 for more.
|
|
|
|
| |
should be more future proof.
|
|
|
|
| |
utility functions called by a build_parser method on the Markdown class. Editing of the processors and patterns now all happen in one file for each type. Additionaly, a subclass of Markdown could potentially override the build_parser method and build a parser for a completely differant markup language without first building the default and then overriding it.
|
| |
|
| |
|
|
|
|
| |
if they desire.
|
|
|
|
| |
wrapped in punctuation without spaces and still will be converted to emphasis (ie: '[_foo_]'). Test included. Thanks for the report seanh.
|
|
|
|
| |
non-greedy - it no longer eats everything between the first links title and the last links title in a paragraph. Thanks to Charles Winebrinner for the report.
|
|
|
|
| |
30 and other related issues. Note that I went with php's behavior rather than perl's when we have have three (ie.: *** or ___) without a closing three.
|
|
|
|
| |
Apparently differant versions of ElementTree encode line breaks in attributes differantly. Therefore, we just remove any such linebreaks as they are insignificant anyway.
|
|
|
|
|
|
| |
output in test-markdown.py for
the same.
|
| |
|
|
|