Scott do you still have a copy of that patch? I haven't been able to find
it in my email. =(
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
> Adam Kalsey wrote:
>> Chris Carlin <[EMAIL PROTECTED]> wrote..
>>> Anyway, as I said the correct solution to this is to have the transport
>>> explicitly decode to unicode, preferably specifying the correct
>>> character encoding during that step. This is especially important since
>>
>> Since we don't know the encoding of the incoming data, won't this always
>> be a bit of a crapshoot?
>>
>
> I don't know what "status" you are retrieving, but I know that both away
> messages and profiles carry an encoding along side. I suspect that you
> are talking about grabbing a profile because the current revision of
> pyaim-t ditches this value with the comment:
>
> #encoding = tlvs[1] We're ignoring this for now
>
> I've submitted a patch about this already. Haven't heard back, but my
> patch was rather large.. FWIW, there is a "guess_encoding" in the oscar
> module, but I have to admit that it is different than my version of the
> same idea.
>
> -Scott
>
> --
> Scott Dial
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
