May 2021 - tz - lists.iana.org

(no subject)
by Cool Gab19 Nov. 8, 2024

Nov. 8, 2024

can you add Philippine Daylight Time on your Database I think it was missing from the list of the time zones please reply immediately if solved thanks...

4 8

Re: [tz] Morocco : Ramdan Time Change 2021
by Paul Eggert March 15, 2023

March 15, 2023

On 3/19/21 3:15 AM, Semlali Naoufal wrote: > At the moment, we have no official government announcement to this effect. But, logically, the change to the GMT schedule should be made on the night of April 10-11, 2021 (last weekend before Ramadan). Yes, that's been the tzdb prediction too, ever since tzdb version 2018h (2018-12-23). For the record, here are tzdb's current predictions Morocco transitions during the next five years. Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 Sun May 16 02:00:00 2021 UT = Sun May 16 03:00:00 2021 +01 Sun Mar 27 01:59:59 2022 UT = Sun Mar 27 02:59:59 2022 +01 Sun Mar 27 02:00:00 2022 UT = Sun Mar 27 02:00:00 2022 +00 Sun May 8 01:59:59 2022 UT = Sun May 8 01:59:59 2022 +00 Sun May 8 02:00:00 2022 UT = Sun May 8 03:00:00 2022 +01 Sun Mar 19 01:59:59 2023 UT = Sun Mar 19 02:59:59 2023 +01 Sun Mar 19 02:00:00 2023 UT = Sun Mar 19 02:00:00 2023 +00 Sun Apr 30 01:59:59 2023 UT = Sun Apr 30 01:59:59 2023 +00 Sun Apr 30 02:00:00 2023 UT = Sun Apr 30 03:00:00 2023 +01 Sun Mar 10 01:59:59 2024 UT = Sun Mar 10 02:59:59 2024 +01 Sun Mar 10 02:00:00 2024 UT = Sun Mar 10 02:00:00 2024 +00 Sun Apr 14 01:59:59 2024 UT = Sun Apr 14 01:59:59 2024 +00 Sun Apr 14 02:00:00 2024 UT = Sun Apr 14 03:00:00 2024 +01 Sun Feb 23 01:59:59 2025 UT = Sun Feb 23 02:59:59 2025 +01 Sun Feb 23 02:00:00 2025 UT = Sun Feb 23 02:00:00 2025 +00 Sun Apr 6 01:59:59 2025 UT = Sun Apr 6 01:59:59 2025 +00 Sun Apr 6 02:00:00 2025 UT = Sun Apr 6 03:00:00 2025 +01 Sun Feb 15 01:59:59 2026 UT = Sun Feb 15 02:59:59 2026 +01 Sun Feb 15 02:00:00 2026 UT = Sun Feb 15 02:00:00 2026 +00 Sun Mar 22 01:59:59 2026 UT = Sun Mar 22 01:59:59 2026 +00 Sun Mar 22 02:00:00 2026 UT = Sun Mar 22 03:00:00 2026 +01 Sun Feb 7 01:59:59 2027 UT = Sun Feb 7 02:59:59 2027 +01 Sun Feb 7 02:00:00 2027 UT = Sun Feb 7 02:00:00 2027 +00 Sun Mar 14 01:59:59 2027 UT = Sun Mar 14 01:59:59 2027 +00 Sun Mar 14 02:00:00 2027 UT = Sun Mar 14 03:00:00 2027 +01 Sun Jan 23 01:59:59 2028 UT = Sun Jan 23 02:59:59 2028 +01 Sun Jan 23 02:00:00 2028 UT = Sun Jan 23 02:00:00 2028 +00 Sun Mar 5 01:59:59 2028 UT = Sun Mar 5 01:59:59 2028 +00 Sun Mar 5 02:00:00 2028 UT = Sun Mar 5 03:00:00 2028 +01 Sun Jan 14 01:59:59 2029 UT = Sun Jan 14 02:59:59 2029 +01 Sun Jan 14 02:00:00 2029 UT = Sun Jan 14 02:00:00 2029 +00 Sun Feb 18 01:59:59 2029 UT = Sun Feb 18 01:59:59 2029 +00 Sun Feb 18 02:00:00 2029 UT = Sun Feb 18 03:00:00 2029 +01 Sun Dec 30 01:59:59 2029 UT = Sun Dec 30 02:59:59 2029 +01 Sun Dec 30 02:00:00 2029 UT = Sun Dec 30 02:00:00 2029 +00 Sun Feb 10 01:59:59 2030 UT = Sun Feb 10 01:59:59 2030 +00 Sun Feb 10 02:00:00 2030 UT = Sun Feb 10 03:00:00 2030 +01 Sun Dec 22 01:59:59 2030 UT = Sun Dec 22 02:59:59 2030 +01 Sun Dec 22 02:00:00 2030 UT = Sun Dec 22 02:00:00 2030 +00

3 9

United States Senate reintroduced Sunshine Protection Act, enabling Permanent DST
by Phake Nick Nov. 14, 2022

Nov. 14, 2022

I don't quite understand the legal text of the bill itself [2], but according to my reading, it seems like the bill will end DST across the entire US by shifting the standard time forward an hour, except in states/territories/area that currently doesn't enact DST, which they can choose to follow the new standard time or old standard time? 1: https://www.rubio.senate.gov/public/index.cfm/2021/3/rubio-colleagues-reint… 2: https://www.rubio.senate.gov/public/_cache/files/d34c77c0-acea-4074-bc57-14…

18 26

Re: [tz] iana build failures on Windows
by Paul Eggert Nov. 2, 2022

Nov. 2, 2022

On 4/19/21 7:09 AM, Manuela Friedrich wrote: > I had to include signal.h in zic.c to prevent the following error: > > zic.c(610): error C2061: syntax error: identifier 'got_signal' This is a portability bug recently introduced to zic.c. I installed the first attached patch to fix it. > The I needed to resolved error > > zic.obj : error LNK2019: unresolved external symbol tz_time referenced in function random_dirent This appears to be another recent portability bug. It's related to a portability problem you reported on MS-Windows in response to which in 2018d I committed a patch that introduced RESERVE_STD_EXT_IDS: https://github.com/eggert/tz/commit/24b45243c5210b4196987fdd06e6c288c358a268 When I recently added the randomish filename code to the development version, I neglected to deal with RESERVE_STD_EXT_IDS. The second attached patch should fix this issue. Please give the two patches a try, as I don't use MS-Windows and can't easily test these patches on that platform. > a test run of zdump -v produced way more output than in the last release, the Linux output seems to have become longer too, but maybe this is still under development. That change is intentional, and was caused by this: https://github.com/eggert/tz/commit/ac07b446a3afaa4cb1ae11a91785a201c91f6351 along with some neighboring commits. Thanks for reporting the problems, and I hope the current development version of tzdb addresses the issues you mentioned.

5 23

Re: [tz] Change Request: Europe/Kiev to Europe/Kyiv
by John Hawkinson March 18, 2022

March 18, 2022

