On 2015-06-05 14:57, Vladimir Panteleev wrote:
1. People receiving messages through NNTP/mailing lists will not see the formatted Markdown. Although Markdown's goal is to be readable in its plain text source code, it still allows many situations in which the source is misleading or difficult to understand. For example, special characters need to be escaped by a backslash, which can create confusion in the presence of other special characters. (Are they part of the D syntax the user is describing, or something else?) Some syntax such as tables or images can also be not very readable in source form.
Some people are already sending something that looks like Markdown, i.e. ``` for code blocks. Even your post can be rendered as Markdown.
2. How should we render messages sent by NNTP/mailing-list users? Do we just assume that they're sending Markdown and render it as such? This can cause the messages to appear broken to forum users. Or do we only render Markdown if the post was sent from the forum? This means that when NNTP/ML users quote forum users' text it will be shown as plain text. 3. There is no unified standard for Markdown. The original format is not used on major sites today - StackOverflow and GitHub extend the format, and users will expect Markdown with those extensions.
That standard would be the one GibHub uses.
5. You can't edit posts once sent. This means that if you accidentally messed up the formatting (e.g. you pasted code without padding it with whitespace or surrounding it in ```...``` blocks), you can't go back and edit it now.
A preview button/view would (hopefully) solve that. -- /Jacob Carlborg