- Moving `code_block_content_func` configuration variable to regular Markdown parser, now using it to convert the content of indented code blocks to HTML too.
- Fix for code block class name and special attribute blocks together.
- Updated the fenced code block syntax in the HTML block parser (so it correctly skips those code blocks).
- Updated Readme.md to explain the changes.
All URLs are now passed through the `encodeURLAttribute` function, which applies the filter as necessary. If the filter function changes the URL of an automatic link, this is reflected in the text of the link too.
Inline- and reference-style email links now benefit from the entity obfuscation since `mailto:` is now detected in `encodeURLAttribute` and it triggers the entity obfuscation.
Fixes#85.
HTML block parser was confusing backtick fenced code blocks with
code spans, which has no consequence most of the time but could
be problematic if you're writing code spans inside of the code block.
Code span markers are now matched only when backtick fence matching
has failed.
Fixed an issue were two consecutive fenced code blocks with no
blank line between them which was causing the next paragraph to
become a code block (with both tilde and backtick fences).
Removing the additional code that I applied previously to implement the `data-lang` attribute. In retrospect, this was a bad idea; as the existing implementation does a good job with this already when used properly.
Many thanks to Michel Fortin for his help in accomplishing these changes :-) I hope this might be merged into the official copy at some point in the future.
- Adding support for GFM backticks ``` (for fenced code blocks); in additional to ~~~ already supported in Markdown Extra.
- Adding support for GFM language marker; e.g. ```php
Added configuration variable to enable enhanced ordered list.
Enhanced ordered list is disabled by default.
Removed extra 'start="1"' when the list's starting value is 1
Removed 'start="1"' on unordered lists
now start with the first number given. For example, if you start your
list in Markdown as follows:
2. second list item
3. third list item
then Markdown will produce this:
<ol start="2">
<li>second list item</li>
<li>third list item</li>
</ol>
