Michel Fortin

I guess it's fixed in Yellow, but this issue about double-encoding is still present in PHP Markdown when `no_entities = true`, and is still worth fixing. So I'll keep it...

I've been following requests for classes and id attributes with interest. For some constructs, like headers, it's pretty obvious what the syntax should be. But I've restrained myself from implementing...

@tobiastom The reason Markdown allows HTML is so you can do everything you can do with HTML without having to reinvent a syntax for every HTML feature. It's perfectly fine...

I think the right margin style is a good argument for putting the attributes at the end. Attributes for headers follow the header, same thing for images and links. Also,...

After the Markdown-to-HTML conversion, do this: ``` $result = str_replace('

Acknowledged. That's a bug in need of fixing. It might take a while to fix this though, as I think it'll require an overhaul of the span-level parser so that...

Seems to work fine on the [dingus](https://michelf.ca/projects/php-markdown/dingus/). Which version of PHP Markdown are you using?

@Kovah Is Wikitten using the `Markdown` or the `MarkdownExtra` parser? Fenced code blocks are not a base feature of Markdown and are only available with Markdown Extra.

For all I can see, the above parses correctly with Markdown Extra. This can be tested on the [PHP Markdown Dingus](https://michelf.ca/projects/php-markdown/dingus/). Perhaps the input above isn't the actual input given...

If I copy-paste the Markdown source for that document in the [Dingus](https://michelf.ca/projects/php-markdown/dingus/), set the filter to PHP Markdown Extra, and hit Convert, I get a correctly formatted code block. So...