icalendar-implementations: Difference between revisions
Jump to navigation
Jump to search
(Detailed documentation of MS Outlook 2003 behavior) |
(Added self to contributors) |
||
| Line 7: | Line 7: | ||
== Contributors== | == Contributors== | ||
* Tantek Çelik | * Tantek Çelik | ||
* [[DimitriGlazkov|Dimitri Glazkov]] | |||
== Products == | == Products == | ||
Revision as of 18:08, 3 July 2006
iCalendar implementations
In the development of hCalendar and proxies like X2V, we have discovered various behaviors and quirks of RFC 2445 iCalendar implementations.
This page is here for keeping track of them.
Contributors
- Tantek Çelik
- Dimitri Glazkov
Products
iCal.app
platform: OSX
subscription handling
supports the non-standard "webcal:" protocol
Evolution
platform: Fedora Core 3
subscription handling
supports the non-standard "webcal:" protocol
Sunbird
AKA Mozilla Sunbird
platform: XP, others?
subscription handling
supports the non-standard "webcal:" protocol
Microsoft Outlook
platform: 2003
Importing of VEvents
Requires UID, DTSTAMP, and METHOD
If any of the three is not present, returns this message:
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format. To avoid this error, set the appointment option to Gregorian instead of Lunar.
After some testing, this seems to be the generic message to indicate a problem with event import.
No such restriction is placed on iCal 1.0 events. So, if VERSION:1.0 is output instead of VERSION:2.0, the only required field is DTSTART.