- tz - lists.iana.org

[tz-announce] 2018f release of tz code and data available
by Paul Eggert Oct. 18, 2018

Oct. 18, 2018

The 2018f 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: Volgograd moves from +03 to +04 on 2018-10-28. Fiji ends DST 2019-01-13, not 2019-01-20. Most of Chile changes DST dates, effective 2019-04-06. Changes to future timestamps Volgograd moves from +03 to +04 on 2018-10-28 at 02:00. (Thanks to Alexander Fetisov and Stepan Golosunov.) Fiji ends DST 2019-01-13 instead of the 2019-01-20 previously predicted. (Thanks to Raymond Kumar.) Adjust future predictions accordingly. Most of Chile will end DST on the first Saturday in April at 24:00 mainland time, and resume DST on the first Saturday in September at 24:00 mainland time. The changes are effective from 2019-04-06, and do not affect the Magallanes region modeled by America/Punta_Arenas. (Thanks to Juan Correa and Tim Parenti.) Adjust future predictions accordingly. Changes to past timestamps The 2018-05-05 North Korea 30-minute time zone change took place at 23:30 the previous day, not at 00:00 that day. China's 1988 spring-forward transition was on April 17, not April 10. Its DST transitions in 1986/91 were at 02:00, not 00:00. (Thanks to P Chan.) Fix several issues for Macau before 1992. Macau's pre-1904 LMT was off by 10 s. Macau switched to +08 in 1904 not 1912, and temporarily switched to +09/+10 during World War II. Macau observed DST in 1942/79, not 1961/80, and there were several errors for transition times and dates. (Thanks to P Chan.) The 1948-1951 fallback transitions in Japan were at 25:00 on September's second Saturday, not at 24:00. (Thanks to Phake Nick.) zic turns this into 01:00 on the day after September's second Saturday, which is the best that POSIX or C platforms can do. Incorporate 1940-1949 Asia/Shanghai DST transitions from a 2014 paper by Li Yu, replacing more-questionable data from Shanks. Changes to time zone abbreviations Use "PST" and "PDT" for Philippine time. (Thanks to Paul Goyette.) Changes to code zic now always generates TZif files where time type 0 is used for timestamps before the first transition. This simplifies the reading of TZif files and should not affect behavior of existing TZif readers because the same set of time types is used; only their internal indexes may have changed. This affects only the legacy zones EST5EDT, CST6CDT, MST7MDT, PST8PDT, CET, MET, and EET, which previously used nonzero types for these timestamps. Because of the type 0 change, zic no longer outputs a dummy transition at time -2**59 (before the Big Bang), as clients should no longer need this to handle historical timestamps correctly. This reverts a change introduced in 2013d and shrinks most TZif files by a few bytes. zic now supports negative time-of-day in Rule and Leap lines, e.g., "Rule X min max - Apr lastSun -6:00 1:00 -" means the transition occurs at 18:00 on the Saturday before the last Sunday in April. This behavior was documented in 2018a but the code did not entirely match the documentation. localtime.c no longer requires at least one time type in TZif files that lack transitions or have a POSIX-style TZ string. This future-proofs the code against possible future extensions to the format that would allow TZif files with POSIX-style TZ strings and without transitions or time types. A read-access subscript error in localtime.c has been fixed. It could occur only in TZif files with timecnt == 0, something that does not happen in practice now but could happen in future versions. localtime.c no longer ignores TZif POSIX-style TZ strings that specify only standard time. Instead, these TZ strings now override the default time type for timestamps after the last transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. leapseconds.awk now outputs "#updated" and "#expires" comments, and supports leap seconds at the ends of months other than June and December. (Inspired by suggestions from Chris Woodbury.) Changes to documentation New restrictions: A Rule name must start with a character that is neither an ASCII digit nor "-" nor "+", and an unquoted name should not use characters in the set "!$%&'()*,/:;<=>?@[\]^`{|}~". The latter restriction makes room for future extensions (a possibility noted by Tom Lane). tzfile.5 now documents what time types apply before the first and after the last transition, if any. Documentation now uses the spelling "timezone" for a TZ setting that determines timestamp history, and "time zone" for a geographic region currently sharing the same standard time. The name "TZif" is now used for the tz binary data format. tz-link.htm now mentions the A0 TimeZone Migration utilities. (Thanks to Aldrin Martoq for the link.) Changes to build procedure New 'make' target 'rearguard_tarballs' to build the rearguard tarball only. This is a convenience on platforms that lack lzip if you want to build the rearguard tarball. (Problem reported by Deborah Goldsmith.) tzdata.zi is now more stable from release to release. (Problem noted by Tom Lane.) It is also a bit shorter. tzdata.zi now can contain comment lines documenting configuration information, such as which data format was selected, which input files were used, and how leap seconds are treated. (Problems noted by Lester Caine and Brian Inglis.) If the Makefile defaults are used these comment lines are absent, for backward compatibility. A redistributor intending to alter its copy of the files should also append "-LABEL" to the 'version' file's first line, where "LABEL" identifies the redistributor's change. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018f.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018f.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018f.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 7c97eb855432c3557a8d84727a685fcd2fdb2bff dated 2018-10-18 00:14:18 -0700 and tagged '2018f' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: d4270918fbd8eb786e6f5cec9f06df6a850bbf1ec278f60ce493b6b7e10e2ad1388383edcd869f07bc78b9d99a123d6f54e74105cdd3d5cb6c98e11d3f043727 tzcode2018f.tar.gz f876729419d45e2b861e564ec7d5940f34fab38c3fedc18852bb800010428c12506f71bde1f20feb23859065118ad4658d97efe89af6f4305cea2beafc515aeb tzdata2018f.tar.gz 4cdc6e2fc3b84c25ba4ac99329cfa7c507bb9be22cab00604bfab65944d225fc605a842e8b0a05e258f6f42eddf8b68273729a211ed78b0172afc2788ae1f29c tzdb-2018f.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlvINAMACgkQ7ZfpDmKq fjSnMRAAr/pLmohlfPzhkcc+Yw4FbpBOYUsj9XeExKd5WDp4nsjgOwLfLJcwT7oo VSp3tiv+jGh+/ZnSZWSTHT/YfBdmRjVmj42FBWZgjYwr70373HGP/vIwHgUrv5Kk wUse5BUX4nwQK0xcuaOzKF5+uUG0MoKDo6sRzrYoS8JMP/mVlLtkZt1GHs99Kkaj Gnn6lyLOTChxrLU2UP1lra0h/t7T/dtTgGHf0biN7onNLYFiRL+La9pJKNVuvljW mjSaPw1Pl+1tCFMo6Rcm8Rkq/cazJaQY2Pdw/CGEvK+a9tjGBf+vvxWhIiLZimAH eygVfg6XCfn7gfjTn6fZHM3+lgGF6W4uQ429jEOR/OUCymb4gOPWB5emSVFms3vy XkHsazZa3UwAD/dzGJ1Y0CXiwggiNqe6xqn41bzqaLgtSg64gK17CIeu42soniZe 5SCXVl45tsURx/z50pQ8Q5I+JK8DvYkkhmP5l8CI6OhYUr8DY+bLdK0+fao8coT9 JXee8U+2ARx7UxgP+yytx+iDzHiRgnnF1is0SkUw9Ksnp61iY9sgpTIuzcr6SOs3 ZLeAT3c6Zmuq+Wikm7u1qVTyR5QcbEmuTspY+4wG9Tn7DrzWnSFj76B1P4+8bENY 28AW/Ca8cqMfcKYv0PVoHhVH3lb1h/zOLV8B06hIWcOErGTGPd4= =9tf8 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlvINAMACgkQ7ZfpDmKq fjRDfg//ciH78cevDN3GyghrxtdY6diUwqaw4qvAngDxeygWS6Hcm8JnExAS7EfZ Mcp1SwDog47Bv+9p11twd0SvdkFPXzrQ4S77ZXIddgTEmZ+a7fVLMtvwn/9w61gL wmEUgSE4yECabGG2mGLMbGaPGmhjCi5Gh3ErmhcmS0xuEvfkyAPcN2KYvLlFt2+H DLvYzYIWhf5O910twzySiIDEpuOsYf60BV9v5/NeEa7Q9kAAytomkhU4WWAeazgU DUFMyWrN9pcn4eWrKFFcRxbXyzSTRdx0E6kgEcVfSjxx75SwNAmWLb5wWarrKV5F MqPRlzVA3favvGNsBGZMdGh2E7Q+qVBGlTxftv2scYX/9I9tP6zMC7/yTl3ys2Hb tNZd5D/99az2VBMxSkaJW8AwwqfHqX5c3GO7p1e5zKy4p5lEMvHtbA1j8GWmy8mQ C1T0pi4JDkq4it/YJyJm8m6eYhUV/v3ftHNPgRIbcoFfMPy+n+wtFAwjY0ml4wKd oUi2x/05u3zoPwGU59aUw09re8LKvbBiu7EuI8p4ZUVaXgkatAqw0T/4jF69hEMx 6X7fY2It1sSg59X5ApWL9JlX8/lK2R5g6MKRqv99HPh60zQ+et8tI6rBY+lX4wx6 2XSOr1OwCNG0l7qLHRx6HVZ7Ce/pX0Mn5TgxonWTKVBh7Jb9Tac= =6cRa -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlvINAUACgkQ7ZfpDmKq fjR7Ag//XMMJj6ZeiWZokr3NEKLNKWwEGo8j/l1XH3tq74KUOINnJqar/d/EPNoi 6mpZHiZ9r03md6TZ/D4Fx2X6lXkdzHnwGiSWY7GzaJSpTqZxzgyWaaZDE9dxGC+5 FB/f96/BSx6oRqZ4dZRBV0vgsjuluo3k9vMotNbUA5lMbIu94QnD4WJ602hNaFbe odI8EXtnr6EQyLBvSFfdbxYLq02cndWPqYTE9cbmNXZ4LnufB/uKmNRYfHIkCOF+ 4ZZNghRbUsC/sUnoSNXaDUV/l43juEPN6RUMKsodOZpAhWyAgRMWw5lbrkCwRMvI dIvpdfynPvQznUuDbq+cyGZefFah9TMPPFZQdGtUejC4hrbWsaP3myTj/jVgvIKC 5qHMb2qD1MebUZtQq2dGZw7/SdyxVmaz8HLINkwrNvfpfGc6+weGmvnPVthPrQxK 4IwQQvzyi4UbPnZLiDuAJZ09OgJ+HgM3CkkIETcUfIXvkYcxFFL4uY+6pHGedoBX KyfPeW3Jc/LivBvy52AOjqYzTjdddQVUymzOQ64rAAzgnBNGdIraCwWEwuBVjHkG hUQFpfjMEkD7kQfxzTxH/LbsT1ifjBBkzxWjeuL8ewhgwykeuwVTeixujH5HKcfx HL2C8e5yY+Zo9eQkyc6YpkUmlnNhsrFLdEoFoAJSrku1dHssw4s= =FA6n -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets, this particular release's data entries are also available in a rearguard-format tarball and signature that does not contain such offsets. This is intended to be a temporary transition aid for these parsers. The URLs are: https://web.cs.ucla.edu/~eggert/tz/release/2018f/tzdata2018f-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2018f/tzdata2018f-rearguard.tar.… with the following SHA-512 and GPG checksums: 7c6105cda6bc81217d7740201133d9ccf0d4ca0f5f3e6248fa071c676976c28f06cf7c2240e455d1948f5b2ef5f8e359aca8b5206beddbd6af79c3a7070ba301 tzdata2018f-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlvINAMACgkQ7ZfpDmKq fjQM0RAAi56P17pHUDukQ81drgNlRCliqRe1x0047jxCtkrBvIDdJb7lnrTolhrH P78E/f36r4PTAKjGjO9FZvvs61si3YSiHcNdBGzzf41Mhwvbsk14a6ybeU6vRJrj AWUNj/LYg+PK1fUjeY/CrViFWmXPtndPpew9G1cyL3H8HvGQlPm6Ey9JDv6rVVi5 mSkBKXcN5w8VfMzMx2UDLFfRgSnTa4bjbuv/I8HXoAJjtzBR+53G/6oGeXiZ9Fnd hwZa8DbAZ+H4YdsPIdUo/Oz/mU/cfvTZcLkTy7rBciEWk7ylXMddlqdc7+blToga 95eeNGinB6b+8pEpdg0BJTCq7VW4TBjG6W4Zu5RsS3ZJOa8TeMyKVR2S0ZV6zCmN +SvFUHWZ9dqKR7jppxbIsoKSeexpY7WPGJJBwjgZEaIudN0HWok+mw0iLG0U6D2q va3cIEuVG4pitb9uQmuM3hVPuO0Bndxm6ws3hSxvRmTuluJIL4tXErhVJqqZsCJ1 XvqcFlCSD7rtcwP7YzNCKgxzCfMXMvf1Nwfylq8ZWhfaWGk/lBm+eH18zKPHBIe2 OMU9uNxF12KlVNmNknod+AaLTHcXan21vgbR7Syar+fGLofcuPyDOu2frB1FxDaW eotUedxfia9p4gbH5qjMeBHPf2ca8yCf0Dnfmxv174NWVLkOmnE= =OEcz -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED] * tz-link.html, theory.html: Remove outdated info, fix links and dates.
by Paul Eggert Oct. 18, 2018

