QIP. Kill can not be pardoned.
Probably at least once in your life you have had to deal with the problem of encodings when communicating in ICQ, messages come in "kryakozyabrami" one or both opponents. You have to write in transliteration or switch to another client / protocol. For me personally, ICQ communication is part of the job and the IM client is the same tool as the IDE development. Probably I'm not the only one who has these problems corny.
Well, actually to the point. I have been using Trillian Pro 2.013 for five years already, the only patch was released 2 years ago due to regular surprises from AOL, except that the program has not changed at all. With users of official clients, Pidgin and Miranda problems are not noticed, messages in both directions come as it should. But I usually find out about updating QIP and QIP Infium programs as one of the first ones; normal work with encodings may break or, on the contrary, be repaired with each subsequent update.
Why sin on QIP? Just analyzing the problem indicates exactly this, let's examine the symptoms:
1. my client has not been updated for the last 5 years, according to data taken from other clients, he uses version 8 of the protocol
2. Work with other clients is proceeding normally, although Miranda had similar problems a few years ago, but they apparently decided
3. offline messages from QIP users come in normal encoding, apparently not without the help of the AOL servers on which they are stored
4. If the quacking through the decoder Lebedev www.artlebedev.ru/tools/decoder , he gives a quite readable text making the transformation WIN1252 -> UTF-8
5. and most important. In recent years, communication with QIP users is a variant of Russian roulette, after the next update of the program, messages suddenly begin to arrive to the quackers, after another update - kosher Cyrillic.
')
Considering the popularity and numerous advantages of QIP, it is foolish to entice users to other customers, the client is good. For his part, he is also not ready to change his client, who faithfully and has served for so many years without any updates (which QIP just cannot boast of). Once I wrote a letter to QIP developers with a description of the problem and a request to enter the “encoding” setting, as it is in the same Pidgin, but I never received an answer.
Please do not arrange holivar about clients, the problem is partly in the protocol (Jabber is not offered, and so I use it), it is known that AOL likes to create problems, and Trillian uses the old version. But there are no problems with other customers, but QIP ... well, in general, you understand.
ps from the comments it turned out that the problem is encountered with other clients when communicating with queues, regardless of the platform. It seems that QPS developers are jealous of the support for the OSCAR protocol, supporting only the most recent version, because of which the program stops working with each update by AOL and does not have backward compatibility with clients using a different version.
Well, actually to the point. I have been using Trillian Pro 2.013 for five years already, the only patch was released 2 years ago due to regular surprises from AOL, except that the program has not changed at all. With users of official clients, Pidgin and Miranda problems are not noticed, messages in both directions come as it should. But I usually find out about updating QIP and QIP Infium programs as one of the first ones; normal work with encodings may break or, on the contrary, be repaired with each subsequent update.
Why sin on QIP? Just analyzing the problem indicates exactly this, let's examine the symptoms:
1. my client has not been updated for the last 5 years, according to data taken from other clients, he uses version 8 of the protocol
2. Work with other clients is proceeding normally, although Miranda had similar problems a few years ago, but they apparently decided
3. offline messages from QIP users come in normal encoding, apparently not without the help of the AOL servers on which they are stored
4. If the quacking through the decoder Lebedev www.artlebedev.ru/tools/decoder , he gives a quite readable text making the transformation WIN1252 -> UTF-8
5. and most important. In recent years, communication with QIP users is a variant of Russian roulette, after the next update of the program, messages suddenly begin to arrive to the quackers, after another update - kosher Cyrillic.
')
Considering the popularity and numerous advantages of QIP, it is foolish to entice users to other customers, the client is good. For his part, he is also not ready to change his client, who faithfully and has served for so many years without any updates (which QIP just cannot boast of). Once I wrote a letter to QIP developers with a description of the problem and a request to enter the “encoding” setting, as it is in the same Pidgin, but I never received an answer.
Please do not arrange holivar about clients, the problem is partly in the protocol (Jabber is not offered, and so I use it), it is known that AOL likes to create problems, and Trillian uses the old version. But there are no problems with other customers, but QIP ... well, in general, you understand.
ps from the comments it turned out that the problem is encountered with other clients when communicating with queues, regardless of the platform. It seems that QPS developers are jealous of the support for the OSCAR protocol, supporting only the most recent version, because of which the program stops working with each update by AOL and does not have backward compatibility with clients using a different version.
Source: https://habr.com/ru/post/46949/
All Articles