similar to: Problem with UL followed by OL

I'm currently attempting to write a spec for parsing Markdown Extra, and since one goal is to minimize the differences in output between implementations, I've made a tool allowing me to compare who does what for any given input. I hope this can also facilitate future discussions about the syntax. So here's Babelmark, a testbed for various Markdown implementations were you

Hello, As I am using markdown to write documentation, I am often tempted to make links to terms in definition lists. Since this is not possible for now (at least in php markdown extra), I was wondering if this could be a common addition in major implementation supporting definition lists. the syntax would be term {#id} : definition This syntax tries to follows current convention and

A lot of people have expressed interest in combining math features with Markdown, but I am not aware of any real developments from these requests. I was looking around and toying with [ASCIIMathPHP](http:// www.jcphysics.com/ASCIIMath/) and integrated it with MultiMarkdown and my xhtml2latex XSLT transforms. You can include math as an inline formula by using a markup similar to inline

On Feb 26, 2009, at 9:51 AM, I wrote: > I can see that really opened a can of worms here. Sorry about that. > I'll have to move up my plan to formally propose a table syntax. The > comment that started this sub-thread was a throwaway line, really. I > probably should have omitted it. And then, on Feb 26, 2009, at 3:28 PM, John Gruber wrote: > 3. A hypothetical official

I am glad to see support for footnotes working its way into other implementations of Markdown! However, I have a couple of issues. Issue # 1. There appears to be a bug in the footnote parser that causes material following the footnote to be included as part of the footnote. For example: < Example Section > ## Metadata ## First, take a look at the overall structure of the document.

I just received a [bug report] for Python-Markdown complaining that colons are used in the ids of footnotes. For reference, we [output] the same format at PHP Markdown Extra. The general complaint is that the colon in the id attribute (`id="fnref:1"`) causes jquery to choke when referencing that id from javascript because jquery uses colons to indicate pseudo elements (as does CSS). As

Markdowners, just a short heads-up to a newly released Markdown implementation: "pegdown" (http://github.com/sirthias/pegdown) implements a Java Markdown-to-HTML processor based on a PEG parser with the grammar being based on John MacFarlanes C implementation "peg-markdown". pegdown uses "parboiled" (http://www.parboiled.org) for the actual parsing work and, as

I just recently became aware of MarkdownTest_1.0.3 (which discount fails, due to the behavior of code blocks changing from "leave whitespace alone except on the first line" to "leave whitespace alone", and the addition of a new kind of magic link that doesn't seem to be documented); is this the most recent version of the test suite, or is there a newer one out there?

It appears that Markdown will process ampersands contained within HTML comments if that comment is part of a markdown paragraph, but will not when that paragraph is contained within an HTML block of it's own (and therefore ignored by Markdown.) For example: This is a markdown paragraph with a comment that *will* be processed <!-- This & *will* be converted -->

How can we improve URL detection in Markdown? I posted a question on Stack Overflow and happened to click a URL in my post. To my surprise, it wasn't functional, and it took three different, nonintuitive manipulations before I achieved a functional URL. Stack Overflow says "not my problem", so I'm deferring to Markdown itself. Here's a

Hi, I have written my own implementation of markdown in Scala. I only later realized there is already one ( <http://tristanhunt.com/projects/knockoff/> ), but I put quite some work into mine and I think it is never bad to have alternatives, so I wanted to release it anyway. I want to use the same BSD License as the original markdown, but before I put it out into the wild I wanted to ask

On the suggestion for double-spaces, I share the general 'oh no'. I see an explosion of people with iPads etc trying out Markdown in education because formatting sucks on iPads. They struggle with needing new lines (see recent post for an example). In short, they struggle with white-space (invisible) mark-up. Added to that, frequently cut and paste leaves double spaces (eg in BBEdit

It would be useful if defining headers (either Setext and atx style), if Markdown would also generate corresponding anchors: ## This is an H2 ## would create: <a name="This is an H2"/> <h2>This is an H2</h2> Or something like that. Or is that available some different way? Thanks, Jeremy C. Reed

Hi! I wrote an markdown interpreter in C. It should support most of the features markdown.pl has (hopefully). Please report any bugs. It would be a good idea if you could test the interpreter with you're own documents and report any differences to markdown.pl Mercurial: hg clone http://s01.de/~gottox/hg/cmarkdown/ Tarball: http://s01.de/~gottox/files/cmarkdown-0.3.tar.gz regards Gottox

Hello, What should the following input produce? Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling with <g> and thus at least a visual similarity to German; English and Frisian have shifted g to [j] before palatal vowels The Dingus says: <p>Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling

I'm using Michel Fortin's MDTest cases to rewrite my html2text.php script. Just now I stumbled upon this bug (in PHP Markdown at least): # Input: Backtick: ``\``` # Output: <p>Backtick: ``&#96;``</p> # Should-Be Output: <p>Backtick: <code>`</code></p> If you (Michel) are already aware of this, just ignore me ;-) -- Milian Wolff

recently though about image captions, then i realized that this could be achiebed by Markdown Extra's definition list feature:  : here goes the *caption* What do you think? -------------- next part -------------- An HTML attachment was scrubbed... URL:

PHP Markdown v 1.0.1i and PHP Markdown Extra v 1.1.5 generate invalid HTML for code blocks Take this input: paragraph codeblock Markdown will generate: <p>paragraph</p> <pre><code>codeblock </pre></code> Notice the wrong position of the closing code tag. -- Milian Wolff http://milianw.de

I'v encountered what seems to be a bug in PHP Markdown v1.0.1k. Given a UTF-8 with a BOM, the first line is not parsed. A brief search revealed a bug report for a similar issue in python- markdown: > I'm using the markdown.py command to generate HTML from Markdown > documentation and I've found that if a utf-8 file starts with a BOM > a paragraph is generated

The following benchmarks have been obtained using the TextMate manual as the input source: <http://macromates.com/textmate/manual/source.tbz> Using PHP Markdown, parsing the 24 files separately (with the reference file appended to each of them), I get this (on an iBook G4 1.2 Ghz): Total Avg. Min. Q1. Med. Q3. Max. Parse Time (ms):