| Issue 153: | Encoding of some messages still wrong | |
| 1 person starred this issue and may be notified of changes. | Back to list |
I still have problem with encodfing of some (online) messages.
I get ":-D:-D:-D rozhodnй slovo mue zaznмlo :-P" instead of ":-D:-D:-D
rozhodné slovo muže zaznělo :-P".
Here is relevant log part:
[2009-01-10 14:21:20] tlvs = {19: '\x10', 2:
'\x05\x01\x00\x02\x01\x06\x01\x01\x00V\x00\x02\x00\x00\x00:\x00-\x00D\x00:\x00-\x00D\x00:\x00-\x00D\x00
\x00r\x00o\x00z\x00h\x00o\x00d\x00n\x049\x00 \x00s\x00l\x00o\x00v\x00o\x00
\x00m\x00u\x00\x9e\x00e\x00 \x00z\x00a\x00z\x00n\x04<\x00l\x00o\x00
\x00:\x00-\x00P', 11: '', 22: 'Ih\xa0\xd0'}
[2009-01-10 14:21:20] unknown TLV for incoming IM, 0013, '\x10'
[2009-01-10 14:21:20] Message data:
'\x05\x01\x00\x02\x01\x06\x01\x01\x00V\x00\x02\x00\x00\x00:\x00-\x00D\x00:\x00-\x00D\x00:\x00-\x00D\x00
\x00r\x00o\x00z\x00h\x00o\x00d\x00n\x049\x00 \x00s\x00l\x00o\x00v\x00o\x00
\x00m\x00u\x00\x9e\x00e\x00 \x00z\x00a\x00z\x00n\x04<\x00l\x00o\x00
\x00:\x00-\x00P'
[2009-01-10 14:21:20] Timestamp: (1231593680,), datetime 2009-01-10 13:21:20
[2009-01-10 14:21:20] Multiparts:
[('\x00:\x00-\x00D\x00:\x00-\x00D\x00:\x00-\x00D\x00
\x00r\x00o\x00z\x00h\x00o\x00d\x00n\x049\x00 \x00s\x00l\x00o\x00v\x00o\x00
\x00m\x00u\x00\x9e\x00e\x00 \x00z\x00a\x00z\x00n\x04<\x00l\x00o\x00
\x00:\x00-\x00P', 'unicode', 'standard')]
Jan 10, 2009
#1
michal@cihar.com
Jan 10, 2009
And the other end seems to be using QIP 2005a.
Jan 12, 2009
é is U+00E9 symbol of Unicode. It should be presented as 0x00e9 but it 0x4900 here. ž is U+017E, 0x009e here (it's even not symbol, control code). We already receiving wrong encoded text, assume it's QIP' bug.
Status:
Accepted
Jan 12, 2009
I know the unicode is messed up. On the other side, AFAIK it used to work with these people some versions ago (I even think that 0.8.1b3 was still okay, but I'm not really sure).
Jan 12, 2009
Sorry, I can't reproduce it. But can send é via QIP if it running with cp1252 encoding)
Jan 13, 2009
I have no idea what configuration the other side might be using (but I'd expect cp1250 there), but I will try to find out details. |