May 2022 - tz - lists.iana.org

(no subject)
by Cool Gab19 05 Sep '24

05 Sep '24

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 7

Re: [tz] Morocco : Ramdan Time Change 2021
by Paul Eggert 15 Mar '23

15 Mar '23

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 14 Nov '22

14 Nov '22

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 02 Nov '22

02 Nov '22

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

question re zone America/Punta_Arenas in Chile
by Alois Treindl 06 Jul '22

06 Jul '22

In 2016, Chile introduced a new time zone for it south-most province Magallanes, and for this reason a new zone Zone America/Punta_Arenas -4:43:40 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 -5:00 - -05 1916 Jul 1 -4:42:46 - SMT 1918 Sep 10 -4:00 - -04 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile -05/-04 1932 Sep 1 -4:00 - -04 1942 Jun 1 -5:00 - -05 1942 Aug 1 -4:00 - -04 1947 Apr 1 -5:00 - -05 1947 May 21 23:00 -4:00 Chile -04/-03 2016 Dec 4 -3:00 - -03 has been created. before it followed Zone America/Santiago -4:42:46 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - -05 1916 Jul 1 -4:42:46 - SMT 1918 Sep 10 -4:00 - -04 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile -05/-04 1932 Sep 1 -4:00 - -04 1942 Jun 1 -5:00 - -05 1942 Aug 1 -4:00 - -04 1946 Jul 15 -4:00 1:00 -03 1946 Sep 1 # central Chile -4:00 - -04 1947 Apr 1 -5:00 - -05 1947 May 21 23:00 -4:00 Chile -04/-03 The new zone differs from zone Santiago at two points: - it does not have the 1946/47 DST - it differs from 2016 Dec 4, the reason of its creation. I wonder on which basis the 1946/47 DST was left out for Puntas_Arenas? Is that documented somewhere? The main reason why I ask: My two sources Shanks and Gabriel have always claimed that zone America/Santiago is only good for the province of Santiago, but that the rest of Chile did not have DST between 1927 and 1932. This is why in my private pre-1970 TZ extension I have an extra zone for 'rest of Chile besides Santiago' Zone America/Chile/Antofagasta -4:41:36 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - -05 1916 Jul 1 -4:42:46 - SMT 1918 Sep 10 -4:00 - -04 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 - -05 1932 Sep 1 0 follow America/Santiago which leaves out the 1927-1932 DST. It has however the 1946/47 DST. I have another zone, based on Shanks and Gabriel, for Vaparaiso, which leaves out the 1946/47 DST, but has a one-summer 1931/1932 DST. Zone America/Chile/Vina_del_Mar -4:46:16 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 # Santiago Mean Time -5:00 - -05 1916 Jul 1 -4:42:46 - SMT 1918 Sep 10 -4:00 - -04 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 - -05 1931 Sep 1 -5:00 Chile -05/-04 1932 Sep 1 -4:00 - -04 1942 Jun 1 -5:00 - -05 1942 Aug 1 -4:00 - -04 1947 Apr 1 0 follow America/Santiago Sadly, I have currently no sources for that beyond Shanks and Gabriel. We would need local newspaper archives from a non-Santiago newspaper for 1927-1932 to confirm. But it this is true, we have to assume that province Magellanes behaved like 'the rest of Chile' and not like Santiago before the split in 2016. That means that it should be: Zone America/Punta_Arenas -4:43:40 - LMT 1890 -4:42:46 - SMT 1910 Jan 10 -5:00 - -05 1916 Jul 1 -4:42:46 - SMT 1918 Sep 10 -4:00 - -04 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 - -05 1932 Sep 1 -4:00 - -04 1942 Jun 1 -5:00 - -05 1942 Aug 1 -4:00 - -04 1947 Apr 1 -5:00 - -05 1947 May 21 23:00 -4:00 Chile -04/-03 2016 Dec 4 -3:00 - -03

4 6

the tzdb information schema
by Michael H Deckers 04 Jul '22

