mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-26 19:22:15 -05:00
Fix typo ("cannot" repeated twice).
This commit is contained in:
parent
1b133e6047
commit
76b358907a
10
xep-0333.xml
10
xep-0333.xml
@ -10,7 +10,7 @@
|
|||||||
<abstract>This specification describes a solution of marking the last received, displayed and acknowledged message in a chat.</abstract>
|
<abstract>This specification describes a solution of marking the last received, displayed and acknowledged message in a chat.</abstract>
|
||||||
&LEGALNOTICE;
|
&LEGALNOTICE;
|
||||||
<number>0333</number>
|
<number>0333</number>
|
||||||
<status>Deferred</status>
|
<status>Experimental</status>
|
||||||
<type>Standards Track</type>
|
<type>Standards Track</type>
|
||||||
<sig>Standards</sig>
|
<sig>Standards</sig>
|
||||||
<approver>Council</approver>
|
<approver>Council</approver>
|
||||||
@ -27,6 +27,12 @@
|
|||||||
<email>im@spencermacdonald.com</email>
|
<email>im@spencermacdonald.com</email>
|
||||||
<jid>im@spencermacdonald.com</jid>
|
<jid>im@spencermacdonald.com</jid>
|
||||||
</author>
|
</author>
|
||||||
|
<revision>
|
||||||
|
<version>0.2.1</version>
|
||||||
|
<date>2015-10-28</date>
|
||||||
|
<initials>XEP Editor (mam)</initials>
|
||||||
|
<remark><p>Fixing typo ("cannot" repeated twice) (JC Brand).</p></remark>
|
||||||
|
</revision>
|
||||||
<revision>
|
<revision>
|
||||||
<version>0.2</version>
|
<version>0.2</version>
|
||||||
<date>2013-09-05</date>
|
<date>2013-09-05</date>
|
||||||
@ -133,7 +139,7 @@
|
|||||||
|
|
||||||
<section1 topic='When to send Chat Markers and markable messages' anchor='when'>
|
<section1 topic='When to send Chat Markers and markable messages' anchor='when'>
|
||||||
<section2 topic='Bare JID' anchor='when-bare'>
|
<section2 topic='Bare JID' anchor='when-bare'>
|
||||||
<p>If the sender knows only the recipient's bare JID, it cannot cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Chat Markers protocol. In this case, the sender MAY send a Chat Marker or markable message.</p>
|
<p>If the sender knows only the recipient's bare JID, it cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Chat Markers protocol. In this case, the sender MAY send a Chat Marker or markable message.</p>
|
||||||
</section2>
|
</section2>
|
||||||
<section2 topic='Full JID' anchor='when-full'>
|
<section2 topic='Full JID' anchor='when-full'>
|
||||||
<p>If the sender knows a full JID for the recipient (e.g., via presence), it SHOULD attempt to determine (via service disco or entity capabilities) whether the client at that full JID supports the Chat Markers protocol before attempting to send a Chat Marker or markable message.</p>
|
<p>If the sender knows a full JID for the recipient (e.g., via presence), it SHOULD attempt to determine (via service disco or entity capabilities) whether the client at that full JID supports the Chat Markers protocol before attempting to send a Chat Marker or markable message.</p>
|
||||||
|
Loading…
Reference in New Issue
Block a user