Oct. 18, 2018

--- theory.html | 2 +- tz-link.html | 12 +++--------- 2 files changed, 4 insertions(+), 10 deletions(-) diff --git a/theory.html b/theory.html index 6e4a14e..8dd58db 100644 --- a/theory.html +++ b/theory.html @@ -1339,7 +1339,7 @@ Sources for time on other planets: Matt Williams, "<a href="https://www.universetoday.com/37481/days-of-the-planets/">How long is a day on the other planets of the solar system?</a>" - (2017-04-27). + (2016-01-20). </li> </ul> </section> diff --git a/tz-link.html b/tz-link.html index eef7b63..8593ba6 100644 --- a/tz-link.html +++ b/tz-link.html @@ -35,8 +35,6 @@ including C Library</a> (used in <a href="https://en.wikipedia.org/wiki/Linux"><abbr>GNU</abbr>/Linux</a>), <a href="https://www.android.com">Android</a>, -<a href="https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS">B2G -<abbr title="Operating System">OS</abbr></a>, <a href="https://www.freebsd.org">Free<abbr title="Berkeley Software Distribution">BSD</abbr></a>, <a href="https://netbsd.org">Net<abbr>BSD</abbr></a>, @@ -68,8 +66,7 @@ name of the largest city within the region containing the clocks. For example, <code>America/New_York</code> represents most of the <abbr title="United States">US</abbr> eastern time zone; <code>America/Phoenix</code> represents most of Arizona, which -uses mountain time without daylight saving time (<abbr -title="daylight saving time">DST</abbr>); +uses mountain time without daylight saving time (<abbr>DST</abbr>); <code>America/Detroit</code> represents most of Michigan, which uses eastern time but with different <abbr>DST</abbr> rules in 1975; and other entries represent smaller regions like Starke County, @@ -548,7 +545,7 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="https://www.relativedata.com/time-zone-master">Time Zone +<li><a href="https://relativedata.com/page/Time-Zone-Master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version is free.</li> @@ -574,9 +571,6 @@ its own <code>tztab</code>(4) format.</li> <a href="#System.TimeZoneInfo">above</a>.</li> <li><a href="https://www.worldtimeserver.com">World Time Server</a> is another time zone database.</li> -<li><a href="http://tycho.usno.navy.mil/tzones.html">World Time Zones</a> -contains data from the Time Service Department of the -<abbr>US</abbr> Naval Observatory.</li> <li>The <a href="https://www.iata.org/publications/store/Pages/standard-schedules-informatio…">Standard Schedules Information Manual</a> of the @@ -762,7 +756,7 @@ href="ftp://ftp.cs.huji.ac.il/pub/tz/announcements" hreflang="he">announcements (in Hebrew)</a>.</dd> <dt>Italy</dt> <dd>The National Institute of Metrological Research maintains a -<a href="http://www.nanospin.eu/res/tf/ora_legale_i.shtml">table of civil time +<a href="http://oldsite.inrim.it/res/tf/ora_legale_i.shtml">table of civil time (in Italian)</a>.</dd> <dt>Macau</dt> <dd>The Meteorological and Geophysical Bureau maintains a -- 2.17.1

