summaryrefslogtreecommitdiff
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
...
| * | 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 "↩". 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-121-2/+5
| | | | | | | | | | | | 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-291-14/+10
| | | | | | | | | | | | | | | 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-291-1/+8
| | |
* | | 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-281-1/+13
|\ \ \ | |/ / | | | Allow backticks in addition to tildes for code blocks in the fenced_code extension
| * | appropriately move the tests to the fenced code documentation in the ↵Daniel Gottlieb2011-12-271-1/+11
| | | | | | | | | | | | extension source
| * | Allow tildes or backticks in the fenced_code extension to support the syntax ↵Daniel Gottlieb2011-12-271-1/+3
| | | | | | | | | | | | used by github
* | | 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-241-2/+2
| |
* | Fixed #51. Removed recussion from footnote preproccessor. Also refactors the ↵Waylan Limberg2011-11-181-47/+31
| | | | | | | | 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-171-18/+19
|/ | | | 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-101-2/+2
|
* Allow UPPERCASE urls in auto links.Waylan Limberg2011-10-061-1/+1
|
* Fixed #44. The TOC extension will now except True/False in addition to 1/0 ↵Waylan Limberg2011-10-061-1/+1
| | | | from the command line style syntax for passing in bool type extension configs. In order words, we now except strings in addition to booleans and integers.
* Added greater-than as an escaped character. Apparently markdown.pl escapes ↵Waylan Limberg2011-08-271-1/+1
| | | | it even though it is not documented.
* Fixed #39. Refactored escaping so that it only escapes a predifined set of ↵Waylan Limberg2011-08-173-5/+29
| | | | 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.
* TOC extension now attaches toc to Markdown instance (Markdown.toc), but only ↵Waylan Limberg2011-08-041-0/+11
| | | | if a marker was not found in the document.
* Set version to '2.1.0.alpha'.2.1.0.alphaWaylan Limberg2011-08-031-2/+2
|
* Added support for python's '-m' command line option. Do 'python -m markdown ↵Waylan Limberg2011-08-032-9/+13
| | | | [options] [args]'. I suspect will drop the command line script (markdown_py) when we drop support for Python 2.4 as this is easier to support.
* Cleaned up commandline script. Everything is in module now.Waylan Limberg2011-08-031-4/+2
|
* Markdown.convertFile now actually works with stdin and stdout. Previously ↵Waylan Limberg2011-08-031-3/+6
| | | | only the commandline script did.
* Added doctests to fabfile and edited them to pass in all supported versions ↵Waylan Limberg2011-08-027-58/+66
| | | | of python. Note: one test (meta) is still failing on Python 3 due to unicode strings.
* Fix a minor Python 3 incompatability in the headerid extension's slugify ↵Waylan Limberg2011-07-281-1/+1
| | | | function. The url is being encoded (with errors ignored) as an easy means of removing non-ascii chars, but we have to re-encode it *before* running the regex on it, not after.
* Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵Waylan Limberg2011-07-281-1/+1
| | | | positional arguments back then.
* All internal encoding of output now uses the 'xmlcharrefreplace' error ↵Waylan Limberg2011-07-281-3/+6
| | | | handler. Also added a note to the docs. Anyone doing their own encoding of output should be as well.
* Stripped out encoding/decoding in the searializers.Waylan Limberg2011-07-272-48/+38
| | | | | | | | | | | | | | | | | | | | | | | Those extra steps always bothered me as being unnecessary. Additionally, this should make conversion to Python 3 easier. The 2to3 tool wasn't converting the searializers properly and we were getting byte strings in the output. Previously, this wasn't a major problem because the default searializer was the xml searializer provided in the ElementTree standard lib. However, now that we are using our own xhtml searializer, it must work smoothly in all supported versions. As a side note, I believe the thought was that we needed to do the encoding to take advantage of the "xmlcharrefreplace" error handling. However, using the example in the python [docs](http://docs.python.org/howto/unicode.html#the-unicode-type): >>> u = unichr(40960) + u'abcd' + unichr(1972) >>> u.encode('utf-8', 'xmlcharrefreplace').decode('utf-8') == u True There's no point of using the "xmlcharrefreplace" error handling if we just convert back to the original Unicode anyway. Interestingly, the Python 3 standard lib is doing essentially what we are doing here, so I'm convinced this is the right way to go.
* Fix syntax error in doctests which tripped up the 2to3 tool.Waylan Limberg2011-07-241-6/+6
|
* Fixed a few minor Python2.4 incompatabilities. Runs in 2.4-2.7 cleanly.Waylan Limberg2011-07-222-2/+8
|
* Fixed the bug exposed in 8761cd1780a7cec60123. We no longer should get empty ↵Waylan Limberg2011-07-211-2/+3
| | | | rawhtml blocks. All tests pass again.
* Fixed #31. Headers in tight lists now get inline patterns run on their ↵Waylan Limberg2011-07-211-1/+12
| | | | tails. Tests included.
* Updated toc extension's anchorlink option to work properly with recent refactor.Waylan Limberg2011-07-141-2/+6
|
* Refactored the toc extension. Fixes #33: The [TOC] marker is now ignored in ↵Waylan Limberg2011-07-141-28/+17
| | | | code blocks/spans. A better fix for #4: Only the *text* from the header is caried over to the toc (without *any* inline formatting). Also refactored the extension to better work in tandem with the refactored headerid extension and the new attr_list extension.
* Fixed #34. Better support for unicode text with the html_tidy extension. ↵Waylan Limberg2011-07-141-2/+5
| | | | Force input and output of tidy to use UTF-8 and encode before and decode after passing in the text.
* Refactored HeaderId extension to no longer include defining ids. It only ↵Waylan Limberg2011-06-302-78/+76
| | | | autogenerates ids. If you want to define your own, use the attr_list extension. Also expanded HeaderId extension to use the same algorithm as the TOC extension (which is better) for slugifying the header text. Added config settings to override the default word separator and the slugify callable. Closes #16 as the reported bug is for a removed feature.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-291-6/+7
| | | | Thanks to skurfer for report and inital patch.
* Fixed #28. Inline raw html is now enclosed in p tags. This used to work. ↵Waylan Limberg2011-06-281-1/+12
| | | | Somehow we stopped checking for a single inline html element when swapping back in raw html. Added a test. Also patched a weird (invalid) comment test. Seeing the input is not really a valid html comment - it doesn't matter what we do with it. I suppose we test it to make sure it doesn't break the parser. Actual output is not so important. As a side note, this has exposed a preexisting (unrelated) bug with the extra extension's handling of raw html. That test is failing following this fix.
* also respect encoding when reading from a user-provided fileTravis Parker2011-06-251-1/+1
|
* Added html5 and xhtml5 output formats. These are just aliases to html4 and ↵Waylan Limberg2011-06-231-0/+4
| | | | xhtml1 searializers respectively.
* Cleaned up backward compatability of old positional arguments. Some people ↵Waylan Limberg2011-06-231-12/+44
| | | | may be using them, so we should continue to support them. Also adjusted docs to encourage using keyword args only. However, if existing code was using positional args in previous versions, it should still work.
View Lorry Controller Status