MultiMarkdown-6
MultiMarkdown-6 copied to clipboard
fletcher
New abbr syntax
I can see the benefits of the new [>ABBR]: format and its inline variation, but is it possible that MMD 6 could still render the *[ABBR]: format as well? This is one of those syntax changes that's going to break older documents, especially because other variants support it as well (PHP Markdown Extra, Maruku, MMD 5, kramdown), and anyone who uses Markdown on a blog is going to have "legacy" syntax...
I'll consider it, but I'm inclined to call the old way deprecated and be done with it....
In this case, all one needs to do in order to upgrade is a global find replace of [\r\n]\*[ to \n[> (and check the first line of the document since there is no preceding newline), right? And for something like Marked, you could do the same thing as a pre-processing step and then your users wouldn't have to worry about it.
MultiMarkdown has evolved a great deal over the last twelve years. v6 was a chance to start fresh and make everything internally consistent and more logical. The old abbreviation syntax was a casualty of this, but the new one is better, more flexible (inline abbreviations), and consistent with everything else (reference links, footnotes, citations, and glossary terms).
There are many things about CommonMark I disagree with, but I think internal consistency is one thing they got right. MMD 6 was an opportunity to try and do the same thing here.
That's fine, and yes, I can easily normalize the syntax if/when I put MMD6 into the Marked distribution. I'm thinking more about people like me who use the <6 syntax on blogs and such. Again, for me, easy fix, just wondering if the vast majority of MMD users will feel the same.
I 100% agree it's a more flexible and consistent syntax. I quite like it. I had thought there was to be a compatibility mode that would handle <6 syntax, but it seems like the only compatibility mode is all the way back to O.G. Markdown. Is that the case?
Also, ditto 💯 on this, both parts :)
There are many things about CommonMark I disagree with, but I think internal consistency is one thing they got right.
Compatibility mode is only for O.G Markdown, that's right...
That's partially why I release new major numbered versions as separate projects (separate github repo's, etc.) Not everyone likes change. I do think this is a change for the better, but all change involves a small amount of pain at the beginning....