- tz - lists.iana.org

Brasil DST changes
by Dedeco Balaco Jan. 15, 2019

Jan. 15, 2019

Hello, last year, the DST automatic adjust for my recently installed system was wrong. It is a Debian 9 install. I adjusted it manually in the start and end or the period. It was not done according to what was defined by our State sometime before. Please note that it was not something done close to the change date. My friends and I looked around a bit, and we found that this change should have passed here somehow. Next year, I do not know how it will be. Who is responsible for this kind of information or update?

3 3

Notice Lead Time Tracking
by Brian Inglis Jan. 13, 2019

Jan. 13, 2019

Given some recent last minute end of year announcements, could I please suggest creating a new document to formally track metadata about every time change notice's lead time from 2019, as a basis for stats, info, distributor/vendor additions and enhancements, walls of shame, etc. as this has never yet been suggested AFAIR. I could see vendors like Apple, Google, Microsoft, Oracle dev groups adding columns to local copies to track their own responses, and using those to prod government officials to do better. The document could be a text file containing an HTML document with a table tracking: CC, announcement date[/time], effective date[/time], lead time in years-months-days [hours:minutes:seconds], tzdb release date[/time], tzdb release lead time +/- in years-months-days [hours:minutes:seconds], whether change affects STD, whether change affects DST, number of zones impacted, list of zones impacted, comments about missing details etc.; with dates[/times] in ISO formats (and perhaps also Unix format metadata attributes, allowing for JS HTML text display customization and sorting by third party users); times only specified when useful or notice is days, and times are available and accurate. If anyone has been doing this already, perhaps they could contribute their data; and anyone with interest and time could backfill data from mailing list posts. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.

5 6

Bulletin C 57: No leap second
by Kurt Roeckx Jan. 7, 2019

Jan. 7, 2019

Bulletin C 57 was sent today, and contained: NO leap second will be introduced at the end of June 2019. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37 s Kurt

1 0

[tz-announce] 2018i release of tz code and data available
by Paul Eggert Jan. 5, 2019

Jan. 5, 2019

