Re: Need localization-proof method of transporting dates.
Re: Need localization-proof method of transporting dates.
- Subject: Re: Need localization-proof method of transporting dates.
- From: Greg Guerin <email@hidden>
- Date: Sat, 4 Apr 2009 10:50:58 -0700
Graham Cox wrote:
One problem I've had occasional reports of is that the expiry is
prematurely detected, and it seems to be on systems with system
language set other than English. I need to store and check the
dates in a way that is not sensitive to this. I thought I was, yet
the reports persist.
When a premature expiry occurs, how premature is it? A day? A few
days? An hour? A few hours?
If it's up to a few hours, it might be the time-zone difference. If
it's at most one day, at about the same local time of day, then that
might also be the time-zone difference. If it's a few days, then
time-zone is unlikely. Otherwise I concur with Andy Lee: try storing
the timeIntervalSince1970.
You might also try correlating it to the specific language, locale,
and/or calendar type. It could be a bug in a particular calendrical
case, such as the Buddhist calendar.
-- GG
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden