<br><br><div class="gmail_quote">On Tue, Dec 29, 2009 at 10:45 AM, Jan Ceuleers <span dir="ltr"><<a href="mailto:jan.ceuleers@computer.org">jan.ceuleers@computer.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
</div>I agree with you that it looks too "sensitive". In fact both time zones are the same, but different labels were used ("CET" and "Europe/Paris") to get to it. It would arguably be enough to check that the UTC offsets are the same.<br>
<br>
Having said that, it may be the case that two time zone labels that currently result in the same UTC offset may not always do so; think different transitions to/from daylight savings time. Does not apply in this instance, but may do so in the general case.<br>
<br></blockquote><div><br><br>There was a recent discussion where a Myth dev was saying that the time zone handling in Myth is VERY precise and handles cases that people would often not even consider an issue. For example, locations that no longer use DST, but did in the past. Those are separate timezones for various complex reasons. In sort, make sure things are set the same, even when it looks like it "should" end up the same. In this case, use Europe/Paris or CET on every system, don't mix them. <br>
</div></div>