| 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 | 7/4/13 (4745 days ago) |
| Due | |
| Updated | 7/16/13 (4733 days ago) |
| Assigned | 7/4/13 (4745 days ago) |
| Resolved | 7/16/13 (4733 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Assigned
Priority ⇒ 2. Medium
Queue ⇒ Kronolith
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ ambiguous time zone in events created by Horde
Queue ⇒ Horde Groupware
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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)