1 0

[TZDB for Delphi] Encountered issue using TBundledTimezone on LINUX
by Jean Frauciel Oct. 17, 2018

Oct. 17, 2018

Hello, I'm working on the development of a software that uses the TZDB for Delphi to deal with the timezones' management, and I'd like to have your opinion about a problem that we are facing. In a procedure, in order to decompose the periods of a timezone, we have to know the timezone's year of a UTC DateTime. To do so, we are using these commands : thisBundledTimezone := TBundledTimeZone.GetTimeZone('America/Los_Angeles'); timeZoneYear := YearOf(IncMinute(aUTCDateTime, Round(thisBundledTimezone.UtcOffset.TotalMinutes))); This is fine if the program is running on Windows, but it crashes on Linux. The error occurs when we're trying to get the UtcOffset. The TBundledTimeZone can't read the FPeriods[I] in the function GetPeriodAndRule. The thing is that FPeriods is a TList that is not typed (with TCompiledPeriod) and Delphi can't use it this way with Linux. We can by the way see a warning when compiling a project that includes TZDB.pas, telling that TList is deprecated. We have solved the problem by modifying the TZDB.pas unit, but it seems weird to have to do this. We are also using the Decomposer.pas unit, but it doesn't have any problem with Linux because it is already working with typed TLists (function Decompose). Do you have any idea about this issue ? You can check the attachment to see our changes. Thank you in advance for your answer, Best regards, Jean FRAUCIEL Développeur Moteur jfrauciel(a)kiamo.fr +33 5 47 48 33 20 <33547483320> | [image: logo web] <http://www.conecteo.fr/> [image: logo linkedin] <https://www.linkedin.com/company/conecteo> <https://twitter.com/Conecteo> <https://www.facebook.com/conecteo> Chers clients et partenaires, rejoignez votre espace communautaire <https://my.kiamo.fr/welcome>

