Mercurial > pidgin
view libpurple/dbus-define-api.h @ 27039:9a79f8a99259
Set charset=utf-8 when cyrus sasl doesn't include it.
Both deryni and my reading of the digest md5 cyrus plugin is that the response
will never actually include the charset (digestmd5.c:make_client_response,
look for IsUTF8). I future-proofed this code by checking for it anyway.
To be polite for older servers, we might want to only send this if the server
sent charset=utf-8 in the challenge (and encode everything to ISO-8859-1).
However, the RFC doesn't say always sending it is wrong (and that's what
the in-tree implementation does).
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Fri, 05 Jun 2009 07:02:16 +0000 |
parents | 32c366eeeb99 |
children |
line wrap: on
line source
#error "This is file is not a valid C code" /* This file contains some of the macros from other header files as function declarations. This does not make sense in C, but it provides type information for the dbus-analyze-functions.py program, which makes these macros callable by DBUS. */ /* blist.h */ gboolean PURPLE_BLIST_NODE_IS_CHAT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_BUDDY(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_CONTACT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_GROUP(PurpleBlistNode *node); gboolean PURPLE_BUDDY_IS_ONLINE(PurpleBuddy *buddy); gboolean PURPLE_BLIST_NODE_HAS_FLAG(PurpleBlistNode *node, int flags); gboolean PURPLE_BLIST_NODE_SHOULD_SAVE(PurpleBlistNode *node); /* connection.h */ gboolean PURPLE_CONNECTION_IS_CONNECTED(PurpleConnection *connection); gboolean PURPLE_CONNECTION_IS_VALID(PurpleConnection *connection); /* conversation.h */ PurpleConvIm *PURPLE_CONV_IM(const PurpleConversation *conversation); PurpleConvIm *PURPLE_CONV_CHAT(const PurpleConversation *conversation);