I do not think we have handled this well; we have not given Victor Perov a good answer. Indeed, to some extent we've made it a "runaround." We can do better. We should take the time to write up a good lengthy explanation of the issues ("boilerplate"), because this a really important issue of concern to many people in the world and the project has indeed thought about it pretty carefully. Dismissing the inquiries because they are repetitive makes it seem like we haven't, and that unnecessarily upsets peopl. Victor Perev: I don't have time for a full write-up right now, but please consult the archives of the tz list (http://mm.icann.org/pipermail/tz/ or perhaps https://www.google.com/search?q=site%3Amm.icann.org%2Fpipermail%2Ftz%2F+kyiv which returns 203 results). The tz project is very conservative in its judgment for when the predominant English spelling of a city has changed, and so far the project has judged that Kiev is still preferred. We discussed it when major English newspapers and style guides changed from Kiev to Kyiv last year (prompted by the US presidential impeachment, which lead to a lot of discussion about Kyiv in America), and we will probably continue to discuss it as time goes on. But we've thought about it and discussed it a lot. The answers you got don't explain that, and that means we have not done a good a job as we should have. Sorry about that. In particular, I think Brian Inglis's answer was actually incorrect in a way that really matters ("Kiev is the correct English spelling"). There are multiple correct English spellings. It used to be that Kiev was the only one, but Kyiv is gaining popularity more and more. Paul Eggert <eggert(a)cs.ucla.edu> wrote on Sat, 15 Aug 2020 at 18:19:08 EDT in <cefc7f01-a3e9-f2a4-9ab9-5288147f994a(a)cs.ucla.edu>: > Thanks for bringing that to the mailing list (if I could shut off GitHub > pull requests I would). Although you cannot do so, we can handle them a little bit better. Please see https://docs.github.com/en/github/building-a-strong-community/creating-a-pu… You can create a template that explains to a would-be pull request submitter than pull requests will be closed and the project uses the mailing list for development discussions. ("I understand that the tz project does not use pull requests on github, and that if I enter a pull request here, it will be closed and I will be directed to send email to tz(a)iana.org.") For the particular case of regular, recurring issues, it may be worth while to keep one of #15, #26, and #27 open and mark the others as a duplicate of it, so that it is easier for newcomers to understand that this issue has been carefully considered and is not a simple oversight. https://github.com/eggert/tz/pulls?q=kiev Also, not to pick on Brian (again), but if the project policy is not to use github pull requests, it's not great to respond to pull requests on their substance, because it bifurcates the discussion and makes it seem like we actually do use pull requests ("except when we don't"). So what seems like a helpful thing may not be. -- jhawk(a)alum.mit.edu John Hawkinson

10 13

Italy April 1944 discrepancy between comment and data
by Alois Treindl Oct. 5, 2021

Oct. 5, 2021

For Italy in 1944 zone Europe/Rome there is a discrepancy between the comment and the data. comment: # From Paul Eggert (2016-10-27): # Go with INRiM for DST rules, except as corrected by Inglis for 1944 # for the Kingdom of Italy. This is consistent with Renzo Baldini. # Model Rome's occupation by using C-Eur rules from 1943-09-10 # to 1944-06-04; although Rome was an open city during this period, it # was effectively controlled by Germany. Data for Italy is Rule Italy 1944 only - Apr 2 2:00s 1:00 S Data for C-Eur is: Rule C-Eur 1944 1945 - Apr Mon>=1 2:00s 1:00 S where Mon>=1 in 1944 is April 3. So Rome is NOT following C-Eur. I think the rule for Itay is right, only the comment is misleading.

4 9

Historical fix for Tonga
by Tim Parenti Sept. 14, 2021

Sept. 14, 2021

First, a quick clerical patch: 0001, attached, fixes the placement of a comment which got shuffled around in the lead-up to publishing the changes for South Sudan in 2021a. Patch 0003 relates to Tonga, and comes from some of the links P Chan shared to 1957–1963 editions of The Air Almanac: https://mm.icann.org/pipermail/tz/2021-February/029866.html On Thu, 25 Feb 2021 at 03:43, P Chan <legco(a)outlook.com> wrote: > 1960 Nov (1962.1-4) > https://books.google.com/books?id=bVgtWM6kPZUC&pg=SL1-PA20 > 1961 Mar (1962.5-8) > https://books.google.com/books?id=W2nItAul4g0C&pg=SL1-PA20 When looking around at how this data was presented for other regions, I noticed on the preceding pages (listing "Places Fast on GMT", i.e., east of Greenwich) in some of the earlier editions provided that Tonga was listed at GMT+12:20. The peculiar offset stuck out, and I quickly noticed that some of the later editions of the same tables had it at GMT+13. A quick bisection puts the changeover, as far as The Air Almanac contemporaneously reckoned it, between November 1960 and March 1961. Previously, our data had Tonga transitioning to UT+13 in 1941 based on a quotation from a 1997 news article. Although this differs from what the Almanac suggests by some 20 years, the article does mention a change coincident with the New Year, and that Tāufaʻāhau Tupou IV was Crown Prince at the time. As his predecessor and mother, Queen Sālote Tupou III, reigned from 1918-04-05 to 1965-12-16, a possible transition of 1961-01-01 still jives with the gist of the article, even if the specific year was perhaps wrong or just misprinted. For what it's worth, our commentary already noted that Shanks & Pottenger had put the transition even later, at 1968-10-01. Although of course we don't know how they arrived at that date, given that they did, 1961 seems rather less out-of-place than it otherwise might. The attached patch 0003 makes this adjustment, while more fully documenting and comparing the conflicting sources. Thanks again to P Chan for pointing us to these resources. I wasn't expecting to get a "bonus" correction out of it, but one never knows quite what will catch the eye… -- Tim Parenti

3 3

[PATCH 1/8] * tzfile.5: Fix prefix/suffix typo (thanks to Ian Abbott).
by Paul Eggert Sept. 14, 2021

Sept. 14, 2021

--- tzfile.5 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tzfile.5 b/tzfile.5 index b4952d5..ec78689 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -134,7 +134,7 @@ bytes that represent time zone designations, which are null-terminated byte strings, each indexed by the .B tt_desigidx values mentioned above. -The byte strings can overlap if one is a prefix of the other. +The byte strings can overlap if one is a suffix of the other. The encoding of these strings is not specified. .IP * .B tzh_leapcnt -- 2.27.0

2 8

[PROPOSED] Avoid backward links in zone.tab
by Paul Eggert June 12, 2021

June 12, 2021

