Article View: comp.text
Article #5005Re: All numeric representation of dates
From: Henry Spencer
Date: Mon, 29 Aug 1988 17:15
Date: Mon, 29 Aug 1988 17:15
23 lines
1614 bytes
1614 bytes
In article <2882@hubcap.UUCP> billwolf@hubcap.clemson.edu writes: >> I also question the human engineering of forms that put the year first. >> It is consistent, and in some sense elegant, but it is poorly adapted to >> human needs. The most important information should be first. For most >> uses of dates, that is the day number, followed by the month. > > Ah, I see... Tell me, do you think your odometer should present > the last two digits first, then some verbal representation of > the next-to-last two digits, followed by the remaining digits? Since the number on an odometer is simply a kilometer/mile number, with no significant internal structure, the analogy is invalid. If mileage were given as a <country, state, county, miles> tuple, would you want the state displayed as a name or a number? > If you REALLY want to question methods of presenting time, why > not investigate the asinine 12-hour format used in the United > States? The 24-hour, European standard is MUCH more sensible... Well, personally I use the 24-hour form whenever possible. -- Intel CPUs are not defective, | Henry Spencer at U of Toronto Zoology they just act that way. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu
Technical Details
Message-ID:
<1988Aug29.171545.10737@utzoo.uucp>Path:
arc1-ca.pugleaf.net!utzoo!henryReferences:
<1988Aug28.010835.17290@utzoo.uucp> <2882@hubcap.UUCP>Show Full Headers
Complete Article Headers
Newsgroups: comp.text,comp.std.internat Path: arc1-ca.pugleaf.net!utzoo!henry From: henry@utzoo.uucp (Henry Spencer) Subject: Re: All numeric representation of dates Message-ID: <1988Aug29.171545.10737@utzoo.uucp> Organization: U of Toronto Zoology References: <1988Aug28.010835.17290@utzoo.uucp> <2882@hubcap.UUCP> Date: Mon, 29 Aug 88 17:15:45 GMT