Hi Jonas, and thanks for this message. I generally agree (as previously said, I'm not firmly opposed to a new syntax, but it needs to be specified, with a strict syntax (rejected if invalid) and extensible, and if possible XML based.
And I also agree that XHTML-IM should be kept until this syntax is draft (with possibly a mention at the top that it will be obsoleted in the future). We also have to check every XEP where XHTML-IM is used (to see if replacement is fine). I just have two remarks: > - Pre-formatted text (code), including a way to specify the language (this > may make the colorisation of things obsolete, the only use-case I’ve heard > so far is syntax-highlighting) It's not the only one. First a language may not be known by receiving client, second color can be used outside of code (for instance sending the colorized output of SHELL command). This maybe a niche use case, but still I think the ability to use colors is needed. But for mainstreams languages code paste, I agree with Edhelas' point that color should be done by receiving client (as it may know if background is clear or not, if use is colorbind, etc.). > - Embedding multimedia content, like images, audio, video (a SIMS-message > may be better suited for that) SIMS is useful to attach media, but for pictures (and maybe video), it is useful to specify where in the text it should be rendered. Cheers Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
