4 ms·
The following RFC which sketches out a system for registration of markdown variants is much more interesting: https://tools.ietf.org/html/rfc7764 https://tools
by qewrffewqwfqew 11y ago
The following RFC which sketches out a system for registration of markdown variants is much more interesting:
https://tools.ietf.org/html/rfc7764 https://tools.ietf.org/html/rfc7764
Maybe, eventually, I'll be able to open a markdown textarea on a new website and be able to predict what markup will actually work!
- voltagex_ 11y agoYep, but I can't remember the difference between Chrome Markdown, Firefox Markdown and Edge Markdown. - me, in the future. I have a hard enough time with GitHub Markdown and Reddit Markdown, as it is.
- codinghorror 11y agoObligatory: http://commonmark.org http://commonmark.org
- creshal 11y agoThat was a jab at browsers and their history of not supporting specs identically. HTML5 is also a "strongly defined" specification and it didn't help.
- cballard 11y agoLooks like fenced blocks are part of the spec - will you be adding them to SO?
- untothebreach 11y agocodinghorror no longer works at SO http://blog.codinghorror.com/farewell-stack-exchange/ http://blog.codinghorror.com/farewell-stack-exchange/
- treve 11y agoYea! Great read.
- amelius 11y agoPerhaps what we need is a registry in which we can store (functional) descriptions for converting markdown variants to e.g. HTML and back.