The 2018i release of the tz code and data is available. It reflects the following change, which was circulated on the tz mailing list: Briefly: São Tomé and Príncipe switches from +01 to +00 on 2019-01-01. Changes to future timestamps Due to a change in government, São Tomé and Príncipe switches back from +01 to +00 on 2019-01-01 at 02:00. (Thanks to Vadim Nasardinov and Michael Deckers.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018i.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018i.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018i.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 388b0a55116099360a99cc9973d75ae6ec63d939 dated 2018-12-30 11:05:43 -0800 and tagged '2018i' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 1a3d53043f20b8252f7598f547d78e7294d9e0cf1fcdd2159354d9769f824c8c8a03cef9cbb7fa579345fdb41372335117d2ef782ecd9c107dd0526e59492d9d tzcode2018i.tar.gz 6afcacb377842190648ed26f01abcf3db37aa2e7c63d8c509c29b4bc0078b7ff2d4e5375291b9f53498215b9e2f04936bc6145e2f651ae0be6d8166d8d336f6a tzdata2018i.tar.gz 1bdab8ce6a2fc17e9b9d88baa7423b44254811255c82ccce0031725cd316b0ac14a696451f98c72559186270de54e8f467afdb788b2b501427f72fb4ea49d145 tzdb-2018i.tar.lz Here are the GPG checksums for the release files::n -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB4ACgkQ7ZfpDmKq fjTyAw/9EA6VzQop7iRV9GA3UQa6w4Rm/P6gJwF3gkz7hlAf39A6Tueulzzwk6F8 K2oIJQ/MlVGNw5yzkGHR2NTY1W3yhSJTKR5X4k2E5f/7vGnTf3USJx2Fs2Itolyn UoGSIRHWesr3tmbNUCT4LImfNyeW2MrW4q8yw1ZS7uZ34TMxDmJ+DTbomSPVhiMu yn3Y9KEqId6z3SsV8yjcDDd4J8B0zuh2WWrhSkPLXjCtGfHdiT9YaTo8y8Ayinwr xzofREicLEj1YX+3Hx0ErUCiWbtEzByOlkSX7CXfABI6EcaNaJzUsiHvrw7TTFoy u1rrJgarkrNj7YXX8Dj4PoAp4cIH4++AwNbZKfZp5PNRlzydKYX0APpuYUwmS5Qv yXqcvsOGHau/wkDb6ZPQwUwu5g7BmZQ42Yvp8tisoeGeCNnm3zu5cKyCMy2LRKyy dELRyxKEpOSOzjYqIl06yPGtQf4xgXh4r/zKCSS1bEBEpzTIV4BvoxB1R9x26hc1 IJwcuYEeU9NAq17Njcs5jyts4SnNfryxX8+RvwtJnxnmoTc1whaMHR8CMka11XI2 bJ1FlJCQr5dBA5M5cstLJZVkreoMp1bNLiVwCL+8cdAHWGXQ6SPUDuQYyUj+wKBp EX6dfVjrX/CYQVe65HnXiqxYJpDamGk2J4suSc4SG6EF8TVtQCw= =eLXg -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIyBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB8ACgkQ7ZfpDmKq fjTMog/3YJT5eFuwlijuTDxlt+VMTaAEaDaSUfzmQhaTDuHPKVDXxCaWq+tcO4J8 gzzecRj40Xc/jZId7MREq2S3uyUu7D6tJR7kRMw8BeTYVkhf+wX4Xmfh+6bVB9bO 34GNTSK9BXoieio68AkaCziVhBy6KynKhzUS4d1sqEDUxhS7r3ir6jTiU4UGAf54 PKWh2YKYITuYww4XnseG9rQsKbVKK4GUm/e7OmV3zf5pI9lhf/TQh1XZXKFbKK70 gDmFPUDAyuiFBCxkA7YsGolAnkscVmuF301brsNg+VKPy1qgMbxY/vF0lo/f7xRw dzi8+ek6/pKCIUmVRWCsg68wUDh1j3pAh9MLT8zhMtxOc42Kh+4b1BNq0x45zVbQ 693ufcf056654Y27bCexy1JbGBNEd6UUGUv/Ou9EGrl6nfrfMSmUneqmBEnl8NY+ 6/cge/JOr+rVbmEku+nuC9kLZx63lSy4BXJ8+vv4DgzE6/3906V30+w/oJUGaImx PjE9tjm6biIWdRi6bZRdFcg0mktBEyzJuAuurX0ZRgcaNkrhNd4zw2Q3yuKDcD67 aM5wUA4JVLX5v6P+s5j5Y+B+OY4sVk8fFzev8BJX+wRulqEmchVertypir17PUSr oqRUAww6oaYwenZNE+6dN0OWtpLDdBUv7+pesiYcaJRrXDCLAA== =ttI4 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGCEACgkQ7ZfpDmKq fjRrfA//ZeU5yiKc9WOW9kco9zXoBvlHgqpxO3qI3ESgUxslFAIpeVA/26JRbEc8 AJaEEEfmKFNFtO0Wev8WAhRT6qayaxlR30qWlhQl73F+F4xVmTuCojf02HlzUS5B QpReCDZecEMXp3SmEHrog3gMtGtT6dbofUbFjXoJtwm8OpjXzlY1LdAwO33eiOKH SKr7r7q4dm/3ZVhdFP2b/OPqiF/ezhywAoYqxIUdglroGyCGtlHECEDyYIHAHlwT /hwRk96a3/ghQiEyVbqREzwBMWydTbeo+MptCtgpA1p1vmVLxLhY/3SUaOdEBIqC mYhDuLMy9SKIVtkLBc537RnUBWyCfX3p9XZ90q2YqcpqzxX47+55IKmZ8MeWEvgU OvPUV6kYVtWCO/7bNVz4I0XaJdK/tA1vhNyk8jXaMW4duCgZZsCDn5uD3oQCKJE4 O+QZqf7k5pGWT3NWFln4vv6/mahAeoV0OxpHpn1qdA6+CAa/DVdU5ZTcaleNsTSy lAd0Zt2UBCb/rycnckgT87RrAtvjUUVq4onHSaTmtOdBYfMLr5BKtD+UClAcudvd jb15tHpErlXpZ/02Bn1yfynd5xFndGA1Rj3xIRCV31/EY+pxYl4i8ZNc9lWvtLa8 PV9bGewU6EsFohzm5/1CnJbT/gKYoFVoYkdQ7/Bc+mtNjYIAYxM= =ehq4 -----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/2018i/tzdata2018i-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2018i/tzdata2018i-rearguard.tar.… with the following SHA-512 and GPG checksums: 55ec0bc2504eddc72187c80c24c80ac7a2ec4c9e5b5a4cee583dcd2f97a648b35674e1eb2e390151e689f9d4eb237615d2f0f3c64b2209672e762f0bc4c580e2 tzdata2018i-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwpGB8ACgkQ7ZfpDmKq fjT/yw/9HUQnV+LGYkiQRE840qJ02XqH5K0l2R7n9OiUKsZnI+PEg5y23bUGd4+A gWwNAvC7629m+La8yiIRMO9fdNX3qHCHAXn7eUBH9nfJLcPML4t5i8kFT+NYvXwT JuauEAHDRqVQw6s0Sjeh3wsz/4Iq0c6AOuPqYC5Nnh8OgXZUsG8sNlJfB6x2Hbfe 85UimkXX+xSizN6gMxrP4Y5adoQaJRcCkvjZLm4TwGvMOTFQLNsERtl9KeiJOD3Z qEnt03Wx+kpOK2nIepe+ZgS2TtgK1uRntiu+L7MmRPmNriegCE+SCQVZhl5Kbm4a HHORTs/97B9ec6tiNreL0lg35Z/0vKA4KUdcpBGCaylGNvXNmz4TnHWHpdOWgueD 3O8E87edCTAUvQ8rAoEcqmg6CPrr2p/gfn+96w1EBfBqVJCjsZ/6KaDhbb6/LBAr oHd3TVtHMxpxrkxGXCyZwwpHEQtdnKeWPAyyc5kKd9LqUM1YQLQhQ44aN0SBeO8n spAFJLQm03GA+1aw1ETVrid474PMLTGKQj4iOg0XY/91E/L5p+Pf15ztMBo8asie lo07vW+o0ED3N0p60EXIdZxnokm/hPLo9yqbrCGpXE6wHcSFOgiK/Q5wOahrA/y0 LVI5yJt9Bc+hHLcQnwIPQei2P50ixVVDq8k2hTiM+2PN3iIcoGY= =fOhE -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

5 10

Timezone change for Asia/Qyzylorda
by Zhanbolat Raimbekov Jan. 3, 2019

Jan. 3, 2019

Hi, Starting 21 December 2018 00:00, Qyzylorda oblast, Kazakhstan (Asia/Qyzylorda) has moved back from +6 to +5. Link: http://adilet.zan.kz/rus/docs/P1800000817 -- Zhanbolat Raimbekov, Rochester Institute of Technology '12

9 15

[PROPOSED] Cite Shanks & Pottenger better
by Paul Eggert Dec. 30, 2018

Dec. 30, 2018

* tz-link.html: Provide library URLs for Shanks and Pottenger’s now out-of-print atlases, since their publisher no longer maintains web pages. Link to ANS on these atlases as sources for much of the older tz data. Use <abbr> a bit more often. --- tz-link.html | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/tz-link.html b/tz-link.html index 4f456ef..924227a 100644 --- a/tz-link.html +++ b/tz-link.html @@ -551,8 +551,8 @@ Java</a> contains a copy of a subset of a recent Java-specific format.</li> <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> +download, compile and use <code><abbr>tz</abbr></code> releases. +The Basic version is free.</li> <li><a href="http://veladg.com/velaterra.html">VelaTerra</a> is a macOS program. Its developers @@ -563,10 +563,16 @@ licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> <ul> <li><a href="https://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's out-of-print -time zone history atlases now published in <a +time zone history atlases +<a href="https://www.worldcat.org/oclc/468828649">for the US</a> and +<a href="https://www.worldcat.org/oclc/76950459">for the world</a>, +now published in <a href="https://astrocom.com/astrology-products/software/acs-atlas-software">software</a> form by <a href="https://astrocom.com">ACS-Starcrafts</a>. -These atlases are extensive but unreliable, as Shanks appears to have +Although these extensive atlases +<a href="https://astrologynewsservice.com/opinion/how-astrologers-contributed-to-the…">were +sources for much of the older <code><abbr>tz</abbr></code> data</a>, +they are unreliable as Shanks appears to have guessed many <abbr>UT</abbr> offsets and transitions. The atlases cite no sources and do not indicate which entries are guesswork.</li> <li><a href="https://en.wikipedia.org/wiki/HP-UX">HP-UX</a> has a database in @@ -856,14 +862,14 @@ href="https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html"><abbr title="International Earth Rotation and Reference Systems Service">IERS</abbr> Bulletins</a> contains official publications of the International Earth Rotation and Reference Systems Service, which decides when leap -seconds occur. The <code>tz</code> code and data support leap seconds +seconds occur. The <code><abbr>tz</abbr></code> code and data support leap seconds via an optional "<code>right</code>" configuration, as opposed to the default "<code>posix</code>" configuration.</li> <li><a href="https://developers.google.com/time/smear">Leap Smear</a> discusses how to gradually adjust <abbr>POSIX</abbr> clocks near a leap second so that they disagree with <abbr>UTC</abbr> by at most a half second, even though every <abbr>POSIX</abbr> minute has exactly -sixty seconds. This approach works with the default <code>tz</code> +sixty seconds. This approach works with the default <code><abbr>tz</abbr></code> "<code>posix</code>" configuration, is <a href="http://bk1.ntp.org/ntp-stable/README.leapsmear">supported</a> by the <abbr>NTP</abbr> reference implementation, and is used by major -- 2.17.1

1 0

São Tomé and Príncipe tz change (Jan 1, 2019)
by Vadim Nasardinov Dec. 30, 2018

Dec. 30, 2018

São Tomé and Príncipe is about to do the following on Jan 1, 2019: http://www.stp-press.st/2018/12/05/governo-jesus-ja-decidiu-repor-hora-lega… “O Conselho de Ministros, relativamente a hora legal de São Tomé e Príncipe, decidiu que a partir de 1 de Janeiro de 2019 será reposta a nossa hora secular” I don't read Portuguese but this sounds like a change. Old news? I don't see any discussion of this in https://mm.icann.org/pipermail/tz/2018-December/thread.html

4 4

[tz-announce] 2018h release of tz code and data available
by Paul Eggert Dec. 29, 2018

Dec. 29, 2018

The 2018h 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: Qyzylorda, Kazakhstan moved from +06 to +05 on 2018-12-21. New zone Asia/Qostanay because Qostanay, Kazakhstan didn't move. Metlakatla, Alaska observes PST this winter only. Guess Morocco will continue to adjust clocks around Ramadan. Add predictions for Iran from 2038 through 2090. Changes to future timestamps Guess that Morocco will continue to fall back just before and spring forward just after Ramadan, the practice since 2012. (Thanks to Maamar Abdelkader.) This means Morocco will observe negative DST during Ramadan in main and vanguard formats, and in rearguard format it stays in the +00 timezone and observes ordinary DST in all months other than Ramadan. As before, extend this guesswork to the year 2037. As a consequence, Morocco is scheduled to observe three DST transitions in some Gregorian years (e.g., 2033) due to the mismatch between the Gregorian and Islamic calendars. The table of exact transitions for Iranian DST has been extended. It formerly cut off before the year 2038 in a nod to 32-bit time_t. It now cuts off before 2091 as there is doubt about how the Persian calendar will treat 2091. This change predicts DST transitions in 2038-9, 2042-3, and 2046-7 to occur one day later than previously predicted. As before, post-cutoff transitions are approximated. Changes to past and future timestamps Qyzylorda (aka Kyzylorda) oblast in Kazakhstan moved from +06 to +05 on 2018-12-21. This is a zone split as Qostanay (aka Kostanay) did not switch, so create a zone Asia/Qostanay. Metlakatla moved from Alaska to Pacific standard time on 2018-11-04. It did not change clocks that day and remains on -08 this winter. (Thanks to Ryan Stanley.) It will revert to the usual Alaska rules next spring, so this change affects only timestamps from 2018-11-04 through 2019-03-10. Change to past timestamps Kwajalein's 1993-08-20 transition from -12 to +12 was at 24:00, not 00:00. I transcribed the time incorrectly from Shanks. (Thanks to Phake Nick.) Nauru's 1979 transition was on 02-10 at 02:00, not 05-01 at 00:00. (Thanks to Phake Nick.) Guam observed DST irregularly from 1959 through 1977. (Thanks to Phake Nick.) Hong Kong observed DST in 1941 starting 06-15 (not 04-01), then on 10-01 changed standard time to +08:30 (not +08). Its transition back to +08 after WWII was on 1945-09-15, not the previous day. Its 1904-10-30 change took effect at 01:00 +08 (not 00:00 LMT). (Thanks to Phake Nick, Steve Allen, and Joseph Myers.) Also, its 1952 fallback was on 11-02 (not 10-25). This release contains many changes to timestamps before 1946 due to Japanese possession or occupation of Pacific/Chuuk, Pacific/Guam, Pacific/Kosrae, Pacific/Kwajalein, Pacific/Majuro, Pacific/Nauru, Pacific/Palau, and Pacific/Pohnpei. (Thanks to Phake Nick.) Assume that the Spanish East Indies was like the Philippines and observed American time until the end of 1844. This affects Pacific/Chuuk, Pacific/Kosrae, Pacific/Palau, and Pacific/Pohnpei. Changes to past tm_isdst flags For the recent Morocco change, the tm_isdst flag should be 1 from 2018-10-27 00:00 to 2018-10-28 03:00. (Thanks to Michael Deckers.) Give a URL to the official decree. (Thanks to Matt Johnson.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018h.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018h.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018h.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 7db91b70ae4ce85c7520960840fc957541a3bdb0 dated 2018-12-23 17:59:32 -0800 and tagged '2018h' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: e30ee77432a07a4f206f7a494bd3b4ed16805017d9907fa42bfc8b952332a3c63e2c344b99ef6b32cae70b0ba25c2068b69f65afec3378f9ce56194d85df1ef8 tzcode2018h.tar.gz 2c72fc2737b896f60c96cd2df80ede19c0fa80c4cd2fac350d13c673e851aac54c6cc7c8a865edb3f325fc0139b850b4b98a29d97967b643bbfaa7e8fa9b4937 tzdata2018h.tar.gz 5c64b894033d81a82d11177b991dbe93b5ab596453cf7c0f29dcab527c5d061dd56e03460091f938d9685d200c4c79bf082dc557eaf7b8ab370dfad9e43fe4e1 tzdb-2018h.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwgPpIACgkQ7ZfpDmKq fjTNyRAAlGlcaHLrGaiGgr8sKAI3Hd53zu53BUhTJjS8FO9WF2OxgDKkj0Yqrzuo CHz3eUuIIYJ2X7BLuCAKY842K2je5goS20jqEirlbEhg1Pd0uU/8FtC4L80l68y8 8LxKEMcYY7Ec9tTraZYNIKmFxL3s9v1vXwiF94FbiPftNALNUnYS2SvvBaVybo66 Tr1DUHz00qRDzZpi9+90FllpOcMOU4PHsds/QpsGd3Q5d7lnQpUCFNN3pxORN4/T LxCJVyBjxJ5zl+G1FVxVjJL1Hrh3VpQkV3MyplmDG9eBwOXBbwLITqvL66i1slpX o9rN0cSNlte1yoxZwcvWKV+2mDGeGJ2P4Hbzq11ZNZ+ZhKZMdu6mMd48hhcCCQqy 5BkIPLEI++8IGZUyoIWEa/wW2djmym1p5a1jUxmI2L/LfwztVnZz+qtPB0khFP8a lqIDXRSXv/ScGpL7TWaL7Rmc5V755/0lGy6s44pCYWS9SBhW29VRFsEkMRl8yAKM R/cRkWbiCvDvgDiZwdtQvCdKPB+HBebIMnyJb7IDKKYpqYRkdfpuXp2lq8xRtfoZ OhZKPYG8D9LC9ovFiRhsdYUde6Oou1DYUPayXZ8/zVXTVnswMaVh4cIoxU9pecUY hYqyE3iwCc0YpWTU47DzruY/sXSmaITxFPF0c24DbQkAhpkRKUk= =NHCF -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwgPpIACgkQ7ZfpDmKq fjT95BAAifCqZHNjQ+Rm8nG3PXu9+FYuqn8+ezIH5vjhcfdQepYDsC5q91+Echx3 2OQpkOB4sjBiHSeeYzu4j6ULm8bvMj+FNGVQz+LXR6AUfnMwGhLM5pyGtHo3VJDh uSUfyzLb505FxT54NyINlr2gPuV5CSP98IQQRAqzjUIxRRC78GDXA+brOjObB/d3 A0apTx0IKu/KiepbSQ2wetM9d92Brb366iPnp1aZQKuiuC4k2nGSC5zo3Jr4HLzA CYL6YVTQuqc1UMyhqBy5yJJExsmheo3Uuz2Vh6bi6FYFNxNiOMLfIfgVZyeNBAk/ 0I9Y3wWh65d4+GJwyOEdNACKqWBfWfHgOwGtheCXBMM1DDypIh7+GQsKo9zOs0n6 Kn7byx4/YMLpqPpd3J7PF5cWJtocVJUivi9RTe7n2zRAoqCT1+vM6YcXsdwbPn1g yI/iBvjvzo10k5fU2dtkRjyKO97kn+KXALVYEnsaUsAHtO3KlppSDYtsxZo37k3B y7ZWmfrFkSLI5U5xKszziLYF362FnEeRKVzNOPOGjs2kJpiu/alGpdxHJKDAtpms paszof0NglEzO+jx9OOcxNHZOGjWRKRxv5BSZw1io8q87xV+eyiGR38zFCLnG/9L udZRijZ5tp7JlxJ6XrqUKPrwDwnlPGCO5G+W2sVsQyEQYKiZZOo= =J8dK -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwgPpQACgkQ7ZfpDmKq fjRaOhAAphyNU0lclXv7YaLXm9SusHp8ElpMN/Okh2BK5dwSfHtECVow5hzKccXA 8TC9srW5DDAUEa08Qv20FNODYTk5ukpphk2IDiUMrjzy+99gkzPd5e9sBC8PHsUU HoiFMIHvsge0WhZMpNalrrdO8tjkRRL4sPui+pvO87cNGNOGJruNUA7BHh/tjugr EP2sDBsB+0tfpDAVzKnf3bvS/ZT/vS4imHRZ+TH5szRgSHWrZYt1IH26b4TmRr1y xfeUS2UsfgiEtTt8/CKwChGHh/ZB+Rp+P7iWQjG15fLrtd7+Of7thRi2BxKsCT1a EXRaBfRkn1HSeYL+a5qSGNrZX4ZKzfWuRlJWCZhoogyZ1tyd2XVnJ5XneKwMaAKH bqdo+wscYB7YwGZXL3LX7tXJzggkXjxljggUHs0eotsLjfxaHVr/tcK8nuz8DNVK gTEmczpQ8ygsycVvkH2Cseh7ETMLjazTD+NTh69jLWCG1At9kGNwoekeJb+Rf7we ErDGPOE0+rp3AXQAxnu8FaWBBwCfqsvH8cls5/v3jBwtN75GM0b8Ui+HfleejTS1 SyoQsQMqVdvtXuZG/qM+FQyIXAkZ+WR+36FotL55GPT58hZhBJL+WlgyL6B30HUI VNBAfdkOdgwN30D20guM68JRGs5dqMr+gg+sajOPgMnl2xk7F30= =Lqgu -----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/2018h/tzdata2018h-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2018h/tzdata2018h-rearguard.tar.… with the following SHA-512 and GPG checksums: 73ed819507ed966ea962a6adb5fbaeff4f416036573757b893d29f7c62f5c9b04c5cebea7e52cd0f502cd49195499719ca76f57e9883bb4de6dadeb87b51ca71 tzdata2018h-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAlwgPpMACgkQ7ZfpDmKq fjRcUw//UnGM+2HY12mtu6AJ2aYb1PjzUv0X6FADua7YDOyXjz5i0sXXi7D2EPa0 qeZuk4x0Zr2EN8vt3Xy9jHuhpLr8bAJn8cwb71sNm+tSdDvKLoJJcokj7QKjBWr9 MTprLgI0guOhOdinSFFnHaumPtXzhOjrYJiy40Qw4RMZH1sTZhPWrSK3kZlpJj+t zGYbskaJtXB1LhlQbUtgepxyV5AaJfz4owYIbYh+Uv0gGqDzJc94BCVxM89LN52l CCHzt3zrsMicBle4QhyRo1qk6D4DDGVq2+AXLMyq8oMQvNvtzFpw34CbsYLaNL9X 3kdCqV723lbTwpqKEcivRhCCc3m2i/0rt1X1nkReXdzior3AJpAtG48pcb/F3/l4 Hc2Af8uohIhYBpw0Tm+x6YL2u1+ZR52rJtzt5UVcWV3ToyJJw1tTCijxxEHd/xoh 6xhtvYVPKkKabQqHUQnp0YKqV6DF83pMeQ4MLtSp7LPrNbxL9y5WvjAMhjzeQAB9 8qtDUQ9tPlSgMvs7EO7LCfUuPji5pPXoWn4caYn3KkFQPYSS0FYTv+RvBlZVjaAJ 84KTx87fD6ren0/XEyIYhtN30TxNng/KODFcmM4KM2+Jk5eVKktrY7N3uZZBEpQ8 H9i/8giTDGPE/hlI3LN1E15FPuC6o0PGYaDUT8Mkk4CjazJEPA8= =9v4P -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Time zone offset changed in Qyzylorda, Kazakhstan
by Askar Timirgazin Dec. 29, 2018

Dec. 29, 2018

Hello there, please consider that according to https://legalacts.egov.kz/npa/view?id=2000931 time offset for zone Asia/Qyzylorda from 21 Dec 2018 must be set to UTC+5 instead of UTC+6 -- Best regards, Askar Timirgazin

2 1

Update with rearguard not refreshed version of tzdata info
by Joel da Rosa Dec. 28, 2018

Dec. 28, 2018

Hello! I executed the steps: 1 - java -jar tzupdater.jar -f -l https://web.cs.ucla.edu/~eggert/tz/release/2018g/tzdata2018g-rearguard.tar.… 2 - java -jar tzupdater.jar -V Result of step 2: "tzupdater version 2.2.0-b01 JRE tzdata version: tzdata2018g tzupdater tool would update with tzdata version: tzdata2018g" It's correct? My environment: Linux Ubuntu 64 java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) -- Att, JOEL DA ROSA

2 1

America/Mexico_City incorrect DST end time for 2018.
by demxic Dec. 28, 2018

Dec. 28, 2018

I would like to draw your attention to the fact that Mexico's City Daylight time ended on October 28 2018 03:00 AM local time. That is the exact moment when clocks moved backward to 02:00 AM. Somehow your database marks DST end at 02:00 AM moving clocks backward to 01:00 AM. Please note that this is incorrect. Is it possible to correct for this? -- *My country is the world and my religion is to do good. *Thomas Paine

3 6

1932 IAU Commission on Time: abolish Summer Time
by Steve Allen Dec. 28, 2018

Dec. 28, 2018

Bulletin Horaire, vol. 4, no. 70 has a synopsis of time-related activities at the 4th General Assembly of the IAU at Cambridge Massachusetts in 1932. Page 399 has the end of the Commission 31 (Time) meeting where Kiyofuso Sotome, director of Tokyo Astronomical Observatory, proposed two items not on the printed agenda. Item 2 was "Immediate abolition of the Summer Time." The commission deemed that it could not take any action on this. http://adsbit.harvard.edu//full/1932BuBIH...4..391./0000427.000.html The same text is found in Transactions of the IAU vol. 4 page 253. -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

1 0

[PATCH 1/2] * tz-art.html: Add a few IMDb URLs and standardize format.
by Paul Eggert Dec. 24, 2018

Dec. 24, 2018

--- tz-art.html | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/tz-art.html b/tz-art.html index c98e9c4..edddae0 100644 --- a/tz-art.html +++ b/tz-art.html @@ -36,19 +36,15 @@ there is a reference to British Double Summer Time. The time does not play a large part in the plot; it's just a passing reference to the time when one of the characters was supposed to have died (but didn't). -The IMDb page is at -<a href="http://us.imdb.com/title/tt0038733/"> -http://us.imdb.com/title/tt0038733/ -</a>. (Dave Cantor) +(<a href="http://us.imdb.com/title/tt0038733/">IMDb entry.</a>) +(Dave Cantor) <li> The 1953 railway comedy movie The Titfield Thunderbolt includes a play on words on British Double Summer Time. Valentine's wife wants him to leave the pub and asks him, "Do you know what time it is?" And he, happy where he is, replies: "Yes, my love. Summer double time." -IMDb page: -<a href="http://us.imdb.com/title/tt0046436/"> -http://us.imdb.com/title/tt0046436/ -</a>. (Mark Brader, 2009-10-02) +(<a href="http://us.imdb.com/title/tt0046436/">IMDb entry.</a>) +(Mark Brader, 2009-10-02) </li> <li> The premise of the 1999 caper movie Entrapment involves computers @@ -60,10 +56,8 @@ a gigantic computerized theft. To achieve this, at one location the crooks interfere with the microwave system supplying time signals to the computer, advancing the time by 0.1 second each minute over the last hour of 1999. (So this movie teaches us that 0.1 × 60 = 10.) -IMDb page: -<a href="http://us.imdb.com/title/tt0137494/"> -http://us.imdb.com/title/tt0137494/ -</a>. (Mark Brader, 2009-10-02) +(<a href="http://us.imdb.com/title/tt0137494/">IMDb entry.</a>) +(Mark Brader, 2009-10-02) </li> <li> One mustn't forget the @@ -79,12 +73,15 @@ Cube," first aired 1958-02-24, had Superman convincing the controllers of the Arlington Time Signal to broadcast ahead of actual time; doing so got a crook trying to be declared dead to emerge a bit too early from the titular enclosure. +(<a href="https://www.imdb.com/title/tt0506628/">IMDb entry</a>.) </li> <li> -"The Chimes of Big Ben", The Prisoner, episode 2, ITC, 1967-10-06. +"<a href="https://en.wikipedia.org/wiki/The_Chimes_of_Big_Ben">The Chimes +of Big Ben</a>", The Prisoner, episode 2, ITC, 1967-10-06. Our protagonist tumbles to the fraudulent nature of a Poland-to-England escape upon hearing "Big Ben" chiming on Polish local time. +(<a href="https://www.imdb.com/title/tt0679185/">IMDb entry.</a>) </li> <li> "The Susie", Seinfeld, season 8, episode 15, NBC, 1997-02-13. @@ -196,7 +193,9 @@ Nick Enright, Daylight Saving, 1989. A fast-paced comedy about love and loneliness as the clocks turn back. </li> <li> -Umberto Eco, The Island of the Day Before +Umberto Eco, +<a href="https://en.wikipedia.org/wiki/The_Island_of_the_Day_Before">The +Island of the Day Before</a> (L'isola del giorno prima), 1994. "...the story of a 17th century Italian nobleman trapped near an island on the International Date Line. Time and time zones play an integral -- 2.19.2