Recent changes caused zone.tab to refer to links defined in the 'backward' file, which means it no longer works in the now-rare case where 'backward' is not used. Fix this by changing zone.tab to refer to the primary name of each zone. * checktab.awk: Adjust to check the new setup. * zone.tab: Replace backward links in the 3rd column with the primary zone names. This lets us fix a longstanding problem with Vietnam, as zone.tab can now have a separate entry for north Vietnam's different time zone history in the 1970s (this was already true of zone1970.tab). --- checktab.awk | 48 +++++++-------- zone.tab | 161 ++++++++++++++++++++++++++------------------------- 2 files changed, 105 insertions(+), 104 deletions(-) diff --git a/checktab.awk b/checktab.awk index 54ac0a6..d5317ac 100644 --- a/checktab.awk +++ b/checktab.awk @@ -58,11 +58,12 @@ BEGIN { zone_table, zone_NR >>"/dev/stderr" status = 1 } - split($1, cca, /,/) - cc = cca[1] + ccs = input_ccs[zone_NR] = $1 coordinates = $2 tz = $3 - comments = $4 + comments = input_comments[zone_NR] = $4 + split(ccs, cca, /,/) + cc = cca[1] # Don't complain about a special case for Crimea in zone.tab. # FIXME: zone.tab should be removed, since it is obsolete. @@ -77,12 +78,9 @@ BEGIN { cc0 = cc tz0 = tz tztab[tz] = 1 - tz2comments[tz] = comments tz2NR[tz] = zone_NR for (i in cca) { cc = cca[i] - cctz = cc tz - cctztab[cctz] = 1 if (cc2name[cc]) { cc_used[cc]++ } else { @@ -99,27 +97,27 @@ BEGIN { } } - for (cctz in cctztab) { - cc = substr (cctz, 1, 2) - tz = substr (cctz, 3) - if (1 < cc_used[cc]) { - comments_needed[tz] = cc - } - } - for (cctz in cctztab) { - cc = substr (cctz, 1, 2) - tz = substr (cctz, 3) - if (!comments_needed[tz] && tz2comments[tz]) { + for (i = 1; i <= zone_NR; i++) { + ccs = input_ccs[i] + if (!ccs) continue + comments = input_comments[i] + split(ccs, cca, /,/) + used_max = 0 + for (j in cca) { + cc = cca[j] + if (used_max < cc_used[cc]) { + used_max = cc_used[cc] + } + } + if (used_max <= 1 && comments) { printf "%s:%d: unnecessary comment '%s'\n", \ - zone_table, tz2NR[tz], tz2comments[tz] \ - >>"/dev/stderr" - tz2comments[tz] = 0 + zone_table, i, comments \ + >>"/dev/stderr" status = 1 - } else if (comments_needed[tz] && !tz2comments[tz]) { + } else if (1 < cc_used[cc] && !comments) { printf "%s:%d: missing comment for %s\n", \ - zone_table, tz2NR[tz], comments_needed[tz] \ + zone_table, i, cc \ >>"/dev/stderr" - tz2comments[tz] = 1 status = 1 } } @@ -172,14 +170,12 @@ END { status = 1 } } - if (zone_table != "zone.tab") { - for (tz in tztab) { + for (tz in tztab) { if (!zoneSeen[tz]) { printf "%s:%d: no Zone table for '%s'\n", \ zone_table, tz2NR[tz], tz >>"/dev/stderr" status = 1 } - } } if (0 < want_warnings) { for (cc in cc2name) { diff --git a/zone.tab b/zone.tab index 14fceb9..fe53f0a 100644 --- a/zone.tab +++ b/zone.tab @@ -16,6 +16,10 @@ # clocks have agreed since 1970; this is a narrower definition than # that of zone1970.tab. # +# Unlike zone1970.tab, this file's third column can contain duplicates, +# and a row's third column does not necessarily name a location within +# the country identified by the row's first column. +# # This table is intended as an aid for users, to help them select timezones # appropriate for their practical needs. It is not intended to take or # endorse any position on legal or territorial claims. @@ -25,12 +29,12 @@ AD +4230+00131 Europe/Andorra AE +2518+05518 Asia/Dubai AF +3431+06912 Asia/Kabul -AG +1703-06148 America/Antigua -AI +1812-06304 America/Anguilla +AG +1703-06148 America/Port_of_Spain +AI +1812-06304 America/Port_of_Spain AL +4120+01950 Europe/Tirane AM +4011+04430 Asia/Yerevan -AO -0848+01314 Africa/Luanda -AQ -7750+16636 Antarctica/McMurdo New Zealand time - McMurdo, South Pole +AO -0848+01314 Africa/Lagos +AQ -7750+16636 Pacific/Auckland New Zealand time - McMurdo, South Pole AQ -6617+11031 Antarctica/Casey Casey AQ -6835+07758 Antarctica/Davis Davis AQ -6640+14001 Antarctica/DumontDUrville Dumont-d'Urville @@ -66,23 +70,23 @@ AU -3455+13835 Australia/Adelaide South Australia AU -1228+13050 Australia/Darwin Northern Territory AU -3157+11551 Australia/Perth Western Australia (most areas) AU -3143+12852 Australia/Eucla Western Australia (Eucla) -AW +1230-06958 America/Aruba -AX +6006+01957 Europe/Mariehamn +AW +1230-06958 America/Curacao +AX +6006+01957 Europe/Helsinki AZ +4023+04951 Asia/Baku -BA +4352+01825 Europe/Sarajevo +BA +4352+01825 Europe/Belgrade BB +1306-05937 America/Barbados BD +2343+09025 Asia/Dhaka BE +5050+00420 Europe/Brussels -BF +1222-00131 Africa/Ouagadougou +BF +1222-00131 Africa/Abidjan BG +4241+02319 Europe/Sofia -BH +2623+05035 Asia/Bahrain -BI -0323+02922 Africa/Bujumbura -BJ +0629+00237 Africa/Porto-Novo -BL +1753-06251 America/St_Barthelemy +BH +2623+05035 Asia/Qatar +BI -0323+02922 Africa/Maputo +BJ +0629+00237 Africa/Lagos +BL +1753-06251 America/Port_of_Spain BM +3217-06446 Atlantic/Bermuda BN +0456+11455 Asia/Brunei BO -1630-06809 America/La_Paz -BQ +120903-0681636 America/Kralendijk +BQ +120903-0681636 America/Curacao BR -0351-03225 America/Noronha Atlantic islands BR -0127-04829 America/Belem Para (east); Amapa BR -0343-03830 America/Fortaleza Brazil (northeast: MA, PI, CE, RN, PB) @@ -101,7 +105,7 @@ BR -0640-06952 America/Eirunepe Amazonas (west) BR -0958-06748 America/Rio_Branco Acre BS +2505-07721 America/Nassau BT +2728+08939 Asia/Thimphu -BW -2439+02555 Africa/Gaborone +BW -2439+02555 Africa/Maputo BY +5354+02734 Europe/Minsk BZ +1730-08812 America/Belize CA +4734-05243 America/St_Johns Newfoundland; Labrador (southeast) @@ -133,17 +137,17 @@ CA +6043-13503 America/Whitehorse MST - Yukon (east) CA +6404-13925 America/Dawson MST - Yukon (west) CA +4916-12307 America/Vancouver Pacific - BC (most areas) CC -1210+09655 Indian/Cocos -CD -0418+01518 Africa/Kinshasa Dem. Rep. of Congo (west) -CD -1140+02728 Africa/Lubumbashi Dem. Rep. of Congo (east) -CF +0422+01835 Africa/Bangui -CG -0416+01517 Africa/Brazzaville +CD -0418+01518 Africa/Lagos Dem. Rep. of Congo (west) +CD -1140+02728 Africa/Maputo Dem. Rep. of Congo (east) +CF +0422+01835 Africa/Lagos +CG -0416+01517 Africa/Lagos CH +4723+00832 Europe/Zurich CI +0519-00402 Africa/Abidjan CK -2114-15946 Pacific/Rarotonga CL -3327-07040 America/Santiago Chile (most areas) CL -5309-07055 America/Punta_Arenas Region of Magallanes CL -2709-10926 Pacific/Easter Easter Island -CM +0403+00942 Africa/Douala +CM +0403+00942 Africa/Lagos CN +3114+12128 Asia/Shanghai Beijing Time CN +4348+08735 Asia/Urumqi Xinjiang Time CO +0436-07405 America/Bogota @@ -156,10 +160,10 @@ CY +3510+03322 Asia/Nicosia Cyprus (most areas) CY +3507+03357 Asia/Famagusta Northern Cyprus CZ +5005+01426 Europe/Prague DE +5230+01322 Europe/Berlin Germany (most areas) -DE +4742+00841 Europe/Busingen Busingen -DJ +1136+04309 Africa/Djibouti +DE +4742+00841 Europe/Zurich Swiss time +DJ +1136+04309 Africa/Nairobi DK +5540+01235 Europe/Copenhagen -DM +1518-06124 America/Dominica +DM +1518-06124 America/Port_of_Spain DO +1828-06954 America/Santo_Domingo DZ +3647+00303 Africa/Algiers EC -0210-07950 America/Guayaquil Ecuador (mainland) @@ -167,11 +171,11 @@ EC -0054-08936 Pacific/Galapagos Galapagos Islands EE +5925+02445 Europe/Tallinn EG +3003+03115 Africa/Cairo EH +2709-01312 Africa/El_Aaiun -ER +1520+03853 Africa/Asmara +ER +1520+03853 Africa/Nairobi ES +4024-00341 Europe/Madrid Spain (mainland) ES +3553-00519 Africa/Ceuta Ceuta, Melilla ES +2806-01524 Atlantic/Canary Canary Islands -ET +0902+03842 Africa/Addis_Ababa +ET +0902+03842 Africa/Nairobi FI +6010+02458 Europe/Helsinki FJ -1808+17825 Pacific/Fiji FK -5142-05751 Atlantic/Stanley @@ -180,22 +184,22 @@ FM +0658+15813 Pacific/Pohnpei Pohnpei/Ponape FM +0519+16259 Pacific/Kosrae Kosrae FO +6201-00646 Atlantic/Faroe FR +4852+00220 Europe/Paris -GA +0023+00927 Africa/Libreville +GA +0023+00927 Africa/Lagos GB +513030-0000731 Europe/London -GD +1203-06145 America/Grenada +GD +1203-06145 America/Port_of_Spain GE +4143+04449 Asia/Tbilisi GF +0456-05220 America/Cayenne -GG +492717-0023210 Europe/Guernsey +GG +492717-0023210 Europe/London GH +0533-00013 Africa/Accra GI +3608-00521 Europe/Gibraltar GL +6411-05144 America/Nuuk Greenland (most areas) GL +7646-01840 America/Danmarkshavn National Park (east coast) GL +7029-02158 America/Scoresbysund Scoresbysund/Ittoqqortoormiit GL +7634-06847 America/Thule Thule/Pituffik -GM +1328-01639 Africa/Banjul -GN +0931-01343 Africa/Conakry -GP +1614-06132 America/Guadeloupe -GQ +0345+00847 Africa/Malabo +GM +1328-01639 Africa/Abidjan +GN +0931-01343 Africa/Abidjan +GP +1614-06132 America/Port_of_Spain +GQ +0345+00847 Africa/Lagos GR +3758+02343 Europe/Athens GS -5416-03632 Atlantic/South_Georgia GT +1438-09031 America/Guatemala @@ -204,7 +208,7 @@ GW +1151-01535 Africa/Bissau GY +0648-05810 America/Guyana HK +2217+11409 Asia/Hong_Kong HN +1406-08713 America/Tegucigalpa -HR +4548+01558 Europe/Zagreb +HR +4548+01558 Europe/Belgrade HT +1832-07220 America/Port-au-Prince HU +4730+01905 Europe/Budapest ID -0610+10648 Asia/Jakarta Java, Sumatra @@ -213,29 +217,29 @@ ID -0507+11924 Asia/Makassar Borneo (east, south); Sulawesi/Celebes, Bali, Nusa ID -0232+14042 Asia/Jayapura New Guinea (West Papua / Irian Jaya); Malukus/Moluccas IE +5320-00615 Europe/Dublin IL +314650+0351326 Asia/Jerusalem -IM +5409-00428 Europe/Isle_of_Man +IM +5409-00428 Europe/London IN +2232+08822 Asia/Kolkata IO -0720+07225 Indian/Chagos IQ +3321+04425 Asia/Baghdad IR +3540+05126 Asia/Tehran IS +6409-02151 Atlantic/Reykjavik IT +4154+01229 Europe/Rome -JE +491101-0020624 Europe/Jersey +JE +491101-0020624 Europe/London JM +175805-0764736 America/Jamaica JO +3157+03556 Asia/Amman JP +353916+1394441 Asia/Tokyo KE -0117+03649 Africa/Nairobi KG +4254+07436 Asia/Bishkek -KH +1133+10455 Asia/Phnom_Penh +KH +1133+10455 Asia/Bangkok KI +0125+17300 Pacific/Tarawa Gilbert Islands KI -0308-17105 Pacific/Enderbury Phoenix Islands KI +0152-15720 Pacific/Kiritimati Line Islands -KM -1141+04316 Indian/Comoro -KN +1718-06243 America/St_Kitts +KM -1141+04316 Africa/Nairobi +KN +1718-06243 America/Port_of_Spain KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul -KW +2920+04759 Asia/Kuwait -KY +1918-08123 America/Cayman +KW +2920+04759 Asia/Riyadh +KY +1918-08123 America/Panama KZ +4315+07657 Asia/Almaty Kazakhstan (most areas) KZ +4448+06528 Asia/Qyzylorda Qyzylorda/Kyzylorda/Kzyl-Orda KZ +5312+06337 Asia/Qostanay Qostanay/Kostanay/Kustanay @@ -243,13 +247,13 @@ KZ +5017+05710 Asia/Aqtobe Aqtobe/Aktobe KZ +4431+05016 Asia/Aqtau Mangghystau/Mankistau KZ +4707+05156 Asia/Atyrau Atyrau/Atirau/Gur'yev KZ +5113+05121 Asia/Oral West Kazakhstan -LA +1758+10236 Asia/Vientiane +LA +1758+10236 Asia/Bangkok LB +3353+03530 Asia/Beirut -LC +1401-06100 America/St_Lucia -LI +4709+00931 Europe/Vaduz +LC +1401-06100 America/Port_of_Spain +LI +4709+00931 Europe/Zurich LK +0656+07951 Asia/Colombo LR +0618-01047 Africa/Monrovia -LS -2928+02730 Africa/Maseru +LS -2928+02730 Africa/Johannesburg LT +5441+02519 Europe/Vilnius LU +4936+00609 Europe/Luxembourg LV +5657+02406 Europe/Riga @@ -257,26 +261,26 @@ LY +3254+01311 Africa/Tripoli MA +3339-00735 Africa/Casablanca MC +4342+00723 Europe/Monaco MD +4700+02850 Europe/Chisinau -ME +4226+01916 Europe/Podgorica -MF +1804-06305 America/Marigot -MG -1855+04731 Indian/Antananarivo +ME +4226+01916 Europe/Belgrade +MF +1804-06305 America/Port_of_Spain +MG -1855+04731 Africa/Nairobi MH +0709+17112 Pacific/Majuro Marshall Islands (most areas) MH +0905+16720 Pacific/Kwajalein Kwajalein -MK +4159+02126 Europe/Skopje -ML +1239-00800 Africa/Bamako +MK +4159+02126 Europe/Belgrade +ML +1239-00800 Africa/Abidjan MM +1647+09610 Asia/Yangon MN +4755+10653 Asia/Ulaanbaatar Mongolia (most areas) MN +4801+09139 Asia/Hovd Bayan-Olgiy, Govi-Altai, Hovd, Uvs, Zavkhan MN +4804+11430 Asia/Choibalsan Dornod, Sukhbaatar MO +221150+1133230 Asia/Macau -MP +1512+14545 Pacific/Saipan +MP +1512+14545 Pacific/Guam MQ +1436-06105 America/Martinique -MR +1806-01557 Africa/Nouakchott -MS +1643-06213 America/Montserrat +MR +1806-01557 Africa/Abidjan +MS +1643-06213 America/Port_of_Spain MT +3554+01431 Europe/Malta MU -2010+05730 Indian/Mauritius MV +0410+07330 Indian/Maldives -MW -1547+03500 Africa/Blantyre +MW -1547+03500 Africa/Maputo MX +1924-09909 America/Mexico_City Central Time MX +2105-08646 America/Cancun Eastern Standard Time - Quintana Roo MX +2058-08937 America/Merida Central Time - Campeche, Yucatan @@ -293,7 +297,7 @@ MY +0133+11020 Asia/Kuching Sabah, Sarawak MZ -2558+03235 Africa/Maputo NA -2234+01706 Africa/Windhoek NC -2216+16627 Pacific/Noumea -NE +1331+00207 Africa/Niamey +NE +1331+00207 Africa/Lagos NF -2903+16758 Pacific/Norfolk NG +0627+00324 Africa/Lagos NI +1209-08617 America/Managua @@ -304,7 +308,7 @@ NR -0031+16655 Pacific/Nauru NU -1901-16955 Pacific/Niue NZ -3652+17446 Pacific/Auckland New Zealand (most areas) NZ -4357-17633 Pacific/Chatham Chatham Islands -OM +2336+05835 Asia/Muscat +OM +2336+05835 Asia/Dubai PA +0858-07932 America/Panama PE -1203-07703 America/Lima PF -1732-14934 Pacific/Tahiti Society Islands @@ -359,32 +363,32 @@ RU +4658+14242 Asia/Sakhalin MSK+08 - Sakhalin Island RU +6728+15343 Asia/Srednekolymsk MSK+08 - Sakha (E); North Kuril Is RU +5301+15839 Asia/Kamchatka MSK+09 - Kamchatka RU +6445+17729 Asia/Anadyr MSK+09 - Bering Sea -RW -0157+03004 Africa/Kigali +RW -0157+03004 Africa/Maputo SA +2438+04643 Asia/Riyadh SB -0932+16012 Pacific/Guadalcanal SC -0440+05528 Indian/Mahe SD +1536+03232 Africa/Khartoum SE +5920+01803 Europe/Stockholm SG +0117+10351 Asia/Singapore -SH -1555-00542 Atlantic/St_Helena -SI +4603+01431 Europe/Ljubljana -SJ +7800+01600 Arctic/Longyearbyen -SK +4809+01707 Europe/Bratislava -SL +0830-01315 Africa/Freetown -SM +4355+01228 Europe/San_Marino -SN +1440-01726 Africa/Dakar -SO +0204+04522 Africa/Mogadishu +SH -1555-00542 Africa/Abidjan +SI +4603+01431 Europe/Belgrade +SJ +7800+01600 Europe/Oslo +SK +4809+01707 Europe/Prague +SL +0830-01315 Africa/Abidjan +SM +4355+01228 Europe/Rome +SN +1440-01726 Africa/Abidjan +SO +0204+04522 Africa/Nairobi SR +0550-05510 America/Paramaribo SS +0451+03137 Africa/Juba ST +0020+00644 Africa/Sao_Tome SV +1342-08912 America/El_Salvador -SX +180305-0630250 America/Lower_Princes +SX +180305-0630250 America/Curacao SY +3330+03618 Asia/Damascus -SZ -2618+03106 Africa/Mbabane +SZ -2618+03106 Africa/Johannesburg TC +2128-07108 America/Grand_Turk TD +1207+01503 Africa/Ndjamena TF -492110+0701303 Indian/Kerguelen -TG +0608+00113 Africa/Lome +TG +0608+00113 Africa/Abidjan TH +1345+10031 Asia/Bangkok TJ +3835+06848 Asia/Dushanbe TK -0922-17114 Pacific/Fakaofo @@ -396,12 +400,12 @@ TR +4101+02858 Europe/Istanbul TT +1039-06131 America/Port_of_Spain TV -0831+17913 Pacific/Funafuti TW +2503+12130 Asia/Taipei -TZ -0648+03917 Africa/Dar_es_Salaam +TZ -0648+03917 Africa/Nairobi UA +5026+03031 Europe/Kiev Ukraine (most areas) UA +4837+02218 Europe/Uzhgorod Transcarpathia UA +4750+03510 Europe/Zaporozhye Zaporozhye and east Lugansk -UG +0019+03225 Africa/Kampala -UM +2813-17722 Pacific/Midway Midway Islands +UG +0019+03225 Africa/Nairobi +UM +2813-17722 Pacific/Pago_Pago Midway Islands UM +1917+16637 Pacific/Wake Wake Island US +404251-0740023 America/New_York Eastern (most areas) US +421953-0830245 America/Detroit Eastern - MI (most areas) @@ -435,17 +439,18 @@ US +211825-1575130 Pacific/Honolulu Hawaii UY -345433-0561245 America/Montevideo UZ +3940+06648 Asia/Samarkand Uzbekistan (west) UZ +4120+06918 Asia/Tashkent Uzbekistan (east) -VA +415408+0122711 Europe/Vatican -VC +1309-06114 America/St_Vincent +VA +415408+0122711 Europe/Rome +VC +1309-06114 America/Port_of_Spain VE +1030-06656 America/Caracas -VG +1827-06437 America/Tortola -VI +1821-06456 America/St_Thomas -VN +1045+10640 Asia/Ho_Chi_Minh +VG +1827-06437 America/Port_of_Spain +VI +1821-06456 America/Port_of_Spain +VN +1045+10640 Asia/Bangkok Vietnam (north) +VN +1045+10640 Asia/Ho_Chi_Minh Vietnam (south) VU -1740+16825 Pacific/Efate WF -1318-17610 Pacific/Wallis WS -1350-17144 Pacific/Apia -YE +1245+04512 Asia/Aden -YT -1247+04514 Indian/Mayotte +YE +1245+04512 Asia/Riyadh +YT -1247+04514 Africa/Nairobi ZA -2615+02800 Africa/Johannesburg -ZM -1525+02817 Africa/Lusaka -ZW -1750+03103 Africa/Harare +ZM -1525+02817 Africa/Maputo +ZW -1750+03103 Africa/Maputo -- 2.27.0

