user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Varun Varada <varuncvarada@gmail.com>
Cc: Eric Wong <e@yhbt.net>,  meta@public-inbox.org
Subject: Re: [Patch] Update 24-hour times to use two digits for the hour
Date: Sun, 07 Jun 2020 00:27:34 +0300	[thread overview]
Message-ID: <mu5fvq9l.dag@gnui.org> (raw)
In-Reply-To: <CAD2i4DBxV9BWL=EXQEENudH9WJxR1UivmCPF2RbKNtKB7+WP+w@mail.gmail.com> (Varun Varada's message of "Fri, 5 Jun 2020 17:48:05 -0500")


[-- Attachment #1.1: Type: text/plain, Size: 292 bytes --]

Varun Varada <varuncvarada@gmail.com> wrote:
> The "why?" is that leading zeroes are standard for virtually any 24-hour clock in the world

> any

Nope, at least not for my Electronica-52 watches.  I am too lazy to look for them to take a photo, but thankfully itʼs easily googleable:

[-- Attachment #1.2: electronica-52.jpg --]
[-- Type: image/jpeg, Size: 61368 bytes --]

[-- Attachment #1.3: Type: text/plain, Size: 382 bytes --]


> virtually any

I strongly suspect, the same is true for all models of Electronica watches.  I also suspect, that Montana, whose appearance Bielorussian designers were undoubtedly inspired by, does not feature any leading zeroes either.

> Without a leading zero, a user immediately expects an a.m./p.m. modifier

As youʼve already guessed, at least I absolutely donʼt.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      parent reply	other threads:[~2020-06-06 21:27 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
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 [this message]

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: http://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=mu5fvq9l.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=e@yhbt.net \
    --cc=meta@public-inbox.org \
    --cc=varuncvarada@gmail.com \
    /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).