Mat Whitney

I'm going to remove the 0.7.1 milestone from this one. At first, I thought this would be a simple feature to add, but as I consider actually coding it, it...

I like this idea, and have attempted to start it a few times, but haven't had the time to really dig into it. I think I mentioned something similar would...

Is this with the released/master version (0.7.1) or with the version in the develop branch? I'm not seeing the issue locally, so I think it may have been fixed in...

While I'm not closing the issue, I'm not sure how long this will take unless someone submits the required changes. The docs use Markdown Extra Extended, and both the Markdown...

@lonnieezell You should be able to replicate the error by reverting the tut_blog.md file to the version prior to the changeset I linked above. Or you can just modify the...

Parsedown claims to pass most of the CommonMark tests and run on PHP 5.2+. After looking at the generated code, the issue is clear in the original post. The tut_blog.md...

The document is fixed, but the parser will still generate broken code if you use the GFM-style code blocks with an opening PHP tag in the code block.

I implemented Parsedown locally, but immediately ran into an issue when I went to update the changelog. Parsedown incorrectly interprets a sequence like #793 as a heading, which makes the...

As mentioned in the commit above, I've changed the way the docs module interacts with the parser to make it easier to replace the parser (and make the parser configurable)....

OK, I believe I'm done with this, for now. The only reason I'm not closing this is because the default driver still exhibits this behavior, and the best drivers currently...