icalendar-implementations: Difference between revisions
AndyMabbett (talk | contribs) m (template) |
AndyMabbett (talk | contribs) (from ical-imlpementations) |
||
Line 39: | Line 39: | ||
* platforms: Windows | * platforms: Windows | ||
* supports importing .ics files | * supports importing .ics files | ||
===== MSOutlook2k3 general comments ===== | ===== 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: | 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: | ||
Line 51: | Line 52: | ||
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>. | 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>. | ||
* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST) | |||
===== MSOutlook2k3 sample importable iCalendar ===== | ===== MSOutlook2k3 sample importable iCalendar ===== |
Revision as of 18:36, 28 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
- 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
- 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
.
- UID and DTSTAMP is required for Outlook to import. GeoffWebb 14:03, 9 Dec 2005 (PST)
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
- Tantek Çelik
- Dimitri Glazkov
- hCalendar - specification
- hCalendar intro - plain English introduction
- hCalendar authoring - learn how to add hCalendar markup to your existing events.
- hCalendar creator (hCalendar creator feedback) - create your own hCalendar events.
- hCalendar cheatsheet - hCalendar properties
- hCalendar examples in the wild - an on-going list of websites which use hCalendars.
- hCalendar implementations - websites or tools which either generate or parse hCalendars
- hCalendar FAQ - If you have any questions about hCalendar, check here.
- hCalendar parsing - normative details of how to parse hCalendar.
- hCalendar profile - the XMDP profile for hCalendar
- hCalendar singular properties - an explanation of the list of singular properties in hCalendar.
- hCalendar tests - a wiki page with actual embedded hCalendar events to try parsing.
- hCalendar "to do" - jobs to do
- hCalendar advocacy - encourage others to use hCalendar.
- iCalendar implementations
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.
- hCalendar Brainstorming - brainstorms and other explorations relating to hCalendar
- hCalendar issues - issues with the specification