search for: takhteyev

> Anyway, a spec for Markdown Extra would contain a spec for Markdown as > well, wouldn't it? I think the whole enterprise would be a lot more valuable, if we produce a combined spec, which would be self-contained, and call it Markdown 2.0. I don't think we necessarily need a formal grammar. What we need is to create a document, starting with "Markdown Syntax" perhaps,

On 10/6/07, Lou Quillio <public at quillio.com> wrote: [snip] > Wish there were an 'Extra' for Python. > There is. Sort of. Python-Markdown has an extension interface [1]. There's a number already available and its fairly easy to write your own. I've slowly been adding many of php extra's features [2]. Unfortunately, some things are still hard, but were working to

Howdy, I've been thinking a lot about definition list syntax, and what I did and didn't like about the PHP Markdown Extra syntax (which seems to be a de-facto standard, discount notwithstanding, yes?). What I came up with is a single character change to the PHP Markdown Extra syntax. I just published a detailed explanation of my thoughts and reasoning for this on [my

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