Version 1 (modified by 16 years ago) (diff) | ,
---|
ICQ Encoding Progress
Here we will attempt to identify precisely what does and does not work as far as ICQ encodings in communication with the official ICQ client. If you can confirm an entry in the below tables currently marked with a question mark (be SURE you know that the remote client is the official client of the appropriate version!), please update the table and provide an annotation below.
ICQ 6
ICQ Locale | Pidgin Version | Pidgin Encoding | Offline Messages | Away Messages | Available Messages | Buddy Info | Auth Request |
Bulgarian | ? | ? | Broken | ? | Broken | ? | ? |
German | ? | ISO-8859-1 | Broken? | Works? | Works? | Broken? | Broken? |
Annotations
Offline available messages reported broken in comment:1645:72
ICQ 5.1
ICQ Locale | Pidgin Version | Pidgin Encoding | Offline Messages | Away Messages | Available Messages | Buddy Info | Auth Request |
Bulgarian | 2.0.2 | CP1251 | Works | Works | Broken? | Broken | Broken |
Bulgarian | ? | ? | ? | ? | Broken | ? | ? |
German? | ? | ? | ? | Broken | ? | ? | ? |
Annotations
Confirmed Bulgarian dispositions are from I4ko on #1645.
comment:1645:43 indicates that attachment:ticket:1645:paket shows ICQ 5.1 sending a UTF-8 message marked as ISO-8859-1.
Unknown Client
ICQ Locale | Pidgin Version | Pidgin Encoding | Offline Messages | Away Messages | Available Messages | Buddy Info | Auth Request |
Hebrew | 2.1.1 | CP1255 | ? | Broken | Broken? | Broken | ? |
Annotations
Hebrew information from attachment:ticket:1645:p.jpg