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 (of course, you can’t really stop a user from adding *emphasis* themselves. but we shouldn’t encourage that type of behaviour; also this isn’t relevant to BMH, because you’d have to make sure that the markup flavour you announce is actually the flavour the user typed into the box). > The > good thing about markup languages which are reasonably well readable in > plain is: Even if the receiving client doesn't know CommonMark exists, > it will display the textual content just fine (thanks to the nature of > CommonMark). > > But if the client knows about the existence of CommonMark, and if there > is an BMH, then it could display the content in a more sophisticated > way. Uh, and there are tons of CommonMark to X converters available. I think we should have one single way to represent markup and if there are so many converter libraries as you claim, I see no reason to push the burden of conversion down the stream and at the same time widen the number of formats a client has to support. I really see what you want to achieve here in general, but I’m really, really sceptical due to the high potential of abuse as a general IM rich-text transport in this XEP. If anything, using a separate element and REQUIREing the implementations to provide a proper plain-text version would already be an improvement. 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] _______________________________________________
