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

[Martin Apel via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]

Hi Lars,


Lars Ingebrigtsen <larsi@gnus.org> 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/Ri-y_fRwJa3GX2PQPOmvUlhqVkVjG5IMhtG34Ywo4bup69pP_gPIWh_-ZlybT53XME0E4c2ZJnEeq4Nrivo6iw>==
> (no login or additional action will be requested).
>
>
> Martin Apel <martin.apel@3ds.com> writes:
>
>> 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.
>
> If you have an event that repeats yearly, that's a lot of entries.  But
> more importantly, you don't know a year in advance what the actual time
> is going to be until much later -- gummints change time zone rules on a
> whim, and a 4:00 PM event in New York time may or may not be 22:00
> German time in five months time -- you can't tell in advance.
>
> The only way to make this work reliably is to store the actual time zone
> of the event.

You are right, I thought that these times are fairly fixed. I think for the time being I have to be careful with
appointments created in different timezones, because extending the diary package is beyond my ELisp skills and also
beyond my free time.
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 3DS.compliance-privacy@3ds.com<mailto:3DS.compliance-privacy@3ds.com>


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