iCalendars often contain custom Timezone definitions (VTIMEZONE) which are not
matching standard timezone names. In such a case the library will, wrongly,
throw a 'bad parameter' exception.
The attached file is a test case.
In that file, parsing
EXDATE;TZID="Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna":20101216T10000
... will cause an exception
The library should handle custom timezones, but will presumably need a more
richer implementation than java.util.TimeZone: for example JodaTime's
DateTimeZone which can be build dynamically by DateTimeZoneBuilder.
Original issue reported on code.google.com by luc.cl...@gmail.com on 12 Jan 2011 at 8:53
Original issue reported on code.google.com by
luc.cl...@gmail.comon 12 Jan 2011 at 8:53Attachments: