aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * docs: capitalization fixes, plural fixes, small wording improvementsJakub Klinkovský2014-02-1517-54/+56
| |
| * docs: update wikilinks documentationJakub Klinkovský2014-02-151-38/+24
| |
| * docs: update toc documentationJakub Klinkovský2014-02-151-30/+43
| |
| * docs: update smarty documentationJakub Klinkovský2014-02-151-19/+10
| |
| * docs: update sane_lists documentationJakub Klinkovský2014-02-151-12/+4
| |
| * docs: update nl2br documentationJakub Klinkovský2014-02-151-3/+15
| |
| * docs: update meta_data documentationJakub Klinkovský2014-02-151-14/+25
| |
| * docs: update header_id documentationJakub Klinkovský2014-02-151-10/+16
| |
| * docs: update codehilite documentationJakub Klinkovský2014-02-151-67/+72
| |
| * docs: improved documentation of the extra/ extensionsJakub Klinkovský2014-02-158-79/+75
|/ | | | | | Simplified, unified style, added some undocumented options. NOTE: Footnotes/UNIQUE_IDS stays mostly undocumented
* Merge pull request #287 from mitya57/masterWaylan Limberg2014-02-136-57/+58
|\ | | | | Release Notes and a fix for Smarty
| * smarty: Get rid of canonicalize() function.Dmitry Shachnev2014-02-131-51/+16
| | | | | | | | | | | | | | | | The previous problem happened because canonicalize() removed the space from closeClass regexp. Instead of fixing the function, get rid of it completely. It should also make module load a bit faster.
| * Add a (failing) test for Smarty extension.Dmitry Shachnev2014-02-132-1/+3
| |
| * Updated version 2.4 release notes.Dmitry Shachnev2014-02-133-5/+39
|/
* Merge pull request #285 from mitya57/masterWaylan Limberg2014-02-122-2/+2
|\ | | | | Fix some tests failures
| * Fix some tests failuresDmitry Shachnev2014-02-122-2/+2
|/
* Merge pull request #284 from eichin/patch-2Waylan Limberg2014-02-111-1/+1
|\ | | | | typo
| * typoMark Eichin2014-02-111-1/+1
|/ | | chaining calls, not changing calls
* Merge pull request #282 from llbit/patch-1Waylan Limberg2014-02-061-1/+1
|\ | | | | Pedantic edit in installation instructions
| * Pedantic edit in installation instructionsJesper Öqvist2014-02-061-1/+1
|/ | | Fixed "you're"/"your" mixup. Sorry.
* No longer restrict INLUNE_PLACEHOLDER to 4 digits.Waylan Limberg2014-02-021-1/+1
| | | | | | This was limiting the parser to only 10,000 placeholders (0-9999) per document. removing this limitation allows longer documents ot be parsered correctly. Fixes #255.
* Merge branch 'master' of github.com:waylan/Python-MarkdownWaylan Limberg2014-01-124-0/+27
|\
| * Merge pull request #267 from ryneeverett/attr_list-tablesWaylan Limberg2014-01-114-0/+27
| |\ | | | | | | tables and attr_list compatibility
| | * tables_and_attr_list testryneeverett2014-01-113-0/+25
| | |
| | * tables and attr_list compatibilityryneeverett2013-11-131-0/+2
| | |
* | | Improved multiline comment parsing.Waylan Limberg2014-01-125-12/+55
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #257 and slightly alters comment parsing behavior. Unlike self-closing tags, a comment can contain angle brackets between the opening and closing tags. The greaterthan angle bracket at the end of the first block should not be mistaken for closing the comment. Need to actually check for a comment closing tag (`-->`). If one if not found, then the comment keeps going (to the end of the document if nessecary) just like in HTML. That last bit is a slight change from previous behavior, but should be unsurprising as that's how broswers parse html comments. And as far as I can tell, more implementations follow this behavior than any other. The ones that don't seem to be all over the place.
* | No longer percent encode spaces in urls.Waylan Limberg2014-01-093-4/+3
| | | | | | | | | | | | | | | | | | | | | | The current implementation was wrong as it also percent encoded query strings (which should be plus encoded) and calling urllib.quote on the path (and urllib.quote_plus on the query string) assumes the url is not already encoded. What if the document author pasted a url that was already encoded? She probably did not intend for `%20` to become `%2520`. Or did she? It is now clear to me why many implementation do nothing to urls. Just pass them though as-is. To bad if they are not valid HTML. HTML authors have to encodee their own urls, so I guess markdown authors have to as well.
* | Only escape ESCAPED_CHARS.Waylan Limberg2014-01-093-1/+25
| | | | | | | | | | | | Leave all other chars prefaced by a backslash alone. Fixes #242. Not sure why I thought that I needed to add another backslash. Thanks for the report and the test case @mhubig.
* | Address various depreciated APIs in PythonWaylan Limberg2014-01-084-16/+16
| | | | | | | | | | This mostly revolves around old APIs for ElementTree, but includes a few others as well. Fixes #254. Thanks for the report.
* | Merge pull request #274 from ajdavis/highlight-linesWaylan Limberg2014-01-075-11/+178
|\ \ | | | | | | Add feature for emphasizing some lines in a code block.
| * | Document hl_lines feature for fenced_code and codehilite extensions.A. Jesse Jiryu Davis2014-01-072-0/+36
| | |
| * | Allow single as well as double quotes for hl_lines.A. Jesse Jiryu Davis2014-01-073-17/+23
| | |
| * | Support syntax for highlighted lines like: ```python hl_lines=“1 3”A. Jesse Jiryu Davis2014-01-063-8/+47
| | |
| * | Add feature for emphasizing some lines in a code block.A. Jesse Jiryu Davis2014-01-033-11/+97
| | | | | | | | | | | | A code blocked headed by “:::python{1,3}” now emphasizes the first and third lines. With fences enabled, ```python{1,3} has the same effect.
* | | Merge pull request #275 from geekman/masterWaylan Limberg2014-01-053-1/+22
|\ \ \ | |/ / |/| | Fixed parsing of brackets within inline image titles
| * | Fixed parsing of brackets within inline image titles.Darell Tan2014-01-053-1/+22
|/ /
* | Fixed silly spelling errors.Waylan Limberg2014-01-011-6/+6
| | | | | | Must remember to spellcheck everything I type.
* | Updated footnote documentation for clarity.Waylan Limberg2014-01-011-8/+21
| | | | | | This addresses a misunderstanding reported in issue #273. The behavior has not changed. The docs just better reflect the actual behavior better. Apparently using the word "definition" both for footnotes and definition lists was an unfortunate coincidence that created confusion. We now use the term "footnote content".
* | Merge pull request #266 from ryneeverett/issue52Waylan Limberg2013-12-233-22/+24
|\ \ | | | | | | miscellaneous issue52 improvements
| * | Miscellaneous improvements and bug fixes.ryneeverett2013-11-193-22/+24
| |/
* | Merge pull request #272 from cjrd/masterWaylan Limberg2013-12-231-3/+2
|\ \ | |/ |/| added missing 's' to wikilinks documentation
| * added missing 's' to wikilinks documentationColorado Reed2013-12-221-3/+2
|/
* Update reference.txtWaylan Limberg2013-10-231-1/+1
| | | Fixed #261. Thanks for the report @mpvharmelen.
* Merge pull request #260 from ryneeverett/masterWaylan Limberg2013-10-146-57/+330
|\ | | | | Issue #52 Patch -- Markdown Inside HTML Blocks
| * Issue #52ryneeverett2013-10-146-57/+330
|/
* Merge pull request #252 from mitya57/masterWaylan Limberg2013-09-2910-47/+78
|\ | | | | Enable anchorlinks in Python-Markdown documentation
| * toc: insert `¶` instead of raw unicode characterDmitry Shachnev2013-09-292-7/+7
| |
| * Mention new option in toc.txtDmitry Shachnev2013-09-291-0/+2
| |
| * Add tests for the previous two commitsDmitry Shachnev2013-09-254-10/+23
| |
| * Add new "permalink" option to toc extensionDmitry Shachnev2013-09-253-15/+34
| | | | | | | | and use it in our docs
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 17:05:20 +0000