3 ms·
If you have ever done anything seriously with time zones you store everything UTC and must use a library to translate. The problem is it is geopolitical, so th
by edoo 8y ago
If you have ever done anything seriously with time zones you store everything UTC and must use a library to translate. The problem is it is geopolitical, so the time zone conversion result can vary based on the date itself as well as the physical location. For example DST was changed in 2007 in the US, there is no option but to programmatically translate.
- jobigoud 8y agoEven if you store in UTC and use a library you have to know what the user mean when they create a recurring appointment. I currently have several recurring alerts in my calendar app. One of them is an alarm everyday at 10 p.m. This must be in local time everywhere I go. Another is a conference call at 10H30 a.m on Wednesdays, Pacific Time (not my timezone). If you treat them the same way one of them will be wrong when I travel.