Chris Carlin wrote: > Encoding in both pyAIMt and pyICQt is a mess, and fixing it has been top > priority on my py-transports todo list... for about six months now :) > > I think so far it's been fixed in this sort of piecemeal fashion, so > that throughout the code there is an unorganized mix of encoded and > decoded strings.
It seems these patches kind of fix problems as they appear. > Anyway, I plan to apply some of the user submitted patches to the > codebase(s) this weekend, so I'll definitely apply this one too. I realised later that it may not be good to hardcode the encoding to UTF-8. Maybe you could check first what it should be? I think Jabber uses UTF-8 by default though, but I'm not sure. > Thanks, and seriously, if you feel like taking a stab at cleaning up the > string handling let me know. I've dealt with python unicode in the past, > so I should be able to give advice. In this case it's a little more > complicated by the way the AOL packets work, though. I wish I could help more, but I don't really know any Python. For this patch, I needed quite a bit of help from others. I do know how to program though & hope I'll learn some more Python and be able to contribute. Julius _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