1 1

Time zone Asia/Qyzylorda
by Alexander Konzurovski Dec. 20, 2018

Dec. 20, 2018

Dear maintainers of the Time Zone Database! I would like to inform you that Qyzyolrda Region (Asia/Qyzylorda) is changing its time zone from UTC+6 to UTC+5 effective December 21st, 2018. The legal document is located here: http://adilet.zan.kz/rus/docs/P1800000817 (russian language). Accordingly resolution the time zone must be changed on December 20 18:00 UTC. -- Alexander Konzurovski

3 5

Time zones in the news
by Arthur David Olson Dec. 20, 2018

Dec. 20, 2018

"Time Lords: a history of authoritarian time changes" by Elena Goukassian in Lapham's Quarterly. (Thanks to Nikita S--@singareddynm on Twitter--for the pointer.) https://www.laphamsquarterly.org/roundtable/time-lords ---ado

2 1

[PROPOSED] Metlakatla goes back to Alaska time next year
by Paul Eggert Dec. 17, 2018

Dec. 17, 2018

* NEWS: Mention this. * northamerica (America/Metlakatla): Go back to Alaska time next year at the first opportunity. --- NEWS | 6 ++++-- northamerica | 8 +++++++- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index abc6094..667cec7 100644 --- a/NEWS +++ b/NEWS @@ -25,8 +25,10 @@ Unreleased, experimental changes Changes to past and future timestamps Metlakatla moved from Alaska to Pacific standard time on 2018-11-04. - It did not change clocks that day and is now on -08 indefinitely, - reverting to its form before fall 2015. (Thanks to Ryan Stanley.) + It did not change clocks that day and remains on -08 this winter. + (Thanks to Ryan Stanley.) It will revert to the usual Alaska + rules next spring, so this change affects only timestamps + from 2018-11-04 through 2019-03-10. Change to past timestamps diff --git a/northamerica b/northamerica index 17597e2..faaf979 100644 --- a/northamerica +++ b/northamerica @@ -605,6 +605,11 @@ Zone America/Los_Angeles -7:52:58 - LMT 1883 Nov 18 12:07:02 # They will be gmtoff=-28800 year-round. # https://www.facebook.com/141055983004923/photos/pb.141055983004923.-2207520… +# From Paul Eggert (2018-12-16): +# In a 2018-12-11 special election, Metlakatla voted to go back to +# Alaska time (including daylight saving time) starting next year. +# https://www.krbd.org/2018/12/12/metlakatla-to-follow-alaska-standard-time-a… + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Juneau 15:02:19 - LMT 1867 Oct 19 15:33:32 -8:57:41 - LMT 1900 Aug 20 12:00 @@ -632,7 +637,8 @@ Zone America/Metlakatla 15:13:42 - LMT 1867 Oct 19 15:44:55 -8:00 US P%sT 1983 Oct 30 2:00 -8:00 - PST 2015 Nov 1 2:00 -9:00 US AK%sT 2018 Nov 4 2:00 - -8:00 - PST + -8:00 - PST 2019 Mar Sun>=8 3:00 + -9:00 US AK%sT Zone America/Yakutat 14:41:05 - LMT 1867 Oct 19 15:12:18 -9:18:55 - LMT 1900 Aug 20 12:00 -9:00 - YST 1942 -- 2.17.1

