icalendar-implementations: Difference between revisions
(Added self to contributors) |
(Minimal importable iCal events for MS Outlook 2003) |
||
| Line 54: | Line 54: | ||
After some testing, this seems to be the generic message to indicate a problem with event import. | After some testing, this seems to be the generic message to indicate a problem with event import. | ||
No such restriction is placed on [http://www.imc.org/pdi/vcal-10.txt iCal 1.0] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>. | No such restriction is placed on [http://www.imc.org/pdi/vcal-10.txt iCal 1.0] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>. | ||
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>. | |||
===== Minimal valid iCal 2.0 event, importable by MS Outlook 2003 ===== | |||
<pre> | |||
BEGIN:VCALENDAR | |||
VERSION:2.0 | |||
METHOD:PUBLISH | |||
BEGIN:VEVENT | |||
UID:0 | |||
DTSTAMP:20060601T080000 | |||
DTSTART:20060601T080000 | |||
END:VEVENT | |||
END:VCALENDAR | |||
</pre> | |||
===== Minimal valid iCal 1.0 event, importable by MS Outlook 2003 ===== | |||
<pre> | |||
BEGIN:VCALENDAR | |||
BEGIN:VEVENT | |||
DTSTART:20060601T080000 | |||
END:VEVENT | |||
END:VCALENDAR | |||
</pre> | |||
Revision as of 18:17, 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.
Note that VERSION property may be omitted. In this case, value inferred as 1.0.
Minimal valid iCal 2.0 event, importable by MS Outlook 2003
BEGIN:VCALENDAR VERSION:2.0 METHOD:PUBLISH BEGIN:VEVENT UID:0 DTSTAMP:20060601T080000 DTSTART:20060601T080000 END:VEVENT END:VCALENDAR
Minimal valid iCal 1.0 event, importable by MS Outlook 2003
BEGIN:VCALENDAR BEGIN:VEVENT DTSTART:20060601T080000 END:VEVENT END:VCALENDAR