From b3417b6d20e8ad46298faf56b0c9ec2fc0d43162 Mon Sep 17 00:00:00 2001 From: George Hazan Date: Thu, 2 Jun 2022 14:34:20 +0300 Subject: Jabber: fix for the wrong char in the OMEMO error message --- protocols/JabberG/src/jabber_omemo.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'protocols/JabberG/src/jabber_omemo.cpp') 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]*/; -- cgit v1.2.3