On Mon, Nov 06, 2017 at 11:58:15AM -0600, Sam Whited wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Styling > > Abstract: > > > This specification defines a plain-text formatting syntax for use in > > exchanging instant messages with simple text styling.
Please no… People have been telling you countless times on standards@ that embedding raw markup in the body is an extremely bad idea, with many examples. Markdown(-like) is NOT a plain text format, having the receiving client choose between rendering all formatting characters or stripping them is stupid, and requiring humans to mentally strip them out in older clients is stupid; have you not seen the mess that OTR is for example? There is exactly no extensibility in this proposal, if tomorrow the trend changes you will end up with all users of clients implementing it not understanding what’s going on. Formatting really should be in a separate payload, so that clients which don’t understand it can use the plain text version and safely ignore the formatted one. And again, this XEP does not address any of the issues with XHTML-IM, web people will just pipe this through the first Markdown library and get rendering wrong, get more elements than listed here, and get a nice passthrough of escaped HTML. > > URL: https://xmpp.org/extensions/inbox/styling.html > > The Council will decide in the next two weeks whether to accept this > proposal as an official XEP. Sorry for the rant, -- Emmanuel Gil Peyrot
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
