aboutsummaryrefslogtreecommitdiffstats
path: root/tests/extensions
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into admonitionTiago Serafim2013-02-097-1/+49
|\ | | | | | | | | | | Conflicts: docs/extensions/index.txt tests/extensions/test.cfg
| * nl2br and attr_list compatability.Waylan Limberg2013-02-063-0/+6
| | | | | | | | | | | | Fixes #177. When using both extensions, breaks (`<br>`) must have a linebreak (`\n`) after them before attr_list is run. This patch reorders the treeprocessors so that happens ('attr_list' runs after 'prettify' not before). Also had to alter headerid extension so it runs after 'prettify' or it would run before 'attr_list' if loaded before 'attr_list' by user.
| * Account for a paragraph that starts with a colon when processing def_listsWaylan Limberg2013-02-062-0/+40
| | | | | | | | Fixes #171. While that report provided an example of an unordered list item that started with a colon, any block that starts with a colon and has no siblings before it (paragraph as begining if document, list item, etc) all exhibit this same behavior. Following PHP Markdown Extra's lead, these are not definition items as they have no term before them.
| * Fixed #164. attr_list extension attribute names are now sanitized and won't ↵Waylan Limberg2012-12-132-1/+3
| | | | | | | | crash the serealizer.
* | More tests for the extension and new tests for the RE. It's now possible to ↵Tiago Serafim2012-09-192-0/+22
| | | | | | | | use an explicit blank title to not have the <p> tag with the title rendered.
* | Initial version with insufficient tests and no docs.Tiago Serafim2012-09-023-0/+39
|/
* Fix `footnote_many_footnotes` test as per #129Dmitry Shachnev2012-08-251-2398/+2398
|
* Fixed #129. Footnotes now output valid HTML5.Waylan Limberg2012-08-093-15/+15
| | | | | | | | | | | | | | | | As HTML5 has depreciated use of `rev=anything` and `rel=footnotes`, they are no longer inlcuded in the output when the output_format is set to HTML5. Note that if someone successful registers a spec for `rel=footnotes` in the future (as a microformat), then that could be considered valid. But until that happens, it is invlaid to use in HTML5. Therefore, we remove it from the output (when outputing HTML% only). As an alternative, two new classes are set (in all output_formats). On the link to the footnote (where `rel=footnotes` was used), we set `class=footnote-ref` and on the backlink (where `rev=footnote` was used), we set `class=footnote-backref`. Also updated the tests to reflect to the new classes in the output.
* Added support for <foo>+<bar> lexers of Pygmentspapaeye2012-07-212-0/+20
|
* Fixes #64. Added sane_list extension.Waylan Limberg2012-01-243-0/+40
| | | | | | | | | | 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.
* Removed Codehilite from tests.Waylan Limberg2012-01-202-32/+32
| | | | | | Codehilite generates differant output with differant versiosn of pygments. We support those various versions of pygments but can't unsure that the same version is always available on every platform tests are run on.
* Support github-flavored markdown by making the '.' optional before language ↵Mike Dirolf2012-01-173-0/+69
| | | | type.
* Fenced code blocks need to end with a fence on its own line.Mike Dirolf2012-01-173-0/+69
|
* 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-272-150/+0
| | | | extension source
* Allow tildes or backticks in the fenced_code extension to support the syntax ↵Daniel Gottlieb2011-12-273-1/+155
| | | | used by github
* 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-183-14/+7
|/ | | | code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
* Fixed #30. Tables now allow three spaces of indent like PHP Markdown Extra. ↵Waylan Limberg2011-06-292-1/+62
| | | | Thanks to skurfer for report and inital patch.
* Added docs and tests to attr_list ext. Closes #7.Waylan Limberg2011-06-203-0/+55
|
* Added our own xhtml searializer. We no longer use a xml searializer to ↵Waylan Limberg2011-06-161-6/+6
| | | | output xhtml. This fixes #9 among other bugs. The test suite even had bad tests that should have been failing. They also have been corrected.
* Skipping codehilite test as differant versions of pygments give slightly ↵Waylan Limberg2010-11-041-0/+2
| | | | differant output and I'm tired of seeing the test fail when there is no real problem.
* Fixed Ticket 70 and added a test. Footnote references whithout a ↵Waylan Limberg2010-08-252-0/+3
| | | | 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-022-0/+15
| | | | 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.
* Fixed Ticket 60. The dd in definition lists can now not be indented on ↵Waylan Limberg2010-03-242-0/+12
| | | | secondary lines.
* Changed the default style used by pygments in the codehilite extension. ↵Waylan Limberg2010-03-251-2/+2
| | | | This was a recently added feature, but older versions of pygments don't know what the 'tango' style is, so we now use pygemnts 'default' by default. Not sure why the 'tango' style was used here in the first place. I'm guess it was the preferance of whoever contributed the patch.
* Updated codehilite test to match new pygments output (they added an extra ↵Waylan Limberg2010-02-131-2/+2
| | | | div around line numbers).
* Moved test dir back out of markdown lib. We don't need to install the tests ↵Waylan Limberg2010-02-1230-0/+3694
in everyones site-packages. We just need to distrubute them in the tarball for people to run before installing etc.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-24 03:33:43 +0000