 @@ -43,27 +43,27 @@ BUGEMAIL=	tz@iana.org
 # Rearguard users might also want "ZFLAGS = -b fat"; see below.
 DATAFORM=		main
 # Change the line below for your timezone (after finding the one you want in
 # one of the $(TDATA) source files, or adding it to a source file).
 # Alternatively, if you discover you've got the wrong timezone, you can just
 # 'zic -l -' to remove it, or 'zic -l rightzone' to change it.
 # Use the command
 #	make zonenames
 # to get a list of the values you can use for LOCALTIME.
 LOCALTIME=	Factory
-# The POSIXRULES macro controls interpretation of POSIX-like TZ
+# The POSIXRULES macro controls interpretation of POSIX-2017.1-like TZ
 # settings like TZ='EET-2EEST' that lack DST transition rules.
 # If POSIXRULES is '-', no template is installed; this is the default.
 # Any other value for POSIXRULES is obsolete and should not be relied on, as:
 # * It does not work correctly in popular implementations such as GNU/Linux.
 # * It does not work even in tzcode, except for historical timestamps
 #   that precede the last explicit transition in the POSIXRULES file.
 #   Hence it typically does not work for current and future timestamps.
 # If, despite the above, you want a template for handling these settings,
 # you can change the line below (after finding the timezone you want in the
 # one of the $(TDATA) source files, or adding it to a source file).
 # Alternatively, if you discover you've got the wrong timezone, you can just
 # 'zic -p -' to remove it, or 'zic -p rightzone' to change it.
 # Use the command
 @@ -264,27 +264,27 @@ LDLIBS=
 #  -DSUPPORT_C89 if the tzcode library should support C89 callers+
 #	However, this might trigger latent bugs in C99-or-later callers.
 #  -DSUPPRESS_TZDIR to not prepend TZDIR to file names; this has
 #	security implications and is not recommended for general use
 #  -DTHREAD_SAFE to make localtime.c thread-safe, as POSIX requires;
 #	not needed by the main-program tz code, which is single-threaded.
 #	Append other compiler flags as needed, e.g., -pthread on GNU/Linux.
 #  -Dtime_tz=\"T\" to use T as the time_t type, rather than the system time_t
 #	This is intended for internal use only; it mangles external names.
 #  -DTZ_DOMAIN=\"foo\" to use "foo" for gettext domain name; default is "tz"
 #  -DTZ_DOMAINDIR=\"/path\" to use "/path" for gettext directory;
 #	the default is system-supplied, typically "/usr/lib/locale"
 #  -DTZDEFRULESTRING=\",date/time,date/time\" to default to the specified
-#	DST transitions for POSIX-style TZ strings lacking them,
+#	DST transitions for POSIX.1-2017-style TZ strings lacking them,
 #	in the usual case where POSIXRULES is '-'.  If not specified,
 #	TZDEFRULESTRING defaults to US rules for future DST transitions.
 #	This mishandles some past timestamps, as US DST rules have changed.
 #	It also mishandles settings like TZ='EET-2EEST' for eastern Europe,
 #	as Europe and US DST rules differ.
 #  -DTZNAME_MAXIMUM=N to limit time zone abbreviations to N bytes (default 255)
 #  -DUNINIT_TRAP if reading uninitialized storage can cause problems
 #	other than simply getting garbage data
 #  -DUSE_LTZ=0 to build zdump with the system time zone library
 #	Also set TZDOBJS=zdump.o and CHECK_TIME_T_ALTERNATIVES= below.
 #  -DZIC_BLOAT_DEFAULT=\"fat\" to default zic's -b option to "fat", and
 #	similarly for "slim".  Fat TZif files work around incompatibilities
 #	and bugs in some TZif readers, notably older ones that
 @@ -330,50 +330,51 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fn
   -Wtrampolines -Wundef -Wuninitialized -Wunused-macros -Wuse-after-free=3 \
   -Wvariadic-macros -Wvla -Wwrite-strings \
   -Wno-address -Wno-format-nonliteral -Wno-sign-compare \
   -Wno-type-limits
+#
 # If your system has a "GMT offset" field in its "struct tm"s
 # (or if you decide to add such a field in your system's "time.h" file),
 # add the name to a define such as
 #	-DTM_GMTOFF=tm_gmtoff
 # to the end of the "CFLAGS=" line.  If not defined, the code attempts to
 # guess TM_GMTOFF from other macros; define NO_TM_GMTOFF to suppress this.
 # Similarly, if your system has a "zone abbreviation" field, define
 #	-DTM_ZONE=tm_zone
-# and define NO_TM_ZONE to suppress any guessing.  Although these two fields
+# and define NO_TM_ZONE to suppress any guessing.
-# not required by POSIX, a future version of POSIX is planned to require them
+# Although these two fields are not required by POSIX.1-2017,
-# and they are widely available on GNU/Linux and BSD systems.
+# POSIX 202x/D4 requires them and they are widely available
 # on GNU/Linux and BSD systems.
+#
 # The next batch of options control support for external variables
 # exported by tzcode.  In practice these variables are less useful
 # than TM_GMTOFF and TM_ZONE.  However, most of them are standardized.
 # #
 # # To omit or support the external variable "tzname", add one of:
 # #	-DHAVE_TZNAME=0 # do not support "tzname"
 # #	-DHAVE_TZNAME=1 # support "tzname", which is defined by system library
 # #	-DHAVE_TZNAME=2 # support and define "tzname"
-# # to the "CFLAGS=" line.  "tzname" is required by POSIX 1988 and later.
+# # to the "CFLAGS=" line.  "tzname" is required by POSIX.1-1988 and later.
 # # If not defined, the code attempts to guess HAVE_TZNAME from other macros.
 # # Warning: unless time_tz is also defined, HAVE_TZNAME=1 can cause
 # # crashes when combined with some platforms' standard libraries,
 # # presumably due to memory allocation issues.
 # #
 # # To omit or support the external variables "timezone" and "daylight", add
 # #	-DUSG_COMPAT=0 # do not support
 # #	-DUSG_COMPAT=1 # support, and variables are defined by system library
 # #	-DUSG_COMPAT=2 # support and define variables
-# # to the "CFLAGS=" line; "timezone" and "daylight" are inspired by
+# # to the "CFLAGS=" line; "timezone" and "daylight" are inspired by Unix
-# # Unix Systems Group code and are required by POSIX 2008 (with XSI) and later.
+# # Systems Group code and are required by POSIX.1-2008 and later (with XSI).
 # # If not defined, the code attempts to guess USG_COMPAT from other macros.
 # #
 # # To support the external variable "altzone", add
 # #	-DALTZONE=0 # do not support
 # #	-DALTZONE=1 # support "altzone", which is defined by system library
 # #	-DALTZONE=2 # support and define "altzone"
 # # to the end of the "CFLAGS=" line; although "altzone" appeared in
 # # System V Release 3.1 it has not been standardized.
 # # If not defined, the code attempts to guess ALTZONE from other macros.
+#
 # If you want functions that were inspired by early versions of X3J11's work,
 # add
 #	-DSTD_INSPIRED
 @@ -417,38 +418,44 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fn
 # to the end of the "CFLAGS=" line.  This causes "strftime" to always return
 # 53 as a week number (rather than 52 or 53) for January days before
 # January's first Monday when a "%V" format is used and January 1
 # falls on a Friday, Saturday, or Sunday.
+#
 # POSIX says CFLAGS defaults to "-O 1".
 # Uncomment the following line and edit its contents as needed.
 #CFLAGS= -O 1
 # The name of a POSIX-like library archiver, its flags, C compiler,
 # linker flags, and 'make' utility.  Ordinarily the defaults suffice.
-# The commented-out values are the defaults specified by POSIX 202x/D3.
+# The commented-out values are the defaults specified by POSIX.1-202x/D4.
 #AR = ar
 #ARFLAGS = -rv
 #CC = c17
 #LDFLAGS =
 #MAKE = make
 # For leap seconds, this Makefile uses LEAPSECONDS='-L leapseconds' in
 # submake command lines.  The default is no leap seconds.
 LEAPSECONDS=
 # Where to fetch leap-seconds.list from.
 leaplist_URI = \
   https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list
 # The file is generated by the IERS Earth Orientation Centre, in Paris.
 leaplist_TZ = Europe/Paris
 # The zic command and its arguments.
 zic=		./zic
 ZIC=		$(zic) $(ZFLAGS)
 # To shrink the size of installed TZif files,
 # append "-r @N" to omit data before N-seconds-after-the-Epoch.
 # To grow the files and work around bugs in older applications,
 # possibly at the expense of introducing bugs in newer ones,
 # append "-b fat"; see ZIC_BLOAT_DEFAULT above.
 # See the zic man page for more about -b and -r.
 ZFLAGS=
 @@ -461,27 +468,28 @@ ZIC_INSTALL=	$(ZIC) -d '$(DESTDIR)$(TZDI
 # Also, it is better (though not essential) if 'awk' supports UTF-8,
 # and unfortunately mawk and busybox awk do not support UTF-8.
 # Try AWK=gawk or AWK=nawk if your awk has the abovementioned problems.
 AWK=		awk
 # The full path name of a POSIX-compliant shell, preferably one that supports
 # the Korn shell's 'select' statement as an extension.
 # These days, Bash is the most popular.
 # It should be OK to set this to /bin/sh, on platforms where /bin/sh
 # lacks 'select' or doesn't completely conform to POSIX, but /bin/bash
 # is typically nicer if it works.
 KSHELL=		/bin/bash
