aboutsummaryrefslogtreecommitdiff
path: root/python/python3-x-wr-timezone/README
diff options
context:
space:
mode:
authorJeremy Hansen <jebrhansen+SBo@gmail.com>2025-09-12 10:17:34 +0700
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2025-09-13 00:34:04 +0700
commit59f5650b412dbe23fff55aeb2c66f2e1d77cf541 (patch)
tree9da973a7da96370649d0f2ef8b1086e8bf866d56 /python/python3-x-wr-timezone/README
parent50340a4ecb2df87df4c79326c6d0b4573e6bb588 (diff)
python/python3-x-wr-timezone: Added (Repair Google Calendar).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'python/python3-x-wr-timezone/README')
-rw-r--r--python/python3-x-wr-timezone/README10
1 files changed, 10 insertions, 0 deletions
diff --git a/python/python3-x-wr-timezone/README b/python/python3-x-wr-timezone/README
new file mode 100644
index 0000000000..99a53683fa
--- /dev/null
+++ b/python/python3-x-wr-timezone/README
@@ -0,0 +1,10 @@
+python3-x-wr-timezone (Handling of X-WR-TIMEZONE icalendar property)
+
+Some calendar providers introduce the non-standard X-WR-TIMEZONE
+parameter to ICS calendar files. Strict interpretations according to
+RFC 5545 ignore the X-WR-TIMEZONE parameter. This causes the times
+of the events to differ from those which make use of X-WR-TIMEZONE.
+
+This module aims to bridge the gap by converting calendars using
+X-WR-TIMEZONE to a strict RFC 5545 calendars. So, let's put our
+heads together and solve this problem for everyone!