diff --git a/inbox/spoiler.xml b/inbox/spoiler.xml index 876e2775..5b8c5c8d 100644 --- a/inbox/spoiler.xml +++ b/inbox/spoiler.xml @@ -37,7 +37,7 @@ vaulor@blastersklan.com - 0.0.1 + 0.0.2 2016-10-31 sfp, xfp

First draft.

 @@ -69,63 +69,71 @@ specified in &xep0115;.

- + + ]]> - - … - - … - + + +… + +… + ]]>

- Messages user wants to be sent as spoilers, MUST contain an - <spoiler> element qualified by the 'urn:xmpp:spoiler:0' namespace - and optionally, <spoiler> elements may possess a 'hint' attribute - that warns about the topic of the spoiler message. + Messages user wants to be sent as spoilers, MUST contain a <spoiler> element qualified by the + 'urn:xmpp:spoiler:0' namespace and optionally, <spoiler> elements may contain character data as + a hint that warns about the topic of the spoiler message. They may also possess the 'xml:lang' + attribute.

- This is a very long message so I'm going to hide inside a spoiler [...] ]]> - And at the end of the story, both of them die! It is so tragic! - + Love story end ]]> - + + holidays.png + Trip to the beach + Viatge a la platja + +]]> + + And at the end of the story, both of them die! It is so tragic! + I al final de la història, els dos moren! És tan tràgic! + Love story end + Fi de la història d'amor + +]]> +

- It MUST be clear a message is in fact a spoiler and its content MUST only - be displayed upon user's request. -

-

- Clients MAY provide a way to display spoilers always uncovered, without - the need of interaction by the user (e.g. in the client's settings). -

-

- Clients SHOULD display spoiler's hint, if any, before showing message's - content. -

-

- Clients MAY display spoiler's hint even after showing message's content - (e.g. as a header or title of the message). -

-

- Users SHOULD be able to uncover or hide a spoiler message at will, - anytime. +

    +
  1. It MUST be clear that a message is in fact a spoiler and its content MUST only be displayed upon + user's request.
    2. +
  2. Clients MAY provide a way to display spoilers always uncovered, without the need of interaction + by the user (e.g. in the client's settings).
    3. +
  3. Clients SHOULD display spoiler's hint, if any, before showing message's content.
    4. +
  4. Clients MAY display spoiler's hint even after showing message's content (e.g. as a header or + title of the message).
    5. +
  5. Users SHOULD uncover or hide a spoiler message at will, anytime.
    6. +

@@ -152,7 +160,7 @@ urn:xmpp:spoiler:0 - Indicates that a message should be hidden by default. + Indicates that a message's content should not be displayed by default. xxxx ]]> @@ -163,16 +171,16 @@ + xmlns:xs='http://www.w3.org/2001/XMLSchema' + targetNamespace='urn:xmpp:spoiler:0' + xmlns='urn:xmpp:spoiler:0' + elementFormDefault='qualified'> - +