summaryrefslogtreecommitdiff
path: root/markdown/extensions
Commit message (Collapse)AuthorAgeFilesLines
...
* Fixed #106. Replaced all references to freewisdom.org (except for Yuri's ↵Waylan Limberg2012-06-2810-17/+17
| | | | homepage).
* Fixed #109. The attr_list extension can now be loaded either before or after ↵Waylan Limberg2012-06-281-2/+6
| | | | the headerid extension.
* Fix #99. Account for empty header IDs when ensuring uniqueness.Waylan Limberg2012-05-241-1/+1
|
* Fixed Issue #98. The language designator must start at the beginging of the ↵Waylan Limberg2012-05-181-1/+1
| | | | first line of a code block for codehilite to recognize it.
* Fixes #64. Added sane_list extension.Waylan Limberg2012-01-241-0/+49
| | | | | | | | | | This is an extension which alters the behavior of lists to be less surprising. If turned out to be rather simple to code. I'm surprised no one had written it yet. I should note that this extension does not generate separate lists if different unordered list markers are used (`*` verses `-` verses `+`) The way the parser works that would be a little more tricky.
* Fixed #73. Codehilite now works in footnotes.Waylan Limberg2012-01-202-4/+4
| | | | | | | | The footnotes treeprocessor must be the first one run so that all others, including codehilite's, can run on the contents of the footnote div which is created and inserted by the footnotes treeprocessor. Thanks to startling for the report.
* Support github-flavored markdown by making the '.' optional before language ↵Mike Dirolf2012-01-171-1/+1
| | | | type.
* Fenced code blocks need to end with a fence on its own line.Mike Dirolf2012-01-171-1/+1
|
* 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.
* 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 #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 #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.
* 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.
* 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.
* 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.
* 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-221-1/+7
|
* 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.
* Added nl2br extension. Closes #13. Thanks to Brian Neal for writing the code ↵Waylan Limberg2011-06-211-0/+35
| | | | and allowing us to use it.
* allow language guessing to be disabled by passing a setting to CodeHilite - ↵Rob McBroom2011-06-192-4/+17
| | | | closes #24
* Added attribute list extension inspired by Maruku's attribute list feature. ↵Waylan Limberg2011-06-171-0/+122
| | | | See issue #7. Also likely to become a replacement for the headerid extension (with a little more work - need a forceid option) which means it will also address issue #16. The extension works with some limited testing. Still needs tests and documentation. Currently breaks toc extension - which should run after attr_list, not before.
* A few minor tweaks to the smart_strong extension. Thanks to David Chambers ↵Waylan Limberg2011-06-131-2/+2
| | | | for pointing out the typo.
* Added smart_strong extension. Fixes Issue #17. Like PHP Markdown Extra, we ↵Waylan Limberg2011-06-072-1/+47
| | | | now include smart handling of double underscores (not just single underscores). The new behavior may be called seperately as the 'smart_strong' extension or as part of the 'extra' extension.
* Added "." to the characters that may be included in implicit heading ids.David Chambers2011-06-051-1/+1
|
* Fix #4. Links in headers no longer munge up table of contents in TOC extension.Waylan Limberg2011-05-041-3/+10
|
* Fixed typo in previous commit. Extension.getConfigs is a method, not a property.Waylan Limberg2011-05-041-1/+1
|
* Extension.getConfigs returns a dict and is used by the extensions that use ↵Waylan Limberg2011-05-046-32/+26
| | | | configs. No more self.config['name'][0] weirdness anymore.
* Minor improvement to Extension settings API. Extension.getConfig now accepts ↵Waylan Limberg2011-04-071-3/+7
| | | | a 'default' keyword and added Extension.getConfigs which returns a list of tuples of all settings without the descriptions.
* Factored out the importing of pygments in CodeHilite Extension so it doesn;t ↵Waylan Limberg2011-04-071-27/+24
| | | | happen every time a block is highlighted. Not sure why I didn't do it this way to begin with.
* Cleaned up CodeHilite extension. When pygments is not available provide ↵Waylan Limberg2011-04-071-25/+12
| | | | simpler markup which should allow for the use of JavaScript Highlighting libraries. In other words, no pygments like <div> and no <ol> for line numbering. Just a <pre><code> block with classes assinged to them. If people want fancier stuff, they can use JavaScript or create their own extension.
* Corrected behavior of headerid extension to match default behavior when ↵Waylan Limberg2011-04-281-1/+4
| | | | "Weve got a problem header". We log a warning - not raise an exception.
* sane logging. remove sys.exit() calls (libraries should never ever call ↵Craig de Stigter2011-04-182-6/+1
| | | | sys.exit()) and raise appropriate exceptions instead. backwards incompatible insofar as custom extensions may need tweaks if they're using old markdown logging (but they shouldn't, it was gross)
* Added an alternative meta list syntax.David Chambers2011-02-171-1/+5
| | | | | | | | | | | | | | | Implicit syntax (existing): tag: Python Markdown Explicit syntax (new): tag: Python tag: Markdown These two examples are now equivalent. Previously, the latter would produce `{u'tag': [u'Markdown']}` rather than `{u'tag': [u'Python', u'Markdown']}`.
* Made the HeaderId extension's word separator configurable to allow, forDavid Chambers2011-01-221-2/+3
| | | | example, hyphens to be used rather than underscores.
* Updated regular expression to accept periods in heading ids.David Chambers2011-01-091-1/+1
|
* Merge branch 'master' of git@gitorious.org:python-markdown/mainlineWaylan Limberg2010-09-201-51/+0
|\
| * Fixed Ticket 71. Wrapper functions no longer do there own thing with ↵Waylan Limberg2010-08-291-51/+0
| | | | | | | | extensions. All behavior is now within the class.
* | Fixed Ticket 78. Wikilinks now support unicode characters.Waylan Limberg2010-09-201-1/+1
|/
* Fixed Ticket 70 and added a test. Footnote references whithout a ↵Waylan Limberg2010-08-251-7/+10
| | | | coresponding definition no longer raise an error. They now pass through as plain text - which is the same behavior as PHP Markdown Extra. Thanks for the report Benjamin Bach.
* Fixed problem hidden by Ticket 68. Defining a footnote placeholder in a ↵Waylan Limberg2010-08-021-8/+7
| | | | markdown document results in the placeholder actually being replaced. Also added a test for this. Note that if the placeholder paragraph has other text, that text is lost. Not sure if this is a bug or bad markdown syntax.
* Fix Ticket 68. Remove an old line of code from the footnote extension that ↵Waylan Limberg2010-08-021-1/+0
| | | | should have been removed excatly 2 years and 3 days ago (commit bd185087dc899b6157f8) when elementtree support was added. And to think it has been generating an error the whole time and was only just reported now. It appears this was never tested as it still does not work after removing the old line. At least we do not get an error. The footnote placeholder is just an empty paragraph. Thanks for the report Evan Carmi.
View Lorry Controller Status