[Pidgin] #10064: No Hebrew typing, in Jabber (Google Talk) after upgrading to 2.6.1

[Pidgin]

#10064: No Hebrew typing, in Jabber (Google Talk) after upgrading to 2.6.1
--------------------+-------------------------------------------------------
 Reporter:  Katom   |        Owner:  darkrain42 
     Type:  defect  |       Status:  pending    
Milestone:          |    Component:  Google Talk
  Version:  2.6.1   |   Resolution:             
 Keywords:  Hebrew  |  
--------------------+-------------------------------------------------------

Comment(by darkrain42):

 Replying to [comment:11 datallah]:
 > No, I'm not aware of there ever being any issues with UTF-8 validation
 being any different on Windows.
 >
 > Are we sure that is the exact same string being passed to
 `g_utf8_validate()`?

 purple_utf8_strip_unprintables() is passed the argument directly from
 XMPP's send_im function. I guess the only other possibility here is some
 other plugin is munging up the message.  If the debug output without
 pidgin-encryption offers no leads, I'll add more verbose output to
 purple_utf8_strip_unprintables about the argument passed in and the first
 'invalid' character.

 This line from the signals-test plugin should print exactly what was sent
 to the prpl, and it does look a little...corrupt. or something:

 `(21:47:02) signals test: sent-im-msg (<my Gmail username>@gmail.com/Home,
 <addressee>@gmail.com, <font color="#ff0000">׳(21:47:02) pidgin-
 encryption: Using pre-existing menu icon for conv 05C9C388, win 033FE228,
 item 057F6D68`

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