Mercurial > pidgin
view doc/ui-ops.dox @ 28315:d9eb51a3a3a2
jabber: Don't try to pull a photo out of the <PHOTO/> cdata.
When the data from the server looks literally like:
<PHOTO>
<TYPE>image/jpeg</TYPE>
<BINVAL></BINVAL>
</PHOTO>
xmlnode_get_data(photo_node) will contain (whitespace) data, but in
no way is it a base64-encoded image. I can't find any reference to
clients distributing avatars in that way in the XEP or the RFC.
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Sat, 03 Oct 2009 02:50:48 +0000 |
parents | e3bf822c19c8 |
children |
line wrap: on
line source
/** @page ui-ops UiOps structures When implementing a UI for libpurple, you need to fill in various UiOps structures: - #PurpleAccountUiOps - #PurpleBlistUiOps - #PurpleConnectionUiOps - #PurpleConversationUiOps - #PurpleCoreUiOps - #PurpleDebugUiOps - #PurpleDnsQueryUiOps - #PurpleEventLoopUiOps (without this, nothing will work and you will cry) - #PurpleIdleUiOps - #PurpleNotifyUiOps - #PurplePrivacyUiOps - #PurpleRequestUiOps - #PurpleRoomlistUiOps - #PurpleSoundUiOps - #PurpleWhiteboardUiOps - #PurpleXferUiOps */ // vim: ft=c.doxygen