[Tickets #1881] Support vCal/iCal 1.0/2.0 and differentiate between them

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1881
-----------------------------------------------------------------------
 Ticket             | 1881
 Updated By         | kevin_myer at iu13.org
 Summary            | Support vCal/iCal 1.0/2.0 and differentiate between them
 Queue              | Horde Framework Packages
 State              | Assigned
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Horde Developers
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-12-08 19:05) wrote:

I've been dabbling with this for a bit the past few weeks, because lack of
Palm sync support for recurring events is held up by this.

I've found some other code that does this, to varying degrees:

http://www.simondobson.org/downloads/files/ical2vcal
http://websvn.kde.org/branches/KDE/3.5/kdepim/korganizer/ical2vcal.in?rev=43
8982&view=markup
and the function format_vcal($event) in:
http://cvs.sourceforge.net/viewcvs.py/webcalendar/webcalendar/includes/xcal.
php?rev=1.10&view=markup

Now my initial approach was to work this into the Synthesis Device code for
SyncML but in thinking about that approach, it seems like it might make
sense to have it in the iCalendar framework code.  My thinking is a pair of
functions (with the original names of ical2vcal and vcal2ical) would take an
iCalendar object, and modify the object to make it v1.0 or v2.0 compatible. 
The Synthsis SyncML Device code could call those functions, but they could
also be used anywhere else (like importing old vCal data).  Or for that
matter, have the iCalendar object automatically handle conversion, based on
version requested, with a default of iCal (v2.0).

Any other suggestions or better ideas how to handle this?