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

* Your Email Address
* Spam protection	Enter the letters below: .___._..__..__. __. [__ \| [__][__](__ [____\|_\| \|\| \|.__)
Comment	> 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=438982&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?
Attachment
Watch this ticket