2 1

Palestine 2018 summer time end
by Sharef Mustafa Oct. 17, 2018

Oct. 17, 2018

Hi, As per the Palestinian cabinet decision announced Oct 16th 2018, the summer time for the state of Palestine will end on Sat, Oct 27th 2018 , the clock shall be returned by 60 minutes at 01:00 o'clock (as per the announcement ) Here is a link to the cabinet announcement (in Arabic) : http://palestinecabinet.gov.ps/Website/AR/ViewDetails?ID=42494 Also another link from a local news portal (in Arabic): https://www.maannews.net/Content.aspx?id=964375 Unfortunately I did not find an English source. Please note that this change affects Gaza & Hebron time zones BR Sharef Also

2 1

Wrong spelling of a city in a timezone name
by Igor Oct. 16, 2018

Oct. 16, 2018

Hello. Currently, in your timezone files Ukrainian capital is spelled incorrectly. Kyiv is the correct spelling as decided by UNCSGN (United Nations Conferences on the Standardization of Geographical Names) and UNGEGN (United Nations Group of Experts on Geographical Names)."Kiev" is transliteration from Russian and as Ukraine, which is an independent country, has only one official language, which is Ukrainian, using transliteration from Russian is offending and incorrect. I saw in your files that you understand that Kyiv is correct spelling and you reason that Kiev is more common, alas that argument is wrong. It's only more common because it's been mistakingly used for a long period of time. Ukrainian government is currently running a campaign called Kyiv Not Kiev to raise awareness of international community and it already has results, many companies, like Microsoft, BBC, Google, Facebook and others have already fixed their spelling. I suggest IANA follows this example and fixes this incorrect spelling. Regards, Igor

8 10

Another change on Brazilian DST time
by Raphael Bastos Oct. 16, 2018

Oct. 16, 2018

Yo, Please, abort this change: https://g1.globo.com/politica/noticia/2018/10/15/planalto-informa-que-nao-h… Att, Raphael Bastos aka Tyresix *====================================================* *Wiki Hackstore* - https://wiki.hackstore.com.br <http://wiki.hackstore.com.br/> *Área 31 Hackerspace* - https://www.area31.net.br <http://www.area31.net.br> *====================================================*

1 0

Brazil DST called out
by Rodrigo Freire Oct. 16, 2018

Oct. 16, 2018

Government decided to abandon the announced second DST change. So it will start in November 4. https://g1.globo.com/politica/noticia/2018/10/15/planalto-informa-que-nao-h… - RF Sent from a mobile device

1 0

Ethiopia local time
by admin＠afocha.com Oct. 13, 2018

Oct. 13, 2018

Greetings, Although Ethiopia is officially in East Africa Time (UTC +3:00), the local time used in the country adopts a different system where 6:00 AM is interpreted as 12:00 and socially used as such. People will see a clock with the time at 1:30, and they will say this is 7:30. The local time is used by businesses in the country and by government offices. Everyone generally does this conversion in their heads, so at times, someone who is unfamiliar with this system can end up inadvertently scheduling meetings for the wrong time. This method of time tracking was developed and maintained with the premise of associating the clock's starting point of 12:00 with sunrise, which is roughly taking place around 6:00 AM every day. So East Africa Time - 6:00 is the working time used by the vast majority of Ethiopians. Here's an article discussing this time system: https://www.pri.org/stories/2015-01-30/if-you-have-meeting-ethiopia-you-bet… Is it possible to include Ethiopia's local time system into the time zone database? If so, what are the requirements for submitting a new time zone? Thanks for your consideration. Regards, Khalid Duri

