> On 6 Jan 2016, at 19:29, Dave Cridland <[email protected]> wrote:
> 
> 
> Ash's suggestion of an additional marker element is probably easier for most 
> implementations to handle, though.
> 
> Not particularly keen on an alternate body, since the only thing I can think 
> of to sensibly degrade Markdown into is its source anyway.

Agreed. Markdown/yaml/whatever (and in theory all the “text/*” content types) 
are readable as plain text (so entirely appropriate for a message body). The 
hint is there to tell clients that might be able to do a better rendition “hey, 
this text body here is actually markdown” and give them an opportunity to 
render it nicely if they can.

I’m happy to knock up a Content Type Hint ProtoXEP if anyone thinks it might be 
useful.

—
Ash

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to