aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Always use Markdown's serializers.Waylan Limberg2012-01-201-1/+1
| | | | | Not only does this ensure that all output matches the output_format, but it is nessecary to run in Python 3.
* Inline html is now escaped by the searializer.Waylan Limberg2012-01-197-8/+9
| | | | | | | | 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.
* Partial fix for issue introduced in fix for #59Waylan Limberg2012-01-197-3/+15
| | | | | Markdown markup inside angle bracktes now gets rendered properly in all cases except when safe_mode='escape'. Also added tests.
* Fixed #59. Raw HTML parsing is no longer slow.Waylan Limberg2012-01-182-14/+13
| | | | | | Replaced the unescape method I carlessly threw in the RawHtmlProcessor. Unfortunetly, this reintroduces the bug just fixed in commit 425fde141f17973aea0a3a85e44632fe18737996 Sigh!
* Cleaned up tests after merging pull request fixing #72.Waylan Limberg2012-01-185-3/+0
|
* Merge branch 'master' of git://github.com/fiesta/Python-Markdown into fiestaWaylan Limberg2012-01-1817-27/+182
|\ | | | | | | | | Conflicts: markdown/inlinepatterns.py
| * Support github-flavored markdown by making the '.' optional before language ↵Mike Dirolf2012-01-174-1/+70
| | | | | | | | type.
| * Fenced code blocks need to end with a fence on its own line.Mike Dirolf2012-01-174-1/+70
| |
| * When safe mode is 'escape', don't allow bad html to stop further processing.Mike Dirolf2012-01-145-22/+30
| | | | | | | | | | | | | | | | | | | | See tests/html4_safe/html_then_blockquote.(txt|html). It looks like having unclosed block-level html elements was causing further processing not to happen, even in the case where we're escaping HTML. Since we're escaping HTML, it seems like it shouldn't affect processing at all. This changes output results in a couple of other tests, but the new output seems reasonable to me.
| * Fix logic bug introduced in 35930e0928e19...Mike Dirolf2012-01-141-1/+1
| |
| * minor: adding some common OSX / emacs gitignore patternsMike Dirolf2012-01-141-1/+2
| |
| * Fixed #68. Blank line is not required after html comments.Waylan Limberg2012-01-154-16/+22
| | | | | | | | | | Interestingly, the change to the misc/mismatched-tags test is inline with PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
| * Fixed #57. Multiline HTML Blocks no longer require a blank line after them.Waylan Limberg2012-01-154-3/+25
| |
| * Fixed #70. Empty anglebrackets '<>' are now properly recognized as raw html.Waylan Limberg2012-01-151-1/+1
| |
| * Fixed #61. stdin and stdout should work better in python 3.Waylan Limberg2012-01-152-16/+26
| | | | | | | | | | Apparently, in Python3 stdin and stdout take str (unicode) not bytes. This provides a solution that will work in both python 2 & 3.
| * Fixed #69. url_sanitize no longer crashes on unparsable urls.Waylan Limberg2012-01-151-9/+18
| | | | | | | | | | | | | | | | | | | | 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.
| * Fixed #60. When we updated codehilite, we forgot to update fenced_codee to ↵Waylan Limberg2012-01-151-5/+5
| | | | | | | | work with it.
| * Fixed issue #66. Silly error. Not sure why the shebang lines were ↵Waylan Limberg2012-01-152-2/+2
| | | | | | | | capitalized. Thanks for the report.
| * fixed an error in the BACKLINK_TEXT option in the footnotes extension.tim2012-01-151-2/+2
| | | | | | | | | | I accidentally changed the wrong line (L294 instead of L293) to "self.footnotes.getConfig("BACKLINK_TEXT")" before. This fixes that.
| * New footnotes configuration option: BACKLINK_TEXT (second try).tim2012-01-151-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BACKLINK_TEXT specifies the text that's used in the link at the end of the footnote to link back up to the reader's place. It still defaults to "&#8617;". Okay, so at first I had an uncessarily complicated commit for this and submitted a pull request. Waylan showed me a better way to do it, here: https://github.com/startling/Python-Markdown/commit/ee7d1a26c76f970c12226ca48ba52dc1d32f2488#markdown/extensions/footnotes.py-P19 So I made another commit and added it to the pull request. But then I accidentally added yet another commit to the pull request, accidentally. Since then, I've realized it would be best to start with a new branch and closed that first pull request. Hopefully this will be the last try.
| * attempt at a fix for issue w/ MD links inside of html tagish stuff with safe ↵Mike Dirolf2012-01-124-2/+10
| | | | | | | | mode on.
* | Fixed a few typos in the doc strings. Thanks to Ivan Konev for the patch.Waylan Limberg2012-01-181-5/+5
| |
* | Fixed #68. Blank line is not required after html comments.Waylan Limberg2011-12-294-16/+22
| | | | | | | | | | Interestingly, the change to the misc/mismatched-tags test is inline with PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
* | Fixed #57. Multiline HTML Blocks no longer require a blank line after them.Waylan Limberg2011-12-294-3/+25
| |
* | Fixed #70. Empty anglebrackets '<>' are now properly recognized as raw html.Waylan Limberg2011-12-291-1/+1
| |
* | Fixed #61. stdin and stdout should work better in python 3.Waylan Limberg2011-12-282-16/+26
| | | | | | | | | | Apparently, in Python3 stdin and stdout take str (unicode) not bytes. This provides a solution that will work in both python 2 & 3.
* | Fixed #69. url_sanitize no longer crashes on unparsable urls.Waylan Limberg2011-12-281-9/+18
| | | | | | | | | | | | | | | | | | | | 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.
* | Fixed #60. When we updated codehilite, we forgot to update fenced_codee to ↵Waylan Limberg2011-12-281-5/+5
| | | | | | | | work with it.
* | Fixed issue #66. Silly error. Not sure why the shebang lines were ↵Waylan Limberg2011-12-282-2/+2
| | | | | | | | capitalized. Thanks for the report.
* | Merge pull request #67 from fiesta/masterWaylan Limberg2011-12-283-2/+16
|\| | | | | Allow backticks in addition to tildes for code blocks in the fenced_code extension
| * also undo changes to the test.cfgDaniel Gottlieb2011-12-271-4/+0
| |
| * appropriately move the tests to the fenced code documentation in the ↵Daniel Gottlieb2011-12-273-151/+11
| | | | | | | | extension source
| * common emacs support for a .gitignore fileDaniel Gottlieb2011-12-271-0/+2
| |
| * Allow tildes or backticks in the fenced_code extension to support the syntax ↵Daniel Gottlieb2011-12-274-2/+158
| | | | | | | | used by github
* | Merge pull request #65 from startling/backlinksWaylan Limberg2011-12-281-2/+8
|\ \ | |/ |/| New footnotes configuration option: BACKLINK_TEXT
| * fixed an error in the BACKLINK_TEXT option in the footnotes extension.tim2011-12-201-2/+2
| | | | | | | | | | I accidentally changed the wrong line (L294 instead of L293) to "self.footnotes.getConfig("BACKLINK_TEXT")" before. This fixes that.
| * New footnotes configuration option: BACKLINK_TEXT (second try).tim2011-12-201-2/+8
|/ | | | | | | | | | | | | | | | | | BACKLINK_TEXT specifies the text that's used in the link at the end of the footnote to link back up to the reader's place. It still defaults to "&#8617;". Okay, so at first I had an uncessarily complicated commit for this and submitted a pull request. Waylan showed me a better way to do it, here: https://github.com/startling/Python-Markdown/commit/ee7d1a26c76f970c12226ca48ba52dc1d32f2488#markdown/extensions/footnotes.py-P19 So I made another commit and added it to the pull request. But then I accidentally added yet another commit to the pull request, accidentally. Since then, I've realized it would be best to start with a new branch and closed that first pull request. Hopefully this will be the last try.
* Version 2.1.0-Final2.1.0.finalWaylan Limberg2011-11-243-9/+7
|
* Some more tests for issue #51. An upate to Marcin Kasperski's tests (which I ↵Waylan Limberg2011-11-173-2402/+1212
| | | | previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
* Merge git://github.com/Mekk/Python-Markdown into mekkWaylan Limberg2011-11-172-0/+10796
|\
| * Example test for #51 (crash on docs with +1000 footnotes)Marcin Kasperski2011-11-102-0/+10796
| |
* | Fixed #51. Removed recussion from footnote preproccessor. Also refactors the ↵Waylan Limberg2011-11-184-61/+38
| | | | | | | | code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
* | Fixed #47. Improved HRProccessor.\n\nPython's re module does not support ↵Waylan Limberg2011-11-173-19/+26
|/ | | | atomic grouping, which was slowing the HR regex down if a long HR ended with a non HR char (casing the regex to backtrack). Therefore, we have to simulate atomic grouping. Fortunately, we only need to match end-of-line or end-of-string after the atomic group here, so it was an easy case to simulate. Just remove the '$' from the end of the regex and manualy check using m.end(). The run method was refactored while I was at it, saving us from running the regex twice for each HR.
* Fixed #49. Don't crash on poorly/randomly ordered header levels. Maybe ↵Waylan Limberg2011-10-301-42/+46
| | | | someday we will better support any input (patches welcome), but we should never crash on poorly formatted input text. With this fix, we catch the exception and skip over it. The TOC up to the point (and perhaps after) still gets rendered. The incomplete TOC should be the clue to the document author that s/he has a formatting error in the document.
* Release 2.1.0-Beta2.1.0.betaWaylan Limberg2011-10-103-27/+28
|
* Removed another [[wikilink]] style link from the docs.Waylan Limberg2011-10-061-1/+2
|
* Fixed a few issues with writing_extensions.md.Waylan Limberg2011-10-061-11/+14
|
* Fixed minor typo in docs/index.mdWaylan Limberg2011-10-061-1/+1
|
* Added an index.md file to the docs. The docs can now be a full website unto ↵Waylan Limberg2011-10-061-0/+61
| | | | themselves.
* Updated docs/extensions/index to be more informative - not just list extensions.Waylan Limberg2011-10-061-2/+30
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 05:47:40 +0000