[fc] Repository: icalendar

Branch: refs/heads/master
Date: 2017-09-28T18:45:43+02:00
Author: Christian Geier (geier) <[email protected]>
Commit: collective/icalendar@043cf5a

Accept Windows timezone identifiers as valid.

Currently we accept Olson timezone identifiers (tzids) as valid, even
when no matching VTIMEZONE component is present.  Windows tzids are
different from Olson tzids, but also far spread.  Some software produces
.ics files using those Windows tzids with missing VTIMEZONE components.
While in general our stance is to only support standard compliant .ics
files and try to get the issuer of the invalid .ics files to fix their
software, I believe our chances here are very slim.  On the other hand,
a lot of those .ics files exist in the wild and not supporting those
Windows tzids is a source of major inconvenience for our users.  We
should there accept Windows tzids as we do for Olson tzids.  The unicode
consortium has a suggested mapping from Windows tzids to Olson tzids
[0], which we now make use of.

[0] http://www.unicode.org/cldr/charts/29/supplemental/zone_tzid.html

Files changed:
A src/icalendar/windows_to_olson.py
M CHANGES.rst
M src/icalendar/prop.py
M src/icalendar/tests/test_unit_prop.py
Repository: icalendar

Branch: refs/heads/master
Date: 2017-09-28T21:49:05+02:00
Author: Johannes Raggam (thet) <[email protected]>
Commit: collective/icalendar@720dd8b

Merge pull request #242 from collective/MStimezones

Accept Windows timezone identifiers as valid.

Files changed:
A src/icalendar/windows_to_olson.py
M CHANGES.rst
M src/icalendar/prop.py
M src/icalendar/tests/test_unit_prop.py