- tz - lists.iana.org

Indian Continent
by Bharat Adur Oct. 12, 2020

Oct. 12, 2020

Dear Sir Indian is very large country with over 130 billion population with 28 states and over fifty major cities including Mumbai. However in your catalog list for India in tz list , we have only as Asia/Calcutta. Can you kindly introduce in python in tz it should locate the place and th local time, with best regards Bharat Adur

2 1

Bug in tzdata version (2020b)
by westmail24＠yandex.com Oct. 9, 2020

Oct. 9, 2020

Hello, After compiling now I see that tzdata version is "8675a", not is "2020b". It's your bug or bug of "my" program now? (Screenshot in attachment.) Please check/fix it. Thank you. -- Andrew Oct. 9, 2020

4 3

Fiji Day Light Saving
by Raymond Kumar Oct. 8, 2020

Oct. 8, 2020

Hi Paul Please find attached gazette for DST changes in Fiji. It is from December 20th 2020, till 17th January 2021. Thanks Raymond Kumar Head of Billing & Products +6797015315 ________________________________ 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.

4 3

Re: [tz] tz Digest, Vol 109, Issue 8
by Alan Lehotsky Oct. 8, 2020

Oct. 8, 2020

I’m a little tardy in upgrading (last installed 2018g), but this 2020b release has tar files without a root directory, so when I carelessly did a tar -xzf tzcode2020b.tar.gz tar -xzf tzdata2020b.tar.gz they overwrite each others files instead of unloading into respective directories ./tzcode2020b and ./tzdata2020b. Maybe this isn’t a change in behavior and I just forgot that it happened to me back in 2018. Alan Lehotsky https://codegentllc.com

2 1

[tz-announce] 2020b release of tz code and data available
by Paul Eggert Oct. 8, 2020

Oct. 8, 2020

