[horde] possible solution for: All-day events with different timezone span days
Michael J Rubinsky
mrubinsk at horde.org
Wed Jul 17 13:34:52 UTC 2013
Quoting Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:
> Hi,
>
> when I create an all-day event with timezone UTC within the GUI, but
> my default timezone is "Europe/Berlin" aka MEST aka UTC+2, the event
> span two days, because the event starts at 02:00. That's true, too,
> when the event gets synchronized to Android via ActiveSync or
> Lightning via CalDAV.
>
> Do I create an all-day event with UTC in an ActiveSync Android
> device, the event is displayed as "all-day" event in the GUI as
> well, but do not span days.
>
> The "trick" maybe is, that the all-day event of Android does not
> have no timezone at all or, to phrase it differently, the GUI
> displays the all-day event with the default timezone. In fact, as
> soon as I select "all-day" on the Android device the timezone
> selection becomes inaccessable.
Correct. ActiveSync passes all time data for events (all-day or not)
as UTC (converted from the client's configured default timezone). Once
imported into Horde, it gets converted into the Horde default timezone.
--
mike
The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20130717/81cbdc2d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130717/81cbdc2d/attachment-0001.bin>
More information about the horde
mailing list