Scott Dial wrote:
> > Is encoding here a character encoding anyway?
> >
>
> I'm not familiar with the rest of the workings of pyaim-t, just of the
> oscar module. I leave that part to you ;).
I mean the oscar stream: does AOL send character encoding data in the
stream?
What's in tlvs[1] (from encoding = tlvs[1])?
> The change I was saying that
> is relevant is that all messages come with an encoding (and my patch is
> to let you get to that for profiles).
The patches I have from you [1] don't seem to deal with encoding other
than to do the right thing upon failures. It doesn't seem to provide
access to anything extra. Am I missing something?
> For refernce, my strategy for dealing with this has been attempt to use
> AIM's suggested charset and otherwise fallback to utf-16be. If AIM
> didn't provide charset with the message, I assume it is ascii.
>
> try:
> text = message.decode(encoding, 'replace')
> except (UnicodeDecodeError, LookupError):
> text = message.decode('utf-16be', 'replace')
Daniel, in guess_encoding utf-16be is commented out. Any idea why?
I ended up with some free time, so I'll take a crack at this stuff and
hopefully have something for testing soon.
~Chris
[1] http://b.airaim.com/oscar.diff http://b.airaim.com/scheduler.diff
_______________________________________________
py-transports mailing list
[email protected]
http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
