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 346337 - smart date formatting
smart date formatting
Status: RESOLVED DUPLICATE of bug 676898
Product: nautilus
Classification: Core
Component: Views: List View
unspecified
Other All
: Normal enhancement
: 3.2
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 333732 504442 564277 664899 (view as bug list)
Depends on: 325064
Blocks:
 
 
Reported: 2006-07-01 07:03 UTC by Emmanuel Touzery
Modified: 2013-05-26 16:23 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
same folder in nautilus and in file opener (177.26 KB, image/jpeg)
2006-07-01 07:05 UTC, Emmanuel Touzery
  Details
Use a smart date/time formatting (#346337). (14.08 KB, patch)
2010-05-12 11:24 UTC, Cosimo Cecchi
none Details | Review

Description Emmanuel Touzery 2006-07-01 07:03:43 UTC
When you browse a directory with the GTK file opener, dates are smartly formatted. "Today", "Monday", probably "Yesterday" etc.
In nautilus we just see eg 26/06/2006.

I think the application would be nicer to use if we had in nautilus the same smart date formatting (more human-readable dates) than in the gtk file opener.

Other information:
Comment 1 Emmanuel Touzery 2006-07-01 07:05:08 UTC
Created attachment 68234 [details]
same folder in nautilus and in file opener

The dates as shown in the file opener are much more pleasing and much more readable to human eyes.
Comment 2 A. Walton 2009-10-06 17:06:06 UTC
*** Bug 564277 has been marked as a duplicate of this bug. ***
Comment 3 Allan Day 2010-04-11 19:01:09 UTC
This is a great proposal. It would give Nautilus more polish and make it easier for users to understand.
Comment 4 Hylke Bons 2010-04-11 19:57:42 UTC
I'm not sure about the date format though.
It will have to be grabbed from the user's locale.
The number of seconds is currently displayed which isn't worth mentioning  compared to the noise it causes. We probably only need to display the year if year_modified != current_year.
The date formats will have to be consistent amongst the lists as well.
Comment 5 Cosimo Cecchi 2010-04-12 00:25:58 UTC
Let's try to work on this for 2.32/3.0.
Comment 6 A. Walton 2010-04-12 00:35:31 UTC
Marking the dependency on an API like the one proposed in bug 325064. We could always throw it somewhere in eel, but it'd be better if we could get that patch merged into glib.
Comment 7 Cosimo Cecchi 2010-05-12 11:24:41 UTC
Created attachment 160891 [details] [review]
Use a smart date/time formatting (#346337).

This is not the complete patch, which removes the locale preference altogether from Nautilus, but is a good overview for the heuristic I want to use to format the date/time.

In this case, I used nl_langinfo() to fetch the default date/time format for the current locale.
 * in the time string, seconds are removed
 * in the date string, we use "Today", "Yesterday" or the name of the day of the week (according to the locale) in case the date is in the same week; otherwise we use the locale preferred representation of the date, substituting the month with its abbreviated name, the year with either the full year (including the century) or its alternative representation, according to the locale, and the day with either the number of the day in the month or its alternative representation, according to the locale.
Comment 8 Allan Day 2010-06-21 10:46:24 UTC
*** Bug 504442 has been marked as a duplicate of this bug. ***
Comment 9 Cosimo Cecchi 2011-03-31 17:38:24 UTC
We should try to pack this for 3.2.
Comment 10 Cosimo Cecchi 2011-03-31 17:40:21 UTC
*** Bug 333732 has been marked as a duplicate of this bug. ***
Comment 11 Cosimo Cecchi 2011-11-29 03:00:37 UTC
*** Bug 664899 has been marked as a duplicate of this bug. ***
Comment 12 William Jon McCann 2012-08-01 13:04:39 UTC

*** This bug has been marked as a duplicate of bug 676898 ***