view etc/toolbar/info-def-cap-xx.xpm @ 4318:4d0f773d5e21

Fix the test failures introduced by the non-ISO-2022 coding systems. APPROVE COMMIT NOTE: this patch has been committed. This is patch http://mid.gmane.org/18264.25814.828088.486899@parhasard.net tests/ChangeLog addition: 2007-12-06 Aidan Kehoe <kehoea@parhasard.net> * automated/mule-tests.el: Add a Known-Bug-Expect-Error call testing and documenting that we don't support all of the Unicode code space in a single session. * automated/test-harness.el (Known-Bug-Expect-Error): Provide Known-Bug-Expect-Error, analagous to Known-Bug-Expect-Failure and Check-Error. * automated/test-harness.el (Silence-Message): Dynamically bind the function definition of #'clear-message, as well as that of #'append-message, to nil. src/ChangeLog addition: 2007-12-06 Aidan Kehoe <kehoea@parhasard.net> * tests.c (Ftest_data_format_conversion): Move those tests that expect that iso-8859-2 is ISO 2022-compatible to testing iso-latin-2-with-esc instead.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 09 Dec 2007 15:10:46 +0100
parents 376386a54a3c
children 7910031dd78a
line wrap: on
line source

/* XPM */
static char * info[] = {
"33 33 2 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXoXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXoooooooXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXoXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXooooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXoooooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXoooooooXXXXXXXXXXXXX",
"XXXXXXXXXXXXoooooooooXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXoXXXXXXXXXXXXX",
"XXXXXXXXXXoXXXXXXXoXXXXXXXXXXXXXX",
"XXXXXXXXXXoXoooXXoooXooXXXXXXXXXX",
"XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX",
"XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX",
"XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX",
"XXXXXXXXXXoXoXXoXXoXXooXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};