[Cosmo-dev] ical bug with VALUE=DATE-TIME parameter in .ics

[Randy Letness]

Randy Letness wrote:
> Brian Moseley wrote:
>> i feel okay about removing VALUE=DATE-TIME - maybe we should do it
>> when we store the item?
>>   
>
> Of course now I found that ical doesn't like multiple dates in an 
> EXDATE property, so for multiple EXDATEs it wants:
>
> EXDATE:date1
> EXDATE:date2
> EXDATE:date3
> afoundation.org/mailman/listinfo/cosmo-dev

Given that there are now two EXDATE problems that ical 2.x has with the 
icalendar that cosmo exports (and I'm sure there are more), do we patch 
cosmo to export ical 2.x friendly icalendar?  I'm sure other clients 
have other quirky problems(hello Outlook), so its impossible to ensure 
the icalendar exported will be compatible with all clients.   Another 
options is to offer different icalendar exports tailored to a specific 
client. 

I would rather offer client specific exports than to patch the base 
export because its impossible to offer a one-size-fit-all icalendar 
export.  Of course we should notify the client developers for those 
clients that don't adhere to the icalendar spec.

-Randy