[savannah-help-public] [sr #109371] bug tracker date format excessive

Update of sr #109371 (project administration): Status:Works For Me => Done Open/Closed:Open => Closed ___ Reply to this item at:

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #10, sr #109371 (project administration): Thanks. Looks great to me. ___ Reply to this item at: ___ Message sent via Savannah h

[savannah-help-public] [sr #109371] bug tracker date format excessive

Update of sr #109371 (project administration): Status: In Progress => Works For Me ___ Follow-up Comment #9: It turns out that the additional setting for time format adds complexity that doesn't jus

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #8, sr #109371 (project administration): That's much better already! Thanks for your work on this! ___ Reply to this item at: ___

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #7, sr #109371 (project administration): None of those. An "international" locale ought to be available, or customly made, that implements ISO 8601. https://www.w3.org/QA/Tips/iso-date https://en.wikipedia.org/wiki/ISO_8601 Default date format: -MM-DD Default time form

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #6, sr #109371 (project administration): What should be the default time locale? On the server, these are currently available: $ locale -a|while read i;do echo $i:;LC_ALL=$i date +%X;LC_ALL=$i date +%x;LC_ALL=$i date +%c;done C: 07:32:20 05/25/18 Fri May 25 07:32:20 2018 C.UTF-

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #5, sr #109371 (project administration): Yes, being able to explicitly select the data-and-time format would be pretty good. ___ Reply to this item at:

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #4, sr #109371 (project administration): What about having a separate selection box for LC_TIME on /i18n.php? ___ Reply to this item at: ___

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #3, sr #109371 (project administration): Oof... That's not really better: now it lists dates in the idiotic American format: 05/24/2018. But in the bugs itself it still shows the day first: "Submitted on: Thu 24 May 2018 04:40:04 PM CEST". It would be much better if in the lis

[savannah-help-public] [sr #109371] bug tracker date format excessive

Update of sr #109371 (project administration): Status:None => In Progress Assigned to:None => ineiev ___ Follow-up Comment #2: I've just pu

[savannah-help-public] [sr #109371] bug tracker date format excessive

Follow-up Comment #1, sr #109371 (project administration): Yes, I second this. The two-line column is ugly, and contains far too much information. (But don't abbreviate the year, so as to keep it obvious which of the numbers is the year, for people whose locale uses a different ordering.) Maybe

[savannah-help-public] [sr #109371] bug tracker date format excessive

URL: Summary: bug tracker date format excessive Project: Savannah Administration Submitted by: Stevan_White Submitted on: Mon 21 Aug 2017 01:11:17 PM CEST Category: Savannah tracke