21 80

Re: [tz] Vanguard vs. "main" vs. rearguard
by Paul Eggert June 9, 2021

June 9, 2021

On 5/20/21 10:50 AM, Kerry Shetline wrote: > Is there a particular reason that the following situation is handled with bespoke awk processing: The goal was to keep the data source simple, and put hacks into ziguard.awk when that's easy. I would rather not have these hacks bleed into the data source. > It would be great if the special comments would be all one needed to parse the data for rearguard, main, or vanguard. I see where you're coming from, but that's not the goal here. I didn't want to invent a preprocessor for zic, creating technology that would have to be documented and supported and have backwards-compatibility problems of its own. The vanguard/main/rearguard stuff is just a hopefully-temporary hack that, once it evaporates, will require zero maintenance. By the way, is anybody still using rearguard format? If not, perhaps it's time to retire this stuff now. (That would save us all the hassle of conversations like this one. :-)

4 7

[PROPOSED] * northamerica: Comment on Attu+Kiska 1942/3.
by Paul Eggert May 28, 2021

May 28, 2021

--- northamerica | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/northamerica b/northamerica index 7edd8ef..a2f2b43 100644 --- a/northamerica +++ b/northamerica @@ -729,7 +729,11 @@ Zone America/Adak 12:13:22 - LMT 1867 Oct 19 12:44:35 -11:00 US B%sT 1983 Oct 30 2:00 -10:00 US AH%sT 1983 Nov 30 -10:00 US H%sT -# The following switches don't quite make our 1970 cutoff. +# The following switches don't make our 1970 cutoff. +# +# Kiska observed Tokyo date and time during Japanese occupation from +# 1942-06-06 to 1943-07-29, and similarly for Attu from 1942-06-07 to +# 1943-05-29 (all dates American). Both islands are now uninhabited. # # Shanks writes that part of southwest Alaska (e.g. Aniak) # switched from -11:00 to -10:00 on 1968-09-22 at 02:00, -- 2.27.0

