| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Note that you can still explicitly set 'enable_attributes' and that
value will be honored regardless of 'safe_mode'. However if 'safe_mode'
is on and 'enable_attributes' is not explicitly set, then
'enable_attributes' defaults to False.
|
|\
| |
| | |
Attempted fix for issue 87
|
| | |
|
|/
|
|
| |
Elements should be inserted in the tree regardless of enable_attributes
|
|\
| |
| | |
added a test for the previous pull request
|
| | |
|
|\|
| |
| | |
Remove `<del>` and `<ins>` from block-level elements list
|
|/
|
|
| |
They are span elements. `<del>` is explicitly mentioned as such in the [markdown syntax document](http://daringfireball.net/projects/markdown/syntax)
|
|
|
|
|
|
|
|
|
| |
This allows the run method to determine if a block is or is not a match in the
midst of parsing outside of the test method. The goal is to eliminate the
often redundant test method in the future. In the interim, it remains and
if the run method returns None, the existing behavior is maintained. Returning
None may generate a DepreciationWarning later. Note that test must still return
True to even get to the run method.
|
|
|
|
| |
Also added a test. Thanks for the report.
|
|\
| |
| | |
Typo fix in doc: s/extension-configs/extension_configs/
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The documentation uses features of Python-Markdown that are not supported on
GitHub and it's better to get a source view of the docs anyway. For example,
that way comments and bug reports can reference a specific line of a file.
Of course, it makes sense for Github to render the README, so that is left
with the `.md` file extension.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is not a full Sphinx implementation. Just a limited implementation
which converts our markdown source filed to work with the default css for
Sphinx so it looks like Pythons docs.
|
|
|
|
| |
stdout is used later based on output being None. Don't try to get a jump on that.
|
|
|
|
|
| |
Also refactored the reference preprocessor to make this a little easier to
implement. Regex does more now.
|
| |
|
| |
|
| |
|
|\
| |
| | |
Allow specifying the full module name for extensions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this patch, it was possible to pass a list of extensions and
parameters to use when instantiating a new Markdown instance, but it was
not possible to give a full module name; the extension had to be a
submodule in markdown.extensions.
Now we allow giving a full module path, to make it easy to use custom
extensions which are not bundled within the markdown package. The
previous behaviour has been retained when there is no '.' in the
extension name.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
This will make it easier for extensions to subclass the list block processors
and alter their behavior. Such as the request in issue #64.
|
| | |
|
| |
| |
| | |
I forget about this now that we have a git log and release notes.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| | |
Not only does this ensure that all output matches the output_format,
but it is nessecary to run in Python 3.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Final fix to issue introduced in fix for #59. Weird stuff inside
angle brackets now also work in safe_mode='escape'. We just did the
same thing as with block html, let the (x)html searializer do the
escaping. Tests updated including the standalone test moved to match
the non-escape cases.
|
| |
| |
| |
| |
| | |
Markdown markup inside angle bracktes now gets rendered properly
in all cases except when safe_mode='escape'. Also added tests.
|
| |
| |
| |
| |
| |
| | |
Replaced the unescape method I carlessly threw in the RawHtmlProcessor.
Unfortunetly, this reintroduces the bug just fixed in commit
425fde141f17973aea0a3a85e44632fe18737996 Sigh!
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
markdown/inlinepatterns.py
|
| | |
| | |
| | |
| | | |
type.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See tests/html4_safe/html_then_blockquote.(txt|html).
It looks like having unclosed block-level html elements was causing
further processing not to happen, even in the case where we're
escaping HTML. Since we're escaping HTML, it seems like it shouldn't
affect processing at all. This changes output results in a couple
of other tests, but the new output seems reasonable to me.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Interestingly, the change to the misc/mismatched-tags test is inline with
PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
|
| | | |
|