Re: Value of a date in Numbers
Re: Value of a date in Numbers
- Subject: Re: Value of a date in Numbers
- From: Luther Fuller <email@hidden>
- Date: Wed, 04 Feb 2009 09:32:15 -0600
On Feb 4, 2009, at 8:03 AM, Mark J. Reed wrote:
ISO 8601. Seriously - it's 2009, you can afford to use 14 to 76 bytes
to store a timestamp.
In any case, Unix timestamps are always unambiguous - well, except for
1-second uncertainties around leap seconds - because they are stored
as a single integer value representing the number of (non-leap)
seconds since 1 January 1970 at midnight GMT. There is no such thing
as a "local timestamp", just the local vs utc representation of a
single unambiguous time value. So any archive format or filesystem
that uses such timestamps is also unambiguous in that regard.
So, a file's creation date is independent of the zone in which it was
created. I searched "ISO 8601" on ADC and found "Time Utilities
Reference". But, I haven't read thru this document, yet.
Now, back to the original problem: Do dates stored in Numbers follow
this standard?
and: Do dates stored in iCal follow this standard?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden