-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document m.room.message formats #917
Comments
Funnily enough I started doing exactly that :) See https://docs.google.com/document/d/1QPncBmMkKOo6_B2jyBuy5FFSZJrRsq7WU5wgRSzOMho/edit |
One theme that is slowly emerging from theabove document is that Riot itself has quite a rich support of HTML formatting (using CommonMark to send, and being embedded in an HTML-capable browser for receiving), most of the other client implementations are a lot more limited in what they support. Prettymuch every client and bridge so far observed at least supports the basic formatting of bold, italics, underline, monospace, and possibly strikethrough. As most of the bridges are talking to 3PNs that consider messages as single-line entities, these bridges almost never support any of the block structuring like numbered headings, pre-formatted blocks, numbered or unnumbered lists, etc. Additionally, none of the terminal-based clients would support things that adjust the font size (either directly, or by numbered headings). |
@leonerd Thanks for sharing your research! I used it as a reference while adding an initial implementation of formatting incoming HTML messages in the Matrix script for Weechat: torhve/weechat-matrix-protocol-script#75 |
While documentation is not there, you can use rich html messages with
|
This is likely to later be replaced by mixins, however this is being documented now so clients aren't left in the dark. Fixes matrix-org#917
m.text messages have undocumented 'format' and 'formatted_body' fields. #471 includes a lot of hand-wringing about what the ideal should be, but maybe we should document what we have?
The text was updated successfully, but these errors were encountered: