[OTR-users] Communication with Pidgin to Miranda (or others) has encoding problemes

[Rainer]

Hello!

I've experienced a problem during OTR encrypted communication between Pidgin
and Miranda (or other clients). In short: several characters are encoded as
HTML entities and so transmitted. E.g. an ampersand is sent as & or a
newline is not the \n character (0x0A) but <br> instead. On the other way
round, messages from Miranda to Pidgin are displayed correctly, but written
HTML entities or tags like <br> will be extra parsed (so a newline is
displayed instead of "<br>").

The communication without OTR is fine, it's plain text transmitted (checked
the packages with Wireshark).

The whole problem is described on Pidgin's bugtracker. The answer was that
is has to be the problem of the third party plugin, namely Pidgin OTR.
Here it is, a longer description of the problem:

http://developer.pidgin.im/ticket/8453

OTR encrypted communication from Pidgin to other libpurple-based messengers
like Pidgin or Adium is fine.
I tested with an independent ICQ messenger (cliMM) with built-in OTR support
and received the same problems as with Miranda as the contact's client. I
also tested XMPP between Pidgin and Miranda: same thing.

The mystery is, Adium is like Pidgin based on libpurple, but has built-in
OTR support. No problems occur in communication to Miranda or cliMM. So I
isolated to problem to the combination Pidgin / OTR plugin.

Please try to help me or to identify the reason of this strange behaviour.


I'm using Pidgin 2.5.4 for Windows, but the same problem goes for the Linux
version. Pidgin OTR is in version 3.2.0.


Thanks for reading,
Rainer