| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\
| | |
| | | |
tables and attr_list compatibility
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
This mostly revolves around old APIs for ElementTree, but includes a few
others as well. Fixes #254. Thanks for the report.
|
|\ \
| | |
| | | |
Add feature for emphasizing some lines in a code block.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| |/ /
|/| | |
Fixed parsing of brackets within inline image titles
|
|/ / |
|
| |
| |
| | |
Must remember to spellcheck everything I type.
|
| |
| |
| | |
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".
|
|\ \
| | |
| | | |
miscellaneous issue52 improvements
|
| |/ |
|
|\ \
| |/
|/| |
added missing 's' to wikilinks documentation
|
|/ |
|
|
|
| |
Fixed #261. Thanks for the report @mpvharmelen.
|
|\
| |
| | |
Issue #52 Patch -- Markdown Inside HTML Blocks
|
|/ |
|
|\
| |
| | |
Enable anchorlinks in Python-Markdown documentation
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
and use it in our docs
|
| |
| |
| |
| | |
and use it in all extension that need parsing bool config values.
|
|\ \
| |/
|/| |
Update __init__.py
|
|/
|
| |
spelling.
|
|\
| |
| | |
Typo fix
|
| | |
|
|\ \
| | |
| | | |
Add missing "s" to wikilinks documentation. Fixes #250.
|
| | | |
|
|/ /
| |
| |
| | |
This fixes #250.
|
|\ \
| |/
|/| |
Fix: "AttributeError: 'dict_items' object has no attribute 'sort'"
|
|/
|
|
| |
Happens on pip install with Python 3.
|
|\
| |
| | |
fix typo
|
|/ |
|
|
|
|
|
|
| |
Previously, the code was ignoring whether this was a new term when determining
whether the currect item should be loose or not. Fixes #243. Thanks for the
report @Anomareh.
|
|\
| |
| | |
Typo in util.py
|
|/
|
| |
implemenation -> implementation
|
|
|
|
|
| |
Not sure why I was using global variables here. Anyway. Fixed now.
Thanks to Andrew for pointing it out.
|
|
|
|
|
| |
Since adding the new smarty extension, the nex release it more than just a
bugfix release.
|
|
|
|
| |
It was previously marked pendingdeprecation in v2.3. Now deprecated.
|
| |
|
|
|
|
|
|
|
|
|
| |
Setting output_format must happen after extensions are loaded. Only in that
way can an extension register a serializer so that it will then be available
to be used with the output_format keyword. A test has been added to avoid
this regression from happening again in the future.
Fixes #238, partially reverses commit 41cc055 and provides a better fix for
|
|
|
|
|
|
|
| |
It is up to the markdown code (and extension authors to make sure tags are
of the correct case (there may be cases were an extension might need to
mix cases - which should be preserved). Fixes #237. Thanks for the report
@eichin.
|