[Pidgin] #7009: conversation signals: message formats are inconsistent

[Pidgin]

#7009: conversation signals: message formats are inconsistent
--------------------+-------------------------------------------------------
 Reporter:  nowic   |        Owner:           
     Type:  defect  |       Status:  new      
Milestone:          |    Component:  libpurple
  Version:  2.5.1   |   Resolution:           
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by deryni):

 The protocol plugins do not see the outgoing text before the sending-im-
 msg signal is fired, so they have no say over what it does or does not
 look like yet. Not directly at least.

 pidgin can reasonably control the outgoing formatting of messages but
 cannot as reasonably control the incoming formatting, especially on
 protocols with real rich formatting support, the incoming messages you see
 are (for protocols that support the same html subset-style formatting that
 pidgin uses internally) exactly what was sent over the wire (which is why
 your XMPP example is wrapped in the html tag).

 If you were to send an XMPP message to yourself (and if everything worked
 correctly) you would likely see your outgoing message 'plain' and the
 incoming version with the html wrapping. The XMPP prpl knows how to
 transmit the data so that other XMPP client can interpret it,
 pidgin/libpurple itself does not so it feeds the protocol a plain
 formatted message (which is what you see in sending-im-msg).

 I am unclear as to why bonjour wraps an empty font tag around the message,
 that may or may not be necessary, if it isn't we should probably stop.

 Likewise, while it would be helpful for prpls to mangle incoming
 formatting into a normalized form that is a large amount of fragile work
 and if the incoming formatting will work as-is is largely without benefit.

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