Make Date / Time format language-dependant

Issue #189 resolved
Christopher Kramer created an issue

Originally reported on Google Code with ID 189

Currently, the format in which date and time is outputted is specified within the code.
It would be better to specify it within language files, so each language could choose
the date-format that is most suitable for the speakers of this language.

Moreover, there seem to be 2 different formats used at the moment: One for date & time
of the last change of a db, and one for the date & time a sql dump was generated.
I don't see a good reason why to use different formats there.

Reported by crazy4chrissi on 2013-03-07 14:56:51

Comments (6)

  1. Christopher Kramer reporter
    (this was first mentioned as a comment in issue #186.)
    

    Reported by crazy4chrissi on 2013-03-07 14:57:36

  2. dreadnaut
    What about using an ISO or RFC format, so dates are easy to parse? (i.e., date('c')
    or date('r') in php)
    

    Reported by dreadnaut on 2013-03-07 18:38:22

  3. Christopher Kramer reporter
    Hmm. Why should you want to parse these dates?
    Maybe the date in the sql-export. But the date of the last modification of the db is
    something we display for the user. No reason to parse the html to find this out, you
    could easier do filemtime() yourself. So this date should clearly be displayed in a
    way that is most readable for the user (which ISO 8601 isn't in my opinion and RFC
    2822 might be well readable for English speaking users, but as a German user this is
    a rather uncommon format and I would prefer date("d.m.Y H:i:s (T)"). And other languages
    would use other formats.
    
    For the sql-dump, you could argue a well parsable date might be okay. But I think nobody
    parses the comments of the sql-dump. Especially if the date is included in the filename.
    So I think a format that is most readable for the user is best here as well.
    

    Reported by crazy4chrissi on 2013-03-07 21:20:58

  4. Christopher Kramer reporter
    This issue was closed by revision r351.
    

    Reported by crazy4chrissi on 2013-03-09 13:59:48 - Status changed: Fixed

  5. Log in to comment