view pidgin/pixmaps/arrow-up.xpm @ 27121: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 37a664cf7f2d
children
line wrap: on
line source

/* XPM */
static char * arrow_up_xpm[] = {
"13 16 30 1",
" 	c None",
".	c #5E3667",
"+	c #623C6B",
"@	c #A787A8",
"#	c #603A6A",
"$	c #623B6B",
"%	c #C2A6C1",
"&	c #D4BDD2",
"*	c #BEA2BD",
"=	c #613A6A",
"-	c #C0A5C0",
";	c #D4BCD1",
">	c #D5BED3",
",	c #BEA3BE",
"'	c #C0A5BF",
")	c #BFA3BE",
"!	c #BC9FBB",
"~	c #D5BDD2",
"{	c #D1B8CF",
"]	c #CFB5CC",
"^	c #5C3566",
"/	c #623C6C",
"(	c #C9ACC6",
"_	c #C4A4C1",
":	c #BF9BBB",
"<	c #B992B4",
"[	c #B389AE",
"}	c #AF83AA",
"|	c #B084AB",
"1	c #D3BBD0",
"      .      ",
"     +@#     ",
"    $%&*=    ",
"   $-;>;,=   ",
"  $';>>>;)=  ",
" =!~~{]{~~!= ",
"^^^^/~(~/^^^^",
"    ^~_~^    ",
"    ^&:&^    ",
"    ^&<&^    ",
"    ^&[&^    ",
"    ^&}&^    ",
"    ^&}&^    ",
"    ^&|&^    ",
"    ^1&1^    ",
"    ^^^^^    "};