- tz - lists.iana.org

USNO steps gingerly into the daylight saving mess
by Paul Eggert July 10, 2019

July 10, 2019

Last month the US Naval Observatory's Astronomical Applications Department published a web page that displays daylight saving starting and ending dates for US rules since 1967. A web page lets you enter a year like 1967 and the response will tell you start and end dates for that year. There is also an API that returns the data in a JSON format. Only US federal rules are supported, and only years from 1967 through 9999. See: https://aa.usno.navy.mil/data/docs/daylight_time.php

1 0

zone America/Indiana/Tell_city 1967 - 1969
by Alois Treindl July 10, 2019

July 10, 2019

I am afraid I have to challenge the entry Zone America/Indiana/Tell_City -5:47:03 - LMT 1883 Nov 18 12:12:57 -6:00 US C%sT 1946 -6:00 Perry C%sT 1964 Apr 26 2:00 -5:00 - EST 1969 -5:00 US E%sT 1971 -5:00 - EST 2006 Apr 2 2:00 -6:00 US C%sT It conflicts with Shanks for 1967-169, and therefore I checked newspaper archives. The Indianapolis News, Friday 27 October 1967 states that Perry County returned to CST. It went again to EST on 27 April 1969, as documented by the Indianapolis star of Saturday 26 April. (second screenshot attached)

2 1

VTIMEZONEs and Outlook
by Ken Murchison July 10, 2019

July 10, 2019

All, Sorry for the off-topic post, but I'm fishing. I'm one of the maintainers of vzic, a utility to convert IANA tzdata into iCalendar VTIMEZONE components. In the process of tweaking the tool to handle recent tzdata changes and to generate more correct/compact VTIMEZONEs in "pure" mode, I managed to break the generation of Outlook-compatible VTIMEZONEs. Does anyone know what parts of the iCalendar/VTIMEZONE spec that Outlook doesn't properly handle and/or know what the requirements are to be compatible with Outlook? -- Ken Murchison Cyrus Development Team Fastmail US LLC

4 4

Blocked USNO sites was: Updated Public Domain leapseconds.list
by Chris Woodbury July 8, 2019

July 8, 2019

