view etc/toolbar/mail-cap-xx.xpm @ 4780:2fd201d73a92

Call character_to_event on characters received from XIM, event-Xt.c src/ChangeLog addition: 2009-12-17 Aidan Kehoe <kehoea@parhasard.net> * events.h (character_to_event_meta_behavior): New enumeration, describing what character_to_event should do with characters in the range ?\x80-?\xFF, and passed as the third argument to character_to_event instead of the binary use_console_meta_flag. * events.c (character_to_event, Fcharacter_to_event): * event-unixoid.c (read_event_from_tty_or_stream_desc): * event-stream.c (maybe_kbd_translate, maybe_kbd_translate): * event-msw.c (mswindows_need_event): Use the new enumeration. * event-Xt.c (x_to_emacs_keysym): Call character_to_event when we receive XLookupChars events, passing latin_1_maps_to_itself as the meta_behavior flag, addressing the problem FKtPp sees in 87bpi9mwpu.fsf@yahoo.com.cn
author Aidan Kehoe <kehoea@parhasard.net>
date Thu, 17 Dec 2009 17:51:38 +0000
parents 376386a54a3c
children 7910031dd78a
line wrap: on
line source

/* XPM */
static char * mail[] = {
"33 33 5 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"O	c Gray90",
"+	c Gray60",
"@	c white",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXoooooooooooXXXXXXXXXXXX",
"XXXXXXXXXXoOOOOOOOOOooXXXXXXXXXXX",
"XXXXXXXXXXoOOOOOOOOOo+oXXXXXXXXXX",
"XXXXXXXXXXoOOOOOOOOOooooXXXXXXXXX",
"XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX",
"XXXXXooooooooooooooooooooooooXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXo@oo@@@@@@@@@@@@@@@ooo@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@o+o@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@o+o@oXXXX",
"XXXXXo@@@@@ooooooooo@@@@ooo@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXo@@@@@ooooooo@@@@@@@@@@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXo@@@@@ooooo@@@@@@@@@@@@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXo@@@@@@@@@@@@@@@@@@@@@@oXXXX",
"XXXXXooooooooooooooooooooooooXXXX",
"XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX",
"XXXXXXXXXXooooooooooooooXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXoXoXXXXXXXXX",
"XXXXXXXXXXXoXXXoXXXXXXXoXXXXXXXXX",
"XXXXXXXXXXXooXooXooXXoXoXXXXXXXXX",
"XXXXXXXXXXXoXoXoXXXoXoXoXXXXXXXXX",
"XXXXXXXXXXXoXoXoXoooXoXoXXXXXXXXX",
"XXXXXXXXXXXoXoXoXoXoXoXoXXXXXXXXX",
"XXXXXXXXXXXoXoXoXooXooXoXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};