The 2020b 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: Revised predictions for Morocco's changes starting in 2023. Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. Macquarie Island has stayed in sync with Tasmania since 2011. Casey, Antarctica is at +08 in winter and +11 in summer. zic no longer supports -y, nor the TYPE field of Rules. Changes to future timestamps Morocco's spring-forward after Ramadan is now predicted to occur no sooner than two days after Ramadan, instead of one day. (Thanks to Milamber.) The first altered prediction is for 2023, now predicted to spring-forward on April 30 instead of April 23. Changes to past and future timestamps Casey Station, Antarctica has been using +08 in winter and +11 in summer since 2018. The most recent transition from +08 to +11 was 2020-10-04 00:01. Also, Macquarie Island has been staying in sync with Tasmania since 2011. (Thanks to Steffen Thorsen.) Changes to past and future time zone abbreviations and DST flags Canada's Yukon, represented by America/Whitehorse and America/Dawson, changes its time zone rules from -08/-07 to permanent -07 on 2020-11-01, not on 2020-03-08 as 2020a had it. This change affects only the time zone abbreviation (MST vs PDT) and daylight saving flag for the period between the two dates. (Thanks to Andrew G. Smith.) Changes to past timestamps Correct several transitions for Hungary for 1918/1983. For example, the 1983-09-25 fall-back was at 01:00, not 03:00. (Thanks to Géza Nyáry.) Also, the 1890 transition to standard time was on 11-01, not 10-01 (thanks to Michael Deckers). The 1891 French transition was on March 16, not March 15. The 1911-03-11 French transition was at midnight, not a minute later. Monaco's transitions were on 1892-06-01 and 1911-03-29, not 1891-03-15 and 1911-03-11. (Thanks to Michael Deckers.) Changes to code Support for zic's long-obsolete '-y YEARISTYPE' option has been removed and, with it, so has support for the TYPE field in Rule lines, which is now reserved for compatibility with earlier zic. These features were previously deprecated in release 2015f. (Thanks to Tim Parenti.) zic now defaults to '-b slim' instead of to '-b fat'. zic's new '-l -' and '-p -' options uninstall any existing localtime and posixrules files, respectively. The undocumented and ineffective tzsetwall function has been removed. Changes to build procedure The Makefile now defaults POSIXRULES to '-', so the posixrules feature (obsolete as of 2019b) is no longer installed by default. Changes to documentation and commentary The long-obsolete files pacificnew, systemv, and yearistype.sh have been removed from the distribution. (Thanks to Tim Parenti.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2020b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2020b.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2020b.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 47311d42a3ad6a8afa95d1f63fa8b6bb2710b16e dated 2020-10-06 18:35:04 -0700 and tagged '2020b' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 04849f196430717962cbeedf11bbba592c304eaff5d67350c936af83dc8e8cb4cedc1c5f461c984aef05124d6c0f13a874789dff77b85a4b399faf80d75537e0 tzcode2020b.tar.gz 27ade698e61881e637ab04834633595cfbdb08fd97177e9731093165d1268a64dffa0570b5e137b9daa4374e6c6827ed01c476074ec61ec0b9a44a7f23479be9 tzdata2020b.tar.gz 475f69b908f8d7d777fcf93f1d223fc4af404a3c8caaa678ca97702a3e9c1ec3e1b5747c8688dfc7b291300bab9ff4804b8ceebfc2de47b505cffe4fa5594abc tzdb-2020b.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl99HSkACgkQ7ZfpDmKq fjRNrBAApj2R+iRJs5UdW5lIdsANGSz3d9l/dMs48Ryk5SU6qBCVtL4cKavSfw5Q Xh6ZaohNc8GPHF4pGTHBBrKwq6lxQgbemSXswqh+Qi4584wlI5zHr2J7ohLJTnnx ma4EgRCEBplU7XnANa/dQEr69DVG1LkgvOFNGS42oNNcS5zIVcLkeQaJ93MI/tJO seHQTmQn5hiKsZ60S+qrPy4Yu4Cwxzo6Le/BVEXE3leVAFMcXMzRvV4UEooh2TCM b7v2cHnTKKdN7iTzmKyYrXh3Xs1ENVECLS9D9d9mXDT6FViIXcx95StSELXH3i/s eqqpgnAcpPQIb16uIrT+XlzGbJ56HNh2j/axVqaVzkwHlEOKz7b7y7OUfUUNpzD+ vI/uZ/0reUs2rr0IeSHLK3LVRbPvcw/sHQN8EjirSXVDQcfjAr0x72V+YPzDIQ5K fQ6o1ADrrd6cHCa90D1xz94d34DD3sSfUjaOOpNpaLJL7GW5CNsm0CaWIc8my4Dp Agt6T4QtA0WAtsnvupKk3tuPP57rvrlVTQYEvfhpDsPxVkY+R80ir/3+eCMZHrvm 3CZ1uWNGd7kG1m4sfcq0AHUl3bgHapJkLRtyMY4izQJZIm0pGEsrCi8P3+87wDgU eIMcGJUYOjTtE1ELGWxzo066FpOLMoGm9YOwN+FYi+eSjEdjGdg= =BKe9 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl99HToACgkQ7ZfpDmKq fjT5CQ//W6kd+vP2tAdMbmJnH35sCd0NoAFBC1j00Blg+I6s507w5VjOTjvrvjlE 0RB2G67vNKTOBybPyk7l8cKq+5Xw5IE1xqwqfpN3+DH2BWt4P0AllcBBRRky9iXS oO+z4F51rud9+CD2vbhtx0eT9MWYVfzrncNUHIYm7sDx01vtCp3h5u9ryB2sfHT/ iMKrB5ytFqWkNXZtMiRDj3LZF0y2+JM1/8lfZB/hyxx1Bbvcm07dQvBBz8ljT6KD /BJFsgwvvlpxOZ1P0fFb7BnMPD5v/fB5r/0i/c4ErIY8JPtxDY6ctGdtbC/0H7Xf kjve+Fue08CBg4tXEW75SvWBP8Li1XylSNohIEtnclXj9B1nwu0WArZtATIqhpxl T77J85JkVQoAi5Wh38Msy9QWb54FRoK8/c1drfwb/iMkRYt57mU5zuY9JJvx7mAm S3eVqU3/tX4Ue7gQ1hjW3m9abmS1Hmq4aQ8r1uS0t2cIjbrMY2zaRwYzb2UknT2w VVr5O5bWoPHSFDeqUU7NdGHQzJX+NLvpTlcvJHXONSu7CksC09uhzBVJ2LbkjQS1 zD+jSCTgXZonegcF0/UsfMrxmrizDFVcvwDXnDa4TcRPVSevtdWvM+EXr3Dto0N/ wlI4v2nZE2ZFB3+7iGxc0WwiHUdsVbQVD+fCTIBl4Uh4ViTAsXI= =/O2G -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAl99HTsACgkQ7ZfpDmKq fjRCtQ//ZOBneEAY4W08oOJ3UipwG+Xq33arMbZ86yBBBrkjUIfcLFi7ESPGvkn8 zAR28fYpL7kUTQyuzMjwIxdFSDpgmRUpLRtlLn+Vdkx1o/WCbj5A0O3nsqq+M04J yuGr1dYGfTnGi624mvsB5dPxneGw9TCh9YseBKV+hF6FxmhdBkl1Gwxz4fyzAdo9 A4OQhtnKntZo6Peuo8ittfnA6fi6hwVZjeaqjGWMN7qEjSOG79mVAHaKxsOKUs2L Mnre/1iRQX/33c/hJHrleit2+H430WCVJ3WGQ0OjODfnrl5B9tmWv0CFIaJTUq4Q zwOBpa2CvTd0hOmagZiP7PuTI1AXjMpJBd1ISssbw1mPO7lcAjSfjYMYy972xhUQ pig67kaKATh8tfPUTUjE8pEOyLnPkZdT0dbFqz1Sqad2u1y5NmWl1ps8YYZl9hHC a0pzxRD7HIK4o1BYuSMLuvwgfdFFjBeGMbm1/sFOSgRzzrZQ8BIXEmNG5whM+OQF +cfmyG9VZimvAI/vcw2w6xqokJn/l8yrG8D3GJZNA4s3xJTLYXUc6qrY7FpTDa0A Ce2Lj1HZN4q9FyIeEU22YAXKDmP8/7eNCO/Z7I9mrjocbpS09tL2YOWh1EI1Gq/U fqxprHL5w+/AKehKr5YZ7eZA5QXQBH80RIXqntJwFsnkd7pfmYU= =1NiW -----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'.

4 5

Removing systemv, pacificnew, Rule TYPEs, zic -y
by Tim Parenti Oct. 4, 2020

Oct. 4, 2020

I noticed recently that the systemv file, which adapted a subset of North American zones with limited rulesets to old versions of System V, has had all its once-useful bits commented out since 2005p. Looking back at list archives, even discussion at the time argued that the file wasn't really needed then. The attached proposed patch 0001 removes this obsolete file and its references. Of course, I was only looking at systemv in the first place because I'd also recalled that we're still distributing the pacificnew file, which has caused some confusion every so often and has likewise generally outlived its usefulness. This led me to the related file yearistype.sh, which is also unused, except as a default script to pass to the Makefile to process the TYPE field of Rule lines. Given that the TYPE field hasn't been used by tzdata since 2000f and has been more formally deprecated since 2015f, the whole unused feature is ripe for "spring cleaning". The attached proposed patch 0002 completely drops support for the TYPE field (marking it reserved for compatibility purposes) and causes non-trivial use of the field or use of zic's -y option to error (instead of warning as it has since 2017c). It also removes the pacificnew and yearistype.sh files that are no longer needed and updates documentation accordingly. I don't presently foresee any need to repurpose the nullified field down the road, but this is the next step in allowing us to "reclaim" it in the event that such a need should arise in the future. -- Tim Parenti

3 3

Converting tz-how-to.html to HTML 5
by Paul Eggert Oct. 4, 2020

Oct. 4, 2020

On 10/3/20 3:49 PM, Tim Parenti wrote: > (the VALIDATE=':' is because my MacBook > doesn't have nsgmls). The VALIDATE stuff in Makefile is needed only because I hadn't bothered to convert tz-how-to.html to HTML 5 with validator.w3.org checking, like the other web pages. I installed the attached proposed patch to do that, removing the need for VALIDATE etc. This is for maintenance convenience; it doesn't change the content of that web page, or its appearance on my Firefox 81 browser.

1 0

Updating zic.c to further match Link line field names
by Tim Parenti Oct. 3, 2020

Oct. 3, 2020

In working on my latest proposed patch, I also noticed an outdated error message in zic.c which referred to the FROM field of a Link line. We had updated these field names in comments and documentation in release 2014g to be more descriptive and readily understandable like the parameters of 'ln': https://github.com/eggert/tz/commit/78e3924ea43079a0f3333677a728e0f0ed679cd3 The attached proposed patch further updates the zic.c code to more consistently use these new names throughout. This mostly affects the naming of parameters and locals, but a few macros and struct fields are also updated for consistency. -- Tim Parenti

1 1

Casey time zone change
by Steffen Thorsen Oct. 2, 2020

Oct. 2, 2020

Based on information we have received from the Australian Antarctic Division, Casey station and Macquarie Island station will move to Tasmanian daylight savings time on Sunday 4 October. This will take effect from 0001hrs on Sunday 4 October 2020 and will mean Casey and Macquarie Island will be on the same time zone as Hobart. Some past dates too for this 3 hour time change back and forth between UTC+8 and UTC+11 for Casey: - 2018 Oct 7 4:00 - 2019 Mar 17 3:00 - 2019 Oct 6 3:00 - 2020 Mar 8 3:00 and now - 2020 Oct 4 0:01 Best regards, Steffen - timeanddate.com

2 3

Re: [tz] [IANA #1173666] Time zone change - Yukon Canada
by Andrew.Smith＠gov.yk.ca Sept. 30, 2020

Sept. 30, 2020

Good day. I work for the Government of Yukon in Canada. We are in the process of revising our definition of time to be permanently on UTC -7, no longer observing a twice-annual time change. I was on the hunt for authoritative standards related to time, and saw the IANA come up as caretaker of the time zone database, which appears to be relied on for software and systems. I am contacting you to see if there is any process beyond notification to making this adjustment in your TZ database, and perhaps to know if there are other agencies that should be aware of what Yukon is planning. From what I see now, TZ database names "America/Dawson", "America/Whitehorse" and "Canada/Yukon" would be affected by this change. Our regulation is not yet complete, so it is not law at this time and I am not looking for immediate change. We are aiming for finalization here by November 1, 2020. Hope to hear from you soon. Andrew Andrew G. Smith Intergovernmental Relations Executive Council Office Government of Yukon C: 867-335-6008 -----Original Message----- From: Amanda Baber via RT <iana-questions(a)iana.org> Sent: July 2, 2020 3:48 PM To: Andrew.Smith <Andrew.Smith(a)gov.yk.ca> Subject: [IANA #1173666] Time zone change - Yukon Canada Dear Andrew, Thank you for contacting us. IANA hosts the Time Zone Database, but the database is managed by the Time Zone Coordinator in conjunction with a mailing list. You can find find mailing list information here: https://www.iana.org/time-zones This document should have or point to much of the information you're looking for: https://data.iana.org/time-zones/tz-link.html As is noted at the link above, "If your government plans to change its time zone boundaries or daylight saving rules, inform tz(a)iana.org well in advance, as this will coordinate updates to many cell phones, computers, and other devices around the world. With less than a year's notice there is a good chance that some computer-based clocks will operate incorrectly after the change, due to delays in propagating updates to software and data. The shorter the notice, the more likely clock problems will arise; see https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%… for examples." Best regards, Amanda Baber Lead IANA Services Specialist On Thu Jul 02 22:20:44 2020, Andrew.Smith(a)gov.yk.ca wrote: > Good day. > > I work for the Government of Yukon in Canada. We are in the process of > revising our definition of time to be permanently on UTC -7, no longer > observing a twice-annual time change. > I was on the hunt for authoritative standards related to time, and saw > the IANA come up as caretaker of the time zone database, which appears > to be relied on for software and systems. I started with ISO 8601, but > couldn't see the full text to know if there are time zone standards > there. I am contacting you to see your TZ database is a widely adopted > and authoritative as it seems, to see if there is any process to > making this adjustment in your TZ database, and perhaps to know if > there are other agencies that should be aware of what Yukon is > planning. > From what I see now, TZ database names "America/Dawson", > "America/Whitehorse" and "Canada/Yukon" would be affected by this > change. > > Our regulation is not yet complete, so it is not law at this time and > I am not looking for immediate change. We are aiming for finalization > here by November 1, 2020. > Hope to hear from you soon. > > Andrew > > > [cid:image003.png@01D65084.40C16690] > > Andrew G. Smith > Intergovernmental Relations > Executive Council Office > C 867-335-6008 | Yukon.ca

10 23