04 Jul '22

Some recent difficulties with tzdb updates have led me to consider how they could have been avoided. • The fact that two timezones agree since 1970 is not represented independently from the data of each timezone. This leads to "update anomalies" well-known from database theory. For instance, before Africa/Khartoum switched to UTC - 02 h in 2017, Africa/Juba was a link (in the file africa) to Africa/Khartoum. After the switch, new Zone data for Africa/Juba had to appear in the file africa. Actually, Zone data for Africa/Juba had survived in the file backzone but this was overlooked, so that we had Zone data for Africa/Juba in both files africa and backzone from 2017c until 2018b, and these Zone data did not even agree. And all this happened for Africa/Juba even though civil time in Juba was not changed at all at the time. It appears that this error would not have happened if all African Zone data had been kept in the file africa (rather than in africa and in backzone) -- it was not the Zone data of Africa/Juba that had changed, but only the fact that Africa/Juba ws merged with Africa/Khartoum because their Zone data agreed since 1970. Unfortunately, this fact was not (and still is not) representable as an independently changeable item in tzdb. • Most of the Zone data currently contained in the file backzone have in earlier versions been stored in the "continental" files (africa, antarctica, asia, australasia, europe, northamerica, southamerica), and the reason why they are in backzone is that their Zone data agree with other Zone data since 1970. And since this may well change in the future, we have to keep these Zone data in backzone current. The file backzone is an integral part of the tzdb data, not just a container for additional data of lesser quality. The quality of any Zone data (and any Rule data) in tzdb should always be "to the best of our current knowledge" -- it just does not make sense to keep Zone data in tzdb that are not updated when we acquire relevant new information for them. Thus we should get rid of Zone data for Argentina/Rosario etc (or else update them); keeping data that are known to be wrong is not only useless, it is an invitation for consequential errors. • Letting derived data (such as whether two timezones should be merged because they agree since 1970) decide about the storage location of the Zone data for a timezone not only implies unnecessary data moves upon data updates, it may also disrupt commentary text and its references. Easily understandable comments (such as which facts were deduced from which document) are crucial for later updates, where the effect of a newly found document has to be determined, often after several years, and likely by a different contributor. • The fact that two timezones agree since 1970 has nothing to do with the fact that some timezones have changed their names, with the old names being kept as Links to the new names. Currently, however, Links representing one or both facts are kept in the same file backward, and cannot be distinguished. This leads to information loss and update anomalies: Currently, the file backward has a Link from Africa/Asmera to Africa/Nairobi -- the information that Asmera is an outdated spelling of Asmara can only be found in the file backzone. The name America/Virgin had been replaced by America/St_Thomas in version 95k, and this fact could be seen in the file backward until 2021a when this information was lost. It reappeared (in backzone) only in version 2021c. Keeping one type of information (spelling changes) in different locations (files backward or backzone) depending on an independent condition (that may even change over time) certainly causes unnecessary maintenance effort. While some of these points may sound like theoretical claims for normal forms as taught in computer science, my point here is only practical simplicity: each basic fact to be recorded in tzdb should have its obvious place where it is stored and where it can be looked up and updated; and updates of independent facts should be possible without mutual side effects. This appears to be a necessity for a collaborative project. Last Saturday, Paul Eggert has very nicely summarized the history and some of the guiding principles of tzdb. It is largely due to his immense work on the maintenance and evolvement of tzdb that the tzdb system was such a tremendous success in its first 30 years. As a means for the success over the next 30 years, I propose a simplification of the tzdb schema, so as to avoid the update anomalies described above, and thus decrease the maintenance burden, currently mainly shouldered by Paul. The information schema used in the fork produced by Stephen Colebourne is already much simpler, and it is apparently what is needed by several power users contributing to the widespread success of tzdb. Michael Deckers.

2 1

Etc/GMT+nn and Etc/GMT-nn not working since zic 2021d
by Peter Krefting 30 Jun '22

30 Jun '22

