Proposed table specification (long!)

[Thomas Leitner]

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 <http://babelmark.bobtfish.net/>), then by starting

> writing such a specification (see

> <http://michelf.com/specs/markdown-extra/>). 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
<http://kramdown.rubyforge.org/syntax.html>) which *should* provide an
unambiguous reference to how kramdown parses a Markdown (kramdown)
document.

-- Thomas