>On Mon Jul 8 11:16:42 UTC 2019,Tony Finch dot at dotat.at wrote: > >The main problem that I can see is 3 out of the 7 navy.mil DNS servers say >that usno.navy.mil does not exist, so it's a matter of luck whether you'll >be able to contact it or not. > >Tony. Great detective work, Tony! After a little "digging" of my own, I discovered it's even worse than that. There are no public facing "authoritative" DNS servers for Navy.MIL (or USNO.Navy.MIL as all of them are unreachable). The Navy.MIL DNS servers have *no authoritative data* for USNO; they all appear to be caching secondary servers. The give away is that the TTLs decrements between "dig" runs. (Possibly "slit horizon" DNS servers that internally referencing their other half. There's no way to tell from this side.) This also means that the primary server listed in the SOA is not the real primary. There must be hidden primary and secondary DNS server somewhere as the servers we can actually see have cached RR (resource records). Someone hasn't thought out all of the implications of what they're doing. When I was looking, only two of seven Navy.MIL DNS servers returning NXDOMAIN for USNO.Navy.MIL. These were ns1.csd.disa.mil, the purported Navy.MIL primary DNS server (with no authoritative SOA RR) and updciftr01.csd.disa.mil. I could not reach *any* of the USNO.Navy.MIL DNS servers, period (The Naval Oceanographic Portal. (NoP) is up as I was able to FTP to Tycho and MAIA. I'm going to have to add Psyche.USNO.Navy.MIL to my /etc/hosts it seems (when I can figure out its IP address)). I must agree that a guaranteed 28% failure rate for USNO.Navy.MIL DNS lookups is unacceptable. The USNO SOA points to hostmaster(a)usno.navy.mil and none of the hosts in that MX RR are reachable. Does anyone have the 'phone number of a responsible person at USNO proper? The Petty Officer who answered the 'phone at the main number was less than helpful... (I hesitate to call Jeff Prillaman about this issue.)

1 0

Blocked USNO sites was: Updated Public Domain leapseconds.list
by Chris Woodbury July 8, 2019

July 8, 2019

Brian et al, DoD sites are subject to frequent attack from the Internet. One of their defense strategies is to "go turtle"". Sometimes they're not there at all but, more often, they isolate just portion of their "space". (TRACERT ends in never-neverland.) I have discovered that, when this happens, the Navy.Mil and USNO.Navy.Mil DNS servers are often not reachable. As a result, while USNO sites are actually available though the Naval Oceanographic Portal (NoP) (point of presence (PoP) in Portsmouth, VA), their DNS entries are not. I, personally, solved part of this problem by adding the USNO sites I use to /etc/host (or its Windows equivalent, %WINDIR%\System32\drivers\etc\hosts). These are: 199.211.133.23 maia.usno.navy.mil 199.211.133.93 aa.usno.navy.mil 199.211.133.239 tycho.usno.navy.mil # Charon is a USNO.Navy.Mil DNS server on the NOP 199.211.133.5 charon.usno.navy.mil charon.nofs.navy.mil 192.68.148.66 charon.nofs.navy.mil 192.68.148.80 toshi.nofs.navy.mil MAIA also has backup servers for their data at NASA Goldstone Space Flight Center (cddis.gsfc.nasa.gov) and, as Brian mentioned, toshi.nofs.navy.mil. (At this instant, MAIA and Toshi are unavailable via HTTP but FTP is just fine (with /etc/host entries). If one is running a local DNS server, adding a pointer to USNO.Navy.Mil with a Charon.USNO.Navy.Mil NS RR might help the cause... Since I've done these things (particularly the /etc/hosts entries), I rarely have problems reaching USNO sites. Also, sometimes, DoD restrict themselves to Secure DNS. As I've got (some of) the certificate information installed, I may not have problems where others might. Lastly, occasionally I can't reach MAIA via HTTP but FTP works just fine. (I've just change my references to ser7.dat to FTP for that reason.) (Pardon my edits to the following. No words were removed...) > On Sat Jul 6 16:12:26 UTC 2019, Brian Inglis Brian.Inglis at SystematicSw.ab.ca wrote: >>On 2019-07-05 15:55, Chris Woodbury via tz wrote: >> # This NTP leap-second file was created with data obtained from >> # the United States Naval Observatory (USNO) MAIA FTP server. >> # >> # Find it at: <ftp://maia.usno.navy.mil/ser7/leapsec.dat> >> ... >> # See: http://maia.usno.navy.mil/ser7/ser7.txt > > Seems to be some DNS resolver and network blocking, possibly only > outside the US, to maia.usno.navy.mil ; interactive web browser access > and Naval Oceanography Portal to tycho.usno.navy.mil and aa.usno.navy.mil > mostly work, but web browser ftp access does not, and non web browser > resolution and access do not, e.g. host or wget; however everything resolves > and is accessible form the browser and command line from toshi.nofs.navy.mil. > Some other previous reports back this up, but there were no followups to say > whether issues were temporary and cleared up, or persisted and were permanent. > > It may be possible that lookups or accesses may be rate limited to deter > intrusions, or entries may have expired because they may be offline for July 4 > thru the weekend, or sites may be blocked due to lack of monitoring staff or > funding for non-defense services.

3 3

Re: [tz] DST in Detroit 1967
by Paul Eggert July 7, 2019

July 7, 2019

Alois Treindl wrote: > So whether it was DST or not, at the time given in the article light cannot have > started to fail That depends on what the article's author Bill Dow meant by "fail". In a burning city, light could "fail" well before astronomical sunset. > You say in your comment that you have seen "multiple reports that (Shanks DST > data) is incorrect." > > I am curious what those other reports might be. Sorry, I don't remember the details. As I vaguely recall, the situation in Michigan was chaotic. The state rebelled against the federal daylight-saving law, some counties rebelled against the state, cases went to the state supreme court which may have (temporarily?) suspended the state's suspension of DST, and I don't know of any reliable catalog of what actually happened that year in Detroit. Perhaps someone could spring the money and read all the stories in the Detroit Free Press and Detroit News archives related to daylight saving time that year. I expect there would be dozens of stories to wade through. Let's hope the competing newspapers in Detroit didn't follow the model of Nashville in the previous decade. That Nashville story is so entertaining that it should be promoted from our email archive to the northamerica comments. Proposed patch attached.

1 1

Blocked USNO sites was: Updated Public Domain leapseconds.list
by Chris Woodbury July 6, 2019

July 6, 2019

For reasons I can not fathom, I did not check on all the links in the leap-seconds.list I just submitted to the list. As a result, I failed to notice that the link to IERS Bulletin A was incorrect. The proper link is: # <ftp://maia.usno.navy.mil/ser7/ser7.dat> ^^^ Also available via HTTP. Note: the FTP and HTTP versions *have different timestamps* (and therefore are most likely separate files in different file structures). Otherwise, the files are identical. (This is why I've got alias cp='cp --preserve=timestamps' in my run commands....) Also, I managed to include a dot (.) at the end of a link in my first Bulletin C number 58 message. The proper URL for the directory in which to find the IERS leap-seconds.list file is: <ftp://hpiers.obspm.fr/iers/bul/bulc/ntp/> "leap-seconds.list" is a symbolic link. Its "real" name is "leap-seconds.3771235866" (4 Jul 2019 15:31:06 CEST) One may also use HTTP or HTTPS protocols to get there. Sorry about that.

1 0

Updated Public Domain leapseconds.list
by Chris Woodbury July 6, 2019

July 6, 2019

# -=*( This file is in the public domain )*=- # This NTP leap-second file was created with data obtained from # the United States Naval Observatory (USNO) MAIA FTP server. # # Find it at: <ftp://maia.usno.navy.mil/ser7/leapsec.dat> # Updated using information from IERS Bulletin C 58 (4 Jul 2019) # Found at <ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat> # # Bulletin C 58 did not announce a new leap-second. # The last leap-second occurred on 1 Jan 2017 (3692217600). # # -=<*>=- # # This file is not produced by a national metrology laboratory. # It *is* created using data from one: # # United States Naval Observatory (USNO) # IERS Rapid Service/Prediction Center for Earth Orientation # 3450 Massachusetts Ave NW, Washington, DC 20392 # # It should be noted that anyone with proper information can # generate an NTP leap-seconds.list file. # # This file's generation was originally necessitated by a U.S. # government shutdown and the resulting lack of an NIST or USNO # generated file until late in January 2019. # # -=<*>=- # # The Network Time Protocol (NTP) keeps time in Coordinated # Universal Time (UTC). UTC is a time scale based upon # Standard International (SI) seconds and derived from Temps # Atomique International (TAI). UTC is the basis for legal # time since 1 Jan 1972 0h. # # [Le] Bureau International des Poids et Mesures (BIPM) tracks # TAI, UT1, TE and UTC uses a weighted ensemble of 420+ atomic # clocks at over 80+ national metrology laboratories worldwide # to track time and Very-Long-Baseline Interferometry (VLBI) # for precision millisecond pulsars timing and to track Earth's # orientation in space. The origin of TAI has been agreed # officially to coincide with UT1 on 1 January 1958 0h. # # For further information, read BIPM monograph "Time Scales" # found at: # # <https://www.bipm.org/... # utils/common/pdf/monographies-misc/Monographie1994-1.pdf> # # And "Coordinated Universal Time" at: # # <https://www.bipm.org/cc/CCTF/Allowed/18/CCTF_09-32_noteUTC.pdf> # # And, lastly: # # "Atomic Time Scales for Dynamical Astronomy" pp.51-56 # # "How Can Millisecond Pulsars Improve the Long-Term Stability # of Atomic Time Scales?", pp.57-60: # # Proceedings of the 6th European Frequency and Time Forum # (17-19 March 1992) # # <http://www.eftf.org/proceedings/proceedingsEFTF1992.pdf> # # -=<*>=- # # Leap seconds are an official correction to UTC to keep it # within 0.9 seconds of UT1; yet another time standard # based upon the orientation of the earth in space (and the # basis of legal time until 1972). IERS Bulletin A keeps # track of and predicts the value of UT1-UTC. # # See: http://maia.usno.navy.mil/ser7/ser7.txt # # The data kept in "leap-seconds.list" are used by the # Network Time Protocol daemon (NTPd) to determine when to # apply leap seconds to Coordinated Universal Time (UTC). # "leap-seconds.list" is a symbolic link to the actual # file name, leap-seconds.xxxxxxxxxx, where xxxxxxxxxx # is derived from the NTP update timestamp (below). # # Theoretically, a leap second may be positive or negative. # Realistically, negative leap seconds are unlikely to occur. # # All timestamps in this leap seconds file are encoded using the # NTP epoch. These timestamps represent the number of seconds # since 1 Jan 1900 0:00:00. This is Modified Julian Date (MJD) # 15020 and Julian Date 2415020.5. There will be an unsigned # 32-bit overflow to the second NTP era in 2036 (07 Feb 2036 # 06:28:16 UTC to be precise). # # A leap second datum consists of an NTP timestamp and the # number of seconds difference between TAI and UTC (e.g. # currently TAI-UTC is 37). UTC was established (at # midnight) on 1 Jan 1972 0h with TAI-UTC started at 10. # There was no mechanism prior to that time defining when # to apply leap seconds. # # Note: the first datum in the leap-seconds.list file is # *not* a leap-second; it denotes the definition of the # UTC timescale. # # Leap-seconds rules are establish in: # # International Telecommunications Union-Recommendation (ITU-R) # 460-6 (Standard-frequency and Time-Signal Emissions), # Annex 1 (Time scales), Section 2 (Leap-Seconds). # # Note: Version 460-6 of the Recommendation is incorporated # by reference in the [ITU] Radio Regulations. # # <http://www.itu.int/rec/R-REC-TF.460-6-200202-I/> # # Section 2.3: Delegates leap-second timing/dissemination to the # International Earth Rotation and Reference System Service (IERS), # (in its role as inheritor of Bureau International de l'Heure (BIH)). # # NTP Leap second files have an update time (#$). This is often # the UTC zero (0) hour time of the day when the leap second file # is built. [I am of the opinion] it should be updated whenever # a new IERS Bulletin C is issued. CCW] # #$ 3771187200 # # Leap second data have a lifetime. Traditionally, this ends on # the twenty-eighth (28) day of the month six months after the # period of time described in the latest IERS Bulletin C. This # is the expiry time (#@). # # File expires on: 28 Jun 2020 # #@ 3802291200 # # Leap second files have a hash, as define in NIST's FIPS 180 # Secure Hash Standard (SHS), current revision 4 (FIPS 180-4). # # FIPS Publications: <http://csrc.nist.gov/publications/fips/> # Direct Link: <http://dx.doi.org/10.6028/NIST.FIPS.180-4> # # It is based on an SHA[1] digest, created using the data # portions of the file including leap second data and the update # and expiry timestamps. All "white space" and comments are # ignored in the computation thereof. The 160-bit SHA[1] # digest polynomial are encoded in five hexadecimal grouping at # the end of the file (#h). The hash itself is NOT included in # the SHA[1]. It can also be calculated using GNU sha1sum which # generates the same 160-bit digest, given the same data, in # forty hexadecimal characters. # # Additionally, there may be an "#SHA256" digest record. If # present, it is a FIPS-180 SHA256 digest that includes the # same records as "#h" plus the comment Day, Month and Year # included in each NTP leap-second record (thus making it # possible to *verify* those comments as well as the file time- # stamps, and NTP leap-second data. # # NTP delta #timestamp T Date of Change # 2272060800 10 # 1 Jan 1972 (MJD 41317) 2287785600 11 # 1 Jul 1972 (MJD 41499) 2303683200 12 # 1 Jan 1973 (MJD 41683) 2335219200 13 # 1 Jan 1974 (MJD 42048) 2366755200 14 # 1 Jan 1975 (MJD 42413) 2398291200 15 # 1 Jan 1976 (MJD 42778) 2429913600 16 # 1 Jan 1977 (MJD 43144) 2461449600 17 # 1 Jan 1978 (MJD 43509) 2492985600 18 # 1 Jan 1979 (MJD 43874) 2524521600 19 # 1 Jan 1980 (MJD 44239) 2571782400 20 # 1 Jul 1981 (MJD 44786) 2603318400 21 # 1 Jul 1982 (MJD 45151) 2634854400 22 # 1 Jul 1983 (MJD 45516) 2698012800 23 # 1 Jul 1985 (MJD 46247) 2776982400 24 # 1 Jan 1988 (MJD 47161) 2840140800 25 # 1 Jan 1990 (MJD 47892) 2871676800 26 # 1 Jan 1991 (MJD 48257) 2918937600 27 # 1 Jul 1992 (MJD 48804) 2950473600 28 # 1 Jul 1993 (MJD 49169) 2982009600 29 # 1 Jul 1994 (MJD 49534) 3029443200 30 # 1 Jan 1996 (MJD 50083) 3076704000 31 # 1 Jul 1997 (MJD 50630) 3124137600 32 # 1 Jan 1999 (MJD 51179) 3345062400 33 # 1 Jan 2006 (MJD 53736) 3439756800 34 # 1 Jan 2009 (MJD 54832) 3550089600 35 # 1 Jul 2012 (MJD 56109) 3644697600 36 # 1 Jul 2015 (MJD 57204) 3692217600 37 # 1 Jan 2017 (MJD 57754) # #SHA256: 128f9463dc3828a1c7a611a4017bc311aabdfbe4c33fd8278a63bed7ef3ba0e2 #h bca6f457 5f358e20 a63e0aab a79ad3c3 c0a21083

3 3

Bulletin C number 58
by Chris Woodbury July 6, 2019

July 6, 2019

Christian Bizouard has struck again (and exactly a week earlier than I was expecting). No new leap-second. I predict (after a careful perusal of Bulletin A) that we will see one in July 2020. i.e.: 3802550400 38 # 1 Jul 2020 There is a new, IERS leap-seconds.3771235866 file at https://hpiers.obspm.fr/iers/bul/bulc/ntp. Dr. Levine and Jeff Prillaman will no doubt shortly generate NIST and USNO versions respectively. (Today is a federal holiday in the US.) For those who can't wait, I have attached another leap-seconds.list file, Eggert_leap-seconds.3771187200, which has a FIPS style SHA-256 digest that includes the erstwhile day, month and year from the comments. Happy (U.S.) Independence Day !!

2 1

Bug Moncton 1973? Where can I find old tzdata releases?
by Alois Treindl July 5, 2019

July 5, 2019

https://data.iana.org/time-zones/ seems to contain only tzdata releases from 2016 upwards. I need to look into pre-2005 ones. Where can I find them? The reason is that I am checking New Brunswick, Canada DST in 1973. The zone America/Moncton was introduced in 2007, to be able to represent an unusual clock time of 0:01 for DST onset. America/Moncton does not list DST for 1973. That is the only year between 1945 and 2020 that NB would not have DST. Nearby zones like Halifax or ST_Johns have 1973 DST, just like the rest of Canada? Is there a bug in America/Moncton ? Shanks has DST in 1973 for New Brunswick.

5 4

Re: [tz] tz Digest, Vol 94, Issue 6
by Andrii Nabok July 5, 2019

July 5, 2019

Dear Paul Eggert, I would like to draw your attention to the fact that the Kyiv time zone is officially defined in the Crimea. In this regard, I have the following statements: 1. This is not a political issue; 2. All projects on the Internet, regardless of their scope, must comply with international law. 3. The territory of Crimea is not a disputed territory. Crimea is an integral part of Ukraine. All countries in the world, except Russia (which started the war in Ukraine), consider Crimea to be part of Ukraine. 4. Also pay attention to the provisions of the BCP 175. *"Changes to existing entries SHALL reflect the consensus on the ground in the region covered by that entry.". *Fake news on Russian sites - is not a consensus. Why is the Tzadat base contributing to Russian invaders and terrorists in conducting an information war against a civilized world? Also, we ask to answer the following questions: 1. On which basis were changes made in 2014? Based on the news on the site in the domain zone. Ru ??? 2. Will you change the time zone in Alaska, if after some time, Russian troops enter Alaska, take prisoner of official representatives of the US government and subsequently publish on all Russian sites the news that the Magadan time zone is set in Alaska??? Sincerely, Andrii Nabok чт, 4 лип. 2019 о 10:36 <tz-request(a)iana.org> пише: > Send tz mailing list submissions to > tz(a)iana.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mm.icann.org/mailman/listinfo/tz > or, via email, send a message with subject or body 'help' to > tz-request(a)iana.org > > You can reach the person managing the list at > tz-owner(a)iana.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tz digest..." > > > Today's Topics: > > 1. Re: Simferopol switch near 2014-03-30 (Paul.Koning(a)dell.com) > 2. Re: Simferopol switch near 2014-03-30 (Tim Parenti) > 3. Re: Simferopol switch near 2014-03-30 (Michael H Deckers) > 4. Re: Simferopol switch near 2014-03-30 (Paul Eggert) > 5. [PROPOSED] Cite Rec. ITU-R TF.460-6 for leap seconds (Paul Eggert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 3 Jul 2019 13:27:29 +0000 > From: <Paul.Koning(a)dell.com> > To: <tz(a)iana.org> > Subject: Re: [tz] Simferopol switch near 2014-03-30 > Message-ID: <43E8DF99-A7A4-4879-9555-5E5DEC7CEC31(a)dell.com> > Content-Type: text/plain; charset="us-ascii" > > > > > On Jul 3, 2019, at 6:44 AM, Sergij Marchenko <makars(a)gmail.com> wrote: > > > > You can continue to live according to the rules imposed by russian > terrorists under the occupation regime of Putin Huylo. > > It's been explained many times already that the TZ project is a technical > one, not a political one, and the issue you raise is out of scope. > > Since you persist in bringing it up in spite of being corrected > repeatedly, it may be time to consider your mail to be spam and filter it > accordingly. > > paul > > > ------------------------------ > > Message: 2 > Date: Wed, 3 Jul 2019 09:33:36 -0400 > From: Tim Parenti <tim(a)timtimeonline.com> > To: Michael H Deckers <michael.h.deckers(a)googlemail.com> > Cc: Time Zone Mailing List <tz(a)iana.org> > Subject: Re: [tz] Simferopol switch near 2014-03-30 > Message-ID: > < > CAFpi07wuB0+X230MukZJGmVwFS2f8PBo5Fcua8CMaB-y+s4PJw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Wed, 3 Jul 2019 at 04:43, Michael H Deckers via tz <tz(a)iana.org> wrote: > > > tzdb currently has the switch in Simferopol from > > 2014-03-30T02:00 to 04:00, following the announcement in > > [https://vz.ru/news/2014/3/17/677464.html] from 2014-03-17. > > > > But the clocks of the main station shown in the video at > > [https://www.rt.com/news/crimea-clocks-moscow-time-173/] > > advance from 22:00 to 00:00. If this is not a fake, the > > switch happened 4 hours earlier. > > > This apparent discrepancy in reporting was discussed contemporaneously > on-list and is already noted in commentary. > https://mm.icann.org/pipermail/tz/2014-March/020814.html > https://mm.icann.org/pipermail/tz/2014-March/020815.html > > Specifically: > > # Simferopol and Sevastopol reportedly changed their central town clocks > > # late the previous day, but this appears to have been ceremonial > > # and the discrepancies are small enough to not worry about. > > > As it so happens, the RT article you linked confirms that particular > perspective ? that the 22:00 transition was merely "ceremonial" and that > the 02:00 transition was official ? more clearly than we had identified at > the time. Quoting the article: > > ?the hands of the main railway station clock in the city of Simferopol > > jumped from 10 pm to 12 am on Saturday. [?] The ceremony follows the > > region?s formal joining the Russian Federation on March 21. Other > Crimeans, > > apart from Simferopol, the region?s capital, were expected to switch > their > > clocks at 2:00 am on Sunday, AFP reported. > > > It appears India's *Business Standard* also contemporaneously reported the > same, at > > https://www.business-standard.com/article/pti-stories/crimea-to-set-clocks-… > : > > ?a symbolic ceremony will be held to move the clocks forward at the railway > > station in the main city of Simferopol. The Black Sea peninsula's prime > > minister Sergei Aksyonov will oversee the switch at 10pm (midnight > Moscow, > > 2000 GMT). Europeans and ordinary Crimeans make the daylight savings > time > > switch at 2am tomorrow. > > > Since the zone is meant to represent the region as a whole, and not > necessarily one or two clocks in the town squares in the representative > city, this is why we settled on 2014-03-30 02:00 for the transition. > > -- > Tim Parenti >

2 3

[PROPOSED] Cite Rec. ITU-R TF.460-6 for leap seconds
by Paul Eggert July 4, 2019

July 4, 2019

(Inspired by patch proposed by Chris Woodbury.) * leapseconds.awk (BEGIN): * tz-link.html (Precision timekeeping): Add ITU-R citation. * leapseconds.awk (BEGIN): Drop mention of rolling leap seconds, as the ITU-R doesn’t mention them and this script doesn’t generate them. --- leapseconds.awk | 16 +++++++++------- tz-link.html | 4 ++++ 2 files changed, 13 insertions(+), 7 deletions(-) mode change 100644 => 100755 leapseconds.awk diff --git a/leapseconds.awk b/leapseconds.awk old mode 100644 new mode 100755 index 242e9d6..241da92 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -16,6 +16,11 @@ BEGIN { print "# The NTP Timescale and Leap Seconds" print "# <https://www.eecis.udel.edu/~mills/leap.html>." print "" + print "# The rules for leap seconds are specified in Annex 1 (Time scales) of:" + print "# Standard-frequency and time-signal emissions." + print "# International Telecommunication Union - Radiocommunication Sector" + print "# (ITU-R) Recommendation TF.460-6 (02/2002)" + print "# <https://www.itu.int/rec/R-REC-TF.460-6-200202-I/>." print "# The International Earth Rotation and Reference Systems Service" print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1" print "# (which measures the true angular orientation of the earth in space)" @@ -29,15 +34,12 @@ BEGIN { print "# accounting for the discrepancy between atomic time and the earth's rotation" print "# did not exist. The first (\"1 Jan 1972\") data line in leap-seconds.list" print "# does not denote a leap second; it denotes the start of the current definition" - print"# of UTC." + print "# of UTC." print "" print "# The correction (+ or -) is made at the given time, so lines" - print "# will typically look like:" - print "# Leap YEAR MON DAY 23:59:60 + R/S" - print "# or" - print "# Leap YEAR MON DAY 23:59:59 - R/S" - print "" - print "# If the leap second is Rolling (R) the given time is local time (unused here)." + print "# typically look like this:" + print "# Leap YEAR MON DAY 23:59:60 + S" + print "# A negative leap second's columns 5 and 6 would be '23:59:59' and '-'." monthabbr[ 1] = "Jan" monthabbr[ 2] = "Feb" diff --git a/tz-link.html b/tz-link.html index 85fc001..234c04e 100644 --- a/tz-link.html +++ b/tz-link.html @@ -929,6 +929,10 @@ scales used by each landed mission on Mars.</li> dedicated not only to leap seconds but to precise time and frequency in general. It covers the state of the art in amateur timekeeping, and how the art has progressed over the past few decades.</li> +<li>The rules for leap seconds are specified in Annex 1 (Time scales) of <a +href="https://www.itu.int/rec/R-REC-TF.460-6-200202-I/">Standard-frequency +and time-signal emissions</a>, International Telecommunication Union – +Radiocommunication Sector (ITU-R) Recommendation TF.460-6 (02/2002).</li> <li><a href="https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html"><abbr title="International Earth Rotation and Reference Systems Service">IERS</abbr> -- 2.17.1

3 7

Clarification on future direction of POSIXRULES and POSIX TZ specs?
by Tom Lane July 4, 2019

July 4, 2019

The 2019b announcement says that zic's -p feature is being deprecated with an eye to eventual removal. I am wondering what is the game plan there exactly, and in particular what is planned to happen in localtime.c. Will the code that tries to load the TZDEFRULES zone be removed? If so, will the behavior for transition-rule-less POSIX TZ specs be that it always falls back to the hard-wired TZDEFRULESTRING? Or are you planning to go further, say by rejecting such TZ specs entirely? (As far as I can see, doing that would be contrary to the POSIX spec --- although they don't say what the default rule should be, it's pretty clear syntactically that you can omit it.) Also, what sort of time scale might this happen on? regards, tom lane

2 1

Backzone entry for Europe/Vaduz
by Alois Treindl July 4, 2019

July 4, 2019

In the year 2013 I had contributed information that Swiss neighbor country Liechtenstein, represented by Europe/Vaduz in file backzone, did not have daylight saving time in 1941 and 1942, while Switzerland, represented by Europe/Zurich, did have it. A colleague sent me a follow-up question today, which cause me to reconsider the question. I was able to access the online archive of the Vaduz paper Vaterland for free - they offer a special summer deal. I could confirm frm the paper that Liechtenstein did in fact follow the same DST in 1941 and 1942 as Switzerland did. The entry Europe/Vaduz in the file backzone can be removed, so that the link Europe/Zurich Europe/Vaduz remains effective even for those who, like me, compile TZ with backzone included. I attach a few newspaper clippings, not translated.

3 4

Golan Heights and Quneitra
by Alois Treindl July 4, 2019

July 4, 2019

The Golan Heights are not represented by a zone in TZ. Since 1967 under control of Israel, they fall under Asia/Jerusalem, as all differences fall under the 1970 TZ cut-off. Having a zone in backzone would be good, though. There is however one town in the Golan Heights, Quneitra, which was returned from Isreal to Syria in 1974. There have been timezone differences in the years 1967 - 1974 between Israel and Syria. Therefore, Asia/Quneitra would merit its own zone, in my opinion. https://en.wikipedia.org/wiki/Quneitra list a population of 153 for the (destroyed) town itself and 4318 for is 'metropolitan' area.

2 1

Simferopol switch near 2014-03-30
by Michael H Deckers July 3, 2019

July 3, 2019

tzdb currently has the switch in Simferopol from 2014-03-30T02:00 to 04:00, following the announcement in [https://vz.ru/news/2014/3/17/677464.html] from 2014-03-17. But the clocks of the main station shown in the video at [https://www.rt.com/news/crimea-clocks-moscow-time-173/] advance from 22:00 to 00:00. If this is not a fake, the switch happened 4 hours earlier. Michael Deckers.

5 7

From Consulate General of Ukraine in San Francisco
by Consulate General of Ukraine in San Francisco July 2, 2019

July 2, 2019

З повагою/Best regards, Генеральне консульство України в Сан-Франциско/Consulate General of Ukraine in San Francisco 530 Bush Street, Suite 402, San Francisco, CA 94108 Tel: + 1 (415) 398 0240, Fax: +1 (415) 398 5039 http://san-francisco.mfa.gov.ua<http://san-francisco.mfa.gov.ua/> gc_uss(a)mfa.gov.ua<mailto:gc_uss@mfa.gov.ua>

2 1

[tz-announce] 2019b release of tz code and data available
by Paul Eggert July 2, 2019

July 2, 2019

The 2019b release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Brazil no longer observes DST. 'zic -b slim' outputs smaller TZif files; please try it out. Palestine's 2019 spring-forward transition was on 03-29, not 03-30. Changes to future timestamps Brazil has canceled DST and will stay on standard time indefinitely. (Thanks to Steffen Thorsen, Marcus Diniz, and Daniel Soares de Oliveira.) Predictions for Morocco now go through 2087 instead of 2037, to work around a problem on newlib when using TZif files output by zic 2019a or earlier. (Problem reported by David Gauchard.) Changes to past and future timestamps Palestine's 2019 spring transition was 03-29 at 00:00, not 03-30 at 01:00. (Thanks to Sharef Mustafa and Even Scharning.) Guess future transitions to be March's last Friday at 00:00. Changes to past timestamps Hong Kong's 1941-06-15 spring-forward transition was at 03:00, not 03:30. Its 1945 transition from JST to HKT was on 11-18 at 02:00, not 09-15 at 00:00. In 1946 its spring-forward transition was on 04-21 at 00:00, not the previous day at 03:30. From 1946 through 1952 its fall-back transitions occurred at 04:30, not at 03:30. In 1947 its fall-back transition was on 11-30, not 12-30. (Thanks to P Chan.) Changes to past time zone abbreviations Italy's 1866 transition to Rome Mean Time was on December 12, not September 22. This affects only the time zone abbreviation for Europe/Rome between those dates. (Thanks to Stephen Trainor and Luigi Rosa.) Changes affecting metadata only Add info about the Crimea situation in zone1970.tab and zone.tab. (Problem reported by Serhii Demediuk.) Changes to code zic's new -b option supports a way to control data bloat and to test for year-2038 bugs in software that reads TZif files. 'zic -b fat' and 'zic -b slim' generate larger and smaller output; for example, changing from fat to slim shrinks the Europe/London file from 3648 to 1599 bytes, saving about 56%. Fat and slim files represent the same set of timestamps and use the same TZif format as documented in tzfile(5) and in Internet RFC 8536. Fat format attempts to work around bugs or incompatibilities in older software, notably software that mishandles 64-bit TZif data or uses obsolete TZ strings like "EET-2EEST" that lack DST rules. Slim format is more efficient and does not work around 64-bit bugs or obsolete TZ strings. Currently zic defaults to fat format unless you compile with -DZIC_BLOAT_DEFAULT=\"slim\"; this out-of-the-box default is intended to change in future releases as the buggy software often mishandles timestamps anyway. zic no longer treats a set of rules ending in 2037 specially. Previously, zic assumed that such a ruleset meant that future timestamps could not be predicted, and therefore omitted a POSIX-like TZ string in the TZif output. The old behavior is no longer needed for current tzdata, and caused problems with newlib when used with older tzdata (reported by David Gauchard). zic no longer generates some artifact transitions. For example, Europe/London no longer has a no-op transition in January 1996. Changes to build procedure tzdata.zi now assumes zic 2017c or later. This shrinks tzdata.zi by a percent or so. Changes to documentation and commentary The Makefile now documents the POSIXRULES macro as being obsolete, and similarly, zic's -p POSIXRULES option is now documented as being obsolete. Although the POSIXRULES feature still exists and works as before, in practice it is rarely used for its intended purpose, and it does not work either in the default reference implementation (for timestamps after 2037) or in common implementations such as GNU/Linux (for contemporary timestamps). Since POSIXRULES was designed primarily as a temporary transition facility for System V platforms that died off decades ago, it is being decommissioned rather than institutionalized. New info on Bonin Islands and Marcus (thanks to Wakaba and Phake Nick). Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2019b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2019b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2019b.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 23a01523a5d6a6ae2217df77b2a3f60e10a373d2 dated 2019-07-01 00:09:53 -0700 and tagged '2019b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: bcfb417fe3b7c39e702da0090291db0489744f733010ae183007fce5e441bfce885fb25ed11730cf7f363572e107d7ff0c4b38691bb99def2d8cf7017c05720f tzcode2019b.tar.gz c0104078d994e501d80a41bea31364b1390a75c2fbf42968a8343a090e2ac2eddbc58770ca470b192ea19dec89fcc634141a1de703ea2ffa0325176a64afe1fc tzdata2019b.tar.gz 98030b41258d21b6040fe95ecee4edd6bb9fa3775d89bebf69f460abad009eb47f053197ac755dc2d631b40fe31d4d3650493f139069b14ab3771e529cebcaea tzdb-2019b.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9AACgkQ7ZfpDmKq fjQziw//UmsHJNgU9cwbxWUBNqqu6VqrllAgLEXXLbK0EhZGwQpYsrhW9h5LZrvS OVHUt7EorLaFB4rSkTr2DP6pSqAn7+i7pXVdETxHNmTcF85rbyLwt5Z4OrbMAaN2 f44BxVSOSO4C/A+wWN7JAhAC57fwj++bCvIZ82qlauV1BsBq0AiuURat5OP2ZA16 Wpz3749wy1N4xEtYaMRzBozWQ6mnyYxaCRZUTv2BhuVK8UbUrHZ8I8KkcqAYnOqL E0fTWSKQVRxciApFNWHEreIeeVonOom0DWWEL3dIQcx09IM0YtocpAXgWoyHzOic mU7ibcx0KrpzDW+6nf/owxe/dkUa+CbHgPDs9b5vTJUwJkSk8wrpr3tAPSjBeo9K WN+BvhxeZKihPU9DziWTs8jAzyVtnqGNesBhVi1zecY723Gk/oizdDQNxh9vLbYU VUP3kcc2IqEciJVeI6bDz2wSJVcCif3bFFosuF2fOpTzmpLx+WceYVw+y0NFMcTN euZ/D1AQK7opCshjoBKqbOMB6TvbjjCiEjQ/pkXKLwhYBWCtIPMblgo+33MrI4Eb r/3S+l4o6yDbxslZjn0kNoG6krrbb6F1IrjIfnd4t2PDoeYS2vE7rCi+qhrJNLEI 24ZxbaZgnt4JvAec+5cy9ZnTOzZs7IhDSiMbm40IB0v2zVFT+rQ= =6vQV -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9AACgkQ7ZfpDmKq fjT55Q/9G4BmEDL48wU0slZCAFNMqbvNfizL2MTNHC6Yv60gwdQCl7CgQk+zE+1W b4ir1Vm23eWWVdCjGGwjt4WWy+SlvnEKqjiZxTRFpkB5to8Zi5KNklGlUX0U9iUu vMCVKeIQMFLUr6sAqAk4lgJ2OUF1MNaj2kVwINxS+C8rCyr6wjn6FWWaxvbCO3+D 2Z8sZgCRBWxmckqX+4Nmv2YeCGuL1ZjVTz0flkWi/OduR+PjBe/9PN506PjeEht8 cqOjtRz/V4SEKfbv6rn8jqxDrl6xkrBxfiaF64smWgwSFcQ9yRrxCt2L35tARdal DAP/vb1PemUb0fJawYP/ZhiArk0fCRRZ+wleTZKsk65I4VsrffQ3rYe5ZtMYnUhO +UP+B7OkxNa0gARf+uFwYvrqZefg0HRq/INFqd3TCkza0wa7Rb3mQL9orCzUH7St XLrdhRJYWGcuepGBiTdO4+yPqXkK7k89W3ACo+HiVuRbMRo3Xf+38918kubns41l /itR/C/lSN+/ErokSh6VshelvOuMVcgoghTD7fDAtNaH9IgldEIF/Wf3m1Um+V9R sN646EvAazgkxw3hD1sEDxHxN7TIsxFvTaimVg+uwrX2b8Ok+tffomlalSXoOS8F zK/EyKROm8v2dSJUD0Hf+FvDqJm/Pre0ydKqsdahJYBxIStNnX8= =P/tF -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl0Zs9IACgkQ7ZfpDmKq fjRlfQ//ev3hI5NxrAoJX8fpb9LAdReo7ZpADinVnNn47AyS0WYUtf6Afaav+lT+ FL+OU39VTJAeQ0zwVrH9JZr3Oy8mIl9mhAEPUsX4NxLw8P7QTdCHO84NmkrzpoM9 l9GEOkBoNTIE5YaM9IezKhMKJv/CyPXkRnx3UBAblgTaBkV0gqkoePPn4sVa0Arh 3Vn6H6AV6oQpC8WtH8yCxBuLXkddiVHFi3zbuM+3MHgFTb+8f/UwTopGUjsZOPoN z00rwFO+jVjdrm2700i1j1bTYGInIe3pIctwfutQfglIQSFK3nQADFYdlhfBLBJM H0NDCYF1z/LKtAWSycWpRhpqU2+25mX6Fldrfp1YhrSiJCrUQYOgQNXRSa32nY1T 5gc71UAe9rQNDRo5deSmOunKXWY5s6tZdxn7Q22FBFWwfrGmCqhR6mrB2dgEBvl8 isjoGxZO1iJYhlTvq7WyxOdnbjR4BLBF0eE8KB2S2F6srb/luPfCG6F9Ier5fYl7 N/NvH5FSeJHC1r2EWw+yy5bjaG5GkX6NP1+FBfw7prKtUNx48x8tpdy11FlULkCN J+zid9ySJBsnMRNL5p/egYbYGaptLGO8yAuKN3s3znaG/f9kh39u+xI1Fo9KFVBd +NvQYaMNYMgTi4qyCaMeCGxUUlJLN/WnjclJyl/ca84sUhpLXRI= =3v1i -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets or times past 24:00, this release's data entries can be turned into a rearguard-format tarball that does not use these features. This is intended to be a temporary transition aid for these parsers. To generate a rearguard-format tarball, obtain the full distribution as described above, and run the command 'make rearguard_tarballs' on a development host. Or you can run 'make rearguard.zi' to generate a single file that can be fed directly to a parser that works like 'zic'.

1 0

[PATCH] Allow the gpg2 binary name to be overridden by the environment.
by Matthew Donadio July 1, 2019

July 1, 2019

On some platforms, the gpg2 binary isn't actually called 'gpg2'; on OSX when you install GPG view Homebrew, it is just 'gpg'. This probably affects about three people on the planet, but noticed it when working on build scripts. --Matthew Donadio (matt(a)mxd120.com)

2 1

[PATCH] Revert Hong Kong 1952 fall-back transition date to Nov 2 (inadvertently changed during recent Hong Kong fixes)
by Brad Arndt June 29, 2019

June 29, 2019

* asia: Revert Hong Kong 1952 fall-back transition from October 26 to November 2nd --- asia | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/asia b/asia index c9b362d..2182455 100644 --- a/asia +++ b/asia @@ -741,7 +741,8 @@ Rule HK 1946 only - Dec 1 3:30s 0 - Rule HK 1947 only - Apr 13 3:30s 1:00 S Rule HK 1947 only - Nov 30 3:30s 0 - Rule HK 1948 only - May 2 3:30s 1:00 S -Rule HK 1948 1952 - Oct Sun>=25 3:30s 0 - +Rule HK 1948 1951 - Oct Sun>=25 3:30s 0 - +Rule HK 1952 only - Nov 2 3:30s 0 - Rule HK 1949 1953 - Apr Sun>=1 3:30 1:00 S Rule HK 1953 1964 - Oct Sun>=31 3:30 0 - Rule HK 1954 1964 - Mar Sun>=18 3:30 1:00 S -- 2.17.0.windows.1

3 2

compiling backzone file with zic - How to?
by Alois Treindl June 28, 2019

June 28, 2019

I am trying to compile the zonefiles with zic, and I want to include the backzone file. I expect that zoneinfo/Africa/Mbabane comes out differently from zoneinfo/Africa/Johannesburg because in backzone there is # Eswatini (formerly Swaziland) Zone Africa/Mbabane 2:04:24 - LMT 1903 Mar 2:00 - SAST (Swaziland did not observe South African DST in 1942-1944 and I want to see that respected in the binary zonefile Africa/Mbabane) while in file africa there is: # South Africa # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule SA 1942 1943 - Sep Sun>=15 2:00 1:00 - Rule SA 1943 1944 - Mar Sun>=15 2:00 0 - Zone Africa/Johannesburg 1:52:00 - LMT 1892 Feb 8 1:30 - SAST 1903 Mar 2:00 SA SAST Link Africa/Johannesburg Africa/Mbabane # Eswatini I use the command: ./zic -d ./tzdata/etc/zoneinfo africa antarctica asia australasia backward backzone etcetera europe factory northamerica pacificnew southamerica systemv and expect the information in 'backzone' to override the information in 'africa'. But it does not. These two files are generated but are binary identical. zoneinfo/Africa/Mbabane zoneinfo/Africa/Johannesburg What is the correct command line for zic so that information in backzone is considered? I have tried putting backzone at he begin or end of the list of files, but that made no difference in the binary output.

2 1

Re: [tz] Timezone in Autonomous Republic of Crimea and spelling of Kyiv
by Sergij Marchenko June 28, 2019

June 28, 2019

Thank you, Mr. Paul Eggert! -- Best regards, Sergij Marchenko mailto:makars@gmail.com http://makar.homelinux.net Skype: makarsoft Viber/WhatsApp/Telegram/Signal: +380661877234

1 0

Summer Time Brazil 2019 - Information
by Walmir Tadeu Satyro June 27, 2019

June 27, 2019

Good Afternoon, I need to know if there is an update of TzUpdater for the Brazil region in 2019. Today we need to validate if there is or was something specific to update here in Brazil. We understand that this is usually time consuming ... It is a question of updating the product and in it is contemplated specific rules for each region not only Brazil As we did not have defined summer schedules there were no corrections issued by IANA regularly, they are valid internationally since it is the Java product. To check if there is a most recent Brazil update in case of summer time 2019 Best regards. [Ass_Everis_WTS] Esta mensagem, incluindo seus anexos, pode conter informa??es privilegiadas e/ou de car?ter confidencial, n?o podendo ser retransmitida sem autoriza??o do remetente. Se voc? n?o ? o destinat?rio ou pessoa autorizada para receb?-la, informamos que o seu uso, divulga??o, c?pia ou arquivamento s?o proibidos. Portanto, se voc? recebeu esta mensagem por engano, por favor nos informe respondendo imediatamente a este e-mail e delete o seu conte?do. This message, including its attachments, may contain privileged or confidential information, and it must not be fowarded without the express authorization of the sender. If you are not the intended recipient, we hereby inform you that the use, disclosure, copy or filing are forbidden. So, if you received this message as a mistake, please inform us by answering this e-mail and deleting its contents Questo messaggio, inclusi gli allegati, potrebbe contenere informazioni privilegiate e/o riservate, e non deve essere ritrasmesse senza l'autorizzazione del mittente. Se non siete il destinatario o la persona autorizzata a riceverlo, informiamo che il suo utilizzo, diffusione, copia o archiviazione sono proibite. Quindi, se avete ricevuto questo messaggio per errore, per cortesia ci informi rispondendo immediatamente a questa email e cancelli il suo contenuto

2 1

I: Brazil Won't Change Clocks in 2019
by DONATELLA SABELLICO June 27, 2019

June 27, 2019

Hi, we got We got this advice.. https://www.timeanddate.com/news/time/brazil-scraps-dst.html the latest 2019A iana table reports Rule Brazil 2018 max - Nov Sun>=1 0:00 1:00 - So we need a new level.. Do you know when the Timezone package will be released' thanks Da: DONATELLA SABELLICO Inviato: lunedì 27 maggio 2019 11:20 A: eggert(a)cs.ucla.edu Cc: Anawesha Khuntia <AnaweshaK(a)in.ibm.com>; Java Timezone Utility Support <JTZU(a)uk.ibm.com>; Sbriccoli's L3 only <sbriccolisl3only(a)hcl.com>; SILVANO LUTRI <silvano.lutri(a)hcl.com> Oggetto: Brazil Won't Change Clocks in 2019 Priorità: Alta Hi Paul sorry to disturb but.. We got this advice.. https://www.timeanddate.com/news/time/brazil-scraps-dst.html We are using Iana 2019A table. Basing on that it seems NO Nov 2019 changes are into them...but when the new IAN Dst olson will be released? Thanks. Da: DONATELLA SABELLICO Inviato: lunedì 8 ottobre 2018 17:39 A: Paul Eggert <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>>; ALESSIO FIORAVANTI <alessio.fioravanti(a)hcl.com<mailto:alessio.fioravanti@hcl.com>> Cc: Anawesha Khuntia <AnaweshaK(a)in.ibm.com<mailto:AnaweshaK@in.ibm.com>>; Java Timezone Utility Support <JTZU(a)uk.ibm.com<mailto:JTZU@uk.ibm.com>>; Sbriccoli's L3 only <sbriccolisl3only(a)hcl.com<mailto:sbriccolisl3only@hcl.com>> Oggetto: Re: R: DST rBrazil 2018 changed again to Nov 18th ..When DST Olson table will be released? Hi jtuz is not our tool. We owned tws product. Well at this time we need to wait official approval from Brazil president. Thanks ________________________________ Da: Paul Eggert <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>> Inviato: lunedì 8 ottobre 2018 17:25:46 A: DONATELLA SABELLICO; ALESSIO FIORAVANTI Cc: Anawesha Khuntia; Java Timezone Utility Support; Sbriccoli's L3 only Oggetto: Re: R: DST rBrazil 2018 changed again to Nov 18th ..When DST Olson table will be released? On 10/8/18 8:15 AM, DONATELLA SABELLICO wrote: > WAS/Java that means that we need also that JTUZ tool is refreshed with the new tables... > > So even if we update our packages with these "developer" dst olson table ... the Jtuz table will be not ....so the Jtuz tool will still not be updated. You can update the Java tables from whatever data you like. See: https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.orac… ::DISCLAIMER:: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

35 150

Minor clerical fixes
by Tim Parenti June 27, 2019

June 27, 2019

Mostly grammar and consistency around areas that have changed recently. See attached. -- Tim Parenti

2 1