Hello Chuck!
** On Tuesday 29.09.20 - 22:15, Chuck Pierson wrote to August Abolins:
>> Thanks for pointing that out. I recently paid closer attention to
>> what my online banking system uses, invoices, and what the gov't
>> prefers. Bank = dd/mm/yyyy. Statments = mm/dd/yyyy Gov't =
>> yyyy/mm/dd
CP> Strange. In the US, most people and places use mm/dd/yyyy. In the
CP> military, we used dd/mm/yyyy. I got used to it, which helped me later.
CP> I worked in the oil and gas industry for years, and had communicated
CP> internationally a lot. Dates could have been confusing there.
I think yyyy/mm/dd makes the most sense. It resembles the way an odometer
works or how any other click counter works, or how the incremental numbering
system works in general.
I've worked with the MIL-STD docs for the Standard Electronic Modules Program
(SEMP). That is where I first noticed the consistent and sensible use of dd/
mm/yyyy. (like an odometer in reverse)
Looking at some of those MIL-STD docs brings back a lot of memories. My work
pertained to the electrical requirements of the modules. Start with MIL-STD
1389C and begin the journey of standard pointing to standard pointing to
standard pointing to standard... (arghh)
--
../|ug
--- OpenXP 5.0.48
* Origin: :) :D :O :( :[ ;) 8) B) :> |I :P =) :S :B :] :\ (2:221/1.58)
|