aboutsummaryrefslogtreecommitdiff
path: root/python/python3-x-wr-timezone/slack-desc
diff options
context:
space:
mode:
Diffstat (limited to 'python/python3-x-wr-timezone/slack-desc')
-rw-r--r--python/python3-x-wr-timezone/slack-desc19
1 files changed, 19 insertions, 0 deletions
diff --git a/python/python3-x-wr-timezone/slack-desc b/python/python3-x-wr-timezone/slack-desc
new file mode 100644
index 0000000000..8417301895
--- /dev/null
+++ b/python/python3-x-wr-timezone/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct. It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+ |-----handy-ruler------------------------------------------------------|
+python3-x-wr-timezone: python3-x-wr-timezone (Handling of X-WR-TIMEZONE icalendar property)
+python3-x-wr-timezone:
+python3-x-wr-timezone: Some calendar providers introduce the non-standard X-WR-TIMEZONE
+python3-x-wr-timezone: parameter to ICS calendar files. Strict interpretations according to
+python3-x-wr-timezone: RFC 5545 ignore the X-WR-TIMEZONE parameter. This causes the times
+python3-x-wr-timezone: of the events to differ from those which make use of X-WR-TIMEZONE.
+python3-x-wr-timezone:
+python3-x-wr-timezone: This module aims to bridge the gap by converting calendars using
+python3-x-wr-timezone: X-WR-TIMEZONE to a strict RFC 5545 calendars. So, let's put our
+python3-x-wr-timezone: heads together and solve this problem for everyone!
+python3-x-wr-timezone: