Changed form utf8 to iso-8859-15 to 8859-11 and now to windows-1252. We'll see how it turns out.
On Tue, 2005-08-02 at 08:59 +0400, Oleg Motienko wrote: > Hello, > > Did you set proper encoding in config file? For me it works ok with > Russian (windows-1251 codepage). > > On 8/2/05, Oscar Hellstr?m <[EMAIL PROTECTED]> wrote: > > Installed the latest CVS tarball and look, i can recieve ???? and such > > from ICQ folks. However, the Vcards and status messages are messed up > > still. If someone doesn't know a quick fix, i'll tell you more about > > what happends, when and what encoding, icq client etc... > > -- Oscar Hellstr?m, [EMAIL PROTECTED] jid: [EMAIL PROTECTED] icq: 52604556 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://modevia.com/pipermail/py-transports/attachments/20050802/4790685d/attachment.pgp From [EMAIL PROTECTED] Tue Aug 2 13:26:20 2005 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Tue Aug 2 13:26:16 2005 Subject: [py-transports] State of the PyICQ Message-ID: <[EMAIL PROTECTED]> Ok folk, obviously I'm not getting a PyICQ release out as fast as I'd hoped. There are a slew of bugs that I feel should be fixed before I put out anything dubbed a release, so please bear with me. Also, just so y'all know, I'm going to be awol wednesday - sunday so don't be surprised if you don't hear from me if you write me. ;D Anyway, we still have encoding problems that need to be addressed and I have a slew of patches that fix numerous problems waiting to be applied. I have not been touching PyAIM lately as I'm simply waiting for myself to get the PyICQ release out the door before I start poking at PyAIM again. (besides, PyAIM has far fewer encoding issues to work with than PyICQ does) Daniel -- "The most addictive drug in the world is music." - The Lost Boyz
