Agreeing on "Historical Markdown" (was: Re: text/markdown effort in IETF (invite))

[Michel Fortin]

Le 11-juil.-2014 à 4:54, Sean Leonard <dev+ietf at seantek.com> a écrit :

> Since we cannot reach consensus on what ought to be "Standard Markdown" today, can the community reach consensus on "Historical Markdown"--of which I propose three working definitions?
> 
> * Classic Markdown: The Markdown syntax or Markdown.pl implementation, as implemented by John Gruber, in 1.0.1, with all ambiguities, bugs, frustrations, and contradictions. [In cases that the syntax and the tool contradict, we come up with a way to resolve the contradictions.]
> 
> * Original Markdown: The Markdown syntax or Markdown.pl implementation, as implemented by John Gruber, in 1.0.2b7, with as many of the ambiguities, bugs, frustrations, and contradictions fixed as he actually fixed (or failed to fix) them. Aka "Markdown Web Dingus".
> 
> * Idealized Markdown (aka Historical Standard Markdown): The Markdown that everyone can agree is the way Markdown "should have been" back when there was One True Markdown. Basically this is Original Markdown with its faults duly recognized and corrected...many of these faults having been corrected in practice in divergent implementations (Markdown Extra etc.) but never officially recognized in Original Markdown.
> 
> 
> I cannot say which of these three is better...but by recognizing these three as common points, we can then start to compare on the same page.

You might also call the first two "Markdown 1.0.1" and "Markdown 1.0.2b7" for simplicity's sake. As for the idealized version, that's what I call "Markdown" personally, or "plain Markdown" when I need to disambiguate.

Wasn't 1.0.2b8 the last one though? Why is the Dingus running 1.0.2b7? Babelmark 2 has 1.0.2b8.


-- 
Michel Fortin
michel.fortin at michelf.ca
http://michelf.ca