I "relented" and added support for GFM (```) fenced code blocks to MultiMarkdown.
I prefer the original GFM syntax, precisely because it is also a valid code span. This means that a Markdown parser without knowledge of fenced code blocks will still do the right thing, except handle the specified language for syntax highlighting. Fletcher -- Fletcher T. Penney [email protected] On Sep 27, 2013, at 7:48 AM, Michel Fortin <[email protected]> wrote: > I get a lot of requests for Github-style fenced code blocks in PHP Markdown > Extra. While I despite the syntax -- it also happens to be a valid code span! > -- I wonder whether I should relent on this. It seems to be bothering a lot > of people (even those who know about the tilde-based fenced code block > syntax). > > In Github-Flavored Markdown, a code block works like this: > > ```php > some php code > ``` > > Replace those backticks with tildes and you get a valid fenced code block in > PHP Markdown Extra: > > ~~~php > some php code > ~~~ > > Of course, now Github also supports tilde for fenced code blocks. But their > documentation only mention the backtick-based syntax. > <https://help.github.com/articles/github-flavored-markdown> > > If take a look at Babelmark 2, it seems that most implementations supporting > one also support the other. > <http://johnmacfarlane.net/babelmark2/?normalize=1&text=```php%0Asome+php+code%0A```%0A> > <http://johnmacfarlane.net/babelmark2/?normalize=1&text=~~~php%0Asome+php+code%0A~~~%0A> > > I wondered if some of you have any opinion to share on this. > > -- > Michel Fortin > [email protected] > http://michelf.ca > > _______________________________________________ > Markdown-Discuss mailing list > [email protected] > http://six.pairlist.net/mailman/listinfo/markdown-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
