Hi Ian, To expand on my comment that ExtendedSyntaxParser doesn't always play well with other extensions, I added a section to the MarkdownSyntax talk page: http://www.mediawiki.org/wiki/Extension_talk:MarkdownSyntax#Incompatibiliti… Basicall (in summary) ExtendedSyntaxParser will strip out HTML comments <!-- like this --> from the rendered wiki page. HTML comments are already stripped out of wikitext when rendering a page, so for a vanilla install this poses no problem. However, if an extension adds HTML comments to an article's rendered body, they'll be stripped and this can interfere with functionality. For example, this would break WikiArticleFeeds (another extension of mine). I've updated the instructions for the UsenetSyntax extension to include downloading and installing ExtendedSyntaxParser, which you can get here: http://jimbojw.com/wiki/index.php?title=ExtendedSyntaxParser I haven't documented this extension on MediaWiki.org (or my own site) due to the HTML comment parsing problem I indicated above. As far as I can tell, there's no good reason why ESP and TabbedData couldn't live in perfect harmony. I have no evidence to support Simon's assertion that they don't. -- Jim R. Wilson (jimbojw) On 5/29/07, Ian Smith &lt;johantheghost(a)yahoo.com&gt; wrote:

Yeah - that call-time pass-by-reference warning refers to the practice of passing an argument to a function by reference using the &$varname syntax. I've updated the extension to fix this, so if you re-download it the problem should go away. -- Jim On 5/29/07, Ian Smith &lt;johantheghost(a)yahoo.com&gt; wrote:

I haven't looked closely at the TableEdit code - but if I'm reading your message correctly, then no, it shouldn't conflict. -- Jim On 5/29/07, Jim Hu &lt;jimhu(a)tamu.edu&gt; wrote:

Hi Simon, I took a look at your extension and started making modifications. After a while at that, I realized that it would probably be more useful (for my own purposes) to extend the original design to support multiple syntaxes and bypass the Parser's wikitext engine rather than just hijacking it at the front. The result is an extension called AlternateSyntaxParser, which supports both Markdown and Textile out-of-the-box and allows per-page inline configuration as well as a site-wide default. For more details, see MediaWiki extension page: http://www.mediawiki.org/wiki/Extension:AlternateSyntaxParser Check out the developer notes section for a description of how the implementation differs from MarkdownSyntax. Or, feel free to review the source code which is available here: http://jimbojw.com/wiki/index.php?title=AlternateSyntaxParser I'll be happy to answer any questions - thanks! -- Jim R. Wilson (jimbojw) On 6/2/07, Simon Dorfman &lt;emaillists(a)simondorfman.com&gt; wrote: