If a vCalendar defines a "custom" timezone (VTIMEZONE), this timezone is not recognized when parsing vEvents in that calendar.
"Custom" timezones are quite common in invitations send by MS Exchange, Outlook, etc. See code below for an example.
Expected behavior
Timezones defined by VTIMEZONE in a vCalendar should be recognized when parsing vEvents - at least if the timezone is defined above the event.
In the example below. the custom timezone "(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" should be handled like according to it's definition.
If a vCalendar defines a "custom" timezone (
VTIMEZONE
), this timezone is not recognized when parsing vEvents in that calendar."Custom" timezones are quite common in invitations send by MS Exchange, Outlook, etc. See code below for an example.
Expected behavior
Timezones defined by
VTIMEZONE
in a vCalendar should be recognized when parsing vEvents - at least if the timezone is defined above the event.In the example below. the custom timezone "(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna" should be handled like according to it's definition.
How to reproduce