Charsets conversion problem

[trofimich]

Hi! I've installed last Licq from opensuse respository and has problems with russian encoding (we use code page windows-1251 here). Same problem were with version 1.3.4 and i was not able to use it because of this problem. The problem is next: when i talk with someone who has nick with russian letters i get popup window with next error message:

Window header: Licq - critical error

Message: Error encoding (?????? invie) to UCS-2BE from (unsupported conversion)

[trofimich]

Screenshot

[Crazy_Hopper]

Hmm... I have plenty of users here with Russian nicknames w/o any problems.

Moreover, as far as I can see from the screenshot, Жеже was ecnoded correctly, so that critical error must be about something else.

For now I close this ticket as invalid, please reopen it once you find out what that error is about.

[trofimich]

Problem is that i can't understand why exactly this error appears. Same behavior were on 1.3.4 and i saw similar bug report it ticket #1522... I will try to understand when it appears...

[Crazy_Hopper]

The screenshot also shows something 'invie'. Is it a part of someone's nickname?

On the other hand, could you provide me with uin of the contact you have such problems with? (For the testing purposes only, of course.)

[trofimich]

Sorry for delay. 'Invie' is not a part of nick name. 'Жеже' is my wife's secret contact, her number is 483196814. She did not specified any info there (including nick name). I gave her nick name 'Жеже' in my contact list from windows machine using QIP Infium and after that i load my contact list into LICQ, so she will not be 'Жеже' in your list.

[Crazy_Hopper]

I have just done the same, renamed using latest QIP Infium, and got no errors whatsoever. Thus, I believe that the error you see has nothing to do with your wife's UIN.

Let me suggest you running the following command from your licq base directory: grep -li invie users/*

This might show us the specific UIN which has that 'invie' somewhere in informational fields. If the command returns nothing, then I'm afraid I won't be able to help.

[trofimich]

I can't run grep -li invie users while i'm at work, but i found who is invie. Seems this man changed his login because he has other nick in my contact list. His ICQ number is 2215965

[Crazy_Hopper]

Now that makes sense.

His info indeed contains weird characters, and a nickname is provided in cp1251. So if you update his info after setting user encoding to cp1251, you won't see that error. Btw, what encoding do you have set now? UTF-8 or 16? Since these are the only two encodings which could cause the message about unsupported conversions for me.

If you still have a contact with him, it would be nice to find out which client and its version he used to set his info. But it's in no way obligatory, it's just my curiosity.

[Yando]

Have the same problem. Speaking with the QIP user at that end. Encoding is CP 1251. Can't find out when exactly does this message appear. Sometimes i don't even chat with anybody and this message pops up...

[flynd]

Ticket #1439 is same encoding error as this.