Proposed table specification (long!)

Thomas Leitner t_leitner at
Wed May 18 04:06:52 EDT 2011

On 2011-05-17 19:49 -0400 Michel Fortin wrote:

> What we really need is an effort in the style of HTML5's HTML parsing

> algorithm which provides an unambiguous definition of how things

> should be parsed. Heck, I started one a while ago for Markdown Extra,

> first by creating a tool to be able to evaluate what each

> implementation do when encountering an edge case (Babelmark, which is

> now hosted at <>), then by starting

> writing such a specification (see

> <>). Then I stopped because I

> realized it'd be too long and that I had many more interesting

> projects I could do in that free time.

You may also look at the syntax specification for kramdown (see
<>) which *should* provide an
unambiguous reference to how kramdown parses a Markdown (kramdown)

-- Thomas

More information about the Markdown-Discuss mailing list