aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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 "↩". 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
|
* No longer skipping all tests from PHP test suite. We skip some because PHP ↵Waylan Limberg2011-10-061-1/+38
| | | | differs from markdown.pl and we match markdown.pl. A few others are skipped because we have to adjust for a few edge cases. See comments in tests/php/test.cfg for details.
* Allow UPPERCASE urls in auto links.Waylan Limberg2011-10-061-1/+1
|
* Skipped 3 failing pl tests with some weird edge cases. A significant rewrite ↵Waylan Limberg2011-10-061-0/+12
| | | | if inlinepatterns will probably be needed for this. Putting it on hold till after 2.1-final is released.
* 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.
* Do'h! Fixed a silly typo.Waylan Limberg2011-10-051-1/+1
|
* Fixed a few typos in the using_as_module docs.Waylan Limberg2011-10-051-12/+16
|
* Fixed one more [[wikilink]] missed in previous commit.Waylan Limberg2011-10-051-1/+1
|
* Fixed a few errors in the 2.1.0-alpha release notes and updated links to not ↵Waylan Limberg2011-10-051-13/+15
| | | | use the [[wikilink]] style.
* Made a few minor edits to command line docs.Waylan Limberg2011-10-051-4/+4
|
* Updated docs to no longer use the [[wikilink]] style links from the old ↵Waylan Limberg2011-09-226-38/+37
| | | | wiki. All links are not realative links which should work with the supplied docs generator.
* Updated Extra Extension docs to relect recent changes in the extension.Waylan Limberg2011-09-221-9/+7
|
* Run a few more pl tests. Some of them are failing but should be easily fixable.Waylan Limberg2011-08-272-0/+12
|
* Added greater-than as an escaped character. Apparently markdown.pl escapes ↵Waylan Limberg2011-08-273-1/+4
| | | | it even though it is not documented.
* Added support to build_docs command to copy non markdown files unmodified.Waylan Limberg2011-08-233-6/+10
|
* Update build_docs script for the *.txt -> *.md change in docs.Waylan Limberg2011-08-232-10/+76
|
* Renamed *.txt -> *.md in docs.Waylan Limberg2011-08-2331-39/+1
|
* Fixed #39. Refactored escaping so that it only escapes a predifined set of ↵Waylan Limberg2011-08-175-8/+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.
* Fixed the fabfile geterate_test(s) commands so they actually import the ↵Waylan Limberg2011-08-171-2/+6
| | | | testing framework.
* The build_docs command now uses extra and toc extensions and a template on ↵Waylan Limberg2011-08-042-31/+34
| | | | the file system.
* 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 some fadfile commands to (re)generate tests when they are added or ↵Waylan Limberg2011-08-042-5/+54
| | | | updated.
* Set version to '2.1.0.alpha'.2.1.0.alphaWaylan Limberg2011-08-032-3/+3
|
* Added 'fab clean' command.Waylan Limberg2011-08-031-0/+4
|
* Updated release notes to include a note about support for python's `-m` option.Waylan Limberg2011-08-031-0/+6
|
* Added support for python's '-m' command line option. Do 'python -m markdown ↵Waylan Limberg2011-08-034-28/+49
| | | | [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-032-10/+2
|
* Markdown.convertFile now actually works with stdin and stdout. Previously ↵Waylan Limberg2011-08-032-5/+9
| | | | only the commandline script did.
* rename command 'fab do_release' -> 'fad deploy_release'Waylan Limberg2011-08-031-1/+1
|
* Updated fabfile to automate deploying a release. Includes building a release ↵Waylan Limberg2011-08-031-2/+81
| | | | distribution, registering it with PyPI and uploading donwloads to PyPI and Github.
* Added doctests to fabfile and edited them to pass in all supported versions ↵Waylan Limberg2011-08-028-58/+67
| | | | of python. Note: one test (meta) is still failing on Python 3 due to unicode strings.
* Edited release notes. Made a few minor corrections and added a note ↵Waylan Limberg2011-07-281-7/+15
| | | | regarding supported python versions. No more support for Python 2.3 with 2.4 support depreciated. We now support Python 3.2.
* TestCase.assert_ and TestCase.failUnless are depreciated in Python 3 in ↵Waylan Limberg2011-07-281-3/+3
| | | | favor of testCase.assertTrue. Might as well be using the right method in our tests.
* 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.
* Skip the UnidoceDecodeError API test in Python 3.x as all input should be ↵Waylan Limberg2011-07-281-2/+3
| | | | unicode anyway.
* Python 3.2 made some changes to the configparser which broke the testing ↵Waylan Limberg2011-07-282-5/+5
| | | | framework. With a simple addition to our subclass (which we then make use of), this is an easy fix.
* Fixed a Python 2.4 incompatability in last commit. 'encode' only accepted ↵Waylan Limberg2011-07-282-2/+2
| | | | positional arguments back then.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 10:03:11 +0000