# Is markdown="0" only used by kramdown?

**URL:** <https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995>\
**Category:** Extensions\
**Created:** [January 26, 2016, 6:50am UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995 "2016-01-26T06:50:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/martin/32/838_2.png) [@Martin](https://talk.commonmark.org/u/Martin)\
**Post date:** [January 26, 2016, 6:50am UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995/1 "2016-01-26T06:50:31Z")

</div>

I am currently using `markdown="0"` for span tags to prevent the Markdown parser from changing TeX which is supposed to be parsed by MathJax (see [Ignore LaTeX-like Math mode (or parse it)](http://talk.commonmark.org/t/ignore-latex-like-math-mode-or-parse-it/1926) for a related discussion).

I am now thinking about changing from the static site generator Jekyll to Pelican. Hence I’m thinking if this approach might be a problem.

---

<div class="post-metadata">

**Author:** ![cben](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/cben/32/407_2.png) [@cben](https://talk.commonmark.org/u/cben)\
**Post date:** [January 26, 2016, 4:34pm UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995/2 "2016-01-26T16:34:34Z")

</div>

[_disclaimer: following is all untested._]

Pelican is using Python-markdown, which defaults to not parsing inside HTML, but [has (buggy) support](https://github.com/waylan/Python-Markdown/issues/52) for `markdown="1"` with the `extra` extension, which Pelican [enables by default](http://docs.getpelican.com/en/latest/search.html?q=md_extensions).  
Unfortunately, it seems to ignore the attribute value — `markdown="0"` makes it _parse_ content as if it was `markdown="1"`. So using `0` would not be portable to Pelican, you’d have to drop the attribute. I assume Python-Markdown’s author would welcome a fix.

But instead of protecting math with the `<span>$A_{i,j}$</span>` trick, you can teach Python-Markdown / Pelican to not parse inside math.  
See [https://www.ceremade.dauphine.fr/~amic/blog/mathjax-pelican-ii.html](https://www.ceremade.dauphine.fr/~amic/blog/mathjax-pelican-ii.html).  
I’m not sure but it seems you need both [https://github.com/getpelican/pelican-plugins/tree/master/render\_math](https://github.com/getpelican/pelican-plugins/tree/master/render_math) Pelican plugin and [https://github.com/mayoff/python-markdown-mathjax](https://github.com/mayoff/python-markdown-mathjax) extension (or similar, e.g. [https://github.com/mitya57/python-markdown-math](https://github.com/mitya57/python-markdown-math)).

---

<div class="post-metadata">

**Author:** ![Martin](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/martin/32/838_2.png) [@Martin](https://talk.commonmark.org/u/Martin)\
**Post date:** [January 26, 2016, 4:50pm UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995/3 "2016-01-26T16:50:16Z")

</div>

Thank you very much! I will have a look at the links as soon as other things are ready for the migration (might take a while). It’s good to have a starting point 🙂

---

<div class="post-metadata">

**Author:** ![Crissov](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/crissov/32/1455_2.png) [@Crissov](https://talk.commonmark.org/u/Crissov)\
**Post date:** [January 26, 2016, 11:15pm UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995/4 "2016-01-26T23:15:42Z")

</div>

Also, all implementations present in [Babelmark](http://johnmacfarlane.net/babelmark2/?normalize=1&text=*foo*+%3Cspan+markdown%3D%220%22%3E+*bar*+%3C%2Fspan%3E+%3Cspan+markdown%3D0%3E+*baz*+%3C%2Fspan%3E+%3Cspan+markdown%3D%221%22%3E+*quuz*+%3C%2Fspan%3E+%3Cspan+markdown%3D%22off%22%3E+*dolor*+%3C%2Fspan%3E) that support `markdown="0"` (i.e. Kramdown and Maruku) fail to parse `markdown=0`.

---

<div class="post-metadata">

**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\
**Post date:** [January 27, 2016, 12:19pm UTC](https://talk.commonmark.org/t/is-markdown-0-only-used-by-kramdown/1995/5 "2016-01-27T12:19:03Z")

</div>

I’ve added this topic to the [list of proposed extensions](https://github.com/jgm/CommonMark/wiki/Proposed-Extensions) under “Disabling Syntax Parsing”.