Re:RFC 7764 – Guidance on Markdown
by jessaustin on Wednesday December 14, 2016 @04:30PM
(#13179835)
Well that's one doodad, and apparently it has had the effect I predicted. Never mind, go ahead and have fun with your new super-markdown. One rather doubts it will displace actual markdown anytime soon.
That's exactly the problem: there is no "actual Markdown". Just a bunch of mutually incompatible competing implementations.
If something like CommonMark had existed from the beginning, we wouldn't have this issue because everyone would be following the standard.
Re:RFC 7764 – Guidance on Markdown
by marssaxman on Wednesday December 14, 2016 @08:49PM
(#13181662)
What is a "code fence"?
It's an alternate way of annotating code blocks which doesn't require you to indent every line (because that can be tedious for longer code snippets), and allows you to explicitly specify the language to use for syntax highlighting.
Example:
```javascript
// JavaScript code here
```
It's used extensively on GitHub.
Re:RFC 7764 – Guidance on Markdown
by marssaxman on Friday December 16, 2016 @02:08AM
(#13191621)
Thanks. I've seen that but hadn't connected the name to the syntax.
Oh, but there have. For instance, code fences are not part of the original markdown spec, but are commonly supported in just about every implementation out there, and are rendered in about [7 different ways][1] depending on which converter you're using.
Play around for a little in BabelMark and you'll see why a standard is needed.
[1]: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60%6...