[Pidgin] #6976: Encoding problem in Pidgin with GTK+ 2.12.8 rev a

[Pidgin]

#6976: Encoding problem in Pidgin with GTK+ 2.12.8 rev a
--------------------+-------------------------------------------------------
 Reporter:  xtonda  |        Owner:  MarkDoliner
     Type:  defect  |       Status:  new        
Milestone:          |    Component:  AIM        
  Version:  2.5.1   |   Resolution:             
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by xtonda):

 It is likely that Trillian is not sending correct encoding info or not
 sending encoding info at all, their AIM protocol implementation is far
 from perfect. I do not negate that RTF support would be useful but I do
 not see it as directly related ti this issue.

 Change of GTK+ from 2.12.1 rev b to 2.12.8 rev a breaks things so it is
 either bug in GTK+ 2.12.8 rev a that should be fixed or some new
 functionality in GTK+ 2.12.8 rev a that changes something and
 Pidgin/libpurple should adapt to it.

 Trillian sends message probably in windows-1250 encoding, so do nothing

 This is log, when using older GTK+ to 2.12.1 rev b and the same character
 sequence (ěščřžýáíé) is displayed correctly in Pidgin:

 (10:57:55) oscar: aim_icq_getstatusnote: requesting status note for
 157643456.
 (10:57:57) oscar: incomingim_ch1: unknown TLV 0x0013 (len 1)
 (10:57:57) oscar: Received IM from xtondacze with 1 parts
 (10:57:57) oscar: Parsing IM part, charset=0x0000, charsubset=0x0000,
 datalen=70
 (10:57:57) oscar: Conversion from ASCII failed: Invalid byte sequence in
 conversion input.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/6976#comment:6>
Pidgin <http://pidgin.im>
Pidgin