1 0

FW: [Bug time/23976] trunk/timezone/zdump.c:811: missing call to va_end ?
by David Binderman Dec. 14, 2018

Dec. 14, 2018

Hello there, Forwarded bug report ________________________________________ https://sourceware.org/bugzilla/show_bug.cgi?id=23976 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- This code is imported from external sources and not modified locally in glibc. Please report your concern to tz(a)iana.org, not here. -- You are receiving this mail because: You reported the bug.

3 3

Error in the Time Zone Database
by serhii.demediuk＠cyberpolice.gov.ua Dec. 7, 2018

Dec. 7, 2018

Cyberpolice Department of National Police of Ukraine presents its compliments and wish to inform your organization regarding the following recent change. Information posted at https://www.iana.org/time-zones suggests that the latest release of the time zone database (version from 10/26/2018), states that Crimea (Ukrainian Autonomous Republic of Crimea) belongs to the time zone "MSK" and is marked with the country code "RU". This information was found in the archive, which contains the full description of the data, codes and applications, and is located at https://data.iana.org/time-zones/releases/tzdb-2018g.tar.lz. Information about the code of Crimea was found in the file "zone.tab" within the specified archive. We consider it necessary to draw your attention to the fact that Crimea is a temporarily occupied part of Ukraine. This fact is generally acknowledged by the international community, which is confirmed by a number of international legal document, including UN General Assembly resolution. Thus, by referring Crimea with the country code "RU", your organization actually accepts and supports the aggressive actions of the Russian Federation who’s armed forces annexed this part of Ukraine. Such recognition may be considered as a criminal offense by the Ukrainian criminal law and we will be obliged to start formal criminal proceedings as it is stipulated in article 110 of the Criminal Code of Ukraine "Infringement of territorial integrity of Ukraine". As you probably know, the aggression of the Russian Federation against Ukraine is still ongoing and any ambiguous decision by countries or international organizations is used by the authorities of the aggressor country to justify their actions. We would like to add that there are Ukrainian citizens still living in Crimea and adhere to the legislation of Ukraine. For their beliefs, such citizens are persecuted by the authorities of Russian Federation. International support for Ukrainian citizens in their aspiration to renew the territorial integrity of Ukraine is extremely important, and in this case your organization can play a positive role. We understand the apolitical status of your organization and respect the existing rules for determining of the actual time zone, but considering the international legal status of Crimea, which is part of Ukraine, we propose to correct this mistake and to change the current version of the time zone database in order to determine that the country code of Crimea is «UA». Best regards, Head of the Cyberpolice Department of the National Police of Ukraine Serhii Demediuk tel.: +380443743738 e-mail: serhii.demediuk(a)cyberpolice.gov.ua Ukraine, Kyiv