17 48

Re: [tz] Europe/Volgograd change from UTC+3 to UTC+4 from 28oct2018
by Paul Eggert Oct. 11, 2018

Oct. 11, 2018

Alexander Fetisov wrote: > Volgograd region in southern Russia (Europe/Volgograd) change timezone from > UTC+3 to UTC+4 from 28oct2018. > > http://sozd.parliament.gov.ru/bill/452878-7 Thanks for the heads-up and the URL. Its supporting info says the transition occurs at 02:00 that day, the usual practice in that region. That web page says "Находится на рассмотрении" which Google Translate renders as "Is pending", and it later says "Срок представления поправок 10.10.2018" which Google Translate renders as "Term for the submission of amendments 10/10/2018", so it sounds like the bill is under consideration but is not yet law and might be amended. Am I correct? If so, we need to know if and when the proposed change becomes definite. If we're pretty sure the law will go in as-is, we might want to update tzdb before October 10 since this is not much notice for downstream users.

3 9

FW: State of Palestine Time zone - need to update
by maysa＠mtit.gov.ps Oct. 10, 2018

Oct. 10, 2018

Dear Sir, I'm contacting you in regard to the time zone data base the field related to the state of Palestine, it's known that Palestine is recognized as a state and it has the Following ISO and Alpha codes, English short name (upper/lower case) Alpha-2 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_e lements> Alpha-3 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3#Officially_assigned_code_e lements> Numeric code <https://en.wikipedia.org/wiki/ISO_3166-1_numeric#Officially_assigned_code_e lements> Link to ISO 3166-2 <https://en.wikipedia.org/wiki/ISO_3166-2> subdivision codes <https://en.wikipedia.org/wiki/State_of_Palestine> State of Palestine <https://en.wikipedia.org/wiki/State_of_Palestine> Palestine, State of <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PS> PS PSE 275 <https://en.wikipedia.org/wiki/ISO_3166-2:PS> ISO 3166-2:PS PS-JEM Jerusalem <https://en.wikipedia.org/wiki/Jerusalem_Governorate> Al Quds I checked the published data regarding the time zones related to Palestine and noticed that it's not accurate, And hence I would like to ask for an update to the time zone data base related to Palestine to be as follow: PS State of Palestine Asia/AlQuds UTC +3:00 Instead of the following data : PS Palestinian Territory <https://timezonedb.com/time-zones/Asia/Gaza> Asia/Gaza UTC +03:00 PS Palestinian Territory <https://timezonedb.com/time-zones/Asia/Hebron> Asia/Hebron UTC +03:00 Kindly advise if any supporting documents, information or procedures are needed from our side. BR Maysa Monayer Telecom Administration - Deputy General Director Ministry of Telecom and IT (State of Palestine) Mobile: +970-562500044

2 3

Re: [tz] tz Digest, Vol 85, Issue 19 Summer time of Brazil
by Daniel Soares de Oliveira Oct. 9, 2018

Oct. 9, 2018

1 0

Apple Watch Series 4 reboot loop on day of Australian spring-forward transition
by Paul Eggert Oct. 8, 2018

Oct. 8, 2018

Benjamin Mayo reports in 9to5Mac that last weekend's spring-forward clock transition in Australia caused the Apple Watch Series 4 to go into a reboot loop when displaying the day's timeline in the Activity complication on the Infograph Modular face. The watch reboots, attempts to display the timeline again, and reboots again, over and over. Apparently the application has trouble with a 23-hour day. Apple solved the problem by - doing nothing yet. After 23 hours of rebooting, an Australian user's watch (if it still has power left) reboots, sees a new day with 24 hours, and displays a nice 24-hour timeline again. Mayo writes, "Obviously, Apple will need to release a bug-fix software update to stop this problem from happening again." There's no word yet on what the current Apple software will do when faced with a 25-hour day. Mayo B. Some Apple Watch Series 4 models repeatedly crashing and rebooting due to daylight saving time bug. 9to5Mac. 2018-10-07 04:31 -07. https://9to5mac.com/2018/10/07/apple-watch-series-4-crash-loop-bug/

1 0

Re: [tz] [PROPOSED] Improve leapseconds support
by Hal Murray Oct. 7, 2018

Oct. 7, 2018

eggert(a)cs.ucla.edu said: > * NEWS, leapseconds.awk: Add support for leap seconds at the ends of months > other than June and December. A leap second other than June or December is probably an error in the input data. I would leave the check and add a big comment. Maybe write the code so that it is a simple edit to disable the check. I think there is provision for an intermediate stage between Jun/Dec and every month. Apr/Jun/Sep/Dec. -- These are my opinions. I hate spam.

5 7

[PROPOSED] Improve leapseconds support
by Paul Eggert Oct. 6, 2018

Oct. 6, 2018

