Christoph Päper

For now, a line break after each row and a space between cells would already help.

Our would still increase the effective usable height.

The caption *Title* is not necessary at least. Itʼs also quite a difference between editing the initial post and a subsequent comment, especially considering the height taken up by *EDIT...

- [OTF 1.8 `sbix` table](http://www.microsoft.com/typography/otspec/sbix.htm) - [Apple `sbix` documentation](http://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6sbix.html)

Well, the best use case for `text/markdown` would be single-part emails. Unfortunately, some MUAs cannot handle mails correctly that do not use the default `text/plain`.

Implementers (or plugin authors) could decide to use asterisk `*` for `em` / `strong` and underscore `_` for `i` / `b` or vice versa, but I think it is too...

What the CM reference implementation should do, though, is to retain information in its AST about which character has been used in the source. PS:

*All* proper implementations of Commonmark support asterisks inside words (but not underscores), while only some implementations of Markdown do.

Since it is no heading underline, it is a normal line of text. With dashes instead, it could be a bullet list or thematic break as well, but with equals...

This is the result of intended and desired behavior. [Commonmark restricts intraword emphasis](https://spec.commonmark.org/0.29/#emphasis-and-strong-emphasis) to asterisks which are less problematic than underscores, since the latter are too frequently encountered as a...