3 3

posix for asia/tehran is wrong
by Mark Nov. 30, 2018

Nov. 30, 2018

I've been adding DST time zone to espurna (https://github.com/xoseperez/espurna/pull/1295) All dst entries but asia/tehran, use Mm.n.d format to specify dst dates. The Tehran use 'Jn': "Asia/Tehran","<+0330>-3:30<+0430>,J80/0,J264/0" When I implement this 'J' format, I came out a day short. From https://en.wikipedia.org/wiki/Iran_Standard_Time: The Iranian DST starts on March 22 and ends on September 22 each year with the exception of leapyears in which the DST starts and ends one day prior. Year DST Start Date and Time DST End Date and Time *2014* Sat, Mar 22, 0:00 AM Mon, Sep 22, 0:00 AM *2015* Sun, Mar 22, 0:00 AM Tue, Sep 22, 0:00 AM *2016* Mon, Mar 21, 0:00 AM Wed, Sep 21, 0:00 AM *2017* Wed, Mar 22, 0:00 AM Fri, Sep 22, 0:00 AM *2018* Thu, Mar 22, 0:00 AM Sat, Sep 22, 0:00 AM This mean Tehran should be "Asia/Tehran","<+0330>-3:30<+0430>,80/0,264/0". The 'n' format, which counts 29 Feb, and starts count from 0, so would not come up a day short on non-leap years.

