On Thu, Oct 15, 2015 at 2:31 PM, Marcus Daniels <[email protected]> wrote:
> Hmm, a browser can support different MIME types, this is just another one > <https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown/>. > > I mean, one wouldn’t convert JPEG to HTML. > An RFC?! Wow! I knew there were folks trying to standardize markdown due to spreading "flavors" like Github Flavored Markdown, and others adding tables & other additions. https://github.com/jgm/CommonMark .. and they've got a good point about bugs and weird end-of-line whitespace. Gruber had some problems, especially the initial name Standard Markdown, thus the current name CommonMark. http://arstechnica.com/information-technology/2014/10/markdown-throwdown-what-happens-when-foss-software-gets-corporate-backing/2/ The key change from the first "standards" approach and the current one is that the current one only "fixes" Gruber's. Extensions like tables come later. I do know that using various markdown variants is tough. GitHub screws up the 4 space indent at times in comments/issues. Still requires experiments to see what it eventually looks like!
============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
