The boring unicode spaces weren't inserted at places within the string that contained special characters, i.e. characters that either have a special meaning in MarkdownMini, or those that get HTML-encoded. Since your comment solely consisted of characters in the second group, nothing was inserted. This is fixed in the next build.

Cody's answer is still valid, though.

The boring unicode spaces weren't inserted at places within the string that contained special characters, i.e. characters that either have a special meaning in MarkdownMini, or those that get HTML-encoded. Since your comment solely consisted of characters in the second group, nothing was inserted. This is fixed in the next build.

Cody's answer is still valid, though.

The boring unicode spaces weren't inserted at places within the string that contained special characters, i.e. characters that either have a special meaning in MarkdownMini, or those that get HTML-encoded. Since your comment solely consisted of characters in the second group, nothing was inserted. This is fixed in the next build.

Cody's answer is still valid, though.

The boring unicode spaces weren't inserted at places within the string that contained special characters, i.e. characters that either have a special meaning in MarkdownMini, or those that get HTML-encoded. Since your comment solely consisted of characters in the second group, nothing was inserted. This is fixed in the next build.

Cody's answer is still valid, though.