From 2ef4e1106a814b8e170b585d1033d092e982f888 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Wed, 3 Jun 2020 08:38:06 -0400 Subject: [PATCH] XEP-0393: remove disabling individual spans/blocks This was a nice workaround, but a convenient code point that is actually for this sort of use can't be found. --- xep-0393.xml | 42 ++++++++++++++++++++++-------------------- 1 file changed, 22 insertions(+), 20 deletions(-) diff --git a/xep-0393.xml b/xep-0393.xml index 494d44f3..e87a189d 100644 --- a/xep-0393.xml +++ b/xep-0393.xml @@ -26,6 +26,18 @@ styling &sam; + + 0.4.0 + 2020-06-02 + ssw + +

+ Remove description of mechanism for disabling styling on individual + spans and blocks, users can do this themselves without us documenting + the use of a codepoint that's not specifically for this purpose. +

+ + 0.3.0 2020-06-02 @@ -471,33 +483,16 @@ 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. + 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.

- - -

- 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. -

> _ < ]]> -

@@ -514,6 +509,13 @@ For example, the string "*emphasis*" would be rendered as "*emphasis*".

+

+ This specification does not provide a mechanism for removing styling from + individual spans or blocks within a styled message. + Implementations are free to implement their own workarounds, for example by + inserting Unicode non-printable characters to invalidate styling directives, + but no specific technique is known to be widely supported. +