Resolves #244

There are a few aesthetic options about how one might try to allow different language notes in footnotes in markdown. I find it a bit hard to allow this in a nice way from direct command line usage, so I've chosen an implementation through in-interpreter use.

The default footnote title is "Jump back to footnote %d in the text." To change, I propose the following.

markdowner = markdown2.Markdown(extras=["footnotes"])
markdowner.footnote_title = "Retournez vers footnote %d. "
markdowner.convert(text)

The extra information is passed as an attribute of the markdown2.Markdown class used for conversion. If there is a format problem, then I revert to the default.

Note: I'm having trouble running tests on my own [I get 22 failures on the current master branch], so I expect to need to clean up a few things first.

Hey I have installed markdown2 using PIP in one of my Docker images and I can invoke it like this: markdown2 input.md > output.html, but I am not able to use markdown2 as a command on Windows nor on WSL when installed through PIP for some reason.

Is there any info on using the TOC extra through CLI? I ran the same script with the TOC extra in my CI pipeline with the Docker image where I am able to invoke markdown2 as a command and pipe the output to a file and it didn't get embedded into the file, so I suppose I can only wrap the invocation in a Python script and write the files myself?

Parsing the Markdown Syntax document 1000 times...
Mistune: 12.9425s
Misaka: 0.537176s
Markdown: 47.7091s
Markdown2: 80.5163s
cMarkdown: 0.680664s

http://lepture.com/en/2014/markdown-parsers-in-python

On the latest release (2.3.8) a payload like this one can lead to xss and bypass safe_mode when set to true.

<lol@/ //id="pwn"//onclick="alert(1)"//**abc**

The Problem: I think its due to just bad regex's not detecting non alphanumeric tags.

For FIPS[0] related installation, the MD5 modules are unavailable, to the tune of md5() raising an exception. Using sha256() from the same hashlib passes the same make test and is now FIPS compliant.

[0] http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm

I've been a longtime user of python-markdown2 and like the way it just works. I'd like to start using it in a Python 3-based project, but it seems as if there is no goal of porting to Python 3 (I last checked it out a year or so ago -- at that time I did my own port).

Would you like me to contribute the port I have made, or is there no real motivation to support Python 3 at this time?

I've been using markdown2 a lot in a recent project to convert a \LaTeX document generator into an online research environment. Combined with MathJax, Markdown2 with the footnotes extension is pretty much perfect. However, the one thing that Markdown can't do is number figures and tables. This is pretty much essential in research papers and is also a useful feature in other styles of documentation.

Whilst I understand that there are way too many "standards" for Markdown, I wanted to add an extension to handle figure, table and equation numbering to Markdown. What I've done (in a relatively few lines of code) is add a preprocessor which generates generic "counters" which can be used to number equations. The syntax is as follows.

When you first want to label an item (figure, table, image whatever), you add a markdown item

     [#counter_id](:item_tag)

and when you want to refer to it in the text you use [:item_tag]. Here both counter_id and item_tag are "words" in the regex sense.

During conversion, the first pass identifies all the labels and creates counters as required and increments them if they're already created. During the second pass, the counter integers are replaced in the text. In principle, each counter can have it's own css style associated with it. At present it doesn't hyperlink the references to the original item but that would be easy to add.

The code is about 40 lines of Python.

So the issue is: Is this more generally useful? There's almost no support for "exhibit numbering" in any Markdown converters -- which is why I had to write my own. I could certainly add this as an "extra" in markdown2 if there was general support for it but I don't want to add useless cruft to a project. Comments?

This is a fix for issue #276. There's a failure in converting markdown lists that have fenced code blocks in them, because the indentation of the fenced code block is not accounted for unless syntax highlighting is enabled.

I also pulled out the code for substituting code blocks with a lexer into its own method so it is a little easier to read.

Following the syntax used in Wikidot:

||~ Head1 ||~ Head2 ||
||  cell1 ||  cell2 ||

Also added indenting to match the format found when using the tables extra.

Are there any plans to implement meta data feature (maybe like the one linked?). If not, would you accept a patch for that? And if yes what should the api look like?

Issue

The code block

``` c const var = foo() ```

is being converted to:

<pre><code>&lt;div class="codehilite"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="k"&gt;const&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;var&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;foo&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="w"&gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
</code></pre>

and should be converted to:

<div class="codehilite">
    <pre><span></span><code><span class="k">const</span><span class="w"> </span><span class="n">var</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">foo</span><span class="p">()</span><span class="w"></span>
    </code></pre>
    </div>

Observation

During the conversion, the input text passes through function _do_code_blocks(self, text) which hashes the <div class="codehilite"></div> and it's content and wraps them in <pre><code></code></pre>

Output of _do_code_blocks(self, text):

'<pre><code>md5-353f226db77851404d4ad30e2cb646b8\n</code></pre>\n'

Output of _do_code_blocks(self, text) is passed as input through function _unescape_special_chars(self, text) and hash is converted to following output:

<pre><code>&lt;div class="codehilite"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="k"&gt;const&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;var&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;foo&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="w"&gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
</code></pre>

Steps to reproduce:

1. create markdown file and paste the text: ``` c const var = foo() ```

2. python /lib/markdown2.py --extras fenced-code-blocks foo.md > foo.html

Example:

# Introduction

...
<!-- every heading after a page-break is missing in toc -->
<div style="page-break-before: always"></div>

## Main Features
...

Instead of using a node.js based solution (e.g. link-preview-generator), I am wondering how I can generate link preview during the processing of markdown. There appears to modules (e.g. linkpreview) that perform the actual uplifting so maybe it is not too difficult to add an extra for this.

This PR fixes #458.

It works by capturing and reading each line of each test runner's stderr in real time. If the line contains a warning it is saved to be re-printed later. Once all of the tests have finished, the warnings are printed to stdout along with the version of Python that raised the warning.

See

https://github.com/trentm/python-markdown2/pull/455#issuecomment-1182130274

https://github.com/trentm/python-markdown2/pull/455#issuecomment-1182538886

Maybe we print warnings when pygments isn't installed locally at the end of the test run. Or do something to make it clear not all tests have ran.

Hi there.

First, thank you for your great work :heart:

Following this discussion #382 , I wanted to try to make the extra part more flexible. I realized it's quite hard to follow the code because everything is packed in a huge file.

This PR is a first step to refactor the code and to then make the extras more flexible/pluggable.

Wolud you agree to split this code? I don't mind about the name of the files if you don't like this organization. But I think it would be nice to avoid having just one big pile of code.

This is "preliminary" pytest port of the testlib.py code, leveraging pytest and its ecosystem.

It supports running all (unchanged) tests (tm-cases, markdowntest-cases, php-markdown-cases and php-markdown-extra-cases).

pytest itself provides extensive support for code quality (coverage, unitest xml etc.).

This change also integrates the workflow actions.