[AlexAffe]

This. Also: The unconverted markdown source is in itself already a nice way of formatting text/code/lists/headings/whatever. That's the whole point of markdown, no? So, yes, markdown rules, but because I can use it in plain text sources and benefit from it. Just never convert to html except on webpages.

[oneeyedpigeon]

Surely convert it to html if the client decides that's how they want it, otherwise leave as markdown?

[AlexAffe]

Well, that should be a receivers end decision imo. The content is there, everyone is free to view it as they please. But in essence it's plain text, no html tag shenanigans (because that's a pain to read when unparsed) or, god forbid, javascript (because it's dangerous).

[oneeyedpigeon]

Yes, that's exactly what I meant by "client". I think the tricky issue in this case relates to links because they totally ruin the text when left untranslated (in much the same way that unparsed html does), but some would prefer to view the original URL. I'd possibly advocate a different format - e.g. surround text in square brackets, supply URLs in order, at bottom of text.