(Inspired by a suggestion from Chris Woodbury.) * NEWS, leapseconds.awk: Add support for leap seconds at the ends of months other than June and December. --- NEWS | 5 +++-- leapseconds.awk | 34 +++++++++++++++++++++++++--------- 2 files changed, 28 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index e9f5366..9780cc8 100644 --- a/NEWS +++ b/NEWS @@ -86,8 +86,9 @@ Unreleased, experimental changes transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. - leapseconds.awk now outputs "#updated" and "#expires" comments. - (Inspired by a suggestion from Chris Woodbury.) + leapseconds.awk now outputs "#updated" and "#expires" comments, + and supports leap seconds at the ends of months other than June + and December. (Inspired by suggestions from Chris Woodbury.) Changes to documentation diff --git a/leapseconds.awk b/leapseconds.awk index 6b069b3..ea0567c 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -35,9 +35,25 @@ BEGIN { 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 "# If the leap second is Stationary (S) the given time is UTC." - print "" - print "# Leap YEAR MONTH DAY HH:MM:SS CORR R/S" + + monthabbr[ 1] = "Jan" + monthabbr[ 2] = "Feb" + monthabbr[ 3] = "Mar" + monthabbr[ 4] = "Apr" + monthabbr[ 5] = "May" + monthabbr[ 6] = "Jun" + monthabbr[ 7] = "Jul" + monthabbr[ 8] = "Aug" + monthabbr[ 9] = "Sep" + monthabbr[10] = "Oct" + monthabbr[11] = "Nov" + monthabbr[12] = "Dec" + for (i in monthabbr) { + monthnum[monthabbr[i]] = i + monthlen[i] = 31 + } + monthlen[2] = 28 + monthlen[4] = monthlen[6] = monthlen[9] = monthlen[11] = 30 } /^#\tUpdated through/ || /^#\tFile expires on:/ { @@ -62,14 +78,14 @@ BEGIN { } else { sign = "23:59:59\t-" } - if (month == "Jan") { + m = monthnum[month] - 1 + if (m == 0) { year--; - month = "Dec"; - day = 31 - } else if (month == "Jul") { - month = "Jun"; - day = 30 + m = 12 } + month = monthabbr[m] + day = monthlen[m] + day += m == 2 && year % 4 == 0 && (year % 100 != 0 || year % 400 == 0) printf "Leap\t%s\t%s\t%s\t%s\tS\n", year, month, day, sign } old_TAI_minus_UTC = TAI_minus_UTC -- 2.17.1

1 0

Rename Ukrainian cities to their official transliterated names
by Volodymyr Kostyrko Oct. 5, 2018

Oct. 5, 2018

Hello. This is my first attempt on patching tz database. Hope I did everything right. Included patch renames Kiev to Kyiv, Uzhgorod to Uzhhorod and Zaporozhye to Zaporizhzhia according to official transliteration rules that came in effect 2014. According to Google search most sites are already using Uzhhorod and Zaporizhzhia to name cities, while with Kyiv it's a little bit complicated, as it's the capital so it's name was appearing on a huge list of sites throughout years... I'm just trying to bring a little bit of lawful sanity… Thanks in advance. -- Sphinx of black quartz judge my vow.

16 31

[PROPOSED] Improve leapseconds.awk commentary
by Paul Eggert Oct. 5, 2018

Oct. 5, 2018

(Inspired by a suggestion by Chris Woodbury.) * NEWS: Mention this. * leapseconds.awk: Improve commentary in output file. Output "#updated" and "#expires" comments that reproduce the updated and expiry timestamps in the input file. --- NEWS | 3 +++ leapseconds.awk | 36 +++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index 395d9a8..e9f5366 100644 --- a/NEWS +++ b/NEWS @@ -86,6 +86,9 @@ Unreleased, experimental changes transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. + leapseconds.awk now outputs "#updated" and "#expires" comments. + (Inspired by a suggestion from Chris Woodbury.) + Changes to documentation New restrictions: A Rule name must start with a character that diff --git a/leapseconds.awk b/leapseconds.awk index 66eb64d..6b069b3 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -8,21 +8,25 @@ BEGIN { print "# This file is in the public domain." print "" print "# This file is generated automatically from the data in the public-domain" - print "# leap-seconds.list file, which is copied from:" - print "# ftp://ftp.nist.gov/pub/time/leap-seconds.list" + print "# leap-seconds.list file, which can be copied from" + print "# <ftp://ftp.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list>." print "# For more about leap-seconds.list, please see" print "# The NTP Timescale and Leap Seconds" - print "# https://www.eecis.udel.edu/~mills/leap.html" + print "# <https://www.eecis.udel.edu/~mills/leap.html>." print "" 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); see" - print "# Levine J. Coordinated Universal Time and the leap second." + print "# (which measures the true angular orientation of the earth in space)" + print "# and publishes leap second data in a copyrighted file" + print "# <https://hpiers.obspm.fr/iers/bul/bulc/Leap_Second.dat>." + print "# See: Levine J. Coordinated Universal Time and the leap second." print "# URSI Radio Sci Bull. 2016;89(4):30-6. doi:10.23919/URSIRSB.2016.7909995" - print "# http://ieeexplore.ieee.org/document/7909995/" + print "# <https://ieeexplore.ieee.org/document/7909995>." print "# There were no leap seconds before 1972, because the official mechanism" print "# accounting for the discrepancy between atomic time and the earth's rotation" - print "# did not exist until the early 1970s." + print "# did not exist." print "" print "# The correction (+ or -) is made at the given time, so lines" print "# will typically look like:" @@ -30,18 +34,19 @@ BEGIN { print "# or" print "# Leap YEAR MON DAY 23:59:59 - R/S" print "" - print "# If the leapsecond is Rolling (R) the given time is local time." - print "# If the leapsecond is Stationary (S) the given time is UTC." + print "# If the leap second is Rolling (R) the given time is local time (unused here)." + print "# If the leap second is Stationary (S) the given time is UTC." print "" print "# Leap YEAR MONTH DAY HH:MM:SS CORR R/S" } -/^ *$/ { next } - /^#\tUpdated through/ || /^#\tFile expires on:/ { last_lines = last_lines $0 "\n" } +/^#[$][ \t]/ { updated = $2 } +/^#[@][ \t]/ { expires = $2 } + /^#/ { next } { @@ -71,5 +76,14 @@ BEGIN { } END { + # The difference between the NTP and POSIX epochs is 70 years + # (including 17 leap days), each 24 hours of 60 minutes of 60 + # seconds each. + epoch_minus_NTP = ((1970 - 1900) * 365 + 17) * 24 * 60 * 60 + + print "" + print "# POSIX timestamps for the data in this file:" + printf "#updated %s\n", updated - epoch_minus_NTP + printf "#expires %s\n", expires - epoch_minus_NTP printf "\n%s", last_lines } -- 2.17.1