-# Name of curl <https://curl.haxx.se/>, used for HTML validation.
+# Name of curl <https://curl.haxx.se/>, used for HTML validation
 # and to fetch leap-seconds.list from upstream.
 CURL=		curl
 # Name of GNU Privacy Guard <https://gnupg.org/>, used to sign distributions.
 GPG=		gpg
 # This expensive test requires USE_LTZ.
 # To suppress it, define this macro to be empty.
 CHECK_TIME_T_ALTERNATIVES = check_time_t_alternatives
 # SAFE_CHAR is a regular expression that matches a safe character.
 # Some parts of this distribution are limited to safe characters;
 # others can use any UTF-8 character.
 # For now, the safe characters are a safe subset of ASCII.
 @@ -708,26 +716,48 @@ version.h:	version
 		mv $@.out $@
 zdump:		$(TZDOBJS)
 		$(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(TZDOBJS) $(LDLIBS)
 zic:		$(TZCOBJS)
 		$(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(TZCOBJS) $(LDLIBS)
 leapseconds:	$(LEAP_DEPS)
 		$(AWK) -v EXPIRES_LINE=$(EXPIRES_LINE) \
 		  -f leapseconds.awk leap-seconds.list >$@.out
 		mv $@.out $@
 # Awk script to extract a Git-style author from leap-seconds.list comments.
 EXTRACT_AUTHOR = \
   author_line { sub(/^.[[:space:]]*/, ""); \
       sub(/:[[:space:]]*/, " <"); \
       printf "%s>\n", $$0; \
       success = 1; \
       exit \
   } \
   /Questions or comments to:/ { author_line = 1 } \
   END { exit !success }
 # Fetch leap-seconds.list from upstream.
 fetch-leap-seconds.list:
 		$(CURL) -OR $(leaplist_URI)
 # Fetch leap-seconds.list from upstream and commit it to the local repository.
 commit-leap-seconds.list: fetch-leap-seconds.list
 		author=$$($(AWK) '$(EXTRACT_AUTHOR)' leap-seconds.list) && \
 		date=$$(TZ=$(leaplist_TZ) stat -c%y leap-seconds.list) && \
 		git commit --author="$$author" --date="$$date" -m'make $@' \
 		  leap-seconds.list
 # Arguments to pass to submakes of install_data.
 # They can be overridden by later submake arguments.
 INSTALLARGS = \
  BACKWARD='$(BACKWARD)' \
  DESTDIR='$(DESTDIR)' \
  LEAPSECONDS='$(LEAPSECONDS)' \
  PACKRATDATA='$(PACKRATDATA)' \
  PACKRATLIST='$(PACKRATLIST)' \
  TZDEFAULT='$(TZDEFAULT)' \
  TZDIR='$(TZDIR)' \
  ZIC='$(ZIC)'
 INSTALL_DATA_DEPS = zic leapseconds tzdata.zi
 @@ -1304,26 +1334,27 @@ zonenames:	tzdata.zi
 		@$(AWK) '/^Z/ { print $$2 } /^L/ { print $$3 }' tzdata.zi
 asctime.o:	private.h tzfile.h
 date.o:		private.h
 difftime.o:	private.h
 localtime.o:	private.h tzfile.h tzdir.h
 strftime.o:	private.h tzfile.h
 zdump.o:	version.h
 zic.o:		private.h tzfile.h tzdir.h version.h
 .PHONY: ALL INSTALL all
 .PHONY: check check_mild check_time_t_alternatives
 .PHONY: check_web check_zishrink
-.PHONY: clean clean_misc dummy.zd force_tzs
+.PHONY: clean clean_misc commit-leap-seconds.list dummy.zd
 .PHONY: fetch-leap-seconds.list force_tzs
 .PHONY: install install_data maintainer-clean names
 .PHONY: posix_only posix_right public
 .PHONY: rearguard_signatures rearguard_signatures_version
 .PHONY: rearguard_tarballs rearguard_tarballs_version
 .PHONY: right_only right_posix signatures signatures_version
 .PHONY: tarballs tarballs_version
 .PHONY: traditional_signatures traditional_signatures_version
 .PHONY: traditional_tarballs traditional_tarballs_version
 .PHONY: tailored_tarballs tailored_tarballs_version
 .PHONY: typecheck
 .PHONY: zonenames zones
 .PHONY: $(ZDS)

 @@ -2468,98 +2468,112 @@ Zone	Asia/Amman	2:23:44 -	LMT	1931
 # 1920-01-01 to the fourth time belt.  But I do not understand
 # how that could happen....
+#
 # [For Atyrau and Oral] 1919 decree
 # (http://www.worldtimezone.com/dst_news/dst_news_russia-1919-02-08.html
 # and in Byalokoz) lists Ural river (plus 10 versts on its left bank) in
 # the third time belt (before 1930 this means +03).
 # From Alexander Konzurovski (2018-12-20):
 # (Asia/Qyzylorda) is changing its time zone from UTC+6 to UTC+5
 # effective December 21st, 2018....
 # http://adilet.zan.kz/rus/docs/P1800000817 (russian language).
 # From Zhanbolat Raimbekov (2024-01-19):
 # Kazakhstan (all parts) switching to UTC+5 on March 1, 2024
 # https://www.gov.kz/memleket/entities/mti/press/news/details/688998?lang=ru
 # [in Russian]
 # (2024-01-20): https://primeminister.kz/ru/decisions/19012024-20
+#
 # From Alexander Krivenyshev (2024-01-19):
 # According to a different news and the official web site for the Ministry of
 # Trade and Integration of the Republic of Kazakhstan:
 # https://en.inform.kz/news/kazakhstan-to-switch-to-single-hour-zone-mar-1-54ad0b/
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
+#
 # Almaty (formerly Alma-Ata), representing most locations in Kazakhstan
-# This includes KZ-AKM, KZ-ALA, KZ-ALM, KZ-AST, KZ-BAY, KZ-VOS, KZ-ZHA,
+# This includes Abai/Abay (ISO 3166-2 code KZ-10), Aqmola/Akmola (KZ-11),
-# KZ-KAR, KZ-SEV, KZ-PAV, and KZ-YUZ.
+# Almaty (KZ-19), Almaty city (KZ-75), Astana city (KZ-71),
 # East Kazkhstan (KZ-63), Jambyl/Zhambyl (KZ-31), Jetisu/Zhetysu (KZ-33),
 # Karaganda (KZ-35), North Kazakhstan (KZ-59), Pavlodar (KZ-55),
 # Shyumkent city (KZ-79), Turkistan (KZ-61), and Ulytau (KZ-62).
 Zone	Asia/Almaty	5:07:48 -	LMT	1924 May  2 # or Alma-Ata
 :00	-	+05	1930 Jun 21
 :00 RussiaAsia +06/+07	1991 Mar 31  2:00s
 :00 RussiaAsia	+05/+06	1992 Jan 19  2:00s
 :00 RussiaAsia	+06/+07	2004 Oct 31  2:00s
-:00	-	+06
+:00	-	+06	2024 Mar  1  0:00
-# Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) (KZ-KZY)
+:00	-	+05
 # Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) (KZ-43)
 Zone	Asia/Qyzylorda	4:21:52 -	LMT	1924 May  2
 :00	-	+04	1930 Jun 21
 :00	-	+05	1981 Apr  1
 :00	1:00	+06	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 :00 RussiaAsia	+04/+05	1991 Sep 29  2:00s
 :00 RussiaAsia	+05/+06	1992 Jan 19  2:00s
 :00 RussiaAsia	+06/+07	1992 Mar 29  2:00s
 :00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
 :00	-	+06	2018 Dec 21  0:00
 :00	-	+05
 # Qostanay (aka Kostanay, Kustanay) (KZ-39)
 # Qostanay (aka Kostanay, Kustanay) (KZ-KUS)
 # The 1991/2 rules are unclear partly because of the 1997 Turgai
 # reorganization.
 Zone	Asia/Qostanay	4:14:28 -	LMT	1924 May  2
 :00	-	+04	1930 Jun 21
 :00	-	+05	1981 Apr  1
 :00	1:00	+06	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 :00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 :00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
-:00	-	+06
+:00	-	+06	2024 Mar  1  0:00
 :00	-	+05
-# Aqtöbe (aka Aktobe, formerly Aktyubinsk) (KZ-AKT)
+# Aqtöbe (aka Aktobe, formerly Aktyubinsk) (KZ-15)
 Zone	Asia/Aqtobe	3:48:40	-	LMT	1924 May  2
 :00	-	+04	1930 Jun 21
 :00	-	+05	1981 Apr  1
 :00	1:00	+06	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 :00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 :00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
 :00	-	+05
-# Mangghystaū (KZ-MAN)
+# Mangghystaū (KZ-47)
 # Aqtau was not founded until 1963, but it represents an inhabited region,
 # so include timestamps before 1963.
 Zone	Asia/Aqtau	3:21:04	-	LMT	1924 May  2
 :00	-	+04	1930 Jun 21
 :00	-	+05	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 :00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 :00 RussiaAsia	+05/+06	1994 Sep 25  2:00s
 :00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 :00	-	+05
-# Atyraū (KZ-ATY) is like Mangghystaū except it switched from
+# Atyraū (KZ-23) is like Mangghystaū except it switched from
 # +04/+05 to +05/+06 in spring 1999, not fall 1994.
 Zone	Asia/Atyrau	3:27:44	-	LMT	1924 May  2
 :00	-	+03	1930 Jun 21
 :00	-	+05	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 :00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 :00 RussiaAsia	+05/+06	1999 Mar 28  2:00s
 :00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 :00	-	+05
-# West Kazakhstan (KZ-ZAP)
+# West Kazakhstan (KZ-27)
 # From Paul Eggert (2016-03-18):
 # The 1989 transition is from USSR act No. 227 (1989-03-14).
 Zone	Asia/Oral	3:25:24	-	LMT	1924 May  2 # or Ural'sk
 :00	-	+03	1930 Jun 21
 :00	-	+05	1981 Apr  1
 :00	1:00	+06	1981 Oct  1
 :00	-	+06	1982 Apr  1
 :00 RussiaAsia	+05/+06	1989 Mar 26  2:00s
 :00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 :00 RussiaAsia	+05/+06	1992 Mar 29  2:00s
 :00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 :00	-	+05
 @@ -3470,47 +3484,55 @@ Zone	Asia/Karachi	4:28:12 -	LMT	1907
 # and winter time for the years: 2023,2024,2025,2026 ...
 # https://mm.icann.org/pipermail/tz/attachments/20220830/9f024566/Time-0001.pdf
 # (2022-08-31): ... the Saturday before the last Sunday in March and October
 # at 2:00 AM ,for the years from 2023 to 2026.
 # (2022-09-05): https://mtit.pna.ps/Site/New/1453
 # From Heba Hamad (2023-03-22):
 # ... summer time will begin in Palestine from Saturday 04-29-2023,
 # 02:00 AM by 60 minutes forward.
 # From Heba Hemad (2023-10-09):
 # ... winter time will begin in Palestine from Saturday 10-28-2023,
 # 02:00 AM by 60 minutes back.
+#
-# From Paul Eggert (2023-03-22):
+# From Heba Hamad (2024-01-25):
 # the summer time for the years 2024,2025 will begin in Palestine
 # from Saturday at 02:00 AM by 60 minutes forward as shown below:
 # year date
 # 2024 2024-04-20
 # 2025 2025-04-12
+#
 # From Paul Eggert (2024-01-25):
 # For now, guess that spring and fall transitions will normally
 # continue to use 2022's rules, that during DST Palestine will switch
 # to standard time at 02:00 the last Saturday before Ramadan and back
-# to DST at 02:00 the first Saturday after Ramadan, and that
+# to DST at 02:00 the second Saturday after Ramadan, and that
 # if the normal spring-forward or fall-back transition occurs during
 # Ramadan the former is delayed and the latter advanced.
 # To implement this, I predicted Ramadan-oriented transition dates for
-# 2023 through 2086 by running the following program under GNU Emacs 28.2,
+# 2026 through 2086 by running the following program under GNU Emacs 29.2,
 # with the results integrated by hand into the table below.
 # Predictions after 2086 are approximated without Ramadan.
+#
-# (let ((islamic-year 1444))
+# (let ((islamic-year 1447))
 #   (require 'cal-islam)
 #   (while (< islamic-year 1510)
 #     (let ((a (calendar-islamic-to-absolute (list 9 1 islamic-year)))
 #           (b (+ 1 (calendar-islamic-to-absolute (list 10 1 islamic-year))))
 #           (saturday 6))
 #       (while (/= saturday (mod (setq a (1- a)) 7)))
 #       (while (/= saturday (mod b 7))
 #         (setq b (1+ b)))
 #       (setq b (+ 7 b))
 #       (setq a (calendar-gregorian-from-absolute a))
 #       (setq b (calendar-gregorian-from-absolute b))
 #       (insert
 #        (format
 #         (concat "Rule Palestine\t%d\tonly\t-\t%s\t%2d\t2:00\t0\t-\n"
 #                 "Rule Palestine\t%d\tonly\t-\t%s\t%2d\t2:00\t1:00\tS\n")
 #         (car (cdr (cdr a))) (calendar-month-name (car a) t) (car (cdr a))
 #         (car (cdr (cdr b))) (calendar-month-name (car b) t) (car (cdr b)))))
 #     (setq islamic-year (+ 1 islamic-year))))
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule EgyptAsia	1957	only	-	May	10	0:00	1:00	S
 Rule EgyptAsia	1957	1958	-	Oct	 1	0:00	0	-
 @@ -3541,104 +3563,104 @@ Rule Palestine	2013	only	-	Sep	27	0:00	0
 Rule Palestine	2014	only	-	Oct	24	0:00	0	-
 Rule Palestine	2015	only	-	Mar	28	0:00	1:00	S
 Rule Palestine	2015	only	-	Oct	23	1:00	0	-
 Rule Palestine	2016	2018	-	Mar	Sat<=30	1:00	1:00	S
 Rule Palestine	2016	2018	-	Oct	Sat<=30	1:00	0	-
 Rule Palestine	2019	only	-	Mar	29	0:00	1:00	S
 Rule Palestine	2019	only	-	Oct	Sat<=30	0:00	0	-
 Rule Palestine	2020	2021	-	Mar	Sat<=30	0:00	1:00	S
 Rule Palestine	2020	only	-	Oct	24	1:00	0	-
 Rule Palestine	2021	only	-	Oct	29	1:00	0	-
 Rule Palestine	2022	only	-	Mar	27	0:00	1:00	S
 Rule Palestine	2022	2035	-	Oct	Sat<=30	2:00	0	-
 Rule Palestine	2023	only	-	Apr	29	2:00	1:00	S
-Rule Palestine	2024	only	-	Apr	13	2:00	1:00	S
+Rule Palestine	2024	only	-	Apr	20	2:00	1:00	S
-Rule Palestine	2025	only	-	Apr	 5	2:00	1:00	S
+Rule Palestine	2025	only	-	Apr	12	2:00	1:00	S
 Rule Palestine	2026	2054	-	Mar	Sat<=30	2:00	1:00	S
 Rule Palestine	2036	only	-	Oct	18	2:00	0	-
 Rule Palestine	2037	only	-	Oct	10	2:00	0	-
 Rule Palestine	2038	only	-	Sep	25	2:00	0	-
 Rule Palestine	2039	only	-	Sep	17	2:00	0	-
 Rule Palestine	2039	only	-	Oct	22	2:00	1:00	S
 Rule Palestine	2039	2067	-	Oct	Sat<=30	2:00	0	-
 Rule Palestine	2040	only	-	Sep	 1	2:00	0	-
-Rule Palestine	2040	only	-	Oct	13	2:00	1:00	S
+Rule Palestine	2040	only	-	Oct	20	2:00	1:00	S
 Rule Palestine	2040	2067	-	Oct	Sat<=30	2:00	0	-
 Rule Palestine	2041	only	-	Aug	24	2:00	0	-
-Rule Palestine	2041	only	-	Sep	28	2:00	1:00	S
+Rule Palestine	2041	only	-	Oct	 5	2:00	1:00	S
 Rule Palestine	2042	only	-	Aug	16	2:00	0	-
-Rule Palestine	2042	only	-	Sep	20	2:00	1:00	S
+Rule Palestine	2042	only	-	Sep	27	2:00	1:00	S
 Rule Palestine	2043	only	-	Aug	 1	2:00	0	-
-Rule Palestine	2043	only	-	Sep	12	2:00	1:00	S
+Rule Palestine	2043	only	-	Sep	19	2:00	1:00	S
 Rule Palestine	2044	only	-	Jul	23	2:00	0	-
-Rule Palestine	2044	only	-	Aug	27	2:00	1:00	S
+Rule Palestine	2044	only	-	Sep	 3	2:00	1:00	S
 Rule Palestine	2045	only	-	Jul	15	2:00	0	-
-Rule Palestine	2045	only	-	Aug	19	2:00	1:00	S
+Rule Palestine	2045	only	-	Aug	26	2:00	1:00	S
 Rule Palestine	2046	only	-	Jun	30	2:00	0	-
-Rule Palestine	2046	only	-	Aug	11	2:00	1:00	S
+Rule Palestine	2046	only	-	Aug	18	2:00	1:00	S
 Rule Palestine	2047	only	-	Jun	22	2:00	0	-
-Rule Palestine	2047	only	-	Jul	27	2:00	1:00	S
+Rule Palestine	2047	only	-	Aug	 3	2:00	1:00	S
 Rule Palestine	2048	only	-	Jun	 6	2:00	0	-
-Rule Palestine	2048	only	-	Jul	18	2:00	1:00	S
+Rule Palestine	2048	only	-	Jul	25	2:00	1:00	S
 Rule Palestine	2049	only	-	May	29	2:00	0	-
-Rule Palestine	2049	only	-	Jul	 3	2:00	1:00	S
+Rule Palestine	2049	only	-	Jul	10	2:00	1:00	S
 Rule Palestine	2050	only	-	May	21	2:00	0	-
-Rule Palestine	2050	only	-	Jun	25	2:00	1:00	S
+Rule Palestine	2050	only	-	Jul	 2	2:00	1:00	S
 Rule Palestine	2051	only	-	May	 6	2:00	0	-
-Rule Palestine	2051	only	-	Jun	17	2:00	1:00	S
+Rule Palestine	2051	only	-	Jun	24	2:00	1:00	S
 Rule Palestine	2052	only	-	Apr	27	2:00	0	-
-Rule Palestine	2052	only	-	Jun	 1	2:00	1:00	S
+Rule Palestine	2052	only	-	Jun	 8	2:00	1:00	S
 Rule Palestine	2053	only	-	Apr	12	2:00	0	-
-Rule Palestine	2053	only	-	May	24	2:00	1:00	S
+Rule Palestine	2053	only	-	May	31	2:00	1:00	S
 Rule Palestine	2054	only	-	Apr	 4	2:00	0	-
-Rule Palestine	2054	only	-	May	16	2:00	1:00	S
+Rule Palestine	2054	only	-	May	23	2:00	1:00	S
-Rule Palestine	2055	only	-	May	 1	2:00	1:00	S
+Rule Palestine	2055	only	-	May	 8	2:00	1:00	S
-Rule Palestine	2056	only	-	Apr	22	2:00	1:00	S
+Rule Palestine	2056	only	-	Apr	29	2:00	1:00	S
-Rule Palestine	2057	only	-	Apr	 7	2:00	1:00	S
+Rule Palestine	2057	only	-	Apr	14	2:00	1:00	S
-Rule Palestine	2058	max	-	Mar	Sat<=30	2:00	1:00	S
+Rule Palestine	2058	only	-	Apr	 6	2:00	1:00	S
 Rule Palestine	2059	max	-	Mar	Sat<=30	2:00	1:00	S
 Rule Palestine	2068	only	-	Oct	20	2:00	0	-
 Rule Palestine	2069	only	-	Oct	12	2:00	0	-
 Rule Palestine	2070	only	-	Oct	 4	2:00	0	-
 Rule Palestine	2071	only	-	Sep	19	2:00	0	-
 Rule Palestine	2072	only	-	Sep	10	2:00	0	-
-Rule Palestine	2072	only	-	Oct	15	2:00	1:00	S
+Rule Palestine	2072	only	-	Oct	22	2:00	1:00	S
 Rule Palestine	2072	max	-	Oct	Sat<=30	2:00	0	-
 Rule Palestine	2073	only	-	Sep	 2	2:00	0	-
-Rule Palestine	2073	only	-	Oct	 7	2:00	1:00	S
+Rule Palestine	2073	only	-	Oct	14	2:00	1:00	S
 Rule Palestine	2074	only	-	Aug	18	2:00	0	-
-Rule Palestine	2074	only	-	Sep	29	2:00	1:00	S
+Rule Palestine	2074	only	-	Oct	 6	2:00	1:00	S
 Rule Palestine	2075	only	-	Aug	10	2:00	0	-
-Rule Palestine	2075	only	-	Sep	14	2:00	1:00	S
+Rule Palestine	2075	only	-	Sep	21	2:00	1:00	S
 Rule Palestine	2076	only	-	Jul	25	2:00	0	-
-Rule Palestine	2076	only	-	Sep	 5	2:00	1:00	S
+Rule Palestine	2076	only	-	Sep	12	2:00	1:00	S
 Rule Palestine	2077	only	-	Jul	17	2:00	0	-
-Rule Palestine	2077	only	-	Aug	28	2:00	1:00	S
+Rule Palestine	2077	only	-	Sep	 4	2:00	1:00	S
 Rule Palestine	2078	only	-	Jul	 9	2:00	0	-
-Rule Palestine	2078	only	-	Aug	13	2:00	1:00	S
+Rule Palestine	2078	only	-	Aug	20	2:00	1:00	S
 Rule Palestine	2079	only	-	Jun	24	2:00	0	-
-Rule Palestine	2079	only	-	Aug	 5	2:00	1:00	S
+Rule Palestine	2079	only	-	Aug	12	2:00	1:00	S
 Rule Palestine	2080	only	-	Jun	15	2:00	0	-
-Rule Palestine	2080	only	-	Jul	20	2:00	1:00	S
+Rule Palestine	2080	only	-	Jul	27	2:00	1:00	S
 Rule Palestine	2081	only	-	Jun	 7	2:00	0	-
-Rule Palestine	2081	only	-	Jul	12	2:00	1:00	S
+Rule Palestine	2081	only	-	Jul	19	2:00	1:00	S
 Rule Palestine	2082	only	-	May	23	2:00	0	-
-Rule Palestine	2082	only	-	Jul	 4	2:00	1:00	S
+Rule Palestine	2082	only	-	Jul	11	2:00	1:00	S
 Rule Palestine	2083	only	-	May	15	2:00	0	-
-Rule Palestine	2083	only	-	Jun	19	2:00	1:00	S
+Rule Palestine	2083	only	-	Jun	26	2:00	1:00	S
 Rule Palestine	2084	only	-	Apr	29	2:00	0	-
-Rule Palestine	2084	only	-	Jun	10	2:00	1:00	S
+Rule Palestine	2084	only	-	Jun	17	2:00	1:00	S
 Rule Palestine	2085	only	-	Apr	21	2:00	0	-
-Rule Palestine	2085	only	-	Jun	 2	2:00	1:00	S
+Rule Palestine	2085	only	-	Jun	 9	2:00	1:00	S
 Rule Palestine	2086	only	-	Apr	13	2:00	0	-
-Rule Palestine	2086	only	-	May	18	2:00	1:00	S
+Rule Palestine	2086	only	-	May	25	2:00	1:00	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Gaza	2:17:52	-	LMT	1900 Oct
 :00	Zion	EET/EEST 1948 May 15
 :00 EgyptAsia	EE%sT	1967 Jun  5
 :00	Zion	I%sT	1996
 :00	Jordan	EE%sT	1999
 :00 Palestine	EE%sT	2008 Aug 29  0:00
 :00	-	EET	2008 Sep
 :00 Palestine	EE%sT	2010
 :00	-	EET	2010 Mar 27  0:01
 :00 Palestine	EE%sT	2011 Aug  1
 :00	-	EET	2012
 @@ -3646,35 +3668,35 @@ Zone	Asia/Gaza	2:17:52	-	LMT	1900 Oct
 Zone	Asia/Hebron	2:20:23	-	LMT	1900 Oct
 :00	Zion	EET/EEST 1948 May 15
 :00 EgyptAsia	EE%sT	1967 Jun  5
 :00	Zion	I%sT	1996
 :00	Jordan	EE%sT	1999
 :00 Palestine	EE%sT
 # Paracel Is
 # no information
 # Philippines
-# From Paul Eggert (2018-11-18):
+# From Paul Eggert (2024-01-21):
 # The Spanish initially used American (west-of-Greenwich) time.
 # It is unknown what time Manila kept when the British occupied it from
 # 1762-10-06 through 1764-04; for now assume it kept American time.
 # On 1844-08-16, Narciso Clavería, governor-general of the
 # Philippines, issued a proclamation announcing that 1844-12-30 was to
 # be immediately followed by 1845-01-01; see R.H. van Gent's
 # History of the International Date Line
-# https://www.staff.science.uu.nl/~gent0113/idl/idl_philippines.htm
+# https://webspace.science.uu.nl/~gent0113/idl/idl_philippines.htm
 # The rest of the data entries are from Shanks & Pottenger.
 # From Jesper Nørgaard Welen (2006-04-26):
 # ... claims that Philippines had DST last time in 1990:
 # http://story.philippinetimes.com/p.x/ct/9/id/145be20cc6b121c0/cid/3e5bbccc730d258c/
 # [a story dated 2006-04-25 by Cris Larano of Dow Jones Newswires,
 # but no details]
 # From Paul Eggert (2014-08-14):
 # The following source says DST may be instituted November-January and again
 # March-June, but this is not definite.  It also says DST was last proclaimed
 # during the Ramos administration (1992-1998); but again, no details.
 # Carcamo D. PNoy urged to declare use of daylight saving time.
 @@ -4071,27 +4093,28 @@ Zone	Asia/Tashkent	4:37:11 -	LMT	1924 Ma
 # Vietnam (southern)
 # From Paul Eggert (2014-10-04):
 # Milne gives 7:16:56 for the meridian of Saigon in 1899, as being
 # used in Lower Laos, Cambodia, and Annam.  But this is quite a ways
 # from Saigon's location.  For now, ignore this and stick with Shanks
 # and Pottenger for LMT before 1906.
 # From Arthur David Olson (2008-03-18):
 # The English-language name of Vietnam's most populous city is "Ho Chi Minh
 # City"; use Ho_Chi_Minh below to avoid a name of more than 14 characters.
-# From Paul Eggert (2022-07-27) after a 2014 heads-up from Trần Ngọc Quân:
+# From Paul Eggert (2024-01-14) after a 2014 heads-up from Trần Ngọc Quân
 # and a 2024-01-14 heads-up from Đoàn Trần Công Danh:
 # Trần Tiến Bình's authoritative book "Lịch Việt Nam: thế kỷ XX-XXI (1901-2100)"
 # (Nhà xuất bản Văn Hoá - Thông Tin, Hanoi, 2005), pp 49-50,
 # is quoted verbatim in:
 # http://www.thoigian.com.vn/?mPage=P80D01
 # is translated by Brian Inglis in:
 # https://mm.icann.org/pipermail/tz/2014-October/021654.html
 # and is the basis for the information below.
+#
 # The 1906 transition was effective July 1 and standardized Indochina to
 # Phù Liễn Observatory, legally 104° 17' 17" east of Paris.
 # It's unclear whether this meant legal Paris Mean Time (00:09:21) or
 # the Paris Meridian; for now guess the former and round the exact
 # 07:06:30.1333... to 07:06:30.13 as the legal spec used 66 2/3 ms precision.
 @@ -4101,44 +4124,65 @@ Zone	Asia/Tashkent	4:37:11 -	LMT	1924 Ma
 # The following transitions occurred in Indochina in general (before 1954)
 # and in South Vietnam in particular (after 1954):
 # To 07:00 on 1911-05-01.
 # To 08:00 on 1942-12-31 at 23:00.
 # To 09:00 on 1945-03-14 at 23:00.
 # To 07:00 on 1945-09-02 in Vietnam.
 # To 08:00 on 1947-04-01 in French-controlled Indochina.
 # To 07:00 on 1955-07-01 in South Vietnam.
 # To 08:00 on 1959-12-31 at 23:00 in South Vietnam.
 # To 07:00 on 1975-06-13 in South Vietnam.
+#
 # Trần cites the following sources; it's unclear which supplied the info above.
+#
-# Hoàng Xuân Hãn: "Lịch và lịch Việt Nam". Tập san Khoa học Xã hội,
+#   Hoàng Xuân Hãn: "Lịch và lịch Việt Nam". Tập san Khoa học Xã hội,
-# No. 9, Paris, February 1982.
+#   No. 9, Paris, February 1982.
+#
 #   Lê Thành Lân: "Lịch và niên biểu lịch sử hai mươi thế kỷ (0001-2010)",
 #   NXB Thống kê, Hanoi, 2000.
+#
-# Lê Thành Lân: "Lịch v�� ni��n bi���u l���ch s��� hai m����i thế kỷ (0001-2010)",
+#   Lê Thành Lân: "Lịch hai thế kỷ (1802-2010) v�� c��c l���ch v��nh c���u",
-# NXB Th���ng k��, Hanoi, 2000.
+#   NXB Thu���n Ho��, Hu���, 1995.
+#
-# Lê Thành Lân: "Lịch hai thế kỷ (1802-2010) và các lịch vĩnh cửu",
+# Here is the decision for the September 1945 transition:
-# NXB Thuận Hoá, Huế, 1995.
+# Võ Nguyên Giáp, Việt Nam Dân Quốc Công Báo, No. 1 (1945-09-29), page 13
 # http://baochi.nlv.gov.vn/baochi/cgi-bin/baochi?a=d&d=JwvzO19450929.2.5&dliv=none
 # It says that on 1945-09-01 at 24:00, Vietnam moved back two hours, to +07.
 # It also mentions a 1945-03-29 decree (by a Japanese Goveror-General)
 # to set the time zone to +09, but does not say whether that decree
 # merely legalized an earlier change to +09.
+#
 # July 1955 transition:
 # Ngô Đình Diệm, Công Báo Việt Nam, No. 92 (1955-07-02), page 1780-1781
 # Ordinance (Dụ) No. 46 (1955-06-25)
 # http://ddsnext.crl.edu/titles/32341#?c=0&m=29&s=0&cv=4&r=0&xywh=-89%2C342%2C1724%2C1216
 # It says that on 1955-07-01 at 01:00, South Vietnam moved back 1 hour (to +07).
+#
 # December 1959 transition:
 # Ngô Đình Diệm, Công Báo Việt Nam Cộng Hòa, 1960 part 1 (1960-01-02), page 62
 # Decree (Sắc lệnh) No. 362-TTP (1959-12-30)
 # http://ddsnext.crl.edu/titles/32341#?c=0&m=138&s=0&cv=793&r=0&xywh=-54%2C1504%2C1705%2C1202
 # It says that on 1959-12-31 at 23:00, South Vietnam moved forward 1 hour (to +08).
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 		#STDOFF	7:06:30.13
 Zone Asia/Ho_Chi_Minh	7:06:30 -	LMT	1906 Jul  1
 :06:30	-	PLMT	1911 May  1 # Phù Liễn MT
 :00	-	+07	1942 Dec 31 23:00
 :00	-	+08	1945 Mar 14 23:00
-:00	-	+09	1945 Sep  2
+:00	-	+09	1945 Sep  1 24:00
 :00	-	+07	1947 Apr  1
-:00	-	+08	1955 Jul  1
+:00	-	+08	1955 Jul  1 01:00
 :00	-	+07	1959 Dec 31 23:00
 :00	-	+08	1975 Jun 13
 :00	-	+07
 # From Paul Eggert (2019-02-19):
+#
 # The Ho Chi Minh entry suffices for most purposes as it agrees with all of
 # Vietnam since 1975-06-13.  Presumably clocks often changed in south Vietnam
 # in the early 1970s as locations changed hands during the war; however the
 # details are unknown and would likely be too voluminous for this database.
+#
 # For timestamps in north Vietnam back to 1970 (the tzdb cutoff),
 # use Asia/Bangkok; see the VN entries in the file zone1970.tab.

 @@ -420,31 +420,31 @@ Rule	Fiji	2010	2013	-	Oct	Sun>=21	2:00	1
 Rule	Fiji	2011	only	-	Mar	Sun>=1	3:00	0	-
 Rule	Fiji	2012	2013	-	Jan	Sun>=18	3:00	0	-
 Rule	Fiji	2014	only	-	Jan	Sun>=18	2:00	0	-
 Rule	Fiji	2014	2018	-	Nov	Sun>=1	2:00	1:00	-
 Rule	Fiji	2015	2021	-	Jan	Sun>=12	3:00	0	-
 Rule	Fiji	2019	only	-	Nov	Sun>=8	2:00	1:00	-
 Rule	Fiji	2020	only	-	Dec	20	2:00	1:00	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Pacific/Fiji	11:55:44 -	LMT	1915 Oct 26 # Suva
 :00	Fiji	+12/+13
 # French Polynesia
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone	Pacific/Gambier	 -8:59:48 -	LMT	1912 Oct # Rikitea
+Zone	Pacific/Gambier	 -8:59:48 -	LMT	1912 Oct  1 # Rikitea
 			 -9:00	-	-09
-Zone	Pacific/Marquesas -9:18:00 -	LMT	1912 Oct
+Zone	Pacific/Marquesas -9:18:00 -	LMT	1912 Oct  1
 			 -9:30	-	-0930
-Zone	Pacific/Tahiti	 -9:58:16 -	LMT	1912 Oct # Papeete
+Zone	Pacific/Tahiti	 -9:58:16 -	LMT	1912 Oct  1 # Papeete
 			-10:00	-	-10
 # Clipperton (near North America) is administered from French Polynesia;
 # it is uninhabited.
 # Guam
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 # http://guamlegislature.com/Public_Laws_5th/PL05-025.pdf
 # http://documents.guam.gov/wp-content/uploads/E.O.-59-7-Guam-Daylight-Savings-Time-May-6-1959.pdf
 Rule	Guam	1959	only	-	Jun	27	2:00	1:00	D
 # http://documents.guam.gov/wp-content/uploads/E.O.-61-5-Revocation-of-Daylight-Saving-Time-and-Restoratio.pdf
 Rule	Guam	1961	only	-	Jan	29	2:00	0	S
 @@ -833,27 +833,27 @@ Rule	WS	2011	only	-	Apr	Sat>=1	4:00	0	-
 Rule	WS	2011	only	-	Sep	lastSat	3:00	1	-
 Rule	WS	2012	2021	-	Apr	Sun>=1	4:00	0	-
 Rule	WS	2012	2020	-	Sep	lastSun	3:00	1	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone Pacific/Apia	 12:33:04 -	LMT	1892 Jul  5
 			-11:26:56 -	LMT	1911
 			-11:30	-	-1130	1950
 			-11:00	WS	-11/-10	2011 Dec 29 24:00
 :00	WS	+13/+14
 # Solomon Is
 # excludes Bougainville, for which see Papua New Guinea
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone Pacific/Guadalcanal 10:39:48 -	LMT	1912 Oct # Honiara
+Zone Pacific/Guadalcanal 10:39:48 -	LMT	1912 Oct  1 # Honiara
 :00	-	+11
 # Tokelau
+#
 # From Gwillim Law (2011-12-29)
 # A correspondent informed me that Tokelau, like Samoa, will be skipping
 # December 31 this year ...
+#
 # From Steffen Thorsen (2012-07-25)
 # ... we double checked by calling hotels and offices based in Tokelau asking
 # about the time there, and they all told a time that agrees with UTC+13....
 # Shanks says UT-10 from 1901 [but] ... there is a good chance the change
 # actually was to UT-11 back then.
 @@ -1015,26 +1015,30 @@ Zone	Pacific/Wallis	12:15:20 -	LMT	1901
 # Association's Standard Schedules Information Manual (IATA SSIM),
 # published semiannually.  Law sent in several helpful summaries
 # of the IATA's data after 1990.  Except where otherwise noted,
 # IATA SSIM is the source for entries after 1990.
+#
 # Another source occasionally used is Edward W. Whitman, World Time Differences,
 # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which
 # I found in the UCLA library.
+#
 # For data circa 1899, a common source is:
 # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94.
 # https://www.jstor.org/stable/1774359
+#
 # For the 1911/1912 establishment of standard time in French possessions, see:
 # Société Française de Physique, Recueil de constantes physiques (1913),
 # page 752, 18b.
+#
 # A reliable and entertaining source about time zones is
 # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997).
+#
 # I invented the abbreviation marked "*".
 # The following abbreviations are from other sources.
 # Corrections are welcome!
 #		std	dst
 #		LMT		Local Mean Time
 #	  8:00	AWST	AWDT	Western Australia
 #	  9:30	ACST	ACDT	Central Australia
 #	 10:00	AEST	AEDT	Eastern Australia
 #	 10:00	GST	GDT*	Guam through 2000
 #	 10:00	ChST		Chamorro
 @@ -2091,27 +2095,27 @@ Zone	Pacific/Wallis	12:15:20 -	LMT	1901
 # Betty Christian told me yesterday that their local time is the same as
 # Pacific Standard Time. They used to be ½ hour different from us here in
 # Sacramento but it was changed a couple of years ago.
 # (Western) Samoa and American Samoa
 # Howse writes (p 153) that after the 1879 standardization on Antipodean
 # time by the British governor of Fiji, the King of Samoa decided to change
 # "the date in his kingdom from the Antipodean to the American system,
 # ordaining - by a masterpiece of diplomatic flattery - that
 # the Fourth of July should be celebrated twice in that year."
 # This happened in 1892, according to the Evening News (Sydney) of 1892-07-20.
-# https://www.staff.science.uu.nl/~gent0113/idl/idl.htm
+# https://webspace.science.uu.nl/~gent0113/idl/idl_alaska_samoa.htm
 # Although Shanks & Pottenger says they both switched to UT -11:30
 # in 1911, and to -11 in 1950. many earlier sources give -11
 # for American Samoa, e.g., the US National Bureau of Standards
 # circular "Standard Time Throughout the World", 1932.
 # Assume American Samoa switched to -11 in 1911, not 1950,
 # and that after 1950 they agreed until (western) Samoa skipped a
 # day in 2011.  Assume also that the Samoas follow the US and New
 # Zealand's "ST"/"DT" style of daylight-saving abbreviations.
 # Tonga

 @@ -1,255 +1,120 @@
 #	ATOMIC TIME.
 #	The Coordinated Universal Time (UTC) is the reference time scale derived
 #	from The "Temps Atomique International" (TAI) calculated by the Bureau
 #	International des Poids et Mesures (BIPM) using a worldwide network of atomic
 #	clocks. UTC differs from TAI by an integer number of seconds; it is the basis
 #	of all activities in the world.
+#
 #	In the following text, the symbol '#' introduces
 #	a comment, which continues from that symbol until
 #	the end of the line. A plain comment line has a
 #	whitespace character following the comment indicator.
 #	There are also special comment lines defined below.
 #	A special comment will always have a non-whitespace
 #	character in column 2.
 #	A blank line should be ignored.
 #	The following table shows the corrections that must
 #	be applied to compute International Atomic Time (TAI)
 #	from the Coordinated Universal Time (UTC) values that
 #	are transmitted by almost all time services.
 #	The first column shows an epoch as a number of seconds
 #	since 1 January 1900, 00:00:00 (1900.0 is also used to
 #	indicate the same epoch.) Both of these time stamp formats
 #	ignore the complexities of the time scales that were
 #	used before the current definition of UTC at the start
 #	of 1972. (See note 3 below.)
 #	The second column shows the number of seconds that
 #	must be added to UTC to compute TAI for any timestamp
 #	at or after that epoch. The value on each line is
 #	valid from the indicated initial instant until the
 #	epoch given on the next one or indefinitely into the
 #	future if there is no next line.
 #	(The comment on each line shows the representation of
 #	the corresponding initial epoch in the usual
 #	day-month-year format. The epoch always begins at
 #	00:00:00 UTC on the indicated day. See Note 5 below.)
 #	Important notes:
 #	1. Coordinated Universal Time (UTC) is often referred to
 #	as Greenwich Mean Time (GMT). The GMT time scale is no
 #	longer used, and the use of GMT to designate UTC is
 #	discouraged.
 #	2. The UTC time scale is realized by many national
 #	laboratories and timing centers. Each laboratory
 #	identifies its realization with its name: Thus
 #	UTC(NIST), UTC(USNO), etc. The differences among
 #	these different realizations are typically on the
 #	order of a few nanoseconds (i.e., 0.000 000 00x s)
 #	and can be ignored for many purposes. These differences
 #	are tabulated in Circular T, which is published monthly
 #	by the International Bureau of Weights and Measures
 #	(BIPM). See www.bipm.org for more information.
 #	3. The current definition of the relationship between UTC
 #	and TAI dates from 1 January 1972. A number of different
 #	time scales were in use before that epoch, and it can be
 #	quite difficult to compute precise timestamps and time
 #	intervals in those "prehistoric" days. For more information,
 #	consult:
 #		The Explanatory Supplement to the Astronomical
 #		Ephemeris.
 #	or
 #		Terry Quinn, "The BIPM and the Accurate Measurement
 #		of Time," Proc. of the IEEE, Vol. 79, pp. 894-905,
 #		July, 1991. <http://dx.doi.org/10.1109/5.84965>
 #		reprinted in:
 #		   Christine Hackman and Donald B Sullivan (eds.)
 #		   Time and Frequency Measurement
 #		   American Association of Physics Teachers (1996)
 #		   <http://tf.nist.gov/general/pdf/1168.pdf>, pp. 75-86
 #	4. The decision to insert a leap second into UTC is currently
 #	the responsibility of the International Earth Rotation and
 #	Reference Systems Service. (The name was changed from the
 #	International Earth Rotation Service, but the acronym IERS
 #	is still used.)
 #	Leap seconds are announced by the IERS in its Bulletin C.
 #	See www.iers.org for more details.
 #	Every national laboratory and timing center uses the
 #	data from the BIPM and the IERS to construct UTC(lab),
 #	their local realization of UTC.
 #	Although the definition also includes the possibility
 #	of dropping seconds ("negative" leap seconds), this has
 #	never been done and is unlikely to be necessary in the
 #	foreseeable future.
 #	5. If your system keeps time as the number of seconds since
 #	some epoch (e.g., NTP timestamps), then the algorithm for
 #	assigning a UTC time stamp to an event that happens during a positive
 #	leap second is not well defined. The official name of that leap
 #	second is 23:59:60, but there is no way of representing that time
 #	in these systems.
 #	Many systems of this type effectively stop the system clock for
 #	one second during the leap second and use a time that is equivalent
 #	to 23:59:59 UTC twice. For these systems, the corresponding TAI
 #	timestamp would be obtained by advancing to the next entry in the
 #	following table when the time equivalent to 23:59:59 UTC
 #	is used for the second time. Thus the leap second which
 #	occurred on 30 June 1972 at 23:59:59 UTC would have TAI
 #	timestamps computed as follows:
 #	...
 #	30 June 1972 23:59:59 (2287785599, first time):	TAI= UTC + 10 seconds
 #	30 June 1972 23:59:60 (2287785599,second time):	TAI= UTC + 11 seconds
 #	1  July 1972 00:00:00 (2287785600)		TAI= UTC + 11 seconds
 #	...
 #	If your system realizes the leap second by repeating 00:00:00 UTC twice
 #	(this is possible but not usual), then the advance to the next entry
 #	in the table must occur the second time that a time equivalent to
 #	00:00:00 UTC is used. Thus, using the same example as above:
 #	...
 #       30 June 1972 23:59:59 (2287785599):		TAI= UTC + 10 seconds
 #       30 June 1972 23:59:60 (2287785600, first time):	TAI= UTC + 10 seconds
 #       1  July 1972 00:00:00 (2287785600,second time):	TAI= UTC + 11 seconds
 #	...
 #	in both cases the use of timestamps based on TAI produces a smooth
 #	time scale with no discontinuity in the time interval. However,
 #	although the long-term behavior of the time scale is correct in both
 #	methods, the second method is technically not correct because it adds
 #	the extra second to the wrong day.
 #	This complexity would not be needed for negative leap seconds (if they
 #	are ever used). The UTC time would skip 23:59:59 and advance from
 #	23:59:58 to 00:00:00 in that case. The TAI offset would decrease by
 #	1 second at the same instant. This is a much easier situation to deal
 #	with, since the difficulty of unambiguously representing the epoch
 #	during the leap second does not arise.
 #	Some systems implement leap seconds by amortizing the leap second
 #	over the last few minutes of the day. The frequency of the local
 #	clock is decreased (or increased) to realize the positive (or
 #	negative) leap second. This method removes the time step described
 #	above. Although the long-term behavior of the time scale is correct
 #	in this case, this method introduces an error during the adjustment
 #	period both in time and in frequency with respect to the official
 #	definition of UTC.
 #	Questions or comments to:
 #		Judah Levine
 #		Time and Frequency Division
 #		NIST
 #		Boulder, Colorado
 #		Judah.Levine@nist.gov
 #	Last Update of leap second values:   8 July 2016
 #	The following line shows this last update date in NTP timestamp
 #	format. This is the date on which the most recent change to
 #	the leap second data was added to the file. This line can
 #	be identified by the unique pair of characters in the first two
 #	columns as shown below.
 #$	 3676924800
 #	The NTP timestamps are in units of seconds since the NTP epoch,
 #	which is 1 January 1900, 00:00:00. The Modified Julian Day number
 #	corresponding to the NTP time stamp, X, can be computed as
 #	X/86400 + 15020
 #	where the first term converts seconds to days and the second
 #	term adds the MJD corresponding to the time origin defined above.
 #	The integer portion of the result is the integer MJD for that
 #	day, and any remainder is the time of day, expressed as the
 #	fraction of the day since 0 hours UTC. The conversion from day
 #	fraction to seconds or to hours, minutes, and seconds may involve
 #	rounding or truncation, depending on the method used in the
 #	computation.
 #	The data in this file will be updated periodically as new leap
 #	seconds are announced. In addition to being entered on the line
 #	above, the update time (in NTP format) will be added to the basic
 #	file name leap-seconds to form the name leap-seconds.<NTP TIME>.
 #	In addition, the generic name leap-seconds.list will always point to
 #	the most recent version of the file.
 #	This update procedure will be performed only when a new leap second
 #	is announced.
 #	The following entry specifies the expiration date of the data
 #	in this file in units of seconds since the origin at the instant
 #	1 January 1900, 00:00:00. This expiration date will be changed
 #	at least twice per year whether or not a new leap second is
 #	announced. These semi-annual changes will be made no later
 #	than 1 June and 1 December of each year to indicate what
 #	action (if any) is to be taken on 30 June and 31 December,
 #	respectively. (These are the customary effective dates for new
 #	leap seconds.) This expiration date will be identified by a
 #	unique pair of characters in columns 1 and 2 as shown below.
 #	In the unlikely event that a leap second is announced with an
 #	effective date other than 30 June or 31 December, then this
 #	file will be edited to include that leap second as soon as it is
 #	announced or at least one month before the effective date
 #	(whichever is later).
 #	If an announcement by the IERS specifies that no leap second is
 #	scheduled, then only the expiration date of the file will
 #	be advanced to show that the information in the file is still
 #	current -- the update time stamp, the data and the name of the file
 #	will not change.
 #	Updated through IERS Bulletin C66
 #	File expires on:  28 June 2024
 #@	3928521600
 2272060800	10	# 1 Jan 1972
 2287785600	11	# 1 Jul 1972
 2303683200	12	# 1 Jan 1973
 2335219200	13	# 1 Jan 1974
 2366755200	14	# 1 Jan 1975
 2398291200	15	# 1 Jan 1976
 2429913600	16	# 1 Jan 1977
 2461449600	17	# 1 Jan 1978
 2492985600	18	# 1 Jan 1979
 2524521600	19	# 1 Jan 1980
 2571782400	20	# 1 Jul 1981
 2603318400	21	# 1 Jul 1982
 2634854400	22	# 1 Jul 1983
 2698012800	23	# 1 Jul 1985
 2776982400	24	# 1 Jan 1988
 2840140800	25	# 1 Jan 1990
 2871676800	26	# 1 Jan 1991
 2918937600	27	# 1 Jul 1992
 2950473600	28	# 1 Jul 1993
 2982009600	29	# 1 Jul 1994
 3029443200	30	# 1 Jan 1996
 3076704000	31	# 1 Jul 1997
 3124137600	32	# 1 Jan 1999
 3345062400	33	# 1 Jan 2006
 3439756800	34	# 1 Jan 2009
 3550089600	35	# 1 Jul 2012
 3644697600	36	# 1 Jul 2015
 3692217600	37	# 1 Jan 2017
 #	the following special comment contains the
 #	hash value of the data in this file computed
 #	use the secure hash algorithm as specified
 #	by FIPS 180-1. See the files in ~/pub/sha for
 #	the details of how this hash value is
 #	computed. Note that the hash computation
 #	ignores comments and whitespace characters
 #	in data lines. It includes the NTP values
 #	of both the last modification time and the
 #	expiration time of the file, but not the
 #	white space on those lines.
 #	the hash line is also ignored in the
 #	computation.
+#
-#h 	16edd0f0 3666784f 37db6bdd e74ced87 59af48f1
+#	ASTRONOMICAL TIME (UT1) is the time scale based on the rate of rotation of the earth.
 #	It is now mainly derived from Very Long Baseline Interferometry (VLBI). The various
 #	irregular fluctuations progressively detected in the rotation rate of the Earth lead
 #	in 1972 to the replacement of UT1 by UTC as the reference time scale.
+#
+#
 #	LEAP SECOND
 #	Atomic clocks are more stable than the rate of the earth rotation since the latter
 #	undergoes a full range of geophysical perturbations at various time scales: lunisolar
 #	and core-mantle torques, atmospheric and oceanic effetcs, etc.
 #	Leap seconds are needed to keep the two time scales in agreement, i.e. UT1-UTC smaller
 #	than 0.9 second. Therefore, when necessary a "leap second" is applied to UTC.
 #	Since the adoption of this system in 1972 it has been necessary to add a number of seconds to UTC,
 #	firstly due to the initial choice of the value of the second (1/86400 mean solar day of
 #	the year 1820) and secondly to the general slowing down of the Earth's rotation. It is
 #	theorically possible to have a negative leap second (a second removed from UTC), but so far,
 #	all leap seconds have been positive (a second has been added to UTC). Based on what we know about
 #	the earth's rotation, it is unlikely that we will ever have a negative leap second.
+#
+#
 #	HISTORY
 #	The first leap second was added on June 30, 1972. Until yhe year 2000, it was necessary in average to add a
 #       leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with an
 #	average interval of 3 to 4 years due to the acceleration of the Earth rotation speed.
+#
+#
 #	RESPONSABILITY OF THE DECISION TO INTRODUCE A LEAP SECOND IN UTC
 #	The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Center of
 #	the International Earth Rotation and reference System Service (IERS). This center is located at Paris
 #	Observatory. According to international agreements, leap seconds should only be scheduled for certain dates:
 #	first preference is given to the end of December and June, and second preference at the end of March
 #	and September. Since the introduction of leap seconds in 1972, only dates in June and December were used.
+#
 #		Questions or comments to:
 #			Christian Bizouard:  christian.bizouard@obspm.fr
 #			Earth orientation Center of the IERS
 #			Paris Observatory, France
+#
+#
+#
 #    	COPYRIGHT STATUS OF THIS FILE
 #    	This file is in the public domain.
+#
+#
 #	VALIDITY OF THE FILE
 #	It is important to express the validity of the file. These next two dates are
 #	given in units of seconds since 1900.0.
+#
 #	1) Last update of the file.
+#
 #	Updated through IERS Bulletin C (https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat)
+#
 #	The following line shows the last update of this file in NTP timestamp:
+#
 #$	3913697179
+#
 #	2) Expiration date of the file given on a semi-annual basis: last June or last December
+#
 #	File expires on 28 December 2024
+#
 #	Expire date in NTP timestamp:
+#
 #@	3944332800
+#
+#
 #	LIST OF LEAP SECONDS
 #	NTP timestamp (X parameter) is the number of seconds since 1900.0
+#
 #	MJD: The Modified Julian Day number. MJD = X/86400 + 15020
+#
 #	DTAI: The difference DTAI= TAI-UTC in units of seconds
 #	It is the quantity to add to UTC to get the time in TAI
+#
 #	Day Month Year : epoch in clear
+#
 #NTP Time      DTAI    Day Month Year
+#
 2272060800      10      # 1 Jan 1972
 2287785600      11      # 1 Jul 1972
 2303683200      12      # 1 Jan 1973
 2335219200      13      # 1 Jan 1974
 2366755200      14      # 1 Jan 1975
 2398291200      15      # 1 Jan 1976
 2429913600      16      # 1 Jan 1977
 2461449600      17      # 1 Jan 1978
 2492985600      18      # 1 Jan 1979
 2524521600      19      # 1 Jan 1980
 2571782400      20      # 1 Jul 1981
 2603318400      21      # 1 Jul 1982
 2634854400      22      # 1 Jul 1983
 2698012800      23      # 1 Jul 1985
 2776982400      24      # 1 Jan 1988
 2840140800      25      # 1 Jan 1990
 2871676800      26      # 1 Jan 1991
 2918937600      27      # 1 Jul 1992
 2950473600      28      # 1 Jul 1993
 2982009600      29      # 1 Jul 1994
 3029443200      30      # 1 Jan 1996
 3076704000      31      # 1 Jul 1997
 3124137600      32      # 1 Jan 1999
 3345062400      33      # 1 Jan 2006
 3439756800      34      # 1 Jan 2009
 3550089600      35      # 1 Jul 2012
 3644697600      36      # 1 Jul 2015
 3692217600      37      # 1 Jan 2017
+#
 #	A hash code has been generated to be able to verify the integrity
 #	of this file. For more information about using this hash code,
 #	please see the readme file in the 'source' directory :
 #	https://hpiers.obspm.fr/iers/bul/bulc/ntp/sources/README
+#
 #h	9dac5845 8acd32c0 2947d462 daf4a943 f58d9391

 @@ -1258,26 +1258,30 @@ Zone America/Menominee	-5:50:27 -	LMT	18
 #	<https://www.jstor.org/stable/1774359>.
+#
 #	Pearce C. The Great Daylight Saving Time Controversy.
 #	Australian Ebook Publisher. 2017. ISBN 978-1-925516-96-8.
+#
 #	Edward W. Whitman, World Time Differences,
 #	Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated),
 #	which I found in the UCLA library.
+#
 #	William Willett, The Waste of Daylight, 19th edition
 #	<http://cs.ucla.edu/~eggert/The-Waste-of-Daylight-19th.pdf>
 #	[PDF] (1914-03)
+#
 # For the 1911/1912 establishment of standard time in French possessions, see:
 # Société Française de Physique, Recueil de constantes physiques (1913),
 # page 752, 18b.
+#
 # See the 'europe' file for Greenland.
 # Canada
 # From Alain LaBonté (1994-11-14):
 # I post here the time zone abbreviations standardized in Canada
 # for both English and French in the CAN/CSA-Z234.4-89 standard....
+#
 #	UTC	Standard time	Daylight saving time
 #	offset	French	English	French	English
 #	-2:30	-	-	HAT	NDT
 #	-3	-	-	HAA	ADT
 #	-3:30	HNT	NST	-	-
 @@ -1344,27 +1348,27 @@ Zone America/Menominee	-5:50:27 -	LMT	18
 # does not seem to believe in bookmarks.  To see the news release, click the
 # following link and search for "Daylight Savings Time Change".  Press the
 # "Daylight Savings Time Change" link; it will fire off a popup using
 # JavaScript.
 # http://www.exec.gov.nt.ca/currentnews/currentPR.asp?mode=archive
 # ...
 # Nunavut
 # An amendment to the Interpretation Act was registered on February 19/2007....
 # http://action.attavik.ca/home/justice-gn/attach/2007/gaz02part2.pdf
 # From Paul Eggert (2014-10-18):
 # H. David Matthews and Mary Vincent's map
 # "It's about TIME", _Canadian Geographic_ (September-October 1998)
-# http://www.canadiangeographic.ca/Magazine/SO98/alacarte.asp
+# https://web.archive.org/web/19990827055050/https://canadiangeographic.ca/SO98/geomap.htm
 # contains detailed boundaries for regions observing nonstandard
 # time and daylight saving time arrangements in Canada circa 1998.
+#
 # National Research Council Canada maintains info about time zones and DST.
 # https://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html
 # https://www.nrc-cnrc.gc.ca/eng/services/time/faq/index.html#Q5
 # Its unofficial information is often taken from Matthews and Vincent.
 # From Paul Eggert (2006-06-27):
 # For now, assume all of DST-observing Canada will fall into line with the
 # new US DST rules,
 # From Chris Walton (2011-12-01)
 @@ -1636,26 +1640,35 @@ Zone America/Blanc-Sablon -3:48:28 -	LMT
 # time at 2 am Sunday morning (which agrees with the database), and that:
+#
 #     The one-hour setback will go into effect throughout most of Ontario,
 #     except in areas like Windsor which remains on standard time all year.
+#
 # ... I don't know if Windsor began observing DST when Detroit did,
 # or in 1974, or on some other date.
+#
 # By the way, the article continues by noting that:
+#
 #     Some cities in the United States have pushed the deadline back
 #     three weeks and will change over from daylight saving in October.
 # From Chris Walton (2024-01-09):
 # The [Toronto] changes in 1947, 1948, and 1949 took place at 2:00 a.m. local
 # time instead of midnight....  Toronto Daily Star - ...
 # April 2, 1947 - Page 39 ... April 7, 1948 - Page 13 ...
 # April 2, 1949 - Page 1 ... April 7, 1949 - Page 24 ...
 # November 25, 1949 - Page 52 ... April 21, 1950 - Page 14 ...
 # September 19, 1950 - Page 46 ... September 20, 1950 - Page 3 ...
 # November 24, 1950 - Page 21
 # From Arthur David Olson (2010-07-17):
+#
 # "Standard Time and Time Zones in Canada" appeared in
 # The Journal of The Royal Astronomical Society of Canada,
 # volume 26, number 2 (February 1932) and, as of 2010-07-17,
 # was available at
 # http://adsabs.harvard.edu/full/1932JRASC..26...49S
+#
 # It includes the text below (starting on page 57):
+#
 #   A list of the places in Canada using daylight saving time would
 # require yearly revision. From information kindly furnished by
 # the provincial governments and by the postmasters in many cities
 @@ -1697,33 +1710,29 @@ Rule	Toronto	1919	only	-	Oct	26	0:00	0	S
 Rule	Toronto	1920	only	-	May	 2	2:00	1:00	D
 Rule	Toronto	1920	only	-	Sep	26	0:00	0	S
 Rule	Toronto	1921	only	-	May	15	2:00	1:00	D
 Rule	Toronto	1921	only	-	Sep	15	2:00	0	S
 Rule	Toronto	1922	1923	-	May	Sun>=8	2:00	1:00	D
 # Shanks & Pottenger say 1923-09-19; assume it's a typo and that "-16"
 # was meant.
 Rule	Toronto	1922	1926	-	Sep	Sun>=15	2:00	0	S
 Rule	Toronto	1924	1927	-	May	Sun>=1	2:00	1:00	D
 Rule	Toronto	1927	1937	-	Sep	Sun>=25	2:00	0	S
 Rule	Toronto	1928	1937	-	Apr	Sun>=25	2:00	1:00	D
 Rule	Toronto	1938	1940	-	Apr	lastSun	2:00	1:00	D
 Rule	Toronto	1938	1939	-	Sep	lastSun	2:00	0	S
-Rule	Toronto	1945	1946	-	Sep	lastSun	2:00	0	S
+Rule	Toronto	1945	1948	-	Sep	lastSun	2:00	0	S
-Rule	Toronto	1946	only	-	Apr	lastSun	2:00	1:00	D
+Rule	Toronto	1946	1973	-	Apr	lastSun	2:00	1:00	D
-Rule	Toronto	1947	1949	-	Apr	lastSun	0:00	1:00	D
+Rule	Toronto	1949	1950	-	Nov	lastSun	2:00	0	S
 Rule	Toronto	1947	1948	-	Sep	lastSun	0:00	0	S
 Rule	Toronto	1949	only	-	Nov	lastSun	0:00	0	S
 Rule	Toronto	1950	1973	-	Apr	lastSun	2:00	1:00	D
 Rule	Toronto	1950	only	-	Nov	lastSun	2:00	0	S
 Rule	Toronto	1951	1956	-	Sep	lastSun	2:00	0	S
 # Shanks & Pottenger say Toronto ended DST a week early in 1971,
 # namely on 1971-10-24, but Mark Brader wrote (2003-05-31) that this
 # is wrong, and that he had confirmed it by checking the 1971-10-30
 # Toronto Star, which said that DST was ending 1971-10-31 as usual.
 Rule	Toronto	1957	1973	-	Oct	lastSun	2:00	0	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/Toronto	-5:17:32 -	LMT	1895
 			-5:00	Canada	E%sT	1919
 			-5:00	Toronto	E%sT	1942 Feb  9  2:00s
 			-5:00	Canada	E%sT	1946
 @@ -3491,27 +3500,27 @@ Zone America/Tegucigalpa -5:48:52 -	LMT
 # http://www.jamaicaobserver.com/columns/The-politician-in-all-of-us_17573647
+#
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 		#STDOFF	-5:07:10.41
 Zone	America/Jamaica	-5:07:10 -	LMT	1890        # Kingston
 			-5:07:10 -	KMT	1912 Feb    # Kingston Mean Time
 			-5:00	-	EST	1974
 			-5:00	US	E%sT	1984
 			-5:00	-	EST
 # Martinique
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/Martinique	-4:04:20 -      LMT	1890        # Fort-de-France
-			-4:04:20 -	FFMT	1911 May    # Fort-de-France MT
+			-4:04:20 -	FFMT	1911 May  1 # Fort-de-France MT
 			-4:00	-	AST	1980 Apr  6
 			-4:00	1:00	ADT	1980 Sep 28
 			-4:00	-	AST
 # Montserrat
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/Montserrat	-4:08:52 -	LMT	1911 Jul  1  0:01 # Cork Hill
 			-4:00	-	AST
 # Nicaragua
+#
 # This uses Shanks & Pottenger for times before 2005.
+#
 @@ -3594,27 +3603,27 @@ Zone America/Puerto_Rico -4:24:25 -	LMT
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/St_Kitts	-4:10:52 -	LMT	1912 Mar  2 # Basseterre
 			-4:00	-	AST
 # St Lucia
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/St_Lucia	-4:04:00 -	LMT	1890 # Castries
 			-4:04:00 -	CMT	1912 # Castries Mean Time
 			-4:00	-	AST
 # St Pierre and Miquelon
 # There are too many St Pierres elsewhere, so we'll use 'Miquelon'.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone America/Miquelon	-3:44:40 -	LMT	1911 May 15 # St Pierre
+Zone America/Miquelon	-3:44:40 -	LMT	1911 Jun 15 # St Pierre
 			-4:00	-	AST	1980 May
 			-3:00	-	-03	1987
 			-3:00	Canada	-03/-02
 # St Vincent & the Grenadines
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone America/St_Vincent	-4:04:56 -	LMT	1890 # Kingstown
 			-4:04:56 -	KMT	1912 # Kingstown Mean Time
 			-4:00	-	AST
 # Sint Maarten
 # See America/Lower_Princes in southamerica.

 @@ -85,27 +85,27 @@ necessarily follow database guidelines.
 <p>
 As described below, reference source code for using the
 <code><abbr>tz</abbr></code> database is also available.
 The <code><abbr>tz</abbr></code> code is upwards compatible with <a
 href="https://en.wikipedia.org/wiki/POSIX">POSIX</a>, an international
 standard for <a
 href="https://en.wikipedia.org/wiki/Unix">UNIX</a>-like systems.
 As of this writing, the current edition of POSIX is: <a
 href="https://pubs.opengroup.org/onlinepubs/9699919799/"> The Open
 Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018
 Edition.
 Because the database's scope encompasses real-world changes to civil
 timekeeping, its model for describing time is more complex than the
-standard and daylight saving times supported by POSIX.
+standard and daylight saving times supported by POSIX.1-2017.
 A <code><abbr>tz</abbr></code> timezone corresponds to a ruleset that can
 have more than two changes per year, these changes need not merely
 flip back and forth between two alternatives, and the rules themselves
 can change at times.
 Whether and when a timezone changes its clock,
 and even the timezone's notional base offset from <abbr>UTC</abbr>,
 are variable.
 It does not always make sense to talk about a timezone's
 "base offset", which is not necessarily a single number.
 </p>
 </section>
 @@ -177,27 +177,27 @@ choosing timezone names,
 in decreasing order of importance:
 </p>
 <ul>
   <li>
     Use only valid POSIX file name components (i.e., the parts of
     names other than '<code>/</code>').
     Do not use the file name components '<code>.</code>' and
     '<code>..</code>'.
     Within a file name component, use only <a
     href="https://en.wikipedia.org/wiki/ASCII">ASCII</a> letters,
     '<code>.</code>', '<code>-</code>' and '<code>_</code>'.
     Do not use digits, as that might create an ambiguity with <a
-    href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03">POSIX
+    href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03">POSIX.1-2017
     <code>TZ</code> strings</a>.
     A file name component must not exceed 14 characters or start with
     '<code>-</code>'.
     E.g., prefer <code>America/Noronha</code> to
     <code>America/Fernando_de_Noronha</code>.
     Exceptions: see the discussion of legacy names below.
   </li>
   <li>
     A name must not be empty, or contain '<code>//</code>', or
     start or end with '<code>/</code>'.
   </li>
   <li>
     Do not use names that differ only in case.
 @@ -352,38 +352,43 @@ The file zone1970.tab lists
 to name timezones.
 It is intended to be an exhaustive list of names for geographic
 regions as described above; this is a subset of the timezones in the data.
 Although a <code>zone1970.tab</code> location's
 <a href="https://en.wikipedia.org/wiki/Longitude">longitude</a>
 corresponds to
 its <a href="https://en.wikipedia.org/wiki/Local_mean_time">local mean
 time (<abbr>LMT</abbr>)</a> offset with one hour for every 15&deg;
 east longitude, this relationship is not exact.
 The backward-compatibility file <code>zone.tab</code> is similar
 but conforms to the older-version guidelines related to <abbr>ISO</abbr> 3166-1;
 it lists only one country code per entry and unlike <code>zone1970.tab</code>
 it can list names defined in <code>backward</code>.
 Applications that process only timestamps from now on can instead use the file
 <code>zonenow.tab</code>, which partitions the world more coarsely,
 into regions where clocks agree now and in the predicted future;
 this file is smaller and simpler than <code>zone1970.tab</code>
 and <code>zone.tab</code>.
 </p>
 <p>
 The database defines each timezone name to be a zone, or a link to a zone.
 The source file <code>backward</code> defines links for backward
 compatibility; it does not define zones.
 Although <code>backward</code> was originally designed to be optional,
 nowadays distributions typically use it
 and no great weight should be attached to whether a link
 is defined in <code>backward</code> or in some other file.
 The source file <code>etcetera</code> defines names that may be useful
-on platforms that do not support POSIX-style <code>TZ</code> strings;
+on platforms that do not support POSIX.1-2017-style <code>TZ</code> strings;
 no other source file other than <code>backward</code>
 contains links to its zones.
 One of <code>etcetera</code>'s names is <code>Etc/UTC</code>,
 used by functions like <code>gmtime</code> to obtain leap
 second information on platforms that support leap seconds.
 Another <code>etcetera</code> name, <code>GMT</code>,
 is used by older code releases.
 </p>
 </section>
 <section>
   <h2 id="abbreviations">Time zone abbreviations</h2>
 <p>
 @@ -411,27 +416,27 @@ in decreasing order of importance:
     Standard Time</a> preferred "ChST", so lower-case letters are now
     allowed.
     Also, POSIX from 2001 on relaxed the rule to allow '<code>-</code>',
     '<code>+</code>', and alphanumeric characters from the portable
     character set in the current locale.
     In practice ASCII alphanumerics and '<code>+</code>' and
     '<code>-</code>' are safe in all locales.
     <p>
     In other words, in the C locale the POSIX extended regular
     expression <code>[-+[:alnum:]]{3,6}</code> should match the
     abbreviation.
     This guarantees that all abbreviations could have been specified by a
-    POSIX <code>TZ</code> string.
+    POSIX.1-2017 <code>TZ</code> string.
     </p>
   </li>
   <li>
     Use abbreviations that are in common use among English-speakers,
     e.g., 'EST' for Eastern Standard Time in North America.
     We assume that applications translate them to other languages
     as part of the normal localization process; for example,
     a French application might translate 'EST' to 'HNE'.
     <p>
     <small>These abbreviations (for standard/daylight/etc. time) are:
       ACST/ACDT Australian Central,
       AST/ADT/APT/AWT/ADDT Atlantic,
 @@ -755,32 +760,32 @@ href="https://www.dissentmagazine.org/bl
     numbered 00 through 23, except when clock transitions occur.
     Pre-standard time is modeled as local mean time.
     However, historically many people used other calendars and other timescales.
     For example, the Roman Empire used
     the <a href="https://en.wikipedia.org/wiki/Julian_calendar">Julian
     calendar</a>,
     and <a href="https://en.wikipedia.org/wiki/Roman_timekeeping">Roman
     timekeeping</a> had twelve varying-length daytime hours with a
     non-hour-based system at night.
     And even today, some local practices diverge from the Gregorian
     calendar with 24-hour days. These divergences range from
     relatively minor, such as Japanese bars giving times like "24:30" for the
     wee hours of the morning, to more-significant differences such as <a
-    href="https://www.pri.org/stories/2015-01-30/if-you-have-meeting-ethiopia-you-better-double-check-time">the
+    href="https://theworld.org/stories/2015-01-30/if-you-have-meeting-ethiopia-you-better-double-check-time">the
     east African practice of starting the day at dawn</a>, renumbering
     the Western 06:00 to be 12:00. These practices are largely outside
     the scope of the <code><abbr>tz</abbr></code> code and data, which
     provide only limited support for date and time localization
-    such as that required by POSIX.
+    such as that required by POSIX.1-2017.
     If <abbr>DST</abbr> is not used a different time zone
     can often do the trick; for example, in Kenya a <code>TZ</code> setting
     like <code>&lt;-03&gt;3</code> or <code>America/Cayenne</code> starts
     the day six hours later than <code>Africa/Nairobi</code> does.
   </li>
   <li>
     Early clocks were less reliable, and data entries do not represent
     clock error.
   </li>
   <li>
     The <code><abbr>tz</abbr></code> database assumes Universal Time
     (<abbr>UT</abbr>) as an origin, even though <abbr>UT</abbr> is not
     standardized for older timestamps.
 @@ -857,43 +862,43 @@ different dates.
 <p>
 The <code><abbr>tz</abbr></code> code contains time and date functions
 that are upwards compatible with those of POSIX.
 Code compatible with this package is already
 <a href="tz-link.html#tzdb">part of many platforms</a>, where the
 primary use of this package is to update obsolete time-related files.
 To do this, you may need to compile the time zone compiler
 '<code>zic</code>' supplied with this package instead of using the
 system '<code>zic</code>', since the format of <code>zic</code>'s
 input is occasionally extended, and a platform may still be shipping
 an older <code>zic</code>.
 </p>
-<h3 id="POSIX">POSIX properties and limitations</h3>
+<h3 id="POSIX">POSIX.1-2017 properties and limitations</h3>
 <ul>
   <li>
     <p>
-    In POSIX, time display in a process is controlled by the
+    In POSIX.1-2017, time display in a process is controlled by the
     environment variable <code>TZ</code>.
-    Unfortunately, the POSIX
+    Unfortunately, the POSIX.1-2017
     <code>TZ</code> string takes a form that is hard to describe and
     is error-prone in practice.
-    Also, POSIX <code>TZ</code> strings cannot deal with daylight
+    Also, POSIX.1-2017 <code>TZ</code> strings cannot deal with daylight
     saving time rules not based on the Gregorian calendar (as in
     Morocco), or with situations where more than two time zone
     abbreviations or <abbr>UT</abbr> offsets are used in an area.
     </p>
     <p>
-    The POSIX <code>TZ</code> string takes the following form:
+    The POSIX.1-2017 <code>TZ</code> string takes the following form:
     </p>
     <p>
     <var>stdoffset</var>[<var>dst</var>[<var>offset</var>][<code>,</code><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]]]
     </p>
     <p>
     where:
     </p>
     <dl>
       <dt><var>std</var> and <var>dst</var></dt><dd>
 	are 3 or more characters specifying the standard
 @@ -940,38 +945,38 @@ an older zic.
 	    month <var>m</var> of the year, where week 1 is the first
 	    week in which day <var>d</var> appears, and
 	    '<code>5</code>' stands for the last week in which
 	    day <var>d</var> appears (which may be either the 4th or
 th week).
 	    Typically, this is the only useful form; the <var>n</var>
 	    and <code>J</code><var>n</var> forms are rarely used.
 	  </dd>
 	</dl>
       </dd>
     </dl>
     <p>
-    Here is an example POSIX <code>TZ</code> string for New
+    Here is an example POSIX.1-2017 <code>TZ</code> string for New
     Zealand after 2007.
     It says that standard time (<abbr>NZST</abbr>) is 12 hours ahead
     of <abbr>UT</abbr>, and that daylight saving time
     (<abbr>NZDT</abbr>) is observed from September's last Sunday at
 :00 until April's first Sunday at 03:00:
     </p>
     <pre><code>TZ='NZST-12NZDT,M9.5.0,M4.1.0/3'</code></pre>
     <p>
-    This POSIX <code>TZ</code> string is hard to remember, and
+    This POSIX.1-2017 <code>TZ</code> string is hard to remember, and
     mishandles some timestamps before 2008.
     With this package you can use this instead:
     </p>
     <pre><code>TZ='Pacific/Auckland'</code></pre>
   </li>
   <li>
     POSIX does not define the <abbr>DST</abbr> transitions
     for <code>TZ</code> values like
     "<code>EST5EDT</code>".
     Traditionally the current <abbr>US</abbr> <abbr>DST</abbr> rules
     were used to interpret such values, but this meant that the
     <abbr>US</abbr> <abbr>DST</abbr> rules were compiled into each
 @@ -989,61 +994,61 @@ an older zic.
   <li>
     In POSIX, there is no tamper-proof way for a process to learn the
     system's best idea of local (wall clock) time.
     This is important for applications that an administrator wants
     used only at certain times &ndash; without regard to whether the
     user has fiddled the
     <code>TZ</code> environment variable.
     While an administrator can "do everything in <abbr>UT</abbr>" to
     get around the problem, doing so is inconvenient and precludes
     handling daylight saving time shifts &ndash; as might be required to
     limit phone calls to off-peak hours.
   </li>
   <li>
-    POSIX provides no convenient and efficient way to determine
+    POSIX.1-2017 provides no convenient and efficient way to determine
     the <abbr>UT</abbr> offset and time zone abbreviation of arbitrary
     timestamps, particularly for timezones
     that do not fit into the POSIX model.
   </li>
   <li>
     POSIX requires that <code>time_t</code> clock counts exclude leap
     seconds.
   </li>
   <li>
     The <code><abbr>tz</abbr></code> code attempts to support all the
     <code>time_t</code> implementations allowed by POSIX.
     The <code>time_t</code> type represents a nonnegative count of seconds
     since 1970-01-01 00:00:00 <abbr>UTC</abbr>, ignoring leap seconds.
     In practice, <code>time_t</code> is usually a signed 64- or 32-bit
     integer; 32-bit signed <code>time_t</code> values stop working after
 -01-19 03:14:07 <abbr>UTC</abbr>, so new implementations these
     days typically use a signed 64-bit integer.
     Unsigned 32-bit integers are used on one or two platforms, and 36-bit
     and 40-bit integers are also used occasionally.
     Although earlier POSIX versions allowed <code>time_t</code> to be a
     floating-point type, this was not supported by any practical system,
     and POSIX.1-2013 and the <code><abbr>tz</abbr></code> code both
     require <code>time_t</code> to be an integer type.
   </li>
 </ul>
-<h3 id="POSIX-extensions">Extensions to POSIX in the
+<h3 id="POSIX-extensions">Extensions to POSIX.1-2017 in the
 <code><abbr>tz</abbr></code> code</h3>
 <ul>
   <li>
     <p>
     The <code>TZ</code> environment variable is used in generating
     the name of a file from which time-related information is read
-    (or is interpreted à la POSIX); <code>TZ</code> is no longer
+    (or is interpreted à la POSIX.1-2017); <code>TZ</code> is no longer
     constrained to be a string containing abbreviations
     and numeric data as described <a href="#POSIX">above</a>.
     The file's format is <dfn><abbr>TZif</abbr></dfn>,
     a timezone information format that contains binary data; see
     <a href="https://datatracker.ietf.org/doc/html/8536">Internet
     <abbr>RFC</abbr> 8536</a>.
     The daylight saving time rules to be used for a
     particular timezone are encoded in the
     <abbr>TZif</abbr> file; the format of the file allows <abbr>US</abbr>,
     Australian, and other rules to be encoded, and
     allows for situations where more than two time zone
     abbreviations are used.
     </p>

 @@ -152,27 +152,27 @@ function prehash_rule_names( \
 function make_line(n, field, \
 		   f, r)
+{
   r = field[1]
   for (f = 2; f <= n; f++)
     r = r " " field[f]
   return r
+}
 # Process the input line LINE and save it for later output.
 function process_input_line(line, \
-			    f, field, end, i, n, r, startdef, \
+			    f, field, end, n, outline, r, \
 			    linkline, ruleline, zoneline)
+{
   # Remove comments, normalize spaces, and append a space to each line.
   sub(/#.*/, "", line)
   line = line " "
   gsub(/[\t ]+/, " ", line)
   # Abbreviate keywords and determine line type.
   linkline = sub(/^Link /, "L ", line)
   ruleline = sub(/^Rule /, "R ", line)
   zoneline = sub(/^Zone /, "Z ", line)
   # Replace FooAsia rules with the same rules without "Asia", as they
 @@ -189,28 +189,30 @@ function process_input_line(line, \
     line = substr(line, 1, RSTART - 1) substr(line, RSTART + 2)
   # Abbreviate weekday names.
   while (match(line, / (last)?(Mon|Wed|Fri)[ <>]/)) {
     end = RSTART + RLENGTH
     line = substr(line, 1, end - 4) substr(line, end - 1)
+  }
   while (match(line, / (last)?(Sun|Tue|Thu|Sat)[ <>]/)) {
     end = RSTART + RLENGTH
     line = substr(line, 1, end - 3) substr(line, end - 1)
+  }
   # Abbreviate "max", "min", "only" and month names.
-  gsub(/ max /, " ma ", line)
+  # Although "max" and "min" can both be abbreviated to just "m",
-  gsub(/ min /, " mi ", line)
+  # the longer forms "ma" and "mi" are needed with zic 2023d and earlier.
   gsub(/ max /, dataform == "vanguard" ? " m " : " ma ", line)
   gsub(/ min /, dataform == "vanguard" ? " m " : " mi ", line)
   gsub(/ only /, " o ", line)
   gsub(/ Jan /, " Ja ", line)
   gsub(/ Feb /, " F ", line)
   gsub(/ Apr /, " Ap ", line)
   gsub(/ Aug /, " Au ", line)
   gsub(/ Sep /, " S ", line)
   gsub(/ Oct /, " O ", line)
   gsub(/ Nov /, " N ", line)
   gsub(/ Dec /, " D ", line)
   # Strip leading and trailing space.
   sub(/^ /, "", line)
   sub(/ $/, "", line)
 @@ -224,86 +226,116 @@ function process_input_line(line, \
   # Remove unnecessary trailing " Ja" (for January).
   sub(/ Ja$/, "", line)
   n = split(line, field)
   # Record which rule names are used, and generate their abbreviations.
   f = zoneline ? 4 : linkline || ruleline ? 0 : 2
   r = field[f]
   if (r ~ /^[^-+0-9]/) {
     rule_used[r] = 1
+  }
   # If this zone supersedes an earlier one, delete the earlier one
   # from the saved output lines.
   startdef = ""
   if (zoneline)
     zonename = startdef = field[2]
   else if (linkline)
     zonename = startdef = field[3]
   else if (ruleline)
     zonename = ""
   if (startdef) {
     i = zonedef[startdef]
     if (i) {
       do
 	output_line[i - 1] = ""
       while (output_line[i++] ~ /^[-+0-9]/);
   zonedef[zonename] = nout + 1
-  # Save the line for later output.
+  # Save the information for later output.
-  output_line[nout++] = make_line(n, field)
+  outline = make_line(n, field)
   if (ruleline)
     rule_output_line[nrule_out++] = outline
   else if (linkline) {
     # In vanguard format with Gawk, links are output sorted by destination.
     if (dataform == "vanguard" && PROCINFO["version"])
       linkdef[zonename] = field[2]
     else
       link_output_line[nlink_out++] = outline
   }else
     zonedef[zonename] = (zoneline ? "" : zonedef[zonename] "\n") outline
+}
 function omit_unused_rules( \
 			   i, field)
+{
-  for (i = 0; i < nout; i++) {
+  for (i = 0; i < nrule_out; i++) {
-    split(output_line[i], field)
+    split(rule_output_line[i], field)
-    if (field[1] == "R" && !rule_used[field[2]]) {
+    if (!rule_used[field[2]])
-      output_line[i] = ""
+      rule_output_line[i] = ""
+  }
+}
 function abbreviate_rule_names( \
-			       abbr, f, field, i, n, r)
+			       abbr, f, field, i, n, newdef, newline, r, \
 			       zoneline, zonelines, zonename)
+{
-  for (i = 0; i < nout; i++) {
+  for (i = 0; i < nrule_out; i++) {
-    n = split(output_line[i], field)
+    n = split(rule_output_line[i], field)
     if (n) {
-      f = field[1] == "Z" ? 4 : field[1] == "L" ? 0 : 2
+      r = field[2]
       r = field[f]
       if (r ~ /^[^-+0-9]/) {
 	abbr = rule[r]
 	if (!abbr) {
 	  rule[r] = abbr = gen_rule_name(r)
+	}
-	field[f] = abbr
+	field[2] = abbr
-	output_line[i] = make_line(n, field)
+	rule_output_line[i] = make_line(n, field)
+      }
+    }
+  }
   for (zonename in zonedef) {
     zonelines = split(zonedef[zonename], zoneline, /\n/)
     newdef = ""
     for (i = 1; i <= zonelines; i++) {
       newline = zoneline[i]
       n = split(newline, field)
       f = i == 1 ? 4 : 2
       r = rule[field[f]]
       if (r) {
 	field[f] = r
 	newline = make_line(n, field)
+      }
       newdef = (newdef ? newdef "\n" : "") newline
+    }
     zonedef[zonename] = newdef
+  }
+}
 function output_saved_lines( \
-			    i)
+			    i, zonename)
+{
-  for (i = 0; i < nout; i++)
+  for (i = 0; i < nrule_out; i++)
-    if (output_line[i])
+    if (rule_output_line[i])
-      print output_line[i]
+      print rule_output_line[i]
   # When using gawk, output zones sorted by name.
   # This makes the output a bit more compressible.
   PROCINFO["sorted_in"] = "@ind_str_asc"
   for (zonename in zonedef)
     print zonedef[zonename]
   if (nlink_out)
     for (i = 0; i < nlink_out; i++)
       print link_output_line[i]
   else {
     # When using gawk, output links sorted by destination.
     # This also helps compressibility a bit.
     PROCINFO["sorted_in"] = "@val_type_asc"
     for (zonename in linkdef)
       printf "L %s %s\n", linkdef[zonename], zonename
+  }
+}
 BEGIN {
   # Files that the output normally depends on.
   default_dep["africa"] = 1
   default_dep["antarctica"] = 1
   default_dep["asia"] = 1
   default_dep["australasia"] = 1
   default_dep["backward"] = 1
   default_dep["etcetera"] = 1
   default_dep["europe"] = 1
   default_dep["factory"] = 1
   default_dep["northamerica"] = 1

	@@ -189,42 +189,44 @@ XX -0117+03649 Africa/Nairobi eastern Af		@@ -189,42 +189,44 @@ XX -0117+03649 Africa/Nairobi eastern Af
189	# +03 - MSK	189	# +03 - MSK
190	XX +554521+0373704 Europe/Moscow Moscow ("MSK")	190	XX +554521+0373704 Europe/Moscow Moscow ("MSK")
191	#	191	#
192	# +03:30	192	# +03:30
193	XX +3540+05126 Asia/Tehran Iran	193	XX +3540+05126 Asia/Tehran Iran
194	#	194	#
195	# +04	195	# +04
196	XX +2518+05518 Asia/Dubai Russia; Caucasus; Persian Gulf; Seychelles; Réunion	196	XX +2518+05518 Asia/Dubai Russia; Caucasus; Persian Gulf; Seychelles; Réunion
197	#	197	#
198	# +04:30	198	# +04:30
199	XX +3431+06912 Asia/Kabul Afghanistan	199	XX +3431+06912 Asia/Kabul Afghanistan
200	#	200	#
201	# +05	201	# +05
202	XX +4120+06918 Asia/Tashkent Russia; Tajikistan; Turkmenistan; Uzbekistan; Maldives	202	XX +4120+06918 Asia/Tashkent Russia; west Kazakhstan; Tajikistan; Turkmenistan; Uzbekistan; Maldives
203	#	203	#
204	# +05 - PKT	204	# +05 - PKT
205	XX +2452+06703 Asia/Karachi Pakistan ("PKT")	205	XX +2452+06703 Asia/Karachi Pakistan ("PKT")
206	#	206	#
207	# +05:30	207	# +05:30
208	XX +0656+07951 Asia/Colombo Sri Lanka	208	XX +0656+07951 Asia/Colombo Sri Lanka
209	#	209	#
210	# +05:30 - IST	210	# +05:30 - IST
211	XX +2232+08822 Asia/Kolkata India ("IST")	211	XX +2232+08822 Asia/Kolkata India ("IST")
212	#	212	#
213	# +05:45	213	# +05:45
214	XX +2743+08519 Asia/Kathmandu Nepal	214	XX +2743+08519 Asia/Kathmandu Nepal
215	#	215	#
216	# +06	216	# +06
217	XX +2343+09025 Asia/Dhaka Russia; Kyrgyzstan; Bhutan; Bangladesh; Chagos	217	XX +2343+09025 Asia/Dhaka Russia; Kyrgyzstan; Bhutan; Bangladesh; Chagos
		218	# +06 until 2024-03-01; then +05
		219	XX +4315+07657 Asia/Almaty Kazakhstan (except western areas)
218	#	220	#
219	# +06:30	221	# +06:30
220	XX +1647+09610 Asia/Yangon Myanmar; Cocos	222	XX +1647+09610 Asia/Yangon Myanmar; Cocos
221	#	223	#
222	# +07	224	# +07
223	XX +1345+10031 Asia/Bangkok Russia; Indochina; Christmas Island	225	XX +1345+10031 Asia/Bangkok Russia; Indochina; Christmas Island
224	#	226	#
225	# +07 - WIB	227	# +07 - WIB
226	XX -0610+10648 Asia/Jakarta Indonesia ("WIB")	228	XX -0610+10648 Asia/Jakarta Indonesia ("WIB")
227	#	229	#
228	# +08	230	# +08
229	XX +0117+10351 Asia/Singapore Russia; Brunei; Malaysia; Singapore	231	XX +0117+10351 Asia/Singapore Russia; Brunei; Malaysia; Singapore
230	#	232	#

 @@ -1,21 +1,21 @@
 # tzdb data for ships at sea and other miscellany
 # This file is in the public domain, so clarified as of
 # 2009-05-17 by Arthur David Olson.
 # These entries are for uses not otherwise covered by the tz database.
 # Their main practical use is for platforms like Android that lack
-# support for POSIX-style TZ strings.  On such platforms these entries
+# support for POSIX.1-2017-style TZ strings.  On such platforms these entries
 # can be useful if the timezone database is wrong or if a ship or
 # aircraft at sea is not in a timezone.
 # Starting with POSIX 1003.1-2001, the entries below are all
 # unnecessary as settings for the TZ environment variable.  E.g.,
 # instead of TZ='Etc/GMT+4' one can use the POSIX setting TZ='<-04>+4'.
+#
 # Do not use a POSIX TZ setting like TZ='GMT+4', which is four hours
 # behind GMT but uses the completely misleading abbreviation "GMT".
 # The following zone is used by tzcode functions like gmtime,
 # which load the "UTC" file to handle seconds properly.
 Zone	Etc/UTC		0	-	UTC

 @@ -1018,29 +1018,54 @@ Zone	Europe/Sofia	1:33:16 -	LMT	1880
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Europe/Zagreb	1:03:52	-	LMT	1884
 :00	-	CET	1941 Apr 18 23:00
 :00	C-Eur	CE%sT	1945 May  8  2:00s
 :00	1:00	CEST	1945 Sep 16  2:00s
 :00	-	CET	1982 Nov 27
 :00	EU	CE%sT
 # Cyprus
 # Please see the 'asia' file for Asia/Nicosia.
 # Czech Republic (Czechia)
+#
-# From Paul Eggert (2018-04-15):
+# From Ivan Benovic (2024-01-30):
-# The source for Czech data is: Kdy začíná a končí letní čas. 2018-04-15.
+# https://www.slov-lex.sk/pravne-predpisy/SK/ZZ/1946/54/
 # (This is an official link to the Czechoslovak Summer Time Act of
 # March 8, 1946 that authorizes the Czechoslovak government to set the
 # exact dates of change to summer time and back to Central European Time.
 # The act also implicitly confirms Central European Time as the
 # official time zone of Czechoslovakia and currently remains in force
 # in both the Czech Republic and Slovakia.)
 # https://www.psp.cz/eknih/1945pns/tisky/t0216_00.htm
 # (This is a link to the original legislative proposal dating back to
 # February 22, 1946. The accompanying memorandum to the proposal says
 # that an advisory committee on European railroad transportation that
 # met in Brussels in October 1945 decided that the change of time
 # should be carried out in all participating countries in a strictly
 # coordinated manner....)
+#
 # From Paul Eggert (2024-01-30):
 # The source for Czech data is: Kdy začíná a končí letní čas.
 # https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas
 # Its main text disagrees with its quoted sources only in 1918,
 # where the main text says spring and autumn transitions
 # occurred at 02:00 and 03:00 respectively (as usual),
 # whereas the 1918 source "Oznámení o zavedení letního času v roce 1918"
 # says transitions were at 01:00 and 02:00 respectively.
 # As the 1918 source appears to be a humorous piece, and it is
 # unlikely that Prague would have disagreed with its neighbors by an hour,
 # go with the main text for now.
+#
 # We know of no English-language name for historical Czech winter time;
 # abbreviate it as "GMT", as it happened to be GMT.
+#
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Czech	1945	only	-	Apr	Mon>=1	2:00s	1:00	S
 Rule	Czech	1945	only	-	Oct	 1	2:00s	0	-
 Rule	Czech	1946	only	-	May	 6	2:00s	1:00	S
 Rule	Czech	1946	1949	-	Oct	Sun>=1	2:00s	0	-
 Rule	Czech	1947	1948	-	Apr	Sun>=15	2:00s	1:00	S
 Rule	Czech	1949	only	-	Apr	 9	2:00s	1:00	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Europe/Prague	0:57:44 -	LMT	1850
 :57:44	-	PMT	1891 Oct    # Prague Mean Time

 @@ -1,43 +1,40 @@
-# Generate zic format 'leapseconds' from NIST format 'leap-seconds.list'.
+# Generate zic format 'leapseconds' from NIST/IERS format 'leap-seconds.list'.
 # This file is in the public domain.
 # This program uses awk arithmetic.  POSIX requires awk to support
 # exact integer arithmetic only through 10**10, which means for NTP
 # timestamps this program works only to the year 2216, which is the
 # year 1900 plus 10**10 seconds.  However, in practice
 # POSIX-conforming awk implementations invariably use IEEE-754 double
 # and so support exact integers through 2**53.  By the year 2216,
 # POSIX will almost surely require at least 2**53 for awk, so for NTP
 # timestamps this program should be good until the year 285,428,681
 # (the year 1900 plus 2**53 seconds).  By then leap seconds will be
 # long obsolete, as the Earth will likely slow down so much that
 # there will be more than 25 hours per day and so some other scheme
 # will be needed.
 BEGIN {
   print "# Allowance for leap seconds added to each time zone file."
   print ""
   print "# This file is in the public domain."
   print ""
   print "# This file is generated automatically from the data in the public-domain"
-  print "# NIST format leap-seconds.list file, which can be copied from"
+  print "# NIST/IERS format leap-seconds.list file, which can be copied from"
   print "# <ftp://ftp.nist.gov/pub/time/leap-seconds.list>"
   print "# or <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>."
   print "# The NIST file is used instead of its IERS upstream counterpart"
   print "# <https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list>"
-  print "# because under US law the NIST file is public domain"
+  print "# or, in a variant with different comments, from"
-  print "# whereas the IERS file's copyright and license status is unclear."
+  print "# <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>."
   print "# For more about leap-seconds.list, please see"
   print "# The NTP Timescale and Leap Seconds"
   print "# <https://www.eecis.udel.edu/~mills/leap.html>."
   print ""
   print "# The rules for leap seconds are specified in Annex 1 (Time scales) of:"
   print "# Standard-frequency and time-signal emissions."
   print "# International Telecommunication Union - Radiocommunication Sector"
   print "# (ITU-R) Recommendation TF.460-6 (02/2002)"
   print "# <https://www.itu.int/rec/R-REC-TF.460-6-200202-I/>."
   print "# The International Earth Rotation and Reference Systems Service (IERS)"
   print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1"
   print "# (a proxy for Earth's angle in space as measured by astronomers)"
   print "# and publishes leap second data in a copyrighted file"

 @@ -1573,28 +1573,31 @@ Rule	Falk	1984	only	-	Sep	16	0:00	1:00	-
 Rule	Falk	1985	2000	-	Sep	Sun>=9	0:00	1:00	-
 Rule	Falk	1986	2000	-	Apr	Sun>=16	0:00	0	-
 Rule	Falk	2001	2010	-	Apr	Sun>=15	2:00	0	-
 Rule	Falk	2001	2010	-	Sep	Sun>=1	2:00	1:00	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone Atlantic/Stanley	-3:51:24 -	LMT	1890
 			-3:51:24 -	SMT	1912 Mar 12 # Stanley Mean Time
 			-4:00	Falk	-04/-03	1983 May
 			-3:00	Falk	-03/-02	1985 Sep 15
 			-4:00	Falk	-04/-03	2010 Sep  5  2:00
 			-3:00	-	-03
 # French Guiana
 # For the 1911/1912 establishment of standard time in French possessions, see:
 # Société Française de Physique, Recueil de constantes physiques (1913),
 # page 752, 18b.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone America/Cayenne	-3:29:20 -	LMT	1911 Jul
+Zone America/Cayenne	-3:29:20 -	LMT	1911 Jul  1
 			-4:00	-	-04	1967 Oct
 			-3:00	-	-03
 # Guyana
 # From P Chan (2020-11-27):
 # https://books.google.com/books?id=5-5CAQAAMAAJ&pg=SA1-PA547
 # The Official Gazette of British Guiana. (New Series.) Vol. XL. July to
 # December, 1915, p 1547, lists as several notes:
 # "Local Mean Time 3 hours 52 mins. 39 secs. slow of Greenwich Mean Time
 # (Georgetown.) From 1st August, 1911, British Guiana Standard Mean Time 4
 # hours slow of Greenwich Mean Time, by notice in Official Gazette on 1st July,
 # 1911.  From 1st March, 1915, British Guiana Standard Mean Time 3 hours 45

 @@ -1,15 +1,83 @@
 News for the tz database
 Release 2024a - 2024-02-01 09:28:56 -0800
   Briefly:
     Kazakhstan unifies on UTC+5 beginning 2024-03-01.
     Palestine springs forward a week later after Ramadan.
     zic no longer pretends to support indefinite-past DST.
     localtime no longer mishandles Ciudad Juárez in 2422.
   Changes to future timestamps
     Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and
     Asia/Qostanay which together represent the eastern portion of the
     country that will transition from UTC+6 on 2024-03-01 at 00:00 to
     join the western portion.  (Thanks to Zhanbolat Raimbekov.)
     Palestine springs forward a week later than previously predicted
     in 2024 and 2025.  (Thanks to Heba Hamad.)  Change spring-forward
     predictions to the second Saturday after Ramadan, not the first;
     this also affects other predictions starting in 2039.
   Changes to past timestamps
     Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00
     not 00:00.  (Thanks to Đoàn Trần Công Danh.)
     From 1947 through 1949, Toronto's transitions occurred at 02:00
     not 00:00.  (Thanks to Chris Walton.)
     In 1911 Miquelon adopted standard time on June 15, not May 15.
   Changes to code
     The FROM and TO columns of Rule lines can no longer be "minimum"
     or an abbreviation of "minimum", because TZif files do not support
     DST rules that extend into the indefinite past - although these
     rules were supported when TZif files had only 32-bit data, this
     stopped working when 64-bit TZif files were introduced in 1995.
     This should not be a problem for realistic data, since DST was
     first used in the 20th century.  As a transition aid, FROM columns
     like "minimum" are now diagnosed and then treated as if they were
     the year 1900; this should suffice for TZif files on old systems
     with only 32-bit time_t, and it is more compatible with bugs in
 c-and-earlier localtime.c.  (Problem reported by Yoshito
     Umaoka.)
     localtime and related functions no longer mishandle some
     timestamps that occur about 400 years after a switch to a time
     zone with a DST schedule.  In 2023d data this problem was visible
     for some timestamps in November 2422, November 2822, etc. in
     America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)
     strftime %s now uses tm_gmtoff if available.  (Problem and draft
     patch reported by Dag-Erling Smørgrav.)
   Changes to build procedure
     The leap-seconds.list file is now copied from the IERS instead of
     from its downstream counterpart at NIST, as the IERS version is
     now in the public domain too and tends to be more up-to-date.
     (Thanks to Martin Burnicki for liaisoning with the IERS.)
   Changes to documentation
     The strftime man page documents which struct tm members affect
     which conversion specs, and that tzset is called.  (Problems
     reported by Robert Elz and Steve Summit.)
 Release 2023d - 2023-12-21 20:02:24 -0800
   Briefly:
     Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
     Vostok, Antarctica changed time zones on 2023-12-18.
     Casey, Antarctica changed time zones five times since 2020.
     Code and data fixes for Palestine timestamps starting in 2072.
     A new data file zonenow.tab for timestamps starting now.
   Changes to future timestamps
     Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
     the rest of Greenland's timekeeping practice on 2024-03-31, by

 @@ -20,26 +20,30 @@
 # Association's Standard Schedules Information Manual (IATA SSIM),
 # published semiannually.  Law sent in several helpful summaries
 # of the IATA's data after 1990.  Except where otherwise noted,
 # IATA SSIM is the source for entries after 1990.
+#
 # Another source occasionally used is Edward W. Whitman, World Time Differences,
 # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which
 # I found in the UCLA library.
+#
 # For data circa 1899, a common source is:
 # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94.
 # https://www.jstor.org/stable/1774359
+#
 # For the 1911/1912 establishment of standard time in French possessions, see:
 # Société Française de Physique, Recueil de constantes physiques (1913),
 # page 752, 18b.
+#
 # European-style abbreviations are commonly used along the Mediterranean.
 # For sub-Saharan Africa abbreviations were less standardized.
 # Previous editions of this database used WAT, CAT, SAT, and EAT
 # for UT +00 through +03, respectively,
 # but in 1997 Mark R V Murray reported that
 # 'SAST' is the official abbreviation for +02 in the country of South Africa,
 # 'CAT' is commonly used for +02 in countries north of South Africa, and
 # 'WAT' is probably the best name for +01, as the common phrase for
 # the area that includes Nigeria is "West Africa".
+#
 # To summarize, the following abbreviations seemed to have some currency:
 #	 +00	GMT	Greenwich Mean Time
 #	 +02	CAT	Central Africa Time
 @@ -143,27 +147,27 @@ Zone	Africa/Douala	0:38:48	-	LMT	1912
 Zone Atlantic/Cape_Verde -1:34:04 -	LMT	1912 Jan 01  2:00u # Praia
 			-2:00	-	-02	1942 Sep
 			-2:00	1:00	-01	1945 Oct 15
 			-2:00	-	-02	1975 Nov 25  2:00
 			-1:00	-	-01
 # Central African Republic
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Africa/Bangui	1:14:20	-	LMT	1912
 :00	-	WAT
 # Chad
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Ndjamena	1:00:12 -	LMT	1912        # N'Djamena
+Zone	Africa/Ndjamena	1:00:12 -	LMT	1912 Jan  1 # N'Djamena
 :00	-	WAT	1979 Oct 14
 :00	1:00	WAST	1980 Mar  8
 :00	-	WAT
 # Comoros
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Indian/Comoro	2:53:04 -	LMT	1911 Jul # Moroni, Gran Comoro
 :00	-	EAT
 # Democratic Republic of the Congo
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone Africa/Kinshasa	1:01:12 -	LMT	1897 Nov  9
 :00	-	WAT
 @@ -178,27 +182,27 @@ Zone Africa/Lubumbashi	1:49:52 -	LMT	189
 Zone Africa/Brazzaville	1:01:08 -	LMT	1912
 :00	-	WAT
 # Côte d'Ivoire (Ivory Coast)
 # The other parts of the St Helena territory are similar:
 #	Tristan da Cunha: on GMT, say Whitman and the CIA
 #	Ascension: on GMT, say the USNO (1995-12-21) and the CIA
 #	Gough (scientific station since 1955; sealers wintered previously):
 #		on GMT, says the CIA
 #	Inaccessible, Nightingale: uninhabited
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
-Zone	Africa/Abidjan	-0:16:08 -	LMT	1912
+Zone	Africa/Abidjan	-0:16:08 -	LMT	1912 Jan  1
 :00	-	GMT
 # Djibouti
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Africa/Djibouti	2:52:36 -	LMT	1911 Jul
 :00	-	EAT
 ###############################################################################
 # Egypt
 # Milne says Cairo used 2:05:08.9, the local mean time of the Abbasizeh

	@@ -35,20 +35,20 @@ BEGIN {		@@ -35,20 +35,20 @@ BEGIN {
35	zone2 = zonenow[data]	35	zone2 = zonenow[data]
36	if (zone2) {	36	if (zone2) {
37	printf "zones %s and %s identical from now on\n", zone, zone2	37	printf "zones %s and %s identical from now on\n", zone, zone2
38	status = 1	38	status = 1
39	} else	39	} else
40	zonenow[data] = zone	40	zonenow[data] = zone
41	}	41	}
42	}	42	}
43		43
44	END {	44	END {
45	for (zone in zone_data) {	45	for (zone in zone_data) {
46	data = zone_data[zone]	46	data = zone_data[zone]
47	if (!zonenow[data]) {	47	if (!zonenow[data]) {
48	printf "checknow.tab should have one of:%s\n", zones[data]	48	printf "zonenow.tab should have one of:%s\n", zones[data]
49	zonenow[data] = zone # This suppresses duplicate diagnostics.	49	zonenow[data] = zone # This suppresses duplicate diagnostics.
50	status = 1	50	status = 1
51	}	51	}
52	}	52	}
53	exit status	53	exit status
54	}	54	}