Comment 2 for bug 203475

Thanks mackeev for reporting, and pilot for checking this!

> 1. My understanding there is no simultaneous support of the both AIM and ICQ, right?

Correct, the transport will support only one account for Jabber user. A workaround might be to create an extra Jabber user, for ICQ (or AIM) only, or to communicate with one's AIM contacts through one's ICQ account (or vice-versa) since the two networks are interoperable.

> 2. My counterparts in ICQ communicate in Russian. They can read my messages, but I receive gibberish from them. No problem with that in AIM, though.

I'm afraid X-Pilot's answer summarizes all we know about this so far. :-(

> 3. I can't decipher Away (status) messages of my contacts if they are written in Russian.

This is probably related to 2 -- status written in Russian set on a Jabber client looks fine here.

> 4. A general problem: Copy is disabled in the communication area, and sometimes this function is really needed (to copy some text received and paste it elsewhere).

Yes, looking into it. Unfortunately a totally obvious problem with a totally non-obvious way to attack it.

I'm leaving this bug open in case more info on ICQ/Cyrillic issues come up. As X-Pilot says, it would be helpful (and friendlier to my decreasing mental sanity :-) ) to have different reports for different issues in the future.