1 0

[PROPOSED] Replace Pacific/Enderbury with Pacific/Kanton
by Paul Eggert May 28, 2021

May 28, 2021

When I added Pacific/Enderbury in 1993, I thought it was the most-populous location in its timezone. I was wrong - it has been uninhabited since 1942. I discovered my mistake this week when doing the recent timezone-coalescing changes. It shouldn’t be surprising that this problem has not been reported, as only two dozen people live in the timezone, they’re rotated in and out, and they likely don’t have a good Internet connection. Leaving the name alone wouldn’t work because Pacific/Enderbury should be at -00 now, our convention for uninhabited locations. So, replace the name with Pacific/Kanton. By strange coincidence, Kanton has been in the news recently, for reasons similar to why Enderbury was in the news in the 1930s; see: https://www.thedrive.com/the-war-zone/40471/china-wants-to-revive-a-strateg… * NEWS: Mention this. * australasia, zone.tab, zone1970.tab (Pacific/Kanton): New zone, replacing ... * backward (Pacific/Enderbury): New backward-compatibility link * backzone: Copy of old data, with fixes for uninhabited times, which includes the current time. --- NEWS | 13 +++++++++++-- australasia | 19 ++++++++++++++++++- backward | 1 + backzone | 12 ++++++++++++ zone.tab | 2 +- zone1970.tab | 2 +- 6 files changed, 44 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index 04c45e9..53890a7 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,13 @@ News for the tz database Unreleased, experimental changes + Changes to zone name + + Rename Pacific/Enderbury to Pacific/Kanton. When we added + Enderbury in 1993, we did not know that it is uninhabited and that + Kanton (population two dozen) is the only inhabited location in + that timezone. The old name is now a backward-compatility link. + Changes to past timestamps Correct many pre-1993 transitions, fixing entries originally @@ -14,11 +21,13 @@ Unreleased, experimental changes - Guyana: corrected LMT for Georgetown; the introduction of standard time in 1911, not 1915; and corrections to 1975 and 1992 transitions + - Kanton: uninhabited before 1937-08-31 - Niue: observed -11:20 in 1951-1978 - Portugal: DST was observed in 1950 - Tonga: adopted standard time in 1945 not 1901, and moved from +12:20 to +13 in 1961 not 1941 Additional fixes to entries in the 'backzone' file include: + - Enderbury: inhabited only 1860/1885 and 1938-03-06/1942-02-09 - The Gambia: 1933 and 1942 transitions - Malawi: several 1911 through 1925 transitions - Sierra Leone: several 1913 through 1941 transitions, and DST @@ -955,8 +964,8 @@ Release 2018d - 2018-03-22 07:05:46 -0700 Institute in Montevideo. (Thanks to Jeremie Bonjour, Tim Parenti, and Michael Deckers.) - Enderbury and Kiritimati skipped New Year's Eve 1994, not - New Year's Day 1995. (Thanks to Kerry Shetline.) + East Kiribati skipped New Year's Eve 1994, not New Year's Day 1995. + (Thanks to Kerry Shetline.) Fix the 1912-01-01 transition for Portugal and its colonies. This transition was at 00:00 according to the new UT offset, not diff --git a/australasia b/australasia index 8e952ad..5cbc0c8 100644 --- a/australasia +++ b/australasia @@ -457,7 +457,7 @@ Zone Pacific/Guam -14:21:00 - LMT 1844 Dec 31 # Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Pacific/Tarawa 11:32:04 - LMT 1901 # Bairiki 12:00 - +12 -Zone Pacific/Enderbury -11:24:20 - LMT 1901 +Zone Pacific/Kanton 0 - -00 1937 Aug 31 -12:00 - -12 1979 Oct -11:00 - -11 1994 Dec 31 13:00 - +13 @@ -1735,6 +1735,23 @@ Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila # One source for this is page 202 of: Bartky IR. One Time Fits All: # The Campaigns for Global Uniformity (2007). +# Kanton + +# From Paul Eggert (2021-05-27): +# Kiribati's +13 timezone is represented by Kanton, its only populated +# island. (It was formerly spelled "Canton", but Gilbertese lacks "C".) +# Kanton was settled on 1937-08-31 by two British radio operators +# <https://history.state.gov/historicaldocuments/frus1937v02/d94>; +# Americans came the next year and built an airfield, partly to +# establish airline service and perhaps partly anticipating the +# next war. Aside from the war, the airfield was used by commercial +# airlines until long-range jets became standard; although currently +# for emergency use only, China says it is considering rebuilding the +# airfield for high-end niche tourism. Kanton has about two dozen +# people, caretakers who rotate in from the rest of Kiribati in 2-5 +# year shifts, and who use some of the leftover structures +# <http://pipa.neaq.org/2012/06/images-of-kanton-island.html>. + # Kwajalein # From an AP article (1993-08-22): diff --git a/backward b/backward index 9e22754..0fec5e4 100644 --- a/backward +++ b/backward @@ -208,6 +208,7 @@ Link Pacific/Chatham NZ-CHAT Link America/Denver Navajo Link Asia/Shanghai PRC Link Pacific/Port_Moresby Pacific/Chuuk +Link Pacific/Kanton Pacific/Enderbury Link Pacific/Tarawa Pacific/Funafuti Link Pacific/Honolulu Pacific/Johnston Link Pacific/Tarawa Pacific/Majuro diff --git a/backzone b/backzone index f5b20fa..4d69a3f 100644 --- a/backzone +++ b/backzone @@ -1566,6 +1566,18 @@ Zone Pacific/Chuuk -13:52:52 - LMT 1844 Dec 31 Link Pacific/Chuuk Pacific/Truk Link Pacific/Chuuk Pacific/Yap +# Phoenix Islands, Kiribati +# From Paul Eggert (2021-05-27): +# Enderbury was inhabited 1860/1880s to mine guano, and 1938-03-06/1942-02-09 +# for aviation (ostensibly commercial, but military uses foreseen). +# The 19th-century dates are approximate. See Pacific/Kanton for +# the currently-inhabited representative for this timezone. +Zone Pacific/Enderbury 0 - -00 1860 + -11:24:20 - LMT 1885 + 0 - -00 1938 Mar 6 + -12:00 - -12 1942 Feb 9 + 0 - -00 + # Tuvalu Zone Pacific/Funafuti 11:56:52 - LMT 1901 12:00 - +12 diff --git a/zone.tab b/zone.tab index cbf4b91..e2062cf 100644 --- a/zone.tab +++ b/zone.tab @@ -232,7 +232,7 @@ KE -0117+03649 Africa/Nairobi KG +4254+07436 Asia/Bishkek KH +1133+10455 Asia/Bangkok KI +0125+17300 Pacific/Tarawa Gilbert Islands -KI -0308-17105 Pacific/Enderbury Phoenix Islands +KI -0247-17143 Pacific/Kanton Phoenix Islands KI +0152-15720 Pacific/Kiritimati Line Islands KM -1141+04316 Africa/Nairobi KN +1718-06243 America/Puerto_Rico diff --git a/zone1970.tab b/zone1970.tab index a02d94d..6b9d288 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -188,7 +188,7 @@ JP +353916+1394441 Asia/Tokyo KE,DJ,ER,ET,KM,MG,SO,TZ,UG,YT -0117+03649 Africa/Nairobi KG +4254+07436 Asia/Bishkek KI,MH,TV,UM,WF +0125+17300 Pacific/Tarawa Gilberts, Marshalls, Tuvalu, Wallis & Futuna, Wake -KI -0308-17105 Pacific/Enderbury Phoenix Islands +KI -0247-17143 Pacific/Kanton Phoenix Islands KI +0152-15720 Pacific/Kiritimati Line Islands KP +3901+12545 Asia/Pyongyang KR +3733+12658 Asia/Seoul -- 2.27.0

