diff --git a/contrib/tzdata/Makefile b/contrib/tzdata/Makefile index 88240ad70e0e..b68f843d08ee 100644 --- a/contrib/tzdata/Makefile +++ b/contrib/tzdata/Makefile @@ -1,1224 +1,1225 @@ # Make and install tzdb code and data. # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. # Package name for the code distribution. PACKAGE= tzcode # Version number for the distribution, overridden in the 'tarballs' rule below. VERSION= unknown # Email address for bug reports. BUGEMAIL= tz@iana.org # DATAFORM selects the data format. # Available formats represent essentially the same data, albeit # possibly with minor discrepancies that users are not likely to notice. # To get new features and the best data right away, use: # DATAFORM= vanguard # To wait a while before using new features, to give downstream users # time to upgrade zic (the default), use: # DATAFORM= main # To wait even longer for new features, use: # DATAFORM= rearguard # 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 nonstandard and obsolete # POSIX-like TZ settings like TZ='EET-2EEST' that lack DST transition rules. # Such a setting uses the rules in a template file to determine # "spring forward" and "fall back" days and times; the environment # variable itself specifies UT offsets of standard and daylight saving time. # # 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. # In short, software should avoid ruleless settings like TZ='EET-2EEST' # and so should not depend on the value of POSIXRULES. # # 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 # make zonenames # to get a list of the values you can use for POSIXRULES. POSIXRULES= - # Also see TZDEFRULESTRING below, which takes effect only # if the time zone files cannot be accessed. # Installation locations. # # The defaults are suitable for Debian, except that if REDO is # posix_right or right_posix then files that Debian puts under # /usr/share/zoneinfo/posix and /usr/share/zoneinfo/right are instead # put under /usr/share/zoneinfo-posix and /usr/share/zoneinfo-leaps, # respectively. Problems with the Debian approach are discussed in # the commentary for the right_posix rule (below). # Destination directory, which can be used for staging. # 'make DESTDIR=/stage install' installs under /stage (e.g., to # /stage/etc/localtime instead of to /etc/localtime). Files under # /stage are not intended to work as-is, but can be copied by hand to # the root directory later. If DESTDIR is empty, 'make install' does # not stage, but installs directly into production locations. DESTDIR = # Everything is installed into subdirectories of TOPDIR, and used there. # TOPDIR should be empty (meaning the root directory), # or a directory name that does not end in "/". # TOPDIR should be empty or an absolute name unless you're just testing. TOPDIR = # The default local timezone is taken from the file TZDEFAULT. TZDEFAULT = $(TOPDIR)/etc/localtime # The subdirectory containing installed program and data files, and # likewise for installed files that can be shared among architectures. # These should be relative file names. USRDIR = usr USRSHAREDIR = $(USRDIR)/share # "Compiled" timezone information is placed in the "TZDIR" directory # (and subdirectories). # TZDIR_BASENAME should not contain "/" and should not be ".", ".." or empty. TZDIR_BASENAME= zoneinfo TZDIR = $(TOPDIR)/$(USRSHAREDIR)/$(TZDIR_BASENAME) # The "tzselect" and (if you do "make INSTALL") "date" commands go in: BINDIR = $(TOPDIR)/$(USRDIR)/bin # The "zdump" command goes in: ZDUMPDIR = $(BINDIR) # The "zic" command goes in: ZICDIR = $(TOPDIR)/$(USRDIR)/sbin # Manual pages go in subdirectories of. . . MANDIR = $(TOPDIR)/$(USRSHAREDIR)/man # Library functions are put in an archive in LIBDIR. LIBDIR = $(TOPDIR)/$(USRDIR)/lib # Types to try, as an alternative to time_t. TIME_T_ALTERNATIVES = $(TIME_T_ALTERNATIVES_HEAD) $(TIME_T_ALTERNATIVES_TAIL) TIME_T_ALTERNATIVES_HEAD = int_least64_t TIME_T_ALTERNATIVES_TAIL = int_least32_t uint_least32_t uint_least64_t # What kind of TZif data files to generate. (TZif is the binary time # zone data format that zic generates; see Internet RFC 8536.) # If you want only POSIX time, with time values interpreted as # seconds since the epoch (not counting leap seconds), use # REDO= posix_only # below. If you want only "right" time, with values interpreted # as seconds since the epoch (counting leap seconds), use # REDO= right_only # below. If you want both sets of data available, with leap seconds not # counted normally, use # REDO= posix_right # below. If you want both sets of data available, with leap seconds counted # normally, use # REDO= right_posix # below. POSIX mandates that leap seconds not be counted; for compatibility # with it, use "posix_only" or "posix_right". Use POSIX time on systems with # leap smearing; this can work better than unsmeared "right" time with # applications that are not leap second aware, and is closer to unsmeared # "right" time than unsmeared POSIX time is (e.g., 0.5 vs 1.0 s max error). REDO= posix_right # Whether to put an "Expires" line in the leapseconds file. # Use EXPIRES_LINE=1 to put the line in, 0 to omit it. # The EXPIRES_LINE value matters only if REDO's value contains "right". # If you change EXPIRES_LINE, remove the leapseconds file before running "make". # zic's support for the Expires line was introduced in tzdb 2020a, # and was modified in tzdb 2021b to generate version 4 TZif files. # EXPIRES_LINE defaults to 0 for now so that the leapseconds file # can be given to pre-2020a zic implementations and so that TZif files # built by newer zic implementations can be read by pre-2021b libraries. EXPIRES_LINE= 0 # To install data in text form that has all the information of the TZif data, # (optionally incorporating leap second information), use # TZDATA_TEXT= tzdata.zi leapseconds # To install text data without leap second information (e.g., because # REDO='posix_only'), use # TZDATA_TEXT= tzdata.zi # To avoid installing text data, use # TZDATA_TEXT= TZDATA_TEXT= leapseconds tzdata.zi # For backward-compatibility links for old zone names, use # BACKWARD= backward # To omit these links, use # BACKWARD= BACKWARD= backward # If you want out-of-scope and often-wrong data from the file 'backzone', # but only for entries listed in the backward-compatibility file zone.tab, use # PACKRATDATA= backzone # PACKRATLIST= zone.tab # If you want all the 'backzone' data, use # PACKRATDATA= backzone # PACKRATLIST= # To omit this data, use # PACKRATDATA= # PACKRATLIST= PACKRATDATA= PACKRATLIST= # The name of a locale using the UTF-8 encoding, used during self-tests. # The tests are skipped if the name does not appear to work on this system. UTF8_LOCALE= en_US.utf8 # Non-default libraries needed to link. LDLIBS= # Add the following to the end of the "CFLAGS=" line as needed to override # defaults specified in the source code. "-DFOO" is equivalent to "-DFOO=1". # -DDEPRECATE_TWO_DIGIT_YEARS for optional runtime warnings about strftime # formats that generate only the last two digits of year numbers # -DEPOCH_LOCAL if the 'time' function returns local time not UT # -DEPOCH_OFFSET=N if the 'time' function returns a value N greater # than what POSIX specifies, assuming local time is UT. # For example, N is 252460800 on AmigaOS. # -DHAVE_DECL_ASCTIME_R=0 if does not declare asctime_r # -DHAVE_DECL_ENVIRON if declares 'environ' # -DHAVE_DIRECT_H if mkdir needs (MS-Windows) # -DHAVE_GENERIC=0 if _Generic does not work # -DHAVE_GETTEXT if 'gettext' works (e.g., GNU/Linux, FreeBSD, Solaris) # -DHAVE_INCOMPATIBLE_CTIME_R if your system's time.h declares # ctime_r and asctime_r incompatibly with the POSIX standard # (Solaris when _POSIX_PTHREAD_SEMANTICS is not defined). # -DHAVE_INTTYPES_H if you have a non-C99 compiler with # -DHAVE_LINK=0 if your system lacks a link function # -DHAVE_LOCALTIME_R=0 if your system lacks a localtime_r function # -DHAVE_LOCALTIME_RZ=0 if you do not want zdump to use localtime_rz # localtime_rz can make zdump significantly faster, but is nonstandard. # -DHAVE_MALLOC_ERRNO=0 if malloc etc. do not set errno on failure. # -DHAVE_POSIX_DECLS=0 if your system's include files do not declare # functions like 'link' or variables like 'tzname' required by POSIX # -DHAVE_SNPRINTF=0 if your system lacks the snprintf function # -DHAVE_STDBOOL_H if you have a non-C99 compiler with # -DHAVE_STDINT_H if you have a non-C99 compiler with # -DHAVE_STRFTIME_L if declares locale_t and strftime_l # -DHAVE_STRDUP=0 if your system lacks the strdup function # -DHAVE_STRTOLL=0 if your system lacks the strtoll function # -DHAVE_SYMLINK=0 if your system lacks the symlink function # -DHAVE_SYS_STAT_H=0 if your compiler lacks a # -DHAVE_TZSET=0 if your system lacks a tzset function # -DHAVE_UNISTD_H=0 if your compiler lacks a # -Dlocale_t=XXX if your system uses XXX instead of locale_t # -DRESERVE_STD_EXT_IDS if your platform reserves standard identifiers # with external linkage, e.g., applications cannot define 'localtime'. # -Dssize_t=long on hosts like MS-Windows that lack ssize_t # -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 if the time zone files cannot be accessed # -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 readers that mishandle 64-bit # data in TZif files. Slim TZif files are more efficient and do not # work around these incompatibilities and bugs. If not given, the # default is "slim". # -DZIC_MAX_ABBR_LEN_WO_WARN=3 # (or some other number) to set the maximum time zone abbreviation length # that zic will accept without a warning (the default is 6) # $(GCC_DEBUG_FLAGS) if you are using recent GCC and want lots of checking # Select instrumentation via "make GCC_INSTRUMENT='whatever'". GCC_INSTRUMENT = \ -fsanitize=undefined -fsanitize-address-use-after-scope \ -fsanitize-undefined-trap-on-error -fstack-protector # Omit -fanalyzer from GCC_DEBUG_FLAGS, as it makes GCC too slow. GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common \ $(GCC_INSTRUMENT) \ -Wall -Wextra \ -Walloc-size-larger-than=100000 -Warray-bounds=2 \ -Wbad-function-cast -Wbidi-chars=any,ucn -Wcast-align=strict -Wdate-time \ -Wdeclaration-after-statement -Wdouble-promotion \ -Wduplicated-branches -Wduplicated-cond \ -Wformat=2 -Wformat-overflow=2 -Wformat-signedness -Wformat-truncation \ -Winit-self -Wlogical-op \ -Wmissing-declarations -Wmissing-prototypes -Wnested-externs \ -Wnull-dereference \ -Wold-style-definition -Woverlength-strings -Wpointer-arith \ -Wshadow -Wshift-overflow=2 -Wstrict-overflow \ -Wstrict-prototypes -Wstringop-overflow=4 \ -Wstringop-truncation -Wsuggest-attribute=cold \ -Wsuggest-attribute=const -Wsuggest-attribute=format \ -Wsuggest-attribute=malloc \ -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure \ -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 -Wno-unused-parameter # # 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. These two fields are not -# required by POSIX, but are widely available on GNU/Linux and BSD systems. +# and define NO_TM_ZONE to suppress any guessing. Although these two fields +# not required by POSIX, a future version of POSIX is planned to require 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. # # 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 # # Unix Systems Group code and are required by POSIX 2008 (with XSI) and later. # # 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 # to the end of the "CFLAGS=" line. This arranges for the functions # "offtime", "timelocal", "timegm", "timeoff", # "posix2time", and "time2posix" to be added to the time conversion library. # "offtime" is like "gmtime" except that it accepts a second (long) argument # that gives an offset to add to the time_t when converting it. # "timelocal" is equivalent to "mktime". # "timegm" is like "timelocal" except that it turns a struct tm into # a time_t using UT (rather than local time as "timelocal" does). # "timeoff" is like "timegm" except that it accepts a second (long) argument # that gives an offset to use when converting to a time_t. # "posix2time" and "time2posix" are described in an included manual page. # X3J11's work does not describe any of these functions. # These functions may well disappear in future releases of the time # conversion package. # # If you don't want functions that were inspired by NetBSD, add # -DNETBSD_INSPIRED=0 # to the end of the "CFLAGS=" line. Otherwise, the functions # "localtime_rz", "mktime_z", "tzalloc", and "tzfree" are added to the # time library, and if STD_INSPIRED is also defined the functions # "posix2time_z" and "time2posix_z" are added as well. # The functions ending in "_z" (or "_rz") are like their unsuffixed # (or suffixed-by-"_r") counterparts, except with an extra first # argument of opaque type timezone_t that specifies the timezone. # "tzalloc" allocates a timezone_t value, and "tzfree" frees it. # # If you want to allocate state structures in localtime, add # -DALL_STATE # to the end of the "CFLAGS=" line. Storage is obtained by calling malloc. # # NIST-PCTS:151-2, Version 1.4, (1993-12-03) is a test suite put # out by the National Institute of Standards and Technology # which claims to test C and Posix conformance. If you want to pass PCTS, add # -DPCTS # to the end of the "CFLAGS=" line. # # If you want strict compliance with XPG4 as of 1994-04-09, add # -DXPG4_1994_04_09 # 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. CFLAGS= # Linker flags. Default to $(LFLAGS) for backwards compatibility # to release 2012h and earlier. LDFLAGS= $(LFLAGS) # For leap seconds, this Makefile uses LEAPSECONDS='-L leapseconds' in # submake command lines. The default is no leap seconds. LEAPSECONDS= # 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 older application bugs, append "-b fat"; # see ZIC_BLOAT_DEFAULT above. # See the zic man page for more about -b and -r. ZFLAGS= # How to use zic to install TZif files. ZIC_INSTALL= $(ZIC) -d '$(DESTDIR)$(TZDIR)' $(LEAPSECONDS) # The name of a Posix-compliant 'awk' on your system. # mawk 1.3.3 and Solaris 10 /usr/bin/awk do not work. # 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 , used for HTML validation. CURL= curl # Name of GNU Privacy Guard , 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. # The caller must set the shell variable 'sharp' to the character '#', # since Makefile macros cannot contain '#'. # TAB_CHAR is a single tab character, in single quotes. TAB_CHAR= ' ' SAFE_CHARSET1= $(TAB_CHAR)' !\"'$$sharp'$$%&'\''()*+,./0123456789:;<=>?@' SAFE_CHARSET2= 'ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\^_`' SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' # These characters are Latin-1, and so are likely to be displayable # even in editors with limited character sets. UNUSUAL_OK_LATIN_1 = «°±»½¾× # This IPA symbol is represented in Unicode as the composition of # U+0075 and U+032F, and U+032F is not considered alphabetic by some # grep implementations that do not grok composition. UNUSUAL_OK_IPA = u̯ # Non-ASCII non-letters that OK_CHAR allows, as these characters are # useful in commentary. UNUSUAL_OK_CHARSET= $(UNUSUAL_OK_LATIN_1)$(UNUSUAL_OK_IPA) # Put this in a bracket expression to match spaces. s = [:space:] # OK_CHAR matches any character allowed in the distributed files. # This is the same as SAFE_CHAR, except that UNUSUAL_OK_CHARSET and # multibyte letters are also allowed so that commentary can contain a # few safe symbols and people's names and can quote non-English sources. # Other non-letters are limited to ASCII renderings for the # convenience of maintainers using XEmacs 21.5.34, which by default # mishandles Unicode characters U+0100 and greater. OK_CHAR= '[][:alpha:]$(UNUSUAL_OK_CHARSET)'$(SAFE_CHARSET)'-]' # SAFE_LINE matches a line of safe characters. # SAFE_SHARP_LINE is similar, except any OK character can follow '#'; # this is so that comments can contain non-ASCII characters. # OK_LINE matches a line of OK characters. SAFE_LINE= '^'$(SAFE_CHAR)'*$$' SAFE_SHARP_LINE='^'$(SAFE_CHAR)'*('$$sharp$(OK_CHAR)'*)?$$' OK_LINE= '^'$(OK_CHAR)'*$$' # Flags to give 'tar' when making a distribution. # Try to use flags appropriate for GNU tar. GNUTARFLAGS= --format=pax --pax-option='delete=atime,delete=ctime' \ --numeric-owner --owner=0 --group=0 \ --mode=go+u,go-w --sort=name TARFLAGS= `if tar $(GNUTARFLAGS) --version >/dev/null 2>&1; \ then echo $(GNUTARFLAGS); \ else :; \ fi` # Flags to give 'gzip' when making a distribution. GZIPFLAGS= -9n ############################################################################### #MAKE= make cc= cc CC= $(cc) -DTZDIR='"$(TZDIR)"' AR= ar # ':' on typical hosts; 'ranlib' on the ancient hosts that still need ranlib. RANLIB= : TZCOBJS= zic.o TZDOBJS= zdump.o localtime.o asctime.o strftime.o DATEOBJS= date.o localtime.o strftime.o asctime.o LIBSRCS= localtime.c asctime.c difftime.c strftime.c LIBOBJS= localtime.o asctime.o difftime.o strftime.o HEADERS= tzfile.h private.h NONLIBSRCS= zic.c zdump.c NEWUCBSRCS= date.c SOURCES= $(HEADERS) $(LIBSRCS) $(NONLIBSRCS) $(NEWUCBSRCS) \ tzselect.ksh workman.sh MANS= newctime.3 newstrftime.3 newtzset.3 time2posix.3 \ tzfile.5 tzselect.8 zic.8 zdump.8 MANTXTS= newctime.3.txt newstrftime.3.txt newtzset.3.txt \ time2posix.3.txt \ tzfile.5.txt tzselect.8.txt zic.8.txt zdump.8.txt \ date.1.txt COMMON= calendars CONTRIBUTING LICENSE Makefile \ NEWS README SECURITY theory.html version WEB_PAGES= tz-art.html tz-how-to.html tz-link.html CHECK_WEB_PAGES=check_theory.html check_tz-art.html \ check_tz-how-to.html check_tz-link.html DOCS= $(MANS) date.1 $(MANTXTS) $(WEB_PAGES) PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica YDATA= $(PRIMARY_YDATA) etcetera NDATA= factory TDATA_TO_CHECK= $(YDATA) $(NDATA) backward TDATA= $(YDATA) $(NDATA) $(BACKWARD) ZONETABLES= zone1970.tab zone.tab TABDATA= iso3166.tab $(TZDATA_TEXT) $(ZONETABLES) LEAP_DEPS= leapseconds.awk leap-seconds.list TZDATA_ZI_DEPS= ziguard.awk zishrink.awk version $(TDATA) \ $(PACKRATDATA) $(PACKRATLIST) DSTDATA_ZI_DEPS= ziguard.awk $(TDATA) $(PACKRATDATA) $(PACKRATLIST) DATA= $(TDATA_TO_CHECK) backzone iso3166.tab leap-seconds.list \ leapseconds $(ZONETABLES) AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk \ ziguard.awk zishrink.awk -MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl +MISC= $(AWK_SCRIPTS) TZS_YEAR= 2050 TZS_CUTOFF_FLAG= -c $(TZS_YEAR) TZS= to$(TZS_YEAR).tzs TZS_NEW= to$(TZS_YEAR)new.tzs TZS_DEPS= $(YDATA) asctime.c localtime.c \ private.h tzfile.h zdump.c zic.c TZDATA_DIST = $(COMMON) $(DATA) $(MISC) # EIGHT_YARDS is just a yard short of the whole ENCHILADA. EIGHT_YARDS = $(TZDATA_DIST) $(DOCS) $(SOURCES) tzdata.zi ENCHILADA = $(EIGHT_YARDS) $(TZS) # Consult these files when deciding whether to rebuild the 'version' file. # This list is not the same as the output of 'git ls-files', since # .gitignore is not distributed. VERSION_DEPS= \ calendars CONTRIBUTING LICENSE Makefile NEWS README SECURITY \ africa antarctica asctime.c asia australasia \ backward backzone \ checklinks.awk checktab.awk \ date.1 date.c difftime.c \ etcetera europe factory iso3166.tab \ leap-seconds.list leapseconds.awk localtime.c \ newctime.3 newstrftime.3 newtzset.3 northamerica \ private.h southamerica strftime.c theory.html \ time2posix.3 tz-art.html tz-how-to.html tz-link.html \ tzfile.5 tzfile.h tzselect.8 tzselect.ksh \ workman.sh zdump.8 zdump.c zic.8 zic.c \ ziguard.awk zishrink.awk \ - zone.tab zone1970.tab zoneinfo2tdf.pl + zone.tab zone1970.tab # And for the benefit of csh users on systems that assume the user # shell should be used to handle commands in Makefiles. . . SHELL= /bin/sh all: tzselect zic zdump libtz.a $(TABDATA) \ vanguard.zi main.zi rearguard.zi ALL: all date $(ENCHILADA) install: all $(DATA) $(REDO) $(MANS) mkdir -p '$(DESTDIR)$(BINDIR)' \ '$(DESTDIR)$(ZDUMPDIR)' '$(DESTDIR)$(ZICDIR)' \ '$(DESTDIR)$(LIBDIR)' \ '$(DESTDIR)$(MANDIR)/man3' '$(DESTDIR)$(MANDIR)/man5' \ '$(DESTDIR)$(MANDIR)/man8' $(ZIC_INSTALL) -l $(LOCALTIME) \ `case '$(POSIXRULES)' in ?*) echo '-p';; esac \ ` $(POSIXRULES) \ -t '$(DESTDIR)$(TZDEFAULT)' cp -f $(TABDATA) '$(DESTDIR)$(TZDIR)/.' cp tzselect '$(DESTDIR)$(BINDIR)/.' cp zdump '$(DESTDIR)$(ZDUMPDIR)/.' cp zic '$(DESTDIR)$(ZICDIR)/.' cp libtz.a '$(DESTDIR)$(LIBDIR)/.' $(RANLIB) '$(DESTDIR)$(LIBDIR)/libtz.a' cp -f newctime.3 newtzset.3 '$(DESTDIR)$(MANDIR)/man3/.' cp -f tzfile.5 '$(DESTDIR)$(MANDIR)/man5/.' cp -f tzselect.8 zdump.8 zic.8 '$(DESTDIR)$(MANDIR)/man8/.' INSTALL: ALL install date.1 mkdir -p '$(DESTDIR)$(BINDIR)' '$(DESTDIR)$(MANDIR)/man1' cp date '$(DESTDIR)$(BINDIR)/.' cp -f date.1 '$(DESTDIR)$(MANDIR)/man1/.' # Calculate version number from git, if available. # Otherwise, use $(VERSION) unless it is "unknown" and there is already # a 'version' file, in which case reuse the existing 'version' contents # and append "-dirty" if the contents do not already end in "-dirty". version: $(VERSION_DEPS) { (type git) >/dev/null 2>&1 && \ V=`git describe --match '[0-9][0-9][0-9][0-9][a-z]*' \ --abbrev=7 --dirty` || \ if test '$(VERSION)' = unknown && V=`cat $@`; then \ case $$V in *-dirty);; *) V=$$V-dirty;; esac; \ else \ V='$(VERSION)'; \ fi; } && \ printf '%s\n' "$$V" >$@.out mv $@.out $@ # These files can be tailored by setting BACKWARD, PACKRATDATA, PACKRATLIST. vanguard.zi main.zi rearguard.zi: $(DSTDATA_ZI_DEPS) $(AWK) \ -v DATAFORM=`expr $@ : '\(.*\).zi'` \ -v PACKRATDATA='$(PACKRATDATA)' \ -v PACKRATLIST='$(PACKRATLIST)' \ -f ziguard.awk \ $(TDATA) $(PACKRATDATA) >$@.out mv $@.out $@ # This file has a version comment that attempts to capture any tailoring # via BACKWARD, DATAFORM, PACKRATDATA, PACKRATLIST, and REDO. tzdata.zi: $(DATAFORM).zi version zishrink.awk version=`sed 1q version` && \ LC_ALL=C $(AWK) \ -v dataform='$(DATAFORM)' \ -v deps='$(DSTDATA_ZI_DEPS) zishrink.awk' \ -v redo='$(REDO)' \ -v version="$$version" \ -f zishrink.awk \ $(DATAFORM).zi >$@.out mv $@.out $@ version.h: version VERSION=`cat version` && printf '%s\n' \ 'static char const PKGVERSION[]="($(PACKAGE)) ";' \ "static char const TZVERSION[]=\"$$VERSION\";" \ 'static char const REPORT_BUGS_TO[]="$(BUGEMAIL)";' \ >$@.out 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 $@ # 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 # 'make install_data' installs one set of TZif files. install_data: $(INSTALL_DATA_DEPS) $(ZIC_INSTALL) tzdata.zi posix_only: $(INSTALL_DATA_DEPS) $(MAKE) $(INSTALLARGS) LEAPSECONDS= install_data right_only: $(INSTALL_DATA_DEPS) $(MAKE) $(INSTALLARGS) LEAPSECONDS='-L leapseconds' \ install_data # In earlier versions of this makefile, the other two directories were # subdirectories of $(TZDIR). However, this led to configuration errors. # For example, with posix_right under the earlier scheme, # TZ='right/Australia/Adelaide' got you localtime with leap seconds, # but gmtime without leap seconds, which led to problems with applications # like sendmail that subtract gmtime from localtime. # Therefore, the other two directories are now siblings of $(TZDIR). # You must replace all of $(TZDIR) to switch from not using leap seconds # to using them, or vice versa. right_posix: right_only rm -fr '$(DESTDIR)$(TZDIR)-leaps' ln -s '$(TZDIR_BASENAME)' '$(DESTDIR)$(TZDIR)-leaps' || \ $(MAKE) $(INSTALLARGS) TZDIR='$(TZDIR)-leaps' right_only $(MAKE) $(INSTALLARGS) TZDIR='$(TZDIR)-posix' posix_only posix_right: posix_only rm -fr '$(DESTDIR)$(TZDIR)-posix' ln -s '$(TZDIR_BASENAME)' '$(DESTDIR)$(TZDIR)-posix' || \ $(MAKE) $(INSTALLARGS) TZDIR='$(TZDIR)-posix' posix_only $(MAKE) $(INSTALLARGS) TZDIR='$(TZDIR)-leaps' right_only zones: $(REDO) # dummy.zd is not a real file; it is mentioned here only so that the # top-level 'make' does not have a syntax error. ZDS = dummy.zd # Rule used only by submakes invoked by the $(TZS_NEW) rule. # It is separate so that GNU 'make -j' can run instances in parallel. $(ZDS): zdump ./zdump -i $(TZS_CUTOFF_FLAG) '$(wd)/'$$(expr $@ : '\(.*\).zd') \ >$@ TZS_NEW_DEPS = tzdata.zi zdump zic $(TZS_NEW): $(TZS_NEW_DEPS) rm -fr tzs$(TZS_YEAR).dir mkdir tzs$(TZS_YEAR).dir $(zic) -d tzs$(TZS_YEAR).dir tzdata.zi $(AWK) '/^L/{print "Link\t" $$2 "\t" $$3}' \ tzdata.zi | LC_ALL=C sort >$@.out wd=`pwd` && \ x=`$(AWK) '/^Z/{print "tzs$(TZS_YEAR).dir/" $$2 ".zd"}' \ tzdata.zi \ | LC_ALL=C sort -t . -k 2,2` && \ set x $$x && \ shift && \ ZDS=$$* && \ $(MAKE) wd="$$wd" TZS_CUTOFF_FLAG="$(TZS_CUTOFF_FLAG)" \ ZDS="$$ZDS" $$ZDS && \ sed 's,^TZ=".*\.dir/,TZ=",' $$ZDS >>$@.out rm -fr tzs$(TZS_YEAR).dir mv $@.out $@ # If $(TZS) exists but 'make check_tzs' fails, a maintainer should inspect the # failed output and fix the inconsistency, perhaps by running 'make force_tzs'. $(TZS): touch $@ force_tzs: $(TZS_NEW) cp $(TZS_NEW) $(TZS) libtz.a: $(LIBOBJS) rm -f $@ $(AR) -rc $@ $(LIBOBJS) $(RANLIB) $@ date: $(DATEOBJS) $(CC) -o $@ $(CFLAGS) $(LDFLAGS) $(DATEOBJS) $(LDLIBS) tzselect: tzselect.ksh version VERSION=`cat version` && sed \ -e 's|#!/bin/bash|#!$(KSHELL)|g' \ -e 's|AWK=[^}]*|AWK='\''$(AWK)'\''|g' \ -e 's|\(PKGVERSION\)=.*|\1='\''($(PACKAGE)) '\''|' \ -e 's|\(REPORT_BUGS_TO\)=.*|\1=$(BUGEMAIL)|' \ -e 's|TZDIR=[^}]*|TZDIR=$(TZDIR)|' \ -e 's|\(TZVERSION\)=.*|\1='"$$VERSION"'|' \ <$@.ksh >$@.out chmod +x $@.out mv $@.out $@ check: check_character_set check_white_space check_links \ check_name_lengths check_slashed_abbrs check_sorted \ check_tables check_web check_ziguard check_zishrink check_tzs check_character_set: $(ENCHILADA) test ! '$(UTF8_LOCALE)' || \ ! printf 'A\304\200B\n' | \ LC_ALL='$(UTF8_LOCALE)' grep -q '^A.B$$' >/dev/null 2>&1 || { \ LC_ALL='$(UTF8_LOCALE)' && export LC_ALL && \ sharp='#' && \ ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) \ CONTRIBUTING LICENSE README SECURITY \ version tzdata.zi && \ ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_'$(OK_CHAR)'*$$' \ Makefile && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA_TO_CHECK) backzone \ leapseconds zone.tab && \ ! grep -Env $(OK_LINE) $(ENCHILADA); \ } touch $@ check_white_space: $(ENCHILADA) patfmt=' \t|[\f\r\v]' && pat=`printf "$$patfmt\\n"` && \ ! grep -En "$$pat" \ $$(ls $(ENCHILADA) | grep -Fvx leap-seconds.list) ! grep -n '[$s]$$' \ $$(ls $(ENCHILADA) | grep -Fvx leap-seconds.list) touch $@ PRECEDES_FILE_NAME = ^(Zone|Link[$s]+[^$s]+)[$s]+ FILE_NAME_COMPONENT_TOO_LONG = $(PRECEDES_FILE_NAME)[^$s]*[^/$s]{15} check_name_lengths: $(TDATA_TO_CHECK) backzone ! grep -En '$(FILE_NAME_COMPONENT_TOO_LONG)' \ $(TDATA_TO_CHECK) backzone touch $@ PRECEDES_STDOFF = ^(Zone[$s]+[^$s]+)?[$s]+ STDOFF = [-+]?[0-9:.]+ RULELESS_SAVE = (-|$(STDOFF)[sd]?) RULELESS_SLASHED_ABBRS = \ $(PRECEDES_STDOFF)$(STDOFF)[$s]+$(RULELESS_SAVE)[$s]+[^$s]*/ check_slashed_abbrs: $(TDATA_TO_CHECK) ! grep -En '$(RULELESS_SLASHED_ABBRS)' $(TDATA_TO_CHECK) touch $@ CHECK_CC_LIST = { n = split($$1,a,/,/); for (i=2; i<=n; i++) print a[1], a[i]; } check_sorted: backward backzone iso3166.tab zone.tab zone1970.tab $(AWK) '/^Link/ {print $$3}' backward | LC_ALL=C sort -cu $(AWK) '/^Zone/ {print $$2}' backzone | LC_ALL=C sort -cu touch $@ check_links: checklinks.awk $(TDATA_TO_CHECK) tzdata.zi $(AWK) -f checklinks.awk $(TDATA_TO_CHECK) $(AWK) -f checklinks.awk tzdata.zi touch $@ check_tables: checktab.awk $(YDATA) backward $(ZONETABLES) for tab in $(ZONETABLES); do \ test "$$tab" = zone.tab && links='$(BACKWARD)' || links=''; \ $(AWK) -f checktab.awk -v zone_table=$$tab $(YDATA) $$links \ || exit; \ done touch $@ check_tzs: $(TZS) $(TZS_NEW) if test -s $(TZS); then \ diff -u $(TZS) $(TZS_NEW); \ else \ cp $(TZS_NEW) $(TZS); \ fi touch $@ check_web: $(CHECK_WEB_PAGES) check_theory.html: theory.html check_tz-art.html: tz-art.html check_tz-how-to.html: tz-how-to.html check_tz-link.html: tz-link.html check_theory.html check_tz-art.html check_tz-how-to.html check_tz-link.html: $(CURL) -sS --url https://validator.w3.org/nu/ -F out=gnu \ -F file=@$$(expr $@ : 'check_\(.*\)') -o $@.out && \ test ! -s $@.out || { cat $@.out; exit 1; } mv $@.out $@ check_ziguard: rearguard.zi vanguard.zi ziguard.awk $(AWK) -v DATAFORM=rearguard -f ziguard.awk vanguard.zi | \ diff -u rearguard.zi - $(AWK) -v DATAFORM=vanguard -f ziguard.awk rearguard.zi | \ diff -u vanguard.zi - touch $@ # Check that zishrink.awk does not alter the data, and that ziguard.awk # preserves main-format data. check_zishrink: check_zishrink_posix check_zishrink_right check_zishrink_posix check_zishrink_right: \ zic leapseconds $(PACKRATDATA) $(PACKRATLIST) \ $(TDATA) $(DATAFORM).zi tzdata.zi rm -fr $@.dir $@-t.dir $@-shrunk.dir mkdir $@.dir $@-t.dir $@-shrunk.dir case $@ in \ *_right) leap='-L leapseconds';; \ *) leap=;; \ esac && \ $(ZIC) $$leap -d $@.dir $(DATAFORM).zi && \ $(ZIC) $$leap -d $@-shrunk.dir tzdata.zi && \ case $(DATAFORM),$(PACKRATLIST) in \ main,) \ $(ZIC) $$leap -d $@-t.dir $(TDATA) && \ $(AWK) '/^Rule/' $(TDATA) | \ $(ZIC) $$leap -d $@-t.dir - $(PACKRATDATA) && \ diff -r $@.dir $@-t.dir;; \ esac diff -r $@.dir $@-shrunk.dir rm -fr $@.dir $@-t.dir $@-shrunk.dir touch $@ clean_misc: rm -fr check_*.dir rm -f *.o *.out $(TIME_T_ALTERNATIVES) \ check_* core typecheck_* \ date tzselect version.h zdump zic libtz.a clean: clean_misc rm -fr *.dir tzdb-*/ rm -f *.zi $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' @echo 'deletes files that may need special tools to rebuild.' rm -f leapseconds version $(MANTXTS) $(TZS) *.asc *.tar.* names: @echo $(ENCHILADA) public: check check_public $(CHECK_TIME_T_ALTERNATIVES) \ tarballs signatures date.1.txt: date.1 newctime.3.txt: newctime.3 newstrftime.3.txt: newstrftime.3 newtzset.3.txt: newtzset.3 time2posix.3.txt: time2posix.3 tzfile.5.txt: tzfile.5 tzselect.8.txt: tzselect.8 zdump.8.txt: zdump.8 zic.8.txt: zic.8 $(MANTXTS): workman.sh LC_ALL=C sh workman.sh `expr $@ : '\(.*\)\.txt$$'` >$@.out mv $@.out $@ # Set file timestamps deterministically if possible, # so that tarballs containing the timestamps are reproducible. # # '$(SET_TIMESTAMP_N) N DEST A B C ...' sets the timestamp of the # file DEST to the maximum of the timestamps of the files A B C ..., # plus N if GNU ls and touch are available. SET_TIMESTAMP_N = sh -c '\ n=$$0 dest=$$1; shift; \ touch -cmr `ls -t "$$@" | sed 1q` "$$dest" && \ if test $$n != 0 && \ lsout=`ls -n --time-style="+%s" "$$dest" 2>/dev/null`; then \ set x $$lsout && \ touch -cmd @`expr $$7 + $$n` "$$dest"; \ else :; fi' # If DEST depends on A B C ... in this Makefile, callers should use # $(SET_TIMESTAMP_DEP) DEST A B C ..., for the benefit of any # downstream 'make' that considers equal timestamps to be out of date. # POSIX allows this 'make' behavior, and HP-UX 'make' does it. # If all that matters is that the timestamp be reproducible # and plausible, use $(SET_TIMESTAMP). SET_TIMESTAMP = $(SET_TIMESTAMP_N) 0 SET_TIMESTAMP_DEP = $(SET_TIMESTAMP_N) 1 # Set the timestamps to those of the git repository, if available, # and if the files have not changed since then. # This uses GNU 'ls --time-style=+%s', which outputs the seconds count, # and GNU 'touch -d@N FILE', where N is the number of seconds since 1970. # If git or GNU is absent, don't bother to sync with git timestamps. # Also, set the timestamp of each prebuilt file like 'leapseconds' # to be the maximum of the files it depends on. set-timestamps.out: $(EIGHT_YARDS) rm -f $@ if (type git) >/dev/null 2>&1 && \ files=`git ls-files $(EIGHT_YARDS)` && \ touch -md @1 test.out; then \ rm -f test.out && \ for file in $$files; do \ if git diff --quiet $$file; then \ time=`git log -1 --format='tformat:%ct' $$file` && \ touch -cmd @$$time $$file; \ else \ echo >&2 "$$file: warning: does not match repository"; \ fi || exit; \ done; \ fi $(SET_TIMESTAMP_DEP) leapseconds $(LEAP_DEPS) for file in `ls $(MANTXTS) | sed 's/\.txt$$//'`; do \ $(SET_TIMESTAMP_DEP) $$file.txt $$file workman.sh || \ exit; \ done $(SET_TIMESTAMP_DEP) version $(VERSION_DEPS) $(SET_TIMESTAMP_DEP) tzdata.zi $(TZDATA_ZI_DEPS) touch $@ set-tzs-timestamp.out: $(TZS) $(SET_TIMESTAMP_DEP) $(TZS) $(TZS_DEPS) touch $@ # The zics below ensure that each data file can stand on its own. # We also do an all-files run to catch links to links. check_public: $(VERSION_DEPS) rm -fr public.dir mkdir public.dir ln $(VERSION_DEPS) public.dir cd public.dir && $(MAKE) CFLAGS='$(GCC_DEBUG_FLAGS)' ALL for i in $(TDATA_TO_CHECK) public.dir/tzdata.zi \ public.dir/vanguard.zi public.dir/main.zi \ public.dir/rearguard.zi; \ do \ public.dir/zic -v -d public.dir/zoneinfo $$i 2>&1 || exit; \ done public.dir/zic -v -d public.dir/zoneinfo-all $(TDATA_TO_CHECK) : : Also check 'backzone' syntax. rm public.dir/main.zi cd public.dir && $(MAKE) PACKRATDATA=backzone main.zi public.dir/zic -d public.dir/zoneinfo main.zi rm public.dir/main.zi cd public.dir && \ $(MAKE) PACKRATDATA=backzone PACKRATLIST=zone.tab main.zi public.dir/zic -d public.dir/zoneinfo main.zi : rm -fr public.dir touch $@ # Check that the code works under various alternative # implementations of time_t. check_time_t_alternatives: $(TIME_T_ALTERNATIVES) $(TIME_T_ALTERNATIVES_TAIL): $(TIME_T_ALTERNATIVES_HEAD) $(TIME_T_ALTERNATIVES): $(VERSION_DEPS) rm -fr $@.dir mkdir $@.dir ln $(VERSION_DEPS) $@.dir case $@ in \ int*32_t) range=-2147483648,2147483648;; \ u*) range=0,4294967296;; \ *) range=-4294967296,4294967296;; \ esac && \ wd=`pwd` && \ zones=`$(AWK) '/^[^#]/ { print $$3 }' /dev/null; then \ quiet_option='-q'; \ else \ quiet_option=''; \ fi && \ diff $$quiet_option -r $(TIME_T_ALTERNATIVES_HEAD).dir/etc \ $@.dir/etc && \ diff $$quiet_option -r \ $(TIME_T_ALTERNATIVES_HEAD).dir/usr/share \ $@.dir/usr/share; \ } touch $@ TRADITIONAL_ASC = \ tzcode$(VERSION).tar.gz.asc \ tzdata$(VERSION).tar.gz.asc REARGUARD_ASC = \ tzdata$(VERSION)-rearguard.tar.gz.asc ALL_ASC = $(TRADITIONAL_ASC) $(REARGUARD_ASC) \ tzdb-$(VERSION).tar.lz.asc tarballs rearguard_tarballs tailored_tarballs traditional_tarballs \ signatures rearguard_signatures traditional_signatures: \ version set-timestamps.out rearguard.zi vanguard.zi VERSION=`cat version` && \ $(MAKE) AWK='$(AWK)' VERSION="$$VERSION" $@_version # These *_version rules are intended for use if VERSION is set by some # other means. Ordinarily these rules are used only by the above # non-_version rules, which set VERSION on the 'make' command line. tarballs_version: traditional_tarballs_version rearguard_tarballs_version \ tzdb-$(VERSION).tar.lz rearguard_tarballs_version: \ tzdata$(VERSION)-rearguard.tar.gz traditional_tarballs_version: \ tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz tailored_tarballs_version: \ tzdata$(VERSION)-tailored.tar.gz signatures_version: $(ALL_ASC) rearguard_signatures_version: $(REARGUARD_ASC) traditional_signatures_version: $(TRADITIONAL_ASC) tzcode$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - \ $(COMMON) $(DOCS) $(SOURCES) | \ gzip $(GZIPFLAGS) >$@.out mv $@.out $@ tzdata$(VERSION).tar.gz: set-timestamps.out LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - $(TZDATA_DIST) | \ gzip $(GZIPFLAGS) >$@.out mv $@.out $@ # Create empty files with a reproducible timestamp. CREATE_EMPTY = TZ=UTC0 touch -mt 202010122253.00 # The obsolescent *rearguard* targets and related macros are present # for backwards compatibility with tz releases 2018e through 2022a. # They should go away eventually. To build rearguard tarballs you # can instead use 'make DATAFORM=rearguard tailored_tarballs'. tzdata$(VERSION)-rearguard.tar.gz: rearguard.zi set-timestamps.out rm -fr $@.dir mkdir $@.dir ln $(TZDATA_DIST) $@.dir cd $@.dir && rm -f $(TDATA) $(PACKRATDATA) version for f in $(TDATA) $(PACKRATDATA); do \ rearf=$@.dir/$$f; \ $(AWK) -v DATAFORM=rearguard -f ziguard.awk $$f >$$rearf && \ $(SET_TIMESTAMP_DEP) $$rearf ziguard.awk $$f || exit; \ done sed '1s/$$/-rearguard/' $@.dir/version : The dummy pacificnew pacifies TZUpdater 2.3.1 and earlier. $(CREATE_EMPTY) $@.dir/pacificnew touch -cmr version $@.dir/version LC_ALL=C && export LC_ALL && \ (cd $@.dir && \ tar $(TARFLAGS) -cf - \ $(TZDATA_DIST) pacificnew | \ gzip $(GZIPFLAGS)) >$@.out mv $@.out $@ # Create a tailored tarball suitable for TZUpdater and compatible tools. # For example, 'make DATAFORM=vanguard tailored_tarballs' makes a tarball # useful for testing whether TZUpdater supports vanguard form. # The generated tarball is not byte-for-byte equivalent to a hand-tailored # traditional tarball, as data entries are put into 'etcetera' even if they # came from some other source file. However, the effect should be the same # for ordinary use, which reads all the source files. tzdata$(VERSION)-tailored.tar.gz: set-timestamps.out rm -fr $@.dir mkdir $@.dir : The dummy pacificnew pacifies TZUpdater 2.3.1 and earlier. cd $@.dir && \ $(CREATE_EMPTY) $(PRIMARY_YDATA) $(NDATA) backward \ `test $(DATAFORM) = vanguard || echo pacificnew` (grep '^#' tzdata.zi && echo && cat $(DATAFORM).zi) \ >$@.dir/etcetera touch -cmr tzdata.zi $@.dir/etcetera sed -n \ -e '/^# *version *\(.*\)/h' \ -e '/^# *ddeps */H' \ -e '$$!d' \ -e 'g' \ -e 's/^# *version *//' \ -e 's/\n# *ddeps */-/' \ -e 's/ /-/g' \ -e 'p' \ $@.dir/version touch -cmr version $@.dir/version links= && \ for file in $(TZDATA_DIST); do \ test -f $@.dir/$$file || links="$$links $$file"; \ done && \ ln $$links $@.dir LC_ALL=C && export LC_ALL && \ (cd $@.dir && \ tar $(TARFLAGS) -cf - * | gzip $(GZIPFLAGS)) >$@.out mv $@.out $@ tzdb-$(VERSION).tar.lz: set-timestamps.out set-tzs-timestamp.out rm -fr tzdb-$(VERSION) mkdir tzdb-$(VERSION) ln $(ENCHILADA) tzdb-$(VERSION) $(SET_TIMESTAMP) tzdb-$(VERSION) tzdb-$(VERSION)/* LC_ALL=C && export LC_ALL && \ tar $(TARFLAGS) -cf - tzdb-$(VERSION) | lzip -9 >$@.out mv $@.out $@ tzcode$(VERSION).tar.gz.asc: tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz.asc: tzdata$(VERSION).tar.gz tzdata$(VERSION)-rearguard.tar.gz.asc: tzdata$(VERSION)-rearguard.tar.gz tzdb-$(VERSION).tar.lz.asc: tzdb-$(VERSION).tar.lz $(ALL_ASC): $(GPG) --armor --detach-sign $? TYPECHECK_CFLAGS = $(CFLAGS) -DTYPECHECK -D__time_t_defined -D_TIME_T typecheck: typecheck_long_long typecheck_unsigned typecheck_long_long typecheck_unsigned: $(VERSION_DEPS) rm -fr $@.dir mkdir $@.dir ln $(VERSION_DEPS) $@.dir cd $@.dir && \ case $@ in \ *_long_long) i="long long";; \ *_unsigned ) i="unsigned" ;; \ esac && \ typecheck_cflags='' && \ $(MAKE) \ CFLAGS="$(TYPECHECK_CFLAGS) \"-Dtime_t=$$i\"" \ TOPDIR="`pwd`" \ install $@.dir/zdump -i -c 1970,1971 Europe/Rome touch $@ 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 strftime.o: private.h tzfile.h zdump.o: version.h zic.o: private.h tzfile.h version.h .PHONY: ALL INSTALL all .PHONY: check check_time_t_alternatives .PHONY: check_web check_zishrink .PHONY: clean clean_misc dummy.zd 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) diff --git a/contrib/tzdata/NEWS b/contrib/tzdata/NEWS index 6a0d5c502727..c4abb32cd4dc 100644 --- a/contrib/tzdata/NEWS +++ b/contrib/tzdata/NEWS @@ -1,5647 +1,5671 @@ News for the tz database +Release 2022c - 2022-08-15 17:47:18 -0700 + + Briefly: + Work around awk bug in FreeBSD, macOS, etc. + Improve tzselect on intercontinental Zones. + + Changes to code + + Work around a bug in onetrueawk that broke commands like + 'make traditional_tarballs' on FreeBSD, macOS, etc. + (Problem reported by Deborah Goldsmith.) + + Add code to tzselect that uses experimental structured comments in + zone1970.tab to clarify whether Zones like Africa/Abidjan and + Europe/Istanbul cross continent or ocean boundaries. + (Inspired by a problem reported by Peter Krefting.) + + Fix bug with 'zic -d /a/b/c' when /a is unwritable but the + directory /a/b already exists. + + Remove zoneinfo2tdf.pl, as it was unused and triggered false + malware alarms on some email servers. + + Release 2022b - 2022-08-10 15:38:32 -0700 Briefly: Chile's DST is delayed by a week in September 2022. Iran no longer observes DST after 2022. Rename Europe/Kiev to Europe/Kyiv. New zic -R option Vanguard form now uses %z. Finish moving duplicate-since-1970 zones to 'backzone'. New build option PACKRATLIST New tailored_tarballs target, replacing rearguard_tarballs Changes to future timestamps Chile's 2022 DST start is delayed from September 4 to September 11. (Thanks to Juan Correa.) Iran plans to stop observing DST permanently, after it falls back on 2022-09-21. (Thanks to Ali Mirjamali.) Changes to past timestamps Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap. From fall 1994 through fall 1995, Shanks wrote that Crimea's DST transitions were at 02:00 standard time, not at 00:00. (Thanks to Michael Deckers.) Iran adopted standard time in 1935, not 1946. In 1977 it observed DST from 03-21 23:00 to 10-20 24:00; its 1978 transitions were on 03-24 and 08-05, not 03-20 and 10-20; and its spring 1979 transition was on 05-27, not 03-21. (Thanks to Roozbeh Pournader and Francis Santoni.) Chile's observance of -04 from 1946-08-29 through 1947-03-31 was considered DST, not standard time. Santiago and environs had moved their clocks back to rejoin the rest of mainland Chile; put this change at the end of 1946-08-28. (Thanks to Michael Deckers.) Some old, small clock transitions have been removed, as people at the time did not change their clocks. This affects Asia/Hong_Kong in 1904, Asia/Ho_Chi_Minh in 1906, and Europe/Dublin in 1880. Changes to zone name Rename Europe/Kiev to Europe/Kyiv, as "Kyiv" is more common in English now. Spelling of other names in Ukraine has not yet demonstrably changed in common English practice so for now these names retain old spellings, as in other countries (e.g., Europe/Prague not "Praha", and Europe/Sofia not "Sofiya"). Changes to code zic has a new option '-R @N' to output explicit transitions < N. (Need suggested by Almaz Mingaleev.) 'zic -r @N' no longer outputs bad data when N < first transition. (Problem introduced in 2021d and reported by Peter Krefting.) zic now checks its input for NUL bytes and unterminated lines, and now supports input line lengths up to 2048 (not 512) bytes. gmtime and related code now use the abbreviation "UTC" not "GMT". POSIX is being revised to require this. When tzset and related functions set vestigial static variables like tzname, they now prefer specified timestamps to unspecified ones. (Problem reported by Almaz Mingaleev.) zic no longer complains "can't determine time zone abbreviation to use just after until time" when a transition to a new standard - time occurs simultanously with the first DST fallback transition. + time occurs simultaneously with the first DST fallback transition. Changes to build procedure Source data in vanguard form now uses the %z notation, introduced in release 2015f. For example, for America/Sao_Paulo vanguard form contains the zone continuation line "-3:00 Brazil %z", which is simpler and more reliable than the line "-3:00 Brazil -03/-02" used in main and rearguard forms. The plan is for the main form to use %z eventually; in the meantime maintainers of zi parsers are encouraged to test the parsers on vanguard.zi. The Makefile has a new PACKRATLIST option to select a subset of 'backzone'. For example, 'make PACKRATDATA=backzone PACKRATLIST=zone.tab' now generates TZif files identical to those of the global-tz project. The Makefile has a new tailored_tarballs target for generating special-purpose tarballs. It generalizes and replaces the rearguard_tarballs target and related targets and macros, which are now obsolescent. 'make install' now defaults LOCALTIME to Factory not GMT, which means the default abbreviation is now "-00" not "GMT". Remove the posix_packrat target, marked obsolescent in 2016a. Release 2022a - 2022-03-15 23:02:01 -0700 Briefly: Palestine will spring forward on 2022-03-27, not -03-26. zdump -v now outputs better failure indications. Bug fixes for code that reads corrupted TZif data. Changes to future timestamps Palestine will spring forward on 2022-03-27, not 2022-03-26. (Thanks to Heba Hamad.) Predict future transitions for first Sunday >= March 25. Additionally, predict fallbacks to be the first Friday on or after October 23, not October's last Friday, to be more consistent with recent practice. The first differing fallback prediction is on 2025-10-24, not 2025-10-31. Changes to past timestamps From 1992 through spring 1996, Ukraine's DST transitions were at 02:00 standard time, not at 01:00 UTC. (Thanks to Alois Treindl.) Chile's Santiago Mean Time and its LMT precursor have been adjusted eastward by 1 second to align with past and present law. Changes to commentary Add several references for Chile's 1946/1947 transitions, some of which only affected portions of the country. Changes to code Fix bug when mktime gets confused by truncated TZif files with unspecified local time. (Problem reported by Almaz Mingaleev.) Fix bug when 32-bit time_t code reads malformed 64-bit TZif data. (Problem reported by Christos Zoulas.) When reading a version 2 or later TZif file, the TZif reader now validates the version 1 header and data block only enough to skip over them, as recommended by RFC 8536 section 4. Also, the TZif reader no longer mistakenly attempts to parse a version 1 TZIf file header as a TZ string. zdump -v now outputs "(localtime failed)" and "(gmtime failed)" when local time and UT cannot be determined for a timestamp. Changes to build procedure Distribution tarballs now use standard POSIX.1-1988 ustar format instead of GNU format. Although the formats are almost identical for these tarballs, ustar headers' magic fields contain "ustar" instead of "ustar ", and their version fields contain "00" instead of " ". The two formats are planned to diverge more significantly for tzdb releases after 2242-03-16 12:56:31 UTC, when the ustar format becomes obsolete and the tarballs switch to pax format, an extension of ustar. For details about these formats, please see "pax - portable archive interchange", IEEE Std 1003.1-2017, . Release 2021e - 2021-10-21 18:41:00 -0700 Changes to future timestamps Palestine will fall back 10-29 (not 10-30) at 01:00. (Thanks to P Chan and Heba Hemad.) Release 2021d - 2021-10-15 13:48:18 -0700 Briefly: Fiji suspends DST for the 2021/2022 season. 'zic -r' marks unspecified timestamps with "-00". Changes to future timestamps Fiji will suspend observance of DST for the 2021/2022 season. Assume for now that it will return next year. (Thanks to Jashneel Kumar and P Chan.) Changes to code 'zic -r' now uses "-00" time zone abbreviations for intervals with UT offsets that are unspecified due to -r truncation. This implements a change in draft Internet RFC 8536bis. Release 2021c - 2021-10-01 14:21:49 -0700 Briefly: Revert most 2021b changes to 'backward'. Fix 'zic -b fat' bug in pre-1970 32-bit data. Fix two Link line typos. Distribute SECURITY file. This release is intended as a bugfix release, to fix compatibility problems and typos reported since 2021b was released. Changes to Link directives Revert almost all of 2021b's changes to the 'backward' file, by moving Link directives back to where they were in 2021a. Although 'zic' doesn't care which source file contains a Link directive, some downstream uses ran into trouble with the move. (Problem reported by Stephen Colebourne for Joda-Time.) Fix typo that linked Atlantic/Jan_Mayen to the wrong location (problem reported by Chris Walton). Fix 'backzone' typo that linked America/Virgin to the wrong location (problem reported by Michael Deckers). Changes to code Fix a bug in 'zic -b fat' that caused old timestamps to be mishandled in 32-bit-only readers (problem reported by Daniel Fischer). Changes to documentation Distribute the SECURITY file (problem reported by Andreas Radke). Release 2021b - 2021-09-24 16:23:00 -0700 Briefly: Jordan now starts DST on February's last Thursday. Samoa no longer observes DST. Merge more location-based Zones whose timestamps agree since 1970. Move some backward-compatibility links to 'backward'. Rename Pacific/Enderbury to Pacific/Kanton. Correct many pre-1993 transitions in Malawi, Portugal, etc. zic now creates each output file or link atomically. zic -L no longer omits the POSIX TZ string in its output. zic fixes for truncation and leap second table expiration. zic now follows POSIX for TZ strings using all-year DST. Fix some localtime crashes and bugs in obscure cases. zdump -v now outputs more-useful boundary cases. tzfile.5 better matches a draft successor to RFC 8536. A new file SECURITY. This release is prompted by recent announcements by Jordan and Samoa. It incorporates many other changes that had accumulated since 2021a. However, it omits most proposed changes that merged all Zones agreeing since 1970, as concerns were raised about doing too many of these changes at once. It does keeps some of these changes in the interest of making tzdb more equitable one step at a time; see "Merge more location-based Zones" below. Changes to future timestamps Jordan now starts DST on February's last Thursday. (Thanks to Steffen Thorsen.) Samoa no longer observes DST. (Thanks to Geoffrey D. Bennett.) Changes to zone name Rename Pacific/Enderbury to Pacific/Kanton. When we added Enderbury in 1993, we did not know that it is uninhabited and that Kanton (population two dozen) is the only inhabited location in that timezone. The old name is now a backward-compatibility link. Changes to past timestamps Correct many pre-1993 transitions, fixing entries originally derived from Shanks, Whitman, and Mundell. The fixes include: - Barbados: standard time was introduced in 1911, not 1932; and DST was observed in 1942-1944 - Cook Islands: In 1899 they switched from east to west of GMT, celebrating Christmas for two days. They (and Niue) switched to standard time in 1952, not 1901. - Guyana: corrected LMT for Georgetown; the introduction of standard time in 1911, not 1915; and corrections to 1975 and 1992 transitions - Kanton: uninhabited before 1937-08-31 - Niue: only observed -11:20 from 1952 through 1964, then went to -11 instead of -11:30 - Portugal: DST was observed in 1950 - Tonga: corrected LMT; the introduction of standard time in 1945, not 1901; and corrections to the transition from +12:20 to +13 in 1961, not 1941 Additional fixes to entries in the 'backzone' file include: - Enderbury: inhabited only 1860/1885 and 1938-03-06/1942-02-09 - The Gambia: 1933 and 1942 transitions - Malawi: several 1911 through 1925 transitions - Sierra Leone: several 1913 through 1941 transitions, and DST was NOT observed in 1957 through 1962 (Thanks to P Chan, Michael Deckers, Alexander Krivenyshev and Alois Treindl.) Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps. When merging, keep the most-populous location's data, and move data for other locations to 'backzone' with a backward link in 'backward'. For example, move America/Creston data to 'backzone' with a link in 'backward' from America/Phoenix because the two timezones' timestamps agree since 1970; this change affects some pre-1968 timestamps in America/Creston because Creston and Phoenix disagreed before 1968. The affected Zones are Africa/Accra, America/Atikokan, America/Blanc-Sablon, America/Creston, America/Curacao, America/Nassau, America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. Changes to maintenance procedure The new file SECURITY covers how to report security-related bugs. Several backward-compatibility links have been moved to the 'backward' file. These links, which range from Africa/Addis_Ababa to Pacific/Saipan, are only for compatibility with now-obsolete guidelines suggesting an entry for every ISO 3166 code. The intercontinental convenience links Asia/Istanbul and Europe/Nicosia have also been moved to 'backward'. Changes to code zic now creates each output file or link atomically, possibly by creating a temporary file and then renaming it. This avoids races where a TZ setting would temporarily stop working while zic was installing a replacement file or link. zic -L no longer omits the POSIX TZ string in its output. Starting with 2020a, zic -L truncated its output according to the "Expires" directive or "#expires" comment in the leapseconds file. The resulting TZif files omitted daylight saving transitions after the leap second table expired, which led to far less-accurate predictions of times after the expiry. Although future timestamps cannot be converted accurately in the presence of leap seconds, it is more accurate to convert near-future timestamps with a few seconds error than with an hour error, so zic -L no longer truncates output in this way. Instead, when zic -L is given the "Expires" directive, it now outputs the expiration by appending a no-change entry to the leap second table. Although this should work well with most TZif readers, it does not conform to Internet RFC 8536 and some pickier clients (including tzdb 2017c through 2021a) reject it, so "Expires" directives are currently disabled by default. To enable them, set the EXPIRES_LINE Makefile variable. If a TZif file uses this new feature it is marked with a new TZif version number 4, a format intended to be documented in a successor to RFC 8536. zic -L LEAPFILE -r @LO no longer generates an invalid TZif file that omits leap second information for the range LO..B when LO falls between two leap seconds A and B. Instead, it generates a TZif version 4 file that represents the previously-missing information. The TZif reader now allows the leap second table to begin with a correction other than -1 or +1, and to contain adjacent transitions with equal corrections. This supports TZif version 4. The TZif reader now lets leap seconds occur less than 28 days apart. This supports possible future TZif extensions. Fix bug that caused 'localtime' etc. to crash when TZ was set to a all-year DST string like "EST5EDT4,0/0,J365/25" that does not conform to POSIX but does conform to Internet RFC 8536. Fix another bug that caused 'localtime' etc. to crash when TZ was set to a POSIX-conforming but unusual TZ string like "EST5EDT4,0/0,J365/0", where almost all the year is DST. Fix yet another bug that caused 'localtime' etc. to mishandle slim TZif files containing leap seconds after the last explicit transition in the table, or when handling far-future timestamps in slim TZif files lacking leap seconds. Fix localtime misbehavior involving positive leap seconds. This change affects only behavior for "right" system time, which contains leap seconds, and only if the UT offset is not a multiple of 60 seconds when a positive leap second occurs. (No such timezone exists in tzdb, luckily.) Without the fix, the timestamp was ambiguous during a positive leap second. With the fix, any seconds occurring after a positive leap second and within the same localtime minute are counted through 60, not through 59; their UT offset (tm_gmtoff) is the same as before. Here is how the fix affects timestamps in a timezone with UT offset +01:23:45 (5025 seconds) and with a positive leap second at 1972-06-30 23:59:60 UTC (78796800): time_t without the fix with the fix 78796800 1972-07-01 01:23:45 1972-07-01 01:23:45 (leap second) 78796801 1972-07-01 01:23:45 1972-07-01 01:23:46 ... 78796815 1972-07-01 01:23:59 1972-07-01 01:23:60 78796816 1972-07-01 01:24:00 1972-07-01 01:24:00 Fix an unlikely bug that caused 'localtime' etc. to misbehave if civil time changes a few seconds before time_t wraps around, when leap seconds are enabled. Fix bug in zic -r; in some cases, the dummy time type after the last time transition disagreed with the TZ string, contrary to Internet RFC 8563 section 3.3. Fix a bug with 'zic -r @X' when X is a negative leap second that has a nonnegative correction. Without the fix, the output file was truncated so that X appeared to be a positive leap second. Fix a similar, even-less-likely bug when truncating at a positive leap second that has a nonpositive correction. zic -r now reports an error if given rolling leap seconds, as this usage has never generally worked and is evidently unused. zic now generates a POSIX-conforming TZ string for TZif files where all-year DST is predicted for the indefinite future. For example, for all-year Eastern Daylight Time, zic now generates "XXX3EDT4,0/0,J365/23" where it previously generated "EST5EDT,0/0,J365/25" or "". (Thanks to Michael Deckers for noting the possibility of POSIX conformance.) zic.c no longer requires sys/wait.h (thanks to spazmodius for noting it wasn't needed). When reading slim TZif files, zdump no longer mishandles leap seconds on the rare platforms where time_t counts leap seconds, fixing a bug introduced in 2014g. zdump -v now outputs timestamps at boundaries of what localtime and gmtime can represent, instead of the less-useful timestamps one day after the minimum and one day before the maximum. (Thanks to Arthur David Olson for prototype code, and to Manuela Friedrich for debugging help.) zdump's -c and -t options are now consistently inclusive for the lower time bound and exclusive for the upper. Formerly they were inconsistent. (Confusion noted by Martin Burnicki.) Changes to build procedure You can now compile with -DHAVE_MALLOC_ERRNO=0 to port to non-POSIX hosts where malloc doesn't set errno. (Problem reported by Jan Engelhardt.) Changes to documentation tzfile.5 better matches a draft successor to RFC 8536 . Release 2021a - 2021-01-24 10:54:57 -0800 Changes to future timestamps South Sudan changes from +03 to +02 on 2021-02-01 at 00:00. (Thanks to Steffen Thorsen.) Release 2020f - 2020-12-29 00:17:46 -0800 Change to build procedure 'make rearguard_tarballs' no longer generates a bad rearguard.zi, fixing a 2020e bug. (Problem reported by Deborah Goldsmith.) Release 2020e - 2020-12-22 15:14:34 -0800 Briefly: Volgograd switches to Moscow time on 2020-12-27 at 02:00. Changes to future timestamps Volgograd changes time zone from +04 to +03 on 2020-12-27 at 02:00. (Thanks to Alexander Krivenyshev and Stepan Golosunov.) Changes to past timestamps Correct many pre-1986 transitions, fixing entries originally derived from Shanks. The fixes include: - Australia: several 1917 through 1971 transitions - The Bahamas: several 1941 through 1945 transitions - Bermuda: several 1917 through 1956 transitions - Belize: several 1942 through 1968 transitions - Ghana: several 1915 through 1956 transitions - Israel and Palestine: several 1940 through 1985 transitions - Kenya and adjacent: several 1908 through 1960 transitions - Nigeria and adjacent: correcting LMT in Lagos, and several 1905 through 1919 transitions - Seychelles: the introduction of standard time in 1907, not 1906 - Vanuatu: DST in 1973-1974, and a corrected 1984 transition (Thanks to P Chan.) Because of the Australia change, Australia/Currie (King Island) is no longer needed, as it is identical to Australia/Hobart for all timestamps since 1970 and was therefore created by mistake. Australia/Currie has been moved to the 'backward' file and its corrected data moved to the 'backzone' file. Changes to past time zone abbreviations and DST flags To better match legislation in Turks and Caicos, the 2015 shift to year-round observance of -04 is now modeled as AST throughout before returning to Eastern Time with US DST in 2018, rather than as maintaining EDT until 2015-11-01. (Thanks to P Chan.) Changes to documentation The zic man page now documents zic's coalescing of transitions when a zone falls back just before DST springs forward. Release 2020d - 2020-10-21 11:24:13 -0700 Briefly: Palestine ends DST earlier than predicted, on 2020-10-24. Changes to past and future timestamps Palestine ends DST on 2020-10-24 at 01:00, instead of 2020-10-31 as previously predicted (thanks to Sharef Mustafa.) Its 2019-10-26 fall-back was at 00:00, not 01:00 (thanks to Steffen Thorsen.) Its 2015-10-23 transition was at 01:00 not 00:00, and its spring 2020 transition was on March 28 at 00:00, not March 27 (thanks to Pierre Cashon.) This affects Asia/Gaza and Asia/Hebron. Assume future spring and fall transitions will be on the Saturday preceding the last Sunday of March and October, respectively. Release 2020c - 2020-10-16 11:15:53 -0700 Briefly: Fiji starts DST later than usual, on 2020-12-20. Changes to future timestamps Fiji will start DST on 2020-12-20, instead of 2020-11-08 as previously predicted. DST will still end on 2021-01-17. (Thanks to Raymond Kumar and Alan Mintz.) Assume for now that the later-than-usual start date is a one-time departure from the recent pattern. Changes to build procedure Rearguard tarballs now contain an empty file pacificnew. Some older downstream software expects this file to exist. (Problem reported by Mike Cullinan.) Release 2020b - 2020-10-06 18:35:04 -0700 Briefly: Revised predictions for Morocco's changes starting in 2023. Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. Macquarie Island has stayed in sync with Tasmania since 2011. Casey, Antarctica is at +08 in winter and +11 in summer. zic no longer supports -y, nor the TYPE field of Rules. Changes to future timestamps Morocco's spring-forward after Ramadan is now predicted to occur no sooner than two days after Ramadan, instead of one day. (Thanks to Milamber.) The first altered prediction is for 2023, now predicted to spring-forward on April 30 instead of April 23. Changes to past and future timestamps Casey Station, Antarctica has been using +08 in winter and +11 in summer since 2018. The most recent transition from +08 to +11 was 2020-10-04 00:01. Also, Macquarie Island has been staying in sync with Tasmania since 2011. (Thanks to Steffen Thorsen.) Changes to past and future time zone abbreviations and DST flags Canada's Yukon, represented by America/Whitehorse and America/Dawson, changes its time zone rules from -08/-07 to permanent -07 on 2020-11-01, not on 2020-03-08 as 2020a had it. This change affects only the time zone abbreviation (MST vs PDT) and daylight saving flag for the period between the two dates. (Thanks to Andrew G. Smith.) Changes to past timestamps Correct several transitions for Hungary for 1918/1983. For example, the 1983-09-25 fall-back was at 01:00, not 03:00. (Thanks to Géza Nyáry.) Also, the 1890 transition to standard time was on 11-01, not 10-01 (thanks to Michael Deckers). The 1891 French transition was on March 16, not March 15. The 1911-03-11 French transition was at midnight, not a minute later. Monaco's transitions were on 1892-06-01 and 1911-03-29, not 1891-03-15 and 1911-03-11. (Thanks to Michael Deckers.) Changes to code Support for zic's long-obsolete '-y YEARISTYPE' option has been removed and, with it, so has support for the TYPE field in Rule lines, which is now reserved for compatibility with earlier zic. These features were previously deprecated in release 2015f. (Thanks to Tim Parenti.) zic now defaults to '-b slim' instead of to '-b fat'. zic's new '-l -' and '-p -' options uninstall any existing localtime and posixrules files, respectively. The undocumented and ineffective tzsetwall function has been removed. Changes to build procedure The Makefile now defaults POSIXRULES to '-', so the posixrules feature (obsolete as of 2019b) is no longer installed by default. Changes to documentation and commentary The long-obsolete files pacificnew, systemv, and yearistype.sh have been removed from the distribution. (Thanks to Tim Parenti.) Release 2020a - 2020-04-23 16:03:47 -0700 Briefly: Morocco springs forward on 2020-05-31, not 2020-05-24. Canada's Yukon advanced to -07 year-round on 2020-03-08. America/Nuuk renamed from America/Godthab. zic now supports expiration dates for leap second lists. Changes to future timestamps Morocco's second spring-forward transition in 2020 will be May 31, not May 24 as predicted earlier. (Thanks to Semlali Naoufal.) Adjust future-year predictions to use the first Sunday after the day after Ramadan, not the first Sunday after Ramadan. Canada's Yukon, represented by America/Whitehorse and America/Dawson, advanced to -07 year-round, beginning with its spring-forward transition on 2020-03-08, and will not fall back on 2020-11-01. Although a government press release calls this "permanent Pacific Daylight Saving Time", we prefer MST for consistency with nearby Dawson Creek, Creston, and Fort Nelson. (Thanks to Tim Parenti.) Changes to past timestamps Shanghai observed DST in 1919. (Thanks to Phake Nick.) Changes to timezone identifiers To reflect current usage in English better, America/Godthab has been renamed to America/Nuuk. A backwards-compatibility link remains for the old name. Changes to code localtime.c no longer mishandles timestamps after the last transition in a TZif file with leap seconds and with daylight saving time transitions projected into the indefinite future. For example, with TZ='America/Los_Angeles' with leap seconds, zdump formerly reported a DST transition on 2038-03-14 from 01:59:32.999... to 02:59:33 instead of the correct transition from 01:59:59.999... to 03:00:00. zic -L now supports an Expires line in the leapseconds file, and truncates the TZif output accordingly. This propagates leap second expiration information into the TZif file, and avoids the abovementioned localtime.c bug as well as similar bugs present in many client implementations. If no Expires line is present, zic -L instead truncates the TZif output based on the #expires comment present in leapseconds files distributed by tzdb 2018f and later; however, this usage is obsolescent. For now, the distributed leapseconds file has an Expires line that is commented out, so that the file can be fed to older versions of zic which ignore the commented-out line. Future tzdb distributions are planned to contain a leapseconds file with an Expires line. The configuration macros HAVE_TZNAME and USG_COMPAT should now be set to 1 if the system library supports the feature, and 2 if not. As before, these macros are nonzero if tzcode should support the feature, zero otherwise. The configuration macro ALTZONE now has the same values with the same meaning as HAVE_TZNAME and USG_COMPAT. The code's defense against CRLF in leap-seconds.list is now portable to POSIX awk. (Problem reported by Deborah Goldsmith.) Although the undocumented tzsetwall function is not changed in this release, it is now deprecated in preparation for removal in future releases. Due to POSIX requirements, tzsetwall has not worked for some time. Any code that uses it should instead use tzalloc(NULL) or, if portability trumps thread-safety, should unset the TZ environment variable. Changes to commentary The Îles-de-la-Madeleine and the Listuguj reserve are noted as following America/Halifax, and comments about Yukon's "south" and "north" have been corrected to say "east" and "west". (Thanks to Jeffery Nichols.) Release 2019c - 2019-09-11 08:59:48 -0700 Briefly: Fiji observes DST from 2019-11-10 to 2020-01-12. Norfolk Island starts observing Australian-style DST. Changes to future timestamps Fiji's next DST transitions will be 2019-11-10 and 2020-01-12 instead of 2019-11-03 and 2020-01-19. (Thanks to Raymond Kumar.) Adjust future guesses accordingly. Norfolk Island will observe Australian-style DST starting in spring 2019. The first transition is on 2019-10-06. (Thanks to Kyle Czech and Michael Deckers.) Changes to past timestamps Many corrections to time in Turkey from 1940 through 1985. (Thanks to Oya Vulaş via Alois Treindl, and to Kıvanç Yazan.) The Norfolk Island 1975-03-02 transition was at 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.) South Korea observed DST from 1948 through 1951. Although this info was supposed to appear in release 2014j, a typo inadvertently suppressed the change. (Thanks to Alois Treindl.) Detroit observed DST in 1967 and 1968 following the US DST rules, except that its 1967 DST began on June 14 at 00:01. (Thanks to Alois Treindl for pointing out that the old data entries were probably wrong.) Fix several errors in pre-1970 transitions in Perry County, IN. (Thanks to Alois Treindl for pointing out the 1967/9 errors.) Edmonton did not observe DST in 1967 or 1969. In 1946 Vancouver ended DST on 09-29 not 10-13, and Vienna ended DST on 10-07 not 10-06. In 1945 Königsberg (now Kaliningrad) switched from +01/+02 to +02/+03 on 04-10 not 01-01, and its +02/+03 is abbreviated EET/EEST, not CET/CEST. (Thanks to Alois Treindl.) In 1946 Königsberg switched to +03 on 04-07 not 01-01. In 1946 Louisville switched from CST to CDT on 04-28 at 00:01, not 01-01 at 00:00. (Thanks to Alois Treindl and Michael Deckers.) Also, it switched from CST to CDT on 1950-04-30, not 1947-04-27. The 1892-05-01 transition in Brussels was at 00:17:30, not at noon. (Thanks to Michael Deckers.) Changes to past time zone abbreviations and DST flags Hong Kong Winter Time, observed from 1941-10-01 to 1941-12-25, is now flagged as DST and is abbreviated HKWT not HKT. Changes to code leapseconds.awk now relies only on its input data, rather than also relying on its comments. (Inspired by code from Dennis Ferguson and Chris Woodbury.) The code now defends against CRLFs in leap-seconds.list. (Thanks to Brian Inglis and Chris Woodbury.) Changes to documentation and commentary theory.html discusses leap seconds. (Thanks to Steve Summit.) Nashville's newspapers dueled about the time of day in the 1950s. (Thanks to John Seigenthaler.) Liechtenstein observed Swiss DST in 1941/2. (Thanks to Alois Treindl.) Release 2019b - 2019-07-01 00:09:53 -0700 Briefly: Brazil no longer observes DST. 'zic -b slim' outputs smaller TZif files; please try it out. Palestine's 2019 spring-forward transition was on 03-29, not 03-30. Changes to future timestamps Brazil has canceled DST and will stay on standard time indefinitely. (Thanks to Steffen Thorsen, Marcus Diniz, and Daniel Soares de Oliveira.) Predictions for Morocco now go through 2087 instead of 2037, to work around a problem on newlib when using TZif files output by zic 2019a or earlier. (Problem reported by David Gauchard.) Changes to past and future timestamps Palestine's 2019 spring transition was 03-29 at 00:00, not 03-30 at 01:00. (Thanks to Sharef Mustafa and Even Scharning.) Guess future transitions to be March's last Friday at 00:00. Changes to past timestamps Hong Kong's 1941-06-15 spring-forward transition was at 03:00, not 03:30. Its 1945 transition from JST to HKT was on 11-18 at 02:00, not 09-15 at 00:00. In 1946 its spring-forward transition was on 04-21 at 00:00, not the previous day at 03:30. From 1946 through 1952 its fall-back transitions occurred at 04:30, not at 03:30. In 1947 its fall-back transition was on 11-30, not 12-30. (Thanks to P Chan.) Changes to past time zone abbreviations Italy's 1866 transition to Rome Mean Time was on December 12, not September 22. This affects only the time zone abbreviation for Europe/Rome between those dates. (Thanks to Stephen Trainor and Luigi Rosa.) Changes affecting metadata only Add info about the Crimea situation in zone1970.tab and zone.tab. (Problem reported by Serhii Demediuk.) Changes to code zic's new -b option supports a way to control data bloat and to test for year-2038 bugs in software that reads TZif files. 'zic -b fat' and 'zic -b slim' generate larger and smaller output; for example, changing from fat to slim shrinks the Europe/London file from 3648 to 1599 bytes, saving about 56%. Fat and slim files represent the same set of timestamps and use the same TZif format as documented in tzfile(5) and in Internet RFC 8536. Fat format attempts to work around bugs or incompatibilities in older software, notably software that mishandles 64-bit TZif data or uses obsolete TZ strings like "EET-2EEST" that lack DST rules. Slim format is more efficient and does not work around 64-bit bugs or obsolete TZ strings. Currently zic defaults to fat format unless you compile with -DZIC_BLOAT_DEFAULT=\"slim\"; this out-of-the-box default is intended to change in future releases as the buggy software often mishandles timestamps anyway. zic no longer treats a set of rules ending in 2037 specially. Previously, zic assumed that such a ruleset meant that future timestamps could not be predicted, and therefore omitted a POSIX-like TZ string in the TZif output. The old behavior is no longer needed for current tzdata, and caused problems with newlib when used with older tzdata (reported by David Gauchard). zic no longer generates some artifact transitions. For example, Europe/London no longer has a no-op transition in January 1996. Changes to build procedure tzdata.zi now assumes zic 2017c or later. This shrinks tzdata.zi by a percent or so. Changes to documentation and commentary The Makefile now documents the POSIXRULES macro as being obsolete, and similarly, zic's -p POSIXRULES option is now documented as being obsolete. Although the POSIXRULES feature still exists and works as before, in practice it is rarely used for its intended purpose, and it does not work either in the default reference implementation (for timestamps after 2037) or in common implementations such as GNU/Linux (for contemporary timestamps). Since POSIXRULES was designed primarily as a temporary transition facility for System V platforms that died off decades ago, it is being decommissioned rather than institutionalized. New info on Bonin Islands and Marcus (thanks to Wakaba and Phake Nick). Release 2019a - 2019-03-25 22:01:33 -0700 Briefly: Palestine "springs forward" on 2019-03-30 instead of 2019-03-23. Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00. Changes to past and future timestamps Palestine will not start DST until 2019-03-30, instead of 2019-03-23 as previously predicted. Adjust our prediction by guessing that spring transitions will be between 24 and 30 March, which matches recent practice since 2016. (Thanks to Even Scharning and Tim Parenti.) Metlakatla ended its observance of Pacific standard time, rejoining Alaska Time, on 2019-01-20 at 02:00. (Thanks to Ryan Stanley and Tim Parenti.) Changes to past timestamps Israel observed DST in 1980 (08-02/09-13) and 1984 (05-05/08-25). (Thanks to Alois Treindl and Isaac Starkman.) Changes to time zone abbreviations Etc/UCT is now a backward-compatibility link to Etc/UTC, instead of being a separate zone that generates the abbreviation "UCT", which nowadays is typically a typo. (Problem reported by Isiah Meadows.) Changes to code zic now has an -r option to limit the time range of output data. For example, 'zic -r @1000000000' limits the output data to timestamps starting 1000000000 seconds after the Epoch. This helps shrink output size and can be useful for applications not needing the full timestamp history, such as TZDIST truncation; see Internet RFC 8536 section 5.1. (Inspired by a feature request from Christopher Wong, helped along by bug reports from Wong and from Tim Parenti.) Changes to documentation Mention Internet RFC 8536 (February 2019), which documents TZif. tz-link.html now cites tzdata-meta . Release 2018i - 2018-12-30 11:05:43 -0800 Briefly: São Tomé and Príncipe switches from +01 to +00 on 2019-01-01. Changes to future timestamps Due to a change in government, São Tomé and Príncipe switches back from +01 to +00 on 2019-01-01 at 02:00. (Thanks to Vadim Nasardinov and Michael Deckers.) Release 2018h - 2018-12-23 17:59:32 -0800 Briefly: Qyzylorda, Kazakhstan moved from +06 to +05 on 2018-12-21. New zone Asia/Qostanay because Qostanay, Kazakhstan didn't move. Metlakatla, Alaska observes PST this winter only. Guess Morocco will continue to adjust clocks around Ramadan. Add predictions for Iran from 2038 through 2090. Changes to future timestamps Guess that Morocco will continue to fall back just before and spring forward just after Ramadan, the practice since 2012. (Thanks to Maamar Abdelkader.) This means Morocco will observe negative DST during Ramadan in main and vanguard formats, and in rearguard format it stays in the +00 timezone and observes ordinary DST in all months other than Ramadan. As before, extend this guesswork to the year 2037. As a consequence, Morocco is scheduled to observe three DST transitions in some Gregorian years (e.g., 2033) due to the mismatch between the Gregorian and Islamic calendars. The table of exact transitions for Iranian DST has been extended. It formerly cut off before the year 2038 in a nod to 32-bit time_t. It now cuts off before 2091 as there is doubt about how the Persian calendar will treat 2091. This change predicts DST transitions in 2038-9, 2042-3, and 2046-7 to occur one day later than previously predicted. As before, post-cutoff transitions are approximated. Changes to past and future timestamps Qyzylorda (aka Kyzylorda) oblast in Kazakhstan moved from +06 to +05 on 2018-12-21. This is a zone split as Qostanay (aka Kostanay) did not switch, so create a zone Asia/Qostanay. Metlakatla moved from Alaska to Pacific standard time on 2018-11-04. It did not change clocks that day and remains on -08 this winter. (Thanks to Ryan Stanley.) It will revert to the usual Alaska rules next spring, so this change affects only timestamps from 2018-11-04 through 2019-03-10. Change to past timestamps Kwajalein's 1993-08-20 transition from -12 to +12 was at 24:00, not 00:00. I transcribed the time incorrectly from Shanks. (Thanks to Phake Nick.) Nauru's 1979 transition was on 02-10 at 02:00, not 05-01 at 00:00. (Thanks to Phake Nick.) Guam observed DST irregularly from 1959 through 1977. (Thanks to Phake Nick.) Hong Kong observed DST in 1941 starting 06-15 (not 04-01), then on 10-01 changed standard time to +08:30 (not +08). Its transition back to +08 after WWII was on 1945-09-15, not the previous day. Its 1904-10-30 change took effect at 01:00 +08 (not 00:00 LMT). (Thanks to Phake Nick, Steve Allen, and Joseph Myers.) Also, its 1952 fallback was on 11-02 (not 10-25). This release contains many changes to timestamps before 1946 due to Japanese possession or occupation of Pacific/Chuuk, Pacific/Guam, Pacific/Kosrae, Pacific/Kwajalein, Pacific/Majuro, Pacific/Nauru, Pacific/Palau, and Pacific/Pohnpei. (Thanks to Phake Nick.) Assume that the Spanish East Indies was like the Philippines and observed American time until the end of 1844. This affects Pacific/Chuuk, Pacific/Kosrae, Pacific/Palau, and Pacific/Pohnpei. Changes to past tm_isdst flags For the recent Morocco change, the tm_isdst flag should be 1 from 2018-10-27 00:00 to 2018-10-28 03:00. (Thanks to Michael Deckers.) Give a URL to the official decree. (Thanks to Matt Johnson.) Release 2018g - 2018-10-26 22:22:45 -0700 Briefly: Morocco switches to permanent +01 on 2018-10-28. Changes to future timestamps Morocco switches from +00/+01 to permanent +01 effective 2018-10-28, so its clocks will not fall back as previously scheduled. (Thanks to Mohamed Essedik Najd and Brian Inglis.) Changes to code When generating TZif files with leap seconds, zic no longer uses a format that trips up older 32-bit clients, fixing a bug introduced in 2018f. (Reported by Daniel Fischer.) Also, the zic workaround for QTBUG-53071 now also works for TZif files with leap seconds. The translator to rearguard format now rewrites the line "Rule Japan 1948 1951 - Sep Sat>=8 25:00 0 S" to "Rule Japan 1948 1951 - Sep Sun>=9 1:00 0 S". This caters to zic before 2007 and to Oracle TZUpdater 2.2.0 and earlier. (Reported by Christos Zoulas.) Changes to past time zone abbreviations Change HDT to HWT/HPT for WWII-era abbreviations in Hawaii. This reverts to 2011h, as the abbreviation change in 2011i was likely inadvertent. Changes to documentation tzfile.5 has new sections on interoperability issues. Release 2018f - 2018-10-18 00:14:18 -0700 Briefly: Volgograd moves from +03 to +04 on 2018-10-28. Fiji ends DST 2019-01-13, not 2019-01-20. Most of Chile changes DST dates, effective 2019-04-06. Changes to future timestamps Volgograd moves from +03 to +04 on 2018-10-28 at 02:00. (Thanks to Alexander Fetisov and Stepan Golosunov.) Fiji ends DST 2019-01-13 instead of the 2019-01-20 previously predicted. (Thanks to Raymond Kumar.) Adjust future predictions accordingly. Most of Chile will end DST on the first Saturday in April at 24:00 mainland time, and resume DST on the first Saturday in September at 24:00 mainland time. The changes are effective from 2019-04-06, and do not affect the Magallanes region modeled by America/Punta_Arenas. (Thanks to Juan Correa and Tim Parenti.) Adjust future predictions accordingly. Changes to past timestamps The 2018-05-05 North Korea 30-minute time zone change took place at 23:30 the previous day, not at 00:00 that day. China's 1988 spring-forward transition was on April 17, not April 10. Its DST transitions in 1986/91 were at 02:00, not 00:00. (Thanks to P Chan.) Fix several issues for Macau before 1992. Macau's pre-1904 LMT was off by 10 s. Macau switched to +08 in 1904 not 1912, and temporarily switched to +09/+10 during World War II. Macau observed DST in 1942/79, not 1961/80, and there were several errors for transition times and dates. (Thanks to P Chan.) The 1948-1951 fallback transitions in Japan were at 25:00 on September's second Saturday, not at 24:00. (Thanks to Phake Nick.) zic turns this into 01:00 on the day after September's second Saturday, which is the best that POSIX or C platforms can do. Incorporate 1940-1949 Asia/Shanghai DST transitions from a 2014 paper by Li Yu, replacing more-questionable data from Shanks. Changes to time zone abbreviations Use "PST" and "PDT" for Philippine time. (Thanks to Paul Goyette.) Changes to code zic now always generates TZif files where time type 0 is used for timestamps before the first transition. This simplifies the reading of TZif files and should not affect behavior of existing TZif readers because the same set of time types is used; only their internal indexes may have changed. This affects only the legacy zones EST5EDT, CST6CDT, MST7MDT, PST8PDT, CET, MET, and EET, which previously used nonzero types for these timestamps. Because of the type 0 change, zic no longer outputs a dummy transition at time -2**59 (before the Big Bang), as clients should no longer need this to handle historical timestamps correctly. This reverts a change introduced in 2013d and shrinks most TZif files by a few bytes. zic now supports negative time-of-day in Rule and Leap lines, e.g., "Rule X min max - Apr lastSun -6:00 1:00 -" means the transition occurs at 18:00 on the Saturday before the last Sunday in April. This behavior was documented in 2018a but the code did not entirely match the documentation. localtime.c no longer requires at least one time type in TZif files that lack transitions or have a POSIX-style TZ string. This future-proofs the code against possible future extensions to the format that would allow TZif files with POSIX-style TZ strings and without transitions or time types. A read-access subscript error in localtime.c has been fixed. It could occur only in TZif files with timecnt == 0, something that does not happen in practice now but could happen in future versions. localtime.c no longer ignores TZif POSIX-style TZ strings that specify only standard time. Instead, these TZ strings now override the default time type for timestamps after the last transition (or for all timestamps if there are no transitions), just as DST strings specifying DST have always done. leapseconds.awk now outputs "#updated" and "#expires" comments, and supports leap seconds at the ends of months other than June and December. (Inspired by suggestions from Chris Woodbury.) Changes to documentation New restrictions: A Rule name must start with a character that is neither an ASCII digit nor "-" nor "+", and an unquoted name should not use characters in the set "!$%&'()*,/:;<=>?@[\]^`{|}~". The latter restriction makes room for future extensions (a possibility noted by Tom Lane). tzfile.5 now documents what time types apply before the first and after the last transition, if any. Documentation now uses the spelling "timezone" for a TZ setting that determines timestamp history, and "time zone" for a geographic region currently sharing the same standard time. The name "TZif" is now used for the tz binary data format. tz-link.htm now mentions the A0 TimeZone Migration utilities. (Thanks to Aldrin Martoq for the link.) Changes to build procedure New 'make' target 'rearguard_tarballs' to build the rearguard tarball only. This is a convenience on platforms that lack lzip if you want to build the rearguard tarball. (Problem reported by Deborah Goldsmith.) tzdata.zi is now more stable from release to release. (Problem noted by Tom Lane.) It is also a bit shorter. tzdata.zi now can contain comment lines documenting configuration information, such as which data format was selected, which input files were used, and how leap seconds are treated. (Problems noted by Lester Caine and Brian Inglis.) If the Makefile defaults are used these comment lines are absent, for backward compatibility. A redistributor intending to alter its copy of the files should also append "-LABEL" to the 'version' file's first line, where "LABEL" identifies the redistributor's change. Release 2018e - 2018-05-01 23:42:51 -0700 Briefly: North Korea switches back to +09 on 2018-05-05. The main format uses negative DST again, for Ireland etc. 'make tarballs' now also builds a rearguard tarball. New 's' and 'd' suffixes in SAVE columns of Rule and Zone lines. Changes to past and future timestamps North Korea switches back from +0830 to +09 on 2018-05-05. (Thanks to Kang Seonghoon, Arthur David Olson, Seo Sanghyeon, and Tim Parenti.) Bring back the negative-DST changes of 2018a, except be more compatible with data parsers that do not support negative DST. Also, this now affects historical timestamps in Namibia and the former Czechoslovakia, not just Ireland. The main format now uses negative DST to model timestamps in Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and Africa/Windhoek (1994/2017). This does not affect UT offsets, only time zone abbreviations and the tm_isdst flag. Also, this does not affect rearguard or vanguard formats; effectively the main format now uses vanguard instead of rearguard format. Data parsers that do not support negative DST can still use data from the rearguard tarball described below. Changes to build procedure The command 'make tarballs' now also builds the tarball tzdataVERSION-rearguard.tar.gz, which is like tzdataVERSION.tar.gz except that it uses rearguard format intended for trailing-edge data parsers. Changes to data format and to code The SAVE column of Rule and Zone lines can now have an 's' or 'd' suffix, which specifies whether the adjusted time is standard time or daylight saving time. If no suffix is given, daylight saving time is used if and only if the SAVE column is nonzero; this is the longstanding behavior. Although this new feature is not used in tzdata, it could be used to specify the legal time in Namibia 1994-2017, as opposed to the popular time (see below). Changes to past timestamps From 1994 through 2017 Namibia observed DST in winter, not summer. That is, it used negative DST, as Ireland still does. This change does not affect UTC offsets; it affects only the tm_isdst flag and the abbreviation used during summer, which is now CAT, not WAST. Although (as noted by Michael Deckers) summer and winter time were both simply called "standard time" in Namibian law, in common practice winter time was considered to be DST (as noted by Stephen Colebourne). The full effect of this change is only in vanguard and main format; in rearguard format, the tm_isdst flag is still zero in winter and nonzero in summer. In 1946/7 Czechoslovakia also observed negative DST in winter. The full effect of this change is only in vanguard and main formats; in rearguard format, it is modeled as plain GMT without daylight saving. Also, the dates of some 1944/5 DST transitions in Czechoslovakia have been changed. Release 2018d - 2018-03-22 07:05:46 -0700 Briefly: Palestine starts DST a week earlier in 2018. Add support for vanguard and rearguard data consumers. Add subsecond precision to source data format, though not to data. Changes to future timestamps In 2018, Palestine starts DST on March 24, not March 31. Adjust future predictions accordingly. (Thanks to Sharef Mustafa.) Changes to past and future timestamps Casey Station in Antarctica changed from +11 to +08 on 2018-03-11 at 04:00. (Thanks to Steffen Thorsen.) Changes to past timestamps Historical transitions for Uruguay, represented by America/Montevideo, have been updated per official legal documents, replacing previous data mainly originating from the inventions of Shanks & Pottenger. This has resulted in adjustments ranging from 30 to 90 minutes in either direction over at least two dozen distinct periods ranging from one day to several years in length. A mere handful of pre-1991 transitions are unaffected; data since then has come from more reliable contemporaneous reporting. These changes affect various timestamps in 1920-1923, 1936, 1939, 1942-1943, 1959, 1966-1970, 1972, 1974-1980, and 1988-1990. Additionally, Uruguay's pre-standard-time UT offset has been adjusted westward by 7 seconds, from UT-03:44:44 to UT-03:44:51, to match the location of the Observatory of the National Meteorological Institute in Montevideo. (Thanks to Jeremie Bonjour, Tim Parenti, and Michael Deckers.) East Kiribati skipped New Year's Eve 1994, not New Year's Day 1995. (Thanks to Kerry Shetline.) Fix the 1912-01-01 transition for Portugal and its colonies. This transition was at 00:00 according to the new UT offset, not according to the old one. Also assume that Cape Verde switched on the same date as the rest, not in 1907. This affects Africa/Bissau, Africa/Sao_Tome, Asia/Macau, Atlantic/Azores, Atlantic/Cape_Verde, Atlantic/Madeira, and Europe/Lisbon. (Thanks to Michael Deckers.) Fix an off-by-1 error for pre-1913 timestamps in Jamaica and in Turks & Caicos. Changes to past time zone abbreviations MMT took effect in Uruguay from 1908-06-10, not 1898-06-28. There is no clock change associated with the transition. Changes to build procedure The new DATAFORM macro in the Makefile lets the installer choose among three source data formats. The idea is to lessen downstream disruption when data formats are improved. * DATAFORM=vanguard installs from the latest, bleeding-edge format. DATAFORM=main (the default) installs from the format used in the 'africa' etc. files. DATAFORM=rearguard installs from a trailing-edge format. Eventually, elements of today's vanguard format should move to the main format, and similarly the main format's features should eventually move to the rearguard format. * In the current version, the main and rearguard formats are identical and match that of 2018c, so this change does not affect default behavior. The vanguard format currently contains one feature not in the main format: negative SAVE values. This improves support for Ireland, which uses Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in winter. tzcode has supported negative SAVE values for decades, and this feature should move to the main format soon. However, it will not move to the rearguard format for quite some time because some downstream parsers do not support it. * The build procedure constructs three files vanguard.zi, main.zi, and rearguard.zi, one for each format. Although the files represent essentially the same data, they may have minor discrepancies that users are not likely to notice. The files are intended for downstream data consumers and are not installed. Zoneinfo parsers that do not support negative SAVE values should start using rearguard.zi, so that they will be unaffected when the negative-DST feature moves from vanguard to main. Bleeding-edge Zoneinfo parsers that support the new features already can use vanguard.zi; in this respect, current tzcode is bleeding-edge. The Makefile should now be safe for parallelized builds, and 'make -j to2050new.tzs' is now much faster on a multiprocessor host with GNU Make. When built with -DSUPPRESS_TZDIR, the tzcode library no longer prepends TZDIR/ to file names that do not begin with '/'. This is not recommended for general use, due to its security implications. (From a suggestion by Manuela Friedrich.) Changes to code zic now accepts subsecond precision in expressions like 00:19:32.13, which is approximately the legal time of the Netherlands from 1835 to 1937. However, because it is questionable whether the few recorded uses of non-integer offsets had subsecond precision in practice, there are no plans for tzdata to use this feature. (Thanks to Steve Allen for pointing out the limitations of historical data in this area.) The code is a bit more portable to MS-Windows. Installers can compile with -DRESERVE_STD_EXT_IDS on MS-Windows platforms that reserve identifiers like 'localtime'. (Thanks to Manuela Friedrich.) Changes to documentation and commentary theory.html now outlines tzdb's extensions to POSIX's model for civil time, and has a section "POSIX features no longer needed" that lists POSIX API components that are now vestigial. (From suggestions by Steve Summit.) It also better distinguishes time zones from tz regions. (From a suggestion by Guy Harris.) Commentary is now more consistent about using the phrase "daylight saving time", to match the C name tm_isdst. Daylight saving time need not occur in summer, and need not have a positive offset from standard time. Commentary about historical transitions in Uruguay has been expanded with links to many relevant legal documents. (Thanks to Tim Parenti.) Commentary now uses some non-ASCII characters with Unicode value less than U+0100, as they can be useful and should work even with older editors such as XEmacs. Release 2018c - 2018-01-22 23:00:44 -0800 Briefly: Revert Irish changes that relied on negative SAVE values. Changes to tm_isdst Revert the 2018a change to Europe/Dublin. As before, this change does not affect UT offsets or abbreviations; it affects only whether timestamps are considered to be standard time or daylight-saving time, as expressed in the tm_isdst flag of C's struct tm type. This reversion is intended to be a temporary workaround for problems discovered with downstream uses of releases 2018a and 2018b, which implemented Irish time by using negative SAVE values in the Eire rules of the 'europe' file. Although negative SAVE values have been part of tzcode for many years and are supported by many platforms, they were not documented before 2018a and ICU and OpenJDK do not currently support them. A mechanism to export data to platforms lacking support for negative DST is planned to be developed before the change is reapplied. (Problems reported by Deborah Goldsmith and Stephen Colebourne.) Changes to past timestamps Japanese DST transitions (1948-1951) were Sundays at 00:00, not Saturdays or Sundays at 02:00. (Thanks to Takayuki Nikai.) Changes to build procedure The build procedure now works around mawk 1.3.3's lack of support for character class expressions. (Problem reported by Ohyama.) Release 2018b - 2018-01-17 23:24:48 -0800 Briefly: Fix a packaging problem in tz2018a, which was missing 'pacificnew'. Changes to build procedure The distribution now contains the file 'pacificnew' again. This file was inadvertently omitted in the 2018a distribution. (Problem reported by Matias Fonzo.) Release 2018a - 2018-01-12 22:29:21 -0800 Briefly: São Tomé and Príncipe switched from +00 to +01. Brazil's DST will now start on November's first Sunday. Ireland's standard time is now in the summer, not the winter. Use Debian-style installation locations, instead of 4.3BSD-style. New zic option -t. Changes to past and future timestamps São Tomé and Príncipe switched from +00 to +01 on 2018-01-01 at 01:00. (Thanks to Steffen Thorsen and Michael Deckers.) Changes to future timestamps Starting in 2018 southern Brazil will begin DST on November's first Sunday instead of October's third Sunday. (Thanks to Steffen Thorsen.) Changes to past timestamps A discrepancy of 4 s in timestamps before 1931 in South Sudan has been corrected. The 'backzone' and 'zone.tab' files did not agree with the 'africa' and 'zone1970.tab' files. (Problem reported by Michael Deckers.) The abbreviation invented for Bolivia Summer Time (1931-2) is now BST instead of BOST, to be more consistent with the convention used for Latvian Summer Time (1918-9) and for British Summer Time. Changes to tm_isdst Change Europe/Dublin so that it observes Irish Standard Time (UT +01) in summer and GMT (as negative daylight-saving) in winter, instead of observing standard time (GMT) in winter and Irish Summer Time (UT +01) in summer. This change does not affect UT offsets or abbreviations; it affects only whether timestamps are considered to be standard time or daylight-saving time, as expressed in the tm_isdst flag of C's struct tm type. (Discrepancy noted by Derick Rethans.) Changes to build procedure The default installation locations have been changed to mostly match Debian circa 2017, instead of being designed as an add-on to 4.3BSD circa 1986. This affects the Makefile macros TOPDIR, TZDIR, MANDIR, and LIBDIR. New Makefile macros TZDEFAULT, USRDIR, USRSHAREDIR, BINDIR, ZDUMPDIR, and ZICDIR let installers tailor locations more precisely. (This responds to suggestions from Brian Inglis and from Steve Summit.) The default installation procedure no longer creates the backward-compatibility link US/Pacific-New, which causes confusion during user setup (e.g., see Debian bug 815200). Use 'make BACKWARD="backward pacificnew"' to create the link anyway, for now. Eventually we plan to remove the link entirely. tzdata.zi now contains a version-number comment. (Suggested by Tom Lane.) The Makefile now quotes values like BACKWARD more carefully when passing them to the shell. (Problem reported by Zefram.) Builders no longer need to specify -DHAVE_SNPRINTF on platforms that have snprintf and use pre-C99 compilers. (Problem reported by Jon Skeet.) Changes to code zic has a new option -t FILE that specifies the location of the file that determines local time when TZ is unset. The default for this location can be configured via the new TZDEFAULT makefile macro, which defaults to /etc/localtime. Diagnostics and commentary now distinguish UT from UTC more carefully; see theory.html for more information about UT vs UTC. zic has been ported to GCC 8's -Wstringop-truncation option. (Problem reported by Martin Sebor.) Changes to documentation and commentary The zic man page now documents the longstanding behavior that times and years can be out of the usual range, with negative times counting backwards from midnight and with year 0 preceding year 1. (Problem reported by Michael Deckers.) The theory.html file now mentions the POSIX limit of six chars per abbreviation, and lists alphabetic abbreviations used. The files tz-art.htm and tz-link.htm have been renamed to tz-art.html and tz-link.html, respectively, for consistency with other file names and to simplify web server configuration. Release 2017c - 2017-10-20 14:49:34 -0700 Briefly: Northern Cyprus switches from +03 to +02/+03 on 2017-10-29. Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. Changes to future timestamps Northern Cyprus has decided to resume EU rules starting 2017-10-29, thus reinstituting winter time. Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted. (Thanks to Dominic Fok.) Adjust future predictions accordingly. Namibia will switch from +01 with DST to +02 all year on 2017-09-03 at 02:00. This affects UT offsets starting 2018-04-01 at 02:00. (Thanks to Steffen Thorsen.) Sudan will switch from +03 to +02 on 2017-11-01. (Thanks to Ahmed Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. Tonga has likely ended its experiment with DST, and will not adjust its clocks on 2017-11-05. Although Tonga has not announced whether it will continue to observe DST, the IATA is assuming that it will not. (Thanks to David Wade.) Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) Changes to past timestamps Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03. (Thanks to Arthur David Olson.) Detroit did not observe DST in 1967. Use railway time for Asia/Kolkata before 1941, by switching to Madras local time (UT +052110) in 1870, then to IST (UT +0530) in 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. Europe/Dublin's 1946 and 1947 fallback transitions occurred at 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.) Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to American time in 1892, not 1879. (Thanks to Michael Deckers.) Adjust the 1867 transition in Alaska to better reflect the historical record, by changing it to occur on 1867-10-18 at 15:30 Sitka time rather than at the start of 1867-10-17 local time. Although strictly speaking this is accurate only for Sitka, the rest of Alaska's blanks need to be filled in somehow. Fix off-by-one errors in UT offsets for Adak and Nome before 1867. (Thanks to Michael Deckers.) Add 7 s to the UT offset in Asia/Yangon before 1920. Changes to zone names Remove Canada/East-Saskatchewan from the 'backward' file, as it exceeded the 14-character limit and was an unused misnomer anyway. Changes to build procedure To support applications that prefer to read time zone data in text form, two zic input files tzdata.zi and leapseconds are now installed by default. The commands 'zic tzdata.zi' and 'zic -L leapseconds tzdata.zi' can reproduce the tzdata binary files without and with leap seconds, respectively. To prevent these two new files from being installed, use 'make TZDATA_TEXT=', and to suppress leap seconds from the tzdata text installation, use 'make TZDATA_TEXT=tzdata.zi'. 'make BACKWARD=' now suppresses backward-compatibility names like 'US/Pacific' that are defined in the 'backward' and 'pacificnew' files. 'make check' now works on systems that lack a UTF-8 locale, or that lack the nsgmls program. Set UTF8_LOCALE to configure the name of a UTF-8 locale, if you have one. Y2K runtime checks are no longer enabled by default. Add -DDEPRECATE_TWO_DIGIT_YEARS to CFLAGS to enable them, instead of adding -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU to disable them. (New name suggested by Brian Inglis.) The build procedure for zdump now works on AIX 7.1. (Problem reported by Kees Dekker.) Changes to code zic and the reference runtime now reject multiple leap seconds within 28 days of each other, or leap seconds before the Epoch. As a result, support for double leap seconds, which was obsolescent and undocumented, has been removed. Double leap seconds were an error in the C89 standard; they have never existed in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) zic now warns about use of the obsolescent and undocumented -y option, and about use of the obsolescent TYPE field of Rule lines. zic now allows unambiguous abbreviations like "Sa" and "Su" for weekdays; formerly it rejected them due to a bug. Conversely, zic no longer considers non-prefixes to be abbreviations; for example, it no longer accepts "lF" as an abbreviation for "lastFriday". Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". Similarly, zic now accepts the unambiguous abbreviation "L" for "Link" in ordinary context and for "Leap" in leap-second context. Conversely, zic no longer accepts non-prefixes such as "La" as abbreviations for words like "Leap". zic no longer accepts leap second lines in ordinary input, or ordinary lines in leap second input. Formerly, zic sometimes warned about this undocumented usage and handled it incorrectly. The new macro HAVE_TZNAME governs whether the tzname external variable is exported, instead of USG_COMPAT. USG_COMPAT now governs only the external variables "timezone" and "daylight". This change is needed because the three variables are not in the same category: although POSIX requires tzname, it specifies the other two variables as optional. Also, USG_COMPAT is now 1 or 0: if not defined, the code attempts to guess it from other macros. localtime.c and difftime.c no longer require stdio.h, and .c files other than zic.c no longer require sys/wait.h. zdump.c no longer assumes snprintf. (Reported by Jonathan Leffler.) Calculation of time_t extrema works around a bug in GCC 4.8.4 (Reported by Stan Shebs and Joseph Myers.) zic.c no longer mistranslates formats of line numbers in non-English locales. (Problem reported by Benno Schulenberg.) Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) Changes to documentation and commentary The two new files 'theory.html' and 'calendars' contain the contents of the removed file 'Theory'. The goal is to document tzdb theory more accessibly. The zic man page now documents abbreviation rules. tz-link.htm now covers how to apply tzdata changes to clients. (Thanks to Jorge Fábregas for the AIX link.) It also mentions MySQL. The leap-seconds.list URL has been updated to something that is more reliable for tzdb. (Thanks to Tim Parenti and Brian Inglis.) Release 2017b - 2017-03-17 07:30:38 -0700 Briefly: Haiti has resumed DST. Changes to past and future timestamps Haiti resumed observance of DST in 2017. (Thanks to Steffen Thorsen.) Changes to past timestamps Liberia changed from -004430 to +00 on 1972-01-07, not 1972-05-01. Use "MMT" to abbreviate Liberia's time zone before 1972, as "-004430" is one byte over the POSIX limit. (Problem reported by Derick Rethans.) Changes to code The reference localtime implementation now falls back on the current US daylight-saving transition rules rather than the 1987-2006 rules. This fallback occurs only when (1) the TZ environment variable has a value like "AST4ADT" that asks for daylight saving time but does not specify the rules, (2) there is no file by that name, and (3) the TZDEFRULES file cannot be loaded. (Thanks to Tom Lane.) Release 2017a - 2017-02-28 00:05:36 -0800 Briefly: Southern Chile moves from -04/-03 to -03, and Mongolia discontinues DST. Changes to future timestamps Mongolia no longer observes DST. (Thanks to Ganbold Tsagaankhuu.) Chile's Region of Magallanes moves from -04/-03 to -03 year-round. Its clocks diverge from America/Santiago starting 2017-05-13 at 23:00, hiving off a new zone America/Punta_Arenas. Although the Chilean government says this change expires in May 2019, for now assume it's permanent. (Thanks to Juan Correa and Deborah Goldsmith.) This also affects Antarctica/Palmer. Changes to past timestamps Fix many entries for historical timestamps for Europe/Madrid before 1979, to agree with tables compiled by Pere Planesas of the National Astronomical Observatory of Spain. As a side effect, this changes some timestamps for Africa/Ceuta before 1929, which are probably guesswork anyway. (Thanks to Steve Allen and Pierpaolo Bernardi for the heads-ups, and to Michael Deckers for correcting the 1901 transition.) Ecuador observed DST from 1992-11-28 to 1993-02-05. (Thanks to Alois Treindl.) Asia/Atyrau and Asia/Oral were at +03 (not +04) before 1930-06-21. (Thanks to Stepan Golosunov.) Changes to past and future time zone abbreviations Switch to numeric time zone abbreviations for South America, as part of the ongoing project of removing invented abbreviations. This avoids the need to invent an abbreviation for the new Chilean new zone. Similarly, switch from invented to numeric time zone abbreviations for Afghanistan, American Samoa, the Azores, Bangladesh, Bhutan, the British Indian Ocean Territory, Brunei, Cape Verde, Chatham Is, Christmas I, Cocos (Keeling) Is, Cook Is, Dubai, East Timor, Eucla, Fiji, French Polynesia, Greenland, Indochina, Iran, Iraq, Kiribati, Lord Howe, Macquarie, Malaysia, the Maldives, Marshall Is, Mauritius, Micronesia, Mongolia, Myanmar, Nauru, Nepal, New Caledonia, Niue, Norfolk I, Palau, Papua New Guinea, the Philippines, Pitcairn, Qatar, Réunion, St Pierre & Miquelon, Samoa, Saudi Arabia, Seychelles, Singapore, Solomon Is, Tokelau, Tuvalu, Wake, Vanuatu, Wallis & Futuna, and Xinjiang; for 20-minute daylight saving time in Ghana before 1943; for half-hour daylight saving time in Belize before 1944 and in the Dominican Republic before 1975; and for Canary Islands before 1946, for Guinea-Bissau before 1975, for Iceland before 1969, for Indian Summer Time before 1942, for Indonesia before around 1964, for Kenya before 1960, for Liberia before 1973, for Madeira before 1967, for Namibia before 1943, for the Netherlands in 1937-9, for Pakistan before 1971, for Western Sahara before 1977, and for Zaporozhye in 1880-1924. For Alaska time from 1900 through 1967, instead of "CAT" use the abbreviation "AST", the abbreviation commonly used at the time (Atlantic Standard Time had not been standardized yet). Use "AWT" and "APT" instead of the invented abbreviations "CAWT" and "CAPT". Use "CST" and "CDT" instead of invented abbreviations for Macau before 1999 and Taiwan before 1938, and use "JST" instead of the invented abbreviation "JCST" for Japan and Korea before 1938. Change to database entry category Move the Pacific/Johnston link from 'australasia' to 'backward', since Johnston is now uninhabited. Changes to code zic no longer mishandles some transitions in January 2038 when it attempts to work around Qt bug 53071. This fixes a bug affecting Pacific/Tongatapu that was introduced in zic 2016e. localtime.c now contains a workaround, useful when loading a file generated by a buggy zic. (Problem and localtime.c fix reported by Bradley White.) zdump -i now outputs non-hour numeric time zone abbreviations without a colon, e.g., "+0530" rather than "+05:30". This agrees with zic %z and with common practice, and simplifies auditing of zdump output. zdump is now buildable again with -DUSE_LTZ=0. (Problem reported by Joseph Myers.) zdump.c now always includes private.h, to avoid code duplication with private.h. (Problem reported by Kees Dekker.) localtime.c no longer mishandles early or late timestamps when TZ is set to a POSIX-style string that specifies DST. (Problem reported by Kees Dekker.) date and strftime now cause %z to generate "-0000" instead of "+0000" when the UT offset is zero and the time zone abbreviation begins with "-". Changes to documentation and commentary The 'Theory' file now better documents choice of historical time zone abbreviations. (Problems reported by Michael Deckers.) tz-link.htm now covers leap smearing, which is popular in clouds. Release 2016j - 2016-11-22 23:17:13 -0800 Briefly: Saratov, Russia moves from +03 to +04 on 2016-12-04. Changes to future timestamps Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. This hives off a new zone Europe/Saratov from Europe/Volgograd. (Thanks to Yuri Konotopov and Stepan Golosunov.) Changes to past timestamps The new zone Asia/Atyrau for Atyraū Region, Kazakhstan, is like Asia/Aqtau except it switched from +05/+06 to +04/+05 in spring 1999, not fall 1994. (Thanks to Stepan Golosunov.) Changes to past time zone abbreviations Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote summer time before 1948. The old use of "EET" was a typo. Changes to code zic no longer mishandles file systems that lack hard links, fixing bugs introduced in 2016g. (Problems reported by Tom Lane.) Also, when the destination already contains symbolic links, zic should now work better on systems where the 'link' system call does not follow symbolic links. Changes to documentation and commentary tz-link.htm now documents the relationship between release version numbers and development-repository commit tags. (Suggested by Paul Koning.) The 'Theory' file now documents UT. iso3166.tab now accents "Curaçao", and commentary now mentions the names "Cabo Verde" and "Czechia". (Thanks to Jiří Boháč.) Release 2016i - 2016-11-01 23:19:52 -0700 Briefly: Cyprus split into two time zones on 2016-10-30, and Tonga reintroduces DST on 2016-11-06. Changes to future timestamps Pacific/Tongatapu begins DST on 2016-11-06 at 02:00, ending on 2017-01-15 at 03:00. Assume future observances in Tonga will be from the first Sunday in November through the third Sunday in January, like Fiji. (Thanks to Pulu ʻAnau.) Switch to numeric time zone abbreviations for this zone. Changes to past and future timestamps Northern Cyprus is now +03 year round, causing a split in Cyprus time zones starting 2016-10-30 at 04:00. This creates a zone Asia/Famagusta. (Thanks to Even Scharning and Matt Johnson.) Antarctica/Casey switched from +08 to +11 on 2016-10-22. (Thanks to Steffen Thorsen.) Changes to past timestamps Several corrections were made for pre-1975 timestamps in Italy. These affect Europe/Malta, Europe/Rome, Europe/San_Marino, and Europe/Vatican. First, the 1893-11-01 00:00 transition in Italy used the new UT offset (+01), not the old (+00:49:56). (Thanks to Michael Deckers.) Second, rules for daylight saving in Italy were changed to agree with Italy's National Institute of Metrological Research (INRiM) except for 1944, as follows (thanks to Pierpaolo Bernardi, Brian Inglis, and Michael Deckers): The 1916-06-03 transition was at 24:00, not 00:00. The 1916-10-01, 1919-10-05, and 1920-09-19 transitions were at 00:00, not 01:00. The 1917-09-30 and 1918-10-06 transitions were at 24:00, not 01:00. The 1944-09-17 transition was at 03:00, not 01:00. This particular change is taken from Italian law as INRiM's table, (which says 02:00) appears to have a typo here. Also, keep the 1944-04-03 transition for Europe/Rome, as Rome was controlled by Germany then. The 1967-1970 and 1972-1974 fallback transitions were at 01:00, not 00:00. Changes to code The code should now be buildable on AmigaOS merely by setting the appropriate Makefile variables. (From a patch by Carsten Larsen.) Release 2016h - 2016-10-19 23:17:57 -0700 Changes to future timestamps Asia/Gaza and Asia/Hebron end DST on 2016-10-29 at 01:00, not 2016-10-21 at 00:00. (Thanks to Sharef Mustafa.) Predict that future fall transitions will be on the last Saturday of October at 01:00, which is consistent with predicted spring transitions on the last Saturday of March. (Thanks to Tim Parenti.) Changes to past timestamps In Turkey, transitions in 1986-1990 were at 01:00 standard time not at 02:00, and the spring 1994 transition was on March 20, not March 27. (Thanks to Kıvanç Yazan.) Changes to past and future time zone abbreviations Asia/Colombo now uses numeric time zone abbreviations like "+0530" instead of alphabetic ones like "IST" and "LKT". Various English-language sources use "IST", "LKT" and "SLST", with no working consensus. (Usage of "SLST" mentioned by Sadika Sumanapala.) Changes to code zic no longer mishandles relativizing file names when creating symbolic links like /etc/localtime, when these symbolic links are outside the usual directory hierarchy. This fixes a bug introduced in 2016g. (Problem reported by Andreas Stieger.) Changes to build procedure New rules 'traditional_tarballs' and 'traditional_signatures' for building just the traditional-format distribution. (Requested by Deborah Goldsmith.) The file 'version' is now put into the tzdata tarball too. (Requested by Howard Hinnant.) Changes to documentation and commentary The 'Theory' file now has a section on interface stability. (Requested by Paul Koning.) It also mentions features like tm_zone and localtime_rz that have long been supported by the reference code. tz-link.htm has improved coverage of time zone boundaries suitable for geolocation. (Thanks to heads-ups from Evan Siroky and Matt Johnson.) The US commentary now mentions Allen and the "day of two noons". The Fiji commentary mentions the government's 2016-10-03 press release. (Thanks to Raymond Kumar.) Release 2016g - 2016-09-13 08:56:38 -0700 Changes to future timestamps Turkey switched from EET/EEST (+02/+03) to permanent +03, effective 2016-09-07. (Thanks to Burak AYDIN.) Use "+03" rather than an invented abbreviation for the new time. New leap second 2016-12-31 23:59:60 UTC as per IERS Bulletin C 52. (Thanks to Tim Parenti.) Changes to past timestamps For America/Los_Angeles, spring-forward transition times have been corrected from 02:00 to 02:01 in 1948, and from 02:00 to 01:00 in 1950-1966. For zones using Soviet time on 1919-07-01, transitions to UT-based time were at 00:00 UT, not at 02:00 local time. The affected zones are Europe/Kirov, Europe/Moscow, Europe/Samara, and Europe/Ulyanovsk. (Thanks to Alexander Belopolsky.) Changes to past and future time zone abbreviations The Factory zone now uses the time zone abbreviation -00 instead of a long English-language string, as -00 is now the normal way to represent an undefined time zone. Several zones in Antarctica and the former Soviet Union, along with zones intended for ships at sea that cannot use POSIX TZ strings, now use numeric time zone abbreviations instead of invented or obsolete alphanumeric abbreviations. The affected zones are Antarctica/Casey, Antarctica/Davis, Antarctica/DumontDUrville, Antarctica/Mawson, Antarctica/Rothera, Antarctica/Syowa, Antarctica/Troll, Antarctica/Vostok, Asia/Anadyr, Asia/Ashgabat, Asia/Baku, Asia/Bishkek, Asia/Chita, Asia/Dushanbe, Asia/Irkutsk, Asia/Kamchatka, Asia/Khandyga, Asia/Krasnoyarsk, Asia/Magadan, Asia/Omsk, Asia/Sakhalin, Asia/Samarkand, Asia/Srednekolymsk, Asia/Tashkent, Asia/Tbilisi, Asia/Ust-Nera, Asia/Vladivostok, Asia/Yakutsk, Asia/Yekaterinburg, Asia/Yerevan, Etc/GMT-14, Etc/GMT-13, Etc/GMT-12, Etc/GMT-11, Etc/GMT-10, Etc/GMT-9, Etc/GMT-8, Etc/GMT-7, Etc/GMT-6, Etc/GMT-5, Etc/GMT-4, Etc/GMT-3, Etc/GMT-2, Etc/GMT-1, Etc/GMT+1, Etc/GMT+2, Etc/GMT+3, Etc/GMT+4, Etc/GMT+5, Etc/GMT+6, Etc/GMT+7, Etc/GMT+8, Etc/GMT+9, Etc/GMT+10, Etc/GMT+11, Etc/GMT+12, Europe/Kaliningrad, Europe/Minsk, Europe/Samara, Europe/Volgograd, and Indian/Kerguelen. For Europe/Moscow the invented abbreviation MSM was replaced by +05, whereas MSK and MSD were kept as they are not our invention and are widely used. Changes to zone names Rename Asia/Rangoon to Asia/Yangon, with a backward compatibility link. (Thanks to David Massoud.) Changes to code zic no longer generates binary files containing POSIX TZ-like strings that disagree with the local time type after the last explicit transition in the data. This fixes a bug with Africa/Casablanca and Africa/El_Aaiun in some year-2037 timestamps on the reference platform. (Thanks to Alexander Belopolsky for reporting the bug and suggesting a way forward.) If the installed localtime and/or posixrules files are symbolic links, zic now keeps them symbolic links when updating them, for compatibility with platforms like OpenSUSE where other programs configure these files as symlinks. zic now avoids hard linking to symbolic links, avoids some unnecessary mkdir and stat system calls, and uses shorter file names internally. zdump has a new -i option to generate transitions in a more-compact but still human-readable format. This option is experimental, and the output format may change in future versions. (Thanks to Jon Skeet for suggesting that an option was needed, and thanks to Tim Parenti and Chris Rovick for further comments.) Changes to build procedure An experimental distribution format is available, in addition to the traditional format which will continue to be distributed. The new format is a tarball tzdb-VERSION.tar.lz with signature file tzdb-VERSION.tar.lz.asc. It unpacks to a top-level directory tzdb-VERSION containing the code and data of the traditional two-tarball format, along with extra data that may be useful. (Thanks to Antonio Diaz Diaz, Oscar van Vlijmen, and many others for comments about the experimental format.) The release version number is now more accurate in the usual case where releases are built from a Git repository. For example, if 23 commits and some working-file changes have been made since release 2016g, the version number is now something like '2016g-23-g50556e3-dirty' instead of the misleading '2016g'. Tagged releases use the same version number format as before, e.g., '2016g'. To support the more-accurate version number, its specification has moved from a line in the Makefile to a new source file 'version'. The experimental distribution contains a file to2050.tzs that contains what should be the output of 'zdump -i -c 2050' on primary zones. If this file is available, 'make check' now checks that zdump generates this output. 'make check_web' now works on Fedora-like distributions. Changes to documentation and commentary tzfile.5 now documents the new restriction on POSIX TZ-like strings that is now implemented by zic. Comments now cite URLs for some 1917-1921 Russian DST decrees. (Thanks to Alexander Belopolsky.) tz-link.htm mentions JuliaTime (thanks to Curtis Vogt) and Time4J (thanks to Meno Hochschild) and ThreeTen-Extra, and its description of Java 8 has been brought up to date (thanks to Stephen Colebourne). Its description of local time on Mars has been updated to match current practice, and URLs have been updated and some obsolete ones removed. Release 2016f - 2016-07-05 16:26:51 +0200 Changes affecting future timestamps The Egyptian government changed its mind on short notice, and Africa/Cairo will not introduce DST starting 2016-07-07 after all. (Thanks to Mina Samuel.) Asia/Novosibirsk switches from +06 to +07 on 2016-07-24 at 02:00. (Thanks to Stepan Golosunov.) Changes to past and future timestamps Asia/Novokuznetsk and Asia/Novosibirsk now use numeric time zone abbreviations instead of invented ones. Changes affecting past timestamps Europe/Minsk's 1992-03-29 spring-forward transition was at 02:00 not 00:00. (Thanks to Stepan Golosunov.) Release 2016e - 2016-06-14 08:46:16 -0700 Changes affecting future timestamps Africa/Cairo observes DST in 2016 from July 7 to the end of October. Guess October 27 and 24:00 transitions. (Thanks to Steffen Thorsen.) For future years, guess April's last Thursday to October's last Thursday except for Ramadan. Changes affecting past timestamps Locations while uninhabited now use '-00', not 'zzz', as a placeholder time zone abbreviation. This is inspired by Internet RFC 3339 and is more consistent with numeric time zone abbreviations already used elsewhere. The change affects several arctic and antarctic locations, e.g., America/Cambridge_Bay before 1920 and Antarctica/Troll before 2005. Asia/Baku's 1992-09-27 transition from +04 (DST) to +04 (non-DST) was at 03:00, not 23:00 the previous day. (Thanks to Michael Deckers.) Changes to code zic now outputs a dummy transition at time 2**31 - 1 in zones whose POSIX-style TZ strings contain a '<'. This mostly works around Qt bug 53071 . (Thanks to Zhanibek Adilbekov for reporting the Qt bug.) Changes affecting documentation and commentary tz-link.htm says why governments should give plenty of notice for time zone or DST changes, and refers to Matt Johnson's blog post. tz-link.htm mentions Tzdata for Elixir. (Thanks to Matt Johnson.) Release 2016d - 2016-04-17 22:50:29 -0700 Changes affecting future timestamps America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30. (Thanks to Alexander Krivenyshev for the heads-up.) Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00. (Thanks to Alexander Krivenyshev and Matt Johnson.) New zone Asia/Tomsk, split off from Asia/Novosibirsk. It covers Tomsk Oblast, Russia, which switches from +06 to +07 on 2016-05-29 at 02:00. (Thanks to Stepan Golosunov.) Changes affecting past timestamps New zone Europe/Kirov, split off from Europe/Volgograd. It covers Kirov Oblast, Russia, which switched from +04/+05 to +03/+04 on 1989-03-26 at 02:00, roughly a year after Europe/Volgograd made the same change. (Thanks to Stepan Golosunov.) Russia and nearby locations had daylight-saving transitions on 1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on 1992-03-28 at 23:00 and 1992-09-26 at 23:00. (Thanks to Stepan Golosunov.) Many corrections to historical time in Kazakhstan from 1991 through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's invented time zone abbreviations with numeric abbreviations. Changes to commentary Mention Internet RFCs 7808 (TZDIST) and 7809 (CalDAV time zone references). Release 2016c - 2016-03-23 00:51:27 -0700 Changes affecting future timestamps Azerbaijan no longer observes DST. (Thanks to Steffen Thorsen.) Chile reverts from permanent to seasonal DST. (Thanks to Juan Correa for the heads-up, and to Tim Parenti for corrections.) Guess that future transitions are August's and May's second Saturdays at 24:00 mainland time. Also, call the period from 2014-09-07 through 2016-05-14 daylight saving time instead of standard time, as that seems more appropriate now. Changes affecting past timestamps Europe/Kaliningrad and Europe/Vilnius changed from +03/+04 to +02/+03 on 1989-03-26, not 1991-03-31. Europe/Volgograd changed from +04/+05 to +03/+04 on 1988-03-27, not 1989-03-26. (Thanks to Stepan Golosunov.) Changes to commentary Several updates and URLs for historical and proposed Russian changes. (Thanks to Stepan Golosunov, Matt Johnson, and Alexander Krivenyshev.) Release 2016b - 2016-03-12 17:30:14 -0800 Compatibility note Starting with release 2016b, some data entries cause zic implementations derived from tz releases 2005j through 2015e to issue warnings like "time zone abbreviation differs from POSIX standard (+03)". These warnings should not otherwise affect zic's output and can safely be ignored on today's platforms, as the warnings refer to a restriction in POSIX.1-1988 that was removed in POSIX.1-2001. One way to suppress the warnings is to upgrade to zic derived from tz releases 2015f and later. Changes affecting future timestamps New zones Europe/Astrakhan and Europe/Ulyanovsk for Astrakhan and Ulyanovsk Oblasts, Russia, both of which will switch from +03 to +04 on 2016-03-27 at 02:00 local time. They need distinct zones since their post-1970 histories disagree. New zone Asia/Barnaul for Altai Krai and Altai Republic, Russia, which will switch from +06 to +07 on the same date and local time. The Astrakhan change is already official; the others have passed the first reading in the State Duma and are extremely likely. Also, Asia/Sakhalin moves from +10 to +11 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev for the heads-up, and to Matt Johnson and Stepan Golosunov for followup.) As a trial of a new system that needs less information to be made up, the new zones use numeric time zone abbreviations like "+04" instead of invented abbreviations like "ASTT". Haiti will not observe DST in 2016. (Thanks to Jean Antoine via Steffen Thorsen.) Palestine's spring-forward transition on 2016-03-26 is at 01:00, not 00:00. (Thanks to Hannah Kreitem.) Guess future transitions will be March's last Saturday at 01:00, not March's last Friday at 24:00. Changes affecting past timestamps Europe/Chisinau observed DST during 1990, and switched from +04 to +03 at 1990-05-06 02:00, instead of switching from +03 to +02. (Thanks to Stepan Golosunov.) 1991 abbreviations in Europe/Samara should be SAMT/SAMST, not KUYT/KUYST. (Thanks to Stepan Golosunov.) Changes to code tzselect's diagnostics and checking, and checktab.awk's checking, have been improved. (Thanks to J William Piggott.) tzcode now builds under MinGW. (Thanks to Ian Abbott and Esben Haabendal.) tzselect now tests Julian-date TZ settings more accurately. (Thanks to J William Piggott.) Changes to commentary Comments in zone tables have been improved. (Thanks to J William Piggott.) tzselect again limits its menu comments so that menus fit on a 24×80 alphanumeric display. A new web page tz-how-to.html. (Thanks to Bill Seymour.) In the Theory file, the description of possible time zone abbreviations in tzdata has been cleaned up, as the old description was unclear and inconsistent. (Thanks to Alain Mouette for reporting the problem.) Release 2016a - 2016-01-26 23:28:02 -0800 Changes affecting future timestamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future timestamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past timestamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) Changes affecting build procedure An installer can now combine leap seconds with use of the backzone file, e.g., with 'make PACKRATDATA=backzone REDO=posix_right zones'. The old 'make posix_packrat' rule is now marked as obsolescent. (Thanks to Ian Abbott for an initial implementation.) Changes affecting documentation and commentary A new file LICENSE makes it easier to see that the code and data are mostly public-domain. (Thanks to James Knight.) The three non-public-domain files now use the current (3-clause) BSD license instead of older versions of that license. tz-link.htm mentions the BDE library (thanks to Andrew Paprocki), CCTZ (thanks to Tim Parenti), TimeJones.com, and has a new section on editing tz source files (with a mention of Sublime zoneinfo, thanks to Gilmore Davidson). The Theory and asia files now mention the 2015 book "The Global Transformation of Time, 1870-1950", and cite a couple of reviews. The America/Chicago entry now documents the informal use of US central time in Fort Pierre, South Dakota. (Thanks to Rick McDermid, Matt Johnson, and Steve Jones.) Release 2015g - 2015-10-01 00:39:51 -0700 Changes affecting future timestamps Turkey's 2015 fall-back transition is scheduled for Nov. 8, not Oct. 25. (Thanks to Fatih.) Norfolk moves from +1130 to +1100 on 2015-10-04 at 02:00 local time. (Thanks to Alexander Krivenyshev.) Fiji's 2016 fall-back transition is scheduled for January 17, not 24. (Thanks to Ken Rylander.) Fort Nelson, British Columbia will not fall back on 2015-11-01. It has effectively been on MST (-0700) since it advanced its clocks on 2015-03-08. New zone America/Fort_Nelson. (Thanks to Matt Johnson.) Changes affecting past timestamps Norfolk observed DST from 1974-10-27 02:00 to 1975-03-02 02:00. Changes affecting code localtime no longer mishandles America/Anchorage after 2037. (Thanks to Bradley White for reporting the bug.) On hosts with signed 32-bit time_t, localtime no longer mishandles Pacific/Fiji after 2038-01-16 14:00 UTC. The localtime module allows the variables 'timezone', 'daylight', and 'altzone' to be in common storage shared with other modules, and declares them in case the system does not. (Problems reported by Kees Dekker.) On platforms with tm_zone, strftime.c now assumes it is not NULL. This simplifies the code and is consistent with zdump.c. (Problem reported by Christos Zoulas.) Changes affecting documentation The tzfile man page now documents that transition times denote the starts (not the ends) of the corresponding time periods. (Ambiguity reported by Bill Seymour.) Release 2015f - 2015-08-10 18:06:56 -0700 Changes affecting future timestamps North Korea switches to +0830 on 2015-08-15. (Thanks to Steffen Thorsen.) The abbreviation remains "KST". (Thanks to Robert Elz.) Uruguay no longer observes DST. (Thanks to Steffen Thorsen and Pablo Camargo.) Changes affecting past and future timestamps Moldova starts and ends DST at 00:00 UTC, not at 01:00 UTC. (Thanks to Roman Tudos.) Changes affecting data format and code zic's '-y YEARISTYPE' option is no longer documented. The TYPE field of a Rule line should now be '-'; the old values 'even', 'odd', 'uspres', 'nonpres', 'nonuspres' were already undocumented. Although the implementation has not changed, these features do not work in the default installation, they are not used in the data, and they are now considered obsolescent. zic now checks that two rules don't take effect at the same time. (Thanks to Jon Skeet and Arthur David Olson.) Constraints on simultaneity are now documented. The two characters '%z' in a zone format now stand for the UT offset, e.g., '-07' for seven hours behind UT and '+0530' for five hours and thirty minutes ahead. This better supports time zone abbreviations conforming to POSIX.1-2001 and later. Changes affecting installed data files Comments for America/Halifax and America/Glace_Bay have been improved. (Thanks to Brian Inglis.) Data entries have been simplified for Atlantic/Canary, Europe/Simferopol, Europe/Sofia, and Europe/Tallinn. This yields slightly smaller installed data files for Europe/Simferopol and Europe/Tallinn. It does not affect timestamps. (Thanks to Howard Hinnant.) Changes affecting code zdump and zic no longer warn about valid time zone abbreviations like '-05'. Some Visual Studio 2013 warnings have been suppressed. (Thanks to Kees Dekker.) 'date' no longer sets the time of day and its -a, -d, -n and -t options have been removed. Long obsolescent, the implementation of these features had porting problems. Builders no longer need to configure HAVE_ADJTIME, HAVE_SETTIMEOFDAY, or HAVE_UTMPX_H. (Thanks to Kees Dekker for pointing out the problem.) Changes affecting documentation The Theory file mentions naming issues earlier, as these seem to be poorly publicized (thanks to Gilmore Davidson for reporting the problem). tz-link.htm mentions Time Zone Database Parser (thanks to Howard Hinnant). Mention that Herbert Samuel introduced the term "Summer Time". Release 2015e - 2015-06-13 10:56:02 -0700 Changes affecting future timestamps Morocco will suspend DST from 2015-06-14 03:00 through 2015-07-19 02:00, not 06-13 and 07-18 as we had guessed. (Thanks to Milamber.) Assume Cayman Islands will observe DST starting next year, using US rules. Although it isn't guaranteed, it is the most likely. Changes affecting data format The file 'iso3166.tab' now uses UTF-8, so that its entries can better spell the names of Åland Islands, Côte d'Ivoire, and Réunion. Changes affecting code When displaying data, tzselect converts it to the current locale's encoding if the iconv command works. (Problem reported by random832.) tzselect no longer mishandles Dominica, fixing a bug introduced in Release 2014f. (Problem reported by Owen Leibman.) zic -l no longer fails when compiled with -DTZDEFAULT=\"/etc/localtime\". This fixes a bug introduced in Release 2014f. (Problem reported by Leonardo Chiquitto.) Release 2015d - 2015-04-24 08:09:46 -0700 Changes affecting future timestamps Egypt will not observe DST in 2015 and will consider canceling it permanently. For now, assume no DST indefinitely. (Thanks to Ahmed Nazmy and Tim Parenti.) Changes affecting past timestamps America/Whitehorse switched from UT -09 to -08 on 1967-05-28, not 1966-07-01. Also, Yukon's time zone history is documented better. (Thanks to Brian Inglis and Dennis Ferguson.) Change affecting past and future time zone abbreviations The abbreviations for Hawaii-Aleutian standard and daylight times have been changed from HAST/HADT to HST/HDT, as per US Government Printing Office style. This affects only America/Adak since 1983, as America/Honolulu was already using the new style. Changes affecting code zic has some minor performance improvements. Release 2015c - 2015-04-11 08:55:55 -0700 Changes affecting future timestamps Egypt's spring-forward transition is at 24:00 on April's last Thursday, not 00:00 on April's last Friday. 2015's transition will therefore be on Thursday, April 30 at 24:00, not Friday, April 24 at 00:00. Similar fixes apply to 2026, 2037, 2043, etc. (Thanks to Steffen Thorsen.) Changes affecting past timestamps The following changes affect some pre-1991 Chile-related timestamps in America/Santiago, Antarctica/Palmer, and Pacific/Easter. The 1910 transition was January 10, not January 1. The 1918 transition was September 10, not September 1. The UT -04 time observed from 1932 to 1942 is now considered to be standard time, not year-round DST. Santiago observed DST (UT -03) from 1946-07-15 through 1946-08-31, then reverted to standard time, then switched to -05 on 1947-04-01. Assume transitions before 1968 were at 00:00, since we have no data saying otherwise. The spring 1988 transition was 1988-10-09, not 1988-10-02. The fall 1990 transition was 1990-03-11, not 1990-03-18. Assume no UT offset change for Pacific/Easter on 1890-01-01, and omit all transitions on Pacific/Easter from 1942 through 1946 since we have no data suggesting that they existed. One more zone has been turned into a link, as it differed from an existing zone only for older timestamps. As usual, this change affects UT offsets in pre-1970 timestamps only. The zone's old contents have been moved to the 'backzone' file. The affected zone is America/Montreal. Changes affecting commentary Mention the TZUpdater tool. Mention "The Time Now". (Thanks to Brandon Ramsey.) Release 2015b - 2015-03-19 23:28:11 -0700 Changes affecting future timestamps Mongolia will start observing DST again this year, from the last Saturday in March at 02:00 to the last Saturday in September at 00:00. (Thanks to Ganbold Tsagaankhuu.) Palestine will start DST on March 28, not March 27. Also, correct the fall 2014 transition from September 26 to October 24. Adjust future predictions accordingly. (Thanks to Steffen Thorsen.) Changes affecting past timestamps The 1982 zone shift in Pacific/Easter has been corrected, fixing a 2015a regression. (Thanks to Stuart Bishop for reporting the problem.) Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: America/Antigua, America/Cayman, Pacific/Midway, and Pacific/Saipan. Changes affecting time zone abbreviations Correct the 1992-2010 DST abbreviation in Volgograd from "MSK" to "MSD". (Thanks to Hank W.) Changes affecting code Fix integer overflow bug in reference 'mktime' implementation. (Problem reported by Jörg Richter.) Allow -Dtime_tz=time_t compilations, and allow -Dtime_tz=... libraries to be used in the same executable as standard-library time_t functions. (Problems reported by Bradley White.) Changes affecting commentary Cite the recent Mexican decree changing Quintana Roo's time zone. (Thanks to Carlos Raúl Perasso.) Likewise for the recent Chilean decree. (Thanks to Eduardo Romero Urra.) Update info about Mars time. Release 2015a - 2015-01-29 22:35:20 -0800 Changes affecting future timestamps The Mexican state of Quintana Roo, represented by America/Cancun, will shift from Central Time with DST to Eastern Time without DST on 2015-02-01 at 02:00. (Thanks to Steffen Thorsen and Gwillim Law.) Chile will not change clocks in April or thereafter; its new standard time will be its old daylight saving time. This affects America/Santiago, Pacific/Easter, and Antarctica/Palmer. (Thanks to Juan Correa.) New leap second 2015-06-30 23:59:60 UTC as per IERS Bulletin C 49. (Thanks to Tim Parenti.) Changes affecting past timestamps Iceland observed DST in 1919 and 1921, and its 1939 fallback transition was Oct. 29, not Nov. 29. Remove incorrect data from Shanks about time in Iceland between 1837 and 1908. Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Asia/Aden, Asia/Bahrain, Asia/Kuwait, and Asia/Muscat. Changes affecting code tzalloc now scrubs time zone abbreviations compatibly with the way that tzset always has, by replacing invalid bytes with '_' and by shortening too-long abbreviations. tzselect ports to POSIX awk implementations, no longer mishandles POSIX TZ settings when GNU awk is used, and reports POSIX TZ settings to the user. (Thanks to Stefan Kuhn.) Changes affecting build procedure 'make check' now checks for links to links in the data. One such link (for Africa/Asmera) has been fixed. (Thanks to Stephen Colebourne for pointing out the problem.) Changes affecting commentary The leapseconds file commentary now mentions the expiration date. (Problem reported by Martin Burnicki.) Update Mexican Library of Congress URL. Release 2014j - 2014-11-10 17:37:11 -0800 Changes affecting current and future timestamps Turks & Caicos' switch from US eastern time to UT -04 year-round did not occur on 2014-11-02 at 02:00. It's currently scheduled for 2015-11-01 at 02:00. (Thanks to Chris Walton.) Changes affecting past timestamps Many pre-1989 timestamps have been corrected for Asia/Seoul and Asia/Pyongyang, based on sources for the Korean-language Wikipedia entry for time in Korea. (Thanks to Sanghyuk Jung.) Also, no longer guess that Pyongyang mimicked Seoul time after World War II, as this is politically implausible. Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Addis_Ababa, Africa/Asmara, Africa/Dar_es_Salaam, Africa/Djibouti, Africa/Kampala, Africa/Mogadishu, Indian/Antananarivo, Indian/Comoro, and Indian/Mayotte. Changes affecting commentary The commentary is less enthusiastic about Shanks as a source, and is more careful to distinguish UT from UTC. Release 2014i - 2014-10-21 22:04:57 -0700 Changes affecting future timestamps Pacific/Fiji will observe DST from 2014-11-02 02:00 to 2015-01-18 03:00. (Thanks to Ken Rylander for the heads-up.) Guess that future years will use a similar pattern. A new Zone Pacific/Bougainville, for the part of Papua New Guinea that plans to switch from UT +10 to +11 on 2014-12-28 at 02:00. (Thanks to Kiley Walbom for the heads-up.) Changes affecting time zone abbreviations Since Belarus is not changing its clocks even though Moscow is, the time zone abbreviation in Europe/Minsk is changing from FET to its more-traditional value MSK on 2014-10-26 at 01:00. (Thanks to Alexander Bokovoy for the heads-up about Belarus.) The new abbreviation IDT stands for the pre-1976 use of UT +08 in Indochina, to distinguish it better from ICT (+07). Changes affecting past timestamps Many timestamps have been corrected for Asia/Ho_Chi_Minh before 1976 (thanks to Trần Ngọc Quân for an indirect pointer to Trần Tiến Bình's authoritative book). Asia/Ho_Chi_Minh has been added to zone1970.tab, to give tzselect users in Vietnam two choices, since north and south Vietnam disagreed after our 1970 cutoff. Asia/Phnom_Penh and Asia/Vientiane have been turned into links, as they differed from existing zones only for older timestamps. As usual, these changes affect pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. Changes affecting code The time-related library functions now set errno on failure, and some crashes in the new tzalloc-related library functions have been fixed. (Thanks to Christos Zoulas for reporting most of these problems and for suggesting fixes.) If USG_COMPAT is defined and the requested timestamp is standard time, the tz library's localtime and mktime functions now set the extern variable timezone to a value appropriate for that timestamp; and similarly for ALTZONE, daylight saving time, and the altzone variable. This change is a companion to the tzname change in 2014h, and is designed to make timezone and altzone more compatible with tzname. The tz library's functions now set errno to EOVERFLOW if they fail because the result cannot be represented. ctime and ctime_r now return NULL and set errno when a timestamp is out of range, rather than having undefined behavior. Some bugs associated with the new 2014g functions have been fixed. This includes a bug that largely incapacitated the new functions time2posix_z and posix2time_z. (Thanks to Christos Zoulas.) It also includes some uses of uninitialized variables after tzalloc. The new code uses the standard type 'ssize_t', which the Makefile now gives porting advice about. Changes affecting commentary Updated URLs for NRC Canada (thanks to Matt Johnson and Brian Inglis). Release 2014h - 2014-09-25 18:59:03 -0700 Changes affecting past timestamps America/Jamaica's 1974 spring-forward transition was Jan. 6, not Apr. 28. Shanks says Asia/Novokuznetsk switched from LMT (not "NMT") on 1924-05-01, not 1920-01-06. The old entry was based on a misinterpretation of Shanks. Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Blantyre, Africa/Bujumbura, Africa/Gaborone, Africa/Harare, Africa/Kigali, Africa/Lubumbashi, Africa/Lusaka, Africa/Maseru, and Africa/Mbabane. Changes affecting code zdump -V and -v now output gmtoff= values on all platforms, not merely on platforms defining TM_GMTOFF. The tz library's localtime and mktime functions now set tzname to a value appropriate for the requested timestamp, and zdump now uses this on platforms not defining TM_ZONE, fixing a 2014g regression. (Thanks to Tim Parenti for reporting the problem.) The tz library no longer sets tzname if localtime or mktime fails. zdump -c no longer mishandles transitions near year boundaries. (Thanks to Tim Parenti for reporting the problem.) An access to uninitialized data has been fixed. (Thanks to Jörg Richter for reporting the problem.) When THREAD_SAFE is defined, the code ports to the C11 memory model. A memory leak has been fixed if ALL_STATE and THREAD_SAFE are defined and two threads race to initialize data used by gmtime-like functions. (Thanks to Andy Heninger for reporting the problems.) Changes affecting build procedure 'make check' now checks better for properly-sorted data. Changes affecting documentation and commentary zdump's gmtoff=N output is now documented, and its isdst=D output is now documented to possibly output D values other than 0 or 1. zdump -c's treatment of years is now documented to use the Gregorian calendar and Universal Time without leap seconds, and its behavior at cutoff boundaries is now documented better. (Thanks to Arthur David Olson and Tim Parenti for reporting the problems.) Programs are now documented to use the proleptic Gregorian calendar. (Thanks to Alan Barrett for the suggestion.) Fractional-second GMT offsets have been documented for civil time in 19th-century Chennai, Jakarta, and New York. Release 2014g - 2014-08-28 12:31:23 -0700 Changes affecting future timestamps Turks & Caicos is switching from US eastern time to UT -04 year-round, modeled as a switch on 2014-11-02 at 02:00. [As noted in 2014j, this switch was later delayed.] Changes affecting past timestamps Time in Russia or the USSR before 1926 or so has been corrected by a few seconds in the following zones: Asia/Irkutsk, Asia/Krasnoyarsk, Asia/Omsk, Asia/Samarkand, Asia/Tbilisi, Asia/Vladivostok, Asia/Yakutsk, Europe/Riga, Europe/Samara. For Asia/Yekaterinburg the correction is a few minutes. (Thanks to Vladimir Karpinsky.) The Portuguese decree of 1911-05-26 took effect on 1912-01-01. This affects 1911 timestamps in Africa/Bissau, Africa/Luanda, Atlantic/Azores, and Atlantic/Madeira. Also, Lisbon's pre-1912 GMT offset was -0:36:45 (rounded from -0:36:44.68), not -0:36:32. (Thanks to Stephen Colebourne for pointing to the decree.) Asia/Dhaka ended DST on 2009-12-31 at 24:00, not 23:59. A new file 'backzone' contains data which may appeal to connoisseurs of old timestamps, although it is out of scope for the tz database, is often poorly sourced, and contains some data that is known to be incorrect. The new file is not recommended for ordinary use and its entries are not installed by default. (Thanks to Lester Caine for the high-quality Jersey, Guernsey, and Isle of Man entries.) Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Bangui, Africa/Brazzaville, Africa/Douala, Africa/Kinshasa, Africa/Libreville, Africa/Luanda, Africa/Malabo, Africa/Niamey, and Africa/Porto-Novo. Changes affecting code Unless NETBSD_INSPIRED is defined to 0, the tz library now supplies functions for creating and using objects that represent timezones. The new functions are tzalloc, tzfree, localtime_rz, mktime_z, and (if STD_INSPIRED is also defined) posix2time_z and time2posix_z. They are intended for performance: for example, localtime_rz (unlike localtime_r) is trivially thread-safe without locking. (Thanks to Christos Zoulas for proposing NetBSD-inspired functions, and to Alan Barrett and Jonathan Lennox for helping to debug the change.) zdump now builds with the tz library unless USE_LTZ is defined to 0, This lets zdump use tz features even if the system library lacks them. To build zdump with the system library, use 'make CFLAGS=-DUSE_LTZ=0 TZDOBJS=zdump.o CHECK_TIME_T_ALTERNATIVES='. zdump now uses localtime_rz if available, as it's significantly faster, and it can help zdump better diagnose invalid timezone names. Define HAVE_LOCALTIME_RZ to 0 to suppress this. HAVE_LOCALTIME_RZ defaults to 1 if NETBSD_INSPIRED && USE_LTZ. When localtime_rz is not available, zdump now uses localtime_r and tzset if available, as this is a bit cleaner and faster than plain localtime. Compile with -DHAVE_LOCALTIME_R=0 and/or -DHAVE_TZSET=0 if your system lacks these two functions. If THREAD_SAFE is defined to 1, the tz library is now thread-safe. Although not needed for tz's own applications, which are single-threaded, this supports POSIX better if the tz library is used in multithreaded apps. Some crashes have been fixed when zdump or the tz library is given invalid or outlandish input. The tz library no longer mishandles leap seconds on platforms with unsigned time_t in timezones that lack ordinary transitions after 1970. The tz code now attempts to infer TM_GMTOFF and TM_ZONE if not already defined, to make it easier to configure on common platforms. Define NO_TM_GMTOFF and NO_TM_ZONE to suppress this. Unless the new macro UNINIT_TRAP is defined to 1, the tz code now assumes that reading uninitialized memory yields garbage values but does not cause other problems such as traps. If TM_GMTOFF is defined and UNINIT_TRAP is 0, mktime is now more likely to guess right for ambiguous timestamps near transitions where tm_isdst does not change. If HAVE_STRFTIME_L is defined to 1, the tz library now defines strftime_l for compatibility with recent versions of POSIX. Only the C locale is supported, though. HAVE_STRFTIME_L defaults to 1 on recent POSIX versions, and to 0 otherwise. tzselect -c now uses a hybrid distance measure that works better in Africa. (Thanks to Alan Barrett for noting the problem.) The C source code now ports to NetBSD when GCC_DEBUG_FLAGS is used, or when time_tz is defined. When HAVE_UTMPX_H is set the 'date' command now builds on systems whose file does not define WTMPX_FILE, and when setting the date it updates the wtmpx file if _PATH_WTMPX is defined. This affects GNU/Linux and similar systems. For easier maintenance later, some C code has been simplified, some lint has been removed, and the code has been tweaked so that plain 'make' is more likely to work. The C type 'bool' is now used for boolean values, instead of 'int'. The long-obsolete LOCALE_HOME code has been removed. The long-obsolete 'gtime' function has been removed. Changes affecting build procedure 'zdump' no longer links in ialloc.o, as it's not needed. 'make check_time_t_alternatives' no longer assumes GNU diff. Changes affecting distribution tarballs The files checktab.awk and zoneinfo2tdf.pl are now distributed in the tzdata tarball instead of the tzcode tarball, since they help maintain the data. The NEWS and Theory files are now also distributed in the tzdata tarball, as they're relevant for data. (Thanks to Alan Barrett for pointing this out.) Also, the leapseconds.awk file is no longer distributed in the tzcode tarball, since it belongs in the tzdata tarball (where 2014f inadvertently also distributed it). Changes affecting documentation and commentary A new file CONTRIBUTING is distributed. (Thanks to Tim Parenti for suggesting a CONTRIBUTING file, and to Tony Finch and Walter Harms for debugging it.) The man pages have been updated to use function prototypes, to document thread-safe variants like localtime_r, and to document the NetBSD-inspired functions tzalloc, tzfree, localtime_rz, and mktime_z. The fields in Link lines have been renamed to be more descriptive and more like the parameters of 'ln'. LINK-FROM has become TARGET, and LINK-TO has become LINK-NAME. tz-link.htm mentions the IETF's tzdist working group; Windows Runtime etc. (thanks to Matt Johnson); and HP-UX's tztab. Some broken URLs have been fixed in the commentary. (Thanks to Lester Caine.) Commentary about Philippines DST has been updated, and commentary on pre-1970 time in India has been added. Release 2014f - 2014-08-05 17:42:36 -0700 Changes affecting future timestamps Russia will subtract an hour from most of its time zones on 2014-10-26 at 02:00 local time. (Thanks to Alexander Krivenyshev.) There are a few exceptions: Magadan Oblast (Asia/Magadan) and Zabaykalsky Krai are subtracting two hours; conversely, Chukotka Autonomous Okrug (Asia/Anadyr), Kamchatka Krai (Asia/Kamchatka), Kemerovo Oblast (Asia/Novokuznetsk), and the Samara Oblast and the Udmurt Republic (Europe/Samara) are not changing their clocks. The changed zones are Europe/Kaliningrad, Europe/Moscow, Europe/Simferopol, Europe/Volgograd, Asia/Yekaterinburg, Asia/Omsk, Asia/Novosibirsk, Asia/Krasnoyarsk, Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Khandyga, Asia/Sakhalin, and Asia/Ust-Nera; Asia/Magadan will have two hours subtracted; and Asia/Novokuznetsk's time zone abbreviation is affected, but not its UTC offset. Two zones are added: Asia/Chita (split from Asia/Yakutsk, and also with two hours subtracted) and Asia/Srednekolymsk (split from Asia/Magadan, but with only one hour subtracted). (Thanks to Tim Parenti for much of the above.) Changes affecting time zone abbreviations Australian eastern time zone abbreviations are now AEST/AEDT not EST, and similarly for the other Australian zones. That is, for eastern standard and daylight saving time the abbreviations are AEST and AEDT instead of the former EST for both; similarly, ACST/ACDT, ACWST/ACWDT, and AWST/AWDT are now used instead of the former CST, CWST, and WST. This change does not affect UT offsets, only time zone abbreviations. (Thanks to Rich Tibbett and many others.) Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UT +07) effective 2014-10-26 at 02:00 local time. The time zone abbreviation for Xinjiang Time (observed in Ürümqi) has been changed from URUT to XJT. (Thanks to Luther Ma.) Prefer MSK/MSD for Moscow time in Russia, even in other cities. Similarly, prefer EET/EEST for eastern European time in Russia. Change time zone abbreviations in (western) Samoa to use "ST" and "DT" suffixes, as this is more likely to match common practice. Prefix "W" to (western) Samoa time when its standard-time offset disagrees with that of American Samoa. America/Metlakatla now uses PST, not MeST, to abbreviate its time zone. Time zone abbreviations have been updated for Japan's two time zones used 1896-1937. JWST now stands for Western Standard Time, and JCST for Central Standard Time (formerly this was CJT). These abbreviations are now used for time in Korea, Taiwan, and Sakhalin while controlled by Japan. Changes affecting past timestamps China's five zones have been simplified to two, since the post-1970 differences in the other three seem to have been imaginary. The zones Asia/Harbin, Asia/Chongqing, and Asia/Kashgar have been removed; backwards-compatibility links still work, albeit with different behaviors for timestamps before May 1980. Asia/Urumqi's 1980 transition to UT +08 has been removed, so that it is now at +06 and not +08. (Thanks to Luther Ma and to Alois Treindl; Treindl sent helpful translations of two papers by Guo Qingsheng.) Some zones have been turned into links, when they differed from existing zones only for older UT offsets where data entries were likely invented. These changes affect UT offsets in pre-1970 timestamps only. This is similar to the change in release 2013e, except this time for western Africa. The affected zones are: Africa/Bamako, Africa/Banjul, Africa/Conakry, Africa/Dakar, Africa/Freetown, Africa/Lome, Africa/Nouakchott, Africa/Ouagadougou, Africa/Sao_Tome, and Atlantic/St_Helena. This also affects the backwards-compatibility link Africa/Timbuktu. (Thanks to Alan Barrett, Stephen Colebourne, Tim Parenti, and David Patte for reporting problems in earlier versions of this change.) Asia/Shanghai's pre-standard-time UT offset has been changed from 8:05:57 to 8:05:43, the location of Xujiahui Observatory. Its transition to standard time has been changed from 1928 to 1901. Asia/Taipei switched to JWST on 1896-01-01, then to JST on 1937-10-01, then to CST on 1945-09-21 at 01:00, and did not observe DST in 1945. In 1946 it observed DST from 05-15 through 09-30; in 1947 from 04-15 through 10-31; and in 1979 from 07-01 through 09-30. (Thanks to Yu-Cheng Chuang.) Asia/Riyadh's transition to standard time is now 1947-03-14, not 1950. Europe/Helsinki's 1942 fall-back transition was 10-04 at 01:00, not 10-03 at 00:00. (Thanks to Konstantin Hyppönen.) Pacific/Pago_Pago has been changed from UT -11:30 to -11 for the period from 1911 to 1950. Pacific/Chatham has been changed to New Zealand standard time plus 45 minutes for the period before 1957, reflecting a 1956 remark in the New Zealand parliament. Europe/Budapest has several pre-1946 corrections: in 1918 the transition out of DST was on 09-16, not 09-29; in 1919 it was on 11-24, not 09-15; in 1945 it was on 11-01, not 11-03; in 1941 the transition to DST was 04-08 not 04-06 at 02:00; and there was no DST in 1920. Africa/Accra is now assumed to have observed DST from 1920 through 1935. Time in Russia before 1927 or so has been corrected by a few seconds in the following zones: Europe/Moscow, Asia/Irkutsk, Asia/Tbilisi, Asia/Tashkent, Asia/Vladivostok, Asia/Yekaterinburg, Europe/Helsinki, and Europe/Riga. Also, Moscow's location has been changed to its Kilometer 0 point. (Thanks to Vladimir Karpinsky for the Moscow changes.) Changes affecting data format A new file 'zone1970.tab' supersedes 'zone.tab' in the installed data. The new file's extended format allows multiple country codes per zone. The older file is still installed but is deprecated; its format is not changing and it will still be distributed for a while, but new applications should use the new file. The new file format simplifies maintenance of obscure locations. To test this, it adds coverage for the Crozet Islands and the Scattered Islands. (Thanks to Tobias Conradi and Antoine Leca.) The file 'iso3166.tab' is planned to switch from ASCII to UTF-8. It is still ASCII now, but commentary about the switch has been added. The new file 'zone1970.tab' already uses UTF-8. Changes affecting code 'localtime', 'mktime', etc. now use much less stack space if ALL_STATE is defined. (Thanks to Elliott Hughes for reporting the problem.) 'zic' no longer mishandles input when ignoring case in locales that are not compatible with English, e.g., unibyte Turkish locales when compiled with HAVE_GETTEXT. Error diagnostics of 'zic' and 'yearistype' have been reworded so that they no longer use ASCII '-' as if it were a dash. 'zic' now rejects output file names that contain '.' or '..' components. (Thanks to Tim Parenti for reporting the problem.) 'zic -v' now warns about output file names that do not follow POSIX rules, or that contain a digit or '.'. (Thanks to Arthur David Olson for starting the ball rolling on this.) Some lint has been removed when using GCC_DEBUG_FLAGS with GCC 4.9.0. Changes affecting build procedure 'zic' no longer links in localtime.o and asctime.o, as they're not needed. (Thanks to John Cochran.) Changes affecting documentation and commentary The 'Theory' file documents legacy names, the longstanding exceptions to the POSIX-inspired file name rules. The 'zic' documentation clarifies the role of time types when interpreting dates. (Thanks to Arthur David Olson.) Documentation and commentary now prefer UTF-8 to US-ASCII, allowing the use of proper accents in foreign words and names. Code and data have not changed because of this. (Thanks to Garrett Wollman, Ian Abbott, and Guy Harris for helping to debug this.) Non-HTML documentation and commentary now use plain-text URLs instead of HTML insertions, and are more consistent about bracketing URLs when they are not already surrounded by white space. (Thanks to suggestions by Steffen Nurpmeso.) There is new commentary about Xujiahui Observatory, the five time-zone project in China from 1918 to 1949, timekeeping in Japanese-occupied Shanghai, and Tibet Time in the 1950s. The sharp-eyed can spot the warlord Jin Shuren in the data. Commentary about the coverage of each Russian zone has been standardized. (Thanks to Tim Parenti.) There is new commentary about contemporary timekeeping in Ethiopia. Obsolete comments about a 2007 proposal for DST in Kuwait has been removed. There is new commentary about time in Poland in 1919. Proper credit has been given to DST inventor George Vernon Hudson. Commentary about time in Metlakatla, AK and Resolute, NU has been improved, with a new source for the former. In zone.tab, Pacific/Easter no longer mentions Salas y Gómez, as it is uninhabited. Commentary about permanent Antarctic bases has been updated. Several typos have been corrected. (Thanks to Tim Parenti for contributing some of these fixes.) tz-link.htm now mentions the JavaScript libraries Moment Timezone, TimezoneJS.Date, Walltime-js, and Timezone. (Thanks to a heads-up from Matt Johnson.) Also, it mentions the Go 'latlong' package. (Thanks to a heads-up from Dirkjan Ochtman.) The files usno1988, usno1989, usno1989a, usno1995, usno1997, and usno1998 have been removed. These obsolescent US Naval Observatory entries were no longer helpful for maintenance. (Thanks to Tim Parenti for the suggestion.) Release 2014e - 2014-06-12 21:53:52 -0700 Changes affecting near-future timestamps Egypt's 2014 Ramadan-based transitions are June 26 and July 31 at 24:00. (Thanks to Imed Chihi.) Guess that from 2015 on Egypt will temporarily switch to standard time at 24:00 the last Thursday before Ramadan, and back to DST at 00:00 the first Friday after Ramadan. Similarly, Morocco's are June 28 at 03:00 and August 2 at 02:00. (Thanks to Milamber Space Network.) Guess that from 2015 on Morocco will temporarily switch to standard time at 03:00 the last Saturday before Ramadan, and back to DST at 02:00 the first Saturday after Ramadan. Changes affecting past timestamps The abbreviation "MSM" (Moscow Midsummer Time) is now used instead of "MSD" for Moscow's double daylight time in summer 1921. Also, a typo "VLASST" has been repaired to be "VLAST" for Vladivostok summer time in 1991. (Thanks to Hank W. for reporting the problems.) Changes affecting commentary tz-link.htm now cites RFC 7265 for jCal, mentions PTP and the draft CalDAV extension, updates URLs for TSP, TZInfo, IATA, and removes stale pointers to World Time Explorer and WORLDTIME. Release 2014d - 2014-05-27 21:34:40 -0700 Changes affecting code zic no longer generates files containing timestamps before the Big Bang. This works around GNOME glib bug 878 (Thanks to Leonardo Chiquitto for reporting the bug, and to Arthur David Olson and James Cloos for suggesting improvements to the fix.) Changes affecting documentation tz-link.htm now mentions GNOME. Release 2014c - 2014-05-13 07:44:13 -0700 Changes affecting near-future timestamps Egypt observes DST starting 2014-05-15 at 24:00. (Thanks to Ahmad El-Dardiry and Gunther Vermier.) Details have not been announced, except that DST will not be observed during Ramadan. Guess that DST will stop during the same Ramadan dates as Morocco, and that Egypt's future spring and fall transitions will be the same as 2010 when it last observed DST, namely April's last Friday at 00:00 to September's last Thursday at 23:00 standard time. Also, guess that Ramadan transitions will be at 00:00 standard time. Changes affecting code zic now generates transitions for minimum time values, eliminating guesswork when handling low-valued timestamps. (Thanks to Arthur David Olson.) Port to Cygwin sans glibc. (Thanks to Arthur David Olson.) Changes affecting commentary and documentation Remove now-confusing comment about Jordan. (Thanks to Oleksii Nochovnyi.) Release 2014b - 2014-03-24 21:28:50 -0700 Changes affecting near-future timestamps Crimea switches to Moscow time on 2014-03-30 at 02:00 local time. (Thanks to Alexander Krivenyshev.) Move its zone.tab entry from UA to RU. New entry for Troll station, Antarctica. (Thanks to Paul-Inge Flakstad and Bengt-Inge Larsson.) This is currently an approximation; a better version will require the zic and localtime fixes mentioned below, and the plan is to wait for a while until at least the zic fixes propagate. Changes affecting code 'zic' and 'localtime' no longer reject locations needing four transitions per year for the foreseeable future. (Thanks to Andrew Main (Zefram).) Also, 'zic' avoids some unlikely failures due to integer overflow. Changes affecting build procedure 'make check' now detects Rule lines defined but never used. The NZAQ rules, an instance of this problem, have been removed. Changes affecting commentary and documentation Fix Tuesday/Thursday typo in description of time in Israel. (Thanks to Bert Katz via Pavel Kharitonov and Mike Frysinger.) Microsoft Windows 8.1 doesn't support tz database names. (Thanks to Donald MacQueen.) Instead, the Microsoft Windows Store app library supports them. Add comments about Johnston Island time in the 1960s. (Thanks to Lyle McElhaney.) Morocco's 2014 DST start will be as predicted. (Thanks to Sebastien Willemijns.) Release 2014a - 2014-03-07 23:30:29 -0800 Changes affecting near-future timestamps Turkey begins DST on 2014-03-31, not 03-30. (Thanks to Faruk Pasin for the heads-up, and to Tim Parenti for simplifying the update.) Changes affecting past timestamps Fiji ended DST on 2014-01-19 at 02:00, not the previously-scheduled 03:00. (Thanks to Steffen Thorsen.) Ukraine switched from Moscow to Eastern European time on 1990-07-01 (not 1992-01-01), and observed DST during the entire next winter. (Thanks to Vladimir in Moscow via Alois Treindl.) In 1988 Israel observed DST from 04-10 to 09-04, not 04-09 to 09-03. (Thanks to Avigdor Finkelstein.) Changes affecting code A uninitialized-storage bug in 'localtime' has been fixed. (Thanks to Logan Chien.) Changes affecting the build procedure The settings for 'make check_web' now default to Ubuntu 13.10. Changes affecting commentary and documentation The boundary of the US Pacific time zone is given more accurately. (Thanks to Alan Mintz.) Chile's 2014 DST will be as predicted. (Thanks to José Miguel Garrido.) Paraguay's 2014 DST will be as predicted. (Thanks to Carlos Raúl Perasso.) Better descriptions of countries with same time zone history as Trinidad and Tobago since 1970. (Thanks to Alan Barrett for suggestion.) Several changes affect tz-link.htm, the main web page. Mention Time.is (thanks to Even Scharning) and WX-now (thanks to David Braverman). Mention xCal (Internet RFC 6321) and jCal. Microsoft has some support for tz database names. CLDR data formats include both XML and JSON. Mention Maggiolo's map of solar vs standard time. (Thanks to Arthur David Olson.) Mention TZ4Net. (Thanks to Matt Johnson.) Mention the timezone-olson Haskell package. Mention zeitverschiebung.net. (Thanks to Martin Jäger.) Remove moribund links to daylight-savings-time.info and to Simple Timer + Clocks. Update two links. (Thanks to Oscar van Vlijmen.) Fix some formatting glitches, e.g., remove random newlines from abbr elements' title attributes. Release 2013i - 2013-12-17 07:25:23 -0800 Changes affecting near-future timestamps: Jordan switches back to standard time at 00:00 on December 20, 2013. The 2006-2011 transition schedule is planned to resume in 2014. (Thanks to Steffen Thorsen.) Changes affecting past timestamps: In 2004, Cuba began DST on March 28, not April 4. (Thanks to Steffen Thorsen.) Changes affecting code The compile-time flag NOSOLAR has been removed, as nowadays the benefit of slightly shrinking runtime table size is outweighed by the cost of disallowing potential future updates that exceed old limits. Changes affecting documentation and commentary The files solar87, solar88, and solar89 are no longer distributed. They were a negative experiment - that is, a demonstration that tz data can represent solar time only with some difficulty and error. Their presence in the distribution caused confusion, as Riyadh civil time was generally not solar time in those years. tz-link.htm now mentions Noda Time. (Thanks to Matt Johnson.) Release 2013h - 2013-10-25 15:32:32 -0700 Changes affecting current and future timestamps: Libya has switched its UT offset back to +02 without DST, instead of +01 with DST. (Thanks to Even Scharning.) Western Sahara (Africa/El_Aaiun) uses Morocco's DST rules. (Thanks to Gwillim Law.) Changes affecting future timestamps: Acre and (we guess) western Amazonas will switch from UT -04 to -05 on 2013-11-10. This affects America/Rio_Branco and America/Eirunepe. (Thanks to Steffen Thorsen.) Add entries for DST transitions in Morocco in the year 2038. This avoids some year-2038 glitches introduced in 2013g. (Thanks to Yoshito Umaoka for reporting the problem.) Changes affecting API The 'tzselect' command no longer requires the 'select' command, and should now work with /bin/sh on more platforms. It also works around a bug in BusyBox awk before version 1.21.0. (Thanks to Patrick 'P. J.' McDermott and Alan Barrett.) Changes affecting code Fix localtime overflow bugs with 32-bit unsigned time_t. zdump no longer assumes sscanf returns maximal values on overflow. Changes affecting the build procedure The builder can specify which programs to use, if any, instead of 'ar' and 'ranlib', and libtz.a is now built locally before being installed. (Thanks to Michael Forney.) A dependency typo in the 'zdump' rule has been fixed. (Thanks to Andrew Paprocki.) The Makefile has been simplified by assuming that 'mkdir -p' and 'cp -f' work as specified by POSIX.2-1992 or later; this is portable nowadays. 'make clean' no longer removes 'leapseconds', since it's host-independent and is part of the distribution. The unused makefile macros TZCSRCS, TZDSRCS, DATESRCS have been removed. Changes affecting documentation and commentary tz-link.htm now mentions TC TIMEZONE's draft time zone service protocol (thanks to Mike Douglass) and TimezoneJS.Date (thanks to Jim Fehrle). Update URLs in tz-link page. Add URLs for Microsoft Windows, since 8.1 introduces tz support. Remove URLs for Tru64 and UnixWare (no longer maintained) and for old advisories. SOFA now does C. Release 2013g - 2013-09-30 21:08:26 -0700 Changes affecting current and near-future timestamps Morocco now observes DST from the last Sunday in March to the last Sunday in October, not April to September respectively. (Thanks to Steffen Thorsen.) Changes affecting 'zic' 'zic' now runs on platforms that lack both hard links and symlinks. (Thanks to Theo Veenker for reporting the problem, for MinGW.) Also, fix some bugs on platforms that lack hard links but have symlinks. 'zic -v' again warns that Asia/Tehran has no POSIX environment variable to predict the far future, fixing a bug introduced in 2013e. Changes affecting the build procedure The 'leapseconds' file is again put into the tzdata tarball. Also, 'leapseconds.awk', so tzdata is self-contained. (Thanks to Matt Burgess and Ian Abbott.) The timestamps of these and other dependent files in tarballs are adjusted more consistently. Changes affecting documentation and commentary The README file is now part of the data tarball as well as the code. It now states that files are public domain unless otherwise specified. (Thanks to Andrew Main (Zefram) for asking for clarifications.) Its details about the 1989 release moved to a place of honor near the end of NEWS. Release 2013f - 2013-09-24 23:37:36 -0700 Changes affecting near-future timestamps Tocantins will very likely not observe DST starting this spring. (Thanks to Steffen Thorsen.) Jordan will likely stay at UT +03 indefinitely, and will not fall back this fall. Palestine will fall back at 00:00, not 01:00. (Thanks to Steffen Thorsen.) Changes affecting API The types of the global variables 'timezone' and 'altzone' (if present) have been changed back to 'long'. This is required for 'timezone' by POSIX, and for 'altzone' by common practice, e.g., Solaris 11. These variables were originally 'long' in the tz code, but were mistakenly changed to 'time_t' in 1987; nobody reported the incompatibility until now. The difference matters on x32, where 'long' is 32 bits and 'time_t' is 64. (Thanks to Elliott Hughes.) Changes affecting the build procedure Avoid long strings in leapseconds.awk to work around a mawk bug. (Thanks to Cyril Baurand.) Changes affecting documentation and commentary New file 'NEWS' that contains release notes like this one. Paraguay's law does not specify DST transition time; 00:00 is customary. (Thanks to Waldemar Villamayor-Venialbo.) Minor capitalization fixes. Changes affecting version-control only The experimental GitHub repository now contains annotated and signed tags for recent releases, e.g., '2013e' for Release 2013e. Releases are tagged starting with 2012e; earlier releases were done differently, and tags would either not have a simple name or not exactly match what was released. 'make set-timestamps' is now simpler and a bit more portable. Release 2013e - 2013-09-19 23:50:04 -0700 Changes affecting near-future timestamps This year Fiji will start DST on October 27, not October 20. (Thanks to David Wheeler for the heads-up.) For now, guess that Fiji will continue to spring forward the Sunday before the fourth Monday in October. Changes affecting current and future time zone abbreviations Use WIB/WITA/WIT rather than WIT/CIT/EIT for alphabetic Indonesian time zone abbreviations since 1932. (Thanks to George Ziegler, Priyadi Iman Nurcahyo, Zakaria, Jason Grimes, Martin Pitt, and Benny Lin.) This affects Asia/Dili, Asia/Jakarta, Asia/Jayapura, Asia/Makassar, and Asia/Pontianak. Use ART (UT -03, standard time), rather than WARST (also -03, but daylight saving time) for San Luis, Argentina since 2009. Changes affecting Godthåb timestamps after 2037 if version mismatch Allow POSIX-like TZ strings where the transition time's hour can range from -167 through 167, instead of the POSIX-required 0 through 24. E.g., TZ='FJT-12FJST,M10.3.1/146,M1.3.4/75' for the new Fiji rules. This is a more-compact way to represent far-future timestamps for America/Godthab, America/Santiago, Antarctica/Palmer, Asia/Gaza, Asia/Hebron, Asia/Jerusalem, Pacific/Easter, and Pacific/Fiji. Other zones are unaffected by this change. (Derived from a suggestion by Arthur David Olson.) Allow POSIX-like TZ strings where daylight saving time is in effect all year. E.g., TZ='WART4WARST,J1/0,J365/25' for Western Argentina Summer Time all year. This supports a more-compact way to represent the 2013d data for America/Argentina/San_Luis. Because of the change for San Luis noted above this change does not affect the current data. (Thanks to Andrew Main (Zefram) for suggestions that improved this change.) Where these two TZ changes take effect, there is a minor extension to the tz file format in that it allows new values for the embedded TZ-format string, and the tz file format version number has therefore been increased from 2 to 3 as a precaution. Version-2-based client code should continue to work as before for all timestamps before 2038. Existing version-2-based client code (tzcode, GNU/Linux, Solaris) has been tested on version-3-format files, and typically works in practice even for timestamps after 2037; the only known exception is America/Godthab. Changes affecting timestamps before 1970 Pacific/Johnston is now a link to Pacific/Honolulu. This corrects some errors before 1947. Some zones have been turned into links, when they differ from existing zones only in older data entries that were likely invented or that differ only in LMT or transitions from LMT. These changes affect only timestamps before 1943. The affected zones are: Africa/Juba, America/Anguilla, America/Aruba, America/Dominica, America/Grenada, America/Guadeloupe, America/Marigot, America/Montserrat, America/St_Barthelemy, America/St_Kitts, America/St_Lucia, America/St_Thomas, America/St_Vincent, America/Tortola, and Europe/Vaduz. (Thanks to Alois Treindl for confirming that the old Europe/Vaduz zone was wrong and the new link is better for WWII-era times.) Change Kingston Mean Time from -5:07:12 to -5:07:11. This affects America/Cayman, America/Jamaica and America/Grand_Turk timestamps from 1890 to 1912. Change the UT offset of Bern Mean Time from 0:29:44 to 0:29:46. This affects Europe/Zurich timestamps from 1853 to 1894. (Thanks to Alois Treindl.) Change the date of the circa-1850 Zurich transition from 1849-09-12 to 1853-07-16, overriding Shanks with data from Messerli about postal and telegraph time in Switzerland. Changes affecting time zone abbreviations before 1970 For Asia/Jakarta, use BMT (not JMT) for mean time from 1923 to 1932, as Jakarta was called Batavia back then. Changes affecting API The 'zic' command now outputs a dummy transition when far-future data can't be summarized using a TZ string, and uses a 402-year window rather than a 400-year window. For the current data, this affects only the Asia/Tehran file. It does not affect any of the timestamps that this file represents, so zdump outputs the same information as before. (Thanks to Andrew Main (Zefram).) The 'date' command has a new '-r' option, which lets you specify the integer time to display, a la FreeBSD. The 'tzselect' command has two new options '-c' and '-n', which lets you select a zone based on latitude and longitude. The 'zic' command's '-v' option now warns about constructs that require the new version-3 binary file format. (Thanks to Arthur David Olson for the suggestion.) Support for floating-point time_t has been removed. It was always dicey, and POSIX no longer requires it. (Thanks to Eric Blake for suggesting to the POSIX committee to remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy Heninger, Arthur David Olson, and Alois Treindl, for reporting bugs and elucidating some of the corners of the old floating-point implementation.) The signatures of 'offtime', 'timeoff', and 'gtime' have been changed back to the old practice of using 'long' to represent UT offsets. This had been inadvertently and mistakenly changed to 'int_fast32_t'. (Thanks to Christos Zoulas.) The code avoids undefined behavior on integer overflow in some more places, including gmtime, localtime, mktime and zdump. Changes affecting the zdump utility zdump now outputs "UT" when referring to Universal Time, not "UTC". "UTC" does not make sense for timestamps that predate the introduction of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen for clarifying UT vs UTC.) Data changes affecting behavior of tzselect and similar programs Country code BQ is now called the more-common name "Caribbean Netherlands" rather than the more-official "Bonaire, St Eustatius & Saba". Remove from zone.tab the names America/Montreal, America/Shiprock, and Antarctica/South_Pole, as they are equivalent to existing same-country-code zones for post-1970 timestamps. The data entries for these names are unchanged, so the names continue to work as before. Changes affecting code internals zic -c now runs way faster on 64-bit hosts when given large numbers. zic now uses vfprintf to avoid allocating and freeing some memory. tzselect now computes the list of continents from the data, rather than have it hard-coded. Minor changes pacify GCC 4.7.3 and GCC 4.8.1. Changes affecting the build procedure The 'leapseconds' file is now generated automatically from a new file 'leap-seconds.list', which is a copy of A new source file 'leapseconds.awk' implements this. The goal is simplification of the future maintenance of 'leapseconds'. When building the 'posix' or 'right' subdirectories, if the subdirectory would be a copy of the default subdirectory, it is now made a symbolic link if that is supported. This saves about 2 MB of file system space. The links America/Shiprock and Antarctica/South_Pole have been moved to the 'backward' file. This affects only nondefault builds that omit 'backward'. Changes affecting version-control only .gitignore now ignores 'date'. Changes affecting documentation and commentary Changes to the 'tzfile' man page It now mentions that the binary file format may be extended in future versions by appending data. It now refers to the 'zdump' and 'zic' man pages. Changes to the 'zic' man page It lists conditions that elicit a warning with '-v'. It says that the behavior is unspecified when duplicate names are given, or if the source of one link is the target of another. Its examples are updated to match the latest data. The definition of white space has been clarified slightly. (Thanks to Michael Deckers.) Changes to the 'Theory' file There is a new section about the accuracy of the tz database, describing the many ways that errors can creep in, and explaining why so many of the pre-1970 timestamps are wrong or misleading (thanks to Steve Allen, Lester Caine, and Garrett Wollman for discussions that contributed to this). The 'Theory' file describes LMT better (this follows a suggestion by Guy Harris). It refers to the 2013 edition of POSIX rather than the 2004 edition. It's mentioned that excluding 'backward' should not affect the other data, and it suggests at least one zone.tab name per inhabited country (thanks to Stephen Colebourne). Some longstanding restrictions on names are documented, e.g., 'America/New_York' precludes 'America/New_York/Bronx'. It gives more reasons for the 1970 cutoff. It now mentions which time_t variants are supported, such as signed integer time_t. (Thanks to Paul Goyette for reporting typos in an experimental version of this change.) (Thanks to Philip Newton for correcting typos in these changes.) Documentation and commentary is more careful to distinguish UT in general from UTC in particular. (Thanks to Steve Allen.) Add a better source for the Zurich 1894 transition. (Thanks to Pierre-Yves Berger.) Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.) Release 2013d - 2013-07-05 07:38:01 -0700 Changes affecting future timestamps: Morocco's midsummer transitions this year are July 7 and August 10, not July 9 and August 8. (Thanks to Andrew Paprocki.) Israel now falls back on the last Sunday of October. (Thanks to Ephraim Silverberg.) Changes affecting past timestamps: Specify Jerusalem's location more precisely; this changes the pre-1880 times by 2 s. Changing affecting metadata only: Fix typos in the entries for country codes BQ and SX. Changes affecting code: Rework the code to fix a bug with handling Australia/Macquarie on 32-bit hosts (thanks to Arthur David Olson). Port to platforms like NetBSD, where time_t can be wider than long. Add support for testing time_t types other than the system's. Run 'make check_time_t_alternatives' to try this out. Currently, the tests fail for unsigned time_t; this should get fixed at some point. Changes affecting documentation and commentary: Deemphasize the significance of national borders. Update the zdump man page. Remove obsolete NOID comment (thanks to Denis Excoffier). Update several URLs and comments in the web pages. Spelling fixes (thanks to Kevin Lyda and Jonathan Leffler). Update URL for CLDR Zone->Tzid table (thanks to Yoshito Umaoka). Release 2013c - 2013-04-19 16:17:40 -0700 Changes affecting current and future timestamps: Palestine observed DST starting March 29, 2013. (Thanks to Steffen Thorsen.) From 2013 on, Gaza and Hebron both observe DST, with the predicted rules being the last Thursday in March at 24:00 to the first Friday on or after September 21 at 01:00. Assume that the recent change to Paraguay's DST rules is permanent, by moving the end of DST to the 4th Sunday in March every year. (Thanks to Carlos Raúl Perasso.) Changes affecting past timestamps: Fix some historical data for Palestine to agree with that of timeanddate.com, as follows: The spring 2008 change in Gaza and Hebron was on 00:00 Mar 28, not 00:00 Apr 1. The fall 2009 change in Gaza and Hebron on Sep 4 was at 01:00, not 02:00. The spring 2010 change in Hebron was 00:00 Mar 26, not 00:01 Mar 27. The spring 2011 change in Gaza was 00:01 Apr 1, not 12:01 Apr 2. The spring 2011 change in Hebron on Apr 1 was at 00:01, not 12:01. The fall 2011 change in Hebron on Sep 30 was at 00:00, not 03:00. Fix times of habitation for Macquarie to agree with the Tasmania Parks & Wildlife Service history, which indicates that permanent habitation was 1899-1919 and 1948 on. Changing affecting metadata only: Macquarie Island is politically part of Australia, not Antarctica. (Thanks to Tobias Conradi.) Sort Macquarie more-consistently with other parts of Australia. (Thanks to Tim Parenti.) Release 2013b - 2013-03-10 22:33:40 -0700 Changes affecting current and future timestamps: Haiti uses US daylight-saving rules this year, and presumably future years. This changes timestamps starting today. (Thanks to Steffen Thorsen.) Paraguay will end DST on March 24 this year. (Thanks to Steffen Thorsen.) For now, assume it's just this year. Morocco does not observe DST during Ramadan; try to predict Ramadan in Morocco as best we can. (Thanks to Erik Homoet for the heads-up.) Changes affecting commentary: Update URLs in tz-link page. Add URLs for webOS, BB10, iOS. Update URL for Solaris. Mention Internet RFC 6557. Update Internet RFCs 2445->5545, 2822->5322. Switch from FTP to HTTP for Internet RFCs. Release 2013a - 2013-02-27 09:20:35 -0800 Change affecting binary data format: The zone offset at the end of version-2-format zone files is now allowed to be 24:00, as per POSIX.1-2008. (Thanks to Arthur David Olson.) Changes affecting current and future timestamps: Chile's 2013 rules, and we guess rules for 2014 and later, will be the same as 2012, namely Apr Sun>=23 03:00 UTC to Sep Sun>=2 04:00 UTC. (Thanks to Steffen Thorsen and Robert Elz.) New Zones Asia/Khandyga, Asia/Ust-Nera, Europe/Busingen. (Thanks to Tobias Conradi and Arthur David Olson.) Many changes affect historical timestamps before 1940. These were deduced from: Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94 . Changes affecting the code: Fix zic bug that mishandled Egypt's 2010 changes (this also affected the data). (Thanks to Arthur David Olson.) Fix localtime bug when time_t is unsigned and data files were generated by a signed time_t system. (Thanks to Doug Bailey for reporting and to Arthur David Olson for fixing.) Allow the email address for bug reports to be set by the packager. The default is tz@iana.org, as before. (Thanks to Joseph S. Myers.) Update HTML checking to be compatible with Ubuntu 12.10. Check that files are a safe subset of ASCII. At some point we may relax this requirement to a safe subset of UTF-8. Without the check, some non-UTF-8 encodings were leaking into the distribution. Commentary changes: Restore a comment about copyright notices that was inadvertently deleted. (Thanks to Arthur David Olson.) Improve the commentary about which districts observe what times in Russia. (Thanks to Oscar van Vlijmen and Arthur David Olson.) Add web page links to tz.js. Add "Run by the Monkeys" to tz-art. (Thanks to Arthur David Olson.) Release 2012j - 2012-11-12 18:34:49 -0800 Libya moved to CET this weekend, but with DST planned next year. (Thanks to Even Scharning, Steffen Thorsen, and Tim Parenti.) Signatures now have the extension .asc, not .sign, as that's more standard. (Thanks to Phil Pennock.) The output of 'zdump --version', and of 'zic --version', now uses a format that is more typical for --version. (Thanks to Joseph S. Myers.) The output of 'tzselect --help', 'zdump --help', and 'zic --help' now uses tz@iana.org rather than the old elsie address. zic -v now complains about abbreviations that are less than 3 or more than 6 characters, as per Posix. Formerly, it checked for abbreviations that were more than 3. 'make public' no longer puts its temporary directory under /tmp, and uses the just-built zic rather than the system zic. Various fixes to documentation and commentary. Release 2012i - 2012-11-03 12:57:09 -0700 Cuba switches from DST tomorrow at 01:00. (Thanks to Steffen Thorsen.) Linker flags can now be specified via LDFLAGS. AWK now defaults to 'awk', not 'nawk'. The shell in tzselect now defaults to /bin/bash, but this can be overridden by specifying KSHELL. The main web page now mentions the unofficial GitHub repository. (Thanks to Mike Frysinger.) Tarball signatures can now be built by running 'make signatures'. There are also new makefile rules 'tarballs', 'check_public', and separate makefile rules for each tarball and signature file. A few makefile rules are now more portable to strict POSIX. The main web page now lists the canonical IANA URL. Release 2012h - 2012-10-26 22:49:10 -0700 Bahia no longer has DST. (Thanks to Kelley Cook.) Tocantins has DST. (Thanks to Rodrigo Severo.) Israel has new DST rules next year. (Thanks to Ephraim Silverberg.) Jordan stays on DST this winter. (Thanks to Steffen Thorsen.) Web page updates. More C modernization, except that at Arthur David Olson's suggestion the instances of 'register' were kept. Release 2012g - 2012-10-17 20:59:45 -0700 Samoa fall 2012 and later. (Thanks to Nicholas Pereira and Robert Elz.) Palestine fall 2012. (Thanks to Steffen Thorsen.) Assume C89. To attack the version-number problem, this release ships the file 'Makefile' (which contains the release number) in both the tzcode and the tzdata tarballs. The two Makefiles are identical, and should be identical in any matching pair of tarballs, so it shouldn't matter which order you extract the tarballs. Perhaps we can come up with a better version-number scheme at some point; this scheme does have the virtue of not adding more files. Release 2012f - 2012-09-12 23:17:03 -0700 * australasia (Pacific/Fiji): Fiji DST is October 21 through January 20 this year. (Thanks to Steffen Thorsen.) Release 2012e - 2012-08-02 20:44:55 -0700 * australasia (Pacific/Fakaofo): Tokelau is UT +13, not +14. (Thanks to Steffen Thorsen.) * Use a single version number for both code and data. * .gitignore: New file. * Remove trailing white space. Release code2012c-data2012d - 2012-07-19 16:35:33 -0700 Changes for Morocco's timestamps, which take effect in a couple of hours, along with infrastructure changes to accommodate how the tz code and data are released on IANA. Release data2012c - 2012-03-27 12:17:25 -0400 africa Summer time changes for Morocco (to start late April 2012) asia Changes for 2012 for Gaza & the West Bank (Hebron) and Syria northamerica Haiti following US/Canada rules for 2012 (and we're assuming, for now anyway, for the future). Release 2012b - 2012-03-02 12:29:15 +0700 There is just one change to tzcode2012b (compared with 2012a): the Makefile that was accidentally included with 2012a has been replaced with the version that should have been there, which is identical with the previous version (from tzcode2011i). There are just two changes in tzdata2012b compared with 2012a. Most significantly, summer time in Cuba has been delayed 3 weeks (now starts April 1 rather than March 11). Since Mar 11 (the old start date, as listed in 2012a) is just a little over a week away, this change is urgent. Less importantly, an excess tab in one of the changes in zone.tab in 2012a has been removed. Release 2012a - 2012-03-01 18:28:10 +0700 The changes in tzcode2012a (compared to the previous version, 2011i) are entirely to the README and tz-art.htm and tz-link.htm files, if none of those concern you, you can ignore the code update. The changes reflect the changed addresses for the mailing list and the code and data distribution points & methods (and a link to DateTime::TimeZone::Tzfile has been added to tz-link.htm). In tzdata2012a (compared to the previous release, which was 2011n) the major changes are: Chile 2011/2012 and 2012/2013 summer time date adjustments. Falkland Islands onto permanent summer time (we're assuming for the foreseeable future, though 2012 is all we're fairly certain of.) Armenia has abolished Summer Time. Tokelau jumped the International Date Line back last December (just the same as their near neighbour, Samoa). America/Creston is a new zone for a small area of British Columbia There will be a leapsecond 2012-06-30 23:59:60 UTC. Other minor changes are: Corrections to 1918 Canadian summer time end dates. Updated URL for UK time zone history (in comments) A few typos in Le Corre's list of free French place names (comments) Release data2011n - 2011-10-30 14:57:54 +0700 There are three changes of note - most urgently, Cuba (America/Havana) has extended summer time by two weeks, now to end on Nov 13, rather than the (already past) Oct 30. Second, the Pridnestrovian Moldavian Republic (Europe/Tiraspol) decided not to split from the rest of Moldova after all, and consequently that zone has been removed (again) and reinstated in the "backward" file as a link to Europe/Chisinau. And third, the end date for Fiji's summer time this summer was moved forward from the earlier planned Feb 26, to Jan 22. Apart from that, Moldova (MD) returns to a single entry in zone.tab (and the incorrect syntax that was in the 2011m version of that file is so fixed - it would have been fixed in a different way had this change not happened - that's the "missing" sccs version id). Release data2011m - 2011-10-24 21:42:16 +0700 In particular, the typos in comments in the data (2011-11-17 should have been 2011-10-17 as Alan Barrett noted, and spelling of Tiraspol that Tim Parenti noted) have been fixed, and the change for Ukraine has been made in all 4 Ukrainian zones, rather than just Kiev (again, thanks to Tim Parenti, and also Denys Gavrysh) In addition, I added Europe/Tiraspol to zone.tab. This time, all the files have new version numbers... (including the files otherwise unchanged in 2011m that were changed in 2011l but didn't get new version numbers there...) Release data2011l - 2011-10-10 11:15:43 +0700 There are just 2 changes that cause different generated tzdata files from zic, to Asia/Hebron and Pacific/Fiji - the possible change for Bahia, Brazil is included, but commented out. Compared with the diff I sent out last week, this version also includes attributions for the sources for the changes (in much the same format as ado used, but the html tags have not been checked, verified, or used in any way at all, so if there are errors there, please let me know.) Release data2011k - 2011-09-20 17:54:03 -0400 [not summarized] Release data2011j - 2011-09-12 09:22:49 -0400 (contemporary changes for Samoa; past changes for Kenya, Uganda, and Tanzania); there are also two spelling corrections to comments in the australasia file (with thanks to Christos Zoulas). Release 2011i - 2011-08-29 05:56:32 -0400 [not summarized] Release data2011h - 2011-06-15 18:41:48 -0400 Russia and Curaçao changes Release 2011g - 2011-04-25 09:07:22 -0400 update the rules for Egypt to reflect its abandonment of DST this year Release 2011f - 2011-04-06 17:14:53 -0400 [not summarized] Release 2011e - 2011-03-31 16:04:38 -0400 Morocco, Chile, and tz-link changes Release 2011d - 2011-03-14 09:18:01 -0400 changes that impact present-day timestamps in Cuba, Samoa, and Turkey Release 2011c - 2011-03-07 09:30:09 -0500 These do affect current timestamps in Chile and Annette Island, Canada. Release 2011b - 2011-02-07 08:44:50 -0500 [not summarized] Release 2011a - 2011-01-24 10:30:16 -0500 [not summarized] Release data2010o - 2010-11-01 09:18:23 -0400 change to the end of DST in Fiji in 2011 Release 2010n - 2010-10-25 08:19:17 -0400 [not summarized] Release 2010m - 2010-09-27 09:24:48 -0400 Hong Kong, Vostok, and zic.c changes Release 2010l - 2010-08-16 06:57:25 -0400 [not summarized] Release 2010k - 2010-07-26 10:42:27 -0400 [not summarized] Release 2010j - 2010-05-10 09:07:48 -0400 changes for Bahía de Banderas and for version naming Release data2010i - 2010-04-16 18:50:45 -0400 the end of DST in Morocco on 2010-08-08 Release data2010h - 2010-04-05 09:58:56 -0400 [not summarized] Release data2010g - 2010-03-24 11:14:53 -0400 [not summarized] Release 2010f - 2010-03-22 09:45:46 -0400 [not summarized] Release data2010e - 2010-03-08 14:24:27 -0500 corrects the Dhaka bug found by Danvin Ruangchan Release data2010d - 2010-03-06 07:26:01 -0500 [not summarized] Release 2010c - 2010-03-01 09:20:58 -0500 changes including KRE's suggestion for earlier initialization of "goahead" and "goback" structure elements Release code2010a - 2010-02-16 10:40:04 -0500 [not summarized] Release data2010b - 2010-01-20 12:37:01 -0500 Mexico changes Release data2010a - 2010-01-18 08:30:04 -0500 changes to Dhaka Release data2009u - 2009-12-26 08:32:28 -0500 changes to DST in Bangladesh Release 2009t - 2009-12-21 13:24:27 -0500 [not summarized] Release data2009s - 2009-11-14 10:26:32 -0500 (cosmetic) Antarctica change and the DST-in-Fiji-in-2009-and-2010 change Release 2009r - 2009-11-09 10:10:31 -0500 "antarctica" and "tz-link.htm" changes Release 2009q - 2009-11-02 09:12:40 -0500 with two corrections as reported by Eric Muller and Philip Newton Release data2009p - 2009-10-23 15:05:27 -0400 Argentina (including San Luis) changes (with the correction from Mariano Absatz) Release data2009o - 2009-10-14 16:49:38 -0400 Samoa (commentary only), Pakistan, and Bangladesh changes Release data2009n - 2009-09-22 15:13:38 -0400 added commentary for Argentina and a change to the end of DST in 2009 in Pakistan Release data2009m - 2009-09-03 10:23:43 -0400 Samoa and Palestine changes Release data2009l - 2009-08-14 09:13:07 -0400 Samoa (comments only) and Egypt Release 2009k - 2009-07-20 09:46:08 -0400 [not summarized] Release data2009j - 2009-06-15 06:43:59 -0400 Bangladesh change (with a short turnaround since the DST change is impending) Release 2009i - 2009-06-08 09:21:22 -0400 updating for DST in Bangladesh this year Release 2009h - 2009-05-26 09:19:14 -0400 [not summarized] Release data2009g - 2009-04-20 16:34:07 -0400 Cairo Release data2009f - 2009-04-10 11:00:52 -0400 correct DST in Pakistan Release 2009e - 2009-04-06 09:08:11 -0400 [not summarized] Release 2009d - 2009-03-23 09:38:12 -0400 Morocco, Tunisia, Argentina, and American Astronomical Society changes Release data2009c - 2009-03-16 09:47:51 -0400 change to the start of Cuban DST Release 2009b - 2009-02-09 11:15:22 -0500 [not summarized] Release 2009a - 2009-01-21 10:09:39 -0500 [not summarized] Release data2008i - 2008-10-21 12:10:25 -0400 southamerica and zone.tab files, with Argentina DST rule changes and United States zone reordering and recommenting Release 2008h - 2008-10-13 07:33:56 -0400 [not summarized] Release 2008g - 2008-10-06 09:03:18 -0400 Fix a broken HTML anchor and update Brazil's DST transitions; there's also a slight reordering of information in tz-art.htm. Release data2008f - 2008-09-09 22:33:26 -0400 [not summarized] Release 2008e - 2008-07-28 14:11:17 -0400 changes by Arthur David Olson and Jesper Nørgaard Welen Release data2008d - 2008-07-07 09:51:38 -0400 changes by Arthur David Olson, Paul Eggert, and Rodrigo Severo Release data2008c - 2008-05-19 17:48:03 -0400 Pakistan, Morocco, and Mongolia Release data2008b - 2008-03-24 08:30:59 -0400 including renaming Asia/Calcutta to Asia/Kolkata, with a backward link provided Release 2008a - 2008-03-08 05:42:16 -0500 [not summarized] Release 2007k - 2007-12-31 10:25:22 -0500 most importantly, changes to the "southamerica" file based on Argentina's readoption of daylight saving time Release 2007j - 2007-12-03 09:51:01 -0500 1. eliminate the "P" (parameter) macro; 2. the "noncontroversial" changes circulated on the time zone mailing list (less the changes to "logwtmp.c"); 3. eliminate "too many transition" errors when "min" is used in time zone rules; 4. changes by Paul Eggert (including updated information for Venezuela). Release data2007i - 2007-10-30 10:28:11 -0400 changes for Cuba and Syria Release 2007h - 2007-10-01 10:05:51 -0400 changes by Paul Eggert, as well as an updated link to the ICU project in tz-link.htm Release 2007g - 2007-08-20 10:47:59 -0400 changes by Paul Eggert The "leapseconds" file has been updated to incorporate the most recent International Earth Rotation and Reference Systems Service (IERS) bulletin. There's an addition to tz-art.htm regarding the television show "Medium". Release 2007f - 2007-05-07 10:46:46 -0400 changes by Paul Eggert (including Haiti, Turks and Caicos, and New Zealand) changes to zic.c to allow hour values greater than 24 (along with Paul's improved time value overflow checking) Release 2007e - 2007-04-02 10:11:52 -0400 Syria and Honduras changes by Paul Eggert zic.c variable renaming changes by Arthur David Olson Release 2007d - 2007-03-20 08:48:30 -0400 changes by Paul Eggert the elimination of white space at the ends of lines Release 2007c - 2007-02-26 09:09:37 -0500 changes by Paul Eggert Release 2007b - 2007-02-12 09:34:20 -0500 Paul Eggert's proposed change to the quotation handling logic in zic.c. changes to the commentary in "leapseconds" reflecting the IERS announcement that there is to be no positive leap second at the end of June 2007. Release 2007a - 2007-01-08 12:28:29 -0500 changes by Paul Eggert Derick Rethans's Asmara change Oscar van Vlijmen's Easter Island local mean time change symbolic link changes Release 2006p - 2006-11-27 08:54:27 -0500 changes by Paul Eggert Release 2006o - 2006-11-06 09:18:07 -0500 changes by Paul Eggert Release 2006n - 2006-10-10 11:32:06 -0400 changes by Paul Eggert Release 2006m - 2006-10-02 15:32:35 -0400 changes for Uruguay, Palestine, and Egypt by Paul Eggert (minimalist) changes to zic.8 to clarify "until" information Release data2006l - 2006-09-18 12:58:11 -0400 Paul's best-effort work on this coming weekend's Egypt time change Release 2006k - 2006-08-28 12:19:09 -0400 changes by Paul Eggert Release 2006j - 2006-08-21 09:56:32 -0400 changes by Paul Eggert Release code2006i - 2006-08-07 12:30:55 -0400 localtime.c fixes Ken Pizzini's conversion script Release code2006h - 2006-07-24 09:19:37 -0400 adds public domain notices to four files includes a fix for transition times being off by a second adds a new recording to the "arts" file (information courtesy Colin Bowern) Release 2006g - 2006-05-08 17:18:09 -0400 northamerica changes by Paul Eggert Release 2006f - 2006-05-01 11:46:00 -0400 a missing version number problem is fixed (with thanks to Bradley White for catching the problem) Release 2006d - 2006-04-17 14:33:43 -0400 changes by Paul Eggert added new items to tz-arts.htm that were found by Paul Release 2006c - 2006-04-03 10:09:32 -0400 two sets of data changes by Paul Eggert a fencepost error fix in zic.c changes to zic.c and the "europe" file to minimize differences between output produced by the old 32-bit zic and the new 64-bit version Release 2006b - 2006-02-20 10:08:18 -0500 [tz32code2006b + tz64code2006b + tzdata2006b] 64-bit code All SCCS IDs were bumped to "8.1" for this release. Release 2006a - 2006-01-30 08:59:31 -0500 changes by Paul Eggert (in particular, Indiana time zone moves) an addition to the zic manual page to describe how special-case transitions are handled Release 2005r - 2005-12-27 09:27:13 -0500 Canadian changes by Paul Eggert They also add "
" directives to time zone data files and reflect
   changes to warning message logic in "zdump.c" (but with calls to
   "gettext" kept unbundled at the suggestion of Ken Pizzini).
 
 
 Release 2005q - 2005-12-13 09:17:09 -0500
 
   Nothing earth-shaking here:
 	1.  Electronic mail addresses have been removed.
 	2.  Casts of the return value of exit have been removed.
 	3.  Casts of the argument of is.* macros have been added.
 	4.  Indentation in one section of zic.c has been fixed.
 	5.  References to dead URLs in the data files have been dealt with.
 
 
 Release 2005p - 2005-12-05 10:30:53 -0500
 
   "systemv", "tz-link.htm", and "zdump.c" changes
   (less the casts of arguments to the is* macros)
 
 
 Release 2005o - 2005-11-28 10:55:26 -0500
 
   Georgia, Cuba, Nicaragua, and Jordan changes by Paul Eggert
 
   zdump.c lint fixes by Arthur David Olson
 
 
 Release 2005n - 2005-10-03 09:44:09 -0400
 
   changes by Paul Eggert (both the Uruguay changes and the Kyrgyzstan
   et al. changes)
 
 
 Release 2005m - 2005-08-29 12:15:40 -0400
 
   changes by Paul Eggert (with a small tweak to the tz-art change)
 
   a declaration of an unused variable has been removed from zdump.c
 
 
 Release 2005l - 2005-08-22 12:06:39 -0400
 
   changes by Paul Eggert
 
   overflow/underflow checks by Arthur David Olson, minus changes to
   the "Theory" file about the pending addition of 64-bit data (I grow
   less confident of the changes being accepted with each passing day,
   and the changes no longer increase the data files nine-fold--there's
   less than a doubling in size by my local Sun's reckoning)
 
 
 Release 2005k - 2005-07-14 14:14:24 -0400
 
   The "leapseconds" file has been edited to reflect the recently
   announced leap second at the end of 2005.
 
   I've also deleted electronic mail addresses from the files as an
   anti-spam measure.
 
 
 Release 2005j - 2005-06-13 14:34:13 -0400
 
   These reflect changes to limit the length of time zone abbreviations
   and the characters used in those abbreviations.
 
   There are also changes to handle POSIX-style "quoted" timezone
   environment variables.
 
   The changes were circulated on the time zone mailing list; the only
   change since then was the removal of a couple of minimum-length of
   abbreviation checks.
 
 
 Release data2005i - 2005-04-21 15:04:16 -0400
 
   changes (most importantly to Nicaragua and Haiti) by Paul Eggert
 
 
 Release 2005h - 2005-04-04 11:24:47 -0400
 
   changes by Paul Eggert
 
   minor changes to Makefile and zdump.c to produce more useful output
   when doing a "make typecheck"
 
 
 Release 2005g - 2005-03-14 10:11:21 -0500
 
   changes by Paul Eggert (a change to current DST rules in Uruguay and
   an update to a link to time zone software)
 
 
 Release 2005f - 2005-03-01 08:45:32 -0500
 
   data and documentation changes by Paul Eggert
 
 
 Release 2005e - 2005-02-10 15:59:44 -0500
 
   [not summarized]
 
 
 Release code2005d - 2005-01-31 09:21:47 -0500
 
   make zic complain about links to links if the -v flag is used
 
   have "make public" do more code checking
 
   add an include to "localtime.c" for the benefit of gcc systems
 
 
 Release 2005c - 2005-01-17 18:36:29 -0500
 
   get better results when mktime runs on a system where time_t is double
 
   changes to the data files (most importantly to Paraguay)
 
 
 Release 2005b - 2005-01-10 09:19:54 -0500
 
   Get localtime and gmtime working on systems with exotic time_t types.
 
   Update the leap second commentary in the "leapseconds" file.
 
 
 Release 2005a - 2005-01-01 13:13:44 -0500
 
   [not summarized]
 
 
 Release code2004i - 2004-12-14 13:42:58 -0500
 
   Deal with systems where time_t is unsigned.
 
 
 Release code2004h - 2004-12-07 11:40:18 -0500
 
   64-bit-time_t changes
 
 
 Release 2004g - 2004-11-02 09:06:01 -0500
 
   update to Cuba (taking effect this weekend)
 
   other changes by Paul Eggert
 
   correction of the spelling of Oslo
 
   changed versions of difftime.c and private.h
 
 
 Release code2004f - 2004-10-21 10:25:22 -0400
 
   Cope with wide-ranging tm_year values.
 
 
 Release 2004e - 2004-10-11 14:47:21 -0400
 
   Brazil/Argentina/Israel changes by Paul Eggert
 
   changes to tz-link.htm by Paul
 
   one small fix to Makefile
 
 
 Release 2004d - 2004-09-22 08:27:29 -0400
 
   Avoid overflow problems when TM_YEAR_BASE is added to an integer.
 
 
 Release 2004c - 2004-08-11 12:06:26 -0400
 
   asctime-related changes
 
   (variants of) some of the documentation changes suggested by Paul Eggert
 
 
 Release 2004b - 2004-07-19 14:33:35 -0400
 
   data changes by Paul Eggert - most importantly, updates for Argentina
 
 
 Release 2004a - 2004-05-27 12:00:47 -0400
 
   changes by Paul Eggert
 
   Handle DST transitions that occur at the end of a month in some
   years but at the start of the following month in other years.
 
   Add a copy of the correspondence that's the basis for claims about
   DST in the Navajo Nation.
 
 
 Release 2003e - 2003-12-15 09:36:47 -0500
 
   changes by Arthur David Olson (primarily code changes)
 
   changes by Paul Eggert (primarily data changes)
 
   minor changes to "Makefile" and "northamerica" (in the latter case,
   optimization of the "Toronto" rules)
 
 
 Release 2003d - 2003-10-06 09:34:44 -0400
 
   changes by Paul Eggert
 
 
 Release 2003c - 2003-09-16 10:47:05 -0400
 
   Fix bad returns in zic.c's inleap function.
   Thanks to Bradley White for catching the problem!
 
 
 Release 2003b - 2003-09-16 07:13:44 -0400
 
   Add a "--version" option (and documentation) to the zic and zdump commands.
 
   changes to overflow/underflow checking in zic
 
   a localtime typo fix.
 
   Update the leapseconds and tz-art.htm files.
 
 
 Release 2003a - 2003-03-24 09:30:54 -0500
 
   changes by Paul Eggert
 
   a few additions and modifications to the tz-art.htm file
 
 
 Release 2002d - 2002-10-15 13:12:42 -0400
 
   changes by Paul Eggert, less the "Britain (UK)" change in iso3166.tab
 
   There's also a new time zone quote in "tz-art.htm".
 
 
 Release 2002c - 2002-04-04 11:55:20 -0500
 
   changes by Paul Eggert
 
   Change zic.c to avoid creating symlinks to files that don't exist.
 
 
 Release 2002b - 2002-01-28 12:56:03 -0500
 
   [These change notes are for Release 2002a, which was corrupted.
   2002b was a corrected version of 2002a.]
 
   changes by Paul Eggert
 
   Update the "leapseconds" file to note that there'll be no leap
   second at the end of June, 2002.
 
   Change "zic.c" to deal with a problem in handling the "Asia/Bishkek" zone.
 
   Change to "difftime.c" to avoid sizeof problems.
 
 
 Release 2001d - 2001-10-09 13:31:32 -0400
 
   changes by Paul Eggert
 
 
 Release 2001c - 2001-06-05 13:59:55 -0400
 
   changes by Paul Eggert and Andrew Brown
 
 
 Release 2001b - 2001-04-05 16:44:38 -0400
 
   changes by Paul Eggert (modulo jnorgard's typo fix)
 
   tz-art.htm has been HTMLified.
 
 
 Release 2001a - 2001-03-13 12:57:44 -0500
 
   changes by Paul Eggert
 
   An addition to the "leapseconds" file: comments with the text of the
   latest IERS leap second notice.
 
   Trailing white space has been removed from data file lines, and
   repeated spaces in "Rule Jordan" lines in the "asia" file have been
   converted to tabs.
 
 
 Release 2000h - 2000-12-14 15:33:38 -0500
 
   changes by Paul Eggert
 
   one typo fix in the "art" file
 
   With providence, this is the last update of the millennium.
 
 
 Release 2000g - 2000-10-10 11:35:22 -0400
 
   changes by Paul Eggert
 
   correction of John Mackin's name submitted by Robert Elz
 
   Garry Shandling's Daylight Saving Time joke (!?!) from the recent
   Emmy Awards broadcast.
 
 
 Release 2000f - 2000-08-10 09:31:58 -0400
 
   changes by Paul Eggert
 
   Added information in "tz-art.htm" on a Seinfeld reference to DST.
 
   Error checking and messages in the "yearistype" script have been
   improved.
 
 
 Release 2000e - 2000-07-31 09:27:54 -0400
 
   data changes by Paul Eggert
 
   a change to the default value of the defined constant HAVE_STRERROR
 
   the addition of a Dave Barry quote on DST to the tz-arts file
 
 
 Release 2000d - 2000-04-20 15:43:04 -0400
 
   changes to the documentation and code of strftime for C99 conformance
 
   a bug fix for date.c
 
   These are based on (though modified from) changes by Paul Eggert.
 
 
 Release 2000c - 2000-03-04 10:31:43 -0500
 
   changes by Paul Eggert
 
 
 Release 2000b - 2000-02-21 12:16:29 -0500
 
   changes by Paul Eggert and Joseph Myers
 
   modest tweaks to the tz-art.htm and tz-link.htm files
 
 
 Release 2000a - 2000-01-18 09:21:26 -0500
 
   changes by Paul Eggert
 
   The two hypertext documents have also been renamed.
 
 
 Release code1999i-data1999j - 1999-11-15 18:43:22 -0500
 
   Paul Eggert's changes
 
   additions to the "zic" manual page and the "Arts.htm" file
 
 
 Release code1999h-data1999i - 1999-11-08 14:55:21 -0500
 
   [not summarized]
 
 
 Release data1999h - 1999-10-07 03:50:29 -0400
 
   changes by Paul Eggert to "europe" (most importantly, fixing
   Lithuania and Estonia)
 
 
 Release 1999g - 1999-09-28 11:06:18 -0400
 
   data changes by Paul Eggert (most importantly, the change for
   Lebanon that buys correctness for this coming Sunday)
 
   The "code" file contains changes to "Makefile" and "checktab.awk" to
   allow better checking of time zone files before they are published.
 
 
 Release 1999f - 1999-09-23 09:48:14 -0400
 
   changes by Arthur David Olson and Paul Eggert
 
 
 Release 1999e - 1999-08-17 15:20:54 -0400
 
   changes circulated by Paul Eggert, although the change to handling
   of DST-specifying timezone names has been commented out for now
   (search for "XXX" in "localtime.c" for details).  These files also
   do not make any changes to the start of DST in Brazil.
 
   In addition to Paul's changes, there are updates to "Arts.htm" and
   cleanups of URLs.
 
 
 Release 1999d - 1999-03-30 11:31:07 -0500
 
   changes by Paul Eggert
 
   The Makefile's "make public" rule has also been changed to do a test
   compile of each individual time zone data file (which should help
   avoid problems such as the one we had with Nicosia).
 
 
 Release 1999c - 1999-03-25 09:47:47 -0500
 
   changes by Paul Eggert, most importantly the change for Chile.
 
 
 Release 1999b - 1999-02-01 17:51:44 -0500
 
   changes by Paul Eggert
 
   code changes (suggested by Mani Varadarajan, mani at be.com) for
   correct handling of symbolic links when building using a relative directory
 
   code changes to generate correct messages for failed links
 
   updates to the URLs in Arts.htm
 
 
 Release 1999a - 1999-01-19 16:20:29 -0500
 
   error message internationalizations and corrections in zic.c and
   zdump.c (as suggested by Vladimir Michl, vladimir.michl at upol.cz,
   to whom thanks!)
 
 
 Release code1998h-data1998i - 1998-10-01 09:56:10 -0400
 
   changes for Brazil, Chile, and Germany
 
   support for use of "24:00" in the input files for the time zone compiler
 
 
 Release code1998g-data1998h - 1998-09-24 10:50:28 -0400
 
   changes by Paul Eggert
 
   correction to a define in the "private.h" file
 
 
 Release data1998g - 1998-08-11 03:28:35 -0000
   [tzdata1998g.tar.gz is missing!]
 
   Lithuanian change provided by mgedmin at pub.osf.it
 
   Move creation of the GMT link with Etc/GMT to "etcetera" (from
   "backward") to ensure that the GMT file is created even where folks
   don't want the "backward" links (as suggested by Paul Eggert).
 
 
 Release data1998f - 1998-07-20 13:50:00 -0000
   [tzdata1998f.tar.gz is missing!]
 
   Update the "leapseconds" file to include the newly-announced
   insertion at the end of 1998.
 
 
 Release code1998f - 1998-06-01 10:18:31 -0400
 
   addition to localtime.c by Guy Harris
 
 
 Release 1998e - 1998-05-28 09:56:26 -0400
 
   The Makefile is changed to produce zoneinfo-posix rather than
   zoneinfo/posix, and to produce zoneinfo-leaps rather than
   zoneinfo/right.
 
   data changes by Paul Eggert
 
   changes from Guy Harris to provide asctime_r and ctime_r
 
   A usno1998 file (substantially identical to usno1997) has been added.
 
 
 Release 1998d - 1998-05-14 11:58:34 -0400
 
   changes to comments (in particular, elimination of references to CIA maps).
   "Arts.htm", "WWW.htm", "asia", and "australasia" are the only places
   where changes occur.
 
 
 Release 1998c - 1998-02-28 12:32:26 -0500
 
   changes by Paul Eggert (save the "French correction," on which I'll
   wait for the dust to settle)
 
   symlink changes
 
   changes and additions to Arts.htm
 
 
 Release 1998b - 1998-01-17 14:31:51 -0500
 
   URL cleanups and additions
 
 
 Release 1998a - 1998-01-13 12:37:35 -0500
 
   changes by Paul Eggert
 
 
 Release code1997i-data1997k - 1997-12-29 09:53:41 -0500
 
   changes by Paul Eggert, with minor modifications from Arthur David
   Olson to make the files more browser friendly
 
 
 Release code1997h-data1997j - 1997-12-18 17:47:35 -0500
 
   minor changes to put "TZif" at the start of each timezone information file
 
   a rule has also been added to the Makefile so you can
 	make zones
   to just recompile the zone information files (rather than doing a
   full "make install" with its other effects).
 
 
 Release data1997i - 1997-10-07 08:45:38 -0400
 
   changes to Africa by Paul Eggert
 
 
 Release code1997g-data1997h - 1997-09-04 16:56:54 -0400
 
   corrections for Uruguay (and other locations)
 
   Arthur David Olson's simple-minded fix allowing mktime to both
   correctly handle leap seconds and correctly handle tm_sec values
   upon which arithmetic has been performed.
 
 
 Release code1997f-data1997g - 1997-07-19 13:15:02 -0400
 
   Paul Eggert's updates
 
   a small change to a function prototype;
 
   "Music" has been renamed "Arts.htm", HTMLified, and augmented to
   include information on Around the World in Eighty Days.
 
 
 Release code1997e-data1997f - 1997-05-03 18:52:34 -0400
 
   fixes to zic's error handling
 
   changes inspired by the item circulated on Slovenia
 
   The description of Web resources has been HTMLified for browsing
   convenience.
 
   A new piece of tz-related music has been added to the "Music" file.
 
 
 Release code1997d-data1997e - 1997-03-29 12:48:52 -0500
 
   Paul Eggert's latest suggestions
 
 
 Release code1997c-data1997d - 1997-03-07 20:37:54 -0500
 
   changes to "zic.c" to correct performance of the "-s" option
 
   a new file "usno1997"
 
 
 Release data1997c - 1997-03-04 09:58:18 -0500
 
   changes in Israel
 
 
 Release 1997b - 1997-02-27 18:34:19 -0500
 
   The data file incorporates the 1997 leap second.
 
   The code file incorporates Arthur David Olson's take on the
   zic/multiprocessor/directory-creation situation.
 
 
 Release 1997a - 1997-01-21 09:11:10 -0500
 
   Paul Eggert's Antarctica (and other changes)
 
   Arthur David Olson finessed the "getopt" issue by checking against
   both -1 and EOF (regardless of POSIX, SunOS 4.1.1's manual says -1
   is returned while SunOS 5.5's manual says EOF is returned).
 
 
 Release code1996o-data1996n - 1996-12-27 21:42:05 -0500
 
   Paul Eggert's latest changes
 
 
 Release code1996n - 1996-12-16 09:42:02 -0500
 
   link snapping fix from Bruce Evans (via Garrett Wollman)
 
 
 Release data1996m - 1996-11-24 02:37:34 -0000
   [tzdata1996m.tar.gz is missing!]
 
   Paul Eggert's batch of changes
 
 
 Release code1996m-data1996l - 1996-11-05 14:00:12 -0500
 
   No functional changes here; the files have simply been changed to
   make more use of ISO style dates in comments. The names of the above
   files now include the year in full.
 
 
 Release code96l - 1996-09-08 17:12:20 -0400
 
   tzcode96k was missing a couple of pieces.
 
 
 Release 96k - 1996-09-08 16:06:22 -0400
 
   the latest round of changes from Paul Eggert
 
   the recent Year 2000 material
 
 
 Release code96j - 1996-07-30 13:18:53 -0400
 
   Set sp->typecnt as suggested by Timothy Patrick Murphy.
 
 
 Release code96i - 1996-07-27 20:11:35 -0400
 
   Paul's suggested patch for strftime %V week numbers
 
 
 Release data96i - 1996-07-01 18:13:04 -0400
 
   "northamerica" and "europe" changes by Paul Eggert
 
 
 Release code96h - 1996-06-05 08:02:21 -0400
 
   fix for handling transitions specified in Universal Time
 
   Some "public domain" notices have also been added.
 
 
 Release code96g - 1996-05-16 14:00:26 -0400
 
   fix for the simultaneous-DST-and-zone-change challenge
 
 
 Release data96h - 1996-05-09 17:40:51 -0400
 
   changes by Paul Eggert
 
 
 Release code96f-data96g - 1996-05-03 03:09:59 -0000
   [tzcode96f.tar.gz + tzdata96g.tar.gz are both missing!]
 
   The changes get us some of the way to fixing the problems noted in Paul
   Eggert's letter yesterday (in addition to a few others).  The approach
   has been to make zic a bit smarter about figuring out what time zone
   abbreviations apply just after the time specified in the "UNTIL" part
   of a zone line.  Putting the smarts in zic means avoiding having
   transition times show up in both "Zone" lines and "Rule" lines, which
   in turn avoids multiple transition time entries in time zone files.
   (This also makes the zic input files such as "europe" a bit shorter and
   should ease maintenance.)
 
 
 Release data96f - 1996-04-19 19:20:03 -0000
   [tzdata96f.tar.gz is missing!]
 
   The only changes are to the "northamerica" file; the time zone
   abbreviation for Denver is corrected to MST (and MDT), and the
   comments for Mexico have been updated.
 
 
 Release data96e - 1996-03-19 17:37:26 -0500
 
   Proposals by Paul Eggert, in particular the Portugal change that
   comes into play at the end of this month.
 
 
 Release data96d - 1996-03-18 20:49:39 -0500
 
   [not summarized]
 
 
 Release code96e - 1996-02-29 15:43:27 -0000
   [tzcode96e.tar.gz is missing!]
 
   internationalization changes and the fix to the documentation for strftime
 
 
 Release code96d-data96c - 1996-02-12 11:05:27 -0500
 
   The "code" file simply updates Bob Kridle's electronic address.
 
   The "data" file updates rules for Mexico.
 
 
 Release data96b - 1996-01-27 15:44:42 -0500
 
   Kiribati change
 
 
 Release code96c - 1996-01-16 16:58:15 -0500
 
   leap-year streamlining and binary-search changes
 
   fix to newctime.3
 
 
 Release code96b - 1996-01-10 20:42:39 -0500
 
   fixes and enhancements from Paul Eggert, including code that
   emulates the behavior of recent versions of the SunOS "date"
   command.
 
 
 Release 96a - 1996-01-06 09:08:24 -0500
 
   Israel updates
 
   fixes to strftime.c for correct ISO 8601 week number generation,
   plus support for two new formats ('G' and 'g') to give ISO 8601 year
   numbers (which are not necessarily the same as calendar year numbers)
 
 
 Release code95i-data95m - 1995-12-21 12:46:47 -0500
 
   The latest revisions from Paul Eggert are included, the usno1995
   file has been updated, and a new file ("WWW") covering useful URLs
   has been added.
 
 
 Release code95h-data95l - 1995-12-19 18:10:12 -0500
 
   A simplification of a macro definition, a change to data for Sudan,
   and (for last minute shoppers) notes in the "Music" file on the CD
   "Old Man Time".
 
 
 Release code95g-data95k - 1995-10-30 10:32:47 -0500
 
   (slightly reformatted) 8-bit-clean proposed patch
 
   minor patch: US/Eastern -> America/New_York
 
   snapshot of the USNO's latest data ("usno1995")
 
   some other minor cleanups
 
 
 Release code95f-data95j - 1995-10-28 21:01:34 -0000
   [tzcode95f.tar.gz + tzdata95j.tar.gz are both missing!]
 
   European cleanups
 
   support for 64-bit time_t's
 
   optimization in localtime.c
 
 
 Release code95e - 1995-10-13 13:23:57 -0400
 
   the mktime change to scan from future to past when trying to find time zone
   offsets
 
 
 Release data95i - 1995-09-26 10:43:26 -0400
 
   For Canada/Central, guess that the Sun customer's "one week too
   early" was just a approximation, and the true error is one month
   too early.  This is consistent with the rest of Canada.
 
 
 Release data95h - 1995-09-21 11:26:48 -0400
 
   latest changes from Paul Eggert
 
 
 Release code95d - 1995-09-14 11:14:45 -0400
 
   the addition of a "Music" file, which documents four recorded
   versions of the tune "Save That Time".
 
 
 Release data95g - 1995-09-01 17:21:36 -0400
 
   "yearistype" correction
 
 
 Release data95f - 1995-08-28 20:46:56 -0400
 
   Paul Eggert's change to the australasia file
 
 
 Release data95e - 1995-07-08 18:02:34 -0400
 
   The only change is a leap second at the end of this year.
   Thanks to Bradley White for forwarding news on the leap second.
 
 
 Release data95d - 1995-07-03 13:26:22 -0400
 
   Paul Eggert's changes
 
 
 Release data95c - 1995-07-02 19:19:28 -0400
 
   changes to "asia", "backward", "europe", and "southamerica"
   (read: northamericacentrics need not apply)
 
 
 Release code95c - 1995-03-13 14:00:46 -0500
 
   one-line fix for sign extension problems in detzcode
 
 
 Release 95b - 1995-03-04 11:22:38 -0500
 
   Minor changes in both:
 
   The "code" file contains a workaround for the lack of "unistd.h" in
   Microsoft C++ version 7.
 
   The "data" file contains a fixed "Link" for America/Shiprock.
 
 
 Release 94h - 1994-12-10 12:51:14 -0500
 
   The files:
 
   *	incorporate the changes to "zdump" and "date" to make changes to
 	the "TZ" environment variable permanent;
 
   *	incorporate the table changes by Paul Eggert;
 
   *	include (and document) support for universal time specifications in
 	data files - but do not (yet) include use of this feature in the
 	data files.
 
   Think of this as "TZ Classic" - the software has been set up not to break if
   universal time shows up in its input, and data entries have been
   left as is so as not to break existing implementations.
 
 
 Release data94f - 1994-08-20 12:56:09 -0400
 
   (with thanks!) the latest data updates from Paul Eggert
 
 
 Release data94e - 1994-06-04 13:13:53 -0400
 
   [not summarized]
 
 
 Release code94g - 1994-05-05 12:14:07 -0400
 
   fix missing "optind.c" and a reference to it in the Makefile
 
 
 Release code94f - 1994-05-05 13:00:33 -0000
   [tzcode94f.tar.gz is missing!]
 
   changes to avoid overflow in difftime, as well as changes to cope
   with the 52/53 challenge in strftime
 
 
 Release code94e - 1994-03-30 23:32:59 -0500
 
   change for the benefit of PCTS
 
 
 Release 94d - 1994-02-24 15:42:25 -0500
 
   Avoid clashes with POSIX semantics for zones such as GMT+4.
 
   Some other very minor housekeeping is also present.
 
 
 Release code94c - 1994-02-10 08:52:40 -0500
 
   Fix bug where mkdirs was broken unless you compile with
   -fwritable-strings (which is generally losing to do).
 
 
 Release 94b - 1994-02-07 10:04:33 -0500
 
   work by Paul Eggert who notes:
 
   I found another book of time zone histories by E W Whitman; it's not
   as extensive as Shanks but has a few goodies of its own.  I used it
   to update the tables.  I also fixed some more as a result of
   correspondence with Adam David and Peter Ilieve, and move some stray
   links from 'europe' to 'backward'.  I corrected some scanning errors
   in usno1989.
 
   As far as the code goes, I fixed zic to allow years in the range
   INT_MIN to INT_MAX; this fixed a few boundary conditions around 1900.
   And I cleaned up the zic documentation a little bit.
 
 
 Release data94a - 1994-02-03 08:58:54 -0500
 
   It simply incorporates the recently announced leap second into the
   "leapseconds" file.
 
 
 Release 93g - 1993-11-22 17:28:27 -0500
 
   Paul Eggert has provided a good deal of historic information (based
   on Shanks), and there are some code changes to deal with the buglets
   that crawled out in dealing with the new information.
 
 
 Release 93f - 1993-10-15 12:27:46 -0400
 
   Paul Eggert's changes
 
 
 Release 93e - 1993-09-05 21:21:44 -0400
 
   This has updated data for Israel, England, and Kwajalein.  There's
   also an update to "zdump" to cope with Kwajalein's 24-hour jump.
   Thanks to Paul Eggert and Peter Ilieve for the changes.
 
 
 Release 93d - 1993-06-17 23:34:17 -0400
 
   new fix and new data on Israel
 
 
 Release 93c - 1993-06-06 19:31:55 -0400
 
   [not summarized]
 
 
 Release 93b - 1993-02-02 14:53:58 -0500
 
   updated "leapseconds" file
 
 
 Release 93 - 1993-01-08 07:01:06 -0500
 
   At kre's suggestion, the package has been split in two - a code piece
   (which also includes documentation) that's only of use to folks who
   want to recompile things and a data piece useful to anyone who can
   run "zic".
 
   The new version has a few changes to the data files, a few
   portability changes, and an off-by-one fix (with thanks to
   Tom Karzes at deshaw.com for providing a description and a
   solution).
 
 
 Release 92c - 1992-11-21 17:35:36 -0000
   [tz92c.tar.Z is missing!]
 
   The fallout from the latest round of DST transitions.
 
   There are changes for Portugal, Saskatchewan, and "Pacific-New";
   there's also a change to "zic.c" that makes it portable to more systems.
 
 
 Release 92 - 1992-04-25 18:17:03 -0000
   [tz92.tar.Z is missing!]
 
   By popular demand (well, at any rate, following a request by kre at munnari)
 
 
 The 1989 update of the time zone package featured:
 
   *	POSIXization (including interpretation of POSIX-style TZ environment
 	variables, provided by Guy Harris),
   *	ANSIfication (including versions of "mktime" and "difftime"),
   *	SVIDulation (an "altzone" variable)
   *	MACHination (the "gtime" function)
   *	corrections to some time zone data (including corrections to the rules
 	for Great Britain and New Zealand)
   *	reference data from the United States Naval Observatory for folks who
 	want to do additional time zones
   *	and the 1989 data for Saudi Arabia.
 
   (Since this code will be treated as "part of the implementation" in some
   places and as "part of the application" in others, there's no good way to
   name functions, such as timegm, that are not part of the proposed ANSI C
   standard; such functions have kept their old, underscore-free names in this
   update.)
 
   And the "dysize" function has disappeared; it was present to allow
   compilation of the "date" command on old BSD systems, and a version of "date"
   is now provided in the package.  The "date" command is not created when you
   "make all" since it may lack options provided by the version distributed with
   your operating system, or may not interact with the system in the same way
   the native version does.
 
   Since POSIX frowns on correct leap second handling, the default behavior of
   the "zic" command (in the absence of a "-L" option) has been changed to omit
   leap second information from its output files.
 
 
 -----
 Notes
 
 This file contains copies of the part of each release announcement
 that talks about the changes in that release.  The text has been
 adapted and reformatted for the purposes of this file.
 
 Traditionally a release R consists of a pair of tarball files,
 tzcodeR.tar.gz and tzdataR.tar.gz.  However, some releases (e.g.,
 code2010a, data2012c) consist of just one or the other tarball, and a
 few (e.g., code2012c-data2012d) have tarballs with mixed version
 numbers.  Recent releases also come in an experimental format
 consisting of a single tarball tzdb-R.tar.lz with extra data.
 
 Release timestamps are taken from the release's commit (for newer,
 Git-based releases), from the newest file in the tarball (for older
 releases, where this info is available) or from the email announcing
 the release (if all else fails; these are marked with a time zone
 abbreviation of -0000 and an "is missing!" comment).
 
 Earlier versions of the code and data were not announced on the tz
 list and are not summarized here.
 
 This file is in the public domain.
 
 Local Variables:
 coding: utf-8
 End:
diff --git a/contrib/tzdata/asia b/contrib/tzdata/asia
index def9b204c053..6e3ea4b36e7e 100644
--- a/contrib/tzdata/asia
+++ b/contrib/tzdata/asia
@@ -1,3952 +1,3952 @@
 # tzdb data for Asia and environs
 
 # This file is in the public domain, so clarified as of
 # 2009-05-17 by Arthur David Olson.
 
 # This file is by no means authoritative; if you think you know better,
 # go ahead and edit the file (and please send any changes to
 # tz@iana.org for general use in the future).  For more, please see
 # the file CONTRIBUTING in the tz distribution.
 
 # From Paul Eggert (2019-07-11):
 #
 # Unless otherwise specified, the source for data through 1990 is:
 # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition),
 # San Diego: ACS Publications, Inc. (2003).
 # Unfortunately this book contains many errors and cites no sources.
 #
 # Many years ago Gwillim Law wrote that a good source
 # for time zone data was the International Air Transport
 # 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 Russian data circa 1919, a source is:
 # Byalokoz EL. New Counting of Time in Russia since July 1, 1919.
 # (See the 'europe' file for a fuller citation.)
 #
 # The following alphabetic abbreviations appear in these tables
 # (corrections are welcome):
 #	     std  dst
 #	     LMT	Local Mean Time
 #	2:00 EET  EEST	Eastern European Time
 #	2:00 IST  IDT	Israel
 #	5:30 IST	India
 #	7:00 WIB	west Indonesia (Waktu Indonesia Barat)
 #	8:00 WITA	central Indonesia (Waktu Indonesia Tengah)
 #	8:00 CST	China
 #	8:00 HKT  HKST	Hong Kong (HKWT* for Winter Time in late 1941)
 #	8:00 PST  PDT*	Philippines
 #	8:30 KST  KDT	Korea when at +0830
 #	9:00 WIT	east Indonesia (Waktu Indonesia Timur)
 #	9:00 JST  JDT	Japan
 #	9:00 KST  KDT	Korea when at +09
 # *I invented the abbreviations HKWT and PDT; see below.
 # Otherwise, these tables typically use numeric abbreviations like +03
 # and +0330 for integer hour and minute UT offsets.  Although earlier
 # editions invented alphabetic time zone abbreviations for every
 # offset, this did not reflect common practice.
 #
 # See the 'europe' file for Russia and Turkey in Asia.
 
 # From Guy Harris:
 # Incorporates data for Singapore from Robert Elz' asia 1.1, as well as
 # additional information from Tom Yap, Sun Microsystems Intercontinental
 # Technical Support (including a page from the Official Airline Guide -
 # Worldwide Edition).
 
 ###############################################################################
 
 # These rules are stolen from the 'europe' file.
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	EUAsia	1981	max	-	Mar	lastSun	 1:00u	1:00	S
 Rule	EUAsia	1979	1995	-	Sep	lastSun	 1:00u	0	-
 Rule	EUAsia	1996	max	-	Oct	lastSun	 1:00u	0	-
 Rule E-EurAsia	1981	max	-	Mar	lastSun	 0:00	1:00	-
 Rule E-EurAsia	1979	1995	-	Sep	lastSun	 0:00	0	-
 Rule E-EurAsia	1996	max	-	Oct	lastSun	 0:00	0	-
 Rule RussiaAsia	1981	1984	-	Apr	1	 0:00	1:00	-
 Rule RussiaAsia	1981	1983	-	Oct	1	 0:00	0	-
 Rule RussiaAsia	1984	1995	-	Sep	lastSun	 2:00s	0	-
 Rule RussiaAsia	1985	2010	-	Mar	lastSun	 2:00s	1:00	-
 Rule RussiaAsia	1996	2010	-	Oct	lastSun	 2:00s	0	-
 
 # Afghanistan
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Kabul	4:36:48 -	LMT	1890
 			4:00	-	+04	1945
 			4:30	-	+0430
 
 # Armenia
 # From Paul Eggert (2006-03-22):
 # Shanks & Pottenger have Yerevan switching to 3:00 (with Russian DST)
 # in spring 1991, then to 4:00 with no DST in fall 1995, then
 # readopting Russian DST in 1997.  Go with Shanks & Pottenger, even
 # when they disagree with others.  Edgar Der-Danieliantz
 # reported (1996-05-04) that Yerevan probably wouldn't use DST
 # in 1996, though it did use DST in 1995.  IATA SSIM (1991/1998) reports that
 # Armenia switched from 3:00 to 4:00 in 1998 and observed DST after 1991,
 # but started switching at 3:00s in 1998.
 
 # From Arthur David Olson (2011-06-15):
 # While Russia abandoned DST in 2011, Armenia may choose to
 # follow Russia's "old" rules.
 
 # From Alexander Krivenyshev (2012-02-10):
 # According to News Armenia, on Feb 9, 2012,
 # http://newsarmenia.ru/society/20120209/42609695.html
 #
 # The Armenia National Assembly adopted final reading of Amendments to the
 # Law "On procedure of calculation time on the territory of the Republic of
 # Armenia" according to which Armenia [is] abolishing Daylight Saving Time.
 # or
 # (brief)
 # http://www.worldtimezone.com/dst_news/dst_news_armenia03.html
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule Armenia	2011	only	-	Mar	lastSun	 2:00s	1:00	-
 Rule Armenia	2011	only	-	Oct	lastSun	 2:00s	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Yerevan	2:58:00 -	LMT	1924 May  2
 			3:00	-	+03	1957 Mar
 			4:00 RussiaAsia +04/+05	1991 Mar 31  2:00s
 			3:00 RussiaAsia	+03/+04	1995 Sep 24  2:00s
 			4:00	-	+04	1997
 			4:00 RussiaAsia	+04/+05	2011
 			4:00	Armenia	+04/+05
 
 # Azerbaijan
 
 # From Rustam Aliyev of the Azerbaijan Internet Forum (2005-10-23):
 # According to the resolution of Cabinet of Ministers, 1997
 # From Paul Eggert (2015-09-17): It was Resolution No. 21 (1997-03-17).
 # http://code.az/files/daylight_res.pdf
 
 # From Steffen Thorsen (2016-03-17):
 # ... the Azerbaijani Cabinet of Ministers has cancelled switching to
 # daylight saving time....
 # https://www.azernews.az/azerbaijan/94137.html
 # http://vestnikkavkaza.net/news/Azerbaijani-Cabinet-of-Ministers-cancels-daylight-saving-time.html
 # http://en.apa.az/xeber_azerbaijan_abolishes_daylight_savings_ti_240862.html
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Azer	1997	2015	-	Mar	lastSun	 4:00	1:00	-
 Rule	Azer	1997	2015	-	Oct	lastSun	 5:00	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Baku	3:19:24 -	LMT	1924 May  2
 			3:00	-	+03	1957 Mar
 			4:00 RussiaAsia +04/+05	1991 Mar 31  2:00s
 			3:00 RussiaAsia	+03/+04	1992 Sep lastSun  2:00s
 			4:00	-	+04	1996
 			4:00	EUAsia	+04/+05	1997
 			4:00	Azer	+04/+05
 
 # Bahrain
 # See Asia/Qatar.
 
 # Bangladesh
 # From Alexander Krivenyshev (2009-05-13):
 # According to newspaper Asian Tribune (May 6, 2009) Bangladesh may introduce
 # Daylight Saving Time from June 16 to Sept 30
 #
 # Bangladesh to introduce daylight saving time likely from June 16
 # http://www.asiantribune.com/?q=node/17288
 # http://www.worldtimezone.com/dst_news/dst_news_bangladesh02.html
 #
 # "... Bangladesh government has decided to switch daylight saving time from
 # June
 # 16 till September 30 in a bid to ensure maximum use of daylight to cope with
 # crippling power crisis. "
 #
 # The switch will remain in effect from June 16 to Sept 30 (2009) but if
 # implemented the next year, it will come in force from April 1, 2010
 
 # From Steffen Thorsen (2009-06-02):
 # They have finally decided now, but changed the start date to midnight between
 # the 19th and 20th, and they have not set the end date yet.
 #
 # Some sources:
 # https://in.reuters.com/article/southAsiaNews/idINIndia-40017620090601
 # http://bdnews24.com/details.php?id=85889&cid=2
 #
 # Our wrap-up:
 # https://www.timeanddate.com/news/time/bangladesh-daylight-saving-2009.html
 
 # From A. N. M. Kamrus Saadat (2009-06-15):
 # Finally we've got the official mail regarding DST start time where DST start
 # time is mentioned as Jun 19 2009, 23:00 from BTRC (Bangladesh
 # Telecommunication Regulatory Commission).
 #
 # No DST end date has been announced yet.
 
 # From Alexander Krivenyshev (2009-09-25):
 # Bangladesh won't go back to Standard Time from October 1, 2009,
 # instead it will continue DST measure till the cabinet makes a fresh decision.
 #
 # Following report by same newspaper-"The Daily Star Friday":
 # "DST change awaits cabinet decision-Clock won't go back by 1-hr from Oct 1"
 # http://www.thedailystar.net/newDesign/news-details.php?nid=107021
 # http://www.worldtimezone.com/dst_news/dst_news_bangladesh04.html
 
 # From Steffen Thorsen (2009-10-13):
 # IANS (Indo-Asian News Service) now reports:
 # Bangladesh has decided that the clock advanced by an hour to make
 # maximum use of daylight hours as an energy saving measure would
 # "continue for an indefinite period."
 #
 # One of many places where it is published:
 # http://www.thaindian.com/newsportal/business/bangladesh-to-continue-indefinitely-with-advanced-time_100259987.html
 
 # From Alexander Krivenyshev (2009-12-24):
 # According to Bangladesh newspaper "The Daily Star,"
 # Bangladesh will change its clock back to Standard Time on Dec 31, 2009.
 #
 # Clock goes back 1-hr on Dec 31 night.
 # http://www.thedailystar.net/newDesign/news-details.php?nid=119228
 # http://www.worldtimezone.com/dst_news/dst_news_bangladesh05.html
 #
 # "...The government yesterday decided to put the clock back by one hour
 # on December 31 midnight and the new time will continue until March 31,
 # 2010 midnight. The decision came at a cabinet meeting at the Prime
 # Minister's Office last night..."
 
 # From Alexander Krivenyshev (2010-03-22):
 # According to Bangladesh newspaper "The Daily Star,"
 # Cabinet cancels Daylight Saving Time
 # http://www.thedailystar.net/newDesign/latest_news.php?nid=22817
 # http://www.worldtimezone.com/dst_news/dst_news_bangladesh06.html
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Dhaka	2009	only	-	Jun	19	23:00	1:00	-
 Rule	Dhaka	2009	only	-	Dec	31	24:00	0	-
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Dhaka	6:01:40 -	LMT	1890
 			5:53:20	-	HMT	1941 Oct    # Howrah Mean Time?
 			6:30	-	+0630	1942 May 15
 			5:30	-	+0530	1942 Sep
 			6:30	-	+0630	1951 Sep 30
 			6:00	-	+06	2009
 			6:00	Dhaka	+06/+07
 
 # Bhutan
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Thimphu	5:58:36 -	LMT	1947 Aug 15 # or Thimbu
 			5:30	-	+0530	1987 Oct
 			6:00	-	+06
 
 # British Indian Ocean Territory
 # Whitman and the 1995 CIA time zone map say 5:00, but the
 # 1997 and later maps say 6:00.  Assume the switch occurred in 1996.
 # We have no information as to when standard time was introduced;
 # assume it occurred in 1907, the same year as Mauritius (which
 # then contained the Chagos Archipelago).
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Indian/Chagos	4:49:40	-	LMT	1907
 			5:00	-	+05	1996
 			6:00	-	+06
 
 # Brunei
 # See Asia/Kuching.
 
 # Burma / Myanmar
 
 # Milne says 6:24:40 was the meridian of the time ball observatory at Rangoon.
 
 # From Paul Eggert (2017-04-20):
 # Page 27 of Reed & Low (cited for Asia/Kolkata) says "Rangoon local time is
 # used upon the railways and telegraphs of Burma, and is 6h. 24m. 47s. ahead
 # of Greenwich."  This refers to the period before Burma's transition to +0630,
 # a transition for which Shanks is the only source.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Yangon	6:24:47 -	LMT	1880        # or Rangoon
 			6:24:47	-	RMT	1920        # Rangoon local time
 			6:30	-	+0630	1942 May
 			9:00	-	+09	1945 May  3
 			6:30	-	+0630
 Link Asia/Yangon Indian/Cocos
 
 # Cambodia
 # See Asia/Bangkok.
 
 
 # China
 
 # From Phake Nick (2020-04-15):
 # According to this news report:
 # http://news.sina.com.cn/c/2004-09-01/19524201403.shtml
 # on April 11, 1919, newspaper in Shanghai said clocks in Shanghai will spring
 # forward for an hour starting from midnight of that Saturday. The report did
 # not mention what happened in Shanghai thereafter, but it mentioned that a
 # similar trial in Tianjin which ended at October 1st as citizens are told to
 # recede the clock on September 30 from 12:00pm to 11:00pm. The trial at
 # Tianjin got terminated in 1920.
 #
 # From Paul Eggert (2020-04-15):
 # The Returns of Trade and Trade Reports, page 711, says "Daylight saving was
 # given a trial during the year, and from the 12th April to the 1st October
 # the clocks were all set one hour ahead of sun time.  Though the scheme was
 # generally esteemed a success, it was announced early in 1920 that it would
 # not be repeated."
 #
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Shang	1919	only	-	Apr	12	24:00	1:00	D
 Rule	Shang	1919	only	-	Sep	30	24:00	0	S
 
 # From Paul Eggert (2018-10-02):
 # The following comes from Table 1 of:
 # Li Yu. Research on the daylight saving movement in 1940s Shanghai.
 # Nanjing Journal of Social Sciences. 2014;(2):144-50.
 # http://oversea.cnki.net/kns55/detail.aspx?dbname=CJFD2014&filename=NJSH201402020
 # The table lists dates only; I am guessing 00:00 and 24:00 transition times.
 # Also, the table lists the planned end of DST in 1949, but the corresponding
 # zone line cuts this off on May 28, when the Communists took power.
 
 # From Phake Nick (2020-04-15):
 #
 # For the history of time in Shanghai between 1940-1942, the situation is
 # actually slightly more complex than the table [below]....  At the time,
 # there were three different authorities in Shanghai, including Shanghai
 # International Settlement, a settlement established by western countries with
 # its own westernized form of government, Shanghai French Concession, similar
 # to the international settlement but is controlled by French, and then the
 # rest of the city of Shanghai, which have already been controlled by Japanese
 # force through a puppet local government (Wang Jingwei regime).  It was
 # additionally complicated by the circumstances that, according to the 1940s
 # Shanghai summer time essay cited in the database, some
 # departments/businesses/people in the Shanghai city itself during that time
 # period, refused to change their clock and instead only changed their opening
 # hours.
 #
 # For example, as quoted in the article, in 1940, other than the authority
 # itself, power, tram, bus companies, cinema, department stores, and other
 # public service organizations have all decided to follow the summer time and
 # spring forward the clock.  On the other hand, the custom office refused to
 # spring forward the clock because of worry on mechanical wear to the physical
 # clock, postal office refused to spring forward because of disruption to
 # business and log-keeping, although they did changed their office hour to
 # match rest of the city.  So is travel agents, and also weather
 # observatory.  It is said both time standards had their own supporters in the
 # city at the time, those who prefer new time standard would have moved their
 # clock while those who prefer the old time standard would keep their clock
 # unchange, and there were different clocks that use different time standard
 # in the city at the time for people who use different time standard to adjust
 # their clock to their preferred time.
 #
 # a. For the 1940 May 31 spring forward, the essay [says] ... "Hong
 # Kong government implemented the spring forward in the same time on
 # the same date as Shanghai".
 #
 # b. For the 1940 fall back, it was said that they initially intended to do
 # so on September 30 00:59 at night, however they postponed it to October 12
 # after discussion with relevant parties. However schools restored to the
 # original schedule ten days earlier.
 #
 # c. For the 1941 spring forward, it is said to start from March 15
 # "following the previous year's method", and in addition to that the essay
 # cited an announcement in 1941 from the Wang regime which said the Special
 # City of Shanghai under Wang regime control will follow the DST rule set by
 # the Settlements, irrespective of the original DST plan announced by the Wang
 # regime for other area under its control(April 1 to September 30). (no idea
 # to situation before that announcement)
 #
 # d. For the 1941 fall back, it was said that the fall back would occurs at
 # the end of September (A newspaper headline cited by the essay, published on
 # October 1, 1941, have the headlines which said "French Concession would
 # rewind to the old clock this morning), but it ultimately didn't happen due
 # to disagreement between the international settlement authority and the
 # French concession authority, and the fall back ultimately occurred on
 # November 1.
 #
 # e. In 1941 December, Japan have officially started war with the United
 # States and the United Kingdom, and in Shanghai they have marched into the
 # international settlement, taken over its control
 #
 # f. For the 1942 spring forward, the essay said that the spring forward
 # started on January 31. It said this time the custom office and postal
 # department will also change their clocks, unlike before.
 #
 # g. The essay itself didn't cover any specific changes thereafter until the
 # end of the war, it quoted a November 1942 command from the government of the
 # Wang regime, which claim the daylight saving time applies year round during
 # the war. However, the essay ambiguously said the period is "February 1 to
 # September 30", which I don't really understand what is the meaning of such
 # period in the context of year round implementation here.. More researches
 # might be needed to show exactly what happened during that period of time.
 
 # From Phake Nick (2020-04-15):
 # According to a Japanese tour bus pamphlet in Nanjing area believed to be
 # from around year 1941: http://www.tt-museum.jp/tairiku_0280_nan1941.html ,
 # the schedule listed was in the format of Japanese time.  Which indicate some
 # use of the Japanese time (instead of syncing by DST) might have occurred in
 # the Yangtze river delta area during that period of time although the scope
 # of such use will need to be investigated to determine.
 #
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Shang	1940	only	-	Jun	 1	 0:00	1:00	D
 Rule	Shang	1940	only	-	Oct	12	24:00	0	S
 Rule	Shang	1941	only	-	Mar	15	 0:00	1:00	D
 Rule	Shang	1941	only	-	Nov	 1	24:00	0	S
 Rule	Shang	1942	only	-	Jan	31	 0:00	1:00	D
 Rule	Shang	1945	only	-	Sep	 1	24:00	0	S
 Rule	Shang	1946	only	-	May	15	 0:00	1:00	D
 Rule	Shang	1946	only	-	Sep	30	24:00	0	S
 Rule	Shang	1947	only	-	Apr	15	 0:00	1:00	D
 Rule	Shang	1947	only	-	Oct	31	24:00	0	S
 Rule	Shang	1948	1949	-	May	 1	 0:00	1:00	D
 Rule	Shang	1948	1949	-	Sep	30	24:00	0	S #plan
 
 # From Guy Harris:
 # People's Republic of China.  Yes, they really have only one time zone.
 
 # From Bob Devine (1988-01-28):
 # No they don't.  See TIME mag, 1986-02-17 p.52.  Even though
 # China is across 4 physical time zones, before Feb 1, 1986 only the
 # Peking (Beijing) time zone was recognized.  Since that date, China
 # has two of 'em - Peking's and Ürümqi (named after the capital of
 # the Xinjiang Uyghur Autonomous Region).  I don't know about DST for it.
 #
 # . . .I just deleted the DST table and this editor makes it too
 # painful to suck in another copy.  So, here is what I have for
 # DST start/end dates for Peking's time zone (info from AP):
 #
 #     1986 May 4 - Sept 14
 #     1987 mid-April - ??
 
 # From U. S. Naval Observatory (1989-01-19):
 # CHINA               8 H  AHEAD OF UTC  ALL OF CHINA, INCL TAIWAN
 # CHINA               9 H  AHEAD OF UTC  APR 17 - SEP 10
 
 # From Paul Eggert (2008-02-11):
 # Jim Mann, "A clumsy embrace for another western custom: China on daylight
 # time - sort of", Los Angeles Times, 1986-05-05 ... [says] that China began
 # observing daylight saving time in 1986.
 
 # From P Chan (2018-05-07):
 # The start and end time of DST in China [from 1986 on] should be 2:00
 # (i.e. 2:00 to 3:00 at the start and 2:00 to 1:00 at the end)....
 # Government notices about summer time:
 #
 # 1986-04-12 http://www.zj.gov.cn/attach/zfgb/198608.pdf p.21-22
 # (To establish summer time from 1986. On 4 May, set the clocks ahead one hour
 # at 2 am. On 14 September, set the clocks backward one hour at 2 am.)
 #
 # 1987-02-15 http://www.gov.cn/gongbao/shuju/1987/gwyb198703.pdf p.114
 # (Summer time in 1987 to start from 12 April until 13 September)
 #
 # 1987-09-09 http://www.gov.cn/gongbao/shuju/1987/gwyb198721.pdf p.709
 # (From 1988, summer time to start from 2 am of the first Sunday of mid-April
 # until 2 am of the first Sunday of mid-September)
 #
 # 1992-03-03 http://www.gov.cn/gongbao/shuju/1992/gwyb199205.pdf p.152
 # (To suspend summer time from 1992)
 #
 # The first page of People's Daily on 12 April 1988 stating that summer time
 # to begin on 17 April.
 # http://data.people.com.cn/pic/101p/1988/04/1988041201.jpg
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	PRC	1986	only	-	May	 4	 2:00	1:00	D
 Rule	PRC	1986	1991	-	Sep	Sun>=11	 2:00	0	S
 Rule	PRC	1987	1991	-	Apr	Sun>=11	 2:00	1:00	D
 
 # From Anthony Fok (2001-12-20):
 # BTW, I did some research on-line and found some info regarding these five
 # historic timezones from some Taiwan websites.  And yes, there are official
 # Chinese names for these locales (before 1949).
 #
 # From Jesper Nørgaard Welen (2006-07-14):
 # I have investigated the timezones around 1970 on the
 # https://www.astro.com/atlas site [with provinces and county
 # boundaries summarized below]....  A few other exceptions were two
 # counties on the Sichuan side of the Xizang-Sichuan border,
 # counties Dege and Baiyu which lies on the Sichuan side and are
 # therefore supposed to be GMT+7, Xizang region being GMT+6, but Dege
 # county is GMT+8 according to astro.com while Baiyu county is GMT+6
 # (could be true), for the moment I am assuming that those two
 # counties are mistakes in the astro.com data.
 
 # From Paul Eggert (2017-01-05):
 # Alois Treindl kindly sent me translations of the following two sources:
 #
 # (1)
 # Guo Qing-sheng (National Time-Service Center, CAS, Xi'an 710600, China)
 # Beijing Time at the Beginning of the PRC
 # China Historical Materials of Science and Technology
 # (Zhongguo ke ji shi liao, 中国科技史料). 2003;24(1):5-9.
 # http://oversea.cnki.net/kcms/detail/detail.aspx?filename=ZGKS200301000&dbname=CJFD2003
 # It gives evidence that at the beginning of the PRC, Beijing time was
 # officially apparent solar time!  However, Guo also says that the
 # evidence is dubious, as the relevant institute of astronomy had not
 # been taken over by the PRC yet.  It's plausible that apparent solar
 # time was announced but never implemented, and that people continued
 # to use UT+8.  As the Shanghai radio station (and I presume the
 # observatory) was still under control of French missionaries, it
 # could well have ignored any such mandate.
 #
 # (2)
 # Guo Qing-sheng (Shaanxi Astronomical Observatory, CAS, Xi'an 710600, China)
 # A Study on the Standard Time Changes for the Past 100 Years in China
 # [undated and unknown publication location]
 # It says several things:
 #   * The Qing dynasty used local apparent solar time throughout China.
 #   * The Republic of China instituted Beijing mean solar time effective
 #     the official calendar book of 1914.
 #   * The French Concession in Shanghai set up signal stations in
 #     French docks in the 1890s, controlled by Xujiahui (Zikawei)
 #     Observatory and set to local mean time.
 #   * "From the end of the 19th century" it changed to UT+8.
 #   * Chinese Customs (by then reduced to a tool of foreign powers)
 #     eventually standardized on this time for all ports, and it
 #     became used by railways as well.
 #   * In 1918 the Central Observatory proposed dividing China into
 #     five time zones (see below for details).  This caught on
 #     at first only in coastal areas observing UT+8.
 #   * During WWII all of China was in theory was at UT+7.  In practice
 #     this was ignored in the west, and I presume was ignored in
 #     Japanese-occupied territory.
 #   * Japanese-occupied Manchuria was at UT+9, i.e., Japan time.
 #   * The five-zone plan was resurrected after WWII and officially put into
 #     place (with some modifications) in March 1948.  It's not clear
 #     how well it was observed in areas under Nationalist control.
 #   * The People's Liberation Army used UT+8 during the civil war.
 #
 # An AP article "Shanghai Internat'l Area Little Changed" in the
 # Lewiston (ME) Daily Sun (1939-05-29), p 17, said "Even the time is
 # different - the occupied districts going by Tokyo time, an hour
 # ahead of that prevailing in the rest of Shanghai."  Guess that the
 # Xujiahui Observatory was under French control and stuck with UT +08.
 #
 # In earlier versions of this file, China had many separate Zone entries, but
 # this was based on what were apparently incorrect data in Shanks & Pottenger.
 # This has now been simplified to the two entries Asia/Shanghai and
 # Asia/Urumqi, with the others being links for backward compatibility.
 # Proposed in 1918 and theoretically in effect until 1949 (although in practice
 # mainly observed in coastal areas), the five zones were:
 #
 # Changbai Time ("Long-white Time", Long-white = Heilongjiang area) UT +08:30
 # Now part of Asia/Shanghai; its pre-1970 times are not recorded here.
 # Heilongjiang (except Mohe county), Jilin
 #
 # Zhongyuan Time ("Central plain Time") UT +08
 # Now part of Asia/Shanghai.
 # most of China
 # Milne gives 8:05:43.2 for Xujiahui Observatory time....
 # Guo says Shanghai switched to UT +08 "from the end of the 19th century".
 #
 # Long-shu Time (probably as Long and Shu were two names of the area) UT +07
 # Now part of Asia/Shanghai; its pre-1970 times are not recorded here.
 # Guangxi, Guizhou, Hainan, Ningxia, Sichuan, Shaanxi, and Yunnan;
 # most of Gansu; west Inner Mongolia; east Qinghai; and the Guangdong
 # counties Deqing, Enping, Kaiping, Luoding, Taishan, Xinxing,
 # Yangchun, Yangjiang, Yu'nan, and Yunfu.
 #
 # Xin-zang Time ("Xinjiang-Tibet Time") UT +06
 # This region is now part of either Asia/Urumqi or Asia/Shanghai with
 # current boundaries uncertain; times before 1970 for areas that
 # disagree with Ürümqi or Shanghai are not recorded here.
 # The Gansu counties Aksay, Anxi, Dunhuang, Subei; west Qinghai;
 # the Guangdong counties  Xuwen, Haikang, Suixi, Lianjiang,
 # Zhanjiang, Wuchuan, Huazhou, Gaozhou, Maoming, Dianbai, and Xinyi;
 # east Tibet, including Lhasa, Chamdo, Shigaise, Jimsar, Shawan and Hutubi;
 # east Xinjiang, including Ürümqi, Turpan, Karamay, Korla, Minfeng, Jinghe,
 # Wusu, Qiemo, Xinyan, Wulanwusu, Jinghe, Yumin, Tacheng, Tuoli, Emin,
 # Shihezi, Changji, Yanqi, Heshuo, Tuokexun, Tulufan, Shanshan, Hami,
 # Fukang, Kuitun, Kumukuli, Miquan, Qitai, and Turfan.
 #
 # Kunlun Time UT +05:30
 # This region is now in the same status as Xin-zang Time (see above).
 # West Tibet, including Pulan, Aheqi, Shufu, Shule;
 # West Xinjiang, including Aksu, Atushi, Yining, Hetian, Cele, Luopu, Nileke,
 # Zhaosu, Tekesi, Gongliu, Chabuchaer, Huocheng, Bole, Pishan, Suiding,
 # and Yarkand.
 
 # From Luther Ma (2009-10-17):
 # Almost all (>99.9%) ethnic Chinese (properly ethnic Han) living in
 # Xinjiang use Chinese Standard Time. Some are aware of Xinjiang time,
 # but have no need of it. All planes, trains, and schools function on
 # what is called "Beijing time." When Han make an appointment in Chinese
 # they implicitly use Beijing time.
 #
 # On the other hand, ethnic Uyghurs, who make up about half the
 # population of Xinjiang, typically use "Xinjiang time" which is two
 # hours behind Beijing time, or UT +06. The government of the Xinjiang
 # Uyghur Autonomous Region, (XAUR, or just Xinjiang for short) as well as
 # local governments such as the Ürümqi city government use both times in
 # publications, referring to what is popularly called Xinjiang time as
 # "Ürümqi time." When Uyghurs make an appointment in the Uyghur language
 # they almost invariably use Xinjiang time.
 #
 # (Their ethnic Han compatriots would typically have no clue of its
 # widespread use, however, because so extremely few of them are fluent in
 # Uyghur, comparable to the number of Anglo-Americans fluent in Navajo.)
 #
 # (...As with the rest of China there was a brief interval ending in 1990
 # or 1991 when summer time was in use.  The confusion was severe, with
 # the province not having dual times but four times in use at the same
 # time. Some areas remained on standard Xinjiang time or Beijing time and
 # others moving their clocks ahead.)
 
 # From Luther Ma (2009-11-19):
 # With the risk of being redundant to previous answers these are the most common
 # English "transliterations" (w/o using non-English symbols):
 #
 # 1. Wulumuqi...
 # 2. Kashi...
 # 3. Urumqi...
 # 4. Kashgar...
 # ...
 # 5. It seems that Uyghurs in Ürümqi has been using Xinjiang since at least the
 # 1960's. I know of one Han, now over 50, who grew up in the surrounding
 # countryside and used Xinjiang time as a child.
 #
 # 6. Likewise for Kashgar and the rest of south Xinjiang I don't know of any
 # start date for Xinjiang time.
 #
 # Without having access to local historical records, nor the ability to legally
 # publish them, I would go with October 1, 1949, when Xinjiang became the Uyghur
 # Autonomous Region under the PRC. (Before that Uyghurs, of course, would also
 # not be using Beijing time, but some local time.)
 
 # From David Cochrane (2014-03-26):
 # Just a confirmation that Ürümqi time was implemented in Ürümqi on 1 Feb 1986:
 # https://content.time.com/time/magazine/article/0,9171,960684,00.html
 
 # From Luther Ma (2014-04-22):
 # I have interviewed numerous people of various nationalities and from
 # different localities in Xinjiang and can confirm the information in Guo's
 # report regarding Xinjiang, as well as the Time article reference by David
 # Cochrane.  Whether officially recognized or not (and both are officially
 # recognized), two separate times have been in use in Xinjiang since at least
 # the Cultural Revolution: Xinjiang Time (XJT), aka Ürümqi Time or local time;
 # and Beijing Time.  There is no confusion in Xinjiang as to which name refers
 # to which time. Both are widely used in the province, although in some
 # population groups might be use one to the exclusion of the other.  The only
 # problem is that computers and smart phones list Ürümqi (or Kashgar) as
 # having the same time as Beijing.
 
 # From Paul Eggert (2014-06-30):
 # In the early days of the PRC, Tibet was given its own time zone (UT +06)
 # but this was withdrawn in 1959 and never reinstated; see Tubten Khétsun,
 # Memories of life in Lhasa under Chinese Rule, Columbia U Press, ISBN
 # 978-0231142861 (2008), translator's introduction by Matthew Akester, p x.
 # As this is before our 1970 cutoff, Tibet doesn't need a separate zone.
 #
 # Xinjiang Time is well-documented as being officially recognized.  E.g., see
 # "The Working-Calendar for The Xinjiang Uygur Autonomous Region Government"
 #  (2014-04-22).
 # Unfortunately, we have no good records of time in Xinjiang before 1986.
 # During the 20th century parts of Xinjiang were ruled by the Qing dynasty,
 # the Republic of China, various warlords, the First and Second East Turkestan
 # Republics, the Soviet Union, the Kuomintang, and the People's Republic of
 # China, and tracking down all these organizations' timekeeping rules would be
 # quite a trick.  Approximate this lost history by a transition from LMT to
 # UT +06 at the start of 1928, the year of accession of the warlord Jin Shuren,
 # which happens to be the date given by Shanks & Pottenger (no doubt as a
 # guess) as the transition from LMT.  Ignore the usage of +08 before
 # 1986-02-01 under the theory that the transition date to +08 is unknown and
 # that the sort of users who prefer Asia/Urumqi now typically ignored the
 # +08 mandate back then.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 # Beijing time, used throughout China; represented by Shanghai.
 		#STDOFF	8:05:43.2
 Zone	Asia/Shanghai	8:05:43	-	LMT	1901
 			8:00	Shang	C%sT	1949 May 28
 			8:00	PRC	C%sT
 # Xinjiang time, used by many in western China; represented by Ürümqi / Ürümchi
 # / Wulumuqi.  (Please use Asia/Shanghai if you prefer Beijing time.)
 Zone	Asia/Urumqi	5:50:20	-	LMT	1928
 			6:00	-	+06
 Link Asia/Urumqi Antarctica/Vostok
 
 
 # Hong Kong
 
 # Milne gives 7:36:41.7.
 
 # From Lee Yiu Chung (2009-10-24):
 # I found there are some mistakes for the...DST rule for Hong
 # Kong. [According] to the DST record from Hong Kong Observatory (actually,
 # it is not [an] observatory, but the official meteorological agency of HK,
 # and also serves as the official timing agency), there are some missing
 # and incorrect rules. Although the exact switch over time is missing, I
 # think 3:30 is correct.
 
 # From Phake Nick (2018-10-27):
 # According to Singaporean newspaper
 # http://eresources.nlb.gov.sg/newspapers/Digitised/Article/singfreepresswk19041102-1.2.37
 # the day that Hong Kong start using GMT+8 should be Oct 30, 1904.
 #
 # From Paul Eggert (2018-11-17):
 # Hong Kong had a time ball near the Marine Police Station, Tsim Sha Tsui.
 # "The ball was raised manually each day and dropped at exactly 1pm
 # (except on Sundays and Government holidays)."
 # Dyson AD. From Time Ball to Atomic Clock. Hong Kong Government. 1983.
 # 
 # "From 1904 October 30 the time-ball at Hong Kong has been dropped by order
 # of the Governor of the Colony at 17h 0m 0s G.M.T., which is 23m 18s.14 in
 # advance of 1h 0m 0s of Hong Kong mean time."
 # Hollis HP. Universal Time, Longitudes, and Geodesy. Mon Not R Astron Soc.
 # 1905-02-10;65(4):405-6. https://doi.org/10.1093/mnras/65.4.382
 #
 # From Joseph Myers (2018-11-18):
 # An astronomer before 1925 referring to GMT would have been using the old
 # astronomical convention where the day started at noon, not midnight.
 #
 # From Steve Allen (2018-11-17):
 # Meteorological Observations made at the Hongkong Observatory in the year 1904
 # page 4 
 # ... the log of drop times in Table II shows that on Sunday 1904-10-30 the
 # ball was dropped.  So that looks like a special case drop for the sake
 # of broadcasting the new local time.
 #
 # From Phake Nick (2018-11-18):
 # According to The Hong Kong Weekly Press, 1904-10-29, p.324, the
 # governor of Hong Kong at the time stated that "We are further desired to
 # make it known that the change will be effected by firing the gun and by the
 # dropping of the Ball at 23min. 18sec. before one."
 # From Paul Eggert (2018-11-18):
 # See  for this; unfortunately Flash is required.
 
 # From Phake Nick (2018-10-26):
 # I went to check microfilm records stored at Hong Kong Public Library....
 # on September 30 1941, according to Ta Kung Pao (Hong Kong edition), it was
 # stated that fallback would occur on the next day (the 1st)'s "03:00 am (Hong
 # Kong Time 04:00 am)" and the clock will fall back for a half hour. (03:00
 # probably refer to the time commonly used in mainland China at the time given
 # the paper's background) ... the sunrise/sunset time given by South China
 # Morning Post for October 1st was indeed moved by half an hour compares to
 # before.  After that, in December, the battle to capture Hong Kong started and
 # the library doesn't seems to have any record stored about press during that
 # period of time.  Some media resumed publication soon after that within the
 # same month, but there were not much information about time there.  Later they
 # started including a radio program guide when they restored radio service,
 # explicitly mentioning it use Tokyo standard time, and later added a note
 # saying it's half an hour ahead of the old Hong Kong standard time, and it
 # also seems to indicate that Hong Kong was not using GMT+8 when it was
 # captured by Japan.
 #
 # Image of related sections on newspaper:
 # * 1941-09-30, Ta Kung Pao (Hong Kong), "Winter Time start tomorrow".
 #   https://i.imgur.com/6waY51Z.jpg (Chinese)
 # * 1941-09-29, South China Morning Post, Information on sunrise/sunset
 #   time and other things for September 30 and October 1.
 #   https://i.imgur.com/kCiUR78.jpg
 # * 1942-02-05. The Hong Kong News, Radio Program Guide.
 #   https://i.imgur.com/eVvDMzS.jpg
 # * 1941-06-14. Hong Kong Daily Press, Daylight Saving from 3am Tomorrow.
 #   https://i.imgur.com/05KkvtC.png
 # * 1941-09-30, Hong Kong Daily Press, Winter Time Warning.
 #   https://i.imgur.com/dge4kFJ.png
 
 # From Paul Eggert (2019-07-11):
 # "Hong Kong winter time" is considered to be daylight saving.
 # "Hong Kong had adopted daylight saving on June 15 as a wartime measure,
 # clocks moving forward one hour until October 1, when they would be put back
 # by just half an hour for 'Hong Kong Winter time', so that daylight saving
 # operated year round." -- Low Z. The longest day: when wartime Hong Kong
 # introduced daylight saving. South China Morning Post. 2019-06-28.
 # https://www.scmp.com/magazines/post-magazine/short-reads/article/3016281/longest-day-when-wartime-hong-kong-introduced
 
 # From P Chan (2018-12-31):
 # * According to the Hong Kong Daylight-Saving Regulations, 1941, the
 #   1941 spring-forward transition was at 03:00.
 #	http://sunzi.lib.hku.hk/hkgro/view/g1941/304271.pdf
 #	http://sunzi.lib.hku.hk/hkgro/view/g1941/305516.pdf
 # * According to some articles from South China Morning Post, +08 was
 #   resumed on 1945-11-18 at 02:00.
 #	https://i.imgur.com/M2IsZ3c.png
 #	https://i.imgur.com/iOPqrVo.png
 #	https://i.imgur.com/fffcGDs.png
 # * Some newspapers ... said the 1946 spring-forward transition was on
 #   04-21 at 00:00.  The Kung Sheung Evening News 1946-04-20 (Chinese)
 #	https://i.imgur.com/ZSzent0.png
 #	https://mmis.hkpl.gov.hk///c/portal/cover?c=QF757YsWv5%2FH7zGe%2FKF%2BFLYsuqGhRBfe p.4
 #   The Kung Sheung Daily News 1946-04-21 (Chinese)
 #	https://i.imgur.com/7ecmRlcm.png
 #	https://mmis.hkpl.gov.hk///c/portal/cover?c=QF757YsWv5%2BQBGt1%2BwUj5qG2GqtwR3Wh p.4
 # * According to the Summer Time Ordinance (1946), the fallback
 #   transitions between 1946 and 1952 were at 03:30 Standard Time (+08)
 #	http://oelawhk.lib.hku.hk/archive/files/bb74b06a74d5294620a15de560ab33c6.pdf
 # * Some other laws and regulations related to DST from 1953 to 1979
 #   Summer Time Ordinance 1953
 #	https://i.imgur.com/IOlJMav.jpg
 #   Summer Time (Amendment) Ordinance 1965
 #	https://i.imgur.com/8rofeLa.jpg
 #   Interpretation and General Clauses Ordinance (1966)
 #	https://i.imgur.com/joy3msj.jpg
 #   Emergency (Summer Time) Regulation 1973 
 #   Interpretation and General Clauses (Amendment) Ordinance 1977
 #	https://i.imgur.com/RaNqnc4.jpg
 #   Resolution of the Legislative Council passed on 9 May 1979
 #	https://www.legco.gov.hk/yr78-79/english/lc_sitg/hansard/h790509.pdf#page=39
 
 # From Paul Eggert (2020-04-15):
 # Here are the dates given at
 # https://www.hko.gov.hk/en/gts/time/Summertime.htm
 # as of 2020-02-10:
 # Year        Period
 # 1941        15 Jun to 30 Sep
 # 1942        Whole year
 # 1943        Whole year
 # 1944        Whole year
 # 1945        Whole year
 # 1946        20 Apr to 1 Dec
 # 1947        13 Apr to 30 Nov
 # 1948        2 May to 31 Oct
 # 1949        3 Apr to 30 Oct
 # 1950        2 Apr to 29 Oct
 # 1951        1 Apr to 28 Oct
 # 1952        6 Apr to 2 Nov
 # 1953        5 Apr to 1 Nov
 # 1954        21 Mar to 31 Oct
 # 1955        20 Mar to 6 Nov
 # 1956        18 Mar to 4 Nov
 # 1957        24 Mar to 3 Nov
 # 1958        23 Mar to 2 Nov
 # 1959        22 Mar to 1 Nov
 # 1960        20 Mar to 6 Nov
 # 1961        19 Mar to 5 Nov
 # 1962        18 Mar to 4 Nov
 # 1963        24 Mar to 3 Nov
 # 1964        22 Mar to 1 Nov
 # 1965        18 Apr to 17 Oct
 # 1966        17 Apr to 16 Oct
 # 1967        16 Apr to 22 Oct
 # 1968        21 Apr to 20 Oct
 # 1969        20 Apr to 19 Oct
 # 1970        19 Apr to 18 Oct
 # 1971        18 Apr to 17 Oct
 # 1972        16 Apr to 22 Oct
 # 1973        22 Apr to 21 Oct
 # 1973/74     30 Dec 73 to 20 Oct 74
 # 1975        20 Apr to 19 Oct
 # 1976        18 Apr to 17 Oct
 # 1977        Nil
 # 1978        Nil
 # 1979        13 May to 21 Oct
 # 1980 to Now Nil
 # The page does not give times of day for transitions,
 # or dates for the 1942 and 1945 transitions.
 # The Japanese occupation of Hong Kong began 1941-12-25.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	HK	1946	only	-	Apr	21	0:00	1:00	S
 Rule	HK	1946	only	-	Dec	1	3:30s	0	-
 Rule	HK	1947	only	-	Apr	13	3:30s	1:00	S
 Rule	HK	1947	only	-	Nov	30	3:30s	0	-
 Rule	HK	1948	only	-	May	2	3:30s	1:00	S
 Rule	HK	1948	1952	-	Oct	Sun>=28	3:30s	0	-
 Rule	HK	1949	1953	-	Apr	Sun>=1	3:30	1:00	S
 Rule	HK	1953	1964	-	Oct	Sun>=31	3:30	0	-
 Rule	HK	1954	1964	-	Mar	Sun>=18	3:30	1:00	S
 Rule	HK	1965	1976	-	Apr	Sun>=16	3:30	1:00	S
 Rule	HK	1965	1976	-	Oct	Sun>=16	3:30	0	-
 Rule	HK	1973	only	-	Dec	30	3:30	1:00	S
 Rule	HK	1979	only	-	May	13	3:30	1:00	S
 Rule	HK	1979	only	-	Oct	21	3:30	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 		#STDOFF	7:36:41.7
 Zone	Asia/Hong_Kong	7:36:42 -	LMT	1904 Oct 29 17:00u
 			8:00	-	HKT	1941 Jun 15  3:00
 			8:00	1:00	HKST	1941 Oct  1  4:00
 			8:00	0:30	HKWT	1941 Dec 25
 			9:00	-	JST	1945 Nov 18  2:00
 			8:00	HK	HK%sT
 
 ###############################################################################
 
 # Taiwan
 
 # From smallufo (2010-04-03):
 # According to Taiwan's CWB [Central Weather Bureau],
 # http://www.cwb.gov.tw/V6/astronomy/cdata/summert.htm
 # Taipei has DST in 1979 between July 1st and Sep 30.
 
 # From Yu-Cheng Chuang (2013-07-12):
 # On Dec 28, 1895, the Meiji Emperor announced Ordinance No. 167 of
 # Meiji Year 28 "The clause about standard time", mentioned that
 # Taiwan and Penghu Islands, as well as Yaeyama and Miyako Islands
 # (both in Okinawa) adopt the Western Standard Time which is based on
 # 120E. The adoption began from Jan 1, 1896. The original text can be
 # found on Wikisource:
 # https://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時)
 # ... This could be the first adoption of time zone in Taiwan, because
 # during the Qing Dynasty, it seems that there was no time zone
 # declared officially.
 #
 # Later, in the beginning of World War II, on Sep 25, 1937, the Showa
 # Emperor announced Ordinance No. 529 of Showa Year 12 "The clause of
 # revision in the ordinance No. 167 of Meiji year 28 about standard
 # time", in which abolished the adoption of Western Standard Time in
 # western islands (listed above), which means the whole Japan
 # territory, including later occupations, adopt Japan Central Time
 # (UT+9). The adoption began on Oct 1, 1937. The original text can
 # be found on Wikisource:
 # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件
 #
 # That is, the time zone of Taipei switched to UT+9 on Oct 1, 1937.
 
 # From Yu-Cheng Chuang (2014-07-02):
 # I've found more evidence about when the time zone was switched from UT+9
 # back to UT+8 after WW2.  I believe it was on Sep 21, 1945.  In a document
 # during Japanese era [1] in which the officer told the staff to change time
 # zone back to Western Standard Time (UT+8) on Sep 21.  And in another
 # history page of National Cheng Kung University [2], on Sep 21 there is a
 # note "from today, switch back to Western Standard Time".  From these two
 # materials, I believe that the time zone change happened on Sep 21.  And
 # today I have found another monthly journal called "The Astronomical Herald"
 # from The Astronomical Society of Japan [3] in which it mentioned the fact
 # that:
 #
 # 1. Standard Time of the Country (Japan) was adopted on Jan 1, 1888, using
 # the time at 135E (GMT+9)
 #
 # 2. Standard Time of the Country was renamed to Central Standard Time, on Jan
 # 1, 1898, and on the same day, the new territories Taiwan and Penghu islands,
 # as well as Yaeyama and Miyako islands, adopted a new time zone called
 # Western Standard Time, which is in GMT+8.
 #
 # 3. Western Standard Time was deprecated on Sep 30, 1937. From then all the
 # territories of Japan adopted the same time zone, which is Central Standard
 # Time.
 #
 # [1] Academica Historica, Taiwan:
 # http://163.29.208.22:8080/govsaleShowImage/connect_img.php?s=00101738900090036&e=00101738900090037
 # [2] Nat'l Cheng Kung University 70th Anniversary Special Site:
 # http://www.ncku.edu.tw/~ncku70/menu/001/01_01.htm
 # [3] Yukio Niimi, The Standard Time in Japan (1997), p.475:
 # http://www.asj.or.jp/geppou/archive_open/1997/pdf/19971001c.pdf
 
 # Yu-Cheng Chuang (2014-07-03):
 # I finally have found the real official gazette about changing back to
 # Western Standard Time on Sep 21 in Taiwan.  It's Taiwan Governor-General
 # Bulletin No. 386 in Showa 20 years (1945), published on Sep 19, 1945. [1] ...
 # [It] abolishes Bulletin No. 207 in Showa 12 years (1937), which is a local
 # bulletin in Taiwan for that Ordinance No. 529. It also mentioned that 1am on
 # Sep 21, 1945 will be 12am on Sep 21.  I think this bulletin is much more
 # official than the one I mentioned in my first mail, because it's from the
 # top-level government in Taiwan. If you're going to quote any resource, this
 # would be a good one.
 # [1] Taiwan Governor-General Gazette, No. 1018, Sep 19, 1945:
 # http://db2.th.gov.tw/db2/view/viewImg.php?imgcode=0072031018a&num=19&bgn=019&end=019&otherImg=&type=gener
 
 # From Yu-Cheng Chuang (2014-07-02):
 # In 1946, DST in Taiwan was from May 15 and ended on Sep 30. The info from
 # Central Weather Bureau website was not correct.
 #
 # Original Bulletin:
 # http://subtpg.tpg.gov.tw/og/image2.asp?f=03502F0AKM1AF
 # http://subtpg.tpg.gov.tw/og/image2.asp?f=0350300AKM1B0 (cont.)
 #
 # In 1947, DST in Taiwan was expanded to Oct 31. There is a backup of that
 # telegram announcement from Taiwan Province Government:
 #
 # http://subtpg.tpg.gov.tw/og/image2.asp?f=0360310AKZ431
 #
 # Here is a brief translation:
 #
 #   The Summer Time this year is adopted from midnight Apr 15 until Sep 20
 #   midnight. To save (energy?) consumption, we're expanding Summer Time
 #   adoption till Oct 31 midnight.
 #
 # The Central Weather Bureau website didn't mention that, however it can
 # be found from historical government announcement database.
 
 # From Paul Eggert (2014-07-03):
 # As per Yu-Cheng Chuang, say that Taiwan was at UT +09 from 1937-10-01
 # until 1945-09-21 at 01:00, overriding Shanks & Pottenger.
 # Likewise, use Yu-Cheng Chuang's data for DST in Taiwan.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Taiwan	1946	only	-	May	15	0:00	1:00	D
 Rule	Taiwan	1946	only	-	Oct	1	0:00	0	S
 Rule	Taiwan	1947	only	-	Apr	15	0:00	1:00	D
 Rule	Taiwan	1947	only	-	Nov	1	0:00	0	S
 Rule	Taiwan	1948	1951	-	May	1	0:00	1:00	D
 Rule	Taiwan	1948	1951	-	Oct	1	0:00	0	S
 Rule	Taiwan	1952	only	-	Mar	1	0:00	1:00	D
 Rule	Taiwan	1952	1954	-	Nov	1	0:00	0	S
 Rule	Taiwan	1953	1959	-	Apr	1	0:00	1:00	D
 Rule	Taiwan	1955	1961	-	Oct	1	0:00	0	S
 Rule	Taiwan	1960	1961	-	Jun	1	0:00	1:00	D
 Rule	Taiwan	1974	1975	-	Apr	1	0:00	1:00	D
 Rule	Taiwan	1974	1975	-	Oct	1	0:00	0	S
 Rule	Taiwan	1979	only	-	Jul	1	0:00	1:00	D
 Rule	Taiwan	1979	only	-	Oct	1	0:00	0	S
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 # Taipei or Taibei or T'ai-pei
 Zone	Asia/Taipei	8:06:00 -	LMT	1896 Jan  1
 			8:00	-	CST	1937 Oct  1
 			9:00	-	JST	1945 Sep 21  1:00
 			8:00	Taiwan	C%sT
 
 # Macau (Macao, Aomen)
 #
 # From P Chan (2018-05-10):
 # * LegisMac
 #   http://legismac.safp.gov.mo/legismac/descqry/Descqry.jsf?lang=pt
 #   A database for searching titles of legal documents of Macau in
 #   Chinese and Portuguese.  The term "HORÁRIO DE VERÃO" can be used for
 #   searching decrees about summer time.
 # * Archives of Macao
 #   http://www.archives.gov.mo/en/bo/
 #   It contains images of old official gazettes.
 # * The Macao Meteorological and Geophysical Bureau have a page listing the
 #   summer time history.  But it is not complete and has some mistakes.
 #   http://www.smg.gov.mo/smg/geophysics/e_t_Summer%20Time.htm
 # Macau adopted GMT+8 on 30 Oct 1904 to follow Hong Kong.  Clocks were
 # advanced by 25 minutes and 50 seconds.  Which means the LMT used was
 # +7:34:10.  As stated in the "Portaria No. 204" dated 21 October 1904
 # and published in the Official Gazette on 29 October 1904.
 # http://igallery.icm.gov.mo/Images/Archives/BO/MO_AH_PUB_BO_1904_10/MO_AH_PUB_BO_1904_10_00025_Grey.JPG
 #
 # Therefore the 1911 decree of Portugal did not change time in Macau.
 #
 # From LegisMac, here is a list of decrees that changed the time ...
 # [Decree Gazette-no. date; titles omitted in this quotation]
 #	DIL 732 BOCM 51 1941.12.20
 #	DIL 764 BOCM 9S 1942.04.30
 #	DIL 781 BOCM 21 1942.10.10
 #	PT 3434 BOCM 8S 1943.04.17
 #	PT 3504 BOCM 20 1943.09.25
 #	PT 3843 BOCM 39 1945.09.29
 #	PT 3961 BOCM 17 1946.04.27
 #	PT 4026 BOCM 39 1946.09.28
 #	PT 4153 BOCM 16 1947.04.10
 #	PT 4271 BOCM 48 1947.11.29
 #	PT 4374 BOCM 18 1948.05.01
 #	PT 4465 BOCM 44 1948.10.30
 #	PT 4590 BOCM 14 1949.04.02
 #	PT 4666 BOCM 44 1949.10.29
 #	PT 4771 BOCM 12 1950.03.25
 #	PT 4838 BOCM 43 1950.10.28
 #	PT 4946 BOCM 12 1951.03.24
 #	PT 5025 BO 43 1951.10.27
 #	PT 5149 BO 14 1952.04.05
 #	PT 5251 BO 43 1952.10.25
 #	PT 5366 BO 13 1953.03.28
 #	PT 5444 BO 44 1953.10.31
 #	PT 5540 BO 12 1954.03.20
 #	PT 5589 BO 44 1954.10.30
 #	PT 5676 BO 12 1955.03.19
 #	PT 5739 BO 45 1955.11.05
 #	PT 5823 BO 11 1956.03.17
 #	PT 5891 BO 44 1956.11.03
 #	PT 5981 BO 12 1957.03.23
 #	PT 6064 BO 43 1957.10.26
 #	PT 6172 BO 12 1958.03.22
 #	PT 6243 BO 43 1958.10.25
 #	PT 6341 BO 12 1959.03.21
 #	PT 6411 BO 43 1959.10.24
 #	PT 6514 BO 11 1960.03.12
 #	PT 6584 BO 44 1960.10.29
 #	PT 6721 BO 10 1961.03.11
 #	PT 6815 BO 43 1961.10.28
 #	PT 6947 BO 10 1962.03.10
 #	PT 7080 BO 43 1962.10.27
 #	PT 7218 BO 12 1963.03.23
 #	PT 7340 BO 43 1963.10.26
 #	PT 7491 BO 11 1964.03.14
 #	PT 7664 BO 43 1964.10.24
 #	PT 7846 BO 15 1965.04.10
 #	PT 7979 BO 42 1965.10.16
 #	PT 8146 BO 15 1966.04.09
 #	PT 8252 BO 41 1966.10.08
 #	PT 8429 BO 15 1967.04.15
 #	PT 8540 BO 41 1967.10.14
 #	PT 8735 BO 15 1968.04.13
 #	PT 8860 BO 41 1968.10.12
 #	PT 9035 BO 16 1969.04.19
 #	PT 9156 BO 42 1969.10.18
 #	PT 9328 BO 15 1970.04.11
 #	PT 9418 BO 41 1970.10.10
 #	PT 9587 BO 14 1971.04.03
 #	PT 9702 BO 41 1971.10.09
 #	PT 38-A/72 BO 14 1972.04.01
 #	PT 126-A/72 BO 41 1972.10.07
 #	PT 61/73 BO 14 1973.04.07
 #	PT 182/73 BO 40 1973.10.06
 #	PT 282/73 BO 51 1973.12.22
 #	PT 177/74 BO 41 1974.10.12
 #	PT 51/75 BO 15 1975.04.12
 #	PT 173/75 BO 41 1975.10.11
 #	PT 67/76/M BO 14 1976.04.03
 #	PT 169/76/M BO 41 1976.10.09
 #	PT 78/79/M BO 19 1979.05.12
 #	PT 166/79/M BO 42 1979.10.20
 # Note that DIL 732 does not belong to "HORÁRIO DE VERÃO" according to
 # LegisMac.... Note that between 1942 and 1945, the time switched
 # between GMT+9 and GMT+10.  Also in 1965 and 1965 the DST ended at 2:30am.
 
 # From Paul Eggert (2018-05-10):
 # The 1904 decree says that Macau changed from the meridian of
 # Fortaleza do Monte, presumably the basis for the 7:34:10 for LMT.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Macau	1942	1943	-	Apr	30	23:00	1:00	-
 Rule	Macau	1942	only	-	Nov	17	23:00	0	-
 Rule	Macau	1943	only	-	Sep	30	23:00	0	S
 Rule	Macau	1946	only	-	Apr	30	23:00s	1:00	D
 Rule	Macau	1946	only	-	Sep	30	23:00s	0	S
 Rule	Macau	1947	only	-	Apr	19	23:00s	1:00	D
 Rule	Macau	1947	only	-	Nov	30	23:00s	0	S
 Rule	Macau	1948	only	-	May	 2	23:00s	1:00	D
 Rule	Macau	1948	only	-	Oct	31	23:00s	0	S
 Rule	Macau	1949	1950	-	Apr	Sat>=1	23:00s	1:00	D
 Rule	Macau	1949	1950	-	Oct	lastSat	23:00s	0	S
 Rule	Macau	1951	only	-	Mar	31	23:00s	1:00	D
 Rule	Macau	1951	only	-	Oct	28	23:00s	0	S
 Rule	Macau	1952	1953	-	Apr	Sat>=1	23:00s	1:00	D
 Rule	Macau	1952	only	-	Nov	 1	23:00s	0	S
 Rule	Macau	1953	1954	-	Oct	lastSat	23:00s	0	S
 Rule	Macau	1954	1956	-	Mar	Sat>=17	23:00s	1:00	D
 Rule	Macau	1955	only	-	Nov	 5	23:00s	0	S
 Rule	Macau	1956	1964	-	Nov	Sun>=1	03:30	0	S
 Rule	Macau	1957	1964	-	Mar	Sun>=18	03:30	1:00	D
 Rule	Macau	1965	1973	-	Apr	Sun>=16	03:30	1:00	D
 Rule	Macau	1965	1966	-	Oct	Sun>=16	02:30	0	S
 Rule	Macau	1967	1976	-	Oct	Sun>=16	03:30	0	S
 Rule	Macau	1973	only	-	Dec	30	03:30	1:00	D
 Rule	Macau	1975	1976	-	Apr	Sun>=16	03:30	1:00	D
 Rule	Macau	1979	only	-	May	13	03:30	1:00	D
 Rule	Macau	1979	only	-	Oct	Sun>=16	03:30	0	S
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Macau	7:34:10 -	LMT	1904 Oct 30
 			8:00	-	CST	1941 Dec 21 23:00
 			9:00	Macau	+09/+10	1945 Sep 30 24:00
 			8:00	Macau	C%sT
 
 
 ###############################################################################
 
 # Cyprus
 
 # Milne says the Eastern Telegraph Company used 2:14:00.  Stick with LMT.
 # IATA SSIM (1998-09) has Cyprus using EU rules for the first time.
 
 # From Paul Eggert (2016-09-09):
 # Yesterday's Cyprus Mail reports that Northern Cyprus followed Turkey's
 # lead and switched from +02/+03 to +03 year-round.
 # http://cyprus-mail.com/2016/09/08/two-time-zones-cyprus-turkey-will-not-turn-clocks-back-next-month/
 #
 # From Even Scharning (2016-10-31):
 # Looks like the time zone split in Cyprus went through last night.
 # http://cyprus-mail.com/2016/10/30/cyprus-new-division-two-time-zones-now-reality/
 
 # From Paul Eggert (2017-10-18):
 # Northern Cyprus will reinstate winter time on October 29, thus
 # staying in sync with the rest of Cyprus.  See: Anastasiou A.
 # Cyprus to remain united in time.  Cyprus Mail 2017-10-17.
 # https://cyprus-mail.com/2017/10/17/cyprus-remain-united-time/
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Cyprus	1975	only	-	Apr	13	0:00	1:00	S
 Rule	Cyprus	1975	only	-	Oct	12	0:00	0	-
 Rule	Cyprus	1976	only	-	May	15	0:00	1:00	S
 Rule	Cyprus	1976	only	-	Oct	11	0:00	0	-
 Rule	Cyprus	1977	1980	-	Apr	Sun>=1	0:00	1:00	S
 Rule	Cyprus	1977	only	-	Sep	25	0:00	0	-
 Rule	Cyprus	1978	only	-	Oct	2	0:00	0	-
 Rule	Cyprus	1979	1997	-	Sep	lastSun	0:00	0	-
 Rule	Cyprus	1981	1998	-	Mar	lastSun	0:00	1:00	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Nicosia	2:13:28 -	LMT	1921 Nov 14
 			2:00	Cyprus	EE%sT	1998 Sep
 			2:00	EUAsia	EE%sT
 Zone	Asia/Famagusta	2:15:48	-	LMT	1921 Nov 14
 			2:00	Cyprus	EE%sT	1998 Sep
 			2:00	EUAsia	EE%sT	2016 Sep  8
 			3:00	-	+03	2017 Oct 29 1:00u
 			2:00	EUAsia	EE%sT
 
 # Classically, Cyprus belongs to Asia; e.g. see Herodotus, Histories, I.72.
 # However, for various reasons many users expect to find it under Europe.
 Link	Asia/Nicosia	Europe/Nicosia
 
 # Georgia
 # From Paul Eggert (1994-11-19):
 # Today's _Economist_ (p 60) reports that Georgia moved its clocks forward
 # an hour recently, due to a law proposed by Zurab Murvanidze,
 # an MP who went on a hunger strike for 11 days to force discussion about it!
 # We have no details, but we'll guess they didn't move the clocks back in fall.
 #
 # From Mathew Englander, quoting AP (1996-10-23 13:05-04):
 # Instead of putting back clocks at the end of October, Georgia
 # will stay on daylight savings time this winter to save energy,
 # President Eduard Shevardnadze decreed Wednesday.
 #
 # From the BBC via Joseph S. Myers (2004-06-27):
 #
 # Georgia moved closer to Western Europe on Sunday...  The former Soviet
 # republic has changed its time zone back to that of Moscow.  As a result it
 # is now just four hours ahead of Greenwich Mean Time, rather than five hours
 # ahead.  The switch was decreed by the pro-Western president of Georgia,
 # Mikheil Saakashvili, who said the change was partly prompted by the process
 # of integration into Europe.
 
 # From Teimuraz Abashidze (2005-11-07):
 # Government of Georgia ... decided to NOT CHANGE daylight savings time on
 # [Oct.] 30, as it was done before during last more than 10 years.
 # Currently, we are in fact GMT +4:00, as before 30 October it was GMT
 # +3:00.... The problem is, there is NO FORMAL LAW or governmental document
 # about it.  As far as I can find, I was told, that there is no document,
 # because we just DIDN'T ISSUE document about switching to winter time....
 # I don't know what can be done, especially knowing that some years ago our
 # DST rules where changed THREE TIMES during one month.
 
 # Milne 1899 says Tbilisi (Tiflis) time was 2:59:05.7.
 # Byalokoz 1919 says Georgia was 2:59:11.
 # Go with Byalokoz.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Tbilisi	2:59:11 -	LMT	1880
 			2:59:11	-	TBMT	1924 May  2 # Tbilisi Mean Time
 			3:00	-	+03	1957 Mar
 			4:00 RussiaAsia +04/+05	1991 Mar 31  2:00s
 			3:00 RussiaAsia +03/+04	1992
 			3:00 E-EurAsia	+03/+04	1994 Sep lastSun
 			4:00 E-EurAsia	+04/+05	1996 Oct lastSun
 			4:00	1:00	+05	1997 Mar lastSun
 			4:00 E-EurAsia	+04/+05	2004 Jun 27
 			3:00 RussiaAsia	+03/+04	2005 Mar lastSun  2:00
 			4:00	-	+04
 
 # East Timor
 
 # See Indonesia for the 1945 transition.
 
 # From João Carrascalão, brother of the former governor of East Timor, in
 # East Timor may be late for its millennium
 #  (1999-12-26/31):
 # Portugal tried to change the time forward in 1974 because the sun
 # rises too early but the suggestion raised a lot of problems with the
 # Timorese and I still don't think it would work today because it
 # conflicts with their way of life.
 
 # From Paul Eggert (2000-12-04):
 # We don't have any record of the above attempt.
 # Most likely our records are incomplete, but we have no better data.
 
 # From Manoel de Almeida e Silva, Deputy Spokesman for the UN Secretary-General
 # http://www.hri.org/news/world/undh/2000/00-08-16.undh.html
 # (2000-08-16):
 # The Cabinet of the East Timor Transition Administration decided
 # today to advance East Timor's time by one hour.  The time change,
 # which will be permanent, with no seasonal adjustment, will happen at
 # midnight on Saturday, September 16.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Dili	8:22:20 -	LMT	1912 Jan  1
 			8:00	-	+08	1942 Feb 21 23:00
 			9:00	-	+09	1976 May  3
 			8:00	-	+08	2000 Sep 17  0:00
 			9:00	-	+09
 
 # India
 
 # British astronomer Henry Park Hollis disliked India Standard Time's offset:
 # "A new time system has been proposed for India, Further India, and Burmah.
 # The scheme suggested is that the times of the meridians 5½ and 6½ hours
 # east of Greenwich should be adopted in these territories.  No reason is
 # given why hourly meridians five hours and six hours east should not be
 # chosen; a plan which would bring the time of India into harmony with
 # that of almost the whole of the civilised world."
 # Hollis HP. Universal Time, Longitudes, and Geodesy. Mon Not R Astron Soc.
 # 1905-02-10;65(4):405-6. https://doi.org/10.1093/mnras/65.4.382
 
 # From Ian P. Beacock, in "A brief history of (modern) time", The Atlantic
 # https://www.theatlantic.com/technology/archive/2015/12/the-creation-of-modern-time/421419/
 # (2015-12-22):
 # In January 1906, several thousand cotton-mill workers rioted on the
 # outskirts of Bombay....  They were protesting the proposed abolition of
 # local time in favor of Indian Standard Time....  Journalists called this
 # dispute the "Battle of the Clocks."  It lasted nearly half a century.
 
 # From Paul Eggert (2017-04-20):
 # Good luck trying to nail down old timekeeping records in India.
 # "... in the nineteenth century ... Madras Observatory took its magnetic
 # measurements on Göttingen time, its meteorological measurements on Madras
 # (local) time, dropped its time ball on Greenwich (ocean navigator's) time,
 # and distributed civil (local time)." -- Bartky IR. Selling the true time:
 # 19th-century timekeeping in america. Stanford U Press (2000), 247 note 19.
 # "A more potent cause of resistance to the general adoption of the present
 # standard time lies in the fact that it is Madras time.  The citizen of
 # Bombay, proud of being 'primus in Indis' and of Calcutta, equally proud of
 # his city being the Capital of India, and - for a part of the year - the Seat
 # of the Supreme Government, alike look down on Madras, and refuse to change
 # the time they are using, for that of what they regard as a benighted
 # Presidency; while Madras, having for long given the standard time to the
 # rest of India, would resist the adoption of any other Indian standard in its
 # place." -- Oldham RD. On Time in India: a suggestion for its improvement.
 # Proceedings of the Asiatic Society of Bengal (April 1899), 49-55.
 #
 # "In 1870 ... Madras time - 'now used by the telegraph and regulated from the
 # only government observatory' - was suggested as a standard railway time,
 # first to be adopted on the Great Indian Peninsular Railway (GIPR)....
 # Calcutta, Bombay, and Karachi, were to be allowed to continue with their
 # local time for civil purposes." - Prasad R. Tracks of Change: Railways and
 # Everyday Life in Colonial India. Cambridge University Press (2016), 145.
 #
 # Reed S, Low F. The Indian Year Book 1936-37. Bennett, Coleman, pp 27-8.
 # https://archive.org/details/in.ernet.dli.2015.282212
 # This lists +052110 as Madras local time used in railways, and says that on
 # 1906-01-01 railways and telegraphs in India switched to +0530.  Some
 # municipalities retained their former time, and the time in Calcutta
 # continued to depend on whether you were at the railway station or at
 # government offices.  Government time was at +055320 (according to Shanks) or
 # at +0554 (according to the Indian Year Book).  Railway time is more
 # appropriate for our purposes, as it was better documented, it is what we do
 # elsewhere (e.g., Europe/London before 1880), and after 1906 it was
 # consistent in the region now identified by Asia/Kolkata.  So, use railway
 # time for 1870-1941.  Shanks is our only (and dubious) source for the
 # 1941-1945 data.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Kolkata	5:53:28 -	LMT	1854 Jun 28 # Kolkata
 			5:53:20	-	HMT	1870	    # Howrah Mean Time?
 			5:21:10	-	MMT	1906 Jan  1 # Madras local time
 			5:30	-	IST	1941 Oct
 			5:30	1:00	+0630	1942 May 15
 			5:30	-	IST	1942 Sep
 			5:30	1:00	+0630	1945 Oct 15
 			5:30	-	IST
 # Since 1970 the following are like Asia/Kolkata:
 #	Andaman Is
 #	Lakshadweep (Laccadive, Minicoy and Amindivi Is)
 #	Nicobar Is
 
 # Indonesia
 #
 # From Paul Eggert (2014-09-06):
 # The 1876 Report of the Secretary of the [US] Navy, p 306 says that Batavia
 # civil time was 7:07:12.5.
 #
 # From Gwillim Law (2001-05-28), overriding Shanks & Pottenger:
 # http://www.sumatera-inc.com/go_to_invest/about_indonesia.asp#standtime
 # says that Indonesia's time zones changed on 1988-01-01.  Looking at some
 # time zone maps, I think that must refer to Western Borneo (Kalimantan Barat
 # and Kalimantan Tengah) switching from UTC+8 to UTC+7.
 #
 # From Paul Eggert (2007-03-10):
 # Here is another correction to Shanks & Pottenger.
 # JohnTWB writes that Japanese forces did not surrender control in
 # Indonesia until 1945-09-01 00:00 at the earliest (in Jakarta) and
 # other formal surrender ceremonies were September 9, 11, and 13, plus
 # September 12 for the regional surrender to Mountbatten in Singapore.
 # These would be the earliest possible times for a change.
 # Régimes horaires pour le monde entier, by Henri Le Corre, (Éditions
 # Traditionnelles, 1987, Paris) says that Java and Madura switched
 # from UT +09 to +07:30 on 1945-09-23, and gives 1944-09-01 for Jayapura
 # (Hollandia).  For now, assume all Indonesian locations other than Jayapura
 # switched on 1945-09-23.
 #
 # From Paul Eggert (2013-08-11):
 # Normally the tz database uses English-language abbreviations, but in
 # Indonesia it's typical to use Indonesian-language abbreviations even
 # when writing in English.  For example, see the English-language
 # summary published by the Time and Frequency Laboratory of the
 # Research Center for Calibration, Instrumentation and Metrology,
 # Indonesia,  (2006-09-29).
 # The time zone abbreviations and UT offsets are:
 #
 # WIB  - +07 - Waktu Indonesia Barat (Indonesia western time)
 # WITA - +08 - Waktu Indonesia Tengah (Indonesia central time)
 # WIT  - +09 - Waktu Indonesia Timur (Indonesia eastern time)
 #
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 # Java, Sumatra
 		#STDOFF	7:07:12.5
 Zone Asia/Jakarta	7:07:12 -	LMT	1867 Aug 10
 # Shanks & Pottenger say the next transition was at 1924 Jan 1 0:13,
 # but this must be a typo.
 			7:07:12	-	BMT	1923 Dec 31 16:40u # Batavia
 			7:20	-	+0720	1932 Nov
 			7:30	-	+0730	1942 Mar 23
 			9:00	-	+09	1945 Sep 23
 			7:30	-	+0730	1948 May
 			8:00	-	+08	1950 May
 			7:30	-	+0730	1964
 			7:00	-	WIB
 # west and central Borneo
 Zone Asia/Pontianak	7:17:20	-	LMT	1908 May
 			7:17:20	-	PMT	1932 Nov    # Pontianak MT
 			7:30	-	+0730	1942 Jan 29
 			9:00	-	+09	1945 Sep 23
 			7:30	-	+0730	1948 May
 			8:00	-	+08	1950 May
 			7:30	-	+0730	1964
 			8:00	-	WITA	1988 Jan  1
 			7:00	-	WIB
 # Sulawesi, Lesser Sundas, east and south Borneo
 Zone Asia/Makassar	7:57:36 -	LMT	1920
 			7:57:36	-	MMT	1932 Nov    # Macassar MT
 			8:00	-	+08	1942 Feb  9
 			9:00	-	+09	1945 Sep 23
 			8:00	-	WITA
 # Maluku Islands, West Papua, Papua
 Zone Asia/Jayapura	9:22:48 -	LMT	1932 Nov
 			9:00	-	+09	1944 Sep  1
 			9:30	-	+0930	1964
 			9:00	-	WIT
 
 # Iran
 
 # From Roozbeh Pournader (2022-05-30):
 # Here's an order from the Cabinet to the rest of the government to switch to
 # Tehran time, which is mentioned to be already at +03:30:
 # https://qavanin.ir/Law/TreeText/180138
 # Just in case that goes away, I also saved a copy at archive.org:
 # https://web.archive.org/web/20220530111940/https://qavanin.ir/Law/TreeText/180138
 # Here's my translation:
 #
 # "Circular on Matching the Hours of Governmental and Official Circles
 # in Provinces
 # Approved 1314/03/22 [=1935-06-13]
 # According to the ruling of the Honorable Cabinet, it is ordered that from
 # now on in all internal provinces of the country, governmental and official
 # circles set their time to match Tehran time (three hours and half before
 # Greenwich)....
 #
 # I still haven't found out when Tehran itself switched to +03:30....
 #
 # From Paul Eggert (2022-06-05):
 # Although the above says Tehran was at +03:30 before 1935-06-13, we don't
 # know when it switched to +03:30.  For now, use 1935-06-13 as the switch date.
 # Although most likely wrong, we have no better info.
 
 # From Roozbeh Pournader (2022-06-01):
 # This is from Kayhan newspaper, one of the major Iranian newspapers, from
 # March 20, 1978, page 2:
 #
 # "Pull the clocks 60 minutes forward
 # As we informed before, from the fourth day of the month Farvardin of the
 # new year [=1978-03-24], clocks will be pulled forward, and people's daily
 # work and life program will start one hour earlier than the current program.
 # On the 1st day of the month Farvardin of this year [=1977-03-21], they had
 # pulled the clocks forward by one hour, but in the month of Mehr
 # [=1977-09-23], the clocks were pulled back by 30 minutes.
 # In this way, from the 4th day of the month Farvardin, clocks will be ahead
 # of the previous years by one hour and a half.
 # According to the new program, during the night of 4th of Farvardin, when
 # the midnight, meaning 24 o'clock is announced, the hands of the clock must
 # be pulled forward by one hour and thus consider midnight 1 o'clock in the
 # forenoon."
 #
 # This implies that in September 1977, when the daylight savings time was
 # done with, Iran didn't go back to +03:30, but immediately to +04:00.
 #
 #
 # This is from the major Iranian newspaper Ettela'at, dated [1978-08-03]...,
 # page 32. It looks like they decided to get the clocks back to +4:00
 # just in time for Ramadan that year:
 #
 # "Tomorrow Night, Pull the Clocks Back by One Hour
 # At 1 o'clock in the forenoon of Saturday 14 Mordad [=1978-08-05], the
 # clocks will be pulled one hour back and instead of 1 o'clock in the
 # forenoon, Radio Iran will announce 24 o'clock.
 # This decision was made in the Cabinet of Ministers meeting of 25 Tir
 # [=1978-07-16], [...]
 # At the beginning of the year 2537 [=March 1978: Iran was using a different
 # year number for a few years then, based on the Coronation of Cyrus the
 # Great], the country's official time was pulled forward by one hour and now
 # the official time is one hour and a half ahead compared to last year,
 # because in Farvardin of last year [=March 1977], the official time was
 # pulled forward one hour and this continued until the second half of last
 # year [=September 1977] until in the second half of last year the official
 # time was pulled back half an hour and that half hour still remains."
 #
 # This matches the time of the true noon published in the newspapers, as they
 # clearly go from +05:00 to +04:00 after that date (which happened during a
 # long weekend in Iran).
 
 # From Roozbeh Pournader (2022-05-31):
 # [Movahedi S. Cultural preconceptions of time: Can we use operational time
 # to meddle in God's Time? Comp Stud Soc Hist. 1985;27(3):385-400]
 # https://www.jstor.org/stable/178704
 # Here's the quotes from the paper:
 # 1. '"Iran's official time keeper moved the clock one hour forward as from
 # March 22, 1977 (Farvardin 2, 2536) to make maximum use of daylight and save
 # in energy consumption. Thus Iran joined such other countries as Britain in
 # observing what is known as 'daylight saving.' The proposal was originally
 # put forward by the Ministry of Energy, in no way having any influence on
 # observing religious ceremonies. Moving time one hour forward in summer
 # means that at 11:00 o'clock on March 21, the official time was set as
 # midnight March 22. Then September 24 will actually begin one hour later
 # than the end of September 23 [...]." Iran's time base thus continued to be
 # Greenwich Mean Time plus three and one-half hours (plus four and one-half
 # hours in summer).'
 #
 # The article sources this from Iran Almanac and Book of Facts, 1977, Tehran:
 # Echo of Iran, which is on Google Books at
 # https://www.google.com/books/edition/Iran_Almanac_and_Book_of_Facts/9ybVAAAAMAAJ.
 # (I confirmed it by searching for snippets.)
 #
 # 2. "After the fall of the shah, the revolutionary government returned to
 # daylight-saving time (DST) on 26 May 1979."
 #
 # This seems to have been announced just one day in advance, on 25 May 1979.
 #
 # The change in 1977 clearly seems to be the first daylight savings effort in
 # Iran. But the article doesn't mention what happened in 1978 (which was
 # still during the shah's government), or how things continued in 1979
 # onwards (which was during the Islamic Republic).
 
 # From Francis Santoni (2022-06-01):
-# for Iran and 1977 the effective change is only 20 october
-# (UIT No. 143 17.XI.1977) and not 23 september (UIT No. 141 13.IX.1977).
+# for Iran and 1977 the effective change is only 20 October
+# (UIT No. 143 17.XI.1977) and not 23 September (UIT No. 141 13.IX.1977).
 # UIT is the Operational Bulletin of International Telecommunication Union.
 
 # From Roozbeh Pournader (2003-03-15):
 # This is an English translation of what I just found (originally in Persian).
 # The Gregorian dates in brackets are mine:
 #
 #	Official Newspaper No. 13548-1370/6/25 [1991-09-16]
 #	No. 16760/T233 H				1370/6/10 [1991-09-01]
 #
 #	The Rule About Change of the Official Time of the Country
 #
 #	The Board of Ministers, in the meeting dated 1370/5/23 [1991-08-14],
 #	based on the suggestion number 2221/D dated 1370/4/22 [1991-07-13]
 #	of the Country's Organization for Official and Employment Affairs,
 #	and referring to the law for equating the working hours of workers
 #	and officers in the whole country dated 1359/4/23 [1980-07-14], and
 #	for synchronizing the official times of the country, agreed that:
 #
 #	The official time of the country will should move forward one hour
 #	at the 24[:00] hours of the first day of Farvardin and should return
 #	to its previous state at the 24[:00] hours of the 30th day of
 #	Shahrivar.
 #
 #	First Deputy to the President - Hassan Habibi
 #
 # From personal experience, that agrees with what has been followed
 # for at least the last 5 years.  Before that, for a few years, the
 # date used was the first Thursday night of Farvardin and the last
 # Thursday night of Shahrivar, but I can't give exact dates....
 #
 # From Roozbeh Pournader (2005-04-05):
 # The text of the Iranian law, in effect since 1925, clearly mentions
 # that the true solar year is the measure, and there is no arithmetic
 # leap year calculation involved.  There has never been any serious
 # plan to change that law....
 #
 # From Paul Eggert (2022-06-30):
 # Go with Pournader for 1935 through spring 1979, and for timestamps
 # after August 1991; go with with Shanks & Pottenger for other timestamps.
 # Go with Santoni's citation of the UIT for fall 1977, as 20 October 1977
 # is 28 Mehr 1356, consistent with the "Mehr" in Pournader's source.
 # Assume that the UIT's "1930" is UTC, i.e., 24:00 local time.
 #
 # From Oscar van Vlijmen (2005-03-30), writing about future
 # discrepancies between cal-persia and the Iranian calendar:
 # For 2091 solar-longitude-after yields 2091-03-20 08:40:07.7 UT for
 # the vernal equinox and that gets so close to 12:00 some local
 # Iranian time that the definition of the correct location needs to be
 # known exactly, amongst other factors.  2157 is even closer:
 # 2157-03-20 08:37:15.5 UT.  But the Gregorian year 2025 should give
 # no interpretation problem whatsoever.  By the way, another instant
 # in the near future where there will be a discrepancy between
 # arithmetical and astronomical Iranian calendars will be in 2058:
 # vernal equinox on 2058-03-20 09:03:05.9 UT.  The Java version of
 # Reingold's/Dershowitz' calculator gives correctly the Gregorian date
 # 2058-03-21 for 1 Farvardin 1437 (astronomical).
 #
 # From Steffen Thorsen (2006-03-22):
 # Several of my users have reported that Iran will not observe DST anymore:
 # http://www.irna.ir/en/news/view/line-17/0603193812164948.htm
 #
 # From Reuters (2007-09-16), with a heads-up from Jesper Nørgaard Welen:
 # ... the Guardian Council ... approved a law on Sunday to re-introduce
 # daylight saving time ...
 # https://uk.reuters.com/article/oilRpt/idUKBLA65048420070916
 #
 # From Roozbeh Pournader (2007-11-05):
 # This is quoted from Official Gazette of the Islamic Republic of
 # Iran, Volume 63, No. 18242, dated Tuesday 1386/6/24
 # [2007-10-16]. I am doing the best translation I can:...
 # The official time of the country will be moved forward for one hour
 # on the 24 hours of the first day of the month of Farvardin and will
 # be changed back to its previous state on the 24 hours of the
 # thirtieth day of Shahrivar.
 #
 # From Ali Mirjamali (2022-05-10):
 # Official IR News Agency announcement: irna.ir/xjJ3TT
 # ...
 # Highlights: DST will be cancelled for the next Iranian year 1402
 # (i.e 2023-March-21) and forthcoming years.
 #
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 # Work around a bug in zic 2022a and earlier.
 Rule	Iran	1910	only	-	Jan	 1	00:00	0	-
 #
 Rule	Iran	1977	only	-	Mar	21	23:00	1:00	-
 Rule	Iran	1977	only	-	Oct	20	24:00	0	-
 Rule	Iran	1978	only	-	Mar	24	24:00	1:00	-
 Rule	Iran	1978	only	-	Aug	 5	01:00	0	-
 Rule	Iran	1979	only	-	May	26	24:00	1:00	-
 Rule	Iran	1979	only	-	Sep	18	24:00	0	-
 Rule	Iran	1980	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	1980	only	-	Sep	22	24:00	0	-
 Rule	Iran	1991	only	-	May	 2	24:00	1:00	-
 Rule	Iran	1992	1995	-	Mar	21	24:00	1:00	-
 Rule	Iran	1991	1995	-	Sep	21	24:00	0	-
 Rule	Iran	1996	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	1996	only	-	Sep	20	24:00	0	-
 Rule	Iran	1997	1999	-	Mar	21	24:00	1:00	-
 Rule	Iran	1997	1999	-	Sep	21	24:00	0	-
 Rule	Iran	2000	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2000	only	-	Sep	20	24:00	0	-
 Rule	Iran	2001	2003	-	Mar	21	24:00	1:00	-
 Rule	Iran	2001	2003	-	Sep	21	24:00	0	-
 Rule	Iran	2004	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2004	only	-	Sep	20	24:00	0	-
 Rule	Iran	2005	only	-	Mar	21	24:00	1:00	-
 Rule	Iran	2005	only	-	Sep	21	24:00	0	-
 Rule	Iran	2008	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2008	only	-	Sep	20	24:00	0	-
 Rule	Iran	2009	2011	-	Mar	21	24:00	1:00	-
 Rule	Iran	2009	2011	-	Sep	21	24:00	0	-
 Rule	Iran	2012	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2012	only	-	Sep	20	24:00	0	-
 Rule	Iran	2013	2015	-	Mar	21	24:00	1:00	-
 Rule	Iran	2013	2015	-	Sep	21	24:00	0	-
 Rule	Iran	2016	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2016	only	-	Sep	20	24:00	0	-
 Rule	Iran	2017	2019	-	Mar	21	24:00	1:00	-
 Rule	Iran	2017	2019	-	Sep	21	24:00	0	-
 Rule	Iran	2020	only	-	Mar	20	24:00	1:00	-
 Rule	Iran	2020	only	-	Sep	20	24:00	0	-
 Rule	Iran	2021	2022	-	Mar	21	24:00	1:00	-
 Rule	Iran	2021	2022	-	Sep	21	24:00	0	-
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Tehran	3:25:44	-	LMT	1916
 			3:25:44	-	TMT	1935 Jun 13 # Tehran Mean Time
 			3:30	Iran	+0330/+0430 1977 Oct 20 24:00
 			4:00	Iran	+04/+05	1979
 			3:30	Iran	+0330/+0430
 
 
 # Iraq
 #
 # From Jonathan Lennox (2000-06-12):
 # An article in this week's Economist ("Inside the Saddam-free zone", p. 50 in
 # the U.S. edition) on the Iraqi Kurds contains a paragraph:
 # "The three northern provinces ... switched their clocks this spring and
 # are an hour ahead of Baghdad."
 #
 # But Rives McDow (2000-06-18) quotes a contact in Iraqi-Kurdistan as follows:
 # In the past, some Kurdish nationalists, as a protest to the Iraqi
 # Government, did not adhere to daylight saving time.  They referred
 # to daylight saving as Saddam time.  But, as of today, the time zone
 # in Iraqi-Kurdistan is on standard time with Baghdad, Iraq.
 #
 # So we'll ignore the Economist's claim.
 
 # From Steffen Thorsen (2008-03-10):
 # The cabinet in Iraq abolished DST last week, according to the following
 # news sources (in Arabic):
 # http://www.aljeeran.net/wesima_articles/news-20080305-98602.html
 # http://www.aswataliraq.info/look/article.tpl?id=2047&IdLanguage=17&IdPublication=4&NrArticle=71743&NrIssue=1&NrSection=10
 #
 # We have published a short article in English about the change:
 # https://www.timeanddate.com/news/time/iraq-dumps-daylight-saving.html
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Iraq	1982	only	-	May	1	0:00	1:00	-
 Rule	Iraq	1982	1984	-	Oct	1	0:00	0	-
 Rule	Iraq	1983	only	-	Mar	31	0:00	1:00	-
 Rule	Iraq	1984	1985	-	Apr	1	0:00	1:00	-
 Rule	Iraq	1985	1990	-	Sep	lastSun	1:00s	0	-
 Rule	Iraq	1986	1990	-	Mar	lastSun	1:00s	1:00	-
 # IATA SSIM (1991/1996) says Apr 1 12:01am UTC; guess the ':01' is a typo.
 # Shanks & Pottenger say Iraq did not observe DST 1992/1997; ignore this.
 #
 Rule	Iraq	1991	2007	-	Apr	 1	3:00s	1:00	-
 Rule	Iraq	1991	2007	-	Oct	 1	3:00s	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Baghdad	2:57:40	-	LMT	1890
 			2:57:36	-	BMT	1918     # Baghdad Mean Time?
 			3:00	-	+03	1982 May
 			3:00	Iraq	+03/+04
 
 
 ###############################################################################
 
 # Israel
 
 # For more info about the motivation for DST in Israel, see:
 # Barak Y. Israel's Daylight Saving Time controversy. Israel Affairs.
 # 2020-08-11. https://doi.org/10.1080/13537121.2020.1806564
 
 # From Ephraim Silverberg (2001-01-11):
 #
 # I coined "IST/IDT" circa 1988.  Until then there were three
 # different abbreviations in use:
 #
 # JST  Jerusalem Standard Time [Danny Braniss, Hebrew University]
 # IZT  Israel Zonal (sic) Time [Prof. Haim Papo, Technion]
 # EEST Eastern Europe Standard Time [used by almost everyone else]
 #
 # Since timezones should be called by country and not capital cities,
 # I ruled out JST.  As Israel is in Asia Minor and not Eastern Europe,
 # EEST was equally unacceptable.  Since "zonal" was not compatible with
 # any other timezone abbreviation, I felt that 'IST' was the way to go
 # and, indeed, it has received almost universal acceptance in timezone
 # settings in Israeli computers.
 #
 # In any case, I am happy to share timezone abbreviations with India,
 # high on my favorite-country list (and not only because my wife's
 # family is from India).
 
 # From P Chan (2020-10-27), with corrections:
 #
 # 1940-1946 Supplement No. 2 to the Palestine Gazette
 # # issue page  Order No.   dated      start        end         note
 # 1 1010  729  67 of 1940 1940-05-22 1940-05-31* 1940-09-30* revoked by #2
 # 2 1013  758  73 of 1940 1940-05-31 1940-05-31  1940-09-30
 # 3 1055 1574 196 of 1940 1940-11-06 1940-11-16  1940-12-31
 # 4 1066 1811 208 of 1940 1940-12-17 1940-12-31  1941-12-31
 # 5 1156 1967 116 of 1941 1941-12-16 1941-12-31  1942-12-31* amended by #6
 # 6 1228 1608  86 of 1942 1942-10-14 1941-12-31  1942-10-31
 # 7 1256  279  21 of 1943 1943-03-18 1943-03-31  1943-10-31
 # 8 1323  249  19 of 1944 1944-03-13 1944-03-31  1944-10-31
 # 9 1402  328  20 of 1945 1945-04-05 1945-04-15  1945-10-31
 #10 1487  596  14 of 1946 1946-04-04 1946-04-15  1946-10-31
 #
 # 1948 Iton Rishmi (Official Gazette of the Provisional Government)
 # #    issue    page   dated      start       end
 #11 2             7 1948-05-20 1948-05-22 1948-10-31*
 #	^This moved timezone to +04, replaced by #12 from 1948-08-31 24:00 GMT.
 #12 17 (Annex B) 84 1948-08-22 1948-08-31 1948-10-31
 #
 # 1949-2000 Kovetz HaTakanot (Collection of Regulations)
 # # issue page  dated      start       end            note
 #13    6  133 1949-03-23 1949-04-30  1949-10-31
 #14   80  755 1950-03-17 1950-04-15  1950-09-14
 #15  164  782 1951-03-22 1951-03-31  1951-09-29* amended by #16
 #16  206 1940 1951-09-23 ----------  1951-10-22* amended by #17
 #17  212   78 1951-10-19 ----------  1951-11-10
 #18  254  652 1952-03-03 1952-04-19  1952-09-27* amended by #19
 #19  300   11 1952-09-15 ----------  1952-10-18
 #20  348  817 1953-03-03 1953-04-11  1953-09-12
 #21  420  385 1954-02-17 1954-06-12  1954-09-11
 #22  497  548 1955-01-14 1955-06-11  1955-09-10
 #23  591  608 1956-03-12 1956-06-02  1956-09-29
 #24  680  957 1957-02-08 1957-04-27  1957-09-21
 #25 3192 1418 1974-06-28 1974-07-06  1974-10-12
 #26 3322 1389 1975-04-03 1975-04-19  1975-08-30
 #27 4146 2089 1980-07-15 1980-08-02  1980-09-13
 #28 4604 1081 1984-02-22 1984-05-05* 1984-08-25* revoked by #29
 #29 4619 1312 1984-04-06 1984-05-05  1984-08-25
 #30 4744  475 1984-12-23 1985-04-13  1985-09-14* amended by #31
 #31 4851 1848 1985-08-18 ----------  1985-08-31
 #32 4932  899 1986-04-22 1986-05-17  1986-09-06
 #33 5013  580 1987-02-15 1987-04-18* 1987-08-22* revoked by #34
 #34 5021  744 1987-03-30 1987-04-14  1987-09-12
 #35 5096  659 1988-02-14 1988-04-09  1988-09-03
 #36 5167  514 1989-02-03 1989-04-29  1989-09-02
 #37 5248  375 1990-01-23 1990-03-24  1990-08-25
 #38 5335  612 1991-02-10 1991-03-09* 1991-08-31	 amended by #39
 #			 1992-03-28  1992-09-05
 #39 5339  709 1991-03-04 1991-03-23  ----------
 #40 5506  503 1993-02-18 1993-04-02  1993-09-05
 #			 1994-04-01  1994-08-28
 #			 1995-03-31  1995-09-03
 #41 5731  438 1996-01-01 1996-03-14  1996-09-15
 #			 1997-03-13* 1997-09-18* overridden by 1997 Temp Prov
 #			 1998-03-19* 1998-09-17* revoked by #42
 #42 5853 1243 1997-09-18 1998-03-19  1998-09-05
 #43 5937   77 1998-10-18 1999-04-02  1999-09-03
 #			 2000-04-14* 2000-09-15* revoked by #44
 #			 2001-04-13* 2001-09-14* revoked by #44
 #44 6024   39 2000-03-14 2000-04-14  2000-10-22* overridden by 2000 Temp Prov
 #			 2001-04-06* 2001-10-10* overridden by 2000 Temp Prov
 #			 2002-03-29* 2002-10-29* overridden by 2000 Temp Prov
 #
 # These are laws enacted by the Knesset since the Minister could only alter the
 # transition dates at least six months in advanced under the 1992 Law.
 #				dated		start		end
 # 1997 Temporary Provisions	1997-03-06	1997-03-20	1997-09-13
 # 2000 Temporary Provisions	2000-07-28	----------	2000-10-06
 #						2001-04-09	2001-09-24
 #						2002-03-29	2002-10-07
 #						2003-03-28	2003-10-03
 #						2004-04-07	2004-09-22
 # Note:
 # Transition times in 1940-1957 (#1-#24) were midnight GMT,
 # in 1974-1998 (#25-#42 and the 1997 Temporary Provisions) were midnight,
 # in 1999-April 2000 (#43,#44) were 02:00,
 # in the 2000 Temporary Provisions were 01:00.
 #
 # -----------------------------------------------------------------------------
 # Links:
 # 1 https://findit.library.yale.edu/images_layout/view?parentoid=15537490&increment=687
 # 2 https://findit.library.yale.edu/images_layout/view?parentoid=15537490&increment=716
 # 3 https://findit.library.yale.edu/images_layout/view?parentoid=15537491&increment=721
 # 4 https://findit.library.yale.edu/images_layout/view?parentoid=15537491&increment=958
 # 5 https://findit.library.yale.edu/images_layout/view?parentoid=15537502&increment=558
 # 6 https://findit.library.yale.edu/images_layout/view?parentoid=15537511&increment=105
 # 7 https://findit.library.yale.edu/images_layout/view?parentoid=15537516&increment=278
 # 8 https://findit.library.yale.edu/images_layout/view?parentoid=15537522&increment=248
 # 9 https://findit.library.yale.edu/images_layout/view?parentoid=15537530&increment=329
 #10 https://findit.library.yale.edu/images_layout/view?parentoid=15537537&increment=601
 #11 https://www.nevo.co.il/law_word/law12/er-002.pdf#page=3
 #12 https://www.nevo.co.il/law_word/law12/er-017-t2.pdf#page=4
 #13 https://www.nevo.co.il/law_word/law06/tak-0006.pdf#page=3
 #14 https://www.nevo.co.il/law_word/law06/tak-0080.pdf#page=7
 #15 https://www.nevo.co.il/law_word/law06/tak-0164.pdf#page=10
 #16 https://www.nevo.co.il/law_word/law06/tak-0206.pdf#page=4
 #17 https://www.nevo.co.il/law_word/law06/tak-0212.pdf#page=2
 #18 https://www.nevo.co.il/law_word/law06/tak-0254.pdf#page=4
 #19 https://www.nevo.co.il/law_word/law06/tak-0300.pdf#page=5
 #20 https://www.nevo.co.il/law_word/law06/tak-0348.pdf#page=3
 #21 https://www.nevo.co.il/law_word/law06/tak-0420.pdf#page=5
 #22 https://www.nevo.co.il/law_word/law06/tak-0497.pdf#page=10
 #23 https://www.nevo.co.il/law_word/law06/tak-0591.pdf#page=6
 #24 https://www.nevo.co.il/law_word/law06/tak-0680.pdf#page=3
 #25 https://www.nevo.co.il/law_word/law06/tak-3192.pdf#page=2
 #26 https://www.nevo.co.il/law_word/law06/tak-3322.pdf#page=5
 #27 https://www.nevo.co.il/law_word/law06/tak-4146.pdf#page=2
 #28 https://www.nevo.co.il/law_word/law06/tak-4604.pdf#page=7
 #29 https://www.nevo.co.il/law_word/law06/tak-4619.pdf#page=2
 #30 https://www.nevo.co.il/law_word/law06/tak-4744.pdf#page=11
 #31 https://www.nevo.co.il/law_word/law06/tak-4851.pdf#page=2
 #32 https://www.nevo.co.il/law_word/law06/tak-4932.pdf#page=19
 #33 https://www.nevo.co.il/law_word/law06/tak-5013.pdf#page=8
 #34 https://www.nevo.co.il/law_word/law06/tak-5021.pdf#page=8
 #35 https://www.nevo.co.il/law_word/law06/tak-5096.pdf#page=3
 #36 https://www.nevo.co.il/law_word/law06/tak-5167.pdf#page=2
 #37 https://www.nevo.co.il/law_word/law06/tak-5248.pdf#page=7
 #38 https://www.nevo.co.il/law_word/law06/tak-5335.pdf#page=6
 #39 https://www.nevo.co.il/law_word/law06/tak-5339.pdf#page=7
 #40 https://www.nevo.co.il/law_word/law06/tak-5506.pdf#page=19
 #41 https://www.nevo.co.il/law_word/law06/tak-5731.pdf#page=2
 #42 https://www.nevo.co.il/law_word/law06/tak-5853.pdf#page=3
 #43 https://www.nevo.co.il/law_word/law06/tak-5937.pdf#page=9
 #44 https://www.nevo.co.il/law_word/law06/tak-6024.pdf#page=4
 #
 # Time Determination (Temporary Provisions) Law, 1997
 # https://www.nevo.co.il/law_html/law19/p201_003.htm
 #
 # Time Determination (Temporary Provisions) Law, 2000
 # https://www.nevo.co.il/law_html/law19/p201_004.htm
 #
 # Time Determination Law, 1992 and amendments
 # https://www.nevo.co.il/law_html/law01/p201_002.htm
 # https://main.knesset.gov.il/Activity/Legislation/Laws/Pages/LawPrimary.aspx?lawitemid=2001174
 
 # From Paul Eggert (2020-10-27):
 # Several of the midnight transitions mentioned above are ambiguous;
 # are they 00:00, 00:00s, 24:00, or 24:00s?  When resolving these ambiguities,
 # try to minimize changes from previous tzdb versions, for lack of better info.
 # Commentary from previous versions is included below, to help explain this.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	1940	only	-	May	31	24:00u	1:00	D
 Rule	Zion	1940	only	-	Sep	30	24:00u	0	S
 Rule	Zion	1940	only	-	Nov	16	24:00u	1:00	D
 Rule	Zion	1942	1946	-	Oct	31	24:00u	0	S
 Rule	Zion	1943	1944	-	Mar	31	24:00u	1:00	D
 Rule	Zion	1945	1946	-	Apr	15	24:00u	1:00	D
 Rule	Zion	1948	only	-	May	22	24:00u	2:00	DD
 Rule	Zion	1948	only	-	Aug	31	24:00u	1:00	D
 Rule	Zion	1948	1949	-	Oct	31	24:00u	0	S
 Rule	Zion	1949	only	-	Apr	30	24:00u	1:00	D
 Rule	Zion	1950	only	-	Apr	15	24:00u	1:00	D
 Rule	Zion	1950	only	-	Sep	14	24:00u	0	S
 Rule	Zion	1951	only	-	Mar	31	24:00u	1:00	D
 Rule	Zion	1951	only	-	Nov	10	24:00u	0	S
 Rule	Zion	1952	only	-	Apr	19	24:00u	1:00	D
 Rule	Zion	1952	only	-	Oct	18	24:00u	0	S
 Rule	Zion	1953	only	-	Apr	11	24:00u	1:00	D
 Rule	Zion	1953	only	-	Sep	12	24:00u	0	S
 Rule	Zion	1954	only	-	Jun	12	24:00u	1:00	D
 Rule	Zion	1954	only	-	Sep	11	24:00u	0	S
 Rule	Zion	1955	only	-	Jun	11	24:00u	1:00	D
 Rule	Zion	1955	only	-	Sep	10	24:00u	0	S
 Rule	Zion	1956	only	-	Jun	 2	24:00u	1:00	D
 Rule	Zion	1956	only	-	Sep	29	24:00u	0	S
 Rule	Zion	1957	only	-	Apr	27	24:00u	1:00	D
 Rule	Zion	1957	only	-	Sep	21	24:00u	0	S
 Rule	Zion	1974	only	-	Jul	 6	24:00	1:00	D
 Rule	Zion	1974	only	-	Oct	12	24:00	0	S
 Rule	Zion	1975	only	-	Apr	19	24:00	1:00	D
 Rule	Zion	1975	only	-	Aug	30	24:00	0	S
 
 # From Alois Treindl (2019-03-06):
 # http://www.moin.gov.il/Documents/שעון%20קיץ/clock-50-years-7-2014.pdf
 # From Isaac Starkman (2019-03-06):
 # Summer time was in that period in 1980 and 1984, see
 # https://www.ynet.co.il/articles/0,7340,L-3951073,00.html
 # You can of course read it in translation.
 # I checked the local newspapers for that years.
 # It started on midnight and end at 01.00 am.
 # From Paul Eggert (2019-03-06):
 # Also see this thread about the moin.gov.il URL:
 # https://mm.icann.org/pipermail/tz/2018-November/027194.html
 Rule	Zion	1980	only	-	Aug	 2	24:00s	1:00	D
 Rule	Zion	1980	only	-	Sep	13	24:00s	0	S
 Rule	Zion	1984	only	-	May	 5	24:00s	1:00	D
 Rule	Zion	1984	only	-	Aug	25	24:00s	0	S
 
 Rule	Zion	1985	only	-	Apr	13	24:00	1:00	D
 Rule	Zion	1985	only	-	Aug	31	24:00	0	S
 Rule	Zion	1986	only	-	May	17	24:00	1:00	D
 Rule	Zion	1986	only	-	Sep	 6	24:00	0	S
 Rule	Zion	1987	only	-	Apr	14	24:00	1:00	D
 Rule	Zion	1987	only	-	Sep	12	24:00	0	S
 
 # From Avigdor Finkelstein (2014-03-05):
 # I check the Parliament (Knesset) records and there it's stated that the
 # [1988] transition should take place on Saturday night, when the Sabbath
 # ends and changes to Sunday.
 Rule	Zion	1988	only	-	Apr	 9	24:00	1:00	D
 Rule	Zion	1988	only	-	Sep	 3	24:00	0	S
 
 # From Ephraim Silverberg
 # (1997-03-04, 1998-03-16, 1998-12-28, 2000-01-17, 2000-07-25, 2004-12-22,
 # and 2005-02-17):
 
 # According to the Office of the Secretary General of the Ministry of
 # Interior, there is NO set rule for Daylight-Savings/Standard time changes.
 # One thing is entrenched in law, however: that there must be at least 150
 # days of daylight savings time annually.  From 1993-1998, the change to
 # daylight savings time was on a Friday morning from midnight IST to
 # 1 a.m IDT; up until 1998, the change back to standard time was on a
 # Saturday night from midnight daylight savings time to 11 p.m. standard
 # time.  1996 is an exception to this rule where the change back to standard
 # time took place on Sunday night instead of Saturday night to avoid
 # conflicts with the Jewish New Year.  In 1999, the change to
 # daylight savings time was still on a Friday morning but from
 # 2 a.m. IST to 3 a.m. IDT; furthermore, the change back to standard time
 # was also on a Friday morning from 2 a.m. IDT to 1 a.m. IST for
 # 1999 only.  In the year 2000, the change to daylight savings time was
 # similar to 1999, but although the change back will be on a Friday, it
 # will take place from 1 a.m. IDT to midnight IST.  Starting in 2001, all
 # changes to/from will take place at 1 a.m. old time, but now there is no
 # rule as to what day of the week it will take place in as the start date
 # (except in 2003) is the night after the Passover Seder (i.e. the eve
 # of the 16th of Nisan in the lunar Hebrew calendar) and the end date
 # (except in 2002) is three nights before Yom Kippur [Day of Atonement]
 # (the eve of the 7th of Tishrei in the lunar Hebrew calendar).
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	1989	only	-	Apr	29	24:00	1:00	D
 Rule	Zion	1989	only	-	Sep	 2	24:00	0	S
 Rule	Zion	1990	only	-	Mar	24	24:00	1:00	D
 Rule	Zion	1990	only	-	Aug	25	24:00	0	S
 Rule	Zion	1991	only	-	Mar	23	24:00	1:00	D
 Rule	Zion	1991	only	-	Aug	31	24:00	0	S
 Rule	Zion	1992	only	-	Mar	28	24:00	1:00	D
 Rule	Zion	1992	only	-	Sep	 5	24:00	0	S
 Rule	Zion	1993	only	-	Apr	 2	0:00	1:00	D
 Rule	Zion	1993	only	-	Sep	 5	0:00	0	S
 
 # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the
 # Ministry of Interior, Jerusalem, Israel.  The spokeswoman can be reached by
 # calling the office directly at 972-2-6701447 or 972-2-6701448.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	1994	only	-	Apr	 1	0:00	1:00	D
 Rule	Zion	1994	only	-	Aug	28	0:00	0	S
 Rule	Zion	1995	only	-	Mar	31	0:00	1:00	D
 Rule	Zion	1995	only	-	Sep	 3	0:00	0	S
 
 # The dates for 1996 were determined by the Minister of Interior of the
 # time, Haim Ramon.  The official announcement regarding 1996-1998
 # (with the dates for 1997-1998 no longer being relevant) can be viewed at:
 #
 #   ftp://ftp.cs.huji.ac.il/pub/tz/announcements/1996-1998.ramon.ps.gz
 #
 # The dates for 1997-1998 were altered by his successor, Rabbi Eli Suissa.
 #
 # The official announcements for the years 1997-1999 can be viewed at:
 #
 #   ftp://ftp.cs.huji.ac.il/pub/tz/announcements/YYYY.ps.gz
 #
 #       where YYYY is the relevant year.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	1996	only	-	Mar	14	24:00	1:00	D
 Rule	Zion	1996	only	-	Sep	15	24:00	0	S
 Rule	Zion	1997	only	-	Mar	20	24:00	1:00	D
 Rule	Zion	1997	only	-	Sep	13	24:00	0	S
 Rule	Zion	1998	only	-	Mar	20	0:00	1:00	D
 Rule	Zion	1998	only	-	Sep	 6	0:00	0	S
 Rule	Zion	1999	only	-	Apr	 2	2:00	1:00	D
 Rule	Zion	1999	only	-	Sep	 3	2:00	0	S
 
 # The Knesset Interior Committee has changed the dates for 2000 for
 # the third time in just over a year and have set new dates for the
 # years 2001-2004 as well.
 #
 # The official announcement for the start date of 2000 can be viewed at:
 #
 #	ftp://ftp.cs.huji.ac.il/pub/tz/announcements/2000-start.ps.gz
 #
 # The official announcement for the end date of 2000 and the dates
 # for the years 2001-2004 can be viewed at:
 #
 #	ftp://ftp.cs.huji.ac.il/pub/tz/announcements/2000-2004.ps.gz
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	2000	only	-	Apr	14	2:00	1:00	D
 Rule	Zion	2000	only	-	Oct	 6	1:00	0	S
 Rule	Zion	2001	only	-	Apr	 9	1:00	1:00	D
 Rule	Zion	2001	only	-	Sep	24	1:00	0	S
 Rule	Zion	2002	only	-	Mar	29	1:00	1:00	D
 Rule	Zion	2002	only	-	Oct	 7	1:00	0	S
 Rule	Zion	2003	only	-	Mar	28	1:00	1:00	D
 Rule	Zion	2003	only	-	Oct	 3	1:00	0	S
 Rule	Zion	2004	only	-	Apr	 7	1:00	1:00	D
 Rule	Zion	2004	only	-	Sep	22	1:00	0	S
 
 # The proposed law agreed upon by the Knesset Interior Committee on
 # 2005-02-14 is that, for 2005 and beyond, DST starts at 02:00 the
 # last Friday before April 2nd (i.e. the last Friday in March or April
 # 1st itself if it falls on a Friday) and ends at 02:00 on the Saturday
 # night _before_ the fast of Yom Kippur.
 #
 # Those who can read Hebrew can view the announcement at:
 #
 #	ftp://ftp.cs.huji.ac.il/pub/tz/announcements/2005+beyond.ps
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	2005	2012	-	Apr	Fri<=1	2:00	1:00	D
 Rule	Zion	2005	only	-	Oct	 9	2:00	0	S
 Rule	Zion	2006	only	-	Oct	 1	2:00	0	S
 Rule	Zion	2007	only	-	Sep	16	2:00	0	S
 Rule	Zion	2008	only	-	Oct	 5	2:00	0	S
 Rule	Zion	2009	only	-	Sep	27	2:00	0	S
 Rule	Zion	2010	only	-	Sep	12	2:00	0	S
 Rule	Zion	2011	only	-	Oct	 2	2:00	0	S
 Rule	Zion	2012	only	-	Sep	23	2:00	0	S
 
 # From Ephraim Silverberg (2020-10-26):
 # The current time law (2013) from the State of Israel can be viewed
 # (in Hebrew) at:
 # ftp://ftp.cs.huji.ac.il/pub/tz/israel/announcements/2013+law.pdf
 # It translates to:
 # Every year, in the period from the Friday before the last Sunday in
 # the month of March at 02:00 a.m. until the last Sunday of the month
 # of October at 02:00 a.m., Israel Time will be advanced an additional
 # hour such that it will be UTC+3.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Zion	2013	max	-	Mar	Fri>=23	2:00	1:00	D
 Rule	Zion	2013	max	-	Oct	lastSun	2:00	0	S
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Jerusalem	2:20:54 -	LMT	1880
 			2:20:40	-	JMT	1918 # Jerusalem Mean Time?
 			2:00	Zion	I%sT
 
 
 
 ###############################################################################
 
 # Japan
 
 # '9:00' and 'JST' is from Guy Harris.
 
 # From Paul Eggert (2020-01-19):
 # Starting in the 7th century, Japan generally followed an ancient Chinese
 # timekeeping system that divided night and day into six hours each,
 # with hour length depending on season.  In 1873 the government
 # started requiring the use of a Western style 24-hour clock.  See:
 # Yulia Frumer, "Making Time: Astronomical Time Measurement in Tokugawa Japan"
 # .  As the tzdb code and
 # data support only 24-hour clocks, its tables model timestamps before
 # 1873 using Western-style local mean time.
 
 # From Hideyuki Suzuki (1998-11-09):
 # 'Tokyo' usually stands for the former location of Tokyo Astronomical
 # Observatory: 139° 44' 40.90" E (9h 18m 58.727s), 35° 39' 16.0" N.
 # This data is from 'Rika Nenpyou (Chronological Scientific Tables) 1996'
 # edited by National Astronomical Observatory of Japan....
 # JST (Japan Standard Time) has been used since 1888-01-01 00:00 (JST).
 # The law is enacted on 1886-07-07.
 
 # From Hideyuki Suzuki (1998-11-16):
 # The ordinance No. 51 (1886) established "standard time" in Japan,
 # which stands for the time on 135° E.
 # In the ordinance No. 167 (1895), "standard time" was renamed to "central
 # standard time".  And the same ordinance also established "western standard
 # time", which stands for the time on 120° E....  But "western standard
 # time" was abolished in the ordinance No. 529 (1937).  In the ordinance No.
 # 167, there is no mention regarding for what place western standard time is
 # standard....
 #
 # I wrote "ordinance" above, but I don't know how to translate.
 # In Japanese it's "chokurei", which means ordinance from emperor.
 
 # From Yu-Cheng Chuang (2013-07-12):
 # ...the Meiji Emperor announced Ordinance No. 167 of Meiji Year 28 "The clause
 # about standard time" ... The adoption began from Jan 1, 1896.
 # https://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時)
 #
 # ...the Showa Emperor announced Ordinance No. 529 of Showa Year 12 ... which
 # means the whole Japan territory, including later occupations, adopt Japan
 # Central Time (UT+9). The adoption began on Oct 1, 1937.
 # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件
 
 # From Paul Eggert (1995-03-06):
 # Today's _Asahi Evening News_ (page 4) reports that Japan had
 # daylight saving between 1948 and 1951, but "the system was discontinued
 # because the public believed it would lead to longer working hours."
 
 # From Mayumi Negishi in the 2005-08-10 Japan Times:
 # http://www.japantimes.co.jp/cgi-bin/getarticle.pl5?nn20050810f2.htm
 # Occupation authorities imposed daylight-saving time on Japan on
 # [1948-05-01]....  But lack of prior debate and the execution of
 # daylight-saving time just three days after the bill was passed generated
 # deep hatred of the concept....  The Diet unceremoniously passed a bill to
 # dump the unpopular system in October 1951, less than a month after the San
 # Francisco Peace Treaty was signed.  (A government poll in 1951 showed 53%
 # of the Japanese wanted to scrap daylight-saving time, as opposed to 30% who
 # wanted to keep it.)
 
 # From Takayuki Nikai (2018-01-19):
 # The source of information is Japanese law.
 # http://www.shugiin.go.jp/internet/itdb_housei.nsf/html/houritsu/00219480428029.htm
 # http://www.shugiin.go.jp/internet/itdb_housei.nsf/html/houritsu/00719500331039.htm
 # ... In summary, it is written as follows.  From 24:00 on the first Saturday
 # in May, until 0:00 on the day after the second Saturday in September.
 
 # From Phake Nick (2018-09-27):
 # [T]he webpage authored by National Astronomical Observatory of Japan
 # https://eco.mtk.nao.ac.jp/koyomi/wiki/BBFEB9EF2FB2C6BBFEB9EF.html
 # ... mentioned that using Showa 23 (year 1948) as example, 13pm of September
 # 11 in summer time will equal to 0am of September 12 in standard time.
 # It cited a document issued by the Liaison Office which briefly existed
 # during the postwar period of Japan, where the detail on implementation
 # of the summer time is described in the document.
 # https://eco.mtk.nao.ac.jp/koyomi/wiki/BBFEB9EF2FB2C6BBFEB9EFB2C6BBFEB9EFA4CEBCC2BBDCA4CBA4C4A4A4A4C6.pdf
 # The text in the document do instruct a fall back to occur at
 # September 11, 13pm in summer time, while ordinary citizens can
 # change the clock before they sleep.
 #
 # From Paul Eggert (2018-09-27):
 # This instruction is equivalent to "Sat>=8 25:00", so use that.  zic treats
 # it like "Sun>=9 01:00", which is not quite the same but is the best we can
 # do in any POSIX or C platform.  The "25:00" assumes zic from 2007 or later,
 # which should be safe now.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Japan	1948	only	-	May	Sat>=1	24:00	1:00	D
 Rule	Japan	1948	1951	-	Sep	Sat>=8	25:00	0	S
 Rule	Japan	1949	only	-	Apr	Sat>=1	24:00	1:00	D
 Rule	Japan	1950	1951	-	May	Sat>=1	24:00	1:00	D
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Tokyo	9:18:59	-	LMT	1887 Dec 31 15:00u
 			9:00	Japan	J%sT
 # Since 1938, all Japanese possessions have been like Asia/Tokyo,
 # except that Truk (Chuuk), Ponape (Pohnpei), and Jaluit (Kosrae) did not
 # switch from +10 to +09 until 1941-04-01; see the 'australasia' file.
 
 # Jordan
 #
 # From 
 # Jordan Week (1999-07-01) via Steffen Thorsen (1999-09-09):
 # Clocks in Jordan were forwarded one hour on Wednesday at midnight,
 # in accordance with the government's decision to implement summer time
 # all year round.
 #
 # From 
 # Jordan Week (1999-09-30) via Steffen Thorsen (1999-11-09):
 # Winter time starts today Thursday, 30 September. Clocks will be turned back
 # by one hour.  This is the latest government decision and it's final!
 # The decision was taken because of the increase in working hours in
 # government's departments from six to seven hours.
 #
 # From Paul Eggert (2005-11-22):
 # Starting 2003 transitions are from Steffen Thorsen's web site timeanddate.com.
 #
 # From Steffen Thorsen (2005-11-23):
 # For Jordan I have received multiple independent user reports every year
 # about DST end dates, as the end-rule is different every year.
 #
 # From Steffen Thorsen (2006-10-01), after a heads-up from Hilal Malawi:
 # http://www.petranews.gov.jo/nepras/2006/Sep/05/4000.htm
 # "Jordan will switch to winter time on Friday, October 27".
 #
 
 # From Steffen Thorsen (2009-04-02):
 # This single one might be good enough, (2009-03-24, Arabic):
 # http://petra.gov.jo/Artical.aspx?Lng=2&Section=8&Artical=95279
 #
 # Google's translation:
 #
 # > The Council of Ministers decided in 2002 to adopt the principle of timely
 # > submission of the summer at 60 minutes as of midnight on the last Thursday
 # > of the month of March of each year.
 #
 # So - this means the midnight between Thursday and Friday since 2002.
 
 # From Arthur David Olson (2009-04-06):
 # We still have Jordan switching to DST on Thursdays in 2000 and 2001.
 
 # From Steffen Thorsen (2012-10-25):
 # Yesterday the government in Jordan announced that they will not
 # switch back to standard time this winter, so the will stay on DST
 # until about the same time next year (at least).
 # http://www.petra.gov.jo/Public_News/Nws_NewsDetails.aspx?NewsID=88950
 
 # From Steffen Thorsen (2013-12-11):
 # Jordan Times and other sources say that Jordan is going back to
 # UTC+2 on 2013-12-19 at midnight:
 # http://jordantimes.com/govt-decides-to-switch-back-to-wintertime
 # Official, in Arabic:
 # http://www.petra.gov.jo/public_news/Nws_NewsDetails.aspx?Menu_ID=&Site_Id=2&lang=1&NewsID=133230&CatID=14
 # ... Our background/permalink about it
 # https://www.timeanddate.com/news/time/jordan-reverses-dst-decision.html
 # ...
 # http://www.petra.gov.jo/Public_News/Nws_NewsDetails.aspx?lang=2&site_id=1&NewsID=133313&Type=P
 # ... says midnight for the coming one and 1:00 for the ones in the future
 # (and they will use DST again next year, using the normal schedule).
 
 # From Paul Eggert (2013-12-11):
 # As Steffen suggested, consider the past 21-month experiment to be DST.
 
 # From Steffen Thorsen (2021-09-24):
 # The Jordanian Government announced yesterday that they will start DST
 # in February instead of March:
 # https://petra.gov.jo/Include/InnerPage.jsp?ID=37683&lang=en&name=en_news (English)
 # https://petra.gov.jo/Include/InnerPage.jsp?ID=189969&lang=ar&name=news (Arabic)
 # From the Arabic version, it seems to say it would be at midnight
 # (assume 24:00) on the last Thursday in February, starting from 2022.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Jordan	1973	only	-	Jun	6	0:00	1:00	S
 Rule	Jordan	1973	1975	-	Oct	1	0:00	0	-
 Rule	Jordan	1974	1977	-	May	1	0:00	1:00	S
 Rule	Jordan	1976	only	-	Nov	1	0:00	0	-
 Rule	Jordan	1977	only	-	Oct	1	0:00	0	-
 Rule	Jordan	1978	only	-	Apr	30	0:00	1:00	S
 Rule	Jordan	1978	only	-	Sep	30	0:00	0	-
 Rule	Jordan	1985	only	-	Apr	1	0:00	1:00	S
 Rule	Jordan	1985	only	-	Oct	1	0:00	0	-
 Rule	Jordan	1986	1988	-	Apr	Fri>=1	0:00	1:00	S
 Rule	Jordan	1986	1990	-	Oct	Fri>=1	0:00	0	-
 Rule	Jordan	1989	only	-	May	8	0:00	1:00	S
 Rule	Jordan	1990	only	-	Apr	27	0:00	1:00	S
 Rule	Jordan	1991	only	-	Apr	17	0:00	1:00	S
 Rule	Jordan	1991	only	-	Sep	27	0:00	0	-
 Rule	Jordan	1992	only	-	Apr	10	0:00	1:00	S
 Rule	Jordan	1992	1993	-	Oct	Fri>=1	0:00	0	-
 Rule	Jordan	1993	1998	-	Apr	Fri>=1	0:00	1:00	S
 Rule	Jordan	1994	only	-	Sep	Fri>=15	0:00	0	-
 Rule	Jordan	1995	1998	-	Sep	Fri>=15	0:00s	0	-
 Rule	Jordan	1999	only	-	Jul	 1	0:00s	1:00	S
 Rule	Jordan	1999	2002	-	Sep	lastFri	0:00s	0	-
 Rule	Jordan	2000	2001	-	Mar	lastThu	0:00s	1:00	S
 Rule	Jordan	2002	2012	-	Mar	lastThu	24:00	1:00	S
 Rule	Jordan	2003	only	-	Oct	24	0:00s	0	-
 Rule	Jordan	2004	only	-	Oct	15	0:00s	0	-
 Rule	Jordan	2005	only	-	Sep	lastFri	0:00s	0	-
 Rule	Jordan	2006	2011	-	Oct	lastFri	0:00s	0	-
 Rule	Jordan	2013	only	-	Dec	20	0:00	0	-
 Rule	Jordan	2014	2021	-	Mar	lastThu	24:00	1:00	S
 Rule	Jordan	2014	max	-	Oct	lastFri	0:00s	0	-
 Rule	Jordan	2022	max	-	Feb	lastThu	24:00	1:00	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Amman	2:23:44 -	LMT	1931
 			2:00	Jordan	EE%sT
 
 
 # Kazakhstan
 
 # From Kazakhstan Embassy's News Bulletin No. 11
 #  (2005-03-21):
 # The Government of Kazakhstan passed a resolution March 15 abolishing
 # daylight saving time citing lack of economic benefits and health
 # complications coupled with a decrease in productivity.
 #
 # From Branislav Kojic (in Astana) via Gwillim Law (2005-06-28):
 # ... what happened was that the former Kazakhstan Eastern time zone
 # was "blended" with the Central zone.  Therefore, Kazakhstan now has
 # two time zones, and difference between them is one hour.  The zone
 # closer to UTC is the former Western zone (probably still called the
 # same), encompassing four provinces in the west: Aqtöbe, Atyraū,
 # Mangghystaū, and West Kazakhstan.  The other zone encompasses
 # everything else....  I guess that would make Kazakhstan time zones
 # de jure UTC+5 and UTC+6 respectively.
 
 # From Stepan Golosunov (2016-03-27):
 # Review of the linked documents from http://adilet.zan.kz/
 # produced the following data for post-1991 Kazakhstan:
 #
 # 0. Act of the Cabinet of Ministers of the USSR
 # from 1991-02-04 No. 20
 # http://pravo.gov.ru/proxy/ips/?docbody=&nd=102010545
 # removed the extra hour ("decree time") on the territory of the USSR
 # starting with the last Sunday of March 1991.
 # It also allowed (but not mandated) Kazakh SSR, Kirghiz SSR, Tajik SSR,
 # Turkmen SSR and Uzbek SSR to not have "summer" time.
 #
 # The 1992-01-13 act also refers to the act of the Cabinet of Ministers
 # of the Kazakh SSR from 1991-03-20 No. 170 "About the act of the Cabinet
 # of Ministers of the USSR from 1991-02-04 No. 20" but I didn't found its
 # text.
 #
 # According to Izvestia newspaper No. 68 (23334) from 1991-03-20
 # -- page 6; available at http://libinfo.org/newsr/newsr2574.djvu via
 # http://libinfo.org/index.php?id=58564 -- on 1991-03-31 at 2:00 during
 # transition to "summer" time:
 # Republic of Georgia, Latvian SSR, Lithuanian SSR, SSR Moldova,
 # Estonian SSR; Komi ASSR; Kaliningrad oblast; Nenets autonomous okrug
 # were to move clocks 1 hour forward.
 # Kazakh SSR (excluding Uralsk oblast); Republic of Kyrgyzstan, Tajik
 # SSR; Andijan, Jizzakh, Namangan, Sirdarya, Tashkent, Fergana oblasts
 # of the Uzbek SSR were to move clocks 1 hour backwards.
 # Other territories were to not move clocks.
 # When the "summer" time would end on 1991-09-29, clocks were to be
 # moved 1 hour backwards on the territory of the USSR excluding
 # Kazakhstan, Kirghizia, Uzbekistan, Turkmenia, Tajikistan.
 #
 # Apparently there were last minute changes. Apparently Kazakh act No. 170
 # was one of such changes.
 #
 # https://ru.wikipedia.org/wiki/Декретное_время
 # claims that Sovetskaya Rossiya newspaper on 1991-03-29 published that
 # Nenets autonomous okrug, Komi and Kazakhstan (excluding Uralsk oblast)
 # were to not move clocks and Uralsk oblast was to move clocks
 # forward; on 1991-09-29 Kazakhstan was to move clocks backwards.
 # (Probably there were changes even after that publication. There is an
 # article claiming that Kaliningrad oblast decided on 1991-03-29 to not
 # move clocks.)
 #
 # This implies that on 1991-03-31 Asia/Oral remained on +04/+05 while
 # the rest of Kazakhstan switched from +06/+07 to +05/06 or from +05/06
 # to +04/+05. It's unclear how Qyzylorda oblast moved into the fifth
 # time belt. (By switching from +04/+05 to +05/+06 on 1991-09-29?) ...
 #
 # 1. Act of the Cabinet of Ministers of the Republic of Kazakhstan
 # from 1992-01-13 No. 28
 # http://adilet.zan.kz/rus/docs/P920000028_
 # (text includes modification from the 1996 act)
 # introduced new rules for calculation of time, mirroring Russian
 # 1992-01-08 act.  It specified that time would be calculated
 # according to time belts plus extra hour ("decree time"), moved clocks
 # on the whole territory of Kazakhstan 1 hour forward on 1992-01-19 at
 # 2:00, specified DST rules.  It acknowledged that Kazakhstan was
 # located in the fourth and the fifth time belts and specified the
 # border between them to be located east of Qostanay and Aktyubinsk
 # oblasts (notably including Turgai and Qyzylorda oblasts into the fifth
 # time belt).
 #
 # This means switch on 1992-01-19 at 2:00 from +04/+05 to +05/+06 for
 # Asia/Aqtau, Asia/Aqtobe, Asia/Oral, Atyraū and Qostanay oblasts; from
 # +05/+06 to +06/+07 for Asia/Almaty and Asia/Qyzylorda (and Arkalyk)....
 #
 # 2. Act of the Cabinet of Ministers of the Republic of Kazakhstan
 # from 1992-03-27 No. 284
 # http://adilet.zan.kz/rus/docs/P920000284_
 # cancels extra hour ("decree time") for Uralsk and Qyzylorda oblasts
 # since the last Sunday of March 1992, while keeping them in the fourth
 # and the fifth time belts respectively.
 #
 # 3. Order of the Prime Minister of the Republic of Kazakhstan
 # from 1994-09-23 No. 384
 # http://adilet.zan.kz/rus/docs/R940000384_
 # cancels the extra hour ("decree time") on the territory of Mangghystaū
 # oblast since the last Sunday of September 1994 (saying that time on
 # the territory would correspond to the third time belt as a
 # result)....
 #
 # 4. Act of the Government of the Republic of Kazakhstan
 # from 1996-05-08 No. 575
 # http://adilet.zan.kz/rus/docs/P960000575_
 # amends the 1992-01-13 act to end summer time in October instead
 # of September, mirroring identical Russian change from 1996-04-23 act.
 #
 # 5. Act of the Government of the Republic of Kazakhstan
 # from 1999-03-26 No. 305
 # http://adilet.zan.kz/rus/docs/P990000305_
 # cancels the extra hour ("decree time") for Atyraū oblast since the
 # last Sunday of March 1999 while retaining the oblast in the fourth
 # time belt.
 #
 # This means change from +05/+06 to +04/+05....
 #
 # 6. Act of the Government of the Republic of Kazakhstan
 # from 2000-11-23 No. 1749
 # http://adilet.zan.kz/rus/archive/docs/P000001749_/23.11.2000
 # replaces the previous five documents.
 #
 # The only changes I noticed are in definition of the border between the
 # fourth and the fifth time belts.  They account for changes in spelling
 # and administrative division (splitting of Turgai oblast in 1997
 # probably changed time in territories incorporated into Qostanay oblast
 # (including Arkalyk) from +06/+07 to +05/+06) and move Qyzylorda oblast
 # from being in the fifth time belt and not using decree time into the
 # fourth time belt (no change in practice).
 #
 # 7. Act of the Government of the Republic of Kazakhstan
 # from 2003-12-29 No. 1342
 # http://adilet.zan.kz/rus/docs/P030001342_
 # modified the 2000-11-23 act.  No relevant changes, apparently.
 #
 # 8. Act of the Government of the Republic of Kazakhstan
 # from 2004-07-20 No. 775
 # http://adilet.zan.kz/rus/archive/docs/P040000775_/20.07.2004
 # modified the 2000-11-23 act to move Qostanay and Qyzylorda oblasts into
 # the fifth time belt and add Aktobe oblast to the list of regions not
 # using extra hour ("decree time"), leaving Kazakhstan with only 2 time
 # zones (+04/+05 and +06/+07).  The changes were to be implemented
 # during DST transitions in 2004 and 2005 but the acts got radically
 # amended before implementation happened.
 #
 # 9. Act of the Government of the Republic of Kazakhstan
 # from 2004-09-15 No. 1059
 # http://adilet.zan.kz/rus/docs/P040001059_
 # modified the 2000-11-23 act to remove exceptions from the "decree time"
 # (leaving Kazakhstan in +05/+06 and +06/+07 zones), amended the
 # 2004-07-20 act to implement changes for Atyraū, West Kazakhstan,
 # Qostanay, Qyzylorda and Mangghystaū oblasts by not moving clocks
 # during the 2004 transition to "winter" time.
 #
 # This means transition from +04/+05 to +05/+06 for Atyraū oblast (no
 # zone currently), Asia/Oral, Asia/Aqtau and transition from +05/+06 to
 # +06/+07 for Qostanay oblast (Qostanay and Arkalyk, no zones currently)
 # and Asia/Qyzylorda on 2004-10-31 at 3:00....
 #
 # 10. Act of the Government of the Republic of Kazakhstan
 # from 2005-03-15 No. 231
 # http://adilet.zan.kz/rus/docs/P050000231_
 # removes DST provisions from the 2000-11-23 act, removes most of the
 # (already implemented) provisions from the 2004-07-20 and 2004-09-15
 # acts, comes into effect 10 days after official publication.
 # The only practical effect seems to be the abolition of the summer
 # time.
 #
 # Unamended version of the act of the Government of the Russian Federation
 # No. 23 from 1992-01-08 [See 'europe' file for details].
 # Kazakh 1992-01-13 act appears to provide the same rules and 1992-03-27
 # act was to be enacted on the last Sunday of March 1992.
 
 # From Stepan Golosunov (2016-11-08):
 # Turgai reorganization should affect only southern part of Qostanay
 # oblast.  Which should probably be separated into Asia/Arkalyk zone.
 # (There were also 1970, 1988 and 1990 Turgai oblast reorganizations
 # according to wikipedia.)
 #
 # [For Qostanay] http://www.ng.kz/gazeta/195/hranit/
 # suggests that clocks were to be moved 40 minutes backwards on
 # 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).
 
 # 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,
 # KZ-KAR, KZ-SEV, KZ-PAV, and KZ-YUZ.
 Zone	Asia/Almaty	5:07:48 -	LMT	1924 May  2 # or Alma-Ata
 			5:00	-	+05	1930 Jun 21
 			6:00 RussiaAsia +06/+07	1991 Mar 31  2:00s
 			5:00 RussiaAsia	+05/+06	1992 Jan 19  2:00s
 			6:00 RussiaAsia	+06/+07	2004 Oct 31  2:00s
 			6:00	-	+06
 # Qyzylorda (aka Kyzylorda, Kizilorda, Kzyl-Orda, etc.) (KZ-KZY)
 Zone	Asia/Qyzylorda	4:21:52 -	LMT	1924 May  2
 			4:00	-	+04	1930 Jun 21
 			5:00	-	+05	1981 Apr  1
 			5:00	1:00	+06	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 			4:00 RussiaAsia	+04/+05	1991 Sep 29  2:00s
 			5:00 RussiaAsia	+05/+06	1992 Jan 19  2:00s
 			6:00 RussiaAsia	+06/+07	1992 Mar 29  2:00s
 			5:00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
 			6:00	-	+06	2018 Dec 21  0:00
 			5:00	-	+05
 #
 # 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
 			4:00	-	+04	1930 Jun 21
 			5:00	-	+05	1981 Apr  1
 			5:00	1:00	+06	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 			5:00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
 			6:00	-	+06
 
 # Aqtöbe (aka Aktobe, formerly Aktyubinsk) (KZ-AKT)
 Zone	Asia/Aqtobe	3:48:40	-	LMT	1924 May  2
 			4:00	-	+04	1930 Jun 21
 			5:00	-	+05	1981 Apr  1
 			5:00	1:00	+06	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 			5:00 RussiaAsia	+05/+06	2004 Oct 31  2:00s
 			5:00	-	+05
 # Mangghystaū (KZ-MAN)
 # 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
 			4:00	-	+04	1930 Jun 21
 			5:00	-	+05	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 			5:00 RussiaAsia	+05/+06	1994 Sep 25  2:00s
 			4:00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 			5:00	-	+05
 # Atyraū (KZ-ATY) 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
 			3:00	-	+03	1930 Jun 21
 			5:00	-	+05	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00s
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 			5:00 RussiaAsia	+05/+06	1999 Mar 28  2:00s
 			4:00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 			5:00	-	+05
 # West Kazakhstan (KZ-ZAP)
 # 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
 			3:00	-	+03	1930 Jun 21
 			5:00	-	+05	1981 Apr  1
 			5:00	1:00	+06	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1989 Mar 26  2:00s
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00s
 			5:00 RussiaAsia	+05/+06	1992 Mar 29  2:00s
 			4:00 RussiaAsia	+04/+05	2004 Oct 31  2:00s
 			5:00	-	+05
 
 # Kyrgyzstan (Kirgizstan)
 # Transitions through 1991 are from Shanks & Pottenger.
 
 # From Paul Eggert (2005-08-15):
 # According to an article dated today in the Kyrgyzstan Development Gateway
 # http://eng.gateway.kg/cgi-bin/page.pl?id=1&story_name=doc9979.shtml
 # Kyrgyzstan is canceling the daylight saving time system.  I take the article
 # to mean that they will leave their clocks at 6 hours ahead of UTC.
 # From Malik Abdugaliev (2005-09-21):
 # Our government cancels daylight saving time 6th of August 2005.
 # From 2005-08-12 our GMT-offset is +6, w/o any daylight saving.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Kyrgyz	1992	1996	-	Apr	Sun>=7	0:00s	1:00	-
 Rule	Kyrgyz	1992	1996	-	Sep	lastSun	0:00	0	-
 Rule	Kyrgyz	1997	2005	-	Mar	lastSun	2:30	1:00	-
 Rule	Kyrgyz	1997	2004	-	Oct	lastSun	2:30	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Bishkek	4:58:24 -	LMT	1924 May  2
 			5:00	-	+05	1930 Jun 21
 			6:00 RussiaAsia +06/+07	1991 Mar 31  2:00s
 			5:00 RussiaAsia	+05/+06	1991 Aug 31  2:00
 			5:00	Kyrgyz	+05/+06	2005 Aug 12
 			6:00	-	+06
 
 ###############################################################################
 
 # Korea (North and South)
 
 # From Annie I. Bang (2006-07-10):
 # http://www.koreaherald.com/view.php?ud=200607100012
 # Korea ran a daylight saving program from 1949-61 but stopped it
 # during the 1950-53 Korean War.  The system was temporarily enforced
 # between 1987 and 1988 ...
 
 # From Sanghyuk Jung (2014-10-29):
 # https://mm.icann.org/pipermail/tz/2014-October/021830.html
 # According to the Korean Wikipedia
 # https://ko.wikipedia.org/wiki/한국_표준시
 # [oldid=12896437 2014-09-04 08:03 UTC]
 # DST in Republic of Korea was as follows....  And I checked old
 # newspapers in Korean, all articles correspond with data in Wikipedia.
 # For example, the article in 1948 (Korean Language) proved that DST
 # started at June 1 in that year.  For another example, the article in
 # 1988 said that DST started at 2:00 AM in that year.
 
 # From Phake Nick (2018-10-27):
 # 1. According to official announcement from Korean government, the DST end
 # date in South Korea should be
 # 1955-09-08 without specifying time
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0027977557
 # 1956-09-29 without specifying time
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0027978341
 # 1957-09-21 24 o'clock
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0027979690#3
 # 1958-09-20 24 o'clock
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0027981189
 # 1959-09-19 24 o'clock
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0027982974#2
 # 1960-09-17 24 o'clock
 # http://theme.archives.go.kr/next/common/viewEbook.do?singleData=N&archiveEventId=0028044104
 # ...
 # 2.... https://namu.wiki/w/대한민국%20표준시 ... [says]
 # when Korea was using GMT+8:30 as standard time, the international
 # aviation/marine/meteorological industry in the country refused to
 # follow and continued to use GMT+9:00 for interoperability.
 
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	ROK	1948	only	-	Jun	 1	 0:00	1:00	D
 Rule	ROK	1948	only	-	Sep	12	24:00	0	S
 Rule	ROK	1949	only	-	Apr	 3	 0:00	1:00	D
 Rule	ROK	1949	1951	-	Sep	Sat>=7	24:00	0	S
 Rule	ROK	1950	only	-	Apr	 1	 0:00	1:00	D
 Rule	ROK	1951	only	-	May	 6	 0:00	1:00	D
 Rule	ROK	1955	only	-	May	 5	 0:00	1:00	D
 Rule	ROK	1955	only	-	Sep	 8	24:00	0	S
 Rule	ROK	1956	only	-	May	20	 0:00	1:00	D
 Rule	ROK	1956	only	-	Sep	29	24:00	0	S
 Rule	ROK	1957	1960	-	May	Sun>=1	 0:00	1:00	D
 Rule	ROK	1957	1960	-	Sep	Sat>=17	24:00	0	S
 Rule	ROK	1987	1988	-	May	Sun>=8	 2:00	1:00	D
 Rule	ROK	1987	1988	-	Oct	Sun>=8	 3:00	0	S
 
 # From Paul Eggert (2016-08-23):
 # The Korean Wikipedia entry gives the following sources for UT offsets:
 #
 # 1908: Official Journal Article No. 3994 (decree No. 5)
 # 1912: Governor-General of Korea Official Gazette Issue No. 367
 #       (Announcement No. 338)
 # 1954: Presidential Decree No. 876 (1954-03-17)
 # 1961: Law No. 676 (1961-08-07)
 #
 # (Another source "1987: Law No. 3919 (1986-12-31)" was in the 2014-10-30
 # edition of the Korean Wikipedia entry.)
 #
 # I guessed that time zone abbreviations through 1945 followed the same
 # rules as discussed under Taiwan, with nominal switches from JST to KST
 # when the respective cities were taken over by the Allies after WWII.
 #
 # For Pyongyang, guess no changes from World War II until 2015, as we
 # have no information otherwise.
 
 # From Steffen Thorsen (2015-08-07):
 # According to many news sources, North Korea is going to change to
 # the 8:30 time zone on August 15, one example:
 # http://www.bbc.com/news/world-asia-33815049
 #
 # From Paul Eggert (2015-08-15):
 # Bells rang out midnight (00:00) Friday as part of the celebrations.  See:
 # Talmadge E. North Korea celebrates new time zone, 'Pyongyang Time'
 # http://news.yahoo.com/north-korea-celebrates-time-zone-pyongyang-time-164038128.html
 # There is no common English-language abbreviation for this time zone.
 # Use KST, as that's what we already use for 1954-1961 in ROK.
 
 # From Kang Seonghoon (2018-04-29):
 # North Korea will revert its time zone from UTC+8:30 (PYT; Pyongyang
 # Time) back to UTC+9 (KST; Korea Standard Time).
 #
 # From Seo Sanghyeon (2018-04-30):
 # Rodong Sinmun 2018-04-30 announced Pyongyang Time transition plan.
 # https://www.nknews.org/kcna/wp-content/uploads/sites/5/2018/04/rodong-2018-04-30.pdf
 # ... the transition date is 2018-05-05 ...  Citation should be Decree
 # No. 2232 of April 30, 2018, of the Presidium of the Supreme People's
 # Assembly, as published in Rodong Sinmun.
 # From Tim Parenti (2018-04-29):
 # It appears to be the front page story at the top in the right-most column.
 #
 # From Paul Eggert (2018-05-04):
 # The BBC reported that the transition was from 23:30 to 24:00 today.
 # https://www.bbc.com/news/world-asia-44010705
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Seoul	8:27:52	-	LMT	1908 Apr  1
 			8:30	-	KST	1912 Jan  1
 			9:00	-	JST	1945 Sep  8
 			9:00	ROK	K%sT	1954 Mar 21
 			8:30	ROK	K%sT	1961 Aug 10
 			9:00	ROK	K%sT
 Zone	Asia/Pyongyang	8:23:00 -	LMT	1908 Apr  1
 			8:30	-	KST	1912 Jan  1
 			9:00	-	JST	1945 Aug 24
 			9:00	-	KST	2015 Aug 15 00:00
 			8:30	-	KST	2018 May  4 23:30
 			9:00	-	KST
 
 ###############################################################################
 
 # Kuwait
 # See Asia/Riyadh.
 
 # Laos
 # See Asia/Bangkok.
 
 
 # Lebanon
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Lebanon	1920	only	-	Mar	28	0:00	1:00	S
 Rule	Lebanon	1920	only	-	Oct	25	0:00	0	-
 Rule	Lebanon	1921	only	-	Apr	3	0:00	1:00	S
 Rule	Lebanon	1921	only	-	Oct	3	0:00	0	-
 Rule	Lebanon	1922	only	-	Mar	26	0:00	1:00	S
 Rule	Lebanon	1922	only	-	Oct	8	0:00	0	-
 Rule	Lebanon	1923	only	-	Apr	22	0:00	1:00	S
 Rule	Lebanon	1923	only	-	Sep	16	0:00	0	-
 Rule	Lebanon	1957	1961	-	May	1	0:00	1:00	S
 Rule	Lebanon	1957	1961	-	Oct	1	0:00	0	-
 Rule	Lebanon	1972	only	-	Jun	22	0:00	1:00	S
 Rule	Lebanon	1972	1977	-	Oct	1	0:00	0	-
 Rule	Lebanon	1973	1977	-	May	1	0:00	1:00	S
 Rule	Lebanon	1978	only	-	Apr	30	0:00	1:00	S
 Rule	Lebanon	1978	only	-	Sep	30	0:00	0	-
 Rule	Lebanon	1984	1987	-	May	1	0:00	1:00	S
 Rule	Lebanon	1984	1991	-	Oct	16	0:00	0	-
 Rule	Lebanon	1988	only	-	Jun	1	0:00	1:00	S
 Rule	Lebanon	1989	only	-	May	10	0:00	1:00	S
 Rule	Lebanon	1990	1992	-	May	1	0:00	1:00	S
 Rule	Lebanon	1992	only	-	Oct	4	0:00	0	-
 Rule	Lebanon	1993	max	-	Mar	lastSun	0:00	1:00	S
 Rule	Lebanon	1993	1998	-	Sep	lastSun	0:00	0	-
 Rule	Lebanon	1999	max	-	Oct	lastSun	0:00	0	-
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Beirut	2:22:00 -	LMT	1880
 			2:00	Lebanon	EE%sT
 
 # Malaysia
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	NBorneo	1935	1941	-	Sep	14	0:00	0:20	-
 Rule	NBorneo	1935	1941	-	Dec	14	0:00	0	-
 #
 # For peninsular Malaysia see Asia/Singapore.
 #
 # Sabah & Sarawak
 # From Paul Eggert (2014-08-12):
 # The data entries here are mostly from Shanks & Pottenger, but the 1942, 1945
 # and 1982 transition dates are from Mok Ly Yng.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone Asia/Kuching	7:21:20	-	LMT	1926 Mar
 			7:30	-	+0730	1933
 			8:00 NBorneo  +08/+0820	1942 Feb 16
 			9:00	-	+09	1945 Sep 12
 			8:00	-	+08
 Link Asia/Kuching Asia/Brunei
 
 # Maldives
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Indian/Maldives	4:54:00 -	LMT	1880 # Malé
 			4:54:00	-	MMT	1960 # Malé Mean Time
 			5:00	-	+05
 Link Indian/Maldives Indian/Kerguelen
 
 # Mongolia
 
 # Shanks & Pottenger say that Mongolia has three time zones, but
 # The USNO (1995-12-21) and the CIA map Standard Time Zones of the World
 # (2005-03) both say that it has just one.
 
 # From Oscar van Vlijmen (1999-12-11):
 # General Information Mongolia
 #  (1999-09)
 # "Time: Mongolia has two time zones. Three westernmost provinces of
 # Bayan-Ölgii, Uvs, and Hovd are one hour earlier than the capital city, and
 # the rest of the country follows the Ulaanbaatar time, which is UTC/GMT plus
 # eight hours."
 
 # From Rives McDow (1999-12-13):
 # Mongolia discontinued the use of daylight savings time in 1999; 1998
 # being the last year it was implemented.  The dates of implementation I am
 # unsure of, but most probably it was similar to Russia, except for the time
 # of implementation may have been different....
 # Some maps in the past have indicated that there was an additional time
 # zone in the eastern part of Mongolia, including the provinces of Dornod,
 # Sükhbaatar, and possibly Khentii.
 
 # From Paul Eggert (1999-12-15):
 # Naming and spelling is tricky in Mongolia.
 # We'll use Hovd (also spelled Chovd and Khovd) to represent the west zone;
 # the capital of the Hovd province is sometimes called Hovd, sometimes Dund-Us,
 # and sometimes Jirgalanta (with variant spellings), but the name Hovd
 # is good enough for our purposes.
 
 # From Rives McDow (2001-05-13):
 # In addition to Mongolia starting daylight savings as reported earlier
 # (adopted DST on 2001-04-27 02:00 local time, ending 2001-09-28),
 # there are three time zones.
 #
 # Provinces [at 7:00]: Bayan-Ölgii, Uvs, Khovd, Zavkhan, Govi-Altai
 # Provinces [at 8:00]: Khövsgöl, Bulgan, Arkhangai, Khentii, Töv,
 #	Bayankhongor, Övörkhangai, Dundgovi, Dornogovi, Ömnögovi
 # Provinces [at 9:00]: Dornod, Sükhbaatar
 #
 # [The province of Selenge is omitted from the above lists.]
 
 # From Ganbold Ts., Ulaanbaatar (2004-04-17):
 # Daylight saving occurs at 02:00 local time last Saturday of March.
 # It will change back to normal at 02:00 local time last Saturday of
 # September.... As I remember this rule was changed in 2001.
 #
 # From Paul Eggert (2004-04-17):
 # For now, assume Rives McDow's informant got confused about Friday vs
 # Saturday, and that his 2001 dates should have 1 added to them.
 
 # From Paul Eggert (2005-07-26):
 # We have wildly conflicting information about Mongolia's time zones.
 # Bill Bonnet (2005-05-19) reports that the US Embassy in Ulaanbaatar says
 # there is only one time zone and that DST is observed, citing Microsoft
 # Windows XP as the source.  Risto Nykänen (2005-05-16) reports that
 # travelmongolia.org says there are two time zones (UT +07, +08) with no DST.
 # Oscar van Vlijmen (2005-05-20) reports that the Mongolian Embassy in
 # Washington, DC says there are two time zones, with DST observed.
 # He also found
 # http://ubpost.mongolnews.mn/index.php?subaction=showcomments&id=1111634894&archive=&start_from=&ucat=1&
 # which also says that there is DST, and which has a comment by "Toddius"
 # (2005-03-31 06:05 +0700) saying "Mongolia actually has 3.5 time zones.
 # The West (OLGII) is +7 GMT, most of the country is ULAT is +8 GMT
 # and some Eastern provinces are +9 GMT but Sükhbaatar Aimag is SUHK +8.5 GMT.
 # The SUKH timezone is new this year, it is one of the few things the
 # parliament passed during the tumultuous winter session."
 # For now, let's ignore this information, until we have more confirmation.
 
 # From Ganbold Ts. (2007-02-26):
 # Parliament of Mongolia has just changed the daylight-saving rule in February.
 # They decided not to adopt daylight-saving time....
 # http://www.mongolnews.mn/index.php?module=unuudur&sec=view&id=15742
 
 # From Deborah Goldsmith (2008-03-30):
 # We received a bug report claiming that the tz database UTC offset for
 # Asia/Choibalsan (GMT+09:00) is incorrect, and that it should be GMT
 # +08:00 instead. Different sources appear to disagree with the tz
 # database on this, e.g.:
 #
 # https://www.timeanddate.com/worldclock/city.html?n=1026
 # http://www.worldtimeserver.com/current_time_in_MN.aspx
 #
 # both say GMT+08:00.
 
 # From Steffen Thorsen (2008-03-31):
 # eznis airways, which operates several domestic flights, has a flight
 # schedule here:
 # http://www.eznis.com/Container.jsp?id=112
 # (click the English flag for English)
 #
 # There it appears that flights between Choibalsan and Ulaanbaatar arrive
 # about 1:35 - 1:50 hours later in local clock time, no matter the
 # direction, while Ulaanbaatar-Khovd takes 2 hours in the Eastern
 # direction and 3:35 back, which indicates that Ulaanbaatar and Khovd are
 # in different time zones (like we know about), while Choibalsan and
 # Ulaanbaatar are in the same time zone (correction needed).
 
 # From Arthur David Olson (2008-05-19):
 # Assume that Choibalsan is indeed offset by 8:00.
 # XXX--in the absence of better information, assume that transition
 # was at the start of 2008-03-31 (the day of Steffen Thorsen's report);
 # this is almost surely wrong.
 
 # From Ganbold Tsagaankhuu (2015-03-10):
 # It seems like yesterday Mongolian Government meeting has concluded to use
 # daylight saving time in Mongolia....  Starting at 2:00AM of last Saturday of
 # March 2015, daylight saving time starts.  And 00:00AM of last Saturday of
 # September daylight saving time ends.  Source:
 # http://zasag.mn/news/view/8969
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Mongol	1983	1984	-	Apr	1	0:00	1:00	-
 Rule	Mongol	1983	only	-	Oct	1	0:00	0	-
 # Shanks & Pottenger and IATA SSIM say 1990s switches occurred at 00:00,
 # but McDow says the 2001 switches occurred at 02:00.  Also, IATA SSIM
 # (1996-09) says 1996-10-25.  Go with Shanks & Pottenger through 1998.
 #
 # Shanks & Pottenger say that the Sept. 1984 through Sept. 1990 switches
 # in Choibalsan (more precisely, in Dornod and Sükhbaatar) took place
 # at 02:00 standard time, not at 00:00 local time as in the rest of
 # the country.  That would be odd, and possibly is a result of their
 # correction of 02:00 (in the previous edition) not being done correctly
 # in the latest edition; so ignore it for now.
 
 # From Ganbold Tsagaankhuu (2017-02-09):
 # Mongolian Government meeting has concluded today to cancel daylight
 # saving time adoption in Mongolia.  Source: http://zasag.mn/news/view/16192
 
 Rule	Mongol	1985	1998	-	Mar	lastSun	0:00	1:00	-
 Rule	Mongol	1984	1998	-	Sep	lastSun	0:00	0	-
 # IATA SSIM (1999-09) says Mongolia no longer observes DST.
 Rule	Mongol	2001	only	-	Apr	lastSat	2:00	1:00	-
 Rule	Mongol	2001	2006	-	Sep	lastSat	2:00	0	-
 Rule	Mongol	2002	2006	-	Mar	lastSat	2:00	1:00	-
 Rule	Mongol	2015	2016	-	Mar	lastSat	2:00	1:00	-
 Rule	Mongol	2015	2016	-	Sep	lastSat	0:00	0	-
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 # Hovd, a.k.a. Chovd, Dund-Us, Dzhargalant, Khovd, Jirgalanta
 Zone	Asia/Hovd	6:06:36 -	LMT	1905 Aug
 			6:00	-	+06	1978
 			7:00	Mongol	+07/+08
 # Ulaanbaatar, a.k.a. Ulan Bataar, Ulan Bator, Urga
 Zone	Asia/Ulaanbaatar 7:07:32 -	LMT	1905 Aug
 			7:00	-	+07	1978
 			8:00	Mongol	+08/+09
 # Choibalsan, a.k.a. Bajan Tümen, Bajan Tumen, Chojbalsan,
 # Choybalsan, Sanbejse, Tchoibalsan
 Zone	Asia/Choibalsan	7:38:00 -	LMT	1905 Aug
 			7:00	-	+07	1978
 			8:00	-	+08	1983 Apr
 			9:00	Mongol	+09/+10	2008 Mar 31
 			8:00	Mongol	+08/+09
 
 # Nepal
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Kathmandu	5:41:16 -	LMT	1920
 			5:30	-	+0530	1986
 			5:45	-	+0545
 
 # Oman
 # See Asia/Dubai.
 
 # Pakistan
 
 # From Rives McDow (2002-03-13):
 # I have been advised that Pakistan has decided to adopt dst on a
 # TRIAL basis for one year, starting 00:01 local time on April 7, 2002
 # and ending at 00:01 local time October 6, 2002.  This is what I was
 # told, but I believe that the actual time of change may be 00:00; the
 # 00:01 was to make it clear which day it was on.
 
 # From Paul Eggert (2002-03-15):
 # Jesper Nørgaard found this URL:
 # http://www.pak.gov.pk/public/news/app/app06_dec.htm
 # (dated 2001-12-06) which says that the Cabinet adopted a scheme "to
 # advance the clocks by one hour on the night between the first
 # Saturday and Sunday of April and revert to the original position on
 # 15th October each year".  This agrees with McDow's 04-07 at 00:00,
 # but disagrees about the October transition, and makes it sound like
 # it's not on a trial basis.  Also, the "between the first Saturday
 # and Sunday of April" phrase, if taken literally, means that the
 # transition takes place at 00:00 on the first Sunday on or after 04-02.
 
 # From Paul Eggert (2003-02-09):
 # DAWN  reported on 2002-10-05
 # that 2002 DST ended that day at midnight.  Go with McDow for now.
 
 # From Steffen Thorsen (2003-03-14):
 # According to http://www.dawn.com/2003/03/07/top15.htm
 # there will be no DST in Pakistan this year:
 #
 # ISLAMABAD, March 6: Information and Media Development Minister Sheikh
 # Rashid Ahmed on Thursday said the cabinet had reversed a previous
 # decision to advance clocks by one hour in summer and put them back by
 # one hour in winter with the aim of saving light hours and energy.
 #
 # The minister told a news conference that the experiment had rather
 # shown 8 per cent higher consumption of electricity.
 
 # From Alex Krivenyshev (2008-05-15):
 #
 # Here is an article that Pakistan plan to introduce Daylight Saving Time
 # on June 1, 2008 for 3 months.
 #
 # "... The federal cabinet on Wednesday announced a new conservation plan to
 # help reduce load shedding by approving the closure of commercial centres at
 # 9pm and moving clocks forward by one hour for the next three months. ...."
 #
 # http://www.worldtimezone.com/dst_news/dst_news_pakistan01.html
 # http://www.dailytimes.com.pk/default.asp?page=2008%5C05%5C15%5Cstory_15-5-2008_pg1_4
 
 # From Arthur David Olson (2008-05-19):
 # XXX--midnight transitions is a guess; 2008 only is a guess.
 
 # From Alexander Krivenyshev (2008-08-28):
 # Pakistan government has decided to keep the watches one-hour advanced
 # for another 2 months - plan to return to Standard Time on October 31
 # instead of August 31.
 #
 # http://www.worldtimezone.com/dst_news/dst_news_pakistan02.html
 # http://dailymailnews.com/200808/28/news/dmbrn03.html
 
 # From Alexander Krivenyshev (2009-04-08):
 # Based on previous media reports that "... proposed plan to
 # advance clocks by one hour from May 1 will cause disturbance
 # to the working schedules rather than bringing discipline in
 # official working."
 # http://www.thenews.com.pk/daily_detail.asp?id=171280
 #
 # recent news that instead of May 2009 - Pakistan plan to
 # introduce DST from April 15, 2009
 #
 # FYI: Associated Press Of Pakistan
 # April 08, 2009
 # Cabinet okays proposal to advance clocks by one hour from April 15
 # http://www.app.com.pk/en_/index.php?option=com_content&task=view&id=73043&Itemid=1
 # http://www.worldtimezone.com/dst_news/dst_news_pakistan05.html
 #
 # ....
 # The Federal Cabinet on Wednesday approved the proposal to
 # advance clocks in the country by one hour from April 15 to
 # conserve energy"
 
 # From Steffen Thorsen (2009-09-17):
 # "The News International," Pakistan reports that: "The Federal
 # Government has decided to restore the previous time by moving the
 # clocks backward by one hour from October 1. A formal announcement to
 # this effect will be made after the Prime Minister grants approval in
 # this regard."
 # http://www.thenews.com.pk/updates.asp?id=87168
 
 # From Alexander Krivenyshev (2009-09-28):
 # According to Associated Press Of Pakistan, it is confirmed that
 # Pakistan clocks across the country would be turned back by an hour from
 # October 1, 2009.
 #
 # "Clocks to go back one hour from 1 Oct"
 # http://www.app.com.pk/en_/index.php?option=com_content&task=view&id=86715&Itemid=2
 # http://www.worldtimezone.com/dst_news/dst_news_pakistan07.htm
 #
 # From Steffen Thorsen (2009-09-29):
 # Now they seem to have changed their mind, November 1 is the new date:
 # http://www.thenews.com.pk/top_story_detail.asp?Id=24742
 # "The country's clocks will be reversed by one hour on November 1.
 # Officials of Federal Ministry for Interior told this to Geo News on
 # Monday."
 #
 # And more importantly, it seems that these dates will be kept every year:
 # "It has now been decided that clocks will be wound forward by one hour
 # on April 15 and reversed by an hour on November 1 every year without
 # obtaining prior approval, the officials added."
 #
 # We have confirmed this year's end date with both with the Ministry of
 # Water and Power and the Pakistan Electric Power Company:
 # https://www.timeanddate.com/news/time/pakistan-ends-dst09.html
 
 # From Christoph Göhre (2009-10-01):
 # [T]he German Consulate General in Karachi reported me today that Pakistan
 # will go back to standard time on 1st of November.
 
 # From Steffen Thorsen (2010-03-26):
 # Steffen Thorsen wrote:
 # > On Thursday (2010-03-25) it was announced that DST would start in
 # > Pakistan on 2010-04-01.
 # >
 # > Then today, the president said that they might have to revert the
 # > decision if it is not supported by the parliament. So at the time
 # > being, it seems unclear if DST will be actually observed or not - but
 # > April 1 could be a more likely date than April 15.
 # Now, it seems that the decision to not observe DST in final:
 #
 # "Govt Withdraws Plan To Advance Clocks"
 # http://www.apakistannews.com/govt-withdraws-plan-to-advance-clocks-172041
 #
 # "People laud PM's announcement to end DST"
 # http://www.app.com.pk/en_/index.php?option=com_content&task=view&id=99374&Itemid=2
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule Pakistan	2002	only	-	Apr	Sun>=2	0:00	1:00	S
 Rule Pakistan	2002	only	-	Oct	Sun>=2	0:00	0	-
 Rule Pakistan	2008	only	-	Jun	1	0:00	1:00	S
 Rule Pakistan	2008	2009	-	Nov	1	0:00	0	-
 Rule Pakistan	2009	only	-	Apr	15	0:00	1:00	S
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Karachi	4:28:12 -	LMT	1907
 			5:30	-	+0530	1942 Sep
 			5:30	1:00	+0630	1945 Oct 15
 			5:30	-	+0530	1951 Sep 30
 			5:00	-	+05	1971 Mar 26
 			5:00 Pakistan	PK%sT	# Pakistan Time
 
 # Palestine
 
 # From Amos Shapir (1998-02-15):
 #
 # From 1917 until 1948-05-15, all of Palestine, including the parts now
 # known as the Gaza Strip and the West Bank, was under British rule.
 # Therefore the rules given for Israel for that period, apply there too...
 #
 # The Gaza Strip was under Egyptian rule between 1948-05-15 until 1967-06-05
 # (except a short occupation by Israel from 1956-11 till 1957-03, but no
 # time zone was affected then).  It was never formally annexed to Egypt,
 # though.
 #
 # The rest of Palestine was under Jordanian rule at that time, formally
 # annexed in 1950 as the West Bank (and the word "Trans" was dropped from
 # the country's previous name of "the Hashemite Kingdom of the
 # Trans-Jordan").  So the rules for Jordan for that time apply.  Major
 # towns in that area are Nablus (Shchem), El-Halil (Hebron), Ramallah, and
 # East Jerusalem.
 #
 # Both areas were occupied by Israel in June 1967, but not annexed (except
 # for East Jerusalem).  They were on Israel time since then; there might
 # have been a Military Governor's order about time zones, but I'm not aware
 # of any (such orders may have been issued semi-annually whenever summer
 # time was in effect, but maybe the legal aspect of time was just neglected).
 #
 # The Palestinian Authority was established in 1993, and got hold of most
 # towns in the West Bank and Gaza by 1995.  I know that in order to
 # demonstrate...independence, they have been switching to
 # summer time and back on a different schedule than Israel's, but I don't
 # know when this was started, or what algorithm is used (most likely the
 # Jordanian one).
 #
 # To summarize, the table should probably look something like that:
 #
 # Area \ when | 1918-1947 | 1948-1967 | 1967-1995 | 1996-
 # ------------+-----------+-----------+-----------+-----------
 # Israel      | Zion      | Zion      | Zion      | Zion
 # West bank   | Zion      | Jordan    | Zion      | Jordan
 # Gaza        | Zion      | Egypt     | Zion      | Jordan
 #
 # I guess more info may be available from the PA's web page (if/when they
 # have one).
 
 # From Paul Eggert (2006-03-22):
 # Shanks & Pottenger write that Gaza did not observe DST until 1957, but go
 # with Shapir and assume that it observed DST from 1940 through 1947,
 # and that it used Jordanian rules starting in 1996.
 # We don't yet need a separate entry for the West Bank, since
 # the only differences between it and Gaza that we know about
 # occurred before our cutoff date of 1970.
 # However, as we get more information, we may need to add entries
 # for parts of the West Bank as they transitioned from Israel's rules
 # to Palestine's rules.
 
 # From IINS News Service - Israel - 1998-03-23 10:38:07 Israel time,
 # forwarded by Ephraim Silverberg:
 #
 # Despite the fact that Israel changed over to daylight savings time
 # last week, the PLO Authority (PA) has decided not to turn its clocks
 # one-hour forward at this time.  As a sign of independence from Israeli rule,
 # the PA has decided to implement DST in April.
 
 # From Paul Eggert (1999-09-20):
 # Daoud Kuttab writes in Holiday havoc
 # http://www.jpost.com/com/Archive/22.Apr.1999/Opinion/Article-2.html
 # (Jerusalem Post, 1999-04-22) that
 # the Palestinian National Authority changed to DST on 1999-04-15.
 # I vaguely recall that they switch back in October (sorry, forgot the source).
 # For now, let's assume that the spring switch was at 24:00,
 # and that they switch at 0:00 on the 3rd Fridays of April and October.
 
 # From Paul Eggert (2005-11-22):
 # Starting 2004 transitions are from Steffen Thorsen's web site timeanddate.com.
 
 # From Steffen Thorsen (2005-11-23):
 # A user from Gaza reported that Gaza made the change early because of
 # the Ramadan.  Next year Ramadan will be even earlier, so I think
 # there is a good chance next year's end date will be around two weeks
 # earlier - the same goes for Jordan.
 
 # From Steffen Thorsen (2006-08-17):
 # I was informed by a user in Bethlehem that in Bethlehem it started the
 # same day as Israel, and after checking with other users in the area, I
 # was informed that they started DST one day after Israel.  I was not
 # able to find any authoritative sources at the time, nor details if
 # Gaza changed as well, but presumed Gaza to follow the same rules as
 # the West Bank.
 
 # From Steffen Thorsen (2006-09-26):
 # according to the Palestine News Network (2006-09-19):
 # http://english.pnn.ps/index.php?option=com_content&task=view&id=596&Itemid=5
 # > The Council of Ministers announced that this year its winter schedule
 # > will begin early, as of midnight Thursday.  It is also time to turn
 # > back the clocks for winter.  Friday will begin an hour late this week.
 # I guess it is likely that next year's date will be moved as well,
 # because of the Ramadan.
 
 # From Jesper Nørgaard Welen (2007-09-18):
 # According to Steffen Thorsen's web site the Gaza Strip and the rest of the
 # Palestinian territories left DST early on 13.th. of September at 2:00.
 
 # From Paul Eggert (2007-09-20):
 # My understanding is that Gaza and the West Bank disagree even over when
 # the weekend is (Thursday+Friday versus Friday+Saturday), so I'd be a bit
 # surprised if they agreed about DST.  But for now, assume they agree.
 # For lack of better information, predict that future changes will be
 # the 2nd Thursday of September at 02:00.
 
 # From Alexander Krivenyshev (2008-08-28):
 # Here is an article, that Mideast running on different clocks at Ramadan.
 #
 # Gaza Strip (as Egypt) ended DST at midnight Thursday (Aug 28, 2008), while
 # the West Bank will end Daylight Saving Time at midnight Sunday (Aug 31, 2008).
 #
 # http://www.guardian.co.uk/world/feedarticle/7759001
 # http://www.abcnews.go.com/International/wireStory?id=5676087
 # http://www.worldtimezone.com/dst_news/dst_news_gazastrip01.html
 
 # From Alexander Krivenyshev (2009-03-26):
 # According to the Palestine News Network (arabic.pnn.ps), Palestinian
 # government decided to start Daylight Time on Thursday night March
 # 26 and continue until the night of 27 September 2009.
 #
 # (in Arabic)
 # http://arabic.pnn.ps/index.php?option=com_content&task=view&id=50850
 #
 # (English translation)
 # http://www.worldtimezone.com/dst_news/dst_news_westbank01.html
 
 # From Steffen Thorsen (2009-08-31):
 # Palestine's Council of Ministers announced that they will revert back to
 # winter time on Friday, 2009-09-04.
 #
 # One news source:
 # http://www.safa.ps/ara/?action=showdetail&seid=4158
 # (Palestinian press agency, Arabic),
 # Google translate: "Decided that the Palestinian government in Ramallah
 # headed by Salam Fayyad, the start of work in time for the winter of
 # 2009, starting on Friday approved the fourth delay Sept. clock sixty
 # minutes per hour as of Friday morning."
 #
 # We are not sure if Gaza will do the same, last year they had a different
 # end date, we will keep this page updated:
 # https://www.timeanddate.com/news/time/westbank-gaza-dst-2009.html
 
 # From Alexander Krivenyshev (2009-09-02):
 # Seems that Gaza Strip will go back to Winter Time same date as West Bank.
 #
 # According to Palestinian Ministry Of Interior, West Bank and Gaza Strip plan
 # to change time back to Standard time on September 4, 2009.
 #
 # "Winter time unite the West Bank and Gaza"
 # (from Palestinian National Authority):
 # http://www.moi.gov.ps/en/?page=633167343250594025&nid=11505
 # http://www.worldtimezone.com/dst_news/dst_news_gazastrip02.html
 
 # From Alexander Krivenyshev (2010-03-19):
 # According to Voice of Palestine DST will last for 191 days, from March
 # 26, 2010 till "the last Sunday before the tenth day of Tishri
 # (October), each year" (October 03, 2010?)
 #
 # http://palvoice.org/forums/showthread.php?t=245697
 # (in Arabic)
 # http://www.worldtimezone.com/dst_news/dst_news_westbank03.html
 
 # From Steffen Thorsen (2010-03-24):
 # ...Ma'an News Agency reports that Hamas cabinet has decided it will
 # start one day later, at 12:01am. Not sure if they really mean 12:01am or
 # noon though:
 #
 # http://www.maannews.net/eng/ViewDetails.aspx?ID=271178
 # (Ma'an News Agency)
 # "At 12:01am Friday, clocks in Israel and the West Bank will change to
 # 1:01am, while Gaza clocks will change at 12:01am Saturday morning."
 
 # From Steffen Thorsen (2010-08-11):
 # According to several sources, including
 # http://www.maannews.net/eng/ViewDetails.aspx?ID=306795
 # the clocks were set back one hour at 2010-08-11 00:00:00 local time in
 # Gaza and the West Bank.
 # Some more background info:
 # https://www.timeanddate.com/news/time/westbank-gaza-end-dst-2010.html
 
 # From Steffen Thorsen (2011-08-26):
 # Gaza and the West Bank did go back to standard time in the beginning of
 # August, and will now enter daylight saving time again on 2011-08-30
 # 00:00 (so two periods of DST in 2011). The pause was because of
 # Ramadan.
 #
 # http://www.maannews.net/eng/ViewDetails.aspx?ID=416217
 # Additional info:
 # https://www.timeanddate.com/news/time/palestine-dst-2011.html
 
 # From Alexander Krivenyshev (2011-08-27):
 # According to the article in The Jerusalem Post:
 # "...Earlier this month, the Palestinian government in the West Bank decided to
 # move to standard time for 30 days, during Ramadan. The Palestinians in the
 # Gaza Strip accepted the change and also moved their clocks one hour back.
 # The Hamas government said on Saturday that it won't observe summertime after
 # the Muslim feast of Id al-Fitr, which begins on Tuesday..."
 # ...
 # https://www.jpost.com/MiddleEast/Article.aspx?id=235650
 # http://www.worldtimezone.com/dst_news/dst_news_gazastrip05.html
 # The rules for Egypt are stolen from the 'africa' file.
 
 # From Steffen Thorsen (2011-09-30):
 # West Bank did end Daylight Saving Time this morning/midnight (2011-09-30
 # 00:00).
 # So West Bank and Gaza now have the same time again.
 #
 # Many sources, including:
 # http://www.maannews.net/eng/ViewDetails.aspx?ID=424808
 
 # From Steffen Thorsen (2012-03-26):
 # Palestinian news sources tell that both Gaza and West Bank will start DST
 # on Friday (Thursday midnight, 2012-03-29 24:00).
 # Some of many sources in Arabic:
 # http://www.samanews.com/index.php?act=Show&id=122638
 #
 # http://safa.ps/details/news/74352/%D8%A8%D8%AF%D8%A1-%D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA-%D8%A7%D9%84%D8%B5%D9%8A%D9%81%D9%8A-%D8%A8%D8%A7%D9%84%D8%B6%D9%81%D8%A9-%D9%88%D8%BA%D8%B2%D8%A9-%D9%84%D9%8A%D9%84%D8%A9-%D8%A7%D9%84%D8%AC%D9%85%D8%B9%D8%A9.html
 #
 # Our brief summary:
 # https://www.timeanddate.com/news/time/gaza-west-bank-dst-2012.html
 
 # From Steffen Thorsen (2013-03-26):
 # The following news sources tells that Palestine will "start daylight saving
 # time from midnight on Friday, March 29, 2013" (translated).
 # [These are in Arabic and are for Gaza and for Ramallah, respectively.]
 # http://www.samanews.com/index.php?act=Show&id=154120
 # http://safa.ps/details/news/99844/%D8%B1%D8%A7%D9%85-%D8%A7%D9%84%D9%84%D9%87-%D8%A8%D8%AF%D8%A1-%D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA-%D8%A7%D9%84%D8%B5%D9%8A%D9%81%D9%8A-29-%D8%A7%D9%84%D8%AC%D8%A7%D8%B1%D9%8A.html
 
 # From Steffen Thorsen (2013-09-24):
 # The Gaza and West Bank are ending DST Thursday at midnight
 # (2013-09-27 00:00:00) (one hour earlier than last year...).
 # This source in English, says "that winter time will go into effect
 # at midnight on Thursday in the West Bank and Gaza Strip":
 # http://english.wafa.ps/index.php?action=detail&id=23246
 # official source...:
 # http://www.palestinecabinet.gov.ps/ar/Views/ViewDetails.aspx?pid=1252
 
 # From Steffen Thorsen (2015-03-03):
 # Sources such as http://www.alquds.com/news/article/view/id/548257
 # and https://www.raya.ps/ar/news/890705.html say Palestine areas will
 # start DST on 2015-03-28 00:00 which is one day later than expected.
 #
 # From Paul Eggert (2015-03-03):
 # https://www.timeanddate.com/time/change/west-bank/ramallah?year=2014
 # says that the fall 2014 transition was Oct 23 at 24:00.
 
 # From Hannah Kreitem (2016-03-09):
 # http://www.palestinecabinet.gov.ps/WebSite/ar/ViewDetails?ID=31728
 # [Google translation]: "The Council also decided to start daylight
 # saving in Palestine as of one o'clock on Saturday morning,
 # 2016-03-26, to provide the clock 60 minutes ahead."
 
 # From Sharef Mustafa (2016-10-19):
 # [T]he Palestinian cabinet decision (Mar 8th 2016) published on
 # http://www.palestinecabinet.gov.ps/WebSite/Upload/Decree/GOV_17/16032016134830.pdf
 # states that summer time will end on Oct 29th at 01:00.
 
 # From Sharef Mustafa (2018-03-16):
 # Palestine summer time will start on Mar 24th 2018 ...
 # http://www.palestinecabinet.gov.ps/Website/AR/NDecrees/ViewFile.ashx?ID=e7a42ab7-ee23-435a-b9c8-a4f7e81f3817
 
 # From Even Scharning (2019-03-23):
 # http://pnn.ps/news/401130
 # http://palweather.ps/ar/node/50136.html
 #
 # From Sharif Mustafa (2019-03-26):
 # The Palestinian cabinet announced today that the switch to DST will
 # be on Fri Mar 29th 2019 by advancing the clock by 60 minutes.
 # http://palestinecabinet.gov.ps/Website/AR/NDecrees/ViewFile.ashx?ID=e54e9ea1-50ee-4137-84df-0d6c78da259b
 #
 # From Even Scharning (2019-04-10):
 # Our source in Palestine said it happened Friday 29 at 00:00 local time....
 
 # From Sharef Mustafa (2019-10-18):
 # Palestine summer time will end on midnight Oct 26th 2019 ...
 #
 # From Steffen Thorsen (2020-10-20):
 # Some sources such as these say, and display on clocks, that DST ended at
 # midnight last year...
 # https://www.amad.ps/ar/post/320006
 #
 # From Tim Parenti (2020-10-20):
 # The report of the Palestinian Cabinet meeting of 2019-10-14 confirms
 # a decision on (translated): "The start of the winter time in Palestine, by
 # delaying the clock by sixty minutes, starting from midnight on Friday /
 # Saturday corresponding to 26/10/2019."
 # http://www.palestinecabinet.gov.ps/portal/meeting/details/43948
 
 # From Sharef Mustafa (2020-10-20):
 # As per the palestinian cabinet announcement yesterday , the day light saving
 # shall [end] on Oct 24th 2020 at 01:00AM by delaying the clock by 60 minutes.
 # http://www.palestinecabinet.gov.ps/portal/Meeting/Details/51584
 
 # From Pierre Cashon (2020-10-20):
 # The summer time this year started on March 28 at 00:00.
 # https://wafa.ps/ar_page.aspx?id=GveQNZa872839351758aGveQNZ
 # http://www.palestinecabinet.gov.ps/portal/meeting/details/50284
 # The winter time in 2015 started on October 23 at 01:00.
 # https://wafa.ps/ar_page.aspx?id=CgpCdYa670694628582aCgpCdY
 # http://www.palestinecabinet.gov.ps/portal/meeting/details/27583
 #
 # From Paul Eggert (2019-04-10):
 # For now, guess spring-ahead transitions are at 00:00 on the Saturday
 # preceding March's last Sunday (i.e., Sat>=24).
 
 # From P Chan (2021-10-18):
 # http://wafa.ps/Pages/Details/34701
 # Palestine winter time will start from midnight 2021-10-29 (Thursday-Friday).
 #
 # From Heba Hemad, Palestine Ministry of Telecom & IT (2021-10-20):
 # ... winter time will begin in Palestine from Friday 10-29, 01:00 AM
 # by 60 minutes backwards.
 #
 # From Tim Parenti (2021-10-25), per Paul Eggert (2021-10-24):
 # Guess future fall transitions at 01:00 on the Friday preceding October's
 # last Sunday (i.e., Fri>=23), as this is more consistent with recent practice.
 
 # From Heba Hamad (2022-03-10):
 # summer time will begin in Palestine from Sunday 03-27-2022, 00:00 AM.
 
 # 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	-
 Rule EgyptAsia	1958	only	-	May	 1	0:00	1:00	S
 Rule EgyptAsia	1959	1967	-	May	 1	1:00	1:00	S
 Rule EgyptAsia	1959	1965	-	Sep	30	3:00	0	-
 Rule EgyptAsia	1966	only	-	Oct	 1	3:00	0	-
 
 Rule Palestine	1999	2005	-	Apr	Fri>=15	0:00	1:00	S
 Rule Palestine	1999	2003	-	Oct	Fri>=15	0:00	0	-
 Rule Palestine	2004	only	-	Oct	 1	1:00	0	-
 Rule Palestine	2005	only	-	Oct	 4	2:00	0	-
 Rule Palestine	2006	2007	-	Apr	 1	0:00	1:00	S
 Rule Palestine	2006	only	-	Sep	22	0:00	0	-
 Rule Palestine	2007	only	-	Sep	13	2:00	0	-
 Rule Palestine	2008	2009	-	Mar	lastFri	0:00	1:00	S
 Rule Palestine	2008	only	-	Sep	 1	0:00	0	-
 Rule Palestine	2009	only	-	Sep	 4	1:00	0	-
 Rule Palestine	2010	only	-	Mar	26	0:00	1:00	S
 Rule Palestine	2010	only	-	Aug	11	0:00	0	-
 Rule Palestine	2011	only	-	Apr	 1	0:01	1:00	S
 Rule Palestine	2011	only	-	Aug	 1	0:00	0	-
 Rule Palestine	2011	only	-	Aug	30	0:00	1:00	S
 Rule Palestine	2011	only	-	Sep	30	0:00	0	-
 Rule Palestine	2012	2014	-	Mar	lastThu	24:00	1:00	S
 Rule Palestine	2012	only	-	Sep	21	1:00	0	-
 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>=24	1:00	1:00	S
 Rule Palestine	2016	2018	-	Oct	Sat>=24	1:00	0	-
 Rule Palestine	2019	only	-	Mar	29	0:00	1:00	S
 Rule Palestine	2019	only	-	Oct	Sat>=24	0:00	0	-
 Rule Palestine	2020	2021	-	Mar	Sat>=24	0:00	1:00	S
 Rule Palestine	2020	only	-	Oct	24	1:00	0	-
 Rule Palestine	2021	max	-	Oct	Fri>=23	1:00	0	-
 Rule Palestine	2022	max	-	Mar	Sun>=25	0:00	1:00	S
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Gaza	2:17:52	-	LMT	1900 Oct
 			2:00	Zion	EET/EEST 1948 May 15
 			2:00 EgyptAsia	EE%sT	1967 Jun  5
 			2:00	Zion	I%sT	1996
 			2:00	Jordan	EE%sT	1999
 			2:00 Palestine	EE%sT	2008 Aug 29  0:00
 			2:00	-	EET	2008 Sep
 			2:00 Palestine	EE%sT	2010
 			2:00	-	EET	2010 Mar 27  0:01
 			2:00 Palestine	EE%sT	2011 Aug  1
 			2:00	-	EET	2012
 			2:00 Palestine	EE%sT
 
 Zone	Asia/Hebron	2:20:23	-	LMT	1900 Oct
 			2:00	Zion	EET/EEST 1948 May 15
 			2:00 EgyptAsia	EE%sT	1967 Jun  5
 			2:00	Zion	I%sT	1996
 			2:00	Jordan	EE%sT	1999
 			2:00 Palestine	EE%sT
 
 # Paracel Is
 # no information
 
 # Philippines
 
 # From Paul Eggert (2018-11-18):
 # 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
 # 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.
 # Philippine Star 2014-08-05
 # http://www.philstar.com/headlines/2014/08/05/1354152/pnoy-urged-declare-use-daylight-saving-time
 
 # From Paul Goyette (2018-06-15):
 # In the Philippines, there is a national law, Republic Act No. 10535
 # which declares the official time here as "Philippine Standard Time".
 # The act [1] even specifies use of PST as the abbreviation, although
 # the FAQ provided by PAGASA [2] uses the "acronym PhST to distinguish
 # it from the Pacific Standard Time (PST)."
 # [1] http://www.officialgazette.gov.ph/2013/05/15/republic-act-no-10535/
 # [2] https://www1.pagasa.dost.gov.ph/index.php/astronomy/philippine-standard-time#republic-act-10535
 #
 # From Paul Eggert (2018-06-19):
 # I surveyed recent news reports, and my impression is that "PST" is
 # more popular among reliable English-language news sources.  This is
 # not just a measure of Google hit counts: it's also the sizes and
 # influence of the sources.  There is no current abbreviation for DST,
 # so use "PDT", the usual American style.
 
 # From P Chan (2021-05-10):
 # Here's a fairly comprehensive article in Japanese:
 # https://wiki.suikawiki.org/n/Philippine%20Time
 # From Paul Eggert (2021-05-10):
 # The info in the Japanese table has not been absorbed (yet) below.
 
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Phil	1936	only	-	Nov	1	0:00	1:00	D
 Rule	Phil	1937	only	-	Feb	1	0:00	0	S
 Rule	Phil	1954	only	-	Apr	12	0:00	1:00	D
 Rule	Phil	1954	only	-	Jul	1	0:00	0	S
 Rule	Phil	1978	only	-	Mar	22	0:00	1:00	D
 Rule	Phil	1978	only	-	Sep	21	0:00	0	S
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Manila	-15:56:00 -	LMT	1844 Dec 31
 			8:04:00 -	LMT	1899 May 11
 			8:00	Phil	P%sT	1942 May
 			9:00	-	JST	1944 Nov
 			8:00	Phil	P%sT
 
 # Qatar
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Qatar	3:26:08 -	LMT	1920     # Al Dawhah / Doha
 			4:00	-	+04	1972 Jun
 			3:00	-	+03
 Link Asia/Qatar Asia/Bahrain
 
 # Saudi Arabia
 #
 # From Paul Eggert (2018-08-29):
 # Time in Saudi Arabia and other countries in the Arabian peninsula was not
 # standardized until 1968 or so; we don't know exactly when, and possibly it
 # has never been made official.  Richard P Hunt, in "Islam city yielding to
 # modern times", New York Times (1961-04-09), p 20, wrote that only airlines
 # observed standard time, and that people in Jeddah mostly observed quasi-solar
 # time, doing so by setting their watches at sunrise to 6 o'clock (or to 12
 # o'clock for "Arab" time).
 #
 # Timekeeping differed depending on who you were and which part of Saudi
 # Arabia you were in.  In 1969, Elias Antar wrote that although a common
 # practice had been to set one's watch to 12:00 (i.e., midnight) at sunset -
 # which meant that the time on one side of a mountain could differ greatly from
 # the time on the other side - many foreigners set their watches to 6pm
 # instead, while airlines instead used UTC +03 (except in Dhahran, where they
 # used UTC +04), Aramco used UTC +03 with DST, and the Trans-Arabian Pipe Line
 # Company used Aramco time in eastern Saudi Arabia and airline time in western.
 # (The American Military Aid Advisory Group used plain UTC.)  Antar writes,
 # "A man named Higgins, so the story goes, used to run a local power
 # station. One day, the whole thing became too much for Higgins and he
 # assembled his staff and laid down the law. 'I've had enough of this,' he
 # shrieked. 'It is now 12 o'clock Higgins Time, and from now on this station is
 # going to run on Higgins Time.' And so, until last year, it did."  See:
 # Antar E. Dinner at When? Saudi Aramco World, 1969 March/April. 2-3.
 # http://archive.aramcoworld.com/issue/196902/dinner.at.when.htm
 # Also see: Antar EN. Arabian flying is confusing.
 # Port Angeles (WA) Evening News. 1965-03-10. page 3.
 #
 # The TZ database cannot represent quasi-solar time; airline time is the best
 # we can do.  The 1946 foreign air news digest of the U.S. Civil Aeronautics
 # Board (OCLC 42299995) reported that the "... Arabian Government, inaugurated
 # a weekly Dhahran-Cairo service, via the Saudi Arabian cities of Riyadh and
 # Jidda, on March 14, 1947".  Shanks & Pottenger guessed 1950; go with the
 # earlier date.
 #
 # Shanks & Pottenger also state that until 1968-05-01 Saudi Arabia had two
 # time zones; the other zone, at UT +04, was in the far eastern part of
 # the country.  Presumably this is documenting airline time.  Ignore this,
 # as it's before our 1970 cutoff.
 #
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Riyadh	3:06:52 -	LMT	1947 Mar 14
 			3:00	-	+03
 Link Asia/Riyadh Antarctica/Syowa
 Link Asia/Riyadh Asia/Aden	# Yemen
 Link Asia/Riyadh Asia/Kuwait
 
 # Singapore
 # taken from Mok Ly Yng (2003-10-30)
 # https://web.archive.org/web/20190822231045/http://www.math.nus.edu.sg/~mathelmr/teaching/timezone.html
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Singapore	6:55:25 -	LMT	1901 Jan  1
 			6:55:25	-	SMT	1905 Jun  1 # Singapore M.T.
 			7:00	-	+07	1933 Jan  1
 			7:00	0:20	+0720	1936 Jan  1
 			7:20	-	+0720	1941 Sep  1
 			7:30	-	+0730	1942 Feb 16
 			9:00	-	+09	1945 Sep 12
 			7:30	-	+0730	1982 Jan  1
 			8:00	-	+08
 Link Asia/Singapore Asia/Kuala_Lumpur
 
 # Spratly Is
 # no information
 
 # Sri Lanka
 
 # From Paul Eggert (2013-02-21):
 # Milne says "Madras mean time use from May 1, 1898.  Prior to this Colombo
 # mean time, 5h. 4m. 21.9s. F., was used."  But 5:04:21.9 differs considerably
 # from Colombo's meridian 5:19:24, so for now ignore Milne and stick with
 # Shanks and Pottenger.
 
 # From Paul Eggert (1996-09-03):
 # "Sri Lanka advances clock by an hour to avoid blackout"
 # (, 1996-05-24,
 # no longer available as of 1999-08-17)
 # reported "the country's standard time will be put forward by one hour at
 # midnight Friday (1830 GMT) 'in the light of the present power crisis'."
 #
 # From Dharmasiri Senanayake, Sri Lanka Media Minister (1996-10-24), as quoted
 # by Shamindra in Daily News - Hot News Section
 #  (1996-10-26):
 # With effect from 12.30 a.m. on 26th October 1996
 # Sri Lanka will be six (06) hours ahead of GMT.
 
 # From Jesper Nørgaard Welen (2006-04-14), quoting Sri Lanka News Online
 #  (2006-04-13):
 # 0030 hrs on April 15, 2006 (midnight of April 14, 2006 +30 minutes)
 # at present, become 2400 hours of April 14, 2006 (midnight of April 14, 2006).
 
 # From Peter Apps and Ranga Sirila of Reuters (2006-04-12) in:
 # http://today.reuters.co.uk/news/newsArticle.aspx?type=scienceNews&storyID=2006-04-12T172228Z_01_COL295762_RTRIDST_0_SCIENCE-SRILANKA-TIME-DC.XML
 # [The Tamil Tigers] never accepted the original 1996 time change and simply
 # kept their clocks set five and a half hours ahead of Greenwich Mean
 # Time (GMT), in line with neighbor India.
 # From Paul Eggert (2006-04-18):
 # People who live in regions under Tamil control can use [TZ='Asia/Kolkata'],
 # as that zone has agreed with the Tamil areas since our cutoff date of 1970.
 
 # From Sadika Sumanapala (2016-10-19):
 # According to http://www.sltime.org (maintained by Measurement Units,
 # Standards & Services Department, Sri Lanka) abbreviation for Sri Lanka
 # standard time is SLST.
 #
 # From Paul Eggert (2016-10-18):
 # "SLST" seems to be reasonably recent and rarely-used outside time
 # zone nerd sources.  I searched Google News and found three uses of
 # it in the International Business Times of India in February and
 # March of this year when discussing cricket match times, but nothing
 # since then (though there has been a lot of cricket) and nothing in
 # other English-language news sources.  Our old abbreviation "LKT" is
 # even worse.  For now, let's use a numeric abbreviation; we can
 # switch to "SLST" if it catches on.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Colombo	5:19:24 -	LMT	1880
 			5:19:32	-	MMT	1906        # Moratuwa Mean Time
 			5:30	-	+0530	1942 Jan  5
 			5:30	0:30	+06	1942 Sep
 			5:30	1:00	+0630	1945 Oct 16  2:00
 			5:30	-	+0530	1996 May 25  0:00
 			6:30	-	+0630	1996 Oct 26  0:30
 			6:00	-	+06	2006 Apr 15  0:30
 			5:30	-	+0530
 
 # Syria
 # Rule	NAME	FROM	TO	-	IN	ON	AT	SAVE	LETTER/S
 Rule	Syria	1920	1923	-	Apr	Sun>=15	2:00	1:00	S
 Rule	Syria	1920	1923	-	Oct	Sun>=1	2:00	0	-
 Rule	Syria	1962	only	-	Apr	29	2:00	1:00	S
 Rule	Syria	1962	only	-	Oct	1	2:00	0	-
 Rule	Syria	1963	1965	-	May	1	2:00	1:00	S
 Rule	Syria	1963	only	-	Sep	30	2:00	0	-
 Rule	Syria	1964	only	-	Oct	1	2:00	0	-
 Rule	Syria	1965	only	-	Sep	30	2:00	0	-
 Rule	Syria	1966	only	-	Apr	24	2:00	1:00	S
 Rule	Syria	1966	1976	-	Oct	1	2:00	0	-
 Rule	Syria	1967	1978	-	May	1	2:00	1:00	S
 Rule	Syria	1977	1978	-	Sep	1	2:00	0	-
 Rule	Syria	1983	1984	-	Apr	9	2:00	1:00	S
 Rule	Syria	1983	1984	-	Oct	1	2:00	0	-
 Rule	Syria	1986	only	-	Feb	16	2:00	1:00	S
 Rule	Syria	1986	only	-	Oct	9	2:00	0	-
 Rule	Syria	1987	only	-	Mar	1	2:00	1:00	S
 Rule	Syria	1987	1988	-	Oct	31	2:00	0	-
 Rule	Syria	1988	only	-	Mar	15	2:00	1:00	S
 Rule	Syria	1989	only	-	Mar	31	2:00	1:00	S
 Rule	Syria	1989	only	-	Oct	1	2:00	0	-
 Rule	Syria	1990	only	-	Apr	1	2:00	1:00	S
 Rule	Syria	1990	only	-	Sep	30	2:00	0	-
 Rule	Syria	1991	only	-	Apr	 1	0:00	1:00	S
 Rule	Syria	1991	1992	-	Oct	 1	0:00	0	-
 Rule	Syria	1992	only	-	Apr	 8	0:00	1:00	S
 Rule	Syria	1993	only	-	Mar	26	0:00	1:00	S
 Rule	Syria	1993	only	-	Sep	25	0:00	0	-
 # IATA SSIM (1998-02) says 1998-04-02;
 # (1998-09) says 1999-03-29 and 1999-09-29; (1999-02) says 1999-04-02,
 # 2000-04-02, and 2001-04-02; (1999-09) says 2000-03-31 and 2001-03-31;
 # (2006) says 2006-03-31 and 2006-09-22;
 # for now ignore all these claims and go with Shanks & Pottenger,
 # except for the 2006-09-22 claim (which seems right for Ramadan).
 Rule	Syria	1994	1996	-	Apr	 1	0:00	1:00	S
 Rule	Syria	1994	2005	-	Oct	 1	0:00	0	-
 Rule	Syria	1997	1998	-	Mar	lastMon	0:00	1:00	S
 Rule	Syria	1999	2006	-	Apr	 1	0:00	1:00	S
 # From Stephen Colebourne (2006-09-18):
 # According to IATA data, Syria will change DST on 21st September [21:00 UTC]
 # this year [only]....  This is probably related to Ramadan, like Egypt.
 Rule	Syria	2006	only	-	Sep	22	0:00	0	-
 # From Paul Eggert (2007-03-29):
 # Today the AP reported "Syria will switch to summertime at midnight Thursday."
 # http://www.iht.com/articles/ap/2007/03/29/africa/ME-GEN-Syria-Time-Change.php
 Rule	Syria	2007	only	-	Mar	lastFri	0:00	1:00	S
 # From Jesper Nørgaard (2007-10-27):
 # The sister center ICARDA of my work CIMMYT is confirming that Syria DST will
 # not take place 1st November at 0:00 o'clock but 1st November at 24:00 or
 # rather Midnight between Thursday and Friday. This does make more sense than
 # having it between Wednesday and Thursday (two workdays in Syria) since the
 # weekend in Syria is not Saturday and Sunday, but Friday and Saturday. So now
 # it is implemented at midnight of the last workday before weekend...
 #
 # From Steffen Thorsen (2007-10-27):
 # Jesper Nørgaard Welen wrote:
 #
 # > "Winter local time in Syria will be observed at midnight of Thursday 1
 # > November 2007, and the clock will be put back 1 hour."
 #
 # I found confirmation on this in this gov.sy-article (Arabic):
 # http://wehda.alwehda.gov.sy/_print_veiw.asp?FileName=12521710520070926111247
 #
 # which using Google's translate tools says:
 # Council of Ministers also approved the commencement of work on
 # identifying the winter time as of Friday, 2/11/2007 where the 60th
 # minute delay at midnight Thursday 1/11/2007.
 Rule	Syria	2007	only	-	Nov	 Fri>=1	0:00	0	-
 
 # From Stephen Colebourne (2008-03-17):
 # For everyone's info, I saw an IATA time zone change for [Syria] for
 # this month (March 2008) in the last day or so....
 # Country     Time Standard   --- DST Start ---   --- DST End ---  DST
 # Name        Zone Variation   Time    Date        Time    Date
 # Variation
 # Syrian Arab
 # Republic    SY    +0200      2200  03APR08       2100  30SEP08   +0300
 #                              2200  02APR09       2100  30SEP09   +0300
 #                              2200  01APR10       2100  30SEP10   +0300
 
 # From Arthur David Olson (2008-03-17):
 # Here's a link to English-language coverage by the Syrian Arab News
 # Agency (SANA)...
 # http://www.sana.sy/eng/21/2008/03/11/165173.htm
 # ...which reads (in part) "The Cabinet approved the suggestion of the
 # Ministry of Electricity to begin daylight savings time on Friday April
 # 4th, advancing clocks one hour ahead on midnight of Thursday April 3rd."
 # Since Syria is two hours east of UTC, the 2200 and 2100 transition times
 # shown above match up with midnight in Syria.
 
 # From Arthur David Olson (2008-03-18):
 # My best guess at a Syrian rule is "the Friday nearest April 1";
 # coding that involves either using a "Mar Fri>=29" construct that old time zone
 # compilers can't handle  or having multiple Rules (a la Israel).
 # For now, use "Apr Fri>=1", and go with IATA on a uniform Sep 30 end.
 
 # From Steffen Thorsen (2008-10-07):
 # Syria has now officially decided to end DST on 2008-11-01 this year,
 # according to the following article in the Syrian Arab News Agency (SANA).
 #
 # The article is in Arabic, and seems to tell that they will go back to
 # winter time on 2008-11-01 at 00:00 local daylight time (delaying/setting
 # clocks back 60 minutes).
 #
 # http://sana.sy/ara/2/2008/10/07/195459.htm
 
 # From Steffen Thorsen (2009-03-19):
 # Syria will start DST on 2009-03-27 00:00 this year according to many sources,
 # two examples:
 #
 # http://www.sana.sy/eng/21/2009/03/17/217563.htm
 # (English, Syrian Arab News # Agency)
 # http://thawra.alwehda.gov.sy/_View_news2.asp?FileName=94459258720090318012209
 # (Arabic, gov-site)
 #
 # We have not found any sources saying anything about when DST ends this year.
 #
 # Our summary
 # https://www.timeanddate.com/news/time/syria-dst-starts-march-27-2009.html
 
 # From Steffen Thorsen (2009-10-27):
 # The Syrian Arab News Network on 2009-09-29 reported that Syria will
 # revert back to winter (standard) time on midnight between Thursday
 # 2009-10-29 and Friday 2009-10-30:
 # http://www.sana.sy/ara/2/2009/09/29/247012.htm (Arabic)
 
 # From Arthur David Olson (2009-10-28):
 # We'll see if future DST switching times turn out to be end of the last
 # Thursday of the month or the start of the last Friday of the month or
 # something else. For now, use the start of the last Friday.
 
 # From Steffen Thorsen (2010-03-17):
 # The "Syrian News Station" reported on 2010-03-16 that the Council of
 # Ministers has decided that Syria will start DST on midnight Thursday
 # 2010-04-01: (midnight between Thursday and Friday):
 # http://sns.sy/sns/?path=news/read/11421 (Arabic)
 
 # From Steffen Thorsen (2012-03-26):
 # Today, Syria's government announced that they will start DST early on Friday
 # (00:00). This is a bit earlier than the past two years.
 #
 # From Syrian Arab News Agency, in Arabic:
 # http://www.sana.sy/ara/2/2012/03/26/408215.htm
 #
 # Our brief summary:
 # https://www.timeanddate.com/news/time/syria-dst-2012.html
 
 # From Arthur David Olson (2012-03-27):
 # Assume last Friday in March going forward XXX.
 
 Rule	Syria	2008	only	-	Apr	Fri>=1	0:00	1:00	S
 Rule	Syria	2008	only	-	Nov	1	0:00	0	-
 Rule	Syria	2009	only	-	Mar	lastFri	0:00	1:00	S
 Rule	Syria	2010	2011	-	Apr	Fri>=1	0:00	1:00	S
 Rule	Syria	2012	max	-	Mar	lastFri	0:00	1:00	S
 Rule	Syria	2009	max	-	Oct	lastFri	0:00	0	-
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Damascus	2:25:12 -	LMT	1920 # Dimashq
 			2:00	Syria	EE%sT
 
 # Tajikistan
 # From Shanks & Pottenger.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Dushanbe	4:35:12 -	LMT	1924 May  2
 			5:00	-	+05	1930 Jun 21
 			6:00 RussiaAsia +06/+07	1991 Mar 31  2:00s
 			5:00	1:00	+06	1991 Sep  9  2:00s
 			5:00	-	+05
 
 # Thailand
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Bangkok	6:42:04	-	LMT	1880
 			6:42:04	-	BMT	1920 Apr # Bangkok Mean Time
 			7:00	-	+07
 Link Asia/Bangkok Asia/Phnom_Penh	# Cambodia
 Link Asia/Bangkok Asia/Vientiane	# Laos
 Link Asia/Bangkok Indian/Christmas
 
 # Turkmenistan
 # From Shanks & Pottenger.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Ashgabat	3:53:32 -	LMT	1924 May  2 # or Ashkhabad
 			4:00	-	+04	1930 Jun 21
 			5:00 RussiaAsia	+05/+06	1991 Mar 31  2:00
 			4:00 RussiaAsia	+04/+05	1992 Jan 19  2:00
 			5:00	-	+05
 
 # United Arab Emirates
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Dubai	3:41:12 -	LMT	1920
 			4:00	-	+04
 Link Asia/Dubai Asia/Muscat	# Oman
 Link Asia/Dubai Indian/Mahe
 Link Asia/Dubai Indian/Reunion
 
 # Uzbekistan
 # Byalokoz 1919 says Uzbekistan was 4:27:53.
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 Zone	Asia/Samarkand	4:27:53 -	LMT	1924 May  2
 			4:00	-	+04	1930 Jun 21
 			5:00	-	+05	1981 Apr  1
 			5:00	1:00	+06	1981 Oct  1
 			6:00	-	+06	1982 Apr  1
 			5:00 RussiaAsia	+05/+06	1992
 			5:00	-	+05
 # Milne says Tashkent was 4:37:10.8.
 		#STDOFF	4:37:10.8
 Zone	Asia/Tashkent	4:37:11 -	LMT	1924 May  2
 			5:00	-	+05	1930 Jun 21
 			6:00 RussiaAsia	+06/+07	1991 Mar 31  2:00
 			5:00 RussiaAsia	+05/+06	1992
 			5:00	-	+05
 
 # Vietnam
 
 # 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:
 # 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.
 # which is used below even though the modern-day Phù Liễn Observatory
 # is closer to 07:06:31.  Abbreviate Phù Liễn Mean Time as PLMT.
 #
 # 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,
 # 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 hai thế kỷ (1802-2010) và các lịch vĩnh cửu",
 # NXB Thuận Hoá, Huế, 1995.
 
 # Zone	NAME		STDOFF	RULES	FORMAT	[UNTIL]
 		#STDOFF	7:06:30.13
 Zone Asia/Ho_Chi_Minh	7:06:30 -	LMT	1906 Jul  1
 			7:06:30	-	PLMT	1911 May  1 # Phù Liễn MT
 			7:00	-	+07	1942 Dec 31 23:00
 			8:00	-	+08	1945 Mar 14 23:00
 			9:00	-	+09	1945 Sep  2
 			7:00	-	+07	1947 Apr  1
 			8:00	-	+08	1955 Jul  1
 			7:00	-	+07	1959 Dec 31 23:00
 			8:00	-	+08	1975 Jun 13
 			7: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.
 # For timestamps before 1970, see Asia/Hanoi in the file 'backzone'.
 
 
 # Yemen
 # See Asia/Riyadh.
diff --git a/contrib/tzdata/theory.html b/contrib/tzdata/theory.html
index 2b14c5114686..56390ae44a8d 100644
--- a/contrib/tzdata/theory.html
+++ b/contrib/tzdata/theory.html
@@ -1,1477 +1,1479 @@
 
 
 
   Theory and pragmatics of the tz code and data
   
   
 
 
 
 
Theory and pragmatics of the tz code and data

   
Outline

   
 
 

   
Scope of the tz database

 

 The tz
 database attempts to record the history and predicted future of
 civil time scales.
 It organizes time zone and daylight saving time
 data by partitioning the world into timezones
 whose clocks all agree about timestamps that occur after the POSIX Epoch
 (1970-01-01 00:00:00 UTC).
 Although 1970 is a somewhat-arbitrary cutoff, there are significant
 challenges to moving the cutoff earlier even by a decade or two, due
 to the wide variety of local practices before computer timekeeping
 became prevalent.
 Most timezones correspond to a notable location and the database
 records all known clock transitions for that location;
 some timezones correspond instead to a fixed UTC offset.
 

 
 

 Each timezone typically corresponds to a geographical region that is
 smaller than a traditional time zone, because clocks in a timezone
 all agree after 1970 whereas a traditional time zone merely
 specifies current standard time. For example, applications that deal
 with current and future timestamps in the traditional North
 American mountain time zone can choose from the timezones
 America/Denver which observes US-style daylight saving
 time (DST),
 America/Mazatlan which observes Mexican-style DST,
 and America/Phoenix which does not observe DST.
 Applications that also deal with past timestamps in the mountain time
 zone can choose from over a dozen timezones, such as
 America/Boise, America/Edmonton, and
 America/Hermosillo, each of which currently uses mountain
 time but differs from other timezones for some timestamps after 1970.
 

 
 

 Clock transitions before 1970 are recorded for location-based timezones,
 because most systems support timestamps before 1970 and could
 misbehave if data entries were omitted for pre-1970 transitions.
 However, the database is not designed for and does not suffice for
 applications requiring accurate handling of all past times everywhere,
 as it would take far too much effort and guesswork to record all
 details of pre-1970 civil timekeeping.
 Although some information outside the scope of the database is
 collected in a file backzone that is distributed along
 with the database proper, this file is less reliable and does not
 necessarily follow database guidelines.
 

 
 

 As described below, reference source code for using the
 tz database is also available.
 The tz code is upwards compatible with POSIX, an international
 standard for UNIX-like systems.
 As of this writing, the current edition of POSIX is:  The Open
 Group Base Specifications Issue 7, 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.
 A tz 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 UTC,
 are variable.
 It does not always make sense to talk about a timezone's
 "base offset", which is not necessarily a single number.
 

 
 

 
 

   
Timezone identifiers

 

 Each timezone has a name that uniquely identifies the timezone.
 Inexperienced users are not expected to select these names unaided.
 Distributors should provide documentation and/or a simple selection
 interface that explains each name via a map or via descriptive text like
 "Czech Republic" instead of the timezone name "Europe/Prague".
 If geolocation information is available, a selection interface can
 locate the user on a timezone map or prioritize names that are
 geographically close. For an example selection interface, see the
 tzselect program in the tz code.
-The Unicode Common Locale Data
+The Unicode Common Locale Data
 Repository contains data that may be useful for other selection
 interfaces; it maps timezone names like Europe/Prague to
 locale-dependent strings like "Prague", "Praha", "Прага", and "布拉格".
 

 
 

 The naming conventions attempt to strike a balance
 among the following goals:
 

 
 
    
   
  • 
     Uniquely identify every timezone where clocks have agreed since 1970.
     This is essential for the intended use: static clocks keeping local
     civil time.
   
    • 
   
  • 
     Indicate to experts where the timezone's clocks typically are.
   
    • 
   
  • 
     Be robust in the presence of political changes.
     For example, names are typically not tied to countries, to avoid
     incompatibilities when countries change their name (e.g.,
     Swaziland→Eswatini) or when locations change countries (e.g., Hong
     Kong from UK colony to China).
     There is no requirement that every country or national
     capital must have a timezone name.
   
    • 
   
  • 
     Be portable to a wide variety of implementations.
   
    • 
   
  • 
     Use a consistent naming conventions over the entire world.
   
    • 
 

 
 

 Names normally have the form
 AREA/LOCATION, where
 AREA is a continent or ocean, and
 LOCATION is a specific location within the area.
 North and South America share the same area, 'America'.
 Typical names are 'Africa/Cairo',
 'America/New_York', and 'Pacific/Honolulu'.
 Some names are further qualified to help avoid confusion; for example,
 'America/Indiana/Petersburg' distinguishes Petersburg,
 Indiana from other Petersburgs in America.
 

 
 

 Here are the general guidelines used for
 choosing timezone names,
 in decreasing order of importance:
 

 
 
    
   
  • 
     Use only valid POSIX file name components (i.e., the parts of
     names other than '/').
     Do not use the file name components '.' and
     '..'.
     Within a file name component, use only ASCII letters,
     '.', '-' and '_'.
     Do not use digits, as that might create an ambiguity with POSIX
     TZ strings.
     A file name component must not exceed 14 characters or start with
     '-'.
     E.g., prefer America/Noronha to
     America/Fernando_de_Noronha.
     Exceptions: see the discussion of legacy names below.
   
    • 
   
  • 
     A name must not be empty, or contain '//', or
     start or end with '/'.
   
    • 
   
  • 
     Do not use names that differ only in case.
     Although the reference implementation is case-sensitive, some
     other implementations are not, and they would mishandle names
     differing only in case.
   
    • 
   
  • 
     If one name A is an initial prefix of another
     name AB (ignoring case), then B must not
     start with '/', as a regular file cannot have the
     same name as a directory in POSIX.
     For example, America/New_York precludes
     America/New_York/Bronx.
   
    • 
   
  • 
     Uninhabited regions like the North Pole and Bouvet Island
     do not need locations, since local time is not defined there.
   
    • 
   
  • 
     If all the clocks in a timezone have agreed since 1970,
     do not bother to include more than one timezone
     even if some of the clocks disagreed before 1970.
     Otherwise these tables would become annoyingly large.
   
    • 
   
  • 
     If boundaries between regions are fluid, such as during a war or
     insurrection, do not bother to create a new timezone merely
     because of yet another boundary change. This helps prevent table
     bloat and simplifies maintenance.
   
    • 
   
  • 
     If a name is ambiguous, use a less ambiguous alternative;
     e.g., many cities are named San José and Georgetown, so
     prefer America/Costa_Rica to
     America/San_Jose and America/Guyana
     to America/Georgetown.
   
    • 
   
  • 
     Keep locations compact.
     Use cities or small islands, not countries or regions, so that any
     future changes do not split individual locations into different
     timezones.
     E.g., prefer Europe/Paris to Europe/France,
     since
     France
     has had multiple time zones.
   
    • 
   
  • 
     Use mainstream English spelling, e.g., prefer
     Europe/Rome to Europa/Roma, and
     prefer Europe/Athens to the Greek
     Ευρώπη/Αθήνα or the Romanized
     Evrópi/Athína.
     The POSIX file name restrictions encourage this guideline.
   
    • 
   
  • 
     Use the most populous among locations in a region,
     e.g., prefer Asia/Shanghai to
     Asia/Beijing.
     Among locations with similar populations, pick the best-known
     location, e.g., prefer Europe/Rome to
     Europe/Milan.
   
    • 
   
  • 
     Use the singular form, e.g., prefer Atlantic/Canary to
     Atlantic/Canaries.
   
    • 
   
  • 
     Omit common suffixes like '_Islands' and
     '_City', unless that would lead to ambiguity.
     E.g., prefer America/Cayman to
     America/Cayman_Islands and
     America/Guatemala to
     America/Guatemala_City, but prefer
     America/Mexico_City to
     America/Mexico
     because the
     country of Mexico has several time zones.
   
    • 
   
  • 
     Use '_' to represent a space.
   
    • 
   
  • 
     Omit '.' from abbreviations in names.
     E.g., prefer Atlantic/St_Helena to
     Atlantic/St._Helena.
   
    • 
   
  • 
     Do not change established names if they only marginally violate
     the above guidelines.
     For example, do not change the existing name Europe/Rome to
     Europe/Milan merely because Milan's population has grown
     to be somewhat greater than Rome's.
   
    • 
   
  • 
     If a name is changed, put its old spelling in the
     'backward' file as a link to the new spelling.
     This means old spellings will continue to work.
     Ordinarily a name change should occur only in the rare case when
     a location's consensus English-language spelling changes; for example,
     in 2008 Asia/Calcutta was renamed to Asia/Kolkata
     due to long-time widespread use of the new city name instead of the old.
   
    • 
 

 
 

 Guidelines have evolved with time, and names following old versions of
 these guidelines might not follow the current version. When guidelines
 have changed, old names continue to be supported. Guideline changes
 have included the following:
 

 
 
    
 
  • 
 Older versions of this package used a different naming scheme.
 See the file 'backward' for most of these older names
 (e.g., 'US/Eastern' instead of 'America/New_York').
 The other old-fashioned names still supported are
 'WET', 'CET', 'MET', and
 'EET' (see the file 'europe').
 
    • 
 
 
  • 
 Older versions of this package defined legacy names that are
 incompatible with the first guideline of location names, but which are
 still supported.
 These legacy names are mostly defined in the file
 'etcetera'.
 Also, the file 'backward' defines the legacy names
 'GMT0', 'GMT-0' and 'GMT+0',
 and the file 'northamerica' defines the legacy names
 'EST5EDT', 'CST6CDT',
 'MST7MDT', and 'PST8PDT'.
 
    • 
 
 
  • 
 Older versions of these guidelines said that
 there should typically be at least one name for each ISO
 3166-1 officially assigned two-letter code for an inhabited
 country or territory.
 This old guideline has been dropped, as it was not needed to handle
 timestamps correctly and it increased maintenance burden.
 
    • 
 

 
 

 The file zone1970.tab lists geographical locations used
 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 zone1970.tab location's
 longitude
 corresponds to
 its local mean
 time (LMT) offset with one hour for every 15°
 east longitude, this relationship is not exact.
 The backward-compatibility file zone.tab is similar
 but conforms to the older-version guidelines related to ISO 3166-1;
 it lists only one country code per entry and unlike zone1970.tab
 it can list names defined in backward.
 

 
 

 The database defines each timezone name to be a zone, or a link to a zone.
 The source file backward defines links for backward
 compatibility; it does not define zones.
 Although backward 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 backward or in some other file.
 The source file etcetera defines names that may be useful
 on platforms that do not support POSIX-style TZ strings;
 no other source file other than backward
 contains links to its zones.
 One of etcetera's names is Etc/UTC,
 used by functions like gmtime to obtain leap
 second information on platforms that support leap seconds.
 Another etcetera name, GMT,
 is used by older code releases.
 

 

 
 

   
Time zone abbreviations

 

 When this package is installed, it generates time zone abbreviations
 like 'EST' to be compatible with human tradition and POSIX.
 Here are the general guidelines used for choosing time zone abbreviations,
 in decreasing order of importance:
 

 
 
    
   
  • 
     Use three to six characters that are ASCII alphanumerics or
     '+' or '-'.
     Previous editions of this database also used characters like
     space and '?', but these characters have a
     special meaning to the
     UNIX shell
     and cause commands like
     'set
     `date`'
     to have unexpected effects.
     Previous editions of this guideline required upper-case letters, but the
     Congressman who introduced
     Chamorro
     Standard Time preferred "ChST", so lower-case letters are now
     allowed.
     Also, POSIX from 2001 on relaxed the rule to allow '-',
     '+', and alphanumeric characters from the portable
     character set in the current locale.
     In practice ASCII alphanumerics and '+' and
     '-' are safe in all locales.
 
     
    
     In other words, in the C locale the POSIX extended regular
     expression [-+[:alnum:]]{3,6} should match the
     abbreviation.
     This guarantees that all abbreviations could have been specified by a
     POSIX TZ string.
     
    
   
    • 
   
  • 
     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'.
 
     
    
     These abbreviations (for standard/daylight/etc. time) are:
       ACST/ACDT Australian Central,
       AST/ADT/APT/AWT/ADDT Atlantic,
       AEST/AEDT Australian Eastern,
       AHST/AHDT Alaska-Hawaii,
       AKST/AKDT Alaska,
       AWST/AWDT Australian Western,
       BST/BDT Bering,
       CAT/CAST Central Africa,
       CET/CEST/CEMT Central European,
       ChST Chamorro,
       CST/CDT/CWT/CPT/CDDT Central [North America],
       CST/CDT China,
       GMT/BST/IST/BDST Greenwich,
       EAT East Africa,
       EST/EDT/EWT/EPT/EDDT Eastern [North America],
       EET/EEST Eastern European,
       GST/GDT Guam,
       HST/HDT/HWT/HPT Hawaii,
       HKT/HKST/HKWT Hong Kong,
       IST India,
       IST/GMT Irish,
       IST/IDT/IDDT Israel,
       JST/JDT Japan,
       KST/KDT Korea,
       MET/MEST Middle European (a backward-compatibility alias for
 	Central European),
       MSK/MSD Moscow,
       MST/MDT/MWT/MPT/MDDT Mountain,
       NST/NDT/NWT/NPT/NDDT Newfoundland,
       NST/NDT/NWT/NPT Nome,
       NZMT/NZST New Zealand through 1945,
       NZST/NZDT New Zealand 1946–present,
       PKT/PKST Pakistan,
       PST/PDT/PWT/PPT/PDDT Pacific,
       PST/PDT Philippine,
       SAST South Africa,
       SST Samoa,
       UTC Universal,
       WAT/WAST West Africa,
       WET/WEST/WEMT Western European,
       WIB Waktu Indonesia Barat,
       WIT Waktu Indonesia Timur,
       WITA Waktu Indonesia Tengah,
       YST/YDT/YWT/YPT/YDDT Yukon.
     
    
   
    • 
   
  • 
     
    
     For times taken from a city's longitude, use the
     traditional xMT notation.
     The only abbreviation like this in current use is 'GMT'.
     The others are for timestamps before 1960,
     except that Monrovia Mean Time persisted until 1972.
     Typically, numeric abbreviations (e.g., '-004430' for
     MMT) would cause trouble here, as the numeric strings would exceed
     the POSIX length limit.
     
    
 
     
    
     These abbreviations are:
       AMT Asunción, Athens;
       BMT Baghdad, Bangkok, Batavia, Bermuda, Bern, Bogotá, Bridgetown,
         Brussels, Bucharest;
       CMT Calamarca, Caracas, Chisinau, Colón, Córdoba;
       DMT Dublin/Dunsink;
       EMT Easter;
       FFMT Fort-de-France;
       FMT Funchal;
       GMT Greenwich;
       HMT Havana, Helsinki, Horta, Howrah;
       IMT Irkutsk, Istanbul;
       JMT Jerusalem;
       KMT Kaunas, Kyiv, Kingston;
       LMT Lima, Lisbon, local, Luanda;
       MMT Macassar, Madras, Malé, Managua, Minsk, Monrovia, Montevideo,
 	Moratuwa, Moscow;
       PLMT Phù Liễn;
       PMT Paramaribo, Paris, Perm, Pontianak, Prague;
       PMMT Port Moresby;
       QMT Quito;
       RMT Rangoon, Riga, Rome;
       SDMT Santo Domingo;
       SJMT San José;
       SMT Santiago, Simferopol, Singapore, Stanley;
       TBMT Tbilisi;
       TMT Tallinn, Tehran;
       WMT Warsaw;
       ZMT Zomba.
     
    
 
     
    
     A few abbreviations also follow the pattern that
     GMT/BST established for time in the UK.
     They are:
       BMT/BST for Bermuda 1890–1930,
       CMT/BST for Calamarca Mean Time and Bolivian Summer Time
 	1890–1932,
       DMT/IST for Dublin/Dunsink Mean Time and Irish Summer Time
 	1880–1916,
       MMT/MST/MDST for Moscow 1880–1919, and
       RMT/LST for Riga Mean Time and Latvian Summer time 1880–1926.
     
     
    
   
    • 
   
  • 
     Use 'LMT' for local mean time of locations before the
     introduction of standard time; see "Scope of the
     tz database".
   
    • 
   
  • 
     If there is no common English abbreviation, use numeric offsets like
     -05 and +0530 that are generated
     by zic's %z notation.
   
    • 
   
  • 
     Use current abbreviations for older timestamps to avoid confusion.
     For example, in 1910 a common English abbreviation for time
     in central Europe was 'MEZ' (short for both "Middle European
     Zone" and for "Mitteleuropäische Zeit" in German).
     Nowadays 'CET' ("Central European Time") is more common in
     English, and the database uses 'CET' even for circa-1910
     timestamps as this is less confusing for modern users and avoids
     the need for determining when 'CET' supplanted 'MEZ' in common
     usage.
   
    • 
   
  • 
     Use a consistent style in a timezone's history.
     For example, if a history tends to use numeric
     abbreviations and a particular entry could go either way, use a
     numeric abbreviation.
   
    • 
   
  • 
     Use
     Universal Time
     (UT) (with time zone abbreviation '-00') for
     locations while uninhabited.
     The leading '-' is a flag that the UT offset is in
     some sense undefined; this notation is derived
-    from Internet
+    from Internet
     RFC 3339.
   
    • 
 

 
 

 Application writers should note that these abbreviations are ambiguous
 in practice: e.g., 'CST' means one thing in China and something else
 in North America, and 'IST' can refer to time in India, Ireland or
 Israel.
 To avoid ambiguity, use numeric UT offsets like
 '-0600' instead of time zone abbreviations like 'CST'.
 

 

 
 

   
Accuracy of the tz database

 

 The tz database is not authoritative, and it
 surely has errors.
 Corrections are welcome and encouraged; see the file CONTRIBUTING.
 Users requiring authoritative data should consult national standards
 bodies and the references cited in the database's comments.
 

 
 

 Errors in the tz database arise from many sources:
 

 
 
    
   
  • 
     The tz database predicts future
     timestamps, and current predictions
     will be incorrect after future governments change the rules.
     For example, if today someone schedules a meeting for 13:00 next
     October 1, Casablanca time, and tomorrow Morocco changes its
     daylight saving rules, software can mess up after the rule change
     if it blithely relies on conversions made before the change.
   
    • 
   
  • 
     The pre-1970 entries in this database cover only a tiny sliver of how
     clocks actually behaved; the vast majority of the necessary
     information was lost or never recorded.
     Thousands more timezones would be needed if
     the tz database's scope were extended to
     cover even just the known or guessed history of standard time; for
     example, the current single entry for France would need to split
     into dozens of entries, perhaps hundreds.
     And in most of the world even this approach would be misleading
     due to widespread disagreement or indifference about what times
     should be observed.
     In her 2015 book
     The
+    href="https://www.hup.harvard.edu/catalog.php?isbn=9780674286146">The
     Global Transformation of Time, 1870–1950,
     Vanessa Ogle writes
     "Outside of Europe and North America there was no system of time
     zones at all, often not even a stable landscape of mean times,
     prior to the middle decades of the twentieth century".
     See: Timothy Shenk, Booked:
       A Global History of Time. Dissent 2015-12-17.
   
    • 
   
  • 
     Most of the pre-1970 data entries come from unreliable sources, often
     astrology books that lack citations and whose compilers evidently
     invented entries when the true facts were unknown, without
     reporting which entries were known and which were invented.
     These books often contradict each other or give implausible entries,
     and on the rare occasions when they are checked they are
     typically found to be incorrect.
   
    • 
   
  • 
     For the UK the tz database relies on
     years of first-class work done by
     Joseph Myers and others; see
     "History of
     legal time in Britain".
     Other countries are not done nearly as well.
   
    • 
   
  • 
     Sometimes, different people in the same city maintain clocks
     that differ significantly.
     Historically, railway time was used by railroad companies (which
     did not always
     agree with each other), church-clock time was used for birth
     certificates, etc.
     More recently, competing political groups might disagree about
     clock settings. Often this is merely common practice, but
     sometimes it is set by law.
     For example, from 1891 to 1911 the UT offset in France
     was legally UT +00:09:21 outside train stations and
     UT +00:04:21 inside. Other examples include
     Chillicothe in 1920, Palm Springs in 1946/7, and Jerusalem and
     Ürümqi to this day.
   
    • 
   
  • 
     Although a named location in the tz
     database stands for the containing region, its pre-1970 data
     entries are often accurate for only a small subset of that region.
     For example, Europe/London stands for the United
     Kingdom, but its pre-1847 times are valid only for locations that
     have London's exact meridian, and its 1847 transition
     to GMT is known to be valid only for the L&NW and
     the Caledonian railways.
   
    • 
   
  • 
     The tz database does not record the
     earliest time for which a timezone's
     data entries are thereafter valid for every location in the region.
     For example, Europe/London is valid for all locations
     in its region after GMT was made the standard time,
     but the date of standardization (1880-08-02) is not in the
     tz database, other than in commentary.
     For many timezones the earliest time of
     validity is unknown.
   
    • 
   
  • 
     The tz database does not record a
     region's boundaries, and in many cases the boundaries are not known.
     For example, the timezone
     America/Kentucky/Louisville represents a region
     around the city of Louisville, the boundaries of which are
     unclear.
   
    • 
   
  • 
     Changes that are modeled as instantaneous transitions in the
     tz
     database were often spread out over hours, days, or even decades.
   
    • 
   
  • 
     Even if the time is specified by law, locations sometimes
     deliberately flout the law.
   
    • 
   
  • 
     Early timekeeping practices, even assuming perfect clocks, were
     often not specified to the accuracy that the
     tz database requires.
   
    • 
   
  • 
     The tz database cannot represent stopped clocks.
     However, on 1911-03-11 at 00:00, some public-facing French clocks
     were changed by stopping them for a few minutes to effect a transition.
     The tz database models this via a
     backward transition; the relevant French legislation does not
     specify exactly how the transition was to occur.
   
    • 
   
  • 
     Sometimes historical timekeeping was specified more precisely
     than what the tz code can handle.
     For example, from 1880 to 1916 clocks in Ireland observed Dublin Mean
     Time (estimated to be UT
     −00:25:21.1); although the tz
     source data can represent the .1 second, TZif files and the code cannot.
     In practice these old specifications were rarely if ever
     implemented to subsecond precision.
   
    • 
   
  • 
     Even when all the timestamp transitions recorded by the
     tz database are correct, the
     tz rules that generate them may not
     faithfully reflect the historical rules.
     For example, from 1922 until World War II the UK moved clocks
     forward the day following the third Saturday in April unless that
     was Easter, in which case it moved clocks forward the previous
     Sunday.
     Because the tz database has no
     way to specify Easter, these exceptional years are entered as
     separate tz Rule lines, even though the
     legal rules did not change.
     When transitions are known but the historical rules behind them are not,
     the database contains Zone and Rule
     entries that are intended to represent only the generated
     transitions, not any underlying historical rules; however, this
     intent is recorded at best only in commentary.
   
    • 
   
  • 
     The tz database models time
     using the proleptic
     Gregorian calendar with days containing 24 equal-length hours
     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 Julian
     calendar,
     and Roman
     timekeeping 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 the
     east African practice of starting the day at dawn, renumbering
     the Western 06:00 to be 12:00. These practices are largely outside
     the scope of the tz code and data, which
     provide only limited support for date and time localization
     such as that required by POSIX.
     If DST is not used a different time zone
     can often do the trick; for example, in Kenya a TZ setting
     like <-03>3 or America/Cayenne starts
     the day six hours later than Africa/Nairobi does.
   
    • 
   
  • 
     Early clocks were less reliable, and data entries do not represent
     clock error.
   
    • 
   
  • 
     The tz database assumes Universal Time
     (UT) as an origin, even though UT is not
     standardized for older timestamps.
     In the tz database commentary,
     UT denotes a family of time standards that includes
     Coordinated Universal Time (UTC) along with other
     variants such as UT1 and GMT,
     with days starting at midnight.
     Although UT equals UTC for modern
     timestamps, UTC was not defined until 1960, so
     commentary uses the more-general abbreviation UT for
     timestamps that might predate 1960.
     Since UT, UT1, etc. disagree slightly,
     and since pre-1972 UTC seconds varied in length,
     interpretation of older timestamps can be problematic when
     subsecond accuracy is needed.
   
    • 
   
  • 
     Civil time was not based on atomic time before 1972, and we do not
     know the history of
     earth's
     rotation accurately enough to map SI seconds to
     historical solar time
     to more than about one-hour accuracy.
     See: Stephenson FR, Morrison LV, Hohenkerk CY.
     Measurement of
     the Earth's rotation: 720 BC to AD 2015.
-    Proc Royal Soc A. 2016 Dec 7;472:20160404.
+    Proc Royal Soc A. 2016;472:20160404.
     Also see: Espenak F. Uncertainty
     in Delta T (ΔT).
   
    • 
   
  • 
     The relationship between POSIX time (that is, UTC but
     ignoring leap
     seconds) and UTC is not agreed upon after 1972.
     Although the POSIX
     clock officially stops during an inserted leap second, at least one
     proposed standard has it jumping back a second instead; and in
     practice POSIX clocks more typically either progress glacially during
     a leap second, or are slightly slowed while near a leap second.
   
    • 
   
  • 
     The tz database does not represent how
     uncertain its information is.
     Ideally it would contain information about when data entries are
     incomplete or dicey.
     Partial temporal knowledge is a field of active research, though,
     and it is not clear how to apply it here.
   
    • 
 

 
 

 In short, many, perhaps most, of the tz
 database's pre-1970 and future timestamps are either wrong or
 misleading.
 Any attempt to pass the
 tz database off as the definition of time
 should be unacceptable to anybody who cares about the facts.
 In particular, the tz database's
 LMT offsets should not be considered meaningful, and
 should not prompt creation of timezones
 merely because two locations
 differ in LMT or transitioned to standard time at
 different dates.
 

 

 
 

   
Time and date functions

 

 The tz code contains time and date functions
 that are upwards compatible with those of POSIX.
 Code compatible with this package is already
 part of many platforms, 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
 'zic' supplied with this package instead of using the
 system 'zic', since the format of zic's
 input is occasionally extended, and a platform may still be shipping
 an older zic.
 

 
 
POSIX properties and limitations

 
    
   
  • 
     
    
     In POSIX, time display in a process is controlled by the
     environment variable TZ.
     Unfortunately, the POSIX
     TZ string takes a form that is hard to describe and
     is error-prone in practice.
     Also, POSIX TZ strings cannot deal with daylight
     saving time rules not based on the Gregorian calendar (as in
     Iran), or with situations where more than two time zone
     abbreviations or UT offsets are used in an area.
     
    
 
     
    
     The POSIX TZ string takes the following form:
     
    
 
     
    
     stdoffset[dst[offset][,date[/time],date[/time]]]
     
    
 
     
    
     where:
     
    
 
     
    
       
    std and dst
    
 	are 3 or more characters specifying the standard
 	and daylight saving time (DST) zone abbreviations.
 	Starting with POSIX.1-2001, std and dst
 	may also be in a quoted form like '<+09>';
 	this allows "+" and "-" in the names.
       
    
       
    offset
    
 	is of the form
 	'[±]hh:[mm[:ss]]'
 	and specifies the offset west of UT.
 	'hh' may be a single digit;
 	0≤hh≤24.
 	The default DST offset is one hour ahead of
 	standard time.
       
    
       
    date[/time],date[/time]
    
 	specifies the beginning and end of DST.
 	If this is absent, the system supplies its own ruleset
 	for DST, and its rules can differ from year to year;
 	typically US DST rules are used.
       
    
       
    time
    
 	takes the form
 	'hh:[mm[:ss]]'
 	and defaults to 02:00.
 	This is the same format as the offset, except that a
 	leading '+' or '-' is not allowed.
       
    
       
    date
    
 	takes one of the following forms:
 	
    
 	  
    Jn (1≤n≤365)
    
 	    origin-1 day number not counting February 29
 	  
    
 	  
    n (0≤n≤365)
    
 	    origin-0 day number counting February 29 if present
 	  
    
 	  
    Mm.n.d
 	    (0[Sunday]≤d≤6[Saturday], 1≤n≤5,
 	    1≤m≤12)
    
 	    for the dth day of week n of
 	    month m of the year, where week 1 is the first
 	    week in which day d appears, and
 	    '5' stands for the last week in which
 	    day d appears (which may be either the 4th or
 	    5th week).
 	    Typically, this is the only useful form; the n
 	    and Jn forms are rarely used.
 	  
    
 	
    
       
    
     
    
 
     
    
     Here is an example POSIX TZ string for New
     Zealand after 2007.
     It says that standard time (NZST) is 12 hours ahead
     of UT, and that daylight saving time
     (NZDT) is observed from September's last Sunday at
     02:00 until April's first Sunday at 03:00:
     
    
 
     
    TZ='NZST-12NZDT,M9.5.0,M4.1.0/3'
    
 
     
    
     This POSIX TZ string is hard to remember, and
     mishandles some timestamps before 2008.
     With this package you can use this instead:
     
    
 
     
    TZ='Pacific/Auckland'
    
   
    • 
   
  • 
     POSIX does not define the DST transitions
     for TZ values like
     "EST5EDT".
     Traditionally the current US DST rules
     were used to interpret such values, but this meant that the
     US DST rules were compiled into each
     program that did time conversion. This meant that when
     US time conversion rules changed (as in the United
     States in 1987), all programs that did time conversion had to be
     recompiled to ensure proper results.
   
    • 
   
  • 
     The TZ environment variable is process-global, which
     makes it hard to write efficient, thread-safe applications that
     need access to multiple timezones.
   
    • 
   
  • 
     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 – without regard to whether the
     user has fiddled the
     TZ environment variable.
     While an administrator can "do everything in UT" to
     get around the problem, doing so is inconvenient and precludes
     handling daylight saving time shifts – as might be required to
     limit phone calls to off-peak hours.
   
    • 
   
  • 
     POSIX provides no convenient and efficient way to determine
     the UT offset and time zone abbreviation of arbitrary
     timestamps, particularly for timezones
     that do not fit into the POSIX model.
   
    • 
   
  • 
     POSIX requires that time_t clock counts exclude leap
     seconds.
   
    • 
   
  • 
     The tz code attempts to support all the
     time_t implementations allowed by POSIX.
     The time_t type represents a nonnegative count of seconds
     since 1970-01-01 00:00:00 UTC, ignoring leap seconds.
     In practice, time_t is usually a signed 64- or 32-bit
     integer; 32-bit signed time_t values stop working after
     2038-01-19 03:14:07 UTC, 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 time_t to be a
     floating-point type, this was not supported by any practical system,
     and POSIX.1-2013 and the tz code both
     require time_t to be an integer type.
   
    • 
 

 
 
Extensions to POSIX in the
 tz code

 
    
   
  • 
     
    
     The TZ environment variable is used in generating
     the name of a file from which time-related information is read
     (or is interpreted à la POSIX); TZ is no longer
     constrained to be a string containing abbreviations
     and numeric data as described above.
     The file's format is TZif,
     a timezone information format that contains binary data; see
-    Internet
+    Internet
     RFC 8536.
     The daylight saving time rules to be used for a
     particular timezone are encoded in the
     TZif file; the format of the file allows US,
     Australian, and other rules to be encoded, and
     allows for situations where more than two time zone
     abbreviations are used.
     
    
     
    
     It was recognized that allowing the TZ environment
     variable to take on values such as 'America/New_York'
     might cause "old" programs (that expect TZ to have a
     certain form) to operate incorrectly; consideration was given to using
     some other environment variable (for example, TIMEZONE)
     to hold the string used to generate the TZif file's name.
     In the end, however, it was decided to continue using
     TZ: it is widely used for time zone purposes;
     separately maintaining both TZ
     and TIMEZONE seemed a nuisance; and systems where
     "new" forms of TZ might cause problems can simply
     use legacy TZ values such as "EST5EDT" which
     can be used by "new" programs as well as by "old" programs that
     assume pre-POSIX TZ values.
     
    
   
    • 
   
  • 
     The code supports platforms with a UT offset member
-    in struct tm, e.g., tm_gmtoff.
-  
    • 
-  
  • 
-    The code supports platforms with a time zone abbreviation member in
-    struct tm, e.g., tm_zone.
+    in struct tm, e.g., tm_gmtoff,
+    or with a time zone abbreviation member in
+    struct tm, e.g., tm_zone. As noted
+    in Austin
+    Group defect 1533, a future version of POSIX is planned to
+    require tm_gmtoff and tm_zone.
   
    • 
   
  • 
     Functions tzalloc, tzfree,
     localtime_rz, and mktime_z for
     more-efficient thread-safe applications that need to use multiple
     timezones.
     The tzalloc and tzfree functions
     allocate and free objects of type timezone_t,
     and localtime_rz and mktime_z are
     like localtime_r and mktime with an
     extra timezone_t argument.
     The functions were inspired by NetBSD.
   
    • 
   
  • 
     Negative time_t values are supported, on systems
     where time_t is signed.
   
    • 
   
  • 
     These functions can account for leap seconds;
     see Leap seconds below.
   
    • 
 

 
 
POSIX features no longer needed

 

 POSIX and ISO C
 define some APIs that are vestigial:
 they are not needed, and are relics of a too-simple model that does
 not suffice to handle many real-world timestamps.
 Although the tz code supports these
 vestigial APIs for backwards compatibility, they should
 be avoided in portable applications.
 The vestigial APIs are:
 

 
    
   
  • 
     The POSIX tzname variable does not suffice and is no
     longer needed.
     To get a timestamp's time zone abbreviation, consult
     the tm_zone member if available; otherwise,
     use strftime's "%Z" conversion
     specification.
   
    • 
   
  • 
     The POSIX daylight and timezone
     variables do not suffice and are no longer needed.
     To get a timestamp's UT offset, consult
     the tm_gmtoff member if available; otherwise,
     subtract values returned by localtime
     and gmtime using the rules of the Gregorian calendar,
     or use strftime's "%z" conversion
     specification if a string like "+0900" suffices.
   
    • 
   
  • 
     The tm_isdst member is almost never needed and most of
     its uses should be discouraged in favor of the abovementioned
     APIs.
     Although it can still be used in arguments to
     mktime to disambiguate timestamps near
-    a DST transition when the clock jumps back, this
+    a DST transition when the clock jumps back on
+    platforms lacking tm_gmtoff, this
     disambiguation does not work when standard time itself jumps back,
     which can occur when a location changes to a time zone with a
     lesser UT offset.
   
    • 
 

 
 
Other portability notes

 
    
   
  • 
     The 7th Edition
     UNIX timezone function is not present in this
     package; it is impossible to reliably map timezone's
     arguments (a "minutes west of GMT" value and a
     "daylight saving time in effect" flag) to a time zone
     abbreviation, and we refuse to guess.
     Programs that in the past used the timezone function
     may now examine localtime(&clock)->tm_zone
     (if TM_ZONE is defined) or
     tzname[localtime(&clock)->tm_isdst]
     (if HAVE_TZNAME is nonzero) to learn the correct time
     zone abbreviation to use.
   
    • 
   
  • 
     The 4.2BSD
     gettimeofday function is not
     used in this package.
     This formerly let users obtain the current UTC offset
     and DST flag, but this functionality was removed in
     later versions of BSD.
   
    • 
   
  • 
     In SVR2, time conversion fails for near-minimum or
     near-maximum time_t values when doing conversions
     for places that do not use UT.
     This package takes care to do these conversions correctly.
     A comment in the source code tells how to get compatibly wrong
     results.
   
    • 
   
  • 
     The functions that are conditionally compiled
     if STD_INSPIRED is defined should, at this point, be
     looked on primarily as food for thought.
     They are not in any sense "standard compatible" – some are
     not, in fact, specified in any standard.
     They do, however, represent responses of various authors to
     standardization proposals.
   
    • 
   
  • 
     Other time conversion proposals, in particular those supported by the
     Time Zone
     Database Parser, offer a wider selection of functions
     that provide capabilities beyond those provided here.
     The absence of such functions from this package is not meant to
     discourage the development, standardization, or use of such
     functions.
     Rather, their absence reflects the decision to make this package
     contain valid extensions to POSIX, to ensure its broad
     acceptability.
     If more powerful time conversion functions can be standardized, so
     much the better.
   
    • 
 

 

 
 

   
Interface stability

 

 The tz code and data supply the following interfaces:
 

 
 
    
   
  • 
     A set of timezone names as per
       "Timezone identifiers" above.
   
    • 
   
  • 
     Library functions described in "Time and date
       functions" above.
   
    • 
   
  • 
     The programs tzselect, zdump,
     and zic, documented in their man pages.
   
    • 
   
  • 
     The format of zic input files, documented in
     the zic man page.
   
    • 
   
  • 
     The format of zic output files, documented in
     the tzfile man page.
   
    • 
   
  • 
     The format of zone table files, documented in zone1970.tab.
   
    • 
   
  • 
     The format of the country code file, documented in iso3166.tab.
   
    • 
   
  • 
     The version number of the code and data, as the first line of
     the text file 'version' in each release.
   
    • 
 

 
 

 Interface changes in a release attempt to preserve compatibility with
 recent releases.
 For example, tz data files typically do not
 rely on recently-added zic features, so that users can
 run older zic versions to process newer data files.
 Downloading
 the tz database describes how releases
 are tagged and distributed.
 

 
 

 Interfaces not listed above are less stable.
 For example, users should not rely on particular UT
 offsets or abbreviations for timestamps, as data entries are often
 based on guesswork and these guesses may be corrected or improved.
 

 
 

 Timezone boundaries are not part of the stable interface.
 For example, even though the Asia/Bangkok timezone
 currently includes Chang Mai, Hanoi, and Phnom Penh, this is not part
 of the stable interface and the timezone can split at any time.
 If a calendar application records a future event in some location other
 than Bangkok by putting "Asia/Bangkok" in the event's record,
 the application should be robust in the presence of timezone splits
 between now and the future time.
 

 

 
 

   
Leap seconds

 

 The tz code and data can account for leap seconds,
 thanks to code contributed by Bradley White.
 However, the leap second support of this package is rarely used directly
 because POSIX requires leap seconds to be excluded and many
 software packages would mishandle leap seconds if they were present.
 Instead, leap seconds are more commonly handled by occasionally adjusting
 the operating system kernel clock as described in
 Precision timekeeping,
 and this package by default installs a leapseconds file
 commonly used by
-NTP
+NTP
 software that adjusts the kernel clock.
 However, kernel-clock twiddling approximates UTC only roughly,
 and systems needing more-precise UTC can use this package's leap
 second support directly.
 

 
 

 The directly-supported mechanism assumes that time_t
 counts of seconds since the POSIX epoch normally include leap seconds,
 as opposed to POSIX time_t counts which exclude leap seconds.
 This modified timescale is converted to UTC
 at the same point that time zone and DST
 adjustments are applied –
 namely, at calls to localtime and analogous functions –
 and the process is driven by leap second information
 stored in alternate versions of the TZif files.
 Because a leap second adjustment may be needed even
 if no time zone correction is desired,
 calls to gmtime-like functions
 also need to consult a TZif file,
 conventionally named Etc/UTC
 (GMT in previous versions),
 to see whether leap second corrections are needed.
 To convert an application's time_t timestamps to or from
 POSIX time_t timestamps (for use when, say,
 embedding or interpreting timestamps in portable
 tar
 files),
 the application can call the utility functions
 time2posix and posix2time
 included with this package.
 

 
 

 If the POSIX-compatible TZif file set is installed
 in a directory whose basename is zoneinfo, the
 leap-second-aware file set is by default installed in a separate
 directory zoneinfo-leaps.
 Although each process can have its own time zone by setting
 its TZ environment variable, there is no support for some
 processes being leap-second aware while other processes are
 POSIX-compatible; the leap-second choice is system-wide.
 So if you configure your kernel to count leap seconds, you should also
 discard zoneinfo and rename zoneinfo-leaps
 to zoneinfo.
 Alternatively, you can install just one set of TZif files
 in the first place; see the REDO variable in this package's
 makefile.
 

 

 
 

   
Calendrical issues

 

 Calendrical issues are a bit out of scope for a time zone database,
 but they indicate the sort of problems that we would run into if we
 extended the time zone database further into the past.
 An excellent resource in this area is Edward M. Reingold
 and Nachum Dershowitz, Calendrical
 Calculations: The Ultimate Edition, Cambridge University Press (2018).
 Other information and sources are given in the file 'calendars'
 in the tz distribution.
 They sometimes disagree.
 

 

 
 

   
Time and time zones on other planets

 

 Some people's work schedules have used
 Mars time.
 Jet Propulsion Laboratory (JPL) coordinators kept Mars time on
 and off during the
 Mars
 Pathfinder mission (1997).
 Some of their family members also adapted to Mars time.
 Dozens of special Mars watches were built for JPL workers who kept
 Mars time during the
 Mars
 Exploration Rovers (MER) mission (2004–2018).
 These timepieces looked like normal Seikos and Citizens but were adjusted
 to use Mars seconds rather than terrestrial seconds, although
 unfortunately the adjusted watches were unreliable and appear to have
 had only limited use.
 

 
 

 A Mars solar day is called a "sol" and has a mean period equal to
 about 24 hours 39 minutes 35.244 seconds in terrestrial time.
 It is divided into a conventional 24-hour clock, so each Mars second
 equals about 1.02749125 terrestrial seconds.
 (One MER worker noted, "If I am working Mars hours, and Mars hours are
 2.5% more than Earth hours, shouldn't I get an extra 2.5% pay raise?")
 

 
 

 The prime
 meridian of Mars goes through the center of the crater
 Airy-0, named in
 honor of the British astronomer who built the Greenwich telescope that
 defines Earth's prime meridian.
 Mean solar time on the Mars prime meridian is
 called Mars Coordinated Time (MTC).
 

 
 

 Each landed mission on Mars has adopted a different reference for
 solar timekeeping, so there is no real standard for Mars time zones.
 For example, the MER mission defined two time zones "Local
 Solar Time A" and "Local Solar Time B" for its two missions, each zone
 designed so that its time equals local true solar time at
 approximately the middle of the nominal mission.
 The A and B zones differ enough so that an MER worker assigned to
 the A zone might suffer "Mars lag" when switching to work in the B zone.
 Such a "time zone" is not particularly suited for any application
 other than the mission itself.
 

 
 

 Many calendars have been proposed for Mars, but none have achieved
 wide acceptance.
 Astronomers often use Mars Sol Date (MSD) which is a
 sequential count of Mars solar days elapsed since about 1873-12-29
 12:00 GMT.
 

 
 

 In our solar system, Mars is the planet with time and calendar most
 like Earth's.
 On other planets, Sun-based time and calendars would work quite
 differently.
 For example, although Mercury's
 sidereal
 rotation period is 58.646 Earth days, Mercury revolves around the
 Sun so rapidly that an observer on Mercury's equator would see a
 sunrise only every 175.97 Earth days, i.e., a Mercury year is 0.5 of a
 Mercury day.
 Venus is more complicated, partly because its rotation is slightly
 retrograde:
 its year is 1.92 of its days.
 Gas giants like Jupiter are trickier still, as their polar and
 equatorial regions rotate at different rates, so that the length of a
 day depends on latitude.
 This effect is most pronounced on Neptune, where the day is about 12
 hours at the poles and 18 hours at the equator.
 

 
 

 Although the tz database does not support
 time on other planets, it is documented here in the hopes that support
 will be added eventually.
 

 
 

 Sources for time on other planets:
 

 
 
 

 
 

   

   This file is in the public domain, so clarified as of 2009-05-17 by
   Arthur David Olson.
 

 
 
diff --git a/contrib/tzdata/version b/contrib/tzdata/version
index 7c9f279dc3c4..9fcedf24a675 100644
--- a/contrib/tzdata/version
+++ b/contrib/tzdata/version
@@ -1 +1 @@
-2022b
+2022c
diff --git a/contrib/tzdata/ziguard.awk b/contrib/tzdata/ziguard.awk
index 0728baa51343..0556cc4a9dbb 100644
--- a/contrib/tzdata/ziguard.awk
+++ b/contrib/tzdata/ziguard.awk
@@ -1,313 +1,316 @@
 # Convert tzdata source into vanguard or rearguard form.
 
 # Contributed by Paul Eggert.  This file is in the public domain.
 
 # This is not a general-purpose converter; it is designed for current tzdata.
 # It just converts from current source to main, vanguard, and rearguard forms.
 # Although it might be nice for it to be idempotent, or to be useful
 # for converting back and forth between vanguard and rearguard formats,
 # it does not do these nonessential tasks now.
 #
 # Although main and vanguard forms are currently equivalent,
 # this need not always be the case.  When the two forms differ,
 # this script can convert either from main to vanguard form (needed then),
 # or from vanguard to main form (this conversion would be needed later,
 # after main became rearguard and vanguard became main).
 # There is no need to convert rearguard to other forms.
 #
 # When converting to vanguard form, the output can use negative SAVE
 # values.
 #
 # When converting to rearguard form, the output uses only nonnegative
 # SAVE values.  The idea is for the output data to simulate the behavior
 # of the input data as best it can within the constraints of the
 # rearguard format.
 
 # Given a FIELD like "-0:30", return a minute count like -30.
 function get_minutes(field, \
 		     sign, hours, minutes)
 {
   sign = field ~ /^-/ ? -1 : 1
   hours = +field
   if (field ~ /:/) {
     minutes = field
     sub(/[^:]*:/, "", minutes)
   }
   return 60 * hours + sign * minutes
 }
 
 # Given an OFFSET, which is a minute count like 300 or 330,
 # return a %z-style abbreviation like "+05" or "+0530".
 function offset_abbr(offset, \
 		     hours, minutes, sign)
 {
   hours = int(offset / 60)
   minutes = offset % 60
   if (minutes) {
     return sprintf("%+.4d", hours * 100 + minutes);
   } else {
     return sprintf("%+.2d", hours)
   }
 }
 
 # Round TIMESTAMP (a +-hh:mm:ss.dddd string) to the nearest second.
 function round_to_second(timestamp, \
 			 hh, mm, ss, seconds, dot_dddd, subseconds)
 {
   dot_dddd = timestamp
   if (!sub(/^[+-]?[0-9]+:[0-9]+:[0-9]+\./, ".", dot_dddd))
     return timestamp
   hh = mm = ss = timestamp
   sub(/^[-+]?[0-9]+:[0-9]+:/, "", ss)
   sub(/^[-+]?[0-9]+:/, "", mm)
   sub(/^[-+]?/, "", hh)
   seconds = 3600 * hh + 60 * mm + ss
   subseconds = +dot_dddd
   seconds += 0.5 < subseconds || ((subseconds == 0.5) && (seconds % 2));
   return sprintf("%s%d:%.2d:%.2d", timestamp ~ /^-/ ? "-" : "", \
 		 seconds / 3600, seconds / 60 % 60, seconds % 60)
 }
 
 BEGIN {
   dataform_type["vanguard"] = 1
   dataform_type["main"] = 1
   dataform_type["rearguard"] = 1
 
   if (PACKRATLIST) {
     while (getline =8 25:00"
   # to "Sun>=9 1:00", to cater to zic before 2007 and to older Java.
-  if (/^Rule/ && $2 == "Japan") {
+  if ($0 ~ /^Rule/ && $2 == "Japan") {
     if (DATAFORM == "rearguard") {
       if ($7 == "Sat>=8" && $8 == "25:00") {
 	sub(/Sat>=8/, "Sun>=9")
 	sub(/25:00/, " 1:00")
       }
     } else {
       if ($7 == "Sun>=9" && $8 == "1:00") {
 	sub(/Sun>=9/, "Sat>=8")
 	sub(/ 1:00/, "25:00")
       }
     }
   }
 
   # In rearguard form, change the Morocco lines with negative SAVE values
   # to use positive SAVE values.
   if ($2 == "Morocco") {
-    if (/^Rule/) {
+    if ($0 ~ /^Rule/) {
       if ($4 ~ /^201[78]$/ && $6 == "Oct") {
 	if (DATAFORM == "rearguard") {
 	  sub(/\t2018\t/, "\t2017\t")
 	} else {
 	  sub(/\t2017\t/, "\t2018\t")
 	}
       }
 
       if (2019 <= $3) {
 	if ($8 == "2:00") {
 	  if (DATAFORM == "rearguard") {
 	    sub(/\t0\t/, "\t1:00\t")
 	  } else {
 	    sub(/\t1:00\t/, "\t0\t")
 	  }
 	} else {
 	  if (DATAFORM == "rearguard") {
 	    sub(/\t-1:00\t/, "\t0\t")
 	  } else {
 	    sub(/\t0\t/, "\t-1:00\t")
 	  }
 	}
       }
     }
     if ($1 ~ /^[+0-9-]/ && NF == 3) {
       if (DATAFORM == "rearguard") {
 	sub(/1:00\tMorocco/, "0:00\tMorocco")
 	sub(/\t\+01\/\+00$/, "\t+00/+01")
       } else {
 	sub(/0:00\tMorocco/, "1:00\tMorocco")
 	sub(/\t\+00\/+01$/, "\t+01/+00")
       }
     }
   }
 }
 
 /^Zone/ {
   packrat_ignored = FILENAME == PACKRATDATA && PACKRATLIST && !packratlist[$2];
 }
-packrat_ignored && !/^Rule/ {
-  sub(/^/, "#")
+{
+  if (packrat_ignored && $0 !~ /^Rule/) {
+    sub(/^/, "#")
+  }
 }
 
 # If a Link line is followed by a Link or Zone line for the same data, comment
 # out the Link line.  This can happen if backzone overrides a Link
 # with a Zone or a different Link.
 /^Zone/ {
   sub(/^Link/, "#Link", line[linkline[$2]])
 }
 /^Link/ {
   sub(/^Link/, "#Link", line[linkline[$3]])
   linkline[$3] = NR
 }
 
 { line[NR] = $0 }
 
 END {
   for (i = 1; i <= NR; i++)
     print line[i]
 }
diff --git a/contrib/tzdata/zone1970.tab b/contrib/tzdata/zone1970.tab
index ffab5ab299f2..756cdf04d972 100644
--- a/contrib/tzdata/zone1970.tab
+++ b/contrib/tzdata/zone1970.tab
@@ -1,354 +1,378 @@
 # tzdb timezone descriptions
 #
 # This file is in the public domain.
 #
 # From Paul Eggert (2018-06-27):
 # This file contains a table where each row stands for a timezone where
 # civil timestamps have agreed since 1970.  Columns are separated by
 # a single tab.  Lines beginning with '#' are comments.  All text uses
 # UTF-8 encoding.  The columns of the table are as follows:
 #
 # 1.  The countries that overlap the timezone, as a comma-separated list
 #     of ISO 3166 2-character country codes.
 #     See the file '/usr/share/misc/iso3166'.
 # 2.  Latitude and longitude of the timezone's principal location
 #     in ISO 6709 sign-degrees-minutes-seconds format,
 #     either ±DDMM±DDDMM or ±DDMMSS±DDDMMSS,
 #     first latitude (+ is north), then longitude (+ is east).
 # 3.  Timezone name used in value of TZ environment variable.
 #     Please see the theory.html file for how these names are chosen.
 #     If multiple timezones overlap a country, each has a row in the
 #     table, with each column 1 containing the country code.
 # 4.  Comments; present if and only if a country has multiple timezones.
 #
 # If a timezone covers multiple countries, the most-populous city is used,
 # and that country is listed first in column 1; any other countries
 # are listed alphabetically by country code.  The table is sorted
 # first by country code, then (if possible) by an order within the
 # country that (1) makes some geographical sense, and (2) puts the
 # most populous timezones first, where that does not contradict (1).
 #
 # This table is intended as an aid for users, to help them select timezones
 # appropriate for their practical needs.  It is not intended to take or
 # endorse any position on legal or territorial claims.
 #
 #country-
 #codes	coordinates	TZ	comments
 AD	+4230+00131	Europe/Andorra
 AE,OM,RE,SC,TF	+2518+05518	Asia/Dubai	UAE, Oman, Réunion, Seychelles, Crozet, Scattered Is
 AF	+3431+06912	Asia/Kabul
 AL	+4120+01950	Europe/Tirane
 AM	+4011+04430	Asia/Yerevan
 AQ	-6617+11031	Antarctica/Casey	Casey
 AQ	-6835+07758	Antarctica/Davis	Davis
 AQ	-6736+06253	Antarctica/Mawson	Mawson
 AQ	-6448-06406	Antarctica/Palmer	Palmer
 AQ	-6734-06808	Antarctica/Rothera	Rothera
 AQ	-720041+0023206	Antarctica/Troll	Troll
 AR	-3436-05827	America/Argentina/Buenos_Aires	Buenos Aires (BA, CF)
 AR	-3124-06411	America/Argentina/Cordoba	Argentina (most areas: CB, CC, CN, ER, FM, MN, SE, SF)
 AR	-2447-06525	America/Argentina/Salta	Salta (SA, LP, NQ, RN)
 AR	-2411-06518	America/Argentina/Jujuy	Jujuy (JY)
 AR	-2649-06513	America/Argentina/Tucuman	Tucumán (TM)
 AR	-2828-06547	America/Argentina/Catamarca	Catamarca (CT); Chubut (CH)
 AR	-2926-06651	America/Argentina/La_Rioja	La Rioja (LR)
 AR	-3132-06831	America/Argentina/San_Juan	San Juan (SJ)
 AR	-3253-06849	America/Argentina/Mendoza	Mendoza (MZ)
 AR	-3319-06621	America/Argentina/San_Luis	San Luis (SL)
 AR	-5138-06913	America/Argentina/Rio_Gallegos	Santa Cruz (SC)
 AR	-5448-06818	America/Argentina/Ushuaia	Tierra del Fuego (TF)
 AS,UM	-1416-17042	Pacific/Pago_Pago	Samoa, Midway
 AT	+4813+01620	Europe/Vienna
 AU	-3133+15905	Australia/Lord_Howe	Lord Howe Island
 AU	-5430+15857	Antarctica/Macquarie	Macquarie Island
 AU	-4253+14719	Australia/Hobart	Tasmania
 AU	-3749+14458	Australia/Melbourne	Victoria
 AU	-3352+15113	Australia/Sydney	New South Wales (most areas)
 AU	-3157+14127	Australia/Broken_Hill	New South Wales (Yancowinna)
 AU	-2728+15302	Australia/Brisbane	Queensland (most areas)
 AU	-2016+14900	Australia/Lindeman	Queensland (Whitsunday Islands)
 AU	-3455+13835	Australia/Adelaide	South Australia
 AU	-1228+13050	Australia/Darwin	Northern Territory
 AU	-3157+11551	Australia/Perth	Western Australia (most areas)
 AU	-3143+12852	Australia/Eucla	Western Australia (Eucla)
 AZ	+4023+04951	Asia/Baku
 BB	+1306-05937	America/Barbados
 BD	+2343+09025	Asia/Dhaka
 BE,LU,NL	+5050+00420	Europe/Brussels
 BG	+4241+02319	Europe/Sofia
 BM	+3217-06446	Atlantic/Bermuda
 BO	-1630-06809	America/La_Paz
 BR	-0351-03225	America/Noronha	Atlantic islands
 BR	-0127-04829	America/Belem	Pará (east); Amapá
 BR	-0343-03830	America/Fortaleza	Brazil (northeast: MA, PI, CE, RN, PB)
 BR	-0803-03454	America/Recife	Pernambuco
 BR	-0712-04812	America/Araguaina	Tocantins
 BR	-0940-03543	America/Maceio	Alagoas, Sergipe
 BR	-1259-03831	America/Bahia	Bahia
 BR	-2332-04637	America/Sao_Paulo	Brazil (southeast: GO, DF, MG, ES, RJ, SP, PR, SC, RS)
 BR	-2027-05437	America/Campo_Grande	Mato Grosso do Sul
 BR	-1535-05605	America/Cuiaba	Mato Grosso
 BR	-0226-05452	America/Santarem	Pará (west)
 BR	-0846-06354	America/Porto_Velho	Rondônia
 BR	+0249-06040	America/Boa_Vista	Roraima
 BR	-0308-06001	America/Manaus	Amazonas (east)
 BR	-0640-06952	America/Eirunepe	Amazonas (west)
 BR	-0958-06748	America/Rio_Branco	Acre
 BT	+2728+08939	Asia/Thimphu
 BY	+5354+02734	Europe/Minsk
 BZ	+1730-08812	America/Belize
 CA	+4734-05243	America/St_Johns	Newfoundland; Labrador (southeast)
 CA	+4439-06336	America/Halifax	Atlantic - NS (most areas); PE
 CA	+4612-05957	America/Glace_Bay	Atlantic - NS (Cape Breton)
 CA	+4606-06447	America/Moncton	Atlantic - New Brunswick
 CA	+5320-06025	America/Goose_Bay	Atlantic - Labrador (most areas)
 CA,BS	+4339-07923	America/Toronto	Eastern - ON, QC (most areas), Bahamas
 CA	+4901-08816	America/Nipigon	Eastern - ON, QC (no DST 1967-73)
 CA	+4823-08915	America/Thunder_Bay	Eastern - ON (Thunder Bay)
 CA	+6344-06828	America/Iqaluit	Eastern - NU (most east areas)
 CA	+6608-06544	America/Pangnirtung	Eastern - NU (Pangnirtung)
 CA	+4953-09709	America/Winnipeg	Central - ON (west); Manitoba
 CA	+4843-09434	America/Rainy_River	Central - ON (Rainy R, Ft Frances)
 CA	+744144-0944945	America/Resolute	Central - NU (Resolute)
 CA	+624900-0920459	America/Rankin_Inlet	Central - NU (central)
 CA	+5024-10439	America/Regina	CST - SK (most areas)
 CA	+5017-10750	America/Swift_Current	CST - SK (midwest)
 CA	+5333-11328	America/Edmonton	Mountain - AB; BC (E); SK (W)
 CA	+690650-1050310	America/Cambridge_Bay	Mountain - NU (west)
 CA	+6227-11421	America/Yellowknife	Mountain - NT (central)
 CA	+682059-1334300	America/Inuvik	Mountain - NT (west)
 CA	+5546-12014	America/Dawson_Creek	MST - BC (Dawson Cr, Ft St John)
 CA	+5848-12242	America/Fort_Nelson	MST - BC (Ft Nelson)
 CA	+6043-13503	America/Whitehorse	MST - Yukon (east)
 CA	+6404-13925	America/Dawson	MST - Yukon (west)
 CA	+4916-12307	America/Vancouver	Pacific - BC (most areas)
 CH,DE,LI	+4723+00832	Europe/Zurich	Swiss time
 CI,BF,GH,GM,GN,IS,ML,MR,SH,SL,SN,TG	+0519-00402	Africa/Abidjan
 CK	-2114-15946	Pacific/Rarotonga
 CL	-3327-07040	America/Santiago	Chile (most areas)
 CL	-5309-07055	America/Punta_Arenas	Region of Magallanes
 CL	-2709-10926	Pacific/Easter	Easter Island
 CN	+3114+12128	Asia/Shanghai	Beijing Time
 CN,AQ	+4348+08735	Asia/Urumqi	Xinjiang Time, Vostok
 CO	+0436-07405	America/Bogota
 CR	+0956-08405	America/Costa_Rica
 CU	+2308-08222	America/Havana
 CV	+1455-02331	Atlantic/Cape_Verde
 CY	+3510+03322	Asia/Nicosia	Cyprus (most areas)
 CY	+3507+03357	Asia/Famagusta	Northern Cyprus
 CZ,SK	+5005+01426	Europe/Prague
 DE,DK,NO,SE,SJ	+5230+01322	Europe/Berlin	Germany (most areas), Scandinavia
 DO	+1828-06954	America/Santo_Domingo
 DZ	+3647+00303	Africa/Algiers
 EC	-0210-07950	America/Guayaquil	Ecuador (mainland)
 EC	-0054-08936	Pacific/Galapagos	Galápagos Islands
 EE	+5925+02445	Europe/Tallinn
 EG	+3003+03115	Africa/Cairo
 EH	+2709-01312	Africa/El_Aaiun
 ES	+4024-00341	Europe/Madrid	Spain (mainland)
 ES	+3553-00519	Africa/Ceuta	Ceuta, Melilla
 ES	+2806-01524	Atlantic/Canary	Canary Islands
 FI,AX	+6010+02458	Europe/Helsinki
 FJ	-1808+17825	Pacific/Fiji
 FK	-5142-05751	Atlantic/Stanley
 FM	+0519+16259	Pacific/Kosrae	Kosrae
 FO	+6201-00646	Atlantic/Faroe
 FR,MC	+4852+00220	Europe/Paris
 GB,GG,IM,JE	+513030-0000731	Europe/London
 GE	+4143+04449	Asia/Tbilisi
 GF	+0456-05220	America/Cayenne
 GI	+3608-00521	Europe/Gibraltar
 GL	+6411-05144	America/Nuuk	Greenland (most areas)
 GL	+7646-01840	America/Danmarkshavn	National Park (east coast)
 GL	+7029-02158	America/Scoresbysund	Scoresbysund/Ittoqqortoormiit
 GL	+7634-06847	America/Thule	Thule/Pituffik
 GR	+3758+02343	Europe/Athens
 GS	-5416-03632	Atlantic/South_Georgia
 GT	+1438-09031	America/Guatemala
 GU,MP	+1328+14445	Pacific/Guam
 GW	+1151-01535	Africa/Bissau
 GY	+0648-05810	America/Guyana
 HK	+2217+11409	Asia/Hong_Kong
 HN	+1406-08713	America/Tegucigalpa
 HT	+1832-07220	America/Port-au-Prince
 HU	+4730+01905	Europe/Budapest
 ID	-0610+10648	Asia/Jakarta	Java, Sumatra
 ID	-0002+10920	Asia/Pontianak	Borneo (west, central)
 ID	-0507+11924	Asia/Makassar	Borneo (east, south); Sulawesi/Celebes, Bali, Nusa Tengarra; Timor (west)
 ID	-0232+14042	Asia/Jayapura	New Guinea (West Papua / Irian Jaya); Malukus/Moluccas
 IE	+5320-00615	Europe/Dublin
 IL	+314650+0351326	Asia/Jerusalem
 IN	+2232+08822	Asia/Kolkata
 IO	-0720+07225	Indian/Chagos
 IQ	+3321+04425	Asia/Baghdad
 IR	+3540+05126	Asia/Tehran
 IT,SM,VA	+4154+01229	Europe/Rome
 JM	+175805-0764736	America/Jamaica
 JO	+3157+03556	Asia/Amman
 JP	+353916+1394441	Asia/Tokyo
 KE,DJ,ER,ET,KM,MG,SO,TZ,UG,YT	-0117+03649	Africa/Nairobi
 KG	+4254+07436	Asia/Bishkek
 KI,MH,TV,UM,WF	+0125+17300	Pacific/Tarawa	Gilberts, Marshalls, Tuvalu, Wallis & Futuna, Wake
 KI	-0247-17143	Pacific/Kanton	Phoenix Islands
 KI	+0152-15720	Pacific/Kiritimati	Line Islands
 KP	+3901+12545	Asia/Pyongyang
 KR	+3733+12658	Asia/Seoul
 KZ	+4315+07657	Asia/Almaty	Kazakhstan (most areas)
 KZ	+4448+06528	Asia/Qyzylorda	Qyzylorda/Kyzylorda/Kzyl-Orda
 KZ	+5312+06337	Asia/Qostanay	Qostanay/Kostanay/Kustanay
 KZ	+5017+05710	Asia/Aqtobe	Aqtöbe/Aktobe
 KZ	+4431+05016	Asia/Aqtau	Mangghystaū/Mankistau
 KZ	+4707+05156	Asia/Atyrau	Atyraū/Atirau/Gur'yev
 KZ	+5113+05121	Asia/Oral	West Kazakhstan
 LB	+3353+03530	Asia/Beirut
 LK	+0656+07951	Asia/Colombo
 LR	+0618-01047	Africa/Monrovia
 LT	+5441+02519	Europe/Vilnius
 LV	+5657+02406	Europe/Riga
 LY	+3254+01311	Africa/Tripoli
 MA	+3339-00735	Africa/Casablanca
 MD	+4700+02850	Europe/Chisinau
 MH	+0905+16720	Pacific/Kwajalein	Kwajalein
 MM,CC	+1647+09610	Asia/Yangon
 MN	+4755+10653	Asia/Ulaanbaatar	Mongolia (most areas)
 MN	+4801+09139	Asia/Hovd	Bayan-Ölgii, Govi-Altai, Hovd, Uvs, Zavkhan
 MN	+4804+11430	Asia/Choibalsan	Dornod, Sükhbaatar
 MO	+221150+1133230	Asia/Macau
 MQ	+1436-06105	America/Martinique
 MT	+3554+01431	Europe/Malta
 MU	-2010+05730	Indian/Mauritius
 MV,TF	+0410+07330	Indian/Maldives	Maldives, Kerguelen, St Paul I, Amsterdam I
 MX	+1924-09909	America/Mexico_City	Central Time
 MX	+2105-08646	America/Cancun	Eastern Standard Time - Quintana Roo
 MX	+2058-08937	America/Merida	Central Time - Campeche, Yucatán
 MX	+2540-10019	America/Monterrey	Central Time - Durango; Coahuila, Nuevo León, Tamaulipas (most areas)
 MX	+2550-09730	America/Matamoros	Central Time US - Coahuila, Nuevo León, Tamaulipas (US border)
 MX	+2313-10625	America/Mazatlan	Mountain Time - Baja California Sur, Nayarit, Sinaloa
 MX	+2838-10605	America/Chihuahua	Mountain Time - Chihuahua (most areas)
 MX	+2934-10425	America/Ojinaga	Mountain Time US - Chihuahua (US border)
 MX	+2904-11058	America/Hermosillo	Mountain Standard Time - Sonora
 MX	+3232-11701	America/Tijuana	Pacific Time US - Baja California
 MX	+2048-10515	America/Bahia_Banderas	Central Time - Bahía de Banderas
 MY,BN	+0133+11020	Asia/Kuching	Sabah, Sarawak, Brunei
 MZ,BI,BW,CD,MW,RW,ZM,ZW	-2558+03235	Africa/Maputo	Central Africa Time
 NA	-2234+01706	Africa/Windhoek
 NC	-2216+16627	Pacific/Noumea
 NF	-2903+16758	Pacific/Norfolk
 NG,AO,BJ,CD,CF,CG,CM,GA,GQ,NE	+0627+00324	Africa/Lagos	West Africa Time
 NI	+1209-08617	America/Managua
 NP	+2743+08519	Asia/Kathmandu
 NR	-0031+16655	Pacific/Nauru
 NU	-1901-16955	Pacific/Niue
 NZ,AQ	-3652+17446	Pacific/Auckland	New Zealand time
 NZ	-4357-17633	Pacific/Chatham	Chatham Islands
 PA,CA,KY	+0858-07932	America/Panama	EST - Panama, Cayman, ON (Atikokan), NU (Coral H)
 PE	-1203-07703	America/Lima
 PF	-1732-14934	Pacific/Tahiti	Society Islands
 PF	-0900-13930	Pacific/Marquesas	Marquesas Islands
 PF	-2308-13457	Pacific/Gambier	Gambier Islands
 PG,AQ,FM	-0930+14710	Pacific/Port_Moresby	Papua New Guinea (most areas), Chuuk, Yap, Dumont d'Urville
 PG	-0613+15534	Pacific/Bougainville	Bougainville
 PH	+1435+12100	Asia/Manila
 PK	+2452+06703	Asia/Karachi
 PL	+5215+02100	Europe/Warsaw
 PM	+4703-05620	America/Miquelon
 PN	-2504-13005	Pacific/Pitcairn
 PR,AG,CA,AI,AW,BL,BQ,CW,DM,GD,GP,KN,LC,MF,MS,SX,TT,VC,VG,VI	+182806-0660622	America/Puerto_Rico	AST
 PS	+3130+03428	Asia/Gaza	Gaza Strip
 PS	+313200+0350542	Asia/Hebron	West Bank
 PT	+3843-00908	Europe/Lisbon	Portugal (mainland)
 PT	+3238-01654	Atlantic/Madeira	Madeira Islands
 PT	+3744-02540	Atlantic/Azores	Azores
 PW	+0720+13429	Pacific/Palau
 PY	-2516-05740	America/Asuncion
 QA,BH	+2517+05132	Asia/Qatar
 RO	+4426+02606	Europe/Bucharest
 RS,BA,HR,ME,MK,SI	+4450+02030	Europe/Belgrade
 RU	+5443+02030	Europe/Kaliningrad	MSK-01 - Kaliningrad
 RU	+554521+0373704	Europe/Moscow	MSK+00 - Moscow area
 # Mention RU and UA alphabetically.  See "territorial claims" above.
 RU,UA	+4457+03406	Europe/Simferopol	Crimea
 RU	+5836+04939	Europe/Kirov	MSK+00 - Kirov
 RU	+4844+04425	Europe/Volgograd	MSK+00 - Volgograd
 RU	+4621+04803	Europe/Astrakhan	MSK+01 - Astrakhan
 RU	+5134+04602	Europe/Saratov	MSK+01 - Saratov
 RU	+5420+04824	Europe/Ulyanovsk	MSK+01 - Ulyanovsk
 RU	+5312+05009	Europe/Samara	MSK+01 - Samara, Udmurtia
 RU	+5651+06036	Asia/Yekaterinburg	MSK+02 - Urals
 RU	+5500+07324	Asia/Omsk	MSK+03 - Omsk
 RU	+5502+08255	Asia/Novosibirsk	MSK+04 - Novosibirsk
 RU	+5322+08345	Asia/Barnaul	MSK+04 - Altai
 RU	+5630+08458	Asia/Tomsk	MSK+04 - Tomsk
 RU	+5345+08707	Asia/Novokuznetsk	MSK+04 - Kemerovo
 RU	+5601+09250	Asia/Krasnoyarsk	MSK+04 - Krasnoyarsk area
 RU	+5216+10420	Asia/Irkutsk	MSK+05 - Irkutsk, Buryatia
 RU	+5203+11328	Asia/Chita	MSK+06 - Zabaykalsky
 RU	+6200+12940	Asia/Yakutsk	MSK+06 - Lena River
 RU	+623923+1353314	Asia/Khandyga	MSK+06 - Tomponsky, Ust-Maysky
 RU	+4310+13156	Asia/Vladivostok	MSK+07 - Amur River
 RU	+643337+1431336	Asia/Ust-Nera	MSK+07 - Oymyakonsky
 RU	+5934+15048	Asia/Magadan	MSK+08 - Magadan
 RU	+4658+14242	Asia/Sakhalin	MSK+08 - Sakhalin Island
 RU	+6728+15343	Asia/Srednekolymsk	MSK+08 - Sakha (E); North Kuril Is
 RU	+5301+15839	Asia/Kamchatka	MSK+09 - Kamchatka
 RU	+6445+17729	Asia/Anadyr	MSK+09 - Bering Sea
 SA,AQ,KW,YE	+2438+04643	Asia/Riyadh	Arabia, Syowa
 SB,FM	-0932+16012	Pacific/Guadalcanal	Solomons, Pohnpei
 SD	+1536+03232	Africa/Khartoum
 SG,MY	+0117+10351	Asia/Singapore	Singapore, peninsular Malaysia
 SR	+0550-05510	America/Paramaribo
 SS	+0451+03137	Africa/Juba
 ST	+0020+00644	Africa/Sao_Tome
 SV	+1342-08912	America/El_Salvador
 SY	+3330+03618	Asia/Damascus
 TC	+2128-07108	America/Grand_Turk
 TD	+1207+01503	Africa/Ndjamena
 TH,CX,KH,LA,VN	+1345+10031	Asia/Bangkok	Indochina (most areas)
 TJ	+3835+06848	Asia/Dushanbe
 TK	-0922-17114	Pacific/Fakaofo
 TL	-0833+12535	Asia/Dili
 TM	+3757+05823	Asia/Ashgabat
 TN	+3648+01011	Africa/Tunis
 TO	-210800-1751200	Pacific/Tongatapu
 TR	+4101+02858	Europe/Istanbul
 TW	+2503+12130	Asia/Taipei
 UA	+5026+03031	Europe/Kyiv	Ukraine (most areas)
 UA	+4837+02218	Europe/Uzhgorod	Transcarpathia
 UA	+4750+03510	Europe/Zaporozhye	Zaporozhye and east Lugansk
 US	+404251-0740023	America/New_York	Eastern (most areas)
 US	+421953-0830245	America/Detroit	Eastern - MI (most areas)
 US	+381515-0854534	America/Kentucky/Louisville	Eastern - KY (Louisville area)
 US	+364947-0845057	America/Kentucky/Monticello	Eastern - KY (Wayne)
 US	+394606-0860929	America/Indiana/Indianapolis	Eastern - IN (most areas)
 US	+384038-0873143	America/Indiana/Vincennes	Eastern - IN (Da, Du, K, Mn)
 US	+410305-0863611	America/Indiana/Winamac	Eastern - IN (Pulaski)
 US	+382232-0862041	America/Indiana/Marengo	Eastern - IN (Crawford)
 US	+382931-0871643	America/Indiana/Petersburg	Eastern - IN (Pike)
 US	+384452-0850402	America/Indiana/Vevay	Eastern - IN (Switzerland)
 US	+415100-0873900	America/Chicago	Central (most areas)
 US	+375711-0864541	America/Indiana/Tell_City	Central - IN (Perry)
 US	+411745-0863730	America/Indiana/Knox	Central - IN (Starke)
 US	+450628-0873651	America/Menominee	Central - MI (Wisconsin border)
 US	+470659-1011757	America/North_Dakota/Center	Central - ND (Oliver)
 US	+465042-1012439	America/North_Dakota/New_Salem	Central - ND (Morton rural)
 US	+471551-1014640	America/North_Dakota/Beulah	Central - ND (Mercer)
 US	+394421-1045903	America/Denver	Mountain (most areas)
 US	+433649-1161209	America/Boise	Mountain - ID (south); OR (east)
 US,CA	+332654-1120424	America/Phoenix	MST - Arizona (except Navajo), Creston BC
 US	+340308-1181434	America/Los_Angeles	Pacific
 US	+611305-1495401	America/Anchorage	Alaska (most areas)
 US	+581807-1342511	America/Juneau	Alaska - Juneau area
 US	+571035-1351807	America/Sitka	Alaska - Sitka area
 US	+550737-1313435	America/Metlakatla	Alaska - Annette Island
 US	+593249-1394338	America/Yakutat	Alaska - Yakutat
 US	+643004-1652423	America/Nome	Alaska (west)
 US	+515248-1763929	America/Adak	Aleutian Islands
 US,UM	+211825-1575130	Pacific/Honolulu	Hawaii
 UY	-345433-0561245	America/Montevideo
 UZ	+3940+06648	Asia/Samarkand	Uzbekistan (west)
 UZ	+4120+06918	Asia/Tashkent	Uzbekistan (east)
 VE	+1030-06656	America/Caracas
 VN	+1045+10640	Asia/Ho_Chi_Minh	Vietnam (south)
 VU	-1740+16825	Pacific/Efate
 WS	-1350-17144	Pacific/Apia
 ZA,LS,SZ	-2615+02800	Africa/Johannesburg
+#
+# The next section contains experimental tab-separated comments for
+# use by user agents like tzselect that identify continents and oceans.
+#
+# For example, the comment "#@AQAntarctica/" means the country code
+# AQ is in the continent Antarctica regardless of the Zone name,
+# so Pacific/Auckland should be listed under Antarctica as well as
+# under the Pacific because its line's country codes include AQ.
+#
+# If more than one country code is affected each is listed separated
+# by commas, e.g., #@IS,SHAtlantic/".  If a country code is in
+# more than one continent or ocean, each is listed separated by
+# commas, e.g., the second column of "#@CY,TRAsia/,Europe/".
+#
+# These experimental comments are present only for country codes where
+# the continent or ocean is not already obvious from the Zone name.
+# For example, there is no such comment for RU since it already
+# corresponds to Zone names starting with both "Europe/" and "Asia/".
+#
+#@AQ	Antarctica/
+#@IS,SH	Atlantic/
+#@CY,TR	Asia/,Europe/
+#@SJ	Arctic/
+#@CC,CX,KM,MG,YT	Indian/