|
| Index | Recent Threads | Register | |
|
Forums » List all forums » Forum: Known Problems » Thread: Daylight Savings not correct |
|
Total posts in this thread: 6 |
[Change thread status]
[Delete this Thread]
[Move this Thread] [Add To My Favorites] [Watch this Thread] [Post new Thread] |
| Author |
|
|
JN756
New Member
|
I have a non-profit site using Localendar which has been working very well for us. We are starting to expand into using all the features, but before I can let my users know about the iCal features, I'm noticing two problems: A. All my events are stored in the calendar as Eastern Standard time, and aren't correctly reflecting the one-hour daylight savings shift. For the web interface this isn't a problem since it shows 2pm and everyone just uses their local clocks to figure out when 2pm it. However when you iCAl these events into a calendar tool like Outlook, it causes all these events to shift an hour as shown in Outlook or Google's calendar. B. I have the iCal working in Outlook (several versions), Google, and Yahoo, but the Microsoft Live calendar won't accept your iCal format. I've opened a ticket with Microsoft, but they haven't responded at all. Any suggestions on what it going on there? |
|||
|
|
support
localendar Expert  Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
Let's try B first since that's easier... The iCal spec has a few nuances that are unfortunately open to interpretation. Though I find it odd that Outlook would work and not Live. Is the entire feed failing or just specific events? Can you tell us what the error message is? Now on to A When we import an iCal feed, we adjust it from the source timezone (which could be anything) into your local timezone, and we should account for DST movement. Now let's talk about what we export.. I have an event from 9-10PM EST on my calendar. When I export it, the iCalendar feed states that it is DTSTART;TZID=America/New_York:20100829T210000 First, we see it's given as America/New_York, which we also know is the same as EST. And the times in 24 hour format are 21 to 22 (or 9 to 10) The date of the event is also in the file. So any consuming program should know whether or not DST is in effect. Let's suppose someone pulls that into a calendar and they live somewhere where DST isn't observed (or changes at a different time).... That application should look at the user's local time setting and say, "Hey, Marc is reading in an event @ 9PM in New York on Oct 19". But I know his calendar is set to Arizona, so let me move that back 2 hours to local time 7PM. What I think *should* happen next is that the consuming program should say, "Wait a sec - New York is also on DST so he's adding an extra hour. We don't observe that here in AZ, so I've got to move it back to 6PM". I'm seeing this problem on the net for other iCal programs. And it doesn't seem like there's a consensus. Should the provider adjust the item? I argue no. 9PM EST is 9PM EST. The Consumer should look at the date and figure out if DST is in effect and if local adjustments need to be made. However, if you can confirm that both Outlook and Google are expecting *us* to make the change, we'll be a little more flexible since they have more users  Can you tell me the timezones you are working with? What do you have set in all 3 programs? ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
One other thing - is your post related to a different calendar than JN756 ? I dont see any events there, and I wanted to take a closer look at your data. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
[Update] Since Google and Microsoft have pushed DST calculations on the feed provider, it seems like we have no choice but to follow to preserve interoperability with them  We've made a change that should correct your issue. However, what we still need to figure out is how to handle repeating events that span DST changes. We'll be doing some testing with Google and Outlook to see what they export and what they expect.---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
|
JN756
New Member
|
Thanks for the updates. Sorry, I was checked out on this problem for a while. The calendar is for the Herndon Band (uid: herndonband) Jeff |
|||
|
|
support
localendar Expert Joined: Aug 9, 2022 Posts: 6437 Status: Offline |
Hey Jeff, If you saw my update, we did start including TZ info in the iCal feed to account for this. Does that solve your issue? ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
|||
|
| [Show Thread Printable Version] [Post new Thread] |
Help! | Cobranding | Legal | Privacy Policy | About localendar.com | Contact Us |