1 0

So, about those LMT offsets
by Tom Lane May 24, 2021

May 24, 2021

As long as we're considering decreasing the historical fidelity of assorted pre-1970 timestamps, I'd like to make a modest suggestion: forget all the "LMT" offsets for years before standardized timezones prevailed, and just assume that the oldest documented standard-time offset in each zone goes back indefinitely far. The reason I suggest this is that we regularly get questions on the Postgres lists from novices who are confused by this behavior (pardon the SQL-isms): postgres=# set timezone = 'UTC'; SET postgres=# select timestamptz '1884-01-01 12:00 America/New_York'; timestamptz ------------------------ 1884-01-01 17:00:00+00 (1 row) This is, of course, saying that noon in New York translates to 1700 UT ... postgres=# select timestamptz '1883-01-01 12:00 America/New_York'; timestamptz ------------------------ 1883-01-01 16:56:02+00 (1 row) ... uh, what? The novices are definitely not expecting that, and they don't find it helpful. We have to explain it away as "that's what tzdb says", but it's still unhelpful. It's even sillier when you consider postgres=# select timestamptz '1752-09-10 12:00 America/New_York'; timestamptz ------------------------ 1752-09-10 16:56:02+00 (1 row) as calendar experts will recall that no such date was recognized in the British colonies. So although it's debatable whether we even know what day it is, for sure we know the UTC offset to the second. So basically, if we're willing to use proleptic Gregorian calendar for years before anyone was actually using that calendar, it's not very clear why we shouldn't use proleptic standard time too. I'd be willing to consider implementing that behavior in Postgres if I could tell (a) that a given offset is LMT not standardized time and (b) what the zone's oldest standardized offset is. But AFAICT that's not possible without mucking with the behavior of localtime.c, which I'd much prefer not to. So ... how about just dropping this oddity from the source data? regards, tom lane

