Mercurial > pidgin.yaz
view gtk/pixmaps/tb_drag_arrow_up.xpm @ 15000:82d1a2fc6d25
[gaim-migrate @ 17778]
SF Patch #1598994 from lexande
Fixes SF Bug #1581999
Original Description:
"The gaim 2.0.0beta5 log reader plugin uses the "Date" XML field in MSN logs, the format of which varies between locales, leading to logs being displayed on incorrect/future dates in locales that do not use the MM/DD/YYYY format. This patch fixes the plugin to use the "DateTime" field which has YYYY-MM-DD date in all locales."
I totally Warmenhovened this patch. My approach:
"I'm using the Date, Time, and DateTime fields. If I can determine that the log matches the current timezone, it'll display 100% properly in the log viewer. If it has a reasonable offset, it'll display as the original time, sort in the right place, but not have a timezone abbreviation. If the offset is bogus or I can't parse the Date or Time field, it'll display in UTC, but still sort properly. I think this is as ideal as is possible, given the data we have to work with."
You don't have to understand this. ;)
committer: Tailor Script <tailor@pidgin.im>
| author | Richard Laager <rlaager@wiktel.com> |
|---|---|
| date | Sun, 19 Nov 2006 06:54:38 +0000 |
| parents | 009db0b357b5 |
| children |
line wrap: on
line source
/* XPM */ static char * tb_drag_arrow_up_xpm[] = { "13 16 13 1", " c None", ". c #B80000", "+ c #F02F2F", "@ c #E87676", "# c #E78383", "$ c #E56A6A", "% c #ED9191", "& c #F05757", "* c #E79F9F", "= c #E54545", "- c #EDAFAF", "; c #D23333", "> c #E40E0E", " . ", " +@. ", " +#@$. ", " +%#@$&. ", " +*%#@$&=. ", " +-*%#@$&=;. ", ">>>>+#@$>>>>.", " +#@$. ", " +#@$. ", " +#@$. ", " +#@$. ", " +#@$. ", " +#@$. ", " +#@$. ", " +#@$. ", " >>>>. "};