On Samstag, 14. Oktober 2017 18:35:46 CEST Dave Cridland wrote: > FWIW, I've been using "Markdown" when I really mean *only* the following: > > *bold* (or other strong emphasis) > /italic/ (or other weak emphasis) > `preformat` (or otherwise indicating a command, code, etc and disabling > markup).
I still don’t know how to put emphasis on the word "Trainer*Innen"... > I defintely could not live with paragraphs, headings, embedded images, and > so on. Those are fine in documents but keep them as far away from IM as > possible. I think you’re excluding some interesting use-cases here. At $dayjob, we have an XMPP bot which sends monitoring notifications. To structure that information, all of these things are useful: headings (of course not huge ones, but something akin to what <h5/> and <h6/> usually render like), enumerations and/or unordered lists and paragraphs (due to the current restrictions, we obviously couldn’t use those). Embedded images also make sense, because icons and such are much quicker to recognize than text. In short: there are use-cases outside of day-to-day IM we should support without having to resort to full-blown XHTML, because as we know, XHTML is hard to implement in clients, and this type of content will be viewed by people with normal clients. If we’re going to have a breakage in markup support in XMPP, we should use that opportunity to consider new use cases beyond day-to-day IM, and include these. This gives us better interop, and I think we can keep the cost low nevertheless. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
