[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 deryni):

 I should have guessed this was Openfire. When I attempt to paste a control
 character into the conversation window it pastes as a control character
 followed by "x#;" is that what you are seeing? It then appears to send
 that way and comes back as "&#x#;x#;"?

 I stand by the fact that pidgin should not be able to send those sort of
 characters at all as they are forbidden by the XMPP RFCs, I also believe
 that Openfire is incorrect to convert them and pass them on. Partly
 because it should not be able to send restriced XML entities and partly
 because it should be dropping the connection when it sees them (or at
 least dropping those characters depending on whether they are trying to
 follow the bis RFC drafts).

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