[Bug 296867]

Fri May 9 20:01:22 UTC 2014

(In reply to comment #68)
> It doesn't matter, if the message is in the form "?OTR:<base64>" then it
> puts new_content to whatever the original message was (html or not). OTR
> doesn't change anything if user wants to send html message as plaintext,
> empathy will escape when displaying them.

Are you saying that in this message

<message>
  <body>?OTR:123123123</body>
</message>

the recipient is expected to decrypt 123123123 and treat the result as
plain text, but in this message

<message>
  <html xmlns='http://jabber.org/protocol/xhtml-im'>
    <body xmlns='http://www.w3.org/1999/xhtml'>
      ?OTR:456456456
    </body>
  </html>

the recipient is expected to decrypt 456456456 and treat the result as
HTML? Or what?

There must be a rule you can use to determine whether the decrypted
content is text/plain or text/html. "Text that may contain HTML" is not
a well-formed concept - either the message "<" is a 4 character reply
to "remind me how you escape < in HTML?", or it's a single U+003C LESS-
THAN SIGN character. It can't be both.

It is entirely possible that the rule is "do whatever Pidgin does",
which in practice probably means it's always treated as HTML - that's
what my review comments assume.

-- 
You received this bug notification because you are a member of
Telepathy, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867

Title:
  empathy needs to support OTR encryption

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions