Tickets :: [#12428] ambiguous time zone in events created by Horde

6.0.0-beta1

7/13/25

Summary	ambiguous time zone in events created by Horde
Queue	Kronolith
Queue Version	4.1.1
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	marten (at) dmfs (dot) org
Created	07/04/2013 (4392 days ago)
Due
Updated	07/16/2013 (4380 days ago)
Assigned	07/04/2013 (4392 days ago)
Resolved	07/16/2013 (4380 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/16/2013 02:52:38 PM	Jan Schneider	State ⇒ Resolved

07/04/2013 02:57:48 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Assigned

07/04/2013 02:57:26 PM	Jan Schneider	Version ⇒ 4.1.1 Priority ⇒ 2. Medium Queue ⇒ Kronolith

07/04/2013 01:15:56 PM	marten (at) dmfs (dot) org	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ ambiguous time zone in events created by Horde Queue ⇒ Horde Groupware Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Events created in Horde have an ambiguous time zone. Horde creates date times like: DTSTART;TZID=Europe/Athens:20111117T200000Z DTEND;TZID=Europe/Athens:20111117T204501Z The "Z" at the end means "UTC". If a TZID is present you must not append the "Z". So is should read as DTSTART;TZID=Europe/Athens:20111117T200000 DTEND;TZID=Europe/Athens:20111117T204501 Please check out: http://tools.ietf.org/html/rfc5545#section-3.3.5 (FORM #3)