4 5

[PROPOSED] * northamerica: Herbert Copeland stops time.
by Paul Eggert Nov. 30, 2018

Nov. 30, 2018

--- northamerica | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/northamerica b/northamerica index e590a30..17597e2 100644 --- a/northamerica +++ b/northamerica @@ -792,6 +792,22 @@ Zone America/Boise -7:44:49 - LMT 1883 Nov 18 12:15:11 # For a map of Indiana's time zone regions, see: # https://en.wikipedia.org/wiki/Time_in_Indiana # +# From Paul Eggert (2018-11-30): +# A brief but entertaining history of time in Indiana describes a 1949 debate +# in the Indiana House where city legislators (who favored "fast time") +# tussled with farm legislators (who didn't) over a bill to outlaw DST: +# "Lacking enough votes, the city faction tries to filibuster until time runs +# out on the session at midnight, but rural champion Rep. Herbert Copeland, +# R-Madison, leans over the gallery railing and forces the official clock +# back to 9 p.m., breaking it in the process. The clock sticks on 9 as the +# debate rages on into the night. The filibuster finally dies out and the +# bill passes, while outside the chamber, clocks read 3:30 a.m. In the end, +# it doesn't matter which side won. The law has no enforcement powers and +# is simply ignored by fast-time communities." +# How Indiana went from 'God's time' to split zones and daylight-saving. +# Indianapolis Star. 2018-11-27 14:58 -05. +# https://www.indystar.com/story/news/politics/2018/11/27/indianapolis-indian… +# # From Paul Eggert (2007-08-17): # Since 1970, most of Indiana has been like America/Indiana/Indianapolis, # with the following exceptions: -- 2.17.1