9 17

Re: [tz] Vanguard vs. "main" vs. rearguard
by Paul Eggert May 20, 2021

May 20, 2021

On 5/19/21 4:35 PM, Kerry Shetline wrote: > Can you show me an example of what the format of a three-mode set of data would look like? I doubt it. I don't think we've ever done it. If we were to do it (I hope not), we'd probably have to change ziguard.awk to implement it. There may be an expectation here that the vanguard/main/rearguard formats are well-specified. They're not. They're purely a hack, they're implemented only by ziguard.awk, we don't even need vanguard any more, and I hope the need for rearguard goes away as well. Perhaps in the future we'll need to do this sort of delayed-implementation again; when that happens we may do it in an entirely different way.

1 0

Re: [tz] Vanguard vs. "main" vs. rearguard
by Kerry Shetline May 19, 2021

May 19, 2021

I think I’ve answered my own question. First of all, I can select between the various versions by reading from one of the vanguard.zi, rearguard.zi, or main.zi files. (I had been reading all of the files like africa, europe, northamerica, etc., separately at first.) Then whatever I want or don’t want to use is already commented out or uncommented as needed. Secondly, even if I’m reading those other files rather than the .zi files, I gather that, in my Europe/Dublin example, the vanguard and main data are the same, but if rearguard and main had been the same, it would be the vanguard section that was commented out, and the rearguard section would have been uncommented. I take it from this that, for any given vanguard/rearguard section, you can’t have all three formats defined differently, but rather “main” will either be identical to one of vanguard or rearguard.

2 1

Vanguard vs. "main" vs. rearguard
by Kerry Shetline May 19, 2021

May 19, 2021

As far as I can tell, their are only four sections in the current tzdb marked as vanguard/rearguard, two sections in the europe for Europe/Dublin and Europe/Prague, and two in the africa file for Africa/Windhoek. What I’m confused about is references I’ve seen to a “main” format, like this: > 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… At least from the current examples, it looks like one would have to choose either Vanguard or Rearguard, period. There is no middle ground of “main” when I look at a case like this below: # Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Europe/Dublin -0:25:00 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00s -0:25:21 1:00 IST 1916 Oct 1 2:00s 0:00 GB-Eire %s 1921 Dec 6 # independence 0:00 GB-Eire GMT/IST 1940 Feb 25 2:00s 0:00 1:00 IST 1946 Oct 6 2:00s 0:00 - GMT 1947 Mar 16 2:00s 0:00 1:00 IST 1947 Nov 2 2:00s 0:00 - GMT 1948 Apr 18 2:00s 0:00 GB-Eire GMT/IST 1968 Oct 27 # Vanguard section, for zic and other parsers that support negative DST. 1:00 Eire IST/GMT # Rearguard section, for parsers lacking negative DST; see ziguard.awk. # 1:00 - IST 1971 Oct 31 2:00u # 0:00 GB-Eire GMT/IST 1996 # 0:00 EU GMT/IST # End of rearguard section. If there is a middle ground here, neither Vanguard or Rearguard, what is it? And if there are no current examples with such a middle ground, what would a middle ground of neither Vanguard or Rearguard look like?

1 0

DKIM misconfiguration of this mailing list
by Yves Goergen May 18, 2021

May 18, 2021

Hello, I'm having trouble receiving messages from this mailing list because many of them have a broken DKIM signature. I guess that's because the mailing list is not configured properly to survive in today's e-mail world. If a message with a DKIM signature is sent to this list (like mine), they're forwarded to all subscribers without correcting that signature but at the same time modifying subject, body or sender. Maybe somebody would like to take a look at that to ensure that messages from this list can still be delivered. This is an article I found about the topic, it might be helpful in fixing the problems. https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html I'm writing to the list directly because list owners never seem to respond to such issues. Several other mailing lists I'm subscribed to have the same issue. If you'd like me to read your reply, please CC me as well to make sure your message arrives here. -Yves

2 1

Time Zone and Daylight Saving Time Customer Service Stories
by Brian Inglis May 13, 2021

May 13, 2021

Just came across a source of articles about Time Zones and Daylight Saving Time from the perspective of Customer Service, or other staff dealing with them, across the globe, at NotAlwaysRight.com. The tone reminds me of articles in The Register. My attention was first drawn by a series of articles entitled "No Fortitude for Longitude" and I have attached some links to that series and to results from search queries on the topics. -- 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. [Data in binary units and prefixes, physical quantities in SI.]

