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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14132
------------------------------------------------------------------------------
  Ticket             | 14132
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | vCalendar timezone definition ignored in case of
                     | starting far ago
  Queue              | Kronolith
  Version            | 4.2.9
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-11-12 16:56) wrote:

Can you be more specific as to what you are seeing that is incorrect?  
I created a unit test for this and it works as expected. That is, the  
vTimezone is correctly parsed, the DTSTART of the event in your  
example file is represented as 3am on 10/9 in America/New_York. This,  
converted to UTC yields a time of 7am since this date is within DST  
and has an offset of UTC - 4 hours.