1 0

Timezone history for some Pacific Islands.
by Phake Nick Nov. 30, 2018

Nov. 30, 2018

>From a Japanese wiki site https://wiki.suikawiki.org/n/南洋群島の標準時 there are some time change history about Pacific Islands that are not included in the tz database. Mainly, the history of time used in those islands during, before and after Japanese administration, and also DST used in Guam during 1960s and 1970s. For "Southern Islands" (modern region of Mariana + Palau + Federation of Micronesia + Marshall Islands): * A 1906 Japanese magazine shown the Caroline Islands and Mariana Islands who was occupied by Germany at the time as GMT+10, together with the like of German New Guinea. However there is a marking saying it have not been implemented (yet). No further information after that were found. * Japan invaded those islands in 1914, and records shows that they were instructed to use JST at the time * 1915 January telecommunication record on the Jaluit Atoll shows they use the meridian of 170E as standard time (GMT+11:20), which is similar to the longitude of the atoll. * 1915 February record say the 170E standard time is to be used until February 9 noon, and after February 9 noon they are to use JST. * However these are time used within the Japanese Military at the time and probably does not reflect the time used by local resident at the time (that is if they keep their own time back then) * In January 1919 the occupying force issued a command that split the area into three different timezone with meridian of 135E, 150E, 165E (JST+0, +1, +2), and the command was to become effective from February 1 of the same year. Despite the target of the command is still only for the occupying force itself, further publication have described the time as the standard time for the occupied area and thus it can probably be seen as such. ** Area that use meridian of 135E: Palau and Yap civil administration area (Southern Islands Western Standard Time) ** Area that use meridian of 150E: Truk(Chuuk) and Saipan civil administration area (Southern Islands Central Standard Time) ** Area that use meridian of 165E: Ponape(Pohnpei) and Jaluit civil administration area. (Southern Islands Eastern Standard Time) ** In the next few years Japanese occupation of those islands have been formalized via League of Nation Mandate (South Pacific Mandate) and formal governance structure have been established, these district [become subprefectures] and timezone classification have been inherited as standard time of the area. ** Saipan subprefecture include Mariana islands (exclude Guam which was occupied by America at the time), Palau and Yap subprefecture rule the Western Caroline Islands with 137E longitude as border, Truk and Ponape subprefecture rule the Eastern Caroline Islands with 154E as border, Ponape subprefecture also rule part of Marshall Islands to the west of 164E starting from (1918?) and Jalnuit subprefecture rule the rest of the Marshall Islands. * And then in year 1937, an announcement was made to change the time in the area into 2 timezones: ** Area that use meridian of 135E: area administered by Palau, Yap and Saipan subprefecture (Southern Islands Western Standard Time) ** Area that use meridian of 150E: area administered by Truk(Chuuk), Ponape(Pohnpei) and Jaluit subprefecture (Southern Islands Eastern Standard Time) * Another announcement issued in 1941 say that on April 1 that year, standard time of the Southern Islands would be changed to use the meridian of 135E (GMT+9), and thus abolishing timezone different within the area. * Then Pacific theater of WWII started and Japan slowly lose control on the island. The webpage I linked above contain no information during this period of time. Guam Island was briefly annexed by Japan during this period of time [year 1941-1944], however there are no detailed information about what time it use during that period. It would probably be reasonable to assume Guam use GMT+9 during that period of time like the surrounding area. * After the end of WWII, in 1946 February, a document written by the (former?) Japanese military personnel describe there are 3 hours time different between Caroline islands time/Wake island time and the Chungking time, which would mean the time being used there at the time was GMT+10. * After that, the area become Trust Territories of the Pacific Islands under American administration from year 1947. The site listed some American/International books/maps/publications about time used in those area during this period of time but they doesn't seems to be reliable information so it would be the best if someone know where can more reliable information can be found. * The site also pointed out that currently tzdata say Pacific/Kwajalein switched from GMT+11 to GMT-12 in 1969 October without explanation, however an 1993 article from NYT say it synchorized its day with US mainland about 40 years ago and thus the switch should occur at around 1950s instead. * Also, the NYT article linked in that website say the jump from GMT-12 to GMT+12 in year 1993 skipped Saturday that day, however the comment in tz database from that year say it skipped Friday. That seems to be an inconsistency that should be investigated, and the comment should probably be annotated accordingly if the comment was not accurate ANd then additional note for Bonin Islands: While not part of the Southern Islands, in the period of time during 1952-1968, Bonin Islands were placed under American administration. It would probably be worth investigating whether they're following the Japanese time or the Mariana time or some other time standard at the time. And then for Guam: * Currently tz database say Guam stopped using local mean time at 1901 but a 1902 earthquake report on Guam seems to be using LMT in the report when compares to the time the earthquake recorded on the Philippines (the site note that it take times for earthquake wave to transmit and thus the time different between records in different place would not be identical to the time different) ** The site say Shanks used 1901 end date for LMT time for a number of places around the world, probably using them as placeholder. Maybe those 1901 end date should be nuked from tz database? * A Japanese magazine in 1906 say Guam's time is "1.5 hours earlier than Japan" and "use 145 degree E meridian" which are contradictory to each other as 145E meridian mean GMT+9:40 and that is not 1.5 hours earlier than Japan. * And then there are some different records about Guam used GMT+9:30 at the time but each of those documents seems to give different transition time for when they give up :30 time different and move to GMT+10. But it most likely occurred before 1927 as a map published by US Navy that year shows Guam as using GMT+10, which appears to be credible as Guam was under US Military administration at the time. * As mentioned above, Guam was invaded by Japan during year 1941-1944. It's unclear about did they shifted the clock to match the surrounding islands during this period of time. * Then in year 1959 there's a daylight saving time act passed for Guam. There is a table on the site that include list an link to time and order for implementation and cancellation of DST at Guam but the implementation time seems to be all over the place according to the list. The last time the DST was implemented in Guam according to the table seems to be 1977 although I am not sure about the completeness of the table. If so then maybe a new zone for CNI would need to be created as it's after 1970 and the DST should be applicable to Guam only?

