I have found the origin of the problem with dtcm. It is not caused by a
bug in rpc.cmsd or the csa library but by the particular value of the TZ
variable.
Starting dtcm with
TZ=Europe/Paris /usr/dt/bin/dtcm
does not produce the incorrect shift of the start time of the recurring
event at the dat
I agree that storing the time of a given event in UTC as is done in the
XAPIA format and in the callog file under /var/spool/calendar is going
to create ambiguities with recurring events that cross a DST change.
The program is forced to make assumptions about what the user wants,
i.e. whether th
IMO, the problem has always been that (AFAIK) time zones were not recorded when
scheduling an event. That means that if the event is seen by people in other
time zones, it cannot be presented accurately - an event should be scheduled in
some particular time zone, adjusted as needed to UTC (an a
I have noticed a problem with recurring events in dtcm.
I have created a weekly event "Séminaire" every Monday at 11am.
For the month of March, I notice that the event will start at 11am
except on March 14 and March 21 when it will start at 12am instead of
11am. (see the PNG in attachment)
For t
