search

in7egral / mirotr

Automatically exported from code.google.com/p/mirotr
1 stars 0 forks source link

one word messages just come through as (null) - sometimes even two word messages #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open up a conversation window
2. start a conversation
3. Start OTR by right clicking on lock in message window and choose Start OTR. 
Also make sure Convert HTML is checked (problem happens even when unchecked)
4. Type in 'ok' - no quotes
5. The other person receives '(null)' - no quotes
6. Type in 'no' - no quotes
7. The other person receives '(null)' - no quotes

Typing in a longer sentence does go through ok.

What is the expected output? What do you see instead?
I expect the message to go through as typed.

What version of the product are you using? On what operating system?
0.10.3.1 on windows 7 - full version info below for sending AND receiving 
computers

Please provide any additional information below.

Please see attached file for version info dumps from both sending and receiving 
computers.

Original issue reported on code.google.com by schw...@gmail.com on 20 Sep 2010 at 3:38

Attachments:

GoogleCodeExporter commented 9 years ago 
I cannot confirm this (WinXP, unicode)

Which protocol did you use?

Original comment by andreas....@student.kit.edu on 20 Sep 2010 at 10:46

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Protocol is Yahoo. How can I get you a netlog?

Original comment by schw...@gmail.com on 20 Sep 2010 at 4:10

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I can confirm this somehow..
Protocol is Jabber. 
I can send single words to a Pidgin user but can't recieve them. Tabsrmm shows 
nothing, History++ shows things like "amk0ƒ".
I dont know if a netlog can help, everything is encrypted ;)

Original comment by len...@gmail.com on 26 Sep 2010 at 3:47

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I can confirm the bug, using Jabber Protocol. Without Convert HTML everything 
is fine. With Convert HTML some short messages won’t be shown in chat window.

What steps will reproduce the problem?
1. Open up a conversation window, using Scriver
[…]
4. Type in '123456' - no quotes
5. The other person receives ''
6. Type in '1234' - no quotes
7. The other person receives '1234'

What is the expected output? What do you see instead?
I expect the message window to show me the received message. It is not 
displayed. But: if you look into history the message is there. It may be a 
problem between MirOTR and scriver or something, because the received data 
seems to be correct.

Original comment by blockchi...@googlemail.com on 7 Oct 2010 at 6:55

GoogleCodeExporter commented 9 years ago 
Here is a patch for the bug.

Original comment by Nicolas....@gmail.com on 26 Jun 2011 at 3:11

Attachments:

GoogleCodeExporter commented 9 years ago 
BTW: the whole bug arises because decode_html_entities_utf8 has the 'feature' 
to make this: 
if (!len) len = strlen(src);

*sigh*

Anyways, I hope the crashes will be gone now

Original comment by Nicolas....@gmail.com on 26 Jun 2011 at 3:18