Hi. It's a sad thruth that many older ICQ clients which do not use Unicode encodings abuse 'us-ascii' tag of ICQ protocol transmitting messages in various 8-bit encodings. There is 'encoding' parameter in the pyicq-t config which, AFAIU, tries to deal with such protocol violation, and it works fine by decoding broken packets.
However, messages emitted by the pyicq-t itself to the older clients (which do not advertise Unicode, and there is plenty of them: licq, centericq to name a few) are still encoded as 'us-ascii', not as specified in config. Attached is the trivial patch to fix this problem. --
--- icqt.py.orig 2006-12-26 13:11:43.000000000 +0600 +++ icqt.py 2006-12-26 13:07:54.000000000 +0600 @@ -320,7 +320,7 @@ charset = 'utf-16be' elif charset == 'utf-8': pass elif charset == "us-ascii": - charset = "iso-8859-1" + charset = config.encoding else: LogEvent(INFO, self.session.jabberID, "Unknown charset (%s) of buddy's away message" % msg[0]); charset = config.encoding
_______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
