[Tickets #14132] Re: vCalendar timezone definition ignored in case of starting far ago

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14132
------------------------------------------------------------------------------
  Ticket           | 14132
  Aktualisiert Von | v.henkel at wenzel-elektronik.de
  Zusammenfassung  | vCalendar timezone definition ignored in case of starting
                   | far ago
  Warteschlange    | Kronolith
  Version          | 4.2.9
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


v.henkel at wenzel-elektronik.de (2015-12-02 18:47) hat geschrieben:

why is good.ics and bad.ics that different in HORDE?
I  still think, that they should give the same results.

>> Hi Michael,
>> I apologize for contractional statements in my last response  and the
>> screen shot attached.
>> To be more precise now:
>> - the item in "bad.ics"  is entered here with 3 am (german winter time)
>
> No, it's not. According to the data in the bad.ics file, it's  
> entered at 3am "Eastern Standard Time" - and is even specified in  
> the ics file as UTC -5.
>