On Dec 13, 3:40 pm, r000n <[email protected]> wrote:
> Hi!
> New version of PyICQt released. Added since 0.8:
>   * secure (md5) authentification
>   * utf-8 in messages

this is probably "not a bug" but...

I switched from 0.8b to 0.8.1-git as of yesterday. I got Cyrillic
encoding problems go away with a couple of my correspondents (one
running native ICQ, one (pathalogical case?) with pidgin). But the
problems that I always had with licq uses became worse. Mind you, most
my correspondents have "windows-1251" set as default encoding, for
compatibility with older clients. I have it too, in the pyicq config,
as "<encoding>windows-1251</encoding>". I did not change this when I
upgraded, I just added "<detectunicode/>". Now, the situation:

Before upgrade (0.8b):
- online communication works fine, transmission is in windows-1251.
- when I get offline message (sent from licq correspondent when I was
offline), the message is unrecognisable ascii characters (no bytes
with high order bit set).

After upgrade (0.8.1-git):
- when online, licq peers need to manually configure "utf-8" as both
sedning and receiving encoding, otherwise I or they cannot read the
text. They complain because this is a special case for them
(windows-1251 setting works for them with all other clients).
- when they send me a message when I am offline, and they have "utf-8"
configured for me, I get an unreadable test, that I need to pass to
"iconv -t utf16" to get readable utf-8 text. Note that this is *NOT*
"iconv -f utf16", but "iconv -t utf-16", so we have a case of
"reverse" encoding, apparently.

Not sure if this can or needs to be fixed, but I thought I'd report it
anyway.

Thanks,

Eugene
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to