[Pidgin] #6031: ASCII control characters cause problems with libpurple clients

[Pidgin]

#6031: ASCII control characters cause problems with libpurple clients
---------------------+------------------------------------------------------
  Reporter:  dhawes  |       Owner:  deryni
      Type:  defect  |      Status:  closed
  Priority:  minor   |   Milestone:        
 Component:  XMPP    |     Version:  2.4.2 
Resolution:  fixed   |    Keywords:        
   Pending:  0       |  
---------------------+------------------------------------------------------
Comment (by dhawes):

 That is not what I'm seeing.  When I paste the control character into the
 conversation window they display as unicode replacement characters (hex
 value of the character inside of a little square).

 I do this by entering the control character in vim (CTRL-V then CTRL-1),
 opening the file created by vim with kwrite, and then pasting the
 character into the window.

 I completely agree that Pidgin should not send these characters.  If that
 had been the case, I would probably not have come across this bug (as
 everyone in my group uses libpurple-based clients).  I also agree that
 Openfire should not convert them and pass them on.  I would prefer the
 characters be ignored rather than dropping the connection for the simple
 reason that it's annoying to have the reconnect issues when something goes
 wrong.  Then again, I'd rather see RFC compliant clients/servers across
 the board.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/6031#comment:14>
Pidgin <http://pidgin.im>
Pidgin