From: Varun Varada <varuncvarada@gmail.com>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: [Patch] Update 24-hour times to use two digits for the hour
Date: Fri, 5 Jun 2020 17:48:05 -0500 [thread overview]
Message-ID: <CAD2i4DBxV9BWL=EXQEENudH9WJxR1UivmCPF2RbKNtKB7+WP+w@mail.gmail.com> (raw)
In-Reply-To: <20200605220321.GA17860@dcvr>
Hi Eric,
The "why?" is that leading zeroes are standard for virtually any
24-hour clock in the world
(https://www.google.com/search?q=24-hour+time). This is even codified
in the ISO 8601 standard
(https://en.wikipedia.org/wiki/ISO_8601#Times), which the project
seems to be following. Without a leading zero, a user immediately
expects an a.m./p.m. modifier, which there is not.
Varun
Varun
On Fri, 5 Jun 2020 at 17:03, Eric Wong <e@yhbt.net> wrote:
>
> Varun Varada <varuncvarada@gmail.com> wrote:
> > Hello,
> >
> > Here is a patch to update the timestamps displayed to have 2 digits
> > for the hour when since it is using the 24-hour clock:
>
> Hello Varun, thanks for your interest in the project.
>
> But why this patch?
>
> It's a requirement to document the "why?" for submitting any
> patch to any project.
>
> > # human-friendly format
> > -sub fmt_ts ($) { strftime('%Y-%m-%d %k:%M', gmtime($_[0])) }
> > +sub fmt_ts ($) { strftime('%Y-%m-%d %H:%M', gmtime($_[0])) }
>
> As a human with degraded eyesight, I see leading zeros from
> %H as visual noise which makes numbers harder to read.
>
> %k uses a leading space instead of zero, but still uses two
> digits for >=10 hours. Pretty much any digital clock or timer
> in the real world behaves the same way.
next prev parent reply other threads:[~2020-06-05 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:22 [Patch] Update 24-hour times to use two digits for the hour Varun Varada
2020-06-05 22:03 ` Eric Wong
2020-06-05 22:48 ` Varun Varada [this message]
2020-06-05 23:27 ` Eric Wong
2020-06-06 0:11 ` Varun Varada
2020-06-06 0:27 ` Eric Wong
2020-06-06 21:27 ` Dmitry Alexandrov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD2i4DBxV9BWL=EXQEENudH9WJxR1UivmCPF2RbKNtKB7+WP+w@mail.gmail.com' \
--to=varuncvarada@gmail.com \
--cc=e@yhbt.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).