1 0

Re: [tz] [PROPOSED] Allow some IPA symbols in commentary
by Paul Eggert Oct. 4, 2018

Oct. 4, 2018

On 10/4/18 9:23 AM, Paul.Koning(a)dell.com wrote: > I wonder if the Unicode standard says so, or if this is a Linux bug. I looked into it, and it's arguably a bug in the glibc regular expression matcher: it does not recognize u̯ as alphabetic because it's composed of U+0075 U+032F and the latter is not alphabetic. Let's add a comment to that effect and remove ɪ from the macro since it works OK. Proposed further patch attached.

1 0

[PROPOSED] Allow some IPA symbols in commentary
by Paul Eggert Oct. 4, 2018

Oct. 4, 2018

This for the [ˈkɪjiu̯] recently added to Kiev comments. * Makefile (UNUSUAL_OK_LATIN_1, UNUSUAL_OK_IPA): New macros. (UNUSUAL_OK_CHARSET): Use them. (check_character_set): Broaden list of exempt lines. --- Makefile | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index 3d06d93..39da17e 100644 --- a/Makefile +++ b/Makefile @@ -418,10 +418,14 @@ SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' +# These characters are Latin-1, and so are likely to be displayable +# even in editors with limited character sets. +UNUSUAL_OK_LATIN_1 = «°±»½¾× +# IPA symbols are OK in commentary despite being non-alphabetic. +UNUSUAL_OK_IPA = ɪu̯ # Non-ASCII non-letters that OK_CHAR allows, as these characters are -# useful in commentary. These all came from Latin-1, and so are likely -# to be displayable even in editors with limited character sets. -UNUSUAL_OK_CHARSET= «°±»½¾× +# useful in commentary. +UNUSUAL_OK_CHARSET= $(UNUSUAL_OK_LATIN_1)$(UNUSUAL_OK_IPA) # OK_CHAR matches any character allowed in the distributed files. # This is the same as SAFE_CHAR, except that UNUSUAL_OK_CHARSET and @@ -735,7 +739,7 @@ check_character_set: $(ENCHILADA) $(MISC) $(SOURCES) $(WEB_PAGES) \ CONTRIBUTING LICENSE README \ version tzdata.zi && \ - ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_CHARSET='$(OK_CHAR)'*$$' \ + ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_'$(OK_CHAR)'*$$' \ Makefile && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA_TO_CHECK) backzone \ leapseconds yearistype.sh zone.tab && \ -- 2.17.1

1 0

[PATCH] Fix Asia/Shanghai 1940/9 DST transitions
by Paul Eggert Oct. 3, 2018

Oct. 3, 2018

* NEWS: Mention this. * asia (Shang): Switch to data from 2014 Li Yu paper. --- NEWS | 3 +++ asia | 34 +++++++++++++++++++++++++++------- 2 files changed, 30 insertions(+), 7 deletions(-) diff --git a/NEWS b/NEWS index a24d4b3..e217a50 100644 --- a/NEWS +++ b/NEWS @@ -42,6 +42,9 @@ Unreleased, experimental changes zic turns this into 01:00 on the day after September's second Saturday, which is the best that POSIX or C platforms can do. + Incorporate 1940-1949 Asia/Shanghai DST transitions from a 2014 + paper by Li Yu, replacing more-questionable data from Shanks. + Changes to time zone abbreviations Use "PST" and "PDT" for Philippine time. (Thanks to Paul Goyette.) diff --git a/asia b/asia index 365593a..a7b5c75 100644 --- a/asia +++ b/asia @@ -286,6 +286,29 @@ Zone Asia/Yangon 6:24:47 - LMT 1880 # or Rangoon # China +# From Paul Eggert (2018-10-02): +# The following comes from Table 1 of: +# Li Yu. Research on the daylight saving movement in 1940s Shanghai. +# Nanjing Journal of Social Sciences. 2014;(2):144-50. +# http://oversea.cnki.net/kns55/detail.aspx?dbname=CJFD2014&filename=NJSH2014… +# The table lists dates only; I am guessing 00:00 and 24:00 transition times. +# Also, the table lists the planned end of DST in 1949, but the corresponding +# zone line cuts this off on May 27, when the Communists took power. +# +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Shang 1940 only - Jun 1 0:00 1:00 D +Rule Shang 1940 only - Oct 12 24:00 0 S +Rule Shang 1941 only - Mar 15 0:00 1:00 D +Rule Shang 1941 only - Nov 1 24:00 0 S +Rule Shang 1942 only - Jan 31 0:00 1:00 D +Rule Shang 1945 only - Sep 1 24:00 0 S +Rule Shang 1946 only - May 15 0:00 1:00 D +Rule Shang 1946 only - Sep 30 24:00 0 S +Rule Shang 1947 only - Apr 15 0:00 1:00 D +Rule Shang 1947 only - Oct 31 24:00 0 S +Rule Shang 1948 1949 - May 1 0:00 1:00 D +Rule Shang 1948 1949 - Sep 30 24:00 0 S + # From Guy Harris: # People's Republic of China. Yes, they really have only one time zone. @@ -336,12 +359,9 @@ Zone Asia/Yangon 6:24:47 - LMT 1880 # or Rangoon # http://data.people.com.cn/pic/101p/1988/04/1988041201.jpg # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Shang 1940 only - Jun 3 0:00 1:00 D -Rule Shang 1940 1941 - Oct 1 0:00 0 S -Rule Shang 1941 only - Mar 16 0:00 1:00 D -Rule PRC 1986 only - May 4 2:00 1:00 D -Rule PRC 1986 1991 - Sep Sun>=11 2:00 0 S -Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D +Rule PRC 1986 only - May 4 2:00 1:00 D +Rule PRC 1986 1991 - Sep Sun>=11 2:00 0 S +Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D # From Anthony Fok (2001-12-20): # BTW, I did some research on-line and found some info regarding these five @@ -543,7 +563,7 @@ Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] # Beijing time, used throughout China; represented by Shanghai. Zone Asia/Shanghai 8:05:43 - LMT 1901 - 8:00 Shang C%sT 1949 + 8:00 Shang C%sT 1949 May 27 8:00 PRC C%sT # Xinjiang time, used by many in western China; represented by Ürümqi / Ürümchi # / Wulumuqi. (Please use Asia/Shanghai if you prefer Beijing time.) -- 2.17.1

