Potential parsing issue of HTML comment with --}
For various reasons, I ended up including the sequence "--}" in an HTML comment in a Multimarkdown document in Multimarkdown Computer, and I noticed that the comment was no longer treated as a comment once this sequence was included, e.g. the first comment is parsed as a comment but the second is not:
<!-- Testing -->
<!-- Testing --} -->
I imagine that this has something to do with CriticMarkup syntax, but I thought that once you were in an HTML comment, Multimarkdown was no longer processed.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on Oct 08, 2013 @ 06:41 PM
Shane,
Thanks for writing in!
1) "--" is not allowed inside HTML comments (it's actually more complex than that, but that's a good first approximation)
2) Previously, MultiMarkdown did not watch for that, and produced invalid HTML as a result (e.g. comments containing "--")
3) I fixed this
4) Which caused problems for LaTeX users (who are not bound by valid HTML)
5) This also confused some users who weren't aware of the invalid HTML they were creating previously.
6) After discussion on the MultiMarkdown mailing list, I "relented" and again allow invalid HTML (e.g. comments with "--" inside) to pass through -- this has been pushed to github for MultiMarkdown itself, and will be included in next release of Composer
7) While this issue is not specifically related to CM, CriticMarkup is in a sense "orthogonal" to Markdown/MultiMarkdown. It can cause confusion if CM tags span other constructs. For more information:
http://support.multimarkdown.com/discussions/conversations/1-technical-limitations-of-criticmarkup-and-what-can-we-do-about-it
Hopefully that explains what is going on.
Fletcher