summaryrefslogtreecommitdiff
path: root/protocols
diff options
context:
space:
mode:
authorGeorge Hazan <ghazan@miranda.im>2022-06-02 14:34:20 +0300
committerGeorge Hazan <ghazan@miranda.im>2022-06-02 14:34:20 +0300
commitb3417b6d20e8ad46298faf56b0c9ec2fc0d43162 (patch)
treecc4fd3f6e529f4e6692b73b7b50b398d9463cd38 /protocols
parent3a1a68b6d509071389da7fdb28010126d1102ebe (diff)
Jabber: fix for the wrong char in the OMEMO error message
Diffstat (limited to 'protocols')
-rw-r--r--protocols/JabberG/src/jabber_omemo.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/protocols/JabberG/src/jabber_omemo.cpp b/protocols/JabberG/src/jabber_omemo.cpp
index 0a2aa68a73..490d370ce0 100644
--- a/protocols/JabberG/src/jabber_omemo.cpp
+++ b/protocols/JabberG/src/jabber_omemo.cpp
@@ -2025,7 +2025,7 @@ void CJabberProto::OmemoOnIqResultGetBundle(const TiXmlElement *iqNode, CJabberI
int CJabberProto::OmemoEncryptMessage(XmlNode &msg, const char *msg_text, MCONTACT hContact)
{
// a message for clients that do not support OMEMO
- msg << XCHILD("body", "I sent you an OMEMO encrypted message but your client doesn’t seem to support that");
+ msg << XCHILD("body", "I sent you an OMEMO encrypted message but your client doesn\'t seem to support that");
const EVP_CIPHER *cipher = EVP_aes_128_gcm();
unsigned char key[16], iv[12], tag[16] /*, aad[48]*/;