pidgin: 189e0d4d: jabber: Check in some new strings under ...

[darkrain42 at pidgin.im]

-----------------------------------------------------------------
Revision: 189e0d4dde22835eb133a3bfc5eed463dad9f0e7
Ancestor: 8cd7ebe0ee16aad48725ab266cbf8a76b5f6fe7b
Author: darkrain42 at pidgin.im
Date: 2010-04-29T03:57:14
Branch: im.pidgin.pidgin
URL: http://d.pidgin.im/viewmtn/revision/info/189e0d4dde22835eb133a3bfc5eed463dad9f0e7

Modified files:
        libpurple/protocols/jabber/auth_scram.c

ChangeLog: 

jabber: Check in some new strings under the freeze radar (no code yet).

"Channel Binding" is ugly and needs to be replaced with a user-friendly term

-------------- next part --------------
============================================================
--- libpurple/protocols/jabber/auth_scram.c	af68529a143c5c95b25c94cdf5fd82bb7a8d3a0e
+++ libpurple/protocols/jabber/auth_scram.c	af6e118ebd5a2b2a5d39e9e9382250e0f9e578db
@@ -47,6 +47,32 @@ static const JabberScramHash *mech_to_ha
 	g_return_val_if_reached(NULL);
 }
 
+static const struct {
+	const char *error;
+	const char *meaning;
+} server_errors[] = {
+	{ "invalid-encoding",
+		N_("Invalid Encoding")},
+	{ "extensions-not-supported",
+		N_("Unsupported Extension") },
+	{ "channel-bindings-dont-match",
+		N_("Channel Bindings don't match; possible MITM") },
+	{ "server-does-support-channel-binding",
+		N_("Server does support channel binding; possible MITM") },
+	{ "channel-binding-not-supported",
+		N_("Server does not support channel binding") },
+	{ "unsupported-channel-binding-type",
+		N_("Unsupported channel binding method") },
+	{ "unknown-user",
+		N_("User not found") },
+	{ "invalid-username-encoding",
+		N_("Invalid Username Encoding") },
+	{ "no-resources",
+		N_("Resource Constraint") },
+	{ "other-error",
+		N_("Unknown Error") }
+};
+
 guchar *jabber_scram_hi(const JabberScramHash *hash, const GString *str,
                         GString *salt, guint iterations)
 {