I am thinking that sounds better Alan, most of the time your calendar is used by people in the country where the company who set up the calendar is based - not necessarly  the same country as the hoster or visitor. 

For instance if it was used on a club site in Coffs Harbour Australia for band bookings then it's only really useful to have the time zone set for +10 east coast time. Maybe including a clock in the title bar with something like "The time is now HH.MM on the ddth of mmmm yyyy" would give the viewer a nudge  - then if someone in Western Australia was looking at it they would know it was 2 hours ahead of their time.

If your band was playing in Coffs I'd expect that you would be aware of the time difference when you viewed the calendar from America to check the booking before boarding your flight - otherwise you'd be 15-17 hours late for the gig

Regards

Wayne Irving

What is the status of the DST fix? I just upgraded to the latest Events module and I still get exported events showing up an hour off. This is extremely frustrating for me and confusing for users. Every time I upgrade I have to disable the Export Event to Desktop Event (from the Department of Redundancy Department?) link because I can't have people exporting and then showing up an hour late for events.

Please fix the DST issue ASAP! This has been going on for far too long.

I have to agree with Alan, there does appear to be some problem with DST at the core. I currently run my discussion forum at GMT-1 even though I am in GMT. Items I export from the calendar (I'm on an old version) export an hour out. I also have to set my Users Online limit to 80 minutes not 20. This problem occured when the US changed it's DST dates, and for some reason didn't correct itself two weeks later when you would have expected it to. Unfortunately I don't have a robust .net v2 debugging environment (time/wprk and all that) to see what is going on. It looked like it was calls to a .Net dll which were handing out the wrong dst info, so I checked that they had been updated by my provider. They stated that they have been.

So to Alan's point. I suggest that the Event module push to get the core to fix this. The core really should be able to accurately provide a date/time in any timezone, but this doesn't seem to be the case. Having a calendar, or anything that displays a time, that doesn't display in the users current time is mad. I guess in the UK it shouldn't be too bad, everyone is in the same timezone, but as soon as you get into Europe as a whole, or into the US, having info in your own time zone is critical.

My view.... :-)

Roger