icalendar-implementations: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(reformat a bit as a more general calendar programs page, move contributors to bottom (consider dropping), add some more details)
Line 1: Line 1:
= iCalendar implementations =
<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar [[RFC2445]] standard.


In the development of [[hcalendar|hCalendar]] and proxies like X2V, we have discovered various behaviors and quirks of RFC 2445 iCalendar implementations.
In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.


This page is here for keeping track of them.
== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar


== Contributors==
== products ==
* Tantek Çelik
=== Apple iCal ===
* [[DimitriGlazkov|Dimitri Glazkov]]
Apple iCal application aka iCal.app.
 
* platform: OSX
== Products ==
* handles "webcal:" URLs and supports subscribing to events.
 
=== iCal.app ===
 
platform: OSX
 
==== subscription handling ====
 
supports the non-standard "webcal:" protocol


=== KOrganizer ===
=== KOrganizer ===
 
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
platform: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.
 
==== subscription handling ====
 
supports the non-standard "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.


=== Evolution ===
=== Evolution ===
 
* platform: Fedora Core 3
platform: Fedora Core 3
* supports "webcal:" protocol
 
==== subscription handling ====
 
supports the non-standard "webcal:" protocol


=== Sunbird ===
=== Sunbird ===
 
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
AKA [http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
 
* supports "webcal:" protocol
platform: XP, others?
 
==== subscription handling ====
 
supports the non-standard "webcal:" protocol


=== Microsoft Outlook ===
=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files,  "webcal:" URLs, etc.


platform: 2003
==== Microsoft Outlook 2003 ====
 
Microsoft Outlook 2003 (MSOutlook2k3)
==== Importing of VEvents ====
* platforms: Windows
 
* supports importing .ics files
Requires <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code>
===== MSOutlook2k3 general comments =====
 
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed''').  If any of the three is not present, returns this message:
If any of the three is not present, returns this message:


<pre>
<pre>
Line 62: Line 49:
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 [[rfc-2445#vCalendar|vCalendar 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>.
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 =====
===== MSOutlook2k3 sample importable iCalendar =====
<pre>
<pre>
BEGIN:VCALENDAR
BEGIN:VCALENDAR
Line 78: Line 65:
</pre>
</pre>


===== Minimal valid iCal 1.0 event, importable by MS Outlook 2003 =====
===== MSOutlook2k3 sample importable vCalendar =====
 
<pre>
<pre>
BEGIN:VCALENDAR
BEGIN:VCALENDAR
Line 88: Line 74:
</pre>
</pre>


== Related Pages ==
== notes ==
* the "webcal:" URL protocol scheme is non-standard.
 
== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
 
== related pages ==
{{hcalendar-related-pages}}
{{hcalendar-related-pages}}

Revision as of 12:31, 7 January 2008

iCalendar implementations

This is a list of calendar programs, applications and services that support the iCalendar RFC2445 standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of hCalendar and proxies like X2V.

services

Google Calendar

http://calendar.google.com/

  • supports subscribing to "webcal:" and "http:" URLs to iCalendar

products

Apple iCal

Apple iCal application aka iCal.app.

  • platform: OSX
  • handles "webcal:" URLs and supports subscribing to events.

KOrganizer

  • platforms: All Linux, *BSD, etc. (Wherever KDE runs)
  • supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

Evolution

  • platform: Fedora Core 3
  • supports "webcal:" protocol

Sunbird

Mozilla Sunbird

  • platforms: Windows XP, others?
  • supports "webcal:" protocol

Microsoft Outlook

Microsoft Outlook 2007

Microsoft Outlook 2007 (MSOutlook2k7)

  • platforms: Windows
  • supports importing and subscribing to .ics files, "webcal:" URLs, etc.

Microsoft Outlook 2003

Microsoft Outlook 2003 (MSOutlook2k3)

  • platforms: Windows
  • supports importing .ics files
MSOutlook2k3 general comments

For importing, MSOutlook2k3 apparently requires VEVENTS to have UID, DTSTAMP, and METHOD properties. (citation/platform/date tested info needed). 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 vCalendar 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.

MSOutlook2k3 sample importable iCalendar
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
MSOutlook2k3 sample importable vCalendar
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR

notes

  • the "webcal:" URL protocol scheme is non-standard.

contributors

related pages

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.