GNOME Bugzilla – Bug 330592
date and time are dependent on the locale
Last modified: 2013-09-13 00:47:39 UTC
Please describe the problem: Evolution parses incorrectly date and time formats when creating a new appointment in the calendar. I have not tested other components, but I suspect this might affect other parts of evolution that use date and time. Steps to reproduce: 1. install a different locale (such as French, or GNOME in Japanese if you want to have fun) 2. start evolution, go to the calendar 3. start creating an appointment. Try saving. Actual results: See the attachment. Evolution complains about an "invalid date" (and an invalid time when you solved the date problem). Expected results: Parse the locale-dependent format correctly, or hard-code the default field values. Does this happen every time? Yes Other information: I believe evolution expects to see YYYY/MM/DD and HH/MM/SS format. However, I don't know why, it grabs the date and time from the locale (I guess). For example, in a French system, evolution displays YYYY.MM.DD So it looks like 2006.02.09 instead of 2006/02/09. Evolution then complains with a very, very annoying popup dialog. There is no way for the user to know what is the expected format, other than installing the English locale. If this bug cannot be fixed at the moment, please take the time to indicate the proper format (in all languages!) in the error dialog that pops up, so that the user can figure it out himself.
Created attachment 59033 [details] screenshot of the problem. On the left, in the date field, is the correct format. On the right, in the time field, is the default, improper format. This is on a French-UTF8 GNOME.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. I believe this one to be a duplicate of bug 250754, which should be fixed in CVS for a few days. The date field should be fully localized now. If you still can reproduce such issues with later releases, please feel free to comment on bug 250754 and re-open, if need be. Thanks. *** This bug has been marked as a duplicate of 250754 ***
*** Bug 272667 has been marked as a duplicate of this bug. ***