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	> just in case, here's the full context this came from initially (a > response to someone from the Synthesis folks): > > > > > > > > The problem is that the horde server for some unknown reason now sends > > calendar entries in an invalid vCalendar format (a mixture of vCalendar > > 1.0 and iCalendar 2.0). This is clearly a bug in the server, and has > > nothing to do with the version v2.1 vs. v2.5 of our client. > > > > In Detail: > > > > The server sends entries with MIME type "text/x-vcalendar", which would > > indicate vCalendar v1.0. > > > > However, the actual data set is someting like: > > > > BEGIN:VCALENDAR > > VERSION:2.0 > > PRODID:-//The Horde Project//Horde_iCalendar Library //EN > > METHOD:PUBLISH > > BEGIN:VEVENT > > DTSTART:20050429T100000Z > > DTEND:20050429T110000Z > > DTSTAMP:20050426T004536Z > > SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:= > > Servers de Poort > > TRANSP:OPAQUE > > ORGANIZER;CN=Joeri Pronk:MAILTO:joeri@joeri.nu > > CATEGORIES:Esprit > > END:VEVENT > > END:VCALENDAR > > > > The second line (VERSION:2.0) identifies this as a iCalendar 2.0 entry. > > However, it is NOT iCalendar 2.0 compatible as the CHARSET attribute is > > not allowed in iCalendar 2.0. > > > > If the VERSION line is fixed to read VERSION:1.0, it will be conformant > > and will work with our client.
Attachment
Watch this ticket