Page MenuHomePhabricator

Should support less-pedantic, T-less ISO-style option for the "Date format" preference
Closed, DuplicatePublic


Now, following standards is great and all, but in my opinion, I think that the ISO and time like "2014-02-15T01:12:23" takes things a *bit* too far.

I would think it would be REALLY nice if you would take advantage of this provision of [ RFC 3339]:

NOTE: ISO 8601 defines date and time separated by "T".
Applications using this syntax may choose, for the sake of
readability, to specify a full-date and full-time separated by
(say) a space character.

I don't particularly care if this is implemented as a new "RFC 3339" or "ISO-style" value for the option, or it replaces the existing "ISO 8601" value. But seriously, I'm not sure I've ever seen the T format in user-facing output *anywhere* else, and it's REALLY a pain -- not only is it hard on the visual centre of my brain, but also not very amenable to easy selection for copy+paste. (Firefox wants to select either none of the "15T01", or the whole chunk.)

Judging by, I'm guessing that the "T" was mostly meant to help in formats where fields are separated from one another by whitespace, and it is desired to have a combined date+time field.

Version: 1.23.0
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 2:56 AM
bzimport set Reference to bz61409.
bzimport added a subscriber: Unknown Object (MLST).

not only is it hard on the visual centre of my brain, but also not very amenable >to easy selection for copy+paste.

Wouldn't the default "November 12, 2001" format be the easiest on the "visual" centre of the brain?

It turns out that GNU date just calls this RFC 3339; look up "--rfc-3339" on, or run:

$ info --index-search=--rfc-3339 coreutils
(with the "info" package installed, obviously)