Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Version 12 (modified by Sim-on, 15 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. If you are reporting something broken, please attach a packet dump (binary tcpdump format with a snaplen of 1500 if possible!) to the ticket and include a comment to that effect in your annotation.

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?
German 2.4.2 CP1252 Works Works Works Fixed in 2.4.3 Broken (2.4.3)
Russian 2.4.2 CP1251 Works ? Works Broken* Broken
Hebrew 2.4.2 ISO-8859-8 Works Works Works Works Broken*

Annotations

Offline messages reported broken in comment:ticket:1645:72

  • (russian, 2.4.2) only away-message-encoding is wrong in Buddy-Info-Dialog
  • (hebrew, 2.4.2) icq 6 sends an hebrew or -RTL alligned english- auth message doesn't show up on client (only first character?)

ICQ 5.1

  • doesn't work any more without hack -

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

All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!