with ics event
BEGIN:VEVENT
SUMMARY: TEST
DTSTART;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201028T133000
DTEND;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201028T150000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20201015T165939Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
the offset here COULD be central time or eastern time.
(we dodn't parse rest of TZID value)
If we DO parse the TZID value, the string is not the current string used by MS
https://support.microsoft.com/en-us/help/973627/microsoft-time-zone-index-values
so like node-ical we need to look up the old TZ name to get the current TZ name, so we can find the IANA name.. to resolve the ambiguity.
jens-maus/node-ical#32
with ics event
the offset here COULD be central time or eastern time.
(we dodn't parse rest of TZID value)
If we DO parse the TZID value, the string is not the current string used by MS
https://support.microsoft.com/en-us/help/973627/microsoft-time-zone-index-values
so like node-ical we need to look up the old TZ name to get the current TZ name, so we can find the IANA name.. to resolve the ambiguity.
jens-maus/node-ical#32