👤samlambert🕑9y🔼475🗨️89
(Replying to PARENT post)
GitHub devs & Markdown enthusiasts at large, please consider contributing some brainpower to these last remaining issues that are blocking the v1.0 release of CommonMark:
https://talk.commonmark.org/t/issues-we-must-resolve-before-...
👤erlend_sh🕑9y🔼0🗨️0
(Replying to PARENT post)
This is great! A couple of years back, there was a failed attempt at standardizing this - http://www.vfmd.org/ and http://www.vfmd.org/vfmd-spec/specification/. GitHub given it's popularity will surely succeed more.
👤simplehuman🕑9y🔼0🗨️0
(Replying to PARENT post)
It's a specification based on the commonmark specification. Both are not a formal specs. They are more of an informal specification with some edge-cases listed (in contrast to the original markdown specification which has known unspecified edgecases).
👤legulere🕑9y🔼0🗨️0
(Replying to PARENT post)
I have to wonder why this isn't done in the form of a context-free grammar, like Hitman[0] uses. Specs in English are still too vague for my liking.
👤rcarmo🕑9y🔼0🗨️0
(Replying to PARENT post)
https://github.github.com/gfm/#disallowed-raw-html-extension...
Why this? This is not a working blacklist to prevent XSS (e.g. onload="...")
👤legulere🕑9y🔼0🗨️0
(Replying to PARENT post)
This is great -- lack of a standard that was actually used (unlike CommonMark) was one of my main issues with Markdown (http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-f...) -- It's really great to see GitHub leading in this department, and it gives me hope that one day we might actually have Markdown that is portable between implementations.
👤forsaken🕑9y🔼0🗨️0
(Replying to PARENT post)
At the risk of starting a mini-flame war, is RST a more cohesive format? If one was to pick one of the two formats to start using for personal documentation, which format should one choose?
👤IgorPartola🕑9y🔼0🗨️0
(Replying to PARENT post)
Now if only org-mode could define a sane, parsable format.
👤patrec🕑9y🔼0🗨️0
(Replying to PARENT post)
HTML used to serve as a simple way to format a document. Now HTML is too complex for that purpose. Introduce markdown. In ten years, markdown will be too complex for formatting documents.
I am big of markdown in case I didn't make that clear. I love it
👤jostmey🕑9y🔼0🗨️0
(Replying to PARENT post)
This is great news! Does anybody have a recommendation for a Javascript parser for Formal GFM? (I know there are a million JS MD parsers; I'm looking for a good one that will let me serve GFM docs over HTTP and render them on the browser.)
👤dreamcompiler🕑9y🔼0🗨️0
(Replying to PARENT post)
So that's why my project wikis have suddenly stopped rendering markdown properly. I've been trying to figure out WTF was going on since yesterday!
👤charonn0🕑9y🔼0🗨️0
(Replying to PARENT post)
I'm really happy to see this. It's actually quite frustrating that although markdown is so nice, it barely has a consistent standard. It's almost impossible to use it cross-service.
Hopefully now that Github has standardised their own flavour of it (and quite a nice flavour too), more people will start to use it.
Of course there is the obligatory XKCD: https://xkcd.com/927/
👤libeclipse🕑9y🔼0🗨️0
(Replying to PARENT post)
web2py handled all of these issues and made its markup language extensible with its markmin specification: http://www.web2py.com/init/static/markmin.html
👤tomcam🕑9y🔼0🗨️0
(Replying to PARENT post)
What's wrong with http://www.vfmd.org/ ???
👤Siecje🕑9y🔼0🗨️0
(Replying to PARENT post)
Why no ~~strike out~~ in spec?
👤strikedout🕑9y🔼0🗨️0
(Replying to PARENT post)
Jeesh, about time!
👤flippyhead🕑9y🔼0🗨️0
(Replying to PARENT post)
Is it ok if I promote my domain here? I read the guidelines but it doesn't mention anything regarding self promotion.
Sorry if it ain't appropriate but anyone looking for a relevant domain (markdown.in) please get in touch or any suggestion if it is better to develop it.
👤harmonyinfotech🕑9y🔼0🗨️0
(Replying to PARENT post)
CommonMark contains this little sentence to work around its specified behavior, which is left untouched in the GFM spec:
> A renderer may also provide an option to render soft line breaks as hard line breaks.
I'd say whether or not it does this is a rather important thing to mention. When I write Markdown documents for GitHub I have to change my editor settings, only because of this.
[1]: https://guides.github.com/features/mastering-markdown/
[2]: https://help.github.com/articles/basic-writing-and-formattin...