comparison pidgin/gtkutils.c @ 32363:3322201b446f

I went through all our calls to purple_notify_user_info_add_pair() and checked whether they should be purple_notify_user_info_add_pair_plaintext(), instead. If it wasn't immediately obvious one way or the other then I left a comment to investigate. I suspect there are still a lot of places where we should use the _plaintext function to escape the value.
author Mark Doliner <mark@kingant.net>
date Mon, 22 Aug 2011 01:53:37 +0000
parents 58e0e310ef2e
children 1f22e6ea1d2a
comparison
equal deleted inserted replaced
32362:57d43a9a4e7e 32363:3322201b446f
982 982
983 static void 983 static void
984 show_retrieveing_info(PurpleConnection *conn, const char *name) 984 show_retrieveing_info(PurpleConnection *conn, const char *name)
985 { 985 {
986 PurpleNotifyUserInfo *info = purple_notify_user_info_new(); 986 PurpleNotifyUserInfo *info = purple_notify_user_info_new();
987 purple_notify_user_info_add_pair(info, _("Information"), _("Retrieving...")); 987 purple_notify_user_info_add_pair_plaintext(info, _("Information"), _("Retrieving..."));
988 purple_notify_userinfo(conn, name, info, NULL, NULL); 988 purple_notify_userinfo(conn, name, info, NULL, NULL);
989 purple_notify_user_info_destroy(info); 989 purple_notify_user_info_destroy(info);
990 } 990 }
991 991
992 void pidgin_retrieve_user_info(PurpleConnection *conn, const char *name) 992 void pidgin_retrieve_user_info(PurpleConnection *conn, const char *name)