Subject: bug#56125: 28.1; Timezone conversion sometimes wrong for recurring events, when importing ical to diary

From: Martin Apel <[email-masked]>
Date: Thu, 23 Jun 2022 12:06:59 +0200

Hallo Lars,

Lars Ingebrigtsen <[email-masked]> writes:

> EXTERNAL EMAIL : The sender of this email is external to 3DS. Be wary of the content and do not open unexpected
> attachments or links. If you consider this email as spam, you can click the following link
> <https://spam-report.3ds.com/?linktext=https://www.mailcontrol.com/sr/kra54IrKYHHGX2PQPOmvUiOFufhVdryLdnNqnQjMvSqaqSk_Vs5yB6Bl580EfnElME0E4c2ZJnGzbAWAmKJQAw>==
> (no login or additional action will be requested).
>
>
> Martin Apel <[email-masked]> writes:
>
>> Maybe this is a more general problem, that the diary does not consider
>> timezones at all. I think, that the conversion functionality would
>> need to convert each date of a recurring event separately, as the
>> daylight savings time might have changed between consecutive
>> repetitions.
>
> Yes, for repeating events, diary has to keep track of what the original
> time zone (and time) is, and convert from that time each day.  I've
> skimmed the diary functions, and it doesn't seem like that's something
> the diary functions have taken into accound, so patches welcome.

I suppose, that it would be a major undertaking to teach the diary about timezones. As this is a personal diary it
probably also doesn't make too much sense. Therefore I wonder, if it wouldn't be the better approach, to split a
recurring event from ical into separate events in the diary. This way the conversion functionality could convert each
event separately. When I find the time, I can try to improve this, but for now I don't fully understand the details of
the code.
This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or responsibility for any use of or reliance on this email.

Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer at [email-masked]<mailto:[email-masked]>

For other languages, go to https://www.3ds.com/terms/email-disclaimer