On Mittwoch, 18. Oktober 2017 20:09:28 CEST Florian Schmaus wrote: > On 18.10.2017 19:58, Jonas Wielicki wrote: > > On Mittwoch, 18. Oktober 2017 18:12:54 CEST Florian Schmaus wrote: > >> The situation BMH tries to improve is the following: I do have a bunch > >> of data formatted using a markup language, say CommonMark, that I want > >> to send over XMPP to an XMPP client. Because there is no converter from > >> CommonMark to XHTML-IM(-NEXT) and since I don't want to write one (for > >> various reasons), I'm just going to stuff CommonMark into <body/>. > > > > I think if you’re doing that, you’re already doing it wrong. Really. There > > should be a separate non-body element for markup, and body should only > > contain simple, unformatted plain text > > How would you image a plain text version of CommonMark to look like?
Ugh. Now I actually see your use-case. Somehow I lost that, probably because I mentally mixed the XHTML-IM thread and this ProtoXEP. I apologize. This is a tough one. On the one hand, stuff like "*foo\*bar*" (where CommonMark meta-characters have to be escaped for formatting to work) is annoying and hard to read. On the other hand, there’s no reasonable meta- character free representation of, for example, blockquotes in plaintext. I’m not convinced that having things like "*foo\*bar*" is a good thing in <body/>. Something like "XYZ wrote:\n> fnord" on the other hand perfectly makes sense. (I still think that a gateway should also provide an XHTML-IM(-NEXT) version of the markup. BMH would then only be a hint for clients which don’t support XHTML-IM(-NEXT), but happen to support the backing markup.) I’m torn. This may be a way to solve this dilemma. I would suggest to plan for adding some normative language which requires entities sending BMH-annotated markup to also send XHTML-IM-NEXT along with it to cater for entities only supporting the latter (which will hopefully exist at some point in the future and will be the standardised markup language within XMPP). 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] _______________________________________________