3 3

Question about the UNTIL fields
by Marcos Passos Nov. 29, 2018

Nov. 29, 2018

Hello everyone, I'm working on a TZDB parser for a PHP project and reading the zic8.txt I came across with the following information: The month, day, and time of day have the same format as the IN, ON, and AT > fields of a rule However, I could not find any Zone line in the latest version of the TZDB containing relative dates, such as "lastSun" or "sun>=5", but only absolute dates. Is this a mistake in the documentation or are relative dates actually supported on those lines but have never been used? - Marcos

3 6

Stop
by The OneCloud Nov. 29, 2018

Nov. 29, 2018

Stop

2 1

query regarding issue will updating open JDK timezone info with tzdata2018g
by Dhanusha, Pb (Nokia - IN/Bangalore) Nov. 27, 2018

Nov. 27, 2018

Hi, We are facing issues while updating open JDK timezone with tzdata2018g with the below error. #/usr/bin/java -jar /root/tzupdater.jar -l file:/root/tzdata2018g.tar.gz Failed: java.lang.Exception: Failed while parsing file '/tmp/tz.tmp/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' java.lang.Exception: Failed while parsing file '/tmp/tz.tmp/asia' on line 1655 'Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S' at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:377) at tools.tzdb.TzdbZoneRulesCompiler.compile(TzdbZoneRulesCompiler.java:191) at tools.tzdb.TzdbZoneRulesCompiler.<init>(TzdbZoneRulesCompiler.java:307) at com.sun.tools.tzupdater.ExternalModule.compileToJSRBinary(ExternalModule.java:212) at com.sun.tools.tzupdater.TimezoneUpdater.run(TimezoneUpdater.java:226) at com.sun.tools.tzupdater.TimezoneUpdater.main(TimezoneUpdater.java:780) Caused by: tools.tzdb.DateTimeException: Invalid value for SecondOfDay value: 90000 at tools.tzdb.ChronoField.checkValidValue(ChronoField.java:173) at tools.tzdb.LocalTime.ofSecondOfDay(LocalTime.java:210) at tools.tzdb.TzdbZoneRulesCompiler.parseMonthDayTime(TzdbZoneRulesCompiler.java:475) at tools.tzdb.TzdbZoneRulesCompiler.parseRuleLine(TzdbZoneRulesCompiler.java:399) at tools.tzdb.TzdbZoneRulesCompiler.parseFile(TzdbZoneRulesCompiler.java:354) ... 5 more Could you please help us with this. Regards, Dhanusha

4 4

Help - Morocco timezone wrong since 28 Oct 2018
by Heidi Hendry Nov. 25, 2018

Nov. 25, 2018

Hi, Based on this version of the TZ values: http://twiki.org/cgi-bin/xtra/tzdate?tz=Africa/Casablanca the Africa/Casablanca timezone is wrong. Morocco abruptly changed the timezone (see this BBC article: https://www.bbc.com/news/world-africa-45995634 ) and Android phones and other UX distributions appear to be wrong every since. Africa/Casablanca is +1 GMT now, and there is NO daylight savings any more. Please, please could you fix this in TZ so that it distributes out for other updates? Regards Heidi Hendry

2 1