[Pidgin] #1645: Some cyrillic problems

[Pidgin]

#1645: Some cyrillic problems
---------------------------+------------------------------------------------
  Reporter:  I4ko          |       Owner:       
      Type:  defect        |      Status:  new  
  Priority:  minor         |   Milestone:       
 Component:  pidgin (gtk)  |     Version:  2.0.1
Resolution:                |    Keywords:       
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by seanegan):

 I confirm that converting that UTF-16 to Windows-1251 results in that
 valid UTF-8 string.

 Also, that does indeed seem to be an official ICQ client; we've worked
 around plenty of broken ICQ i18n problems before, and we should try to
 work around this one.

 We already special-case "unicode-2.0," as it's not the canonical name of
 any encoding iconv understands. We should, therefore, assume ICQ reserves
 the right to choose how it should be interpreted (especially since other
 official clients can handle it), instead of just making it a synonym for
 UCS2-BE.

 In this case, it seems like we should go through the list of fallback
 encodings, convert the "unicode-2.0" string to them, and see if the result
 validates as UTF-8. If none of them do, treat it as UTF-16. It's
 definitely crack.

 It seems this particular string is not a user-set string, but a hard-coded
 "auto-away" status message. l4ko, does this happen for all status
 messages, or just auto-status messages? If the latter, we may even be able
 to just special case the few status messages that have this problem.

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