Feature Requests item #1664242, was opened at 2007-02-20 06:23
Message generated for change (Comment added) made by rlaager
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: oscar
Group: None
>Status: Pending
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Dmitriy Geels (dm_ig)
Assigned to: Mark Doliner (thekingant)
Summary: ICQ non-unicode charset

Initial Comment:
There is a flaw in ICQ protocol implementation: one of ICQ bugs is not handled 
correctly in non-win32 versions of gaim.

Because of windoze has 3 charsets for each locale (Unicode, ANSI, OEM), all 
text sent thru ICQ protocol, which not marked/known as unicode, actually are in 
ANSI charset.
But non-win32 gaim versions doesn't event know about it. So those texts are 
mapped to first 255 chars in system encoding (UTF-8 in my case). There is a 
known workaround for this: run gaim like this "LOCALE=cp1251 && gaim".

Best solution is to add parameter specially for ICQ protocol for non-win32 
versions 'ANSI charset', so user could select it manually.


>Comment By: Richard Laager (rlaager)
Date: 2007-02-20 19:18

Logged In: YES 
Originator: NO

Where would you expect such an option? I ask because the place I'd expect
it is in the account options for an ICQ account, which is exactly where the
"encoding" option exists now. Doesn't that work?


You can respond by visiting: 

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
Gaim-features mailing list

Reply via email to