Again, no characters are treated as special here. Everything that applies to '@' applies to anything else, as well. IF you decide to send extra characters with your mentions, you include them in the range. It doesn't matter what those characters are. The receiver shouldn't need to care either; that's kind of the entire point.
And also, this is an IF. Any implementation that doesn't want to send extra characters can just... not. The recommendation isn't TO send them, but just the way to do it IF you send them. On 13 March 2026 10:51:04 am UTC, Maxime Buquet <[email protected]> wrote: >What if a client doesn't use the "@" character but something else. >Should it also treat "@" as special on reception? Which characters >should also be treated specially for this case? > >More importantly, I don't think "@" should appear anywhere in the body >element of the sent message, hence including it in begin/end attributes >not making sense to me. (As opposed to natural language "markers", >punctuation and the like, which may) > >To me, an "@" (or equivalent) may only be used in clients for >autocompletion, and/or as a graphical marker to show it's a mention. Yes >that means the displayed and sent messages aren't the same, and that's >already the case anyway with other features. _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
