[Pidgin] #9087: Outgoing Direct IM with UTF-8 fails

[Pidgin]

#9087: Outgoing Direct IM with UTF-8 fails
--------------------+-------------------------------------------------------
 Reporter:  zacw    |     Owner:  MarkDoliner
     Type:  defect  |    Status:  new        
Component:  AIM     |   Version:  2.5.5      
 Keywords:          |  
--------------------+-------------------------------------------------------
 When sending an outgoing direct IM which contains UTF-8, the receiver ends
 up receiving a blank message.

 On Pidgin 2.5.5 (as well as a recent copy of 2.6.0mtn libpurple via Adium)
 sending a message containing UTF-8 reveals the following debug log:
 {{{
 (14:14:01) oscar: Sending direct IM with flags 1
 (14:14:01) oscar: Conversion from UTF-8 to ISO-8859-1 failed
     (Invalid byte sequence in conversion input), falling back to unicode.
 (14:14:01) oscar: Outgoing ODC frame to fuark with
 type=0x0001,flags=0x0000, payload length=54
 (14:14:01) oscar: Outgoing ODC frame to fuark with type=0x0001,
 flags=0x0002, payload length=0
 }}}

 The receiver of the message sees a blank message, without any of the text.
 No error messages are echod or displayed.

 A correctly-sent message over direct IM looks like:
 {{{
 (14:15:14) oscar: Sending direct IM with flags 1
 (14:15:14) oscar: Outgoing ODC frame to fuark with type=0x0001,
 flags=0x0000, payload length=112
 (14:15:14) oscar: Outgoing ODC frame to fuark with type=0x0001,
 flags=0x0002, payload length=0
 }}}

 The main difference being the lack of the second "outgoing ODC frame"
 which has a payload.

 I was able to duplicate this with rekkanoryo in a Pidgin <-> Pidgin Direct
 IM connection.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9087>
Pidgin <http://pidgin.im>
Pidgin