+ Add ability to disable styling, further clarify accessibility + considerations, and mention that Styling is not Markdown in the security + considerations section. +
++ Clients that support message styling MUST advertise the fact by including a + feature of "urn::xmpp:styling:0" in response to &xep0030; information + requests and in their &xep0115; profiles. +
+@@ -441,6 +466,39 @@
+ On rare occasions styling hints may conflict with the contents of a message. + For example, if the user sends the emoji "> _ <" it would be + interpreted as a block quote. +
+ ++ To remove styling without removing the styling directives, a whitespace + character can be inserted after the opening styling directive and before + the closing styling directive (if applicable). + This whitespace character SHOULD be U+2060 WORD JOINER to prevent line + breaks between the character that was misinterpreted as a styling + directive and the text that it would otherwise style. +
++ An entire message may also have styling disabled to remove the need to + parse the message for styling in the first place. + Senders may indicate to the receiver that a particular message SHOULD NOT + be styled by adding an empty <unstyled> element qualified by the + "urn:xmpp:styling:0" namespace. +
+This document does not define a regular grammar and thus styling cannot be @@ -467,9 +525,12 @@ text more difficult to read for visually impaired users.
- Styled text may also be rendered poorly by screen readers. + Styled text may be rendered poorly by screen readers. When applying formatting it may be desirable to include directives to - exclude styling directives from being read. + exclude styling directives from being read, or to add markers to the final + output that have semantic meaning for screen readers. + For example, in an web based client an emphasis span might be converted to + an HTML <em> element.
+ Though message styling is not compatible with Markdown, some of its styles + are similar. + Markdown parsers often allow arbitrary HTML to be inserted into documents + and therefore MUST NOT be used to parse the format defined in this document + even if they are flexible enough to do so. +
@@ -484,7 +552,40 @@
This specification requires no interaction with the ®ISTRAR;
+This specification defines the following XML namespace:
++ Upon advancement of this specification from a status of Experimental to a + status of Draft, the ®ISTRAR; shall add the foregoing namespace to the + registries located at &DISCOFEATURES;, as described in Section 4 of + &xep0053;. +
+
+ urn:xmpp:styling:0
+ Support for rendering message styling.
+ &xep0393;
+]]>
+ + The ®ISTRAR; shall also add the foregoing namespace to the Jabber/XMPP + Protocol Namespaces Registry located at &NAMESPACES;. + Upon advancement of this specification from a status of Experimental to a + status of Draft, the ®ISTRAR; shall remove the provisional status from + this registry entry. +
+
+ urn:xmpp:styling:0
+ &xep0393;
+ provisional
+]]>
+ This document does not define any new XML structure requiring a schema.