More than 2 transitions per year for Asia/Gaza & Hebron in 2068+
Hi all, With the latest release (2023d) I'm seeing some surprising output from zdump for the Asia/Gaza & Asia/Hebron zones: $> zdump -v Asia/Hebron ... Asia/Hebron Fri Mar 23 23:59:59 2068 UT = Sat Mar 24 01:59:59 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 24 00:00:00 2068 UT = Sat Mar 24 03:00:00 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 22:59:59 2068 UT = Sat Oct 20 01:59:59 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 23:00:00 2068 UT = Sat Oct 20 01:00:00 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 29 23:59:59 2069 UT = Sat Mar 30 01:59:59 2069 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 30 00:00:00 2069 UT = Sat Mar 30 03:00:00 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 22:59:59 2069 UT = Sat Oct 12 01:59:59 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 23:00:00 2069 UT = Sat Oct 12 01:00:00 2069 EET isdst=0 gmtoff=7200 This pattern of >2 transitions per year continues from that year. Is this correct? It seems awfully weird. Cheers, Dave Rolsky http://blog.urth.org https://github.com/autarch
I don't see anything wrong with that zdump output. It's just two transitions per year. Each transition consumes two output lines, as usual.
Oops, you are right. The weirdness starts in 2072: Asia/Hebron Fri Mar 25 23:59:59 2072 UT = Sat Mar 26 01:59:59 2072 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 26 00:00:00 2072 UT = Sat Mar 26 03:00:00 2072 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Sep 9 22:59:59 2072 UT = Sat Sep 10 01:59:59 2072 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Sep 9 23:00:00 2072 UT = Sat Sep 10 01:00:00 2072 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Oct 14 23:59:59 2072 UT = Sat Oct 15 01:59:59 2072 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Oct 15 00:00:00 2072 UT = Sat Oct 15 03:00:00 2072 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 28 22:59:59 2072 UT = Sat Oct 29 01:59:59 2072 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 28 23:00:00 2072 UT = Sat Oct 29 01:00:00 2072 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 24 23:59:59 2073 UT = Sat Mar 25 01:59:59 2073 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 25 00:00:00 2073 UT = Sat Mar 25 03:00:00 2073 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Sep 1 22:59:59 2073 UT = Sat Sep 2 01:59:59 2073 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Sep 1 23:00:00 2073 UT = Sat Sep 2 01:00:00 2073 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Oct 6 23:59:59 2073 UT = Sat Oct 7 01:59:59 2073 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Oct 7 00:00:00 2073 UT = Sat Oct 7 03:00:00 2073 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 27 22:59:59 2073 UT = Sat Oct 28 01:59:59 2073 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 27 23:00:00 2073 UT = Sat Oct 28 01:00:00 2073 EET isdst=0 gmtoff=7200 By my reading, that's 4 transitions per year. Cheers, Dave Rolsky http://blog.urth.org https://github.com/autarch On Sat, Dec 30, 2023 at 2:08 PM Dave Rolsky <autarch@urth.org> wrote:
Hi all,
With the latest release (2023d) I'm seeing some surprising output from zdump for the Asia/Gaza & Asia/Hebron zones:
$> zdump -v Asia/Hebron ... Asia/Hebron Fri Mar 23 23:59:59 2068 UT = Sat Mar 24 01:59:59 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 24 00:00:00 2068 UT = Sat Mar 24 03:00:00 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 22:59:59 2068 UT = Sat Oct 20 01:59:59 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 23:00:00 2068 UT = Sat Oct 20 01:00:00 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 29 23:59:59 2069 UT = Sat Mar 30 01:59:59 2069 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 30 00:00:00 2069 UT = Sat Mar 30 03:00:00 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 22:59:59 2069 UT = Sat Oct 12 01:59:59 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 23:00:00 2069 UT = Sat Oct 12 01:00:00 2069 EET isdst=0 gmtoff=7200
This pattern of >2 transitions per year continues from that year.
Is this correct? It seems awfully weird.
Cheers,
Dave Rolsky http://blog.urth.org https://github.com/autarch
On Sat, 30 Dec 2023, Dave Rolsky via tz wrote:
Hi all,
With the latest release (2023d) I'm seeing some surprising output from zdump for the Asia/Gaza & Asia/Hebron zones:
$> zdump -v Asia/Hebron ... Asia/Hebron Fri Mar 23 23:59:59 2068 UT = Sat Mar 24 01:59:59 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 24 00:00:00 2068 UT = Sat Mar 24 03:00:00 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 22:59:59 2068 UT = Sat Oct 20 01:59:59 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 23:00:00 2068 UT = Sat Oct 20 01:00:00 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 29 23:59:59 2069 UT = Sat Mar 30 01:59:59 2069 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 30 00:00:00 2069 UT = Sat Mar 30 03:00:00 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 22:59:59 2069 UT = Sat Oct 12 01:59:59 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 23:00:00 2069 UT = Sat Oct 12 01:00:00 2069 EET isdst=0 gmtoff=7200
This pattern of >2 transitions per year continues from that year.
Is this correct? It seems awfully weird.
IIRC, this is to accomodate a temporary-return-to-standard-time for the duration of Ramadan.
Cheers,
Dave Rolsky http://blog.urth.org https://github.com/autarch
!DSPAM:658fb40d15421143672522!
+---------------------+--------------------------+----------------------+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses: | | (Retired) | 1B11 1849 721C 56C8 F63A | paul@whooppee.com | | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoyette@netbsd.org | | & Network Engineer | | pgoyette99@gmail.com | +---------------------+--------------------------+----------------------+
Ah, ok. Thanks for the quick clarification! Cheers, Dave Rolsky http://blog.urth.org https://github.com/autarch On Sat, Dec 30, 2023 at 2:49 PM Paul Goyette <paul@whooppee.com> wrote:
On Sat, 30 Dec 2023, Dave Rolsky via tz wrote:
Hi all,
With the latest release (2023d) I'm seeing some surprising output from zdump for the Asia/Gaza & Asia/Hebron zones:
$> zdump -v Asia/Hebron ... Asia/Hebron Fri Mar 23 23:59:59 2068 UT = Sat Mar 24 01:59:59 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 24 00:00:00 2068 UT = Sat Mar 24 03:00:00 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 22:59:59 2068 UT = Sat Oct 20 01:59:59 2068 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 19 23:00:00 2068 UT = Sat Oct 20 01:00:00 2068 EET isdst=0 gmtoff=7200 Asia/Hebron Fri Mar 29 23:59:59 2069 UT = Sat Mar 30 01:59:59 2069 EET isdst=0 gmtoff=7200 Asia/Hebron Sat Mar 30 00:00:00 2069 UT = Sat Mar 30 03:00:00 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 22:59:59 2069 UT = Sat Oct 12 01:59:59 2069 EEST isdst=1 gmtoff=10800 Asia/Hebron Fri Oct 11 23:00:00 2069 UT = Sat Oct 12 01:00:00 2069 EET isdst=0 gmtoff=7200
This pattern of >2 transitions per year continues from that year.
Is this correct? It seems awfully weird.
IIRC, this is to accomodate a temporary-return-to-standard-time for the duration of Ramadan.
Cheers,
Dave Rolsky http://blog.urth.org https://github.com/autarch
!DSPAM:658fb40d15421143672522!
+---------------------+--------------------------+----------------------+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses: | | (Retired) | 1B11 1849 721C 56C8 F63A | paul@whooppee.com | | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoyette@netbsd.org | | & Network Engineer | | pgoyette99@gmail.com | +---------------------+--------------------------+----------------------+
On 2023-12-29 22:49, Paul Goyette via tz wrote:
IIRC, this is to accomodate a temporary-return-to-standard-time for the duration of Ramadan.
Yes, for example in 2072 the current guess is that Palestine will observe DST from March 26 through October 29, except that from September 10 through October 15 it will observe standard time, to help observe Ramadan. This is of course sheer guesswork that extrapolates from the rules Palestine observed in 2022 and 2023 and announced for 2024 through 2026. One test of this guesswork will occur in 2041, where we're currently guessing that Palestine will observe DST from March 30 through October 26, except that from August 24 through September 28 it will observe standard time. Quite possibly they'll do something other than predicted, which means we'll likely change our 2072 predictions as well.
participants (3)
-
Dave Rolsky -
Paul Eggert -
Paul Goyette