1 0

Re: [tz] IANA .tar.gz files with incorrect checksums
by Paul Eggert May 13, 2021

May 13, 2021

On 5/12/21 4:30 PM, Peter Adelman wrote: > I am contacting you to let you know that some of the old releases of the > IANA time zones databases are missing (or perhaps have incorrect) > checksums in their .tars. The Julia language uses the IANA Time Zone > Databases for its TimeZones.jl package, and in the language's most > recent minor release (1.6) they started failing extractions where the > header checksum didn't match the standard. > > Here are two related tickets: > * https://github.com/JuliaTime/TimeZones.jl/issues/325 > <https://github.com/JuliaTime/TimeZones.jl/issues/325> > * https://github.com/JuliaIO/Tar.jl/issues/111 > <https://github.com/JuliaIO/Tar.jl/issues/111> > > Of the tzdata___.tar.gzs that I have looked at (I think that I explored > all of them while trying to build my Julia package), these have > problematic tar checksums: > 93g > 94a/b/d/e/f/h > 95b/c/d/e/f/g/h/i/k/l/m > 96a/b/c/d/e/h/i > 1996n > 1997b/c > 1999f > > I checked two of them by hand (1997b and one other that I didn't note) > and both had blank header checksum bytes (0). ( > https://www.gnu.org/software/tar/manual/html_node/Standard.html > <https://www.gnu.org/software/tar/manual/html_node/Standard.html> ) > > Anyway, the glory of standards releases is that they don't change so > obviously I understand not changing it, but I thought I'd reach out with > the information anyway. Those old tarballs were built by old SunOS tar, which computed some checksums incompatibly with POSIX <https://www.gnu.org/software/tar/manual/html_node/Checksumming.html> and which put leading spaces into numeric fields, contra POSIX. GNU Tar is generous and accepts these old tarballs, but perhaps TimeZones.jl has never had to deal with old SunOS tar, or maybe Julia's tarball-extracting library has a "let's be generous in what we accept" option that TimeZones.jl could enable. I installed the attached to tz-link to document some of this. This patch assumes that 1999g and later are OK (I haven't checked this).

2 1

About missing country in your Time Zone Database?
by Sadiku, Besnik May 11, 2021

May 11, 2021

Hello there IANA personnel, I am currently taking a Python class and learning about using Time Zone and noticed that Kosovo is missing in the Time Zone Database list. Please, I would to request to add in your Time Zone Database the country KOSOVO and its capital PRISHTINA? Thank you and I appreciated. Sincerely, ******************************************* * Besnik Sadiku, BS in M.C.S. and Web Dev. & Admin. * Business Analyst 2 / Certified * Office: (608) 741-5629 * Cell: (262) 473-9511 * e-mail: bsadiku(a)mhemail.org<mailto:bsadiku@mhemail.org> ******************************************* [cid:image001.png@01D201CE.DEAEBCD0]

4 6

(no subject)
by Cool Gab19 May 11, 2021

May 11, 2021

can you add UTC+15:00 "Future Standard Time" time zone it was 1 hour ahead from all 24 hour world time zone and it doesn't have any current region or countries same to Universal Time which can be used anywhere and i do really know that we need calculations for these but please put this thing on your database so i can able to see this on my devices settings.

2 1

[PATCH] Definite article for Bahamas, Gambia
by Paul Eggert May 10, 2021

May 10, 2021

* NEWS, backzone, iso3166.tab, northamerica: Put "The" in front of "Bahamas" and "Gambia"; this is a common style and is preferred by the respective governments. --- NEWS | 4 ++-- backzone | 2 +- iso3166.tab | 4 ++-- northamerica | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index 67fb000..6d1cd09 100644 --- a/NEWS +++ b/NEWS @@ -19,7 +19,7 @@ Unreleased, experimental changes - Tonga: adopted standard time in 1945 not 1901, and moved from +12:20 to +13 in 1961 not 1941 Additional fixes to entries in the 'backzone' file include: - - Gambia: 1933 and 1942 transitions + - The Gambia: 1933 and 1942 transitions - Malawi: several 1911 through 1925 transitions - Sierra Leone: several 1913 through 1941 transitions, and DST was NOT observed in 1957 through 1962 @@ -148,7 +148,7 @@ Release 2020e - 2020-12-22 15:14:34 -0800 Correct many pre-1986 transitions, fixing entries originally derived from Shanks. The fixes include: - Australia: several 1917 through 1971 transitions - - Bahamas: several 1941 through 1945 transitions + - The Bahamas: several 1941 through 1945 transitions - Bermuda: several 1917 through 1956 transitions - Belize: several 1942 through 1968 transitions - Ghana: several 1915 through 1956 transitions diff --git a/backzone b/backzone index 9ebf9d2..8e4f97a 100644 --- a/backzone +++ b/backzone @@ -101,7 +101,7 @@ Zone Africa/Bamako -0:32:00 - LMT 1912 Zone Africa/Bangui 1:14:20 - LMT 1912 1:00 - WAT -# Gambia +# The Gambia # From P Chan (2020-12-09): # Standard time of GMT-1 was adopted on 1933-04-01. On 1942-02-01, GMT was # adopted as a war time measure. This was made permanent in 1946. diff --git a/iso3166.tab b/iso3166.tab index a4ff61a..e7ab54d 100644 --- a/iso3166.tab +++ b/iso3166.tab @@ -54,7 +54,7 @@ BN Brunei BO Bolivia BQ Caribbean NL BR Brazil -BS Bahamas +BS The Bahamas BT Bhutan BV Bouvet Island BW Botswana @@ -107,7 +107,7 @@ GG Guernsey GH Ghana GI Gibraltar GL Greenland -GM Gambia +GM The Gambia GN Guinea GP Guadeloupe GQ Equatorial Guinea diff --git a/northamerica b/northamerica index c7d9274..b27311a 100644 --- a/northamerica +++ b/northamerica @@ -2931,7 +2931,7 @@ Zone America/Tijuana -7:48:04 - LMT 1922 Jan 1 0:11:56 # Antigua and Barbuda # See America/Port_of_Spain. -# Bahamas +# The Bahamas # # For 1899 Milne gives -5:09:29.5; round that. # -- 2.27.0

2 1

[PROPOSED 1/2] Omit duplicate Link lines in ziguard output
by Paul Eggert May 10, 2021

May 10, 2021

* ziguard.awk: Later Link lines now comment out earlier ones. Formerly, we relied on ‘zic’ to ignore the earlier lines, but this made for more-confusing ziguard output. This change does not affect zic’s output. --- ziguard.awk | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/ziguard.awk b/ziguard.awk index 7d6f7c9..6888c27 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -114,15 +114,16 @@ DATAFORM != "main" { } } -# If a Link line is followed by a Zone line for the same data, comment +# If a Link line is followed by a Link or Zone line for the same data, comment # out the Link line. This can happen if backzone overrides a Link -# with a Zone. -/^Link/ { - linkline[$3] = NR -} +# with a Zone or a different Link. /^Zone/ { sub(/^Link/, "#Link", line[linkline[$2]]) } +/^Link/ { + sub(/^Link/, "#Link", line[linkline[$3]]) + linkline[$3] = NR +} { line[NR] = $0 } -- 2.27.0

1 1