After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347240 - Date editor does not allow localized date formats (without :)
Date editor does not allow localized date formats (without :)
Status: RESOLVED WONTFIX
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[compeditor]
: 347241 (view as bug list)
Depends on: 336253
Blocks:
 
 
Reported: 2006-07-11 17:44 UTC by Ilkka Tuohela
Modified: 2015-06-15 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ilkka Tuohela 2006-07-11 17:44:34 UTC
Following item is valid Finnish timestamp translation:

#. This is a strftime() format. %H = hour (0-23), %M = minute.
#: ../widgets/misc/e-dateedit.c:1436 ../widgets/misc/e-dateedit.c:1763
msgid "%H:%M"
msgstr "%H.%M"

String is shown correctly in editor, but the user can't enter new dates because the editor component checks that the format matches the common nn:mm format. If the entry is manually modified from nn.mm to nn:mm the date is accepted.

Using . as time delimiter is official Finnish standard, nobody really cares about it though and everyone uses : - it still should be possible to do the right thing as well.
Comment 1 Fabio Bonelli 2006-07-11 19:07:20 UTC
*** Bug 347241 has been marked as a duplicate of this bug. ***
Comment 2 Ilkka Tuohela 2006-08-10 09:17:28 UTC
I did a workaround for Finnish translation (using in 2.14 the 'invalid' 
format %H:%M until it's fixed), but the bug is most likely really old.
Comment 3 Matthew Barnes 2008-03-11 00:27:04 UTC
Bumping version to a stable release.
Comment 4 André Klapper 2012-06-21 09:21:45 UTC
In 3.2.3 it is the other way round: You cannot enter 11:30 in Finnish, must enter 11.30 instead.
Comment 5 Milan Crha 2015-06-15 14:28:55 UTC
The related code resides in the evolution-data-server,
libedataserver/e-time-utils.c, where is a list of formats marked for the translation, thus evolution-data-server lefts the responsibility to use the right format to the translators. These strings are not otherwise modified.

It probably doesn't surprise that one cannot use a dot when trying to enter the time in an en_US.utf8 locale. The same it might not surprise if the translator used a different separator (like the dot in the Finish) and the colon cannot be used.

I guess there are more than these two separators being used in different locales, aren't there?

So we have a time separator and a date separator. The routines use one, the other, or both (when parsing date and time at once). Should there be a list of possible date/time separators, and mix them all together, just in case a Finish person would like to enter a Finish-formatted time when running evolution in the English locale? (No offence meant, 'Finish' used as one of the known locales with a different time separator.)

Any such change might make the code quite complex, from my point of view, thus I'm WontFix-ing this.