• Status Confirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Translations → Greek
  • Assigned To No-one
  • Operating System All
  • Severity Very Low
  • Priority Very Low
  • Reported Version 1.0 devel (github master)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by protonotarios - 24.10.2016
Last edited by peterdd - 22.11.2016

FS#2225 - Greek uses slash for dates

Short dates in Greek are represented in the majority of cases with slashes (24/10/2016). Very seldom some people may use the dash form (24-10-2016) and hardly ever the dot form (24.10.2016).

So it would be much appreciated if the slash form were a (working) option because as it is dates are a bit confusing to us, especially in a date-time combination (too many numbers in a not-so-obvious format - brain needs extra time to decode it).

This task is a sub task of FS#2222 - Greek translation issues
Project Manager

Yeah, I think using date formats could be a real solution

instead the current 'half' dropdown list.

But maybe adding the slash version is a quick fix. But we must keep in mind that U.S. people would write 10/24/2016 instead 24/10/2016 so using slashes for short dates is a bit ambiguous. (Should be clear in the format date select lists especially if it is day 1-12 of a month.) ;-)

No problem if all users are greek speakers.

  • I think that php date formats is the simplest, more elegant solution with the most potential but it could be very confusing for people who are not very familiar with computers (as my clients are). BTW, Windows uses something similar too. On the other hand, why would a person who doesn't understand computers mess with the date in the first place? They can just accept the default option and be happy.
  • The big current 'half' dropdown list it may be good for everyone but it's too big already, and will become bigger if you add slashes to it.
  • To avoid the ambiguous dates you could:
    • use a bogus date instead of current one, like "31/12/2016" (pity because current one looks nice), or
    • use current one but put an explanation in parenthesis next to ambiguous ones only, like "1/1/2016 (m/d/y)". But this would make a big list even bigger.
  • Another option would be to let the locale decide the available separators and the day-month order. But this I guess would be limiting for no reason and would demand a lot of effort to code all the locale options.

So after all this analysis I vote for the php date formats solution.

Project Manager

Added the DD/MM/YYYY format to github master.


Available keyboard shortcuts


Task Details

Task Editing