Calendar:Timezones: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Issues) |
||
| Line 13: | Line 13: | ||
* In what timezone are events created by default? | * In what timezone are events created by default? | ||
* UTC events have issues with recurrance and daylist saving time. For example, 14:00 in UTC can be 12:00 or 13:00 in european time. Recurring every week at 14:00 UTC will change the time in european time. So UTC isn't a suitable storage for normal events. | * UTC events have issues with recurrance and daylist saving time. For example, 14:00 in UTC can be 12:00 or 13:00 in european time. Recurring every week at 14:00 UTC will change the time in european time. So UTC isn't a suitable storage for normal events. | ||
* How to find out the timezone the user lives in? (in tzid format if possible) | |||
=== Suggestions === | === Suggestions === | ||
Revision as of 18:39, 5 February 2005
Timezones
An event can be defined in any timezone, or be 'floating' (meaning there is no timezone defined)
The calendar is displayed in a timezone the users configured (usually the timezone he lives in, but could be anything)
Issues
- In what timezone should the datepicker be when editing an event? In the stored timezone or in the display timezone?
- Should editing show the timezone?
- calIDateTime.jsDate is always in the local timezone. Should it be banned?
- In what timezone are events created by default?
- UTC events have issues with recurrance and daylist saving time. For example, 14:00 in UTC can be 12:00 or 13:00 in european time. Recurring every week at 14:00 UTC will change the time in european time. So UTC isn't a suitable storage for normal events.
- How to find out the timezone the user lives in? (in tzid format if possible)
Suggestions
for editing:
- floating events show the floating time
- other timezones show in the display timezone
- not complete yet