[kronolith] Default timezone and CalDAV event synchronization

[Eduardo M KALINOWSKI]

I sync my calendar with Lightning using CalDAV.

If I select a timezone when creating the event in Kronolith, the event
in Lightning uses the selected timezone and the time in that timezone
(when editing the event).

But if I use the default timezone, the event in Lightning uses UTC/GMT
as its timezone. The time is correct, and in the calendar view/upcoming
events the time is properly displayed in the local time zone. It's just
when editing the event that the GMT time is used, which makes editing
events less convenient.

My guess is that when an event with the default timezone (which in the
database is stored with no value in the timezone column) is sent, no
timezone information is sent, and so Lightning selects UTC/GMT.

Is there anything that Horde could do, such as sending the actual
default timezone instead of nothing for events without an explicitly
selected timezone? I though about writing a feature request, but I
wanted to check first if my guess regarding the cause is correct
(perhaps the problem is with Lightning) and if the proposed solution
wouldn't violate the specification or something like that.


Thanks,

-- 
If you keep your mind sufficiently open, people will throw a lot of
rubbish into it.
		-- William Orton

Eduardo M KALINOWSKI
eduardo at kalinowski.com.br