Hi! I am creating timezone data for an embedded device, and with space as a premium I run zic with the -r parameter to cut off all time change information from before the software release date, as this is not relevant for the system. Since commit 5f06f9a3182d2c2942be1b678e4defa9c7400653 (included in 2021d), this causes the Etc/GMT+xx and Etc/GMT-xx timezones not to work, they always report GMT ("-00"): ~ # TZ=Europe/Oslo date Mon Mar 21 13:08:32 CET 2022 ~ # TZ=Europe/London date Mon Mar 21 12:08:36 GMT 2022 ~ # TZ=Etc/GMT+1 date Mon Mar 21 12:08:43 -00 2022 ~ # TZ=Etc/GMT+2 date Mon Mar 21 12:08:45 -00 2022 This is particularly severe for our devices since previous versions of our software only supported UTC offsets, and these are automatically updated to these GMT+xx and GMT-xx timezones on update, so many of our customers are expected to have these zones configured. We are running with "-r cutoff -b fat", where cutoff depends on the release date, and the embedded software currenlty is using GNU libc 2.20. Reverting 5f06f9a3182d2c2942be1b678e4defa9c7400653 fixes the issue for us, but is probably not the correct approach. -- \\// Peter - http://www.softwolves.pp.se/

3 6

Kyiv not Kiev error
by Євген Доманський 24 Jun '22

24 Jun '22

Dear All There is an error in name of the capital city of Ukraine - Kiev ('Київ' in Ukrainian language). Kiev is the transliteration of the city name from Russian language. The only correct transliteration is Kyiv. Please update the name. Best regards. *Yevhen Domanskyi* *Study Coordinator* Department of Oncology and Medical Radiology Dnipro State Medical University 31, Blyzhnya Str., Dnipro, 49102, Ukraine *Mobile*: +380 93 060 26 92 *e-mail: *dom.eugene(a)gmail.com Website: http://www.sitetv.net/ <http:/www.sitetv.net/>

11 26

Change Request: Europe/Kiev to Europe/Kyiv
by Oleksandr Leskiv 23 Jun '22

23 Jun '22

The history of timezones has some existing cases where a specific timezone has been renamed. For example, the *Asia/Calcutta* timezone has been deemed obsolete and replaced by *Asia/Kolkata*. In Ukraine, according to international standards, there is a timezone called *Europe/Kiev*. The capital of Ukraine is officially and internationally should be spelled as "Kyiv". "Kiev" is an incorrect version that emerged a long time before the Soviet Union collapsed in 1991. We have a really large community of programmers that would like to start the process of renaming the Europe/Kiev timezone to Europe/Kyiv. We understand that it will take a long time for everybody to transition, but it has to be done in the long term. Sincerely, Oleksandr. TakeUsEat.

7 10

Historical data for Iran
by Roozbeh Pournader 05 Jun '22

05 Jun '22

Hi, The timezone database currently lists Iran switching to standard time in 1946. I've been doing some research on the history of the adoption of standard time by Iran, and while it's very hard to find much, I found that the correct date is actually 1935. Here's an order from the Cabinet to the rest of the government to switch to Tehran time, which is mentioned to be already at +03:30: https://qavanin.ir/Law/TreeText/180138 Just in case that goes away, I also saved a copy at archive.org: https://web.archive.org/web/20220530111940/https://qavanin.ir/Law/TreeText/… Here's my translation: "Circular on Matching the Hours of Governmental and Official Circles in Provinces Approved 1314/03/22 [=1935-06-13] According to the ruling of the Honorable Cabinet, it is ordered that from now on in all internal provinces of the country, governmental and official circles set their time to match Tehran time (three hours and half before Greenwich). It is required to mind the above order. For Minister of Judiciary, Dr Matin-Daftari" Now, I still haven't found out when Tehran itself switched to +03:30 (let's assume some time earlier in 1935), but it is clear that standard time in Iran started on 1935-06-13 and not 1946. Thanks, Roozbeh

4 7