https://bugs.kde.org/show_bug.cgi?id=421400
Daniel Vrátil <dvra...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |5.112.0
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
Latest Commit| |https://invent.kde.org/fram
| |eworks/kcalendarcore/-/comm
| |it/921e04f64921e86288e57144
| |c82dab2a1a0679b5
--- Comment #18 from Daniel Vrátil <dvra...@kde.org> ---
Git commit 921e04f64921e86288e57144c82dab2a1a0679b5 by Daniel Vrátil.
Committed on 13/10/2023 at 19:57.
Pushed by dvratil into branch 'master'.
ICalFormat: don't shift all-day invite dates to UTC
When generating scheduling message for an event, the ICalFormat
checks whether the event is recurrent and if not it shifts the
start and end datetimes to UTC timezone (since recurring events
need TZ information for proper calculations across DSTs and TZs).
However if the event is an all-day event with start and end datetimes
in local time (e.g. Europe/Prague), this shift effectively moves
the start and end datetimes from midnight to -2 hours previous day.
Later on when writing the DTSTART and DTEND properties, the code
omits the time (since it's an all-day event) and only writes out
DATEs, but now the scheduling message is actually shifted one day
back!
This change extends the check in ICalFormat to also avoid shifting
dates to UTC when the event is an all-day event, since in this case
the timezone information is dropped anyway.
FIXED-IN: 5.112.0
M +24 -0 autotests/testicalformat.cpp
M +1 -0 autotests/testicalformat.h
M +1 -1 src/icalformat.cpp
https://invent.kde.org/frameworks/kcalendarcore/-/commit/921e04f64921e86288e57144c82dab2a1a0679b5
--
You are receiving this mail because:
You are watching all bug changes.
