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

* Your Email Address
* Spam protection	Enter the letters below: .___..__.. ..___. . _/ \| \|\| \|[__ \|\/\| ./__.\|__\\|/\\|[___\| \|
Comment	> 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) > instead of 7 am, as shown in the screenshot. > - please ckeck the attached file "Bildschirmfoto vom 2015-11-30 09_28_42.png" > > as soon as the timezone definition is changed to a more recent date, > everything is fine: > please check the difference between "good.ics" (attached here) and > former "bad.ics" > > $diff good.ics bad.ics > 8c8 > < DTSTART:20010101T020000 > --- >> DTSTART:16010101T020000 > 14c14 > < DTSTART:20010101T020000 > --- >> DTSTART:16010101T020000 > > the item in "good.ics" is shown here correctly at 9am german winter > time 07am UTC > > hence, I am still convinced, there must be a serious bug in SW or > environment. hopefully you can reproduce it now. > BR > >> 7AM is the correct time, if you are viewing it in UTC. >
Attachment
Watch this ticket