<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2022-03-16 11:44 AM, Fred Gleason
via tz wrote:<br>
</div>
<blockquote
cite="mid:5694DFB9-B410-45F6-88AB-6EB2C3D8A88F@paravelsystems.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
On Mar 16, 2022, at 11:16, Tim Parenti via tz <<a
moz-do-not-send="true" href="mailto:tz@iana.org" class="">tz@iana.org</a>>
wrote:
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="">Complicating matters somewhat is that,
because of the prevalence of tzdb, in a sense we're
"victims of our own success". That is, whatever we
end up picking will likely show up fairly
automatically in a lot of public-facing places, and so
even if it isn't what the public would've naturally
used in the immediate aftermath of a change, many will
be fairly quickly informed by what they start to see,
and may start adopting and spreading whatever
nomenclature we've picked.</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>With that in mind, I’m thinking that the best approach
might be (to take a page from the Hippocratic Oath) to “do no
harm”. Given that the overall thrust of the Bill is ‘permanent
DST’, perhaps we should reflect just that —i.e. the
“permanent” abbreviations would become EDT | CDT | MDT | PDT,
the 'tm_isdst' member of the 'tm' struct would always return a
positive value, etc. <br>
</div>
</div>
</blockquote>
This is what happened in America/New_York in 1942, except the
abbreviations were EWT and EPT, right?<br>
<br>
Rule US 1918 1919 - Oct lastSun 2:00 0 S<br>
Rule US 1942 only - Feb 9 2:00 1:00 W #
War<br>
Rule US 1945 only - Aug 14 23:00u 1:00 P
# Peace<br>
Rule US 1945 only - Sep 30 2:00 0 S<br>
<br>
-880218001 1942-02-09 01:59:59 EST isdst 0 gmtoff -18000 stdoff
-18000<br>
-880218000 1942-02-09 03:00:00 EWT isdst 1 gmtoff -14400 stdoff
-18000<br>
<br>
-769395601 1945-08-14 18:59:59 EWT isdst 1 gmtoff -14400 stdoff
-18000<br>
-769395600 1945-08-14 19:00:00 EPT isdst 1 gmtoff -14400 stdoff
-18000<br>
<br>
-765396001 1945-09-30 01:59:59 EPT isdst 1 gmtoff -14400 stdoff
-18000<br>
-765396000 1945-09-30 01:00:00 EST isdst 0 gmtoff -18000 stdoff
-18000<br>
<br>
-Brooks<br>
<blockquote
cite="mid:5694DFB9-B410-45F6-88AB-6EB2C3D8A88F@paravelsystems.com"
type="cite">
<div class="">
<div><br class="">
</div>
<div>Doing this would narrowly confine the scope of the changes
to DST transition handling itself; without the need to go
change the meanings of abbreviations as defined in the
relevant RFCs and other standards with the concomitant needed
changes in downstream applications.</div>
<div><br class="">
</div>
<div>Cheers!</div>
<div><br class="">
</div>
<div><br class="">
</div>
</div>
<div class="">
<div class=""><span class="">|---------------------------------------------------------------------|</span></div>
<div class=""><span class="">| Frederick F. Gleason, Jr. |
Chief Developer |</span></div>
<div class=""><span class="">| |
Paravel Systems |</span></div>
<div class=""><span class="">|---------------------------------------------------------------------|</span></div>
<div class=""><span class="">| A room without books is
like a body without a soul. |</span></div>
<div class=""><span class="">|
|</span></div>
<div class=""><span class="">|
-- Cicero |</span></div>
<div class=""><span class="">|---------------------------------------------------------------------|</span></div>
</div>
</blockquote>
<br>
</body>
</html>