2 3

Re： Inquiry to NICT about Japanese Summer time in 1948-1952.
by aya sekido Oct. 2, 2018

Oct. 2, 2018

Dear Nick, Thank you for your interest. We will respond to your inquiry. It is said that corresponding summer time was performed by instruction of the GHQ: General Headquarters (office of the Supreme Commander of the Allied Powers). We do not have detailed data about summer time then. According to the law of those days, the last day of summer time was made into 25 hours. What came after 12:59 p.m. of the last day was 00:00 a.m. of the next day. If you have any further questions, please let us know. Sincerely, Japan Standard Time Group Space-Time standards Laboratory Applied Electromagnetic Research Institute National Institute of Information and Communications Technology From: Phake Nick <c933103(a)gmail.com> Sent: Sunday, September 09, 2018 12:53 AM To: horonet(a)ml.nict.go.jp Cc: tz(a)iana.org Subject: [horonet 13333] Inquiry to NICT about Japanese Summer time in 1948-1952. To receivers of this email: Recently, I have read an article, which mentioned the history of Japanese Summer Time Implementation in the past at www.bengo4.com/internet/n_8461/ <http://www.bengo4.com/internet/n_8461/> . In the article, it was mentioned that the summer time (DST) end at 25 hours at the last day of the implementation period. Does that mean the clock would go up to the 25th hours back then and reach 24:59 before it continues toward 00:00 on the next day in standard time? If not then how did the clock switched from Summer Time back to Standard Time back then? Please use the "reply to all" function when replying to the message so that other receivers of the message can also hear answer on the matter. Sincerely, P.N.

6 13

Turkey decided to stay in +3
by Kıvanç Yazan Oct. 2, 2018

Oct. 2, 2018

Hi, Recently there was some confusion on whether Turkey was going back to +2. A decision is published today. It says all-year-long summer time (ie. UTC+3) is here to stay. No end date is specified. http://www.resmigazete.gov.tr/eskiler/2018/10/20181002-7.pdf Thanks, Kivanc Yazan

1 0

stale leap seconds file at IETF
by Hal Murray Sept. 29, 2018

Sept. 29, 2018

From: https://www.ietf.org/timezones/data/leap-seconds.list # Updated through IERS Bulletin C55 # File expires on: 28 December 2018 >From ftp://ftp.nist.gov/pub/time/leap-seconds.list # Updated through IERS Bulletin C56 # File expires on: 28 June 2019 What's the procedure for getting the IETF copy updated? Is the TZ community maintaining that file or is somebody at the IETF responsible for tracking NIST? -- These are my opinions. I hate spam.

2 1

When will physics make 32-bit signed leap-second counts obsolete?
by Paul Eggert Sept. 27, 2018

Sept. 27, 2018

A while ago I vaguely remember a prediction on this list of when the TZif file format will become obsolete because we have accumulated 2**31 total leap seconds if we continue to just add leap seconds as needed to keep UTC roughly in sync with TAI. To some extent this is just a playful prediction, as the format will undoubtedly become obsolete for other reasons long before then, but it's still fun to predict. Unfortunately I don't remember the details, and a quick Google search didn't find it. Does anyone else remember this? If not, I'll have to recalculate. The topic has just come up again on the tzdist-bis mailing list, which is why I'm thinking about it again. See <https://mailarchive.ietf.org/arch/msg/tzdist-bis/Q7OVmd60wydqcJahS3QRNHwtXHM>.

3 2

another solar-based time proposal (not)
by scs＠eskimo.com Sept. 27, 2018

Sept. 27, 2018

Many have probably seen this, but I'm surprised no one has mentioned Monday's xkcd: https://xkcd.com/2050/

3 2

Samoa DST
by Vishal Vineet Kumar Sept. 25, 2018

Sept. 25, 2018

Hi Paul/Team, Kindly advice if there is a java patch available for upcoming DST in Samoa on 30th September. https://www.mcil.gov.ws/wp-content/uploads/2018/09/public-notice-_Daylight-… Thanks, Vishal. ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

3 2