From: Richard L. <rl...@wi...> - 2006-02-09 18:43:33
|
Sorry for the bad threading... I marked "%x %X" and "%B %Y" as translatable "Just In Case" it was necessary for some language to have those in a different order or with other stuff around them... From the discussion here, it seems like that was a good idea. I did not mark %x, %X, or %c by themselves, as those should be handled properly by the C library. If they're not, I'd say it should be fixed there. However, I've created the various gaim_{date,time} functions with the intention that signals could be added to them, similar to what we do with the message/logging timestamps. Then, plugins could override the handling of the date formatting. I'd like to see us honor the GNOME and KDE settings when running under one of those environments, for example. On a related note... What charset does gettext() return strings in? The man page says : RETURN VALUE If a translation was found in one of the specified catalogs, it is converted to the locale=E2=80=99s codeset and returned. However, we use _("Some string") in all sorts of places (e.g. GTK+ functions) that expect UTF-8. I ask because we shouldn't be passing UTF-8 to strftime(). So, if gettext() returns UTF-8 in non-UTF-8 locales, then I need to convert it in gaim_utf8_strftime(). However, if gettext() does behave as the man page suggests, doesn't that cause problems with GTK+? Richard |