Thomas Leitner

Introducing a new syntax will take a major version change for compatibility reasons and which is currently not planned anytime soon. You could implement a custom syntax highlighter and (ab)use...

The problem is that there *is no common Markdown syntax*. Each implementation differs in subtle and not so subtle ways. Luckily most syntax differences are small so running another implementation...

Yes, CommonMark is a nice try but still not universal. You could invoke a new parser instance in the custom syntax-highlighter that does the parsing.

The reason for this is backtracking. For the first three underscores kramdown tries to find the matching pair. When encountering the second three underscores, it sees that those are not...

Underscores only match at word boundaries and the stopping delimiter must not be preceded by a space (see https://kramdown.gettalong.org/syntax.html#emphasis). So yes, that is intentional.

Thanks for the issue and the pull request! I get what you want to accomplish with the issue and pull request. If the resulting HTML still validates, it would be...

The reason for this is that the `Gammad` entity is not recognized by kramdown. I will fix this for the next release. In the meantime you can do the following:...

Yes, CDATA sections are currently not supported.

You are doing nothing wrong, this is just how the conversion is done. The entities for `< > & "` are not converted to characters.

I'm open to pull requests that adjust this behaviour in the kramdown converter, the used utility function should not be changed because it is used in several places.