<br><br><div class="gmail_quote">On Tue, Nov 6, 2012 at 10:44 AM, Michael Watson <span dir="ltr"><<a href="mailto:michael@thewatsonfamily.id.au" target="_blank">michael@thewatsonfamily.id.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 6/11/2012 5:55 AM, Gary Buhrmaster wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Nov 5, 2012 at 10:16 AM, Brian J. Murrell <<a href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>> wrote:<br>
....<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If every custom record rule needs every time specification in them<br>
converted to/from UTC, that should be done internally, IMHO.<br>
</blockquote>
There is no way to know the true intent behind custom rules.<br>
And while **some** custom rules might have been able to be<br>
automagically converted, no one contributed that code (or<br>
the dialog that would have been required for upgrade such<br>
as "Conversion of rule x is now <whatever>, is that correct?"),<br>
and now that pony has left the building...<br>
<br>
Custom rules give great power. They also come with great<br>
responsibility. And that includes TZ issues.<br>
<br>
<br>
</blockquote></div>
People generally think of time, as it is in there current time zone. Given that most Myth Installations are not portable, there is no reason a User should be confronted by UTC Times at any time.</blockquote><div><br>Geeez see Mike Dean's response. Seems the devs just cannot win with the users! <br>
</div></div>