The key is that it doesn't accept the VTIMEZONE updates that break ical4j. If such an update arrives from the iCalendar parser, it's ignored so that the default VTIMEZONE for the respective TZID remains active and calculations use the default time zone.
Hopefully closes #94
The key is that it doesn't accept the VTIMEZONE updates that break ical4j. If such an update arrives from the iCalendar parser, it's ignored so that the default VTIMEZONE for the respective TZID remains active and calculations use the default time zone.