Extension talk:MarkdownSyntax

Incompatibilities
First of all, good work Simon! I hope that one day the format of a particular wiki article becomes a user choice - I think your MarkdownSyntax extension is a step in this direction.

Regarding my comment that my ExtendedSyntaxParser is "not amicable to running along side certain other kinds of extensions", I'd like to expand on that a little. The reason it doesn't play well is that it uses the PHP SAX XML parser to identify blocks of markup that exist outside any tags or attributes. Unfortunately, the parser doesn't provide a way to detect and handle XML/HTML comments &lt;!-- like this --&gt;. It seems to just skip over them altogether.

So in order to play nice with extensions which inject XML comments into the article body, the ExtendedSyntaxParser really needs to be able to break apart the incoming text around these comments and preserve them in the output.

I hope that makes sense. It has been my intent for some time to revisit the code and figure out how to preserve the comments so that this is no longer an issue. I've been holding off releasing the ExtendedSyntaxParser here (on mediawiki.org) until I've solved that problem as I feel that it's a significant drawback to its usage.

The good news, however, is that since you're using ExtendedSyntaxParser rather than recreating the functionality yourself, when I do get around to fixing ESP, MarkdownSyntax will immediately benefit. --Jimbojw 14:23, 29 May 2007 (UTC)

Source of bugs
I suspect that the reason for the broken [edit] links is that Markdown doesn't assign id's to any of its headers. --Anonymous