On 01/06/2016 08:00 AM, Peter Waher wrote: > Sending markdown encoded as markdown has several benefits.
But also many downsides, there is not really such a thing as a markdown standard. There are different 'flavors', such as github-flavored-markdown, and then there are just major/minor differences in various markdown libraries. A newish effort is CommonMark[1][2], and it is strictly defined, but has only a few implementations at last check. Point being, you couldn't write a XEP talking about 'markdown' alone and expect it to be very compatible across implementations. I'd instead suggest client-side support for markdown, but sending it as HTML with the raw markdown as the text alternative. [1]: http://commonmark.org/ [2]: https://xkcd.com/927/ _______________________________________________ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
