The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Subject: ISO date format [was: Wireless Extension update]
Date: 20 Oct 2001 08:52:27 -0400	[thread overview]
Message-ID: <1003582348.2042.260.camel@thanatos> (raw)

I don't think it's true that there are alternative ISO standards,
otherwise the ISO standard (YYYY-MM-DD) wouldn't be a standard.
The standard applies only to _numerical_ dates, however.

This web page gives a summary:
http://www.cl.cam.ac.uk/~mgk25/iso-time.html

Quotation from the page:
ISO 8601 is only specifying numeric notations and does not cover
dates and times where words are used in the representation. It is
not intended as a replacement for language-dependent worded date
notations such as "24. Dezember 2001" (German) or "February 4, 1995"
(US English).

When writing dates in English I like "4 February 2001" or
"4 Feb 2001" since it reads easily and still puts day, month, year
in a sane order.

I tried to look up the standard itself at the ISO website but
found that I would have to pay 104 Swiss Francs to download the
pdf file.

--
Thomas Hood

--- original message ---

Hi Randy.

>> - * Version :   11      28.3.01
>> + * Version :   12      5.10.01

> nitpicking, i'm sure, but:

> 5.10.01 could have several meanings, usually depending on geographic
> location etc., and there is an ISO standard (8601) which says:

> The international standard date notation is YYYY-MM-DD

There is also another ISO standard (I forget the number) which states
that the international standard date notation is any of...

	DD.MM.YYYY	(European)
	MM/DD/YYYY	(American)
	YYYY-MM-DD	(Japanese)

...with the punctuation character specifying the one in use. I note that
the dates as originally quoted above are clearly consistant with this
standard, so see no problem myself.

Personally, I prefer to use the DD-MMM-YYYY format myself, where MMM in
the three-letter English abbreviation for the month in question, and
there is thus no room for misreading it as something else.

> I'd prefer not to be confused by the '>' quoted notation above,
> although I don't mind the dots instead of hyphens.

I'm so used to > quoting in emails that anything else gets me confused.

Best wishes from Riley.






                 reply	other threads:[~2001-10-20 12:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1003582348.2042.260.camel@thanatos \
    --to=jdthood@mail.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox