GNOME Bugzilla – Bug 582922
Share timezones with other gnome apps
Last modified: 2010-05-22 19:20:42 UTC
Currently Evolution has its own list of timezones in calendar/zones.h but maybe it makes sense to move it to e-d-s or somewhere else so if any other app needs this information it will be available for them.
Pretty sure that file is dead and should be removed. We use system timezones now like other apps.
I just compiled evolution-2-26 removing the calendar/zones.h file and it didn't complain, so yes we can remove it, attaching a patch.
Created attachment 134817 [details] [review] Patch to remove calendar/zones.h and update po/POTFILES.in Note that the patch has been done with gnome-2-26 branch I don't have installed all dependencies for master right now but should be the same, if anyone is willing to test it please :)
This affects I18N, so adding that keyword.
Patch looks fine to me, but I'll let one of the calendar guys approve it.
It's not surprising that the compilation does not complain, after reading this: - * These are the timezone names from the Olson timezone data. - * We only place them here so gettext picks them up for translation. - * Don't include in any C files. Now, the next question is, where are these strings really coming from, if not from this file? In which project should we translate them? These names are visible in several places, so I think we should find the proper place for the translations and not just throw them out.
After doing a bit of research, it seems that they are from glibc, but they are not translatable there.
The same file exists in libical/zoneinfo/. Since libical does not have any translation in it, we would need this to be present. This is used for evolution on windows. system timezone info is not used in case of windows.
Can this be closed or do we want to share the libical timezone translations with other apps?
OK, so this is a duplicate of bug #559039, known for more than half of a year, isn't it?
Agreed, looks like this is bug 559039 by now. *** This bug has been marked as a duplicate of bug 559039 ***