- tz - lists.iana.org

models for timezones
by scs＠eskimo.com Feb. 14, 2018

Feb. 14, 2018

It gets mentioned here often enough, but there's another significant aspect of the tz database which I'm not sure is always sufficiently appreciated, and that's how significantly it extends on the old V7/SysV/Posix model of time zones. In that old model, a time zone has one offset from Greenwich/UTC, and maybe a second offset on top of that to realize "daylight saving time", and one set of rules for deciding when to transition to and from DST. (Once upon a time, that set of rules might have been limited to the pre-1987 rules for the United States, and it might have been hard-compiled into C code. With the advent of the Posix TZ environment variable definition it's at least a little bit more flexible.) But of course (and since the beginning) the tz database has expanded on that model in at least two different ways: 1. It's not limited to one "standard" and perhaps one "daylight" time per year; there can be almost arbitrarily many offsets and arbitrarily many transition dates between them. 2. Everything -- the "base" offset (not that this is even a meaningful concept any more), the alternate offsets, and the transition dates between them can vary over time. And of course the reasons for doing this were that both changes were necessary in order to accommodate the real world; the old SysV/Posix model simply couldn't cope. But this means that there's a significantly imperfect match between the tz database and any programming language or time-handling library that has any of these notions: * A timezone is primarily defined by its base offset from UTC. * It's an additional property of a timezone whether it observes DST or not. * If DST applies to a timezone, it's defined by an additional offset and a single set of rules defining when it applies. * DST always involves a positive offset from the base offset. You *might* be able to get away with a tricky and/or imperfect mapping between the tz database and a scheme that has some of those notions -- for example, the tz reference code successfully implements the C/Posix API, isdst flag and all -- but it's bound to have warts or imperfections. Everything I've said here is, I imagine, familiar and unsurprising to any regular reader of this list, but it probably bears a bit more discussion in the Theory file. I was going to suggest adding these two new bullets under "Extensions to POSIX": * The TZ database allows for considerably more variation in time per year beyond the familiar "standard" and "daylight savings" times. A time zone can have any number of variations per year, and they may have arbitrary designations, not limited to "standard" and "daylight". * The parameters defining a time zone can vary over time, reflecting the fact that this happens in the real world all the time, as legislatures continually redefine them. Whether and when a zone observes DST (or other variants), and even the zone's notional "base offset" from UTC, are variable. (Therefore it doesn't even really make sense to talk about a zone's "base offset", since it's not necessarily a single number.) But that's in the "Time and date functions" section, and easy to overlook. So maybe these words belong as a paragraph higher up, perhaps even in the initial "Scope of the tz database" section: Because the database's scope encompasses real-world timezones which have wide-ranging complexity and are always evolving, the model for describing time zones allows for considerably more variation in time per year beyond the familiar "standard" and "daylight savings" times. A time zone can have any number of variations per year, and they may have arbitrary designations, not limited to "standard" and "daylight". Furthermore, the parameters defining a time zone can vary over time. Whether and when a zone observes DST (or other variants), and even the zone's notional "base offset" from UTC, are variable. (Therefore it doesn't even really make sense to talk about a zone's "base offset", since it is not necessarily a single number.)

3 3

Recommendations for stable list of timezone ids
by Tobias Lindaaker Feb. 14, 2018

Feb. 14, 2018

I am trying to compile a flat list of all tzids in the Time Zone Database in a way such that the position of a tzid remains the same in the list even in the face of future changes to the Time Zone Database. I would like to know if anyone could provide me with some insight into how (a prefix of) such a list could be generated from any version of the Time Zone Database. Or would this be something I would have to maintain myself from release to release of the Time Zone Database? The requirements I would have for generating this list would be that given two releases of the Time Zone Database, X and Y. If X is released before Y, then the list generated from X must be a prefix of the list generated from Y (and vice versa: if Y is released before X, the list generated from Y must be a prefix of the list generated from X). A simple alphabetical ordering is obviously not going to work, since for example the addition of America/Punta_Arenas in 2017a would end up before many of the tzids that existed in versions prior. Since I don't require this to work for all historical releases, my first thought was to start from a fairly recent release (tzdata2013h) and verify that I got the same order when sorting the timezones based on their earliest rule. However the removal of tzids (such as Canada/East-Saskatchewan in tzdata2017c) made this impossible, since any removal makes it impossible to ensure that prior versions are strict prefixes. It now seems as if I would have to maintain this list myself, tracking each release of the Time Zone Database and ensure that any tzids added to the Time Zone Database are appended to my list in release order. If possible I would very much prefer to avoid this, since it requires me to release updates of my software to track the releases of the Time Zone Database, I would much rather like it if my software could rely on the Time Zone Database available from the system where it was running. Finally some background on why (I think) I need to generate this type of list of tzids: I am improving the support for storing timestamp values in a database management system (Neo4j), and would like to avoid having to store the timezone component of zoned timestamps as a (variable length) text component, but rather store it as a fixed size integer offset into a table of tzids. Thus I need such a stable list of tzids. I have tried searching the archives of this mailing list for similar questions before posting, but have not been able to find such an entry. The closest I found were a few questions on how to translate the tzids to localized names. Since I did not read through the entire archives, but only did a search, I apologise in advance if this has been asked and solved before, and hope that you will be able to direct my attention to that thread. Thank you, Tobias

8 15

Inappropriate project direction
by Stephen Colebourne Feb. 12, 2018

Feb. 12, 2018

In the last few years, the following changes have been made to the tzdb project. Each of these - added no value - had a cost that far exceeded the benefits - should not have happened 1) Removal of Zone definitions from many countries. While the Zone definitions may have been the same across different countries, it was never appropriate to merge the time-zones of multiple different countries (backzone being the result). - the change caused LMT values to be lost - downstream consumers had to change logic wrt the meaning of backzone - it was culturally insensitive to not provide a primary Zone entry for some countries 2) Removal of textual short zone names. While these names may well have been invented in some cases, the had often become de facto standards - end-users complained about the loss of textual names - downstream consumers had to change logic to handle numeric-style identifiers 3) Move to a niche archive format The main archive format was changed from the well-known and widely supported gz to the niche lz format. There was and is no justification for using a niche format on a project as important as this one. - downstream consumers need to find and use the niche format - Windows does not have proper support for the niche format 4) Negative SAVE values Despite being a known fact in tzdb since 2005, and despite being warned not to in advance, a decision to re-interpret the meaning of Ireland DST was pushed through. - downstream consumers broke - the interaction with CLDR is incompatible with negative DST - the change has no impact on actual times - even if someone thought it was broken, there are no benefits to making the change 5) Fractional seconds A desire to fix subsecond data from over 50 years ago. - downstream consumers will break - the number of people who care is vanishingly small Were recent discussions a one-off, I might be prepared to let things lie, but as can be seen, there is a pattern here. Not one of these changes has added value to the project. Not one of them has been necessary to the primary mission of recording what governments are doing to their clocks now, nor even in the last 40 years. Worse, the majority are driven by a notion that getting the data "pure" trumps all problems reported by downstream consumers. It is long past time to accept that tzdb needs to focus on the primary mission - recording current government changes in a stable, backwards compatible manner. Tinkering needs to stop. Stephen

10 15

EP vote on EU DST; afternoon gloom in Scotland
by Paul Eggert Feb. 11, 2018

Feb. 11, 2018

On Thursday, the European Parliament voted 384-152 to pass a nonbinding resolution calling for the European Commission to re-evaluate the current system of daylight saving time in Europe. An article about this and how it's entangled with European politics can be found here: Yeginsu C. Daylight saving time: what's it good for? European lawmakers ask. New York Times. 2018-02-09. https://www.nytimes.com/2018/02/09/world/europe/europe-daylight-saving.html My favorite quote is about the UK Daylight Saving Bill 2010-12. Yeginsu writes: "That bill was met with fierce resistance in places like Scotland, where residents argued that they liked the afternoon gloom just fine."

2 1

License of lzip, lzlib and pdlzip
by Antonio Diaz Diaz Feb. 11, 2018

Feb. 11, 2018

Bryan Smith wrote: > There is still a heavy copyleft (e.g., GPL) v. non-copyleft FLOSS > debate that rages on, with various people putting various values -- > from nothing to everything -- on that. lzip -- or more problematic, > it's lzlib -- is GPLv2 -- not even LGPL -- which has some asterisks > for commercial developers. I don't know the state of public domain > lzip (pdlzip), but it seems to be good enough for any decompression > (and most general compression). Thanks for your comments. I'll just add a clarification about lzip licensing. Lzip itself is GPL version 2 or later. Lzlib was also GPLv2+, but a year ago (in version 1.9) the license was changed to 2-clause BSD as you can see in lzlib's homepage[1]. There is also another BSD licensed library (libarchive) able to (de)compress lzip files and lzip-compressed tar archives. Pdlzip has a 2-clause BSD license[2]. It is maintained and fully compatible with the lzip format for both compression and decompression. [1] http://www.nongnu.org/lzip/lzlib.html [2] http://www.nongnu.org/lzip/pdlzip.html Best regards, Antonio.

1 0

Fractional seconds in zic input
by Paul Eggert Feb. 10, 2018

Feb. 10, 2018

For many years I've chafed at tzdata's lack of support for fractional seconds. We have good evidence of well-established standard-time UT offsets that were not multiples of one second; for example, the Netherlands before 1937. These can't be recorded in tzdata except as comments. Ideally tzcode would support fractional-second times and UT offsets all the way down the chain. This would mean changes to the tz binary format and to the runtime API, though, which is not something we'd do lightly, if ever. However, it's easy to change the zic spec to allow fractional seconds, and to change zic to accept and ignore the fractions, so that fractional seconds can be documented more formally in the data; this could well be useful to applications other than tzcode. Proposed patch attached, hairy sscanf format and all. This patch does not actually change the data, as we'll need time, and/or a procedure to automatically generate data compatible with zic 2018c and earlier.

17 51

tzdata source compatibility
by christos＠zoulas.com Feb. 7, 2018

Feb. 7, 2018

Hi, Here's my 5 cents to the tzdb compatibility discussion: - Things need to move forward; half-measures like "functional comments" end up hurting in the long term and create unpredictable behavior. - There are other users of the tzdata "source" so compatibility needs to be maintained for "some time". - On the other hand, we can't be held hostage forever; people who write parsers, should be able to maintain the code. Straw man proposal: 1. Create a version ChangeLog with tzdb; it should be simple: - a version number (for reference) - the release date (to guide expiration) - an explanation to what changed in the format (for parser writers) 2. Maintain two copies of the source; the current one, and the previous version in a "compat" subdirectory. Expire "compat" a year after the release of the next version. I hope this is helpful, christos

5 6

New open-source zoneinfo compiler
by Kerry Shetline Feb. 5, 2018

Feb. 5, 2018

Hi, In case this might be of use to others, I’ve posted a new project on GitHub, https://github.com/kshetline/compact-time-zone-generator <https://github.com/kshetline/compact-time-zone-generator>. This is a parser and compiler written in Java that produces output primarily meant to be used with web apps. The project also includes an Angular demo app which consumes this format of compiled time zone data. The README for the project explains more, and provides some demo links, which might help decide if this is a project that might be useful to share on the discussion list. -Kerry

2 1

[PROPOSED] Fix 0.5 s bug for Jakarta in 1923
by Paul Eggert Feb. 5, 2018

Feb. 5, 2018

* ziguard.awk: Fix bug for Asia/Jakarta: the 1923-12-31 transition was off by 0.5 s when fractional seconds were enabled. --- ziguard.awk | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ziguard.awk b/ziguard.awk index 795b4ef..70376b7 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -38,6 +38,8 @@ BEGIN { frac["7:07:12"] = "7:07:12.5" # Asia/Jakarta before 1923 frac["7:36:42"] = "7:36:41.7" # Asia/Hong_Kong before 1904 frac["8:05:43"] = "8:05:43.2" # Asia/Shanghai before 1901 + + fract["23:47:12"] = "23:47:12.5" # Asia/Jakarta 1923-12-31 transition } /^Zone/ { zone = $2 } @@ -61,7 +63,7 @@ outfile != "main.zi" { } } - # Add or remove fractional seconds as needed. + # Add or remove fractional seconds as needed in UT offsets. f = $1 == "Zone" ? 3 : 1 for (rounded in frac) { original = frac[rounded] @@ -69,6 +71,13 @@ outfile != "main.zi" { $f = vanguard ? original : rounded } } + # Likewise for transition times. + for (rounded in fract) { + original = fract[rounded] + if ($(f + 6) == rounded || $(f + 6) == original) { + $(f + 6) = vanguard ? original : rounded + } + } } # If a Link line is followed by a Zone line for the same data, comment -- 2.14.3

1 0

[PROPOSED] Generalize data format upgrade procedure
by Paul Eggert Feb. 5, 2018

Feb. 5, 2018

* Makefile (XDST): Remove, replacing with the more-general ... (DATAFORM): ... new macro. All uses changed. (fulldata.zi, pdstdata.zi): Remove, replacing with the more-general ... (vanguard.zi, main.zi, rearguard.zi): ... new targets. All uses changed. (check_zishrink): Fix bug that caused this test to fail when PACKRATDATA was nonempty and testing vanguard or rearguard data. * NEWS, europe: Mention changes. * ziguard.awk: Handle fractional seconds as well as negative DST offsets. Rename from zidst.awk, since it now handles issues other than just DST. All uses changed. --- Makefile | 69 ++++++++++++++++++----------------------------- NEWS | 64 ++++++++++++++++++++++++++------------------ europe | 29 +++++++++----------- zidst.awk | 50 ---------------------------------- ziguard.awk | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 166 insertions(+), 135 deletions(-) delete mode 100644 zidst.awk create mode 100644 ziguard.awk diff --git a/Makefile b/Makefile index 92ddb80..659a5b0 100644 --- a/Makefile +++ b/Makefile @@ -10,25 +10,14 @@ VERSION= unknown # Email address for bug reports. BUGEMAIL= tz(a)iana.org -# To install the full data, which can contain daylight saving time -# offsets that are negative (relative to standard time), use -# XDST= full -# To install data containing only positive daylight saving time -# offsets, but otherwise as close to the full data as practical, use -# XDST= pdst -XDST= pdst -# Parsers requiring DST offsets to be positive should use the file -# pdstdata.zi, which contains almost all the data of 'africa' etc., -# except with positive DST offsets. This works around a problem that -# was discovered in January 2018 with negative DST in tests for ICU -# and OpenJDK. See: -# https://mm.icann.org/pipermail/tz/2018-January/025825.html -# https://mm.icann.org/pipermail/tz/2018-January/025822.html -# Currently the 'africa' etc. files use pdst form if comments are -# ignored, to ease transition for parsers that do not support -# negative DST offsets. This is intended to change to full form at -# some point, so that full-featured zi parsers that use the 'africa' -# files will get the full data without changing anything. +# Choose source data features. To get new features 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 +DATAFORM= main # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). @@ -483,8 +472,8 @@ 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= zidst.awk zishrink.awk version $(TDATA) $(PACKRATDATA) -DSTDATA_ZI_DEPS= zidst.awk $(TDATA) $(PACKRATDATA) +TZDATA_ZI_DEPS= ziguard.awk zishrink.awk version $(TDATA) $(PACKRATDATA) +DSTDATA_ZI_DEPS= ziguard.awk $(TDATA) $(PACKRATDATA) DATA= $(TDATA_TO_CHECK) backzone iso3166.tab leap-seconds.list \ leapseconds yearistype.sh $(ZONETABLES) AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk zishrink.awk @@ -522,7 +511,7 @@ VERSION_DEPS= \ SHELL= /bin/sh all: tzselect yearistype zic zdump libtz.a $(TABDATA) \ - fulldata.zi pdstdata.zi + vanguard.zi main.zi rearguard.zi ALL: all date $(ENCHILADA) @@ -558,14 +547,14 @@ version: $(VERSION_DEPS) mv $@.out $@ # These files can be tailored by setting BACKWARD, PACKRATDATA, etc. -fulldata.zi pdstdata.zi: $(DSTDATA_ZI_DEPS) - $(AWK) -v outfile='$@' -f zidst.awk $(TDATA) $(PACKRATDATA) \ +vanguard.zi main.zi rearguard.zi: $(DSTDATA_ZI_DEPS) + $(AWK) -v outfile='$@' -f ziguard.awk $(TDATA) $(PACKRATDATA) \ >$@.out mv $@.out $@ -tzdata.zi: $(XDST)data.zi version +tzdata.zi: $(DATAFORM).zi version version=`sed 1q version` && \ LC_ALL=C $(AWK) -v version="$$version" -f zishrink.awk \ - $(XDST)data.zi >$@.out + $(DATAFORM).zi >$@.out mv $@.out $@ version.h: version @@ -747,31 +736,25 @@ check_tzs: $(TZS) $(TZS_NEW) check_web: tz-how-to.html $(VALIDATE_ENV) $(VALIDATE) $(VALIDATE_FLAGS) tz-how-to.html -# The format of the source files, either full or pdst. -# Currently they are in pdst format, but this is expected to change. -SDST = pdst - -# Check that zishrink.awk does not alter the data, and that zidst.awk -# preserves $(SDST) data. +# Check that zishrink.awk does not alter the data, and that ziguard.awk +# preserves main-format data. check_zishrink: zic leapseconds $(PACKRATDATA) $(TDATA) \ - $(XDST)data.zi tzdata.zi + $(DATAFORM).zi tzdata.zi for type in posix right; do \ - mkdir -p time_t.dir/$$type time_t.dir/$$type-$(SDST) \ + mkdir -p time_t.dir/$$type time_t.dir/$$type-t \ time_t.dir/$$type-shrunk && \ case $$type in \ right) leap='-L leapseconds';; \ *) leap=;; \ esac && \ - $(ZIC) $$leap -d time_t.dir/$$type $(XDST)data.zi && \ - $(AWK) '/^Rule/' $(XDST)data.zi | \ - $(ZIC) $$leap -d time_t.dir/$$type - $(PACKRATDATA) && \ - case $(XDST) in \ - $(SDST)) \ - $(ZIC) $$leap -d time_t.dir/$$type-$(SDST) $(TDATA) && \ + $(ZIC) $$leap -d time_t.dir/$$type $(DATAFORM).zi && \ + case $(DATAFORM) in \ + main) \ + $(ZIC) $$leap -d time_t.dir/$$type-t $(TDATA) && \ $(AWK) '/^Rule/' $(TDATA) | \ - $(ZIC) $$leap -d time_t.dir/$$type-$(SDST) \ - $(XDST)data.zi && \ - diff -r time_t.dir/$$type time_t.dir/$$type-$(SDST);; \ + $(ZIC) $$leap -d time_t.dir/$$type-t - \ + $(PACKRATDATA) && \ + diff -r time_t.dir/$$type time_t.dir/$$type-t;; \ esac && \ $(ZIC) $$leap -d time_t.dir/$$type-shrunk tzdata.zi && \ diff -r time_t.dir/$$type time_t.dir/$$type-shrunk || exit; \ diff --git a/NEWS b/NEWS index adc9814..b13c356 100644 --- a/NEWS +++ b/NEWS @@ -3,8 +3,8 @@ News for the tz database Unreleased, experimental changes Briefly: - Support zi parsers that mishandle negative DST offsets - Add fractional seconds to source data format. + Add support for vanguard and rearguard data consumers. + Add fractional seconds to source data format and to vanguard data. Changes to past time stamps @@ -16,30 +16,41 @@ Unreleased, experimental changes Changes to build procedure - The new XDST macro in the Makefile lets the installer choose - XDST=full, which allows arbitrary DST offsets in the data, or - XDST=pdst, which allows only positive DST offsets. Choosing - XDST=full is arguably more correct for Ireland, which observes - Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in - winter. Choosing XDST=pdst is better for zoneinfo parsers that do - not work well with negative DST offsets, notably OpenJDK+CLDR. - On platforms using tzcode or similar APIs, XDST should not affect - any behavior other than that depending on the tm_isdst flag. - - For now this change does not affect client-visible behavior by - default, as the Makefile defaults to XDST=pdst and uncommented - parts of the data source files contain only pdst-format data. - After a bit of time for testing, XDST=full and full-format source - files are planned to become the default, so that parsers that - support negative DST offsets can get full data without changing - their build procedures. Parsers requiring positive DST offsets - should use the new file pdstdata.zi instead of tzdata.zi or the - source files 'africa' etc.: pdstdata.zi is pdst-compatible, it is - automatically built from the data source files, and it will - continue to be pdst-compatible regardless of XDST. To get - full-format data now, use the new file fulldata.zi, which will - continue to be full-format regardless of XDST. To get the format - selected by XDST, use tzdata.zi. + 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 contains two + features not in the main format: fractional seconds and negative + DST offsets. Fractional seconds were added in this release, + where they affect only zic input (output is unaffected). + Negative DST offsets improve support for Ireland, which uses + Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in + winter. tzcode has supported negative DST offsets 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. The files represent the + same data as closely as the formats allow. These three files + are intended for downstream data consumers and are not + installed. Zoneinfo parsers that require positive DST offsets + 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. Changes to code @@ -48,6 +59,7 @@ Unreleased, experimental changes zic currently rounds these fractions to the nearest integer (breaking ties to the even integer), the fractions may be useful to applications requiring more precision in historical timestamps. + This extension is currently used only in vanguard.zi. The code is a bit more portable to MS-Windows. (Thanks to Manuela Friedrich). diff --git a/europe b/europe index 76cbb5d..8aab26e 100644 --- a/europe +++ b/europe @@ -514,21 +514,19 @@ Link Europe/London Europe/Isle_of_Man # https://mm.icann.org/pipermail/tz/2018-January/025825.html # and with tests for OpenJDK: # https://mm.icann.org/pipermail/tz/2018-January/025822.html -# To work around this problem, zidst.awk translates the following data -# lines into two forms. First, fulldata.zi contains the full data, -# which includes negative DST offsets. Second, pdstdata.zi uses a -# traditional approximation for Irish time stamps after 1971-10-31 -# 02:00 UTC; although this approximation has tm_isdst flags that are -# the reverse of the full data, its UTC offsets are correct and this -# suffices for ICU and OpenJDK. Although this source file currently -# has pdstdata.zi lines active and fulldata.zi lines commented out, -# this is intended to change in the near future and downstream code -# should not rely on it. +# +# To work around this problem, the build procedure can translate the +# following data into two forms, one with negative DST offsets and the +# other form with a traditional approximation for Irish time stamps +# after 1971-10-31 02:00 UTC; although this approximation has tm_isdst +# flags that are reversed, its UTC offsets are correct and this often +# suffices. This source file currently uses only positive DST +# offsets, but this is intended to change and downstream code should +# not rely on it. # # The following is like GB-Eire and EU, except with standard time in -# summer and negative daylight saving time in winter. -# This rule set is active in fulldata.zi and is commented out in -# pdstdata.zi. +# summer and negative daylight saving time in winter. It is for when +# negative DST offsets are used. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S #Rule Eire 1971 only - Oct 31 2:00u -1:00 GMT #Rule Eire 1972 1980 - Mar Sun>=16 2:00u 0 IST @@ -549,10 +547,9 @@ Zone Europe/Dublin -0:25:00 - LMT 1880 Aug 2 0:00 1:00 IST 1947 Nov 2 2:00s 0:00 - GMT 1948 Apr 18 2:00s 0:00 GB-Eire GMT/IST 1968 Oct 27 -# The next line is active in fulldata.zi and commented out in pdstdata.zi. +# The next line is for when negative DST offsets are used. # 1:00 Eire IST/GMT -# These three lines are active in pdstdata.zi and commented out in -# fulldata.zi. +# These three lines are for when positive DST offsets are used. 1:00 - IST 1971 Oct 31 2:00u 0:00 GB-Eire GMT/IST 1996 0:00 EU GMT/IST diff --git a/zidst.awk b/zidst.awk deleted file mode 100644 index 7885e9a..0000000 --- a/zidst.awk +++ /dev/null @@ -1,50 +0,0 @@ -# Convert tzdata source into full or positive-DST 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. -# -# When converting to full form, the output can use negative DST offsets. -# -# When converting to positive-DST form, the output uses only positive -# DST offsets. The idea is for the output data to simulate the -# behavior of the input data as best it can within the constraints of -# positive DST offsets. -# -# In the input, lines requiring the full format are commented #[full] -# and the positive DST near-equivalents are commented #[pdst]. - -BEGIN { - dst_type["full"] = 1 - dst_type["pdst"] = 1 - - # The command line should set OUTFILE to the name of the output file, - # which should start with either "full" or "pdst". - todst = substr(outfile, 1, 4) - if (!dst_type[todst]) exit 1 -} - -/^Zone/ { zone = $2 } - -{ - in_comment = /^#/ - - # Test whether this line should differ between the full and the pdst versions. - Rule_Eire = /^#?Rule[\t ]+Eire[\t ]/ - Zone_Dublin_post_1968 \ - = (zone == "Europe/Dublin" && /^#?[\t ]+[01]:00[\t ]/ \ - && (!$(in_comment + 4) || 1968 < $(in_comment + 4))) - - # If so, uncomment the desired version and comment out the undesired one. - if (Rule_Eire || Zone_Dublin_post_1968) { - if ((Rule_Eire \ - || (Zone_Dublin_post_1968 && $(in_comment + 3) == "IST/GMT")) \ - == (todst == "full")) { - sub(/^#/, "") - } else if (/^[^#]/) { - sub(/^/, "#") - } - } -} - -{ print } diff --git a/ziguard.awk b/ziguard.awk new file mode 100644 index 0000000..795b4ef --- /dev/null +++ b/ziguard.awk @@ -0,0 +1,89 @@ +# 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. +# +# When converting to vanguard form, the output can use fractional seconds +# and negative DST offsets. +# +# When converting to rearguard form, the output omits fractional +# seconds and uses only positive DST offsets. 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. + +BEGIN { + dst_type["vanguard.zi"] = 1 + dst_type["main.zi"] = 1 + dst_type["rearguard.zi"] = 1 + + # The command line should set OUTFILE to the name of the output file. + if (!dst_type[outfile]) exit 1 + vanguard = outfile == "vanguard.zi" + + # List non-integer standard times more accurately if known. + # This list does not attempt to record every UT offset that is + # not an integral multiple of 1 s; it merely records those that + # do not appear to be just LMT. + frac["-5:36:13"] = "-5:36:13.3" # America/Costa_Rica before 1921 + frac["-5:07:10"] = "-5:07:10.41" # America/Jamaica before 1912 + frac["-4:16:48"] = "-4:16:48.25" # America/Cordoba etc. 1894-1920 + frac["-0:36:45"] = "-0:36:44.68" # Europe/Lisbon before 1912 + frac["-0:25:21"] = "-0:25:21.1" # Europe/Dublin 1880-1916 + frac["0:19:32"] = "0:19:32.13" # Europe/Amsterdam before 1937 + frac["1:39:49"] = "1:39:49.2" # Europe/Helsinki before 1921 + frac["2:05:09"] = "2:05:08.9" # Africa/Cairo before 1900 + frac["4:37:11"] = "4:37:10.8" # Asia/Tashkent before 1924 + frac["7:06:30"] = "7:06:30.1333" #... Asia/Ho_Chi_Minh 1906-1911 + frac["7:07:12"] = "7:07:12.5" # Asia/Jakarta before 1923 + frac["7:36:42"] = "7:36:41.7" # Asia/Hong_Kong before 1904 + frac["8:05:43"] = "8:05:43.2" # Asia/Shanghai before 1901 +} + +/^Zone/ { zone = $2 } + +outfile != "main.zi" { + in_comment = /^#/ + + # If this line should differ due to Ireland using negative DST offsets, + # uncomment the desired version and comment out the undesired one. + Rule_Eire = /^#?Rule[\t ]+Eire[\t ]/ + Zone_Dublin_post_1968 \ + = (zone == "Europe/Dublin" && /^#?[\t ]+[01]:00[\t ]/ \ + && (!$(in_comment + 4) || 1968 < $(in_comment + 4))) + if (Rule_Eire || Zone_Dublin_post_1968) { + if ((Rule_Eire \ + || (Zone_Dublin_post_1968 && $(in_comment + 3) == "IST/GMT")) \ + == vanguard) { + sub(/^#/, "") + } else if (/^[^#]/) { + sub(/^/, "#") + } + } + + # Add or remove fractional seconds as needed. + f = $1 == "Zone" ? 3 : 1 + for (rounded in frac) { + original = frac[rounded] + if ($f == rounded || $f == original) { + $f = vanguard ? original : rounded + } + } +} + +# If a Link line is followed by a Zone line for the same data, comment +# out the Link line. This can happen if backzone overrides a Link +# with a Zone. +/^Link/ { + linkline[$3] = NR +} +/^Zone/ { + sub(/^Link/, "#Link", line[linkline[$2]]) +} + +{ line[NR] = $0 } + +END { + for (i = 1; i <= NR; i++) + print line[i] +} -- 2.14.3

1 0

[PROPOSED] zic now rounds to even
by Paul Eggert Feb. 5, 2018

Feb. 5, 2018

* NEWS, zic.8: Mention this. * zic.c (gethms): Round to even instead of discarding fractional seconds. --- NEWS | 5 +++-- zic.8 | 4 +++- zic.c | 18 ++++++++++++++---- 3 files changed, 20 insertions(+), 7 deletions(-) diff --git a/NEWS b/NEWS index f00b29f..adc9814 100644 --- a/NEWS +++ b/NEWS @@ -45,8 +45,9 @@ Unreleased, experimental changes zic now accepts fractional seconds in expressions like 00:19:32.13 (the UT offset of the Netherlands from 1835 to 1937). Although - zic currently ignores these fractions, they may be useful to - applications requiring more precision in historical timestamps. + zic currently rounds these fractions to the nearest integer + (breaking ties to the even integer), the fractions may be useful + to applications requiring more precision in historical timestamps. The code is a bit more portable to MS-Windows. (Thanks to Manuela Friedrich). diff --git a/zic.8 b/zic.8 index f1fc8e2..28e4bd6 100644 --- a/zic.8 +++ b/zic.8 @@ -267,8 +267,10 @@ where hour 0 is midnight at the start of the day, and hour 24 is midnight at the end of the day. Although .I zic -currently ignores any fractional seconds, the fractions may be useful +currently rounds fractional seconds to the nearest integer +(breaking ties to the even integer), the fractions may be useful to other applications requiring greater precision. +The source format does not specify any maximum precision. Any of these forms may be followed by the letter .B w if the given time is local diff --git a/zic.c b/zic.c index 4965a10..6ad31f9 100644 --- a/zic.c +++ b/zic.c @@ -1197,7 +1197,8 @@ gethms(char const *string, char const *errstring, bool signable) { zic_t hh; int sign, mm = 0, ss = 0; - char hhx, mmx, ssx, xs; + char hhx, mmx, ssx, xr = '0', xs; + int tenths = 0; bool ok = true; if (string == NULL || *string == '\0') @@ -1209,10 +1210,18 @@ gethms(char const *string, char const *errstring, bool signable) ++string; } else sign = 1; switch (sscanf(string, - "%"SCNdZIC"%c%d%c%d%c%*1d%*[0123456789]%c", - &hh, &hhx, &mm, &mmx, &ss, &ssx, &xs)) { + "%"SCNdZIC"%c%d%c%d%c%1d%*[0]%c%*[0123456789]%c", + &hh, &hhx, &mm, &mmx, &ss, &ssx, &tenths, &xr, &xs)) { default: ok = false; break; - case 6: ok &= ssx == '.'; /* fallthrough */ + case 8: + ok = '0' <= xr && xr <= '9'; + /* fallthrough */ + case 7: + ok &= ssx == '.'; + if (ok && noise) + warning(_("fractional seconds rejected by" + " pre-2018 versions of zic")); + /* fallthrough */ case 5: ok &= mmx == ':'; /* fallthrough */ case 3: ok &= hhx == ':'; /* fallthrough */ case 1: break; @@ -1231,6 +1240,7 @@ gethms(char const *string, char const *errstring, bool signable) error(_("time overflow")); return 0; } + ss += 5 + ((ss ^ 1) & (xr == '0')) <= tenths; /* Round to even. */ if (noise && (hh > HOURSPERDAY || (hh == HOURSPERDAY && (mm != 0 || ss != 0)))) warning(_("values over 24 hours not handled by pre-2007 versions of zic")); -- 2.7.4

1 0

[PROPOSED] Fix off-by-1 error for Jamaica and T&C before 1913
by Paul Eggert Feb. 5, 2018

Feb. 5, 2018

This was discovered when checking a not-yet-published version of zic. * NEWS: Mention this. * northamerica (America/Jamaica, America/Grand_Turk): * backzone (America/Cayman): Fix rounding error. --- NEWS | 3 +++ backzone | 2 +- northamerica | 6 +++--- 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index beefd39..f00b29f 100644 --- a/NEWS +++ b/NEWS @@ -11,6 +11,9 @@ Unreleased, experimental changes Enderbury and Kiritimati skipped New Year's Eve 1994, not New Year's day 1995. (Thanks to Kerry Shetline.) + Fix an off-by-1 error for pre-1913 timestamps in Jamaica and in + Turks & Caicos. + Changes to build procedure The new XDST macro in the Makefile lets the installer choose diff --git a/backzone b/backzone index 3006b27..cc724aa 100644 --- a/backzone +++ b/backzone @@ -271,7 +271,7 @@ Zone America/Aruba -4:40:24 - LMT 1912 Feb 12 # Oranjestad # Cayman Is Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown - -5:07:11 - KMT 1912 Feb # Kingston Mean Time + -5:07:10 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST # Canada diff --git a/northamerica b/northamerica index a014126..dabca97 100644 --- a/northamerica +++ b/northamerica @@ -3264,8 +3264,8 @@ Zone America/Tegucigalpa -5:48:52 - LMT 1921 Apr # http://www.jamaicaobserver.com/columns/The-politician-in-all-of-us_17573647 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone America/Jamaica -5:07:11 - LMT 1890 # Kingston - -5:07:11 - KMT 1912 Feb # Kingston Mean Time +Zone America/Jamaica -5:07:10 - LMT 1890 # Kingston + -5:07:10 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST 1974 -5:00 US E%sT 1984 -5:00 - EST @@ -3415,7 +3415,7 @@ Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Grand_Turk -4:44:32 - LMT 1890 - -5:07:11 - KMT 1912 Feb # Kingston Mean Time + -5:07:10 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST 1979 -5:00 US E%sT 2015 Nov Sun>=1 2:00 -4:00 - AST 2018 Mar 11 3:00 -- 2.14.3

1 0

Pacific/Enderbury and Pacific/Kiritimati, 1995
by Kerry Shetline Feb. 4, 2018

Feb. 4, 2018

Hello, When these time zones switched sides of the International Dateline at the beginning of 1995, the tz database, viewed via zdump, shows Sunday, January 1 being skipped — Saturday December 31, 1994 being followed immediately by Monday, January 2, 1995. I found an article, however, that suggests that December 31 was the day that was skipped, so that the transition would be from Friday December 30, 1994 to Sunday January 1, 1995: https://wikitravel.org/en/Kiribati <https://wikitravel.org/en/Kiribati> I have no particular reason to believe this article is authoritative, but it did strike me odd that New Year’s Day, and a Sunday (more likely to offend some people’s religious sensibilities) would be the day that was skipped rather than Saturday. -Kerry

2 2

Fwd: Request to mention 24timezones.com under the links section
by 24tz Team Feb. 3, 2018

Feb. 3, 2018

Oops, here is the patch attached ============ Forwarded message ============ >From : 24tz Team <info(a)24timezones.com> To : "tz"<tz(a)iana.org> Date : Thu, 01 Feb 2018 13:31:14 +0200 Subject : Request to mention 24timezones.com under the links section ============ Forwarded message ============ > Greetings > > https://24timezones.com is one of the oldest time zones related websites on the web, and has helped millions of people find out the time around the globe over the past 13 years, using the tz database as its primary source. > > It would be great if you could mention us under the "Websites using recent versions of the tz database" section. Please find suggested patch attached and adjust order of complexity and fanciness accordingly :) > > Many thanks for all efforts in maintaining this database! > >

2 1

[PROPOSED] Improve commentary for pre-1920 Argentina
by Paul Eggert Feb. 1, 2018

Feb. 1, 2018

* southamerica: Coalesc comments for standard time in Argentina before 1920. --- southamerica | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/southamerica b/southamerica index e1c6590..e3684aa 100644 --- a/southamerica +++ b/southamerica @@ -202,12 +202,14 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 - # It's Law No. 7,210. This change is due to a public power emergency, so for # now we'll assume it's for this year only. # -# From Paul Eggert (2014-08-09): +# From Paul Eggert (2018-01-31): # Hora de verano para la República Argentina # http://buenasiembra.com.ar/esoterismo/astrologia/hora-de-verano-de-la-repub… # says that standard time in Argentina from 1894-10-31 # to 1920-05-01 was -4:16:48.25. Go with this more-precise value -# over Shanks & Pottenger. +# over Shanks & Pottenger. It is upward compatible with Milne, who +# says Córdoba time was -4:16:48.2. + # # From Mariano Absatz (2004-06-05): # These media articles from a major newspaper mostly cover the current state: @@ -392,9 +394,6 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 - # plus is that this silences a zic complaint that there's no POSIX TZ # setting for time stamps past 2038. -# From Paul Eggert (2013-02-21): -# Milne says Córdoba time was -4:16:48.2. Round to the nearest second. - # Zone NAME GMTOFF RULES FORMAT [UNTIL] # # Buenos Aires (BA), Capital Federal (CF), -- 2.14.3

1 0

Re: [tz] Will you add America/Boston?
by None Jan. 31, 2018

Jan. 31, 2018

Why exactly do you want an America/Boston? The timezone for Boston is America/ New_York. -- John Harris, Jr. <johnmh(a)splentity.com> CTO, Splentity Software

2 1

Will you add America/Boston?
by David Hedlund Jan. 30, 2018

Jan. 30, 2018

Boston is unfortunately not listed in the Time Zone Database. Are you going to add it?

4 3

[PROPOSED] Remove unused letters from Rule lines
by Paul Eggert Jan. 30, 2018

Jan. 30, 2018

* checktab.awk: Check for common instances of a Rule line containing LETTER/S that are never used. All instances removed. This does not change zic output; it merely omits data no longer relevant to entries that now use numeric time zone abbreviations. --- africa | 8 +-- asia | 148 ++++++++++++++++++++-------------------- australasia | 86 ++++++++++++------------ checktab.awk | 9 +++ europe | 14 ++-- southamerica | 216 +++++++++++++++++++++++++++++------------------------------ 6 files changed, 245 insertions(+), 236 deletions(-) diff --git a/africa b/africa index 56640cd..0f8b16c 100644 --- a/africa +++ b/africa @@ -396,8 +396,8 @@ Zone Africa/Cairo 2:05:09 - LMT 1900 Oct # lack of better info, use Shanks except treat the minus sign as a # typo, and assume DST started in 1920 not 1936. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Ghana 1920 1942 - Sep 1 0:00 0:20 GHST -Rule Ghana 1920 1942 - Dec 31 0:00 0 GMT +Rule Ghana 1920 1942 - Sep 1 0:00 0:20 - +Rule Ghana 1920 1942 - Dec 31 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Accra -0:00:52 - LMT 1918 0:00 Ghana GMT/+0020 @@ -609,9 +609,9 @@ Zone Africa/Tripoli 0:52:44 - LMT 1920 # at 2am (or 02:00) local time..." # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Mauritius 1982 only - Oct 10 0:00 1:00 S +Rule Mauritius 1982 only - Oct 10 0:00 1:00 - Rule Mauritius 1983 only - Mar 21 0:00 0 - -Rule Mauritius 2008 only - Oct lastSun 2:00 1:00 S +Rule Mauritius 2008 only - Oct lastSun 2:00 1:00 - Rule Mauritius 2009 only - Mar lastSun 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis diff --git a/asia b/asia index 3f6e95c..63d2fb0 100644 --- a/asia +++ b/asia @@ -69,13 +69,13 @@ 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 S +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 S +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 S +Rule RussiaAsia 1985 2010 - Mar lastSun 2:00s 1:00 - Rule RussiaAsia 1996 2010 - Oct lastSun 2:00s 0 - # Afghanistan @@ -110,7 +110,7 @@ Zone Asia/Kabul 4:36:48 - LMT 1890 # (brief) # http://www.worldtimezone.com/dst_news/dst_news_armenia03.html # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Armenia 2011 only - Mar lastSun 2:00s 1:00 S +Rule Armenia 2011 only - Mar lastSun 2:00s 1:00 - Rule Armenia 2011 only - Oct lastSun 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 @@ -136,7 +136,7 @@ Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 # http://en.apa.az/xeber_azerbaijan_abolishes_daylight_savings_ti_240862.html # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Azer 1997 2015 - Mar lastSun 4:00 1:00 S +Rule Azer 1997 2015 - Mar lastSun 4:00 1:00 - Rule Azer 1997 2015 - Oct lastSun 5:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 @@ -223,7 +223,7 @@ Zone Asia/Baku 3:19:24 - LMT 1924 May 2 # http://www.worldtimezone.com/dst_news/dst_news_bangladesh06.html # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Dhaka 2009 only - Jun 19 23:00 1:00 S +Rule Dhaka 2009 only - Jun 19 23:00 1:00 - Rule Dhaka 2009 only - Dec 31 24:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1106,61 +1106,61 @@ Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov # thirtieth day of Shahrivar. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Iran 1978 1980 - Mar 21 0:00 1:00 D -Rule Iran 1978 only - Oct 21 0:00 0 S -Rule Iran 1979 only - Sep 19 0:00 0 S -Rule Iran 1980 only - Sep 23 0:00 0 S -Rule Iran 1991 only - May 3 0:00 1:00 D -Rule Iran 1992 1995 - Mar 22 0:00 1:00 D -Rule Iran 1991 1995 - Sep 22 0:00 0 S -Rule Iran 1996 only - Mar 21 0:00 1:00 D -Rule Iran 1996 only - Sep 21 0:00 0 S -Rule Iran 1997 1999 - Mar 22 0:00 1:00 D -Rule Iran 1997 1999 - Sep 22 0:00 0 S -Rule Iran 2000 only - Mar 21 0:00 1:00 D -Rule Iran 2000 only - Sep 21 0:00 0 S -Rule Iran 2001 2003 - Mar 22 0:00 1:00 D -Rule Iran 2001 2003 - Sep 22 0:00 0 S -Rule Iran 2004 only - Mar 21 0:00 1:00 D -Rule Iran 2004 only - Sep 21 0:00 0 S -Rule Iran 2005 only - Mar 22 0:00 1:00 D -Rule Iran 2005 only - Sep 22 0:00 0 S -Rule Iran 2008 only - Mar 21 0:00 1:00 D -Rule Iran 2008 only - Sep 21 0:00 0 S -Rule Iran 2009 2011 - Mar 22 0:00 1:00 D -Rule Iran 2009 2011 - Sep 22 0:00 0 S -Rule Iran 2012 only - Mar 21 0:00 1:00 D -Rule Iran 2012 only - Sep 21 0:00 0 S -Rule Iran 2013 2015 - Mar 22 0:00 1:00 D -Rule Iran 2013 2015 - Sep 22 0:00 0 S -Rule Iran 2016 only - Mar 21 0:00 1:00 D -Rule Iran 2016 only - Sep 21 0:00 0 S -Rule Iran 2017 2019 - Mar 22 0:00 1:00 D -Rule Iran 2017 2019 - Sep 22 0:00 0 S -Rule Iran 2020 only - Mar 21 0:00 1:00 D -Rule Iran 2020 only - Sep 21 0:00 0 S -Rule Iran 2021 2023 - Mar 22 0:00 1:00 D -Rule Iran 2021 2023 - Sep 22 0:00 0 S -Rule Iran 2024 only - Mar 21 0:00 1:00 D -Rule Iran 2024 only - Sep 21 0:00 0 S -Rule Iran 2025 2027 - Mar 22 0:00 1:00 D -Rule Iran 2025 2027 - Sep 22 0:00 0 S -Rule Iran 2028 2029 - Mar 21 0:00 1:00 D -Rule Iran 2028 2029 - Sep 21 0:00 0 S -Rule Iran 2030 2031 - Mar 22 0:00 1:00 D -Rule Iran 2030 2031 - Sep 22 0:00 0 S -Rule Iran 2032 2033 - Mar 21 0:00 1:00 D -Rule Iran 2032 2033 - Sep 21 0:00 0 S -Rule Iran 2034 2035 - Mar 22 0:00 1:00 D -Rule Iran 2034 2035 - Sep 22 0:00 0 S +Rule Iran 1978 1980 - Mar 21 0:00 1:00 - +Rule Iran 1978 only - Oct 21 0:00 0 - +Rule Iran 1979 only - Sep 19 0:00 0 - +Rule Iran 1980 only - Sep 23 0:00 0 - +Rule Iran 1991 only - May 3 0:00 1:00 - +Rule Iran 1992 1995 - Mar 22 0:00 1:00 - +Rule Iran 1991 1995 - Sep 22 0:00 0 - +Rule Iran 1996 only - Mar 21 0:00 1:00 - +Rule Iran 1996 only - Sep 21 0:00 0 - +Rule Iran 1997 1999 - Mar 22 0:00 1:00 - +Rule Iran 1997 1999 - Sep 22 0:00 0 - +Rule Iran 2000 only - Mar 21 0:00 1:00 - +Rule Iran 2000 only - Sep 21 0:00 0 - +Rule Iran 2001 2003 - Mar 22 0:00 1:00 - +Rule Iran 2001 2003 - Sep 22 0:00 0 - +Rule Iran 2004 only - Mar 21 0:00 1:00 - +Rule Iran 2004 only - Sep 21 0:00 0 - +Rule Iran 2005 only - Mar 22 0:00 1:00 - +Rule Iran 2005 only - Sep 22 0:00 0 - +Rule Iran 2008 only - Mar 21 0:00 1:00 - +Rule Iran 2008 only - Sep 21 0:00 0 - +Rule Iran 2009 2011 - Mar 22 0:00 1:00 - +Rule Iran 2009 2011 - Sep 22 0:00 0 - +Rule Iran 2012 only - Mar 21 0:00 1:00 - +Rule Iran 2012 only - Sep 21 0:00 0 - +Rule Iran 2013 2015 - Mar 22 0:00 1:00 - +Rule Iran 2013 2015 - Sep 22 0:00 0 - +Rule Iran 2016 only - Mar 21 0:00 1:00 - +Rule Iran 2016 only - Sep 21 0:00 0 - +Rule Iran 2017 2019 - Mar 22 0:00 1:00 - +Rule Iran 2017 2019 - Sep 22 0:00 0 - +Rule Iran 2020 only - Mar 21 0:00 1:00 - +Rule Iran 2020 only - Sep 21 0:00 0 - +Rule Iran 2021 2023 - Mar 22 0:00 1:00 - +Rule Iran 2021 2023 - Sep 22 0:00 0 - +Rule Iran 2024 only - Mar 21 0:00 1:00 - +Rule Iran 2024 only - Sep 21 0:00 0 - +Rule Iran 2025 2027 - Mar 22 0:00 1:00 - +Rule Iran 2025 2027 - Sep 22 0:00 0 - +Rule Iran 2028 2029 - Mar 21 0:00 1:00 - +Rule Iran 2028 2029 - Sep 21 0:00 0 - +Rule Iran 2030 2031 - Mar 22 0:00 1:00 - +Rule Iran 2030 2031 - Sep 22 0:00 0 - +Rule Iran 2032 2033 - Mar 21 0:00 1:00 - +Rule Iran 2032 2033 - Sep 21 0:00 0 - +Rule Iran 2034 2035 - Mar 22 0:00 1:00 - +Rule Iran 2034 2035 - Sep 22 0:00 0 - # # The following rules are approximations starting in the year 2038. # These are the best post-2037 approximations available, given the # restrictions of a single rule using a Gregorian-based data format. # At some point this table will need to be extended, though quite # possibly Iran will change the rules first. -Rule Iran 2036 max - Mar 21 0:00 1:00 D -Rule Iran 2036 max - Sep 21 0:00 0 S +Rule Iran 2036 max - Mar 21 0:00 1:00 - +Rule Iran 2036 max - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 @@ -1196,17 +1196,17 @@ Zone Asia/Tehran 3:25:44 - LMT 1916 # https://www.timeanddate.com/news/time/iraq-dumps-daylight-saving.html # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Iraq 1982 only - May 1 0:00 1:00 D -Rule Iraq 1982 1984 - Oct 1 0:00 0 S -Rule Iraq 1983 only - Mar 31 0:00 1:00 D -Rule Iraq 1984 1985 - Apr 1 0:00 1:00 D -Rule Iraq 1985 1990 - Sep lastSun 1:00s 0 S -Rule Iraq 1986 1990 - Mar lastSun 1:00s 1:00 D +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 D -Rule Iraq 1991 2007 - Oct 1 3:00s 0 S +Rule Iraq 1991 2007 - Apr 1 3:00s 1:00 - +Rule Iraq 1991 2007 - Oct 1 3:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 2:57:36 - BMT 1918 # Baghdad Mean Time? @@ -1903,9 +1903,9 @@ Zone Asia/Oral 3:25:24 - LMT 1924 May 2 # or Ural'sk # From 2005-08-12 our GMT-offset is +6, w/o any daylight saving. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Kyrgyz 1992 1996 - Apr Sun>=7 0:00s 1:00 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 S +Rule Kyrgyz 1997 2005 - Mar lastSun 2:30 1:00 - Rule Kyrgyz 1997 2004 - Oct lastSun 2:30 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 @@ -2037,7 +2037,7 @@ Zone Asia/Beirut 2:22:00 - LMT 1880 # Malaysia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule NBorneo 1935 1941 - Sep 14 0:00 0:20 TS # one-Third Summer +Rule NBorneo 1935 1941 - Sep 14 0:00 0:20 - Rule NBorneo 1935 1941 - Dec 14 0:00 0 - # # peninsular Malaysia @@ -2182,7 +2182,7 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # Malé # http://zasag.mn/news/view/8969 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Mongol 1983 1984 - Apr 1 0:00 1:00 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 @@ -2199,13 +2199,13 @@ Rule Mongol 1983 only - Oct 1 0:00 0 - # 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 S +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 S +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 S -Rule Mongol 2015 2016 - Mar lastSat 2:00 1:00 S +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 GMTOFF RULES FORMAT [UNTIL] @@ -2737,11 +2737,11 @@ Zone Asia/Hebron 2:20:23 - LMT 1900 Oct # http://www.philstar.com/headlines/2014/08/05/1354152/pnoy-urged-declare-use… # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Phil 1936 only - Nov 1 0:00 1:00 S +Rule Phil 1936 only - Nov 1 0:00 1:00 - Rule Phil 1937 only - Feb 1 0:00 0 - -Rule Phil 1954 only - Apr 12 0:00 1:00 S +Rule Phil 1954 only - Apr 12 0:00 1:00 - Rule Phil 1954 only - Jul 1 0:00 0 - -Rule Phil 1978 only - Mar 22 0:00 1:00 S +Rule Phil 1978 only - Mar 22 0:00 1:00 - Rule Phil 1978 only - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Manila -15:56:00 - LMT 1844 Dec 31 diff --git a/australasia b/australasia index bdf19a4..2de41d2 100644 --- a/australasia +++ b/australasia @@ -196,20 +196,20 @@ Zone Australia/Broken_Hill 9:25:48 - LMT 1895 Feb # Lord Howe Island # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule LH 1981 1984 - Oct lastSun 2:00 1:00 D -Rule LH 1982 1985 - Mar Sun>=1 2:00 0 S -Rule LH 1985 only - Oct lastSun 2:00 0:30 D -Rule LH 1986 1989 - Mar Sun>=15 2:00 0 S -Rule LH 1986 only - Oct 19 2:00 0:30 D -Rule LH 1987 1999 - Oct lastSun 2:00 0:30 D -Rule LH 1990 1995 - Mar Sun>=1 2:00 0 S -Rule LH 1996 2005 - Mar lastSun 2:00 0 S -Rule LH 2000 only - Aug lastSun 2:00 0:30 D -Rule LH 2001 2007 - Oct lastSun 2:00 0:30 D -Rule LH 2006 only - Apr Sun>=1 2:00 0 S -Rule LH 2007 only - Mar lastSun 2:00 0 S -Rule LH 2008 max - Apr Sun>=1 2:00 0 S -Rule LH 2008 max - Oct Sun>=1 2:00 0:30 D +Rule LH 1981 1984 - Oct lastSun 2:00 1:00 - +Rule LH 1982 1985 - Mar Sun>=1 2:00 0 - +Rule LH 1985 only - Oct lastSun 2:00 0:30 - +Rule LH 1986 1989 - Mar Sun>=15 2:00 0 - +Rule LH 1986 only - Oct 19 2:00 0:30 - +Rule LH 1987 1999 - Oct lastSun 2:00 0:30 - +Rule LH 1990 1995 - Mar Sun>=1 2:00 0 - +Rule LH 1996 2005 - Mar lastSun 2:00 0 - +Rule LH 2000 only - Aug lastSun 2:00 0:30 - +Rule LH 2001 2007 - Oct lastSun 2:00 0:30 - +Rule LH 2006 only - Apr Sun>=1 2:00 0 - +Rule LH 2007 only - Mar lastSun 2:00 0 - +Rule LH 2008 max - Apr Sun>=1 2:00 0 - +Rule LH 2008 max - Oct Sun>=1 2:00 0:30 - Zone Australia/Lord_Howe 10:36:20 - LMT 1895 Feb 10:00 - AEST 1981 Mar 10:30 LH +1030/+1130 1985 Jul @@ -367,15 +367,15 @@ Zone Indian/Cocos 6:27:40 - LMT 1900 # practice than guessing no DST. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Fiji 1998 1999 - Nov Sun>=1 2:00 1:00 S +Rule Fiji 1998 1999 - Nov Sun>=1 2:00 1:00 - Rule Fiji 1999 2000 - Feb lastSun 3:00 0 - -Rule Fiji 2009 only - Nov 29 2:00 1:00 S +Rule Fiji 2009 only - Nov 29 2:00 1:00 - Rule Fiji 2010 only - Mar lastSun 3:00 0 - -Rule Fiji 2010 2013 - Oct Sun>=21 2:00 1:00 S +Rule Fiji 2010 2013 - Oct Sun>=21 2:00 1:00 - Rule Fiji 2011 only - Mar Sun>=1 3:00 0 - Rule Fiji 2012 2013 - Jan Sun>=18 3:00 0 - Rule Fiji 2014 only - Jan Sun>=18 2:00 0 - -Rule Fiji 2014 max - Nov Sun>=1 2:00 1:00 S +Rule Fiji 2014 max - Nov Sun>=1 2:00 1:00 - Rule Fiji 2015 max - Jan Sun>=14 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fiji 11:55:44 - LMT 1915 Oct 26 # Suva @@ -447,9 +447,9 @@ Zone Pacific/Nauru 11:07:40 - LMT 1921 Jan 15 # Uaobe # New Caledonia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule NC 1977 1978 - Dec Sun>=1 0:00 1:00 S +Rule NC 1977 1978 - Dec Sun>=1 0:00 1:00 - Rule NC 1978 1979 - Feb 27 0:00 0 - -Rule NC 1996 only - Dec 1 2:00s 1:00 S +Rule NC 1996 only - Dec 1 2:00s 1:00 - # Shanks & Pottenger say the following was at 2:00; go with IATA. Rule NC 1997 only - Mar 2 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -474,23 +474,23 @@ Rule NZ 1946 only - Jan 1 0:00 0 S # transition. Duplicate the Rule lines for now, to give the 2018a change # time to percolate out. Rule NZ 1974 only - Nov Sun>=1 2:00s 1:00 D -Rule Chatham 1974 only - Nov Sun>=1 2:45s 1:00 D +Rule Chatham 1974 only - Nov Sun>=1 2:45s 1:00 - Rule NZ 1975 only - Feb lastSun 2:00s 0 S -Rule Chatham 1975 only - Feb lastSun 2:45s 0 S +Rule Chatham 1975 only - Feb lastSun 2:45s 0 - Rule NZ 1975 1988 - Oct lastSun 2:00s 1:00 D -Rule Chatham 1975 1988 - Oct lastSun 2:45s 1:00 D +Rule Chatham 1975 1988 - Oct lastSun 2:45s 1:00 - Rule NZ 1976 1989 - Mar Sun>=1 2:00s 0 S -Rule Chatham 1976 1989 - Mar Sun>=1 2:45s 0 S +Rule Chatham 1976 1989 - Mar Sun>=1 2:45s 0 - Rule NZ 1989 only - Oct Sun>=8 2:00s 1:00 D -Rule Chatham 1989 only - Oct Sun>=8 2:45s 1:00 D +Rule Chatham 1989 only - Oct Sun>=8 2:45s 1:00 - Rule NZ 1990 2006 - Oct Sun>=1 2:00s 1:00 D -Rule Chatham 1990 2006 - Oct Sun>=1 2:45s 1:00 D +Rule Chatham 1990 2006 - Oct Sun>=1 2:45s 1:00 - Rule NZ 1990 2007 - Mar Sun>=15 2:00s 0 S -Rule Chatham 1990 2007 - Mar Sun>=15 2:45s 0 S +Rule Chatham 1990 2007 - Mar Sun>=15 2:45s 0 - Rule NZ 2007 max - Sep lastSun 2:00s 1:00 D -Rule Chatham 2007 max - Sep lastSun 2:45s 1:00 D +Rule Chatham 2007 max - Sep lastSun 2:45s 1:00 - Rule NZ 2008 max - Apr Sun>=1 2:00s 0 S -Rule Chatham 2008 max - Apr Sun>=1 2:45s 0 S +Rule Chatham 2008 max - Apr Sun>=1 2:45s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Auckland 11:39:04 - LMT 1868 Nov 2 11:30 NZ NZ%sT 1946 Jan 1 @@ -514,9 +514,9 @@ Link Pacific/Auckland Antarctica/McMurdo # Cook Is # From Shanks & Pottenger: # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Cook 1978 only - Nov 12 0:00 0:30 HS +Rule Cook 1978 only - Nov 12 0:00 0:30 - Rule Cook 1979 1991 - Mar Sun>=1 0:00 0 - -Rule Cook 1979 1990 - Oct lastSun 0:00 0:30 HS +Rule Cook 1979 1990 - Oct lastSun 0:00 0:30 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Rarotonga -10:39:04 - LMT 1901 # Avarua -10:30 - -1030 1978 Nov 12 @@ -657,11 +657,11 @@ Link Pacific/Pago_Pago Pacific/Midway # in US minor outlying islands # Assume the pattern instituted in 2012 will continue indefinitely. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule WS 2010 only - Sep lastSun 0:00 1 D -Rule WS 2011 only - Apr Sat>=1 4:00 0 S -Rule WS 2011 only - Sep lastSat 3:00 1 D -Rule WS 2012 max - Apr Sun>=1 4:00 0 S -Rule WS 2012 max - Sep lastSun 3:00 1 D +Rule WS 2010 only - Sep lastSun 0:00 1 - +Rule WS 2011 only - Apr Sat>=1 4:00 0 - +Rule WS 2011 only - Sep lastSat 3:00 1 - +Rule WS 2012 max - Apr Sun>=1 4:00 0 - +Rule WS 2012 max - Sep lastSun 3:00 1 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Apia 12:33:04 - LMT 1892 Jul 5 -11:26:56 - LMT 1911 @@ -701,11 +701,11 @@ Zone Pacific/Fakaofo -11:24:56 - LMT 1901 # Tonga # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Tonga 1999 only - Oct 7 2:00s 1:00 S +Rule Tonga 1999 only - Oct 7 2:00s 1:00 - Rule Tonga 2000 only - Mar 19 2:00s 0 - -Rule Tonga 2000 2001 - Nov Sun>=1 2:00 1:00 S +Rule Tonga 2000 2001 - Nov Sun>=1 2:00 1:00 - Rule Tonga 2001 2002 - Jan lastSun 2:00 0 - -Rule Tonga 2016 only - Nov Sun>=1 2:00 1:00 S +Rule Tonga 2016 only - Nov Sun>=1 2:00 1:00 - Rule Tonga 2017 only - Jan Sun>=15 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tongatapu 12:19:20 - LMT 1901 @@ -782,12 +782,12 @@ Zone Pacific/Wake 11:06:28 - LMT 1901 # Vanuatu # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Vanuatu 1983 only - Sep 25 0:00 1:00 S +Rule Vanuatu 1983 only - Sep 25 0:00 1:00 - Rule Vanuatu 1984 1991 - Mar Sun>=23 0:00 0 - -Rule Vanuatu 1984 only - Oct 23 0:00 1:00 S -Rule Vanuatu 1985 1991 - Sep Sun>=23 0:00 1:00 S +Rule Vanuatu 1984 only - Oct 23 0:00 1:00 - +Rule Vanuatu 1985 1991 - Sep Sun>=23 0:00 1:00 - Rule Vanuatu 1992 1993 - Jan Sun>=23 0:00 0 - -Rule Vanuatu 1992 only - Oct Sun>=23 0:00 1:00 S +Rule Vanuatu 1992 only - Oct Sun>=23 0:00 1:00 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila 11:00 Vanuatu +11/+12 diff --git a/checktab.awk b/checktab.awk index 2397673..393ab19 100644 --- a/checktab.awk +++ b/checktab.awk @@ -126,6 +126,7 @@ $1 ~ /^#/ { next } if ($1 == "Zone") { tz = $2 ruleUsed[$4] = 1 + if ($5 ~ /%/) rulePercentUsed[$4] = 1 } else if ($1 == "Link" && zone_table == "zone.tab") { # Ignore Link commands if source and destination basenames # are identical, e.g. Europe/Istanbul versus Asia/Istanbul. @@ -136,8 +137,10 @@ $1 ~ /^#/ { next } if (src != dst) tz = $3 } else if ($1 == "Rule") { ruleDefined[$2] = 1 + if ($10 != "-") ruleLetters[$2] = 1 } else { ruleUsed[$2] = 1 + if ($3 ~ /%/) rulePercentUsed[$2] = 1 } if (tz && tz ~ /\//) { if (!tztab[tz]) { @@ -156,6 +159,12 @@ END { status = 1 } } + for (tz in ruleLetters) { + if (!rulePercentUsed[tz]) { + printf "%s: Rule contains letters never used\n", tz + status = 1 + } + } for (tz in tztab) { if (!zoneSeen[tz]) { printf "%s:%d: no Zone table for '%s'\n", \ diff --git a/europe b/europe index 5aeda33..76cbb5d 100644 --- a/europe +++ b/europe @@ -1539,21 +1539,21 @@ Zone Europe/Budapest 1:16:20 - LMT 1890 Oct # http://www.almanak.hi.is/klukkan.html # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Iceland 1917 1919 - Feb 19 23:00 1:00 S +Rule Iceland 1917 1919 - Feb 19 23:00 1:00 - Rule Iceland 1917 only - Oct 21 1:00 0 - Rule Iceland 1918 1919 - Nov 16 1:00 0 - -Rule Iceland 1921 only - Mar 19 23:00 1:00 S +Rule Iceland 1921 only - Mar 19 23:00 1:00 - Rule Iceland 1921 only - Jun 23 1:00 0 - -Rule Iceland 1939 only - Apr 29 23:00 1:00 S +Rule Iceland 1939 only - Apr 29 23:00 1:00 - Rule Iceland 1939 only - Oct 29 2:00 0 - -Rule Iceland 1940 only - Feb 25 2:00 1:00 S +Rule Iceland 1940 only - Feb 25 2:00 1:00 - Rule Iceland 1940 1941 - Nov Sun>=2 1:00s 0 - -Rule Iceland 1941 1942 - Mar Sun>=2 1:00s 1:00 S +Rule Iceland 1941 1942 - Mar Sun>=2 1:00s 1:00 - # 1943-1946 - first Sunday in March until first Sunday in winter -Rule Iceland 1943 1946 - Mar Sun>=1 1:00s 1:00 S +Rule Iceland 1943 1946 - Mar Sun>=1 1:00s 1:00 - Rule Iceland 1942 1948 - Oct Sun>=22 1:00s 0 - # 1947-1967 - first Sunday in April until first Sunday in winter -Rule Iceland 1947 1967 - Apr Sun>=1 1:00s 1:00 S +Rule Iceland 1947 1967 - Apr Sun>=1 1:00s 1:00 - # 1949 and 1967 Oct transitions delayed by 1 week Rule Iceland 1949 only - Oct 30 1:00s 0 - Rule Iceland 1950 1966 - Oct Sun>=22 1:00s 0 - diff --git a/southamerica b/southamerica index bcfde4b..e1c6590 100644 --- a/southamerica +++ b/southamerica @@ -47,28 +47,28 @@ # AR was chosen because they are the ISO letters that represent Argentina. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Arg 1930 only - Dec 1 0:00 1:00 S +Rule Arg 1930 only - Dec 1 0:00 1:00 - Rule Arg 1931 only - Apr 1 0:00 0 - -Rule Arg 1931 only - Oct 15 0:00 1:00 S +Rule Arg 1931 only - Oct 15 0:00 1:00 - Rule Arg 1932 1940 - Mar 1 0:00 0 - -Rule Arg 1932 1939 - Nov 1 0:00 1:00 S -Rule Arg 1940 only - Jul 1 0:00 1:00 S +Rule Arg 1932 1939 - Nov 1 0:00 1:00 - +Rule Arg 1940 only - Jul 1 0:00 1:00 - Rule Arg 1941 only - Jun 15 0:00 0 - -Rule Arg 1941 only - Oct 15 0:00 1:00 S +Rule Arg 1941 only - Oct 15 0:00 1:00 - Rule Arg 1943 only - Aug 1 0:00 0 - -Rule Arg 1943 only - Oct 15 0:00 1:00 S +Rule Arg 1943 only - Oct 15 0:00 1:00 - Rule Arg 1946 only - Mar 1 0:00 0 - -Rule Arg 1946 only - Oct 1 0:00 1:00 S +Rule Arg 1946 only - Oct 1 0:00 1:00 - Rule Arg 1963 only - Oct 1 0:00 0 - -Rule Arg 1963 only - Dec 15 0:00 1:00 S +Rule Arg 1963 only - Dec 15 0:00 1:00 - Rule Arg 1964 1966 - Mar 1 0:00 0 - -Rule Arg 1964 1966 - Oct 15 0:00 1:00 S +Rule Arg 1964 1966 - Oct 15 0:00 1:00 - Rule Arg 1967 only - Apr 2 0:00 0 - -Rule Arg 1967 1968 - Oct Sun>=1 0:00 1:00 S +Rule Arg 1967 1968 - Oct Sun>=1 0:00 1:00 - Rule Arg 1968 1969 - Apr Sun>=1 0:00 0 - -Rule Arg 1974 only - Jan 23 0:00 1:00 S +Rule Arg 1974 only - Jan 23 0:00 1:00 - Rule Arg 1974 only - May 1 0:00 0 - -Rule Arg 1988 only - Dec 1 0:00 1:00 S +Rule Arg 1988 only - Dec 1 0:00 1:00 - # # From Hernan G. Otero (1995-06-26): # These corrections were contributed by InterSoft Argentina S.A., @@ -76,7 +76,7 @@ Rule Arg 1988 only - Dec 1 0:00 1:00 S # Talleres de Hidrografía Naval Argentina # (Argentine Naval Hydrography Institute) Rule Arg 1989 1993 - Mar Sun>=1 0:00 0 - -Rule Arg 1989 1992 - Oct Sun>=15 0:00 1:00 S +Rule Arg 1989 1992 - Oct Sun>=15 0:00 1:00 - # # From Hernan G. Otero (1995-06-26): # From this moment on, the law that mandated the daylight saving @@ -87,7 +87,7 @@ Rule Arg 1989 1992 - Oct Sun>=15 0:00 1:00 S # On October 3, 1999, 0:00 local, Argentina implemented daylight savings time, # which did not result in the switch of a time zone, as they stayed 9 hours # from the International Date Line. -Rule Arg 1999 only - Oct Sun>=1 0:00 1:00 S +Rule Arg 1999 only - Oct Sun>=1 0:00 1:00 - # From Paul Eggert (2007-12-28): # DST was set to expire on March 5, not March 3, but since it was converted # to standard time on March 3 it's more convenient for us to pretend that @@ -190,9 +190,9 @@ Rule Arg 2000 only - Mar 3 0:00 0 - # la modificación del huso horario, ya que 2009 nos encuentra con # crecimiento en la producción y distribución energética." -Rule Arg 2007 only - Dec 30 0:00 1:00 S +Rule Arg 2007 only - Dec 30 0:00 1:00 - Rule Arg 2008 2009 - Mar Sun>=15 0:00 0 - -Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S +Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 - # From Mariano Absatz (2004-05-21): # Today it was officially published that the Province of Mendoza is changing @@ -529,7 +529,7 @@ Zone America/Argentina/Mendoza -4:35:16 - LMT 1894 Oct 31 # San Luis (SL) Rule SanLuis 2008 2009 - Mar Sun>=8 0:00 0 - -Rule SanLuis 2007 2008 - Oct Sun>=8 0:00 1:00 S +Rule SanLuis 2007 2008 - Oct Sun>=8 0:00 1:00 - Zone America/Argentina/San_Luis -4:25:24 - LMT 1894 Oct 31 -4:16:48 - CMT 1920 May @@ -771,14 +771,14 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Decree 20,466 <http://pcdsh01.on.br/HV20466.htm> (1931-10-01) # Decree 21,896 <http://pcdsh01.on.br/HV21896.htm> (1932-01-10) -Rule Brazil 1931 only - Oct 3 11:00 1:00 S +Rule Brazil 1931 only - Oct 3 11:00 1:00 - Rule Brazil 1932 1933 - Apr 1 0:00 0 - -Rule Brazil 1932 only - Oct 3 0:00 1:00 S +Rule Brazil 1932 only - Oct 3 0:00 1:00 - # Decree 23,195 <http://pcdsh01.on.br/HV23195.htm> (1933-10-10) # revoked DST. # Decree 27,496 <http://pcdsh01.on.br/HV27496.htm> (1949-11-24) # Decree 27,998 <http://pcdsh01.on.br/HV27998.htm> (1950-04-13) -Rule Brazil 1949 1952 - Dec 1 0:00 1:00 S +Rule Brazil 1949 1952 - Dec 1 0:00 1:00 - Rule Brazil 1950 only - Apr 16 1:00 0 - Rule Brazil 1951 1952 - Apr 1 0:00 0 - # Decree 32,308 <http://pcdsh01.on.br/HV32308.htm> (1953-02-24) @@ -790,51 +790,51 @@ Rule Brazil 1953 only - Mar 1 0:00 0 - # in SP, RJ, GB, MG, ES, due to the prolongation of the drought. # Decree 53,071 <http://pcdsh01.on.br/HV53071.htm> (1963-12-03) # extended the above decree to all of the national territory on 12-09. -Rule Brazil 1963 only - Dec 9 0:00 1:00 S +Rule Brazil 1963 only - Dec 9 0:00 1:00 - # Decree 53,604 <http://pcdsh01.on.br/HV53604.htm> (1964-02-25) # extended summer time by one day to 1964-03-01 00:00 (start of school). Rule Brazil 1964 only - Mar 1 0:00 0 - # Decree 55,639 <http://pcdsh01.on.br/HV55639.htm> (1965-01-27) -Rule Brazil 1965 only - Jan 31 0:00 1:00 S +Rule Brazil 1965 only - Jan 31 0:00 1:00 - Rule Brazil 1965 only - Mar 31 0:00 0 - # Decree 57,303 <http://pcdsh01.on.br/HV57303.htm> (1965-11-22) -Rule Brazil 1965 only - Dec 1 0:00 1:00 S +Rule Brazil 1965 only - Dec 1 0:00 1:00 - # Decree 57,843 <http://pcdsh01.on.br/HV57843.htm> (1966-02-18) Rule Brazil 1966 1968 - Mar 1 0:00 0 - -Rule Brazil 1966 1967 - Nov 1 0:00 1:00 S +Rule Brazil 1966 1967 - Nov 1 0:00 1:00 - # Decree 63,429 <http://pcdsh01.on.br/HV63429.htm> (1968-10-15) # revoked DST. # Decree 91,698 <http://pcdsh01.on.br/HV91698.htm> (1985-09-27) -Rule Brazil 1985 only - Nov 2 0:00 1:00 S +Rule Brazil 1985 only - Nov 2 0:00 1:00 - # Decree 92,310 (1986-01-21) # Decree 92,463 (1986-03-13) Rule Brazil 1986 only - Mar 15 0:00 0 - # Decree 93,316 (1986-10-01) -Rule Brazil 1986 only - Oct 25 0:00 1:00 S +Rule Brazil 1986 only - Oct 25 0:00 1:00 - Rule Brazil 1987 only - Feb 14 0:00 0 - # Decree 94,922 <http://pcdsh01.on.br/HV94922.htm> (1987-09-22) -Rule Brazil 1987 only - Oct 25 0:00 1:00 S +Rule Brazil 1987 only - Oct 25 0:00 1:00 - Rule Brazil 1988 only - Feb 7 0:00 0 - # Decree 96,676 <http://pcdsh01.on.br/HV96676.htm> (1988-09-12) # except for the states of AC, AM, PA, RR, RO, and AP (then a territory) -Rule Brazil 1988 only - Oct 16 0:00 1:00 S +Rule Brazil 1988 only - Oct 16 0:00 1:00 - Rule Brazil 1989 only - Jan 29 0:00 0 - # Decree 98,077 <http://pcdsh01.on.br/HV98077.htm> (1989-08-21) # with the same exceptions -Rule Brazil 1989 only - Oct 15 0:00 1:00 S +Rule Brazil 1989 only - Oct 15 0:00 1:00 - Rule Brazil 1990 only - Feb 11 0:00 0 - # Decree 99,530 <http://pcdsh01.on.br/HV99530.htm> (1990-09-17) # adopted by RS, SC, PR, SP, RJ, ES, MG, GO, MS, DF. # Decree 99,629 (1990-10-19) adds BA, MT. -Rule Brazil 1990 only - Oct 21 0:00 1:00 S +Rule Brazil 1990 only - Oct 21 0:00 1:00 - Rule Brazil 1991 only - Feb 17 0:00 0 - # Unnumbered decree <http://pcdsh01.on.br/HV1991.htm> (1991-09-25) # adopted by RS, SC, PR, SP, RJ, ES, MG, BA, GO, MT, MS, DF. -Rule Brazil 1991 only - Oct 20 0:00 1:00 S +Rule Brazil 1991 only - Oct 20 0:00 1:00 - Rule Brazil 1992 only - Feb 9 0:00 0 - # Unnumbered decree <http://pcdsh01.on.br/HV1992.htm> (1992-10-16) # adopted by same states. -Rule Brazil 1992 only - Oct 25 0:00 1:00 S +Rule Brazil 1992 only - Oct 25 0:00 1:00 - Rule Brazil 1993 only - Jan 31 0:00 0 - # Decree 942 <http://pcdsh01.on.br/HV942.htm> (1993-09-28) # adopted by same states, plus AM. @@ -844,12 +844,12 @@ Rule Brazil 1993 only - Jan 31 0:00 0 - # adopted by same states, plus MT and TO. # Decree 1,674 <http://pcdsh01.on.br/HV1674.htm> (1995-10-13) # adds AL, SE. -Rule Brazil 1993 1995 - Oct Sun>=11 0:00 1:00 S +Rule Brazil 1993 1995 - Oct Sun>=11 0:00 1:00 - Rule Brazil 1994 1995 - Feb Sun>=15 0:00 0 - Rule Brazil 1996 only - Feb 11 0:00 0 - # Decree 2,000 <http://pcdsh01.on.br/HV2000.htm> (1996-09-04) # adopted by same states, minus AL, SE. -Rule Brazil 1996 only - Oct 6 0:00 1:00 S +Rule Brazil 1996 only - Oct 6 0:00 1:00 - Rule Brazil 1997 only - Feb 16 0:00 0 - # From Daniel C. Sobral (1998-02-12): # In 1997, the DS began on October 6. The stated reason was that @@ -859,19 +859,19 @@ Rule Brazil 1997 only - Feb 16 0:00 0 - # to help dealing with the shortages of electric power. # # Decree 2,317 (1997-09-04), adopted by same states. -Rule Brazil 1997 only - Oct 6 0:00 1:00 S +Rule Brazil 1997 only - Oct 6 0:00 1:00 - # Decree 2,495 <http://pcdsh01.on.br/figuras/HV2495.JPG> # (1998-02-10) Rule Brazil 1998 only - Mar 1 0:00 0 - # Decree 2,780 <http://pcdsh01.on.br/figuras/Hv98.jpg> (1998-09-11) # adopted by the same states as before. -Rule Brazil 1998 only - Oct 11 0:00 1:00 S +Rule Brazil 1998 only - Oct 11 0:00 1:00 - Rule Brazil 1999 only - Feb 21 0:00 0 - # Decree 3,150 <http://pcdsh01.on.br/figuras/HV3150.gif> # (1999-08-23) adopted by same states. # Decree 3,188 <http://pcdsh01.on.br/DecHV99.gif> (1999-09-30) # adds SE, AL, PB, PE, RN, CE, PI, MA and RR. -Rule Brazil 1999 only - Oct 3 0:00 1:00 S +Rule Brazil 1999 only - Oct 3 0:00 1:00 - Rule Brazil 2000 only - Feb 27 0:00 0 - # Decree 3,592 <http://pcdsh01.on.br/DEC3592.htm> (2000-09-06) # adopted by the same states as before. @@ -881,34 +881,34 @@ Rule Brazil 2000 only - Feb 27 0:00 0 - # repeals DST in SE, AL, PB, RN, CE, PI and MA, effective 2000-10-22 00:00. # Decree 3,916 <http://pcdsh01.on.br/figuras/HV3916.gif> # (2001-09-13) reestablishes DST in AL, CE, MA, PB, PE, PI, RN, SE. -Rule Brazil 2000 2001 - Oct Sun>=8 0:00 1:00 S +Rule Brazil 2000 2001 - Oct Sun>=8 0:00 1:00 - Rule Brazil 2001 2006 - Feb Sun>=15 0:00 0 - # Decree 4,399 (2002-10-01) repeals DST in AL, CE, MA, PB, PE, PI, RN, SE. # 4,399 <http://www.presidencia.gov.br/CCIVIL/decreto/2002/D4399.htm> -Rule Brazil 2002 only - Nov 3 0:00 1:00 S +Rule Brazil 2002 only - Nov 3 0:00 1:00 - # Decree 4,844 (2003-09-24; corrected 2003-09-26) repeals DST in BA, MT, TO. # 4,844 <http://www.presidencia.gov.br/CCIVIL/decreto/2003/D4844.htm> -Rule Brazil 2003 only - Oct 19 0:00 1:00 S +Rule Brazil 2003 only - Oct 19 0:00 1:00 - # Decree 5,223 (2004-10-01) reestablishes DST in MT. # 5,223 <http://www.planalto.gov.br/ccivil_03/_Ato2004-2006/2004/Decreto/D5223.htm> -Rule Brazil 2004 only - Nov 2 0:00 1:00 S +Rule Brazil 2004 only - Nov 2 0:00 1:00 - # Decree 5,539 <http://pcdsh01.on.br/DecHV5539.gif> (2005-09-19), # adopted by the same states as before. -Rule Brazil 2005 only - Oct 16 0:00 1:00 S +Rule Brazil 2005 only - Oct 16 0:00 1:00 - # Decree 5,920 <http://pcdsh01.on.br/DecHV5920.gif> (2006-10-03), # adopted by the same states as before. -Rule Brazil 2006 only - Nov 5 0:00 1:00 S +Rule Brazil 2006 only - Nov 5 0:00 1:00 - Rule Brazil 2007 only - Feb 25 0:00 0 - # Decree 6,212 <http://pcdsh01.on.br/DecHV6212.gif> (2007-09-26), # adopted by the same states as before. -Rule Brazil 2007 only - Oct Sun>=8 0:00 1:00 S +Rule Brazil 2007 only - Oct Sun>=8 0:00 1:00 - # From Frederico A. C. Neves (2008-09-10): # According to this decree # http://www.planalto.gov.br/ccivil_03/_Ato2007-2010/2008/Decreto/D6558.htm # [t]he DST period in Brazil now on will be from the 3rd Oct Sunday to the # 3rd Feb Sunday. There is an exception on the return date when this is # the Carnival Sunday then the return date will be the next Sunday... -Rule Brazil 2008 2017 - Oct Sun>=15 0:00 1:00 S +Rule Brazil 2008 2017 - Oct Sun>=15 0:00 1:00 - Rule Brazil 2008 2011 - Feb Sun>=15 0:00 0 - # Decree 7,584 <http://pcdsh01.on.br/HVdecreto7584_20111013.jpg> (2011-10-13) # added Bahia. @@ -926,7 +926,7 @@ Rule Brazil 2016 2022 - Feb Sun>=15 0:00 0 - # ... https://www.timeanddate.com/news/time/brazil-delays-dst-2018.html # From Steffen Thorsen (2017-12-20): # http://www.planalto.gov.br/ccivil_03/_ato2015-2018/2017/decreto/D9242.htm -Rule Brazil 2018 max - Nov Sun>=1 0:00 1:00 S +Rule Brazil 2018 max - Nov Sun>=1 0:00 1:00 - Rule Brazil 2023 only - Feb Sun>=22 0:00 0 - Rule Brazil 2024 2025 - Feb Sun>=15 0:00 0 - Rule Brazil 2026 only - Feb Sun>=22 0:00 0 - @@ -1233,28 +1233,28 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # For now, assume that they will not revert. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Chile 1927 1931 - Sep 1 0:00 1:00 S +Rule Chile 1927 1931 - Sep 1 0:00 1:00 - Rule Chile 1928 1932 - Apr 1 0:00 0 - -Rule Chile 1968 only - Nov 3 4:00u 1:00 S +Rule Chile 1968 only - Nov 3 4:00u 1:00 - Rule Chile 1969 only - Mar 30 3:00u 0 - -Rule Chile 1969 only - Nov 23 4:00u 1:00 S +Rule Chile 1969 only - Nov 23 4:00u 1:00 - Rule Chile 1970 only - Mar 29 3:00u 0 - Rule Chile 1971 only - Mar 14 3:00u 0 - -Rule Chile 1970 1972 - Oct Sun>=9 4:00u 1:00 S +Rule Chile 1970 1972 - Oct Sun>=9 4:00u 1:00 - Rule Chile 1972 1986 - Mar Sun>=9 3:00u 0 - -Rule Chile 1973 only - Sep 30 4:00u 1:00 S -Rule Chile 1974 1987 - Oct Sun>=9 4:00u 1:00 S +Rule Chile 1973 only - Sep 30 4:00u 1:00 - +Rule Chile 1974 1987 - Oct Sun>=9 4:00u 1:00 - Rule Chile 1987 only - Apr 12 3:00u 0 - Rule Chile 1988 1990 - Mar Sun>=9 3:00u 0 - -Rule Chile 1988 1989 - Oct Sun>=9 4:00u 1:00 S -Rule Chile 1990 only - Sep 16 4:00u 1:00 S +Rule Chile 1988 1989 - Oct Sun>=9 4:00u 1:00 - +Rule Chile 1990 only - Sep 16 4:00u 1:00 - Rule Chile 1991 1996 - Mar Sun>=9 3:00u 0 - -Rule Chile 1991 1997 - Oct Sun>=9 4:00u 1:00 S +Rule Chile 1991 1997 - Oct Sun>=9 4:00u 1:00 - Rule Chile 1997 only - Mar 30 3:00u 0 - Rule Chile 1998 only - Mar Sun>=9 3:00u 0 - -Rule Chile 1998 only - Sep 27 4:00u 1:00 S +Rule Chile 1998 only - Sep 27 4:00u 1:00 - Rule Chile 1999 only - Apr 4 3:00u 0 - -Rule Chile 1999 2010 - Oct Sun>=9 4:00u 1:00 S +Rule Chile 1999 2010 - Oct Sun>=9 4:00u 1:00 - Rule Chile 2000 2007 - Mar Sun>=9 3:00u 0 - # N.B.: the end of March 29 in Chile is March 30 in Universal time, # which is used below in specifying the transition. @@ -1262,11 +1262,11 @@ Rule Chile 2008 only - Mar 30 3:00u 0 - Rule Chile 2009 only - Mar Sun>=9 3:00u 0 - Rule Chile 2010 only - Apr Sun>=1 3:00u 0 - Rule Chile 2011 only - May Sun>=2 3:00u 0 - -Rule Chile 2011 only - Aug Sun>=16 4:00u 1:00 S +Rule Chile 2011 only - Aug Sun>=16 4:00u 1:00 - Rule Chile 2012 2014 - Apr Sun>=23 3:00u 0 - -Rule Chile 2012 2014 - Sep Sun>=2 4:00u 1:00 S +Rule Chile 2012 2014 - Sep Sun>=2 4:00u 1:00 - Rule Chile 2016 max - May Sun>=9 3:00u 0 - -Rule Chile 2016 max - Aug Sun>=9 4:00u 1:00 S +Rule Chile 2016 max - Aug Sun>=9 4:00u 1:00 - # IATA SSIM anomalies: (1992-02) says 1992-03-14; # (1996-09) says 1998-03-08. Ignore these. # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1331,7 +1331,7 @@ Zone Antarctica/Palmer 0 - -00 1965 # "A variation of fifteen minutes in the public clocks of Bogota is not rare." # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule CO 1992 only - May 3 0:00 1:00 S +Rule CO 1992 only - May 3 0:00 1:00 - Rule CO 1993 only - Apr 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:16 - LMT 1884 Mar 13 @@ -1391,7 +1391,7 @@ Link America/Curacao America/Kralendijk # Caribbean Netherlands # repeated. For now, assume transitions were at 00:00 local time country-wide. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Ecuador 1992 only - Nov 28 0:00 1:00 S +Rule Ecuador 1992 only - Nov 28 0:00 1:00 - Rule Ecuador 1993 only - Feb 5 0:00 0 - # # Zone NAME GMTOFF RULES FORMAT [UNTIL] @@ -1485,18 +1485,18 @@ Zone Pacific/Galapagos -5:58:24 - LMT 1931 # Puerto Baquerizo Moreno # until advised differently (to apply for 2012 and beyond, after the 2011 # experiment was apparently successful.) # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Falk 1937 1938 - Sep lastSun 0:00 1:00 S +Rule Falk 1937 1938 - Sep lastSun 0:00 1:00 - Rule Falk 1938 1942 - Mar Sun>=19 0:00 0 - -Rule Falk 1939 only - Oct 1 0:00 1:00 S -Rule Falk 1940 1942 - Sep lastSun 0:00 1:00 S +Rule Falk 1939 only - Oct 1 0:00 1:00 - +Rule Falk 1940 1942 - Sep lastSun 0:00 1:00 - Rule Falk 1943 only - Jan 1 0:00 0 - -Rule Falk 1983 only - Sep lastSun 0:00 1:00 S +Rule Falk 1983 only - Sep lastSun 0:00 1:00 - Rule Falk 1984 1985 - Apr lastSun 0:00 0 - -Rule Falk 1984 only - Sep 16 0:00 1:00 S -Rule Falk 1985 2000 - Sep Sun>=9 0:00 1:00 S +Rule Falk 1984 only - Sep 16 0:00 1:00 - +Rule Falk 1985 2000 - Sep Sun>=9 0:00 1:00 - Rule Falk 1986 2000 - Apr Sun>=16 0:00 0 - Rule Falk 2001 2010 - Apr Sun>=15 2:00 0 - -Rule Falk 2001 2010 - Sep Sun>=1 2:00 1:00 S +Rule Falk 2001 2010 - Sep Sun>=1 2:00 1:00 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 -3:51:24 - SMT 1912 Mar 12 # Stanley Mean Time @@ -1531,16 +1531,16 @@ Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown # adjust their clocks at 0 hour of the given dates. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Para 1975 1988 - Oct 1 0:00 1:00 S +Rule Para 1975 1988 - Oct 1 0:00 1:00 - Rule Para 1975 1978 - Mar 1 0:00 0 - Rule Para 1979 1991 - Apr 1 0:00 0 - -Rule Para 1989 only - Oct 22 0:00 1:00 S -Rule Para 1990 only - Oct 1 0:00 1:00 S -Rule Para 1991 only - Oct 6 0:00 1:00 S +Rule Para 1989 only - Oct 22 0:00 1:00 - +Rule Para 1990 only - Oct 1 0:00 1:00 - +Rule Para 1991 only - Oct 6 0:00 1:00 - Rule Para 1992 only - Mar 1 0:00 0 - -Rule Para 1992 only - Oct 5 0:00 1:00 S +Rule Para 1992 only - Oct 5 0:00 1:00 - Rule Para 1993 only - Mar 31 0:00 0 - -Rule Para 1993 1995 - Oct 1 0:00 1:00 S +Rule Para 1993 1995 - Oct 1 0:00 1:00 - Rule Para 1994 1995 - Feb lastSun 0:00 0 - Rule Para 1996 only - Mar 1 0:00 0 - # IATA SSIM (2000-02) says 1999-10-10; ignore this for now. @@ -1558,7 +1558,7 @@ Rule Para 1996 only - Mar 1 0:00 0 - # year, the time will change on the first Sunday of October; likewise, the # clock will be set back on the first Sunday of March. # -Rule Para 1996 2001 - Oct Sun>=1 0:00 1:00 S +Rule Para 1996 2001 - Oct Sun>=1 0:00 1:00 - # IATA SSIM (1997-09) says Mar 1; go with Shanks & Pottenger. Rule Para 1997 only - Feb lastSun 0:00 0 - # Shanks & Pottenger say 1999-02-28; IATA SSIM (1999-02) says 1999-02-27, but @@ -1569,7 +1569,7 @@ Rule Para 1998 2001 - Mar Sun>=1 0:00 0 - # dst method to be from the first Sunday in September to the first Sunday in # April. Rule Para 2002 2004 - Apr Sun>=1 0:00 0 - -Rule Para 2002 2003 - Sep Sun>=1 0:00 1:00 S +Rule Para 2002 2003 - Sep Sun>=1 0:00 1:00 - # # From Jesper Nørgaard Welen (2005-01-02): # There are several sources that claim that Paraguay made @@ -1578,7 +1578,7 @@ Rule Para 2002 2003 - Sep Sun>=1 0:00 1:00 S # Decree 1,867 (2004-03-05) # From Carlos Raúl Perasso via Jesper Nørgaard Welen (2006-10-13) # http://www.presidencia.gov.py/decretos/D1867.pdf -Rule Para 2004 2009 - Oct Sun>=15 0:00 1:00 S +Rule Para 2004 2009 - Oct Sun>=15 0:00 1:00 - Rule Para 2005 2009 - Mar Sun>=8 0:00 0 - # From Carlos Raúl Perasso (2010-02-18): # By decree number 3958 issued yesterday @@ -1591,7 +1591,7 @@ Rule Para 2005 2009 - Mar Sun>=8 0:00 0 - # and that on the first Sunday of the month of October, it is to be set # forward 60 minutes, in all the territory of the Paraguayan Republic. # ... -Rule Para 2010 max - Oct Sun>=1 0:00 1:00 S +Rule Para 2010 max - Oct Sun>=1 0:00 1:00 - Rule Para 2010 2012 - Apr Sun>=8 0:00 0 - # # From Steffen Thorsen (2013-03-07): @@ -1624,16 +1624,16 @@ Zone America/Asuncion -3:50:40 - LMT 1890 # Shanks & Pottenger don't have this transition. Assume 1986 was like 1987. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Peru 1938 only - Jan 1 0:00 1:00 S +Rule Peru 1938 only - Jan 1 0:00 1:00 - Rule Peru 1938 only - Apr 1 0:00 0 - -Rule Peru 1938 1939 - Sep lastSun 0:00 1:00 S +Rule Peru 1938 1939 - Sep lastSun 0:00 1:00 - Rule Peru 1939 1940 - Mar Sun>=24 0:00 0 - -Rule Peru 1986 1987 - Jan 1 0:00 1:00 S +Rule Peru 1986 1987 - Jan 1 0:00 1:00 - Rule Peru 1986 1987 - Apr 1 0:00 0 - -Rule Peru 1990 only - Jan 1 0:00 1:00 S +Rule Peru 1990 only - Jan 1 0:00 1:00 - Rule Peru 1990 only - Apr 1 0:00 0 - # IATA is ambiguous for 1993/1995; go with Shanks & Pottenger. -Rule Peru 1994 only - Jan 1 0:00 1:00 S +Rule Peru 1994 only - Jan 1 0:00 1:00 - Rule Peru 1994 only - Apr 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Lima -5:08:12 - LMT 1890 @@ -1682,55 +1682,55 @@ Link America/Port_of_Spain America/Tortola # Virgin Islands (UK) # From Shanks & Pottenger: # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1923 Oct 1; go with Shanks & Pottenger. -Rule Uruguay 1923 only - Oct 2 0:00 0:30 HS +Rule Uruguay 1923 only - Oct 2 0:00 0:30 - Rule Uruguay 1924 1926 - Apr 1 0:00 0 - -Rule Uruguay 1924 1925 - Oct 1 0:00 0:30 HS -Rule Uruguay 1933 1935 - Oct lastSun 0:00 0:30 HS +Rule Uruguay 1924 1925 - Oct 1 0:00 0:30 - +Rule Uruguay 1933 1935 - Oct lastSun 0:00 0:30 - # Shanks & Pottenger give 1935 Apr 1 0:00 & 1936 Mar 30 0:00; go with Whitman. Rule Uruguay 1934 1936 - Mar Sat>=25 23:30s 0 - -Rule Uruguay 1936 only - Nov 1 0:00 0:30 HS +Rule Uruguay 1936 only - Nov 1 0:00 0:30 - Rule Uruguay 1937 1941 - Mar lastSun 0:00 0 - # Whitman gives 1937 Oct 3; go with Shanks & Pottenger. -Rule Uruguay 1937 1940 - Oct lastSun 0:00 0:30 HS +Rule Uruguay 1937 1940 - Oct lastSun 0:00 0:30 - # Whitman gives 1941 Oct 24 - 1942 Mar 27, 1942 Dec 14 - 1943 Apr 13, # and 1943 Apr 13 "to present time"; go with Shanks & Pottenger. -Rule Uruguay 1941 only - Aug 1 0:00 0:30 HS +Rule Uruguay 1941 only - Aug 1 0:00 0:30 - Rule Uruguay 1942 only - Jan 1 0:00 0 - -Rule Uruguay 1942 only - Dec 14 0:00 1:00 S +Rule Uruguay 1942 only - Dec 14 0:00 1:00 - Rule Uruguay 1943 only - Mar 14 0:00 0 - -Rule Uruguay 1959 only - May 24 0:00 1:00 S +Rule Uruguay 1959 only - May 24 0:00 1:00 - Rule Uruguay 1959 only - Nov 15 0:00 0 - -Rule Uruguay 1960 only - Jan 17 0:00 1:00 S +Rule Uruguay 1960 only - Jan 17 0:00 1:00 - Rule Uruguay 1960 only - Mar 6 0:00 0 - -Rule Uruguay 1965 1967 - Apr Sun>=1 0:00 1:00 S +Rule Uruguay 1965 1967 - Apr Sun>=1 0:00 1:00 - Rule Uruguay 1965 only - Sep 26 0:00 0 - Rule Uruguay 1966 1967 - Oct 31 0:00 0 - -Rule Uruguay 1968 1970 - May 27 0:00 0:30 HS +Rule Uruguay 1968 1970 - May 27 0:00 0:30 - Rule Uruguay 1968 1970 - Dec 2 0:00 0 - -Rule Uruguay 1972 only - Apr 24 0:00 1:00 S +Rule Uruguay 1972 only - Apr 24 0:00 1:00 - Rule Uruguay 1972 only - Aug 15 0:00 0 - -Rule Uruguay 1974 only - Mar 10 0:00 0:30 HS -Rule Uruguay 1974 only - Dec 22 0:00 1:00 S +Rule Uruguay 1974 only - Mar 10 0:00 0:30 - +Rule Uruguay 1974 only - Dec 22 0:00 1:00 - Rule Uruguay 1976 only - Oct 1 0:00 0 - -Rule Uruguay 1977 only - Dec 4 0:00 1:00 S +Rule Uruguay 1977 only - Dec 4 0:00 1:00 - Rule Uruguay 1978 only - Apr 1 0:00 0 - -Rule Uruguay 1979 only - Oct 1 0:00 1:00 S +Rule Uruguay 1979 only - Oct 1 0:00 1:00 - Rule Uruguay 1980 only - May 1 0:00 0 - -Rule Uruguay 1987 only - Dec 14 0:00 1:00 S +Rule Uruguay 1987 only - Dec 14 0:00 1:00 - Rule Uruguay 1988 only - Mar 14 0:00 0 - -Rule Uruguay 1988 only - Dec 11 0:00 1:00 S +Rule Uruguay 1988 only - Dec 11 0:00 1:00 - Rule Uruguay 1989 only - Mar 12 0:00 0 - -Rule Uruguay 1989 only - Oct 29 0:00 1:00 S +Rule Uruguay 1989 only - Oct 29 0:00 1:00 - # Shanks & Pottenger say no DST was observed in 1990/1 and 1991/2, # and that 1992/3's DST was from 10-25 to 03-01. Go with IATA. Rule Uruguay 1990 1992 - Mar Sun>=1 0:00 0 - -Rule Uruguay 1990 1991 - Oct Sun>=21 0:00 1:00 S -Rule Uruguay 1992 only - Oct 18 0:00 1:00 S +Rule Uruguay 1990 1991 - Oct Sun>=21 0:00 1:00 - +Rule Uruguay 1992 only - Oct 18 0:00 1:00 - Rule Uruguay 1993 only - Feb 28 0:00 0 - # From Eduardo Cota (2004-09-20): # The Uruguayan government has decreed a change in the local time.... # http://www.presidencia.gub.uy/decretos/2004091502.htm -Rule Uruguay 2004 only - Sep 19 0:00 1:00 S +Rule Uruguay 2004 only - Sep 19 0:00 1:00 - # From Steffen Thorsen (2005-03-11): # Uruguay's DST was scheduled to end on Sunday, 2005-03-13, but in order to # save energy ... it was postponed two weeks.... @@ -1740,7 +1740,7 @@ Rule Uruguay 2005 only - Mar 27 2:00 0 - # http://www.presidencia.gub.uy/_Web/decretos/2005/09/CM%20119_09%2009%202005… # This means that from 2005-10-09 at 02:00 local time, until 2006-03-12 at # 02:00 local time, official time in Uruguay will be at GMT -2. -Rule Uruguay 2005 only - Oct 9 2:00 1:00 S +Rule Uruguay 2005 only - Oct 9 2:00 1:00 - Rule Uruguay 2006 only - Mar 12 2:00 0 - # From Jesper Nørgaard Welen (2006-09-06): # http://www.presidencia.gub.uy/_web/decretos/2006/09/CM%20210_08%2006%202006… @@ -1755,7 +1755,7 @@ Rule Uruguay 2006 only - Mar 12 2:00 0 - # From Pablo Camargo (2015-07-13): # http://archivo.presidencia.gub.uy/sci/decretos/2015/06/cons_min_201.pdf # [dated 2015-06-29; repeals Decree 311/006 dated 2006-09-04] -Rule Uruguay 2006 2014 - Oct Sun>=1 2:00 1:00 S +Rule Uruguay 2006 2014 - Oct Sun>=1 2:00 1:00 - Rule Uruguay 2007 2015 - Mar Sun>=8 2:00 0 - # This Zone can be simplified once we assume zic %z. -- 2.14.3

1 0

[PROPOSED] Add notes about Ghana confusion
by Paul Eggert Jan. 30, 2018

Jan. 30, 2018

* africa (Ghana): Add commentary about what little is known about time near Accra from 1919 through 1942. Every source seems to differ. For now, leave the data alone. It would be nice if someone could get to the bottom of this. --- africa | 31 +++++++++++++++++++++++++------ 1 file changed, 25 insertions(+), 6 deletions(-) diff --git a/africa b/africa index 02115ad..6e86d21 100644 --- a/africa +++ b/africa @@ -370,13 +370,32 @@ Zone Africa/Cairo 2:05:09 - LMT 1900 Oct # See Africa/Abidjan. # Ghana -# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + +# From Paul Eggert (2019-01-30): # Whitman says DST was observed from 1931 to "the present"; -# Shanks & Pottenger say 1936 to 1942; -# and September 1 to January 1 is given by: -# Scott Keltie J, Epstein M (eds), The Statesman's Year-Book, -# 57th ed. Macmillan, London (1920), OCLC 609408015, pp xxviii. -# For lack of better info, assume DST was observed from 1920 to 1942. +# Shanks & Pottenger say 1936 to 1942 with 20 minutes of DST, +# with transitions on 09-01 and 12-31 at 00:00. +# Page 33 of Parish GCB, Colonial Reports - Annual. No. 1066. Gold +# Coast. Report for 1919. (March 1921), OCLC 784024077 +# http://libsysdigi.library.illinois.edu/ilharvest/africana/books2011-05/5530… +# lists the Determination of the Time Ordinance, 1919, No. 18, +# "to advance the time observed locally by the space of twenty minutes +# during the last four months of each year; the object in view being +# to extend during those months the period of daylight-time available +# for evening recreation after office hours." +# Vanessa Ogle, The Global Transformation of Time, 1870-1950 (2015), p 33, +# writes "In 1919, the Gold Coast (Ghana as of 1957) made Greenwich +# time its legal time and simultaneously legalized a summer time of +# UTC - 00:20 minutes from March to October."; a footnote lists +# the ordinance as being dated 1919-11-24. +# The Crown Colonist, Volume 12 (1942), p 176, says "the Government +# intend advancing Gold Coast time half an hour ahead of G.M.T. +# The actual date of the alteration has not yet been announced." +# These sources are incomplete and contradictory. Possibly what is +# now Ghana observed different DST regimes in different years. For +# lack of better info, use Shanks except treat the minus sign as a +# typo, and assume DST started in 1920 not 1936. +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Ghana 1920 1942 - Sep 1 0:00 0:20 GHST Rule Ghana 1920 1942 - Dec 31 0:00 0 GMT # Zone NAME GMTOFF RULES FORMAT [UNTIL] -- 2.14.3

2 2

OpenJDK/CLDR/ICU/Joda issues with Ireland change
by Stephen Colebourne Jan. 29, 2018

Jan. 29, 2018

Let me try to summarize why the negative SAVE (Ireland change) matters to Java-based projects. there are two basic streams of code - old and new. The older OpenJDK time-zone code and ICU Java code both derive from the same original 20 year old source. The newer OpenJDK time-zone code derives indirectly from Joda-Time, which is still based on many principles from the older OpenJDK code. The ThreeTen-Backport project is an early version of the newer OpenJDK time-zone code. Thus, the vast majority of Java time-zone code is linked and follows a similar approach. The basic data stored is: - a "raw" offset that changes over time, also known as "standard" - a "daylight" offset that changes over time (either relative to the "raw" or absolute) - time-zone changes available from 1970 or earlier - only the *current* names of time-zones are available Some problems: 1) The older code has limits on the difference between the "raw" and "daylight" offset in `GregorianCalendar`. Specifically, the "DST_OFFSET" can only be from 0 to 2 hours. Negative SAVE values are not expected or supported. Note that the limits of 0 to 2 hours are publicly visible via the API `GregorianCalendar.getLeastMinimum()` and friends. 2) The current names of the time-zones is accessed via an array of a fixed order, roughly [long-std, short-std, long-daylight, short-daylight]. Whether the std or daylight text form should be returned is determined by a parameter - a boolean, named "daylight". The basic way this is determined is whether the offset and the"raw" offset are the same or not. This is also expressed in `TimeZone.inDaylightTime()` and `ZoneRules.isDaylightSavings()`, making any switch in the boolean user-visible. The problem here is that the Ireland change flips when the boolean is true from summer to winter. Whereas the content of the array has been stable for 20 years. In the problematic case I looked at, this means that the wrong textual description is returned. ie. in winter, the code has always accessed array elements 0 and 1, whereas if the boolean flag is swapped it will access elements 2 and 3. Remember that only the *current* names of the time-zones are available - so if the Ireland change happens, the time-zone name will necessarily be wrong either before the change occurs or after it. It is a similar problem as Yoshito Umaoka from CLDR expressed a clash between data and code. Here the data on names would clash with the boolean "daylight" flag. Fixing the code doesn't help in this scenario - there is no viable approach to fixing it that can work, as Java has a long history of backwards compatibility over decades, not a year (as is being talked about). Specifically, some of these libraries (Joda-Time, ThreeTen-Backport) run with new tzdb data on older JDK versions. It is the incompatibility in the boolean, where false no longer means winter that cannot be accepted. So, to summarize, even if those in the CLDR/ICU/Java world thought this change was meaningful and positive, backwards compatibility rules out making it. But, in fact the majority of the feedback on the topic from software library maintainers has been negative. I'm pretty sure that negative SAVE is going to be rejected by CLDR, ICU, OpenJDK, Joda-Time and ThreeTen-Backport permanently, and probably Android and Apple too based on their responses so far. As I've outlined, there is no way to meet the backwards compatibility requirements with it. A one year stay of execution won't make a difference in the practicality of the change. FWIW, I understand why some are attached to trying to express data in a "pure" form, but that was never the original intent of the project IMO. The project needs to get back to serving its downstream consumers who just want to know the time without continuous instability in the data format. Stephen PS, Microsoft .NET APIs also have an IsDaylightSavingTime() method: https://msdn.microsoft.com/en-us/library/bb460642(v=vs.110).aspx#Anchor_3

28 140

[PATCH] Clean up theory.html formatting
by Paul Eggert Jan. 28, 2018

Jan. 28, 2018

* theory.html: Redo formatting of the HTML to make it more consistent. Add URLs and some markup. The intent is to improve presentation and make the HTML easier to edit, without changing anything substantive. --- theory.html | 1742 ++++++++++++++++++++++++++++++++--------------------------- 1 file changed, 943 insertions(+), 799 deletions(-) diff --git a/theory.html b/theory.html index 6f03832..ff82fd7 100644 --- a/theory.html +++ b/theory.html @@ -1,26 +1,20 @@ -<!DOCTYPE html> <html lang="en"> <head> <title>Theory and pragmatics of the tz code and data</title> <meta charset="UTF-8"> </head> - - <body> - <h1>Theory and pragmatics of the tz code and data</h1> +<h1>Theory and pragmatics of the <code><abbr>tz</abbr></code> code and data</h1> <h3>Outline</h3> <nav> <ul> - <li><a href="#scope">Scope of the tz database</a></li> + <li><a href="#scope">Scope of the <code><abbr>tz</abbr></code> + database</a></li> <li><a href="#naming">Names of time zone rules</a></li> <li><a href="#abbreviations">Time zone abbreviations</a></li> - <li><a href="#accuracy">Accuracy of the tz database</a></li> + <li><a href="#accuracy">Accuracy of the <code><abbr>tz</abbr></code> + database</a></li> <li><a href="#functions">Time and date functions</a></li> <li><a href="#stability">Interface stability</a></li> <li><a href="#calendar">Calendrical issues</a></li> @@ -28,20 +22,27 @@ </ul> </nav> - - <section> - <h2 id="scope">Scope of the tz database</h2> +<section> + <h2 id="scope">Scope of the <code><abbr>tz</abbr></code> database</h2> <p> -The tz database attempts to record the history and predicted future of -all computer-based clocks that track civil time. To represent this -data, the world is partitioned into regions whose clocks all agree -about timestamps that occur after the somewhat-arbitrary cutoff point -of the POSIX Epoch (1970-01-01 00:00:00 UTC). For each such region, -the database records all known clock transitions, and labels the region -with a notable location. 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. +The <a +href="https://www.iana.org/time-zones"><code><abbr>tz</abbr></code> +database</a> attempts to record the history and predicted future of +all computer-based clocks that track civil time. +It organizes <a href="tz-link.html">time zone and daylight saving time +data</a> by partitioning the world into <a +href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones">regions</a> +whose clocks all agree about timestamps that occur after the of the <a +href="https://en.wikipedia.org/wiki/Unix_time">POSIX Epoch</a> +(1970-01-01 00:00:00 <a +href="https://en.wikipedia.org/wiki/Coordinated_Universal_Time"><abbr +title="Coordinated Universal Time">UTC</abbr></a>). +For each such region, the database records all known clock +transitions, and labels the region with a notable location. +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. </p> <p> @@ -59,193 +60,204 @@ necessarily follow database guidelines. </p> <p> -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: - <a href="http://pubs.opengroup.org/onlinepubs/9699919799/"> - The Open Group Base Specifications Issue 7</a>, - IEEE Std 1003.1-2008, 2016 Edition. +As described below, reference source code for using the +<code><abbr>tz</abbr></code> database is also available. +The <code><abbr>tz</abbr></code> code is upwards compatible with <a +href="https://en.wikipedia.org/wiki/POSIX">POSIX</a>, an international +standard for <a +href="https://en.wikipedia.org/wiki/Unix">UNIX</a>-like systems. +As of this writing, the current edition of POSIX is: <a +href="http://pubs.opengroup.org/onlinepubs/9699919799/"> The Open +Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2008, 2016 +Edition. </p> - </section> - - +</section> - <section> - <h2 id="naming">Names of time zone rules</h2> +<section> + <h2 id="naming">Names of time zone rules</h2> <p> Each of the database's time zone rules has a unique name. Inexperienced users are not expected to select these names unaided. Distributors should provide documentation and/or a simple selection interface that explains the names; for one example, see the 'tzselect' -program in the tz code. The -<a href="http://cldr.unicode.org/">Unicode Common Locale Data -Repository</a> contains data that may be useful for other -selection interfaces. +program in the <code><abbr>tz</abbr></code> code. +The <a href="http://cldr.unicode.org/">Unicode Common Locale Data +Repository</a> contains data that may be useful for other selection +interfaces. </p> <p> The time zone rule naming conventions attempt to strike a balance among the following goals: </p> + <ul> <li> - Uniquely identify every region where clocks have agreed since 1970. - This is essential for the intended use: static clocks keeping local - civil time. + Uniquely identify every region where clocks have agreed since 1970. + This is essential for the intended use: static clocks keeping local + civil time. </li> <li> - Indicate to experts where that region is. + Indicate to experts where that region is. </li> <li> - Be robust in the presence of political changes. For example, names - of countries are ordinarily not used, to avoid incompatibilities - when countries change their name (e.g. Zaire→Congo) or when - locations change countries (e.g. Hong Kong from UK colony to - China). + Be robust in the presence of political changes. + For example, names of countries are ordinarily not used, to avoid + incompatibilities when countries change their name (e.g., + Zaire→Congo) or when locations change countries (e.g., Hong + Kong from UK colony to China). </li> <li> - Be portable to a wide variety of implementations. + Be portable to a wide variety of implementations. </li> <li> - Use a consistent naming conventions over the entire world. + Use a consistent naming conventions over the entire world. </li> </ul> + <p> -Names normally have the -form <var>AREA</var><code>/</code><var>LOCATION</var>, -where <var>AREA</var> is the name of a continent or ocean, -and <var>LOCATION</var> is the name of a specific -location within that region. North and South America share the same -area, '<code>America</code>'. Typical names are -'<code>Africa/Cairo</code>', '<code>America/New_York</code>', and -'<code>Pacific/Honolulu</code>'. +Names normally have the form +<var>AREA</var><code>/</code><var>LOCATION</var>, where +<var>AREA</var> is the name of a continent or ocean, and +<var>LOCATION</var> is the name of a specific location within that +region. +North and South America share the same area, '<code>America</code>'. +Typical names are '<code>Africa/Cairo</code>', +'<code>America/New_York</code>', and '<code>Pacific/Honolulu</code>'. </p> <p> Here are the general rules used for choosing location names, in decreasing order of importance: </p> + <ul> <li> - Use only valid POSIX file name components (i.e., the parts of - names other than '<code>/</code>'). Do not use the file name - components '<code>.</code>' and '<code>..</code>'. - Within a file name component, - use only ASCII letters, '<code>.</code>', - '<code>-</code>' and '<code>_</code>'. 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 '<code>-</code>'. E.g., - prefer '<code>Brunei</code>' to - '<code>Bandar_Seri_Begawan</code>'. Exceptions: see - the discussion - of legacy names below. + Use only valid POSIX file name components (i.e., the parts of + names other than '<code>/</code>'). + Do not use the file name components '<code>.</code>' and + '<code>..</code>'. + Within a file name component, use only <a + href="https://en.wikipedia.org/wiki/ASCII">ASCII</a> letters, + '<code>.</code>', '<code>-</code>' and '<code>_</code>'. + Do not use digits, as that might create an ambiguity with <a + href="http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag…">POSIX + <code>TZ</code> strings</a>. + A file name component must not exceed 14 characters or start with + '<code>-</code>'. + E.g., prefer '<code>Brunei</code>' to '<code>Bandar_Seri_Begawan</code>'. + Exceptions: see the discussion of legacy names below. </li> <li> - A name must not be empty, or contain '<code>//</code>', or - start or end with '<code>/</code>'. + A name must not be empty, or contain '<code>//</code>', or + start or end with '<code>/</code>'. </li> <li> - Do not use names that differ only in case. Although the reference - implementation is case-sensitive, some other implementations - are not, and they would mishandle names differing only in case. + 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. </li> <li> - If one name <var>A</var> is an initial prefix of another - name <var>AB</var> (ignoring case), then <var>B</var> - must not start with '<code>/</code>', as a - regular file cannot have - the same name as a directory in POSIX. For example, - '<code>America/New_York</code>' precludes - '<code>America/New_York/Bronx</code>'. + If one name <var>A</var> is an initial prefix of another + name <var>AB</var> (ignoring case), then <var>B</var> must not + start with '<code>/</code>', as a regular file cannot have the + same name as a directory in POSIX. + For example, '<code>America/New_York</code>' precludes + '<code>America/New_York/Bronx</code>'. </li> <li> - Uninhabited regions like the North Pole and Bouvet Island - do not need locations, since local time is not defined there. + Uninhabited regions like the North Pole and Bouvet Island + do not need locations, since local time is not defined there. </li> <li> - There should typically be at least one name for each ISO 3166-1 - officially assigned two-letter code for an inhabited country - or territory. + There should typically be at least one name for each <a + href="https://en.wikipedia.org/wiki/ISO_3166-1"><abbr + title="International Organization for Standardization">ISO</abbr> + 3166-1</a> officially assigned two-letter code for an inhabited + country or territory. </li> <li> - If all the clocks in a region have agreed since 1970, - don't bother to include more than one location - even if subregions' clocks disagreed before 1970. - Otherwise these tables would become annoyingly large. + If all the clocks in a region have agreed since 1970, + don't bother to include more than one location + even if subregions' clocks disagreed before 1970. + Otherwise these tables would become annoyingly large. </li> <li> - If a name is ambiguous, use a less ambiguous alternative; - e.g. many cities are named San José and Georgetown, so - prefer '<code>Costa_Rica</code>' to '<code>San_Jose</code>' and '<code>Guyana</code>' to '<code>Georgetown</code>'. + If a name is ambiguous, use a less ambiguous alternative; + e.g., many cities are named San José and Georgetown, so + prefer '<code>Costa_Rica</code>' to '<code>San_Jose</code>' and + '<code>Guyana</code>' to '<code>Georgetown</code>'. </li> <li> - Keep locations compact. Use cities or small islands, not countries - or regions, so that any future time zone changes do not split - locations into different time zones. E.g. prefer - '<code>Paris</code>' to '<code>France</code>', since - France has had multiple time zones. + Keep locations compact. + Use cities or small islands, not countries or regions, so that any + future time zone changes do not split locations into different + time zones. + E.g., prefer '<code>Paris</code>' to '<code>France</code>', since + <a href="https://en.wikipedia.org/wiki/Time_in_France#History">France + has had multiple time zones</a>. </li> <li> - Use mainstream English spelling, e.g. prefer - '<code>Rome</code>' to '<code>Roma</code>', and prefer - '<code>Athens</code>' to the Greek - '<code>Αθήνα</code>' or the Romanized - '<code>Athína</code>'. - The POSIX file name restrictions encourage this rule. + Use mainstream English spelling, e.g., prefer '<code>Rome</code>' + to '<code>Roma</code>', and prefer '<code>Athens</code>' to the + Greek '<code>Αθήνα</code>' or the Romanized '<code>Athína</code>'. + The POSIX file name restrictions encourage this rule. </li> <li> - Use the most populous among locations in a zone, - e.g. prefer '<code>Shanghai</code>' to - '<code>Beijing</code>'. Among locations with - similar populations, pick the best-known location, - e.g. prefer '<code>Rome</code>' to '<code>Milan</code>'. + Use the most populous among locations in a zone, + e.g., prefer '<code>Shanghai</code>' to + '<code>Beijing</code>'. + Among locations with similar populations, pick the best-known + location, e.g., prefer '<code>Rome</code>' to + '<code>Milan</code>'. </li> <li> - Use the singular form, e.g. prefer '<code>Canary</code>' to '<code>Canaries</code>'. + Use the singular form, e.g., prefer '<code>Canary</code>' to + '<code>Canaries</code>'. </li> <li> - Omit common suffixes like '<code>_Islands</code>' and - '<code>_City</code>', unless that would lead to - ambiguity. E.g. prefer '<code>Cayman</code>' to - '<code>Cayman_Islands</code>' and - '<code>Guatemala</code>' to - '<code>Guatemala_City</code>', but prefer - '<code>Mexico_City</code>' to '<code>Mexico</code>' - because the country - of Mexico has several time zones. + Omit common suffixes like '<code>_Islands</code>' and + '<code>_City</code>', unless that would lead to ambiguity. + E.g., prefer '<code>Cayman</code>' to + '<code>Cayman_Islands</code>' and '<code>Guatemala</code>' to + '<code>Guatemala_City</code>', but prefer + '<code>Mexico_City</code>' to '<code>Mexico</code>' + because <a href="https://en.wikipedia.org/wiki/Time_in_Mexico">the + country of Mexico has several time zones</a>. </li> <li> - Use '<code>_</code>' to represent a space. + Use '<code>_</code>' to represent a space. </li> <li> - Omit '<code>.</code>' from abbreviations in names, e.g. prefer - '<code>St_Helena</code>' to '<code>St._Helena</code>'. + Omit '<code>.</code>' from abbreviations in names. + E.g., prefer '<code>St_Helena</code>' to '<code>St._Helena</code>'. </li> <li> - Do not change established names if they only marginally - violate the above rules. For example, don't change - the existing name '<code>Rome</code>' to - '<code>Milan</code>' merely because - Milan's population has grown to be somewhat greater - than Rome's. + Do not change established names if they only marginally violate + the above rules. + For example, don't change the existing name '<code>Rome</code>' to + '<code>Milan</code>' merely because Milan's population has grown + to be somewhat greater than Rome's. </li> <li> - If a name is changed, put its old spelling in the - '<code>backward</code>' file. - This means old spellings will continue to work. + If a name is changed, put its old spelling in the + '<code>backward</code>' file. + This means old spellings will continue to work. </li> </ul> <p> The file '<code>zone1970.tab</code>' lists geographical locations used -to name time -zone rules. It is intended to be an exhaustive list of names for -geographic regions as described above; this is a subset of the names -in the data. Although a '<code>zone1970.tab</code>' location's longitude -corresponds to its LMT offset with one hour for every 15° east -longitude, this relationship is not exact. +to name time zone rules. +It is intended to be an exhaustive list of names for geographic +regions as described above; this is a subset of the names in the data. +Although a '<code>zone1970.tab</code>' location's +<a href="https://en.wikipedia.org/wiki/Longitude">longitude</a> +corresponds to +its <a href="https://en.wikipedia.org/wiki/Local_mean_time">local mean +time (<abbr>LMT</abbr>)</a> offset with one hour for every 15° +east longitude, this relationship is not exact. </p> <p> @@ -254,864 +266,996 @@ and these older names are still supported. See the file '<code>backward</code>' for most of these older names (e.g., '<code>US/Eastern</code>' instead of '<code>America/New_York</code>'). The other old-fashioned names still supported are -'<code>WET</code>', '<code>CET</code>', '<code>MET</code>', and '<code>EET</code>' (see the file '<code>europe</code>'). +'<code>WET</code>', '<code>CET</code>', '<code>MET</code>', and +'<code>EET</code>' (see the file '<code>europe</code>'). </p> <p> Older versions of this package defined legacy names that are incompatible with the first rule of location names, but which are -still supported. These legacy names are mostly defined in the file -'<code>etcetera</code>'. Also, the file '<code>backward</code>' defines the legacy names -'<code>GMT0</code>', '<code>GMT-0</code>' and '<code>GMT+0</code>', and the file '<code>northamerica</code>' defines the -legacy names '<code>EST5EDT</code>', '<code>CST6CDT</code>', '<code>MST7MDT</code>', and '<code>PST8PDT</code>'. +still supported. +These legacy names are mostly defined in the file +'<code>etcetera</code>'. +Also, the file '<code>backward</code>' defines the legacy names +'<code>GMT0</code>', '<code>GMT-0</code>' and '<code>GMT+0</code>', +and the file '<code>northamerica</code>' defines the legacy names +'<code>EST5EDT</code>', '<code>CST6CDT</code>', +'<code>MST7MDT</code>', and '<code>PST8PDT</code>'. </p> <p> -Excluding '<code>backward</code>' should not affect the other data. If -'<code>backward</code>' is excluded, excluding '<code>etcetera</code>' should not affect the -remaining data. +Excluding '<code>backward</code>' should not affect the other data. +If '<code>backward</code>' is excluded, excluding +'<code>etcetera</code>' should not affect the remaining data. </p> +</section> - - </section> - <section> - <h2 id="abbreviations">Time zone abbreviations</h2> +<section> + <h2 id="abbreviations">Time zone abbreviations</h2> <p> When this package is installed, it generates time zone abbreviations like '<code>EST</code>' to be compatible with human tradition and POSIX. Here are the general rules used for choosing time zone abbreviations, in decreasing order of importance: +</p> + <ul> <li> - Use three to six characters that are ASCII alphanumerics or - '<code>+</code>' or '<code>-</code>'. - Previous editions of this database also used characters like - '<code> </code>' and '<code>?</code>', but these - characters have a special meaning to - the shell and cause commands like - '<code>set `date`</code>' - to have unexpected effects. - Previous editions of this rule 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 - '<code>-</code>', '<code>+</code>', - and alphanumeric characters from the portable character set - in the current locale. In practice ASCII alphanumerics and - '<code>+</code>' and '<code>-</code>' are safe in all locales. + Use three to six characters that are ASCII alphanumerics or + '<code>+</code>' or '<code>-</code>'. + Previous editions of this database also used characters like + '<code> </code>' and '<code>?</code>', but these characters have a + special meaning to the shell and cause commands like + '<code><a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#set">set</a> + `<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html">date</a>`</code>' + to have unexpected effects. + Previous editions of this rule required upper-case letters, but the + Congressman who + introduced <a href="https://en.wikipedia.org/wiki/Chamorro_Time_Zone">Chamorro + Standard Time</a> preferred "ChST", so lower-case letters are now + allowed. + Also, POSIX from 2001 on relaxed the rule to allow '<code>-</code>', + '<code>+</code>', and alphanumeric characters from the portable + character set in the current locale. + In practice ASCII alphanumerics and '<code>+</code>' and + '<code>-</code>' are safe in all locales. - In other words, in the C locale the POSIX extended regular - expression <code>[-+[:alnum:]]{3,6}</code> should match - the abbreviation. - This guarantees that all abbreviations could have been - specified by a POSIX TZ string. - </li> - <li> - Use abbreviations that are in common use among English-speakers, - e.g. 'EST' for Eastern Standard Time in North America. - We assume that applications translate them to other languages - as part of the normal localization process; for example, - a French application might translate 'EST' to 'HNE'. - -<p><small>These abbreviations (for standard/daylight/etc. time) are: -ACST/ACDT Australian Central, -AST/ADT/APT/AWT/ADDT Atlantic, -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 Guam, -HST/HDT Hawaii, -HKT/HKST 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, -SAST South Africa, -SST Samoa, -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</small>.</p> - </li> - <li> - For zones whose times are taken from a city's longitude, use the -traditional <var>x</var>MT 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., '<code>-</code>004430' for MMT) would -cause trouble here, as the numeric strings would exceed the POSIX length limit. + <p> + In other words, in the C locale the POSIX extended regular + expression <code>[-+[:alnum:]]{3,6}</code> should match the + abbreviation. + This guarantees that all abbreviations could have been specified by a + POSIX <code>TZ</code> string. + </p> + </li> + <li> + Use abbreviations that are in common use among English-speakers, + e.g., 'EST' for Eastern Standard Time in North America. + We assume that applications translate them to other languages + as part of the normal localization process; for example, + a French application might translate 'EST' to 'HNE'. -<p><small>These abbreviations are: -AMT Amsterdam, Asunción, Athens; -BMT Baghdad, Bangkok, Batavia, Bern, Bogotá, Bridgetown, Brussels, Bucharest; -CMT Calamarca, Caracas, Chisinau, Colón, Copenhagen, 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, Kiev, 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</small>.</p> + <p> + <small>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 Guam, + HST/HDT Hawaii, + HKT/HKST 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, + SAST South Africa, + SST Samoa, + 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</small>. + </p> + </li> + <li> + <p> + For zones whose times are taken from a city's longitude, use the + traditional <var>x</var>MT notation. + The only abbreviation like this in current use is '<abbr>GMT</abbr>'. + The others are for timestamps before 1960, + except that Monrovia Mean Time persisted until 1972. + Typically, numeric abbreviations (e.g., '<code>-</code>004430' for + MMT) would cause trouble here, as the numeric strings would exceed + the POSIX length limit. + </p> -<p><small>A few abbreviations also follow the pattern that -GMT/BST established for time in the UK. They are: + <p> + <small>These abbreviations are: + AMT Amsterdam, Asunción, Athens; + BMT Baghdad, Bangkok, Batavia, Bern, Bogotá, Bridgetown, Brussels, + Bucharest; + CMT Calamarca, Caracas, Chisinau, Colón, Copenhagen, 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, Kiev, 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</small>. + </p> -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. -An extra-special case is SET for Swedish Time (<em>svensk -normaltid</em>) 1879–1899, 3° west of the Stockholm -Observatory.</small></p> + <p> + <small>A few abbreviations also follow the pattern that + <abbr>GMT<abbr>/<abbr>BST</abbr> established for time in the UK. + They are: + 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. + An extra-special case is SET for Swedish Time (<em>svensk + normaltid</em>) 1879–1899, 3° west of the Stockholm + Observatory.</small> + </p> </li> <li> - Use 'LMT' for local mean time of locations before the introduction - of standard time; see "<a href="#scope">Scope of the - tz database</a>". + Use '<abbr>LMT</abbr>' for local mean time of locations before the + introduction of standard time; see "<a href="#scope">Scope of the + <code><abbr>tz</abbr></code> database</a>". </li> <li> - If there is no common English abbreviation, use numeric offsets like - <code>-</code>05 and <code>+</code>0830 that are - generated by zic's <code>%z</code> notation. + If there is no common English abbreviation, use numeric offsets like + <code>-</code>05 and <code>+</code>0830 that are generated + by <code>zic</code>'s <code>%z</code> notation. </li> <li> - Use current abbreviations for older timestamps to avoid confusion. - For example, in 1910 a common English abbreviation for UT +01 - 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 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. </li> <li> - Use a consistent style in a zone's history. For example, if a zone's - history tends to use numeric abbreviations and a particular - entry could go either way, use a numeric abbreviation. + Use a consistent style in a zone's history. + For example, if a zone's history tends to use numeric + abbreviations and a particular entry could go either way, use a + numeric abbreviation. </li> <li> - Use UT (with time zone abbreviation '<code>-</code>00') for - locations while uninhabited. The leading - '<code>-</code>' is a flag that the time - zone is in some sense undefined; this notation is - derived from Internet RFC 3339. + Use <a href="https://en.wikipedia.org/wiki/Universal_Time">Universal Time</a> + (<abbr>UT</abbr>) (with time zone abbreviation '<code>-</code>00') for + locations while uninhabited. + The leading '<code>-</code>' is a flag that the time zone is in + some sense undefined; this notation is derived + from <a href="https://tools.ietf.org/html/rfc3339">Internet + <abbr title="Request For Comments">RFC 3339</a>. </li> </ul> + <p> 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 +Israel. +To avoid ambiguity, use numeric <abbr>UT</abbr> offsets like '<code>-</code>0600' instead of time zone abbreviations like 'CST'. </p> - </section> - +</section> - <section> - <h2 id="accuracy">Accuracy of the tz database</h2> +<section> + <h2 id="accuracy">Accuracy of the <code><abbr>tz</abbr></code> database</h2> <p> -The tz database is not authoritative, and it surely has errors. +The <code><abbr>tz</abbr></code> database is not authoritative, and it +surely has errors. Corrections are welcome and encouraged; see the file <code>CONTRIBUTING</code>. Users requiring authoritative data should consult national standards bodies and the references cited in the database's comments. </p> <p> -Errors in the tz database arise from many sources: +Errors in the <code><abbr>tz</abbr></code> database arise from many sources: </p> + <ul> <li> - 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. - </li> - <li> - 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 zones 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 - <cite>The Global Transformation of Time, 1870-1950</cite>, 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, <a - href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vaness…">Booked: - A Global History of Time</a>. <cite>Dissent</cite> 2015-12-17. - </li> - <li> - 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. - </li> - <li> - For the UK the tz database relies on years of first-class work done by - Joseph Myers and others; see - "<a href="https://www.polyomino.org.uk/british-time/">History of - legal time in Britain</a>". - Other countries are not done nearly as well. - </li> - <li> - Sometimes, different people in the same city would maintain clocks - that differed significantly. Railway time was used by railroad - companies (which did not always agree with each other), - church-clock time was used for birth certificates, etc. - Often this was merely common practice, but sometimes it was set by law. - For example, from 1891 to 1911 the UT offset in France was legally - 0:09:21 outside train stations and 0:04:21 inside. - </li> - <li> - 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, <code>Europe/London</code> - 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. - </li> - <li> - The tz database does not record the earliest time for which a zone's - data entries are thereafter valid for every location in the region. - For example, <code>Europe/London</code> 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 zones the earliest time of validity is - unknown. - </li> - <li> - The tz database does not record a region's boundaries, and in many - cases the boundaries are not known. For example, the zone - <code>America/Kentucky/Louisville</code> represents a region around - the city of - Louisville, the boundaries of which are unclear. - </li> - <li> - Changes that are modeled as instantaneous transitions in the tz - database were often spread out over hours, days, or even decades. - </li> - <li> - Even if the time is specified by law, locations sometimes - deliberately flout the law. - </li> - <li> - Early timekeeping practices, even assuming perfect clocks, were - often not specified to the accuracy that the tz database requires. - </li> - <li> - Sometimes historical timekeeping was specified more precisely - than what the tz database can handle. For example, from 1909 to - 1937 Netherlands clocks were legally UT +00:19:32.13, but the tz - database cannot represent the fractional second. - </li> - <li> - 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. - </li> - <li> - The tz database models pre-standard time using the proleptic Gregorian - calendar and local mean time (LMT), but many people used other - calendars and other timescales. For example, the Roman Empire used - the Julian calendar, and had 12 varying-length daytime hours with a - non-hour-based system at night. - </li> - <li> - Early clocks were less reliable, and data entries do not represent - clock error. - </li> - <li> - 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. - </li> - <li> - Civil time was not based on atomic time before 1972, and we don't - 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. - <a href="http://dx.doi.org/10.1098/rspa.2016.0404">Measurement - of the Earth's rotation: 720 BC to AD 2015</a>. - <cite>Proc Royal Soc A</cite>. 2016 Dec 7;472:20160404. - Also see: Espenak F. <a - href="https://eclipse.gsfc.nasa.gov/SEhelp/uncertainty2004.html">Uncertainty - in Delta T (ΔT)</a>. - </li> - <li> - 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. - </li> - <li> - 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's not clear how to apply it here. + The <code><abbr>tz</abbr></code> 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. + </li> + <li> + 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 zones would be needed if + the <code><abbr>tz</abbr></code> 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 + <cite><a href="http://www.hup.harvard.edu/catalog.php?isbn=9780674286146">The + Global Transformation of Time, 1870–1950</a></cite>, + 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, <a +href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vaness…">Booked: + A Global History of Time</a>. <cite>Dissent</cite> 2015-12-17. + </li> + <li> + 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. + </li> + <li> + For the UK the <code><abbr>tz</abbr></code> database relies on + years of first-class work done by + Joseph Myers and others; see + "<a href="https://www.polyomino.org.uk/british-time/">History of + legal time in Britain</a>". + Other countries are not done nearly as well. + </li> + <li> + Sometimes, different people in the same city would maintain clocks + that differed significantly. + Railway time was used by railroad companies (which did not always + agree with each other), church-clock time was used for birth + certificates, etc. + Often this was merely common practice, but sometimes it was set by law. + For example, from 1891 to 1911 the <abbr>UT</abbr> offset in France + was legally <abbr>UT</abbr> +00:09:21 outside train stations and + <abbr>UT</abbr> +00:04:21 inside. + </li> + <li> + Although a named location in the <code><abbr>tz</abbr></code> + database stands for the containing region, its pre-1970 data + entries are often accurate for only a small subset of that region. + For example, <code>Europe/London</code> 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 <abbr>GMT</abbr> is known to be valid only for the L&NW and + the Caledonian railways. + </li> + <li> + The <code><abbr>tz</abbr></code> database does not record the + earliest time for which a zone's + data entries are thereafter valid for every location in the region. + For example, <code>Europe/London</code> is valid for all locations + in its region after <abbr>GMT</abbr> was made the standard time, + but the date of standardization (1880-08-02) is not in the + <code><abbr>tz</abbr></code> database, other than in commentary. + For many zones the earliest time of validity is unknown. + </li> + <li> + The <code><abbr>tz</abbr></code> database does not record a + region's boundaries, and in many cases the boundaries are not known. + For example, the zone + <code>America/Kentucky/Louisville</code> represents a region + around the city of Louisville, the boundaries of which are + unclear. + </li> + <li> + Changes that are modeled as instantaneous transitions in the + <code><abbr>tz</abbr></code> + database were often spread out over hours, days, or even decades. + </li> + <li> + Even if the time is specified by law, locations sometimes + deliberately flout the law. + </li> + <li> + Early timekeeping practices, even assuming perfect clocks, were + often not specified to the accuracy that the + <code><abbr>tz</abbr></code> database requires. + </li> + <li> + Sometimes historical timekeeping was specified more precisely + than what the <code><abbr>tz</abbr></code> database can handle. + For example, from 1909 to 1937 <a + href="https://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm" + hreflang="nl">Netherlands clocks</a> were legally <abbr>UT</abbr> + +00:19:32.13, but the <code><abbr>tz</abbr></code> + database cannot represent the fractional second. + </li> + <li> + Even when all the timestamp transitions recorded by the + <code><abbr>tz</abbr></code> database are correct, the + <code><abbr>tz</abbr></code> 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 <code><abbr>tz</abbr></code> database has no + way to specify Easter, these exceptional years are entered as + separate <code><abbr>tz</abbr> Rule</code> lines, even though the + legal rules did not change. + </li> + <li> + The <code><abbr>tz</abbr></code> database models pre-standard time + using the <a + href="https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar">proleptic + Gregorian calendar</a> and local mean time, but many people used + other calendars and other timescales. + For example, the Roman Empire used + the <a href="https://en.wikipedia.org/wiki/Julian_calendar">Julian + calendar</a>, + and <a href="https://en.wikipedia.org/wiki/Roman_timekeeping">Roman + timekeeping</a> had twelve varying-length daytime hours with a + non-hour-based system at night. + </li> + <li> + Early clocks were less reliable, and data entries do not represent + clock error. + </li> + <li> + The <code><abbr>tz</abbr></code> database assumes Universal Time + (<abbr>UT</abbr>) as an origin, even though <abbr>UT</abbr> is not + standardized for older timestamps. + In the <code><abbr>tz</abbr></code> database commentary, + <abbr>UT</abbr> denotes a family of time standards that includes + Coordinated Universal Time (<abbr>UTC</abbr>) along with other + variants such as <abbr>UT1</abbr> and <abbr>GMT</abbr>, + with days starting at midnight. + Although <abbr>UT</abbr> equals <abbr>UTC</abbr> for modern + timestamps, <abbr>UTC</abbr> was not defined until 1960, so + commentary uses the more-general abbreviation <abbr>UT</abbr> for + timestamps that might predate 1960. + Since <abbr>UT</abbr>, <abbr>UT1</abbr>, etc. disagree slightly, + and since pre-1972 <abbr>UTC</abbr> seconds varied in length, + interpretation of older timestamps can be problematic when + subsecond accuracy is needed. + </li> + <li> + Civil time was not based on atomic time before 1972, and we don't + know the history of + <a href="https://en.wikipedia.org/wiki/Earth's_rotation">earth's + rotation</a> accurately enough to map <a + href="https://en.wikipedia.org/wiki/International_System_of_Units"><abbr + title="International System of Units">SI</abbr></a> seconds to + historical <a href="https://en.wikipedia.org/wiki/Solar_time">solar time</a> + to more than about one-hour accuracy. + See: Stephenson FR, Morrison LV, Hohenkerk CY. + <a href="http://dx.doi.org/10.1098/rspa.2016.0404">Measurement of + the Earth's rotation: 720 BC to AD 2015</a>. + <cite>Proc Royal Soc A</cite>. 2016 Dec 7;472:20160404. + Also see: Espenak F. <a + href="https://eclipse.gsfc.nasa.gov/SEhelp/uncertainty2004.html">Uncertainty + in Delta T (ΔT)</a>. + </li> + <li> + The relationship between POSIX time (that is, <abbr>UTC</abbr> but + ignoring <a href="https://en.wikipedia.org/wiki/Leap_second">leap + seconds</a>) and <abbr>UTC</abbr> 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. + </li> + <li> + The <code><abbr>tz</abbr></code> 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's not clear how to apply it here. </li> </ul> + <p> -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 zones merely because two locations differ in LMT or -transitioned to standard time at different dates. +In short, many, perhaps most, of the <code><abbr>tz</abbr></code> +database's pre-1970 and future timestamps are either wrong or +misleading. +Any attempt to pass the +<code><abbr>tz</abbr></code> database off as the definition of time +should be unacceptable to anybody who cares about the facts. +In particular, the <code><abbr>tz</abbr></code> database's +<abbr>LMT</abbr> offsets should not be considered meaningful, and +should not prompt creation of zones merely because two locations +differ in <abbr>LMT</abbr> or transitioned to standard time at +different dates. </p> - </section> - +</section> - <section> - <h2 id="functions">Time and date functions</h2> +<section> + <h2 id="functions">Time and date functions</h2> <p> -The tz code contains time and date functions that are upwards -compatible with those of POSIX. +The <code><abbr>tz</abbr></code> code contains time and date functions +that are upwards compatible with those of POSIX. Code compatible with this package is already -<a href="tz-link.html#tzdb">part of many platforms</a>, -where the primary use of this package -is to update obsolete time zone rule tables. +<a href="tz-link.html#tzdb">part of many platforms</a>, where the +primary use of this package is to update obsolete time zone rule +tables. To do this, you may need to compile the time zone compiler -'<code>zic</code>' supplied with this package instead of using -the system '<code>zic</code>', since the format -of <code>zic</code>'s input is occasionally extended, and a -platform may still be shipping an older <code>zic</code>. +'<code>zic</code>' supplied with this package instead of using the +system '<code>zic</code>', since the format of <code>zic</code>'s +input is occasionally extended, and a platform may still be shipping +an older <code>zic</code>. </p> <h3 id="POSIX">POSIX properties and limitations</h3> <ul> <li> <p> - 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 can't deal with other (for example, Iranian) - daylight saving time rules, or situations where more than two - time zone abbreviations are used in an area. + In POSIX, time display in a process is controlled by the + environment variable <code>TZ</code>. + Unfortunately, the POSIX + <code>TZ</code> string takes a form that is hard to describe and + is error-prone in practice. + Also, POSIX <code>TZ</code> strings can't 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 <abbr>UT</abbr> offsets are used in an area. </p> + <p> - The POSIX TZ string takes the following form: + The POSIX <code>TZ</code> string takes the following form: </p> + <p> - <var>stdoffset</var>[<var>dst</var>[<var>offset</var>][<code>,</code><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]]] + <var>stdoffset</var>[<var>dst</var>[<var>offset</var>][<code>,</code><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]]] </p> + <p> - where: + where: + </p> + <dl> <dt><var>std</var> and <var>dst</var></dt><dd> - are 3 or more characters specifying the standard - and daylight saving time (DST) zone names. - Starting with POSIX.1-2001, <var>std</var> - and <var>dst</var> may also be - in a quoted form like '<code><+09></code>'; this allows - "<code>+</code>" and "<code>-</code>" in the names. + are 3 or more characters specifying the standard + and daylight saving time (<abbr>DST</abbr>) zone names. + Starting with POSIX.1-2001, <var>std</var> and <var>dst</var> + may also be in a quoted form like '<code><+09></code>'; + this allows "<code>+</code>" and "<code>-</code>" in the names. </dd> <dt><var>offset</var></dt><dd> - is of the form - '<code>[±]<var>hh</var>:[<var>mm</var>[:<var>ss</var>]]</code>' - and specifies the offset west of UT. '<var>hh</var>' - may be a single digit; 0≤<var>hh</var>≤24. - The default DST offset is one hour ahead of standard time. + is of the form + '<code>[±]<var>hh</var>:[<var>mm</var>[:<var>ss</var>]]</code>' + and specifies the offset west of <abbr>UT</abbr>. + '<var>hh</var>' may be a single digit; + 0≤<var>hh</var>≤24. + The default <abbr>DST</abbr> offset is one hour ahead of + standard time. </dd> <dt><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]</dt><dd> - specifies the beginning and end of DST. If this is absent, - the system supplies its own rules for DST, and these can - differ from year to year; typically US DST rules are used. + specifies the beginning and end of <abbr>DST</abbr>. + If this is absent, the system supplies its own rules + for <abbr>DST</abbr>, and these can differ from year to year; + typically <abbr>US</abbr> <abbr>DST</abbr> rules are used. </dd> <dt><var>time</var></dt><dd> - takes the form - '<var>hh</var><code>:</code>[<var>mm</var>[<code>:</code><var>ss</var>]]' - and defaults to 02:00. - This is the same format as the offset, except that a - leading '<code>+</code>' or '<code>-</code>' is not allowed. + takes the form + '<var>hh</var><code>:</code>[<var>mm</var>[<code>:</code><var>ss</var>]]' + and defaults to 02:00. + This is the same format as the offset, except that a + leading '<code>+</code>' or '<code>-</code>' is not allowed. </dd> <dt><var>date</var></dt><dd> - takes one of the following forms: + takes one of the following forms: <dl> <dt>J<var>n</var> (1≤<var>n</var>≤365)</dt><dd> - origin-1 day number not counting February 29 - </dd> + origin-1 day number not counting February 29 + </dd> <dt><var>n</var> (0≤<var>n</var>≤365)</dt><dd> - origin-0 day number counting February 29 if present - </dd> - <dt><code>M</code><var>m</var><code>.</code><var>n</var><code>.</code><var>d</var> (0[Sunday]≤<var>d</var>≤6[Saturday], 1≤<var>n</var>≤5, 1≤<var>m</var>≤12)</dt><dd> - for the <var>d</var>th day of - week <var>n</var> of month <var>m</var> of the - year, where week 1 is the first week in which - day <var>d</var> appears, and '<code>5</code>' - stands for the last week in which - day <var>d</var> appears - (which may be either the 4th or 5th week). - Typically, this is the only useful form; - the <var>n</var> - and <code>J</code><var>n</var> forms are - rarely used. + origin-0 day number counting February 29 if present </dd> -</dl> -</dd> -</dl> - 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: + <dt><code>M</code><var>m</var><code>.</code><var>n</var><code>.</code><var>d</var> + (0[Sunday]≤<var>d</var>≤6[Saturday], 1≤<var>n</var>≤5, + 1≤<var>m</var>≤12)</dt><dd> + for the <var>d</var>th day of week <var>n</var> of + month <var>m</var> of the year, where week 1 is the first + week in which day <var>d</var> appears, and + '<code>5</code>' stands for the last week in which + day <var>d</var> appears (which may be either the 4th or + 5th week). + Typically, this is the only useful form; the <var>n</var> + and <code>J</code><var>n</var> forms are rarely used. + </dd> + </dl> + </dd> + </dl> - <pre><code>TZ='NZST-12NZDT,M9.5.0,M4.1.0/3'</code></pre> + <p> + Here is an example POSIX <code>TZ</code> string for New + Zealand after 2007. + It says that standard time (<abbr>NZST</abbr>) is 12 hours ahead + of <abbr>UT</abbr>, and that daylight saving time + (<abbr>NZDT</abbr>) is observed from September's last Sunday at + 02:00 until April's first Sunday at 03:00: + </p> - This POSIX TZ string is hard to remember, and mishandles some - timestamps before 2008. With this package you can use this - instead: + <pre><code>TZ='NZST-12NZDT,M9.5.0,M4.1.0/3'</code></pre> - <pre><code>TZ='Pacific/Auckland'</code></pre> + <p> + This POSIX <code>TZ</code> string is hard to remember, and + mishandles some timestamps before 2008. + With this package you can use this instead: + </p> + + <pre><code>TZ='Pacific/Auckland'</code></pre> + </li> + <li> + POSIX does not define the exact meaning of <code>TZ</code> values like + "<code>EST5EDT</code>". + Typically the current <abbr>US</abbr> <abbr>DST</abbr> rules + are used to interpret such values, but this means that the + <abbr>US</abbr> <abbr>DST</abbr> rules are compiled into each + program that does time conversion. + This means that when + <abbr>US</abbr> time conversion rules change (as in the United + States in 1987), all programs that do time conversion must be + recompiled to ensure proper results. + </li> + <li> + The <code>TZ</code> environment variable is process-global, which + makes it hard to write efficient, thread-safe applications that + need access to multiple time zones. + </li> + <li> + In POSIX, there's no tamper-proof way for a process to learn the + system's best idea of local wall clock. + (This is important for applications that an administrator wants + used only at certain times – without regard to whether the + user has fiddled the + <code>TZ</code> environment variable. + While an administrator can "do everything in <abbr>UT</abbr>" to + get around the problem, doing so is inconvenient and precludes + handling daylight saving time shifts - as might be required to + limit phone calls to off-peak hours.) + </li> + <li> + POSIX provides no convenient and efficient way to determine + the <abbr>UT</abbr> offset and time zone abbreviation of arbitrary + timestamps, particularly for time zone settings that do not fit + into the POSIX model. + </li> + <li> + POSIX requires that systems ignore leap seconds. + </li> + <li> + The <code><abbr>tz</abbr></code> code attempts to support all the + <code>time_t</code> implementations allowed by POSIX. + The <code>time_t</code> type represents a nonnegative count of seconds + since 1970-01-01 00:00:00 <abbr>UTC</abbr>, ignoring leap seconds. + In practice, <code>time_t</code> is usually a signed 64- or 32-bit + integer; 32-bit signed <code>time_t</code> values stop working after + 2038-01-19 03:14:07 <abbr>UTC</abbr>, so new implementations these + days typically use a signed 64-bit integer. + Unsigned 32-bit integers are used on one or two platforms, and 36-bit + and 40-bit integers are also used occasionally. + Although earlier POSIX versions allowed <code>time_t</code> to be a + floating-point type, this was not supported by any practical systems, + and POSIX.1-2013 and the <code><abbr>tz</abbr></code> code both + require <code>time_t</code> to be an integer type. </li> +</ul> + +<h3 id="POSIX-extensions">Extensions to POSIX in the +<code><abbr>tz</abbr></code> code</h3> +<ul> <li> - POSIX does not define the exact meaning of TZ values like - "<code>EST5EDT</code>". - Typically the current US DST rules are used to interpret such values, - but this means that the US DST rules are compiled into each program - that does time conversion. This means that when US time conversion - rules change (as in the United States in 1987), all programs that - do time conversion must be recompiled to ensure proper results. + <p> + The <code>TZ</code> environment variable is used in generating + the name of a file from which time zone information is read + (or is interpreted à la POSIX); <code>TZ</code> is no longer + constrained to be a three-letter time zone + name followed by a number of hours and an optional three-letter + daylight time zone name. + The daylight saving time rules to be used for a particular time + zone are encoded in the time zone file; the format of the file + allows U.S., Australian, and other rules to be encoded, and + allows for situations where more than two time zone + abbreviations are used. + </p> + <p> + It was recognized that allowing the <code>TZ</code> environment + variable to take on values such as '<code>America/New_York</code>' + might cause "old" programs (that expect <code>TZ</code> to have a + certain form) to operate incorrectly; consideration was given to using + some other environment variable (for example, <code>TIMEZONE</code>) + to hold the string used to generate the time zone information file name. + In the end, however, it was decided to continue using + <code>TZ</code>: it is widely used for time zone purposes; + separately maintaining both <code>TZ</code> + and <code>TIMEZONE</code> seemed a nuisance; and systems where + "new" forms of <code>TZ</code> might cause problems can simply + use <code>TZ</code> values such as "<code>EST5EDT</code>" which + can be used both by "new" programs (à la POSIX) and "old" + programs (as zone names and offsets). + </p> </li> <li> - The TZ environment variable is process-global, which makes it hard - to write efficient, thread-safe applications that need access - to multiple time zones. + The code supports platforms with a <abbr>UT</abbr> offset member + in <code>struct tm</code>, e.g., <code>tm_gmtoff</code>. </li> <li> - In POSIX, there's no tamper-proof way for a process to learn the - system's best idea of local wall clock. (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.) + The code supports platforms with a time zone abbreviation member in + <code>struct tm</code>, e.g., <code>tm_zone</code>. </li> <li> - POSIX provides no convenient and efficient way to determine the UT - offset and time zone abbreviation of arbitrary timestamps, - particularly for time zone settings that do not fit into the - POSIX model. + Functions <code>tzalloc</code>, <code>tzfree</code>, + <code>localtime_rz</code>, and <code>mktime_z</code> for + more-efficient thread-safe applications that need to use multiple + time zones. + The <code>tzalloc</code> and <code>tzfree</code> functions + allocate and free objects of type <code>timezone_t</code>, + and <code>localtime_rz</code> and <code>mktime_z</code> are + like <code>localtime_r</code> and <code>mktime</code> with an + extra <code>timezone_t</code> argument. + The functions were inspired by <a href="https://netbsd.org/">NetBSD</a>. </li> <li> - POSIX requires that systems ignore leap seconds. + A function <code>tzsetwall</code> has been added to arrange for the + system's best approximation to local wall clock time to be delivered + by subsequent calls to <code>localtime</code>. + Source code for portable applications that "must" run on local wall + clock time should call <code>tzsetwall</code>; + if such code is moved to "old" systems that don't + provide <code>tzsetwall</code>, you won't be able to generate an + executable program. + (These time zone functions also arrange for local wall clock time to + be used if <code>tzset</code> is called – directly or + indirectly – and there's no <code>TZ</code> environment + variable; portable applications should not, however, rely on this + behavior since it's not the way SVR2 systems behave.) </li> <li> - The tz code attempts to support all the <code>time_t</code> - implementations allowed by POSIX. The <code>time_t</code> - type represents a nonnegative count of - seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds. - In practice, <code>time_t</code> is usually a signed 64- or - 32-bit integer; 32-bit signed <code>time_t</code> values stop - working after 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 <code>time_t</code> to be a - floating-point type, this was not supported by any practical - systems, and POSIX.1-2013 and the tz code both - require <code>time_t</code> - to be an integer type. + Negative <code>time_t</code> values are supported, on systems + where <code>time_t</code> is signed. </li> -</ul> - -<h3 id="POSIX-extensions">Extensions to POSIX in the tz code</h3> -<ul> <li> - <p> - The TZ environment variable is used in generating the name of a file - from which time zone information is read (or is interpreted a la - POSIX); TZ is no longer constrained to be a three-letter time zone - name followed by a number of hours and an optional three-letter - daylight time zone name. The daylight saving time rules to be used - for a particular time zone are encoded in the time zone file; - the format of the file allows U.S., Australian, and other rules to be - encoded, and allows for situations where more than two time zone - abbreviations are used. - </p> - <p> - It was recognized that allowing the TZ environment variable to - take on values such as '<code>America/New_York</code>' 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 - time zone information file 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 TZ values such as "<code>EST5EDT</code>" which can be used both by - "new" programs (a la POSIX) and "old" programs (as zone names and - offsets). - </p> -</li> -<li> - The code supports platforms with a UT offset member - in <code>struct tm</code>, - e.g., <code>tm_gmtoff</code>. -</li> -<li> - The code supports platforms with a time zone abbreviation member in - <code>struct tm</code>, e.g., <code>tm_zone</code>. -</li> -<li> - Functions <code>tzalloc</code>, <code>tzfree</code>, - <code>localtime_rz</code>, and <code>mktime_z</code> for - more-efficient thread-safe applications that need to use - multiple time zones. The <code>tzalloc</code> - and <code>tzfree</code> functions allocate and free objects of - type <code>timezone_t</code>, and <code>localtime_rz</code> - and <code>mktime_z</code> are like <code>localtime_r</code> - and <code>mktime</code> with an extra - <code>timezone_t</code> argument. The functions were inspired - by NetBSD. -</li> -<li> - A function <code>tzsetwall</code> has been added to arrange - for the system's - best approximation to local wall clock time to be delivered by - subsequent calls to <code>localtime</code>. Source code for portable - applications that "must" run on local wall clock time should call - <code>tzsetwall</code>; if such code is moved to "old" systems that don't - provide tzsetwall, you won't be able to generate an executable program. - (These time zone functions also arrange for local wall clock time to be - used if tzset is called – directly or indirectly – - and there's no TZ - environment variable; portable applications should not, however, rely - on this behavior since it's not the way SVR2 systems behave.) -</li> -<li> - Negative <code>time_t</code> values are supported, on systems - where <code>time_t</code> is signed. -</li> -<li> - These functions can account for leap seconds, thanks to Bradley White. -</li> + These functions can account for leap seconds, thanks to Bradley White. + </li> </ul> <h3 id="vestigial">POSIX features no longer needed</h3> <p> -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: +POSIX and <a href="https://en.wikipedia.org/wiki/ISO_C"><abbr>ISO</abbr> C</a> +define some <a href="https://en.wikipedia.org/wiki/API"><abbr +title="application programming interface">API</abbr>s</a> 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 <code><abbr>tz</abbr></code> code supports these +vestigial <abbr>API</abbr>s for backwards compatibility, they should +be avoided in portable applications. +The vestigial <abbr>API</abbr>s are: </p> <ul> <li> The POSIX <code>tzname</code> variable does not suffice and is no - longer needed. To get a timestamp's time zone abbreviation, - consult the <code>tm_zone</code> member if available; otherwise, + longer needed. + To get a timestamp's time zone abbreviation, consult + the <code>tm_zone</code> member if available; otherwise, use <code>strftime</code>'s <code>"%Z"</code> conversion specification. </li> <li> The POSIX <code>daylight</code> and <code>timezone</code> - variables do not suffice and are no longer needed. To get a - timestamp's UT offset, consult the <code>tm_gmtoff</code> member - if available; otherwise, subtract values returned - by <code>localtime</code> and <code>gmtime</code> using the rules - of the Gregorian calendar, or - use <code>strftime</code>'s <code>"%z"</code> conversion + variables do not suffice and are no longer needed. + To get a timestamp's <abbr>UT</abbr> offset, consult + the <code>tm_gmtoff</code> member if available; otherwise, + subtract values returned by <code>localtime</code> + and <code>gmtime</code> using the rules of the Gregorian calendar, + or use <code>strftime</code>'s <code>"%z"</code> conversion specification if a string like <samp>"+0900"</samp> suffices. </li> <li> The <code>tm_isdst</code> 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 - <code>mktime</code> to disambiguate timestamps near a DST - transition when the clock jumps back, this disambguation 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. + <abbr>API</abbr>s. + Although it can still be used in arguments to + <code>mktime</code> to disambiguate timestamps near + a <abbr>DST</abbr> transition when the clock jumps back, this + disambguation does not work when standard time itself jumps back, + which can occur when a location changes to a time zone with a + lesser <abbr>UT</abbr> offset. </li> </ul> <h3 id="other-portability">Other portability notes</h3> <ul> <li> - The UNIX Version 7 <code>timezone</code> function is not - present in this package; - it's 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 - <code>localtime(&clock)->tm_zone</code> - (if <code>TM_ZONE</code> is defined) or - <code>tzname[localtime(&clock)->tm_isdst]</code> - (if <code>HAVE_TZNAME</code> is defined) - to learn the correct time zone abbreviation to use. - </li> - <li> - The 4.2BSD <code>gettimeofday</code> 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. - </li> - <li> - In SVR2, time conversion fails for near-minimum or near-maximum - <code>time_t</code> values when doing conversions for places - that don't use UT. - This package takes care to do these conversions correctly. - A comment in the source code tells how to get compatibly wrong - results. - </li> -<li> -The functions that are conditionally compiled -if <code>STD_INSPIRED</code> 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 <em>any</em> standard. They do, however, represent responses of -various authors to -standardization proposals. -</li> -<li> -Other time conversion proposals, in particular the one developed by folks at -Hewlett Packard, 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. -</li> + The <a href="https://en.wikipedia.org/wiki/Version_7_Unix">7th Edition + UNIX</a> <code>timezone</code> function is not present in this + package; it's impossible to reliably map <code>timezone</code>'s + arguments (a "minutes west of <abbr>GMT</abbr>" 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 <code>timezone</code> function + may now examine <code>localtime(&clock)->tm_zone</code> + (if <code>TM_ZONE</code> is defined) or + <code>tzname[localtime(&clock)->tm_isdst]</code> + (if <code>HAVE_TZNAME</code> is defined) to learn the correct time + zone abbreviation to use. + </li> + <li> + The <abbr>4.2BSD</abbr> <code>gettimeofday</code> function is not + used in this package. + This formerly let users obtain the current <abbr>UTC</abbr> offset + and <abbr>DST</abbr> flag, but this functionality was removed in + later versions of <abbr>BSD</abbr>. + </li> + <li> + In <abbr>SVR2</abbr>, time conversion fails for near-minimum or + near-maximum <code>time_t</code> values when doing conversions + for places that don't use <abbr>UT</abbr>. + This package takes care to do these conversions correctly. + A comment in the source code tells how to get compatibly wrong + results. + </li> + <li> + The functions that are conditionally compiled + if <code>STD_INSPIRED</code> 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 <em>any</em> standard. + They do, however, represent responses of various authors to + standardization proposals. + </li> + <li> + Other time conversion proposals, in particular the one developed + by folks at Hewlett Packard, 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. + </li> </ul> - </section> - +</section> - <section> - <h2 id="stability">Interface stability</h2> +<section> + <h2 id="stability">Interface stability</h2> <p> -The tz code and data supply the following interfaces: +The <code><abbr>tz</abbr></code> code and data supply the following interfaces: </p> + <ul> <li> - A set of zone names as per "<a href="#naming">Names of time zone - rules</a>" above. + A set of zone names as per "<a href="#naming">Names of time zone + rules</a>" above. </li> <li> - Library functions described in "<a href="#functions">Time and date - functions</a>" above. + Library functions described in "<a href="#functions">Time and date + functions</a>" above. </li> <li> - The programs <code>tzselect</code>, <code>zdump</code>, - and <code>zic</code>, documented in their man pages. + The programs <code>tzselect</code>, <code>zdump</code>, + and <code>zic</code>, documented in their man pages. </li> <li> - The format of <code>zic</code> input files, documented in - the <code>zic</code> man page. + The format of <code>zic</code> input files, documented in + the <code>zic</code> man page. </li> <li> - The format of <code>zic</code> output files, documented in - the <code>tzfile</code> man page. + The format of <code>zic</code> output files, documented in + the <code>tzfile</code> man page. </li> <li> - The format of zone table files, documented in <code>zone1970.tab</code>. + The format of zone table files, documented in <code>zone1970.tab</code>. </li> <li> - The format of the country code file, documented in <code>iso3166.tab</code>. + The format of the country code file, documented in <code>iso3166.tab</code>. </li> <li> - The version number of the code and data, as the first line of - the text file '<code>version</code>' in each release. + The version number of the code and data, as the first line of + the text file '<code>version</code>' in each release. </li> </ul> + <p> Interface changes in a release attempt to preserve compatibility with -recent releases. For example, tz data files typically do not rely on -recently-added <code>zic</code> features, so that users can run -older <code>zic</code> versions to process newer data -files. <a href="tz-link.html">Sources for time zone and daylight -saving time data</a> describes how -releases are tagged and distributed. +recent releases. +For example, <code><abbr>tz</abbr></code> data files typically do not +rely on recently-added <code>zic</code> features, so that users can +run older <code>zic</code> versions to process newer data files. +<a href="tz-link.html#download">Downloading +the <code><abbr>tz</abbr></code> database</a> describes how releases +are tagged and distributed. </p> <p> -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. +Interfaces not listed above are less stable. +For example, users should not rely on particular <abbr>UT</abbr> +offsets or abbreviations for timestamps, as data entries are often +based on guesswork and these guesses may be corrected or improved. </p> - </section> - +</section> - <section> - <h2 id="calendar">Calendrical issues</h2> +<section> + <h2 id="calendar">Calendrical issues</h2> <p> 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 Nachum Dershowitz and Edward M. Reingold, -<cite><a href="https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/">Calendrical +extended the time zone database further into the past. +An excellent resource in this area is Nachum Dershowitz and Edward M. +Reingold, <cite><a +href="https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/">Calendrical Calculations: Third Edition</a></cite>, Cambridge University Press (2008). Other information and sources are given in the file '<samp>calendars</samp>' -in the tz distribution. They sometimes disagree. +in the <code><abbr>tz</abbr></code> distribution. +They sometimes disagree. </p> - </section> +</section> - - <section> - <h2 id="planets">Time and time zones on other planets</h2> +<section> + <h2 id="planets">Time and time zones on other planets</h2> <p> -Some people's work schedules use Mars time. Jet Propulsion Laboratory -(JPL) coordinators have kept Mars time on and off at least since 1997 -for the Mars Pathfinder mission. Some of their family members have -also adapted to Mars time. Dozens of special Mars watches were built -for JPL workers who kept Mars time during the Mars Exploration -Rovers mission (2004). These timepieces look like normal Seikos and -Citizens but use Mars seconds rather than terrestrial seconds. +Some people's work schedules +use <a href="https://en.wikipedia.org/wiki/Timekeeping on Mars">Mars time</a>. +Jet Propulsion Laboratory (JPL) coordinators have kept Mars time on +and off at least since 1997 for the +<a href="https://en.wikipedia.org/wiki/Mars_Pathfinder#End_of_mission">Mars +Pathfinder</a> mission. +Some of their family members have also adapted to Mars time. +Dozens of special Mars watches were built for JPL workers who kept +Mars time during the Mars Exploration Rovers mission (2004). +These timepieces look like normal Seikos and Citizens but use Mars +seconds rather than terrestrial seconds. </p> <p> 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. +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. </p> <p> -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). -</p> +The <a href="https://en.wikipedia.org/wiki/Prime_meridian">prime +meridian</a> of Mars goes through the center of the crater +<a href="https://en.wikipedia.org/wiki/Airy-0">Airy-0</a>, 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 <a href="https://en.wikipedia.org/wiki/Mars_Coordinated_Time">Mars +Coordinated Time (<abbr>MTC</abbr>)</a>. +</p> <p> Each landed mission on Mars has adopted a different reference for solar time keeping, so there is no real standard for Mars time zones. -For example, the Mars Exploration Rover project (2004) 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. Such a "time -zone" is not particularly suited for any application other than the -mission itself. +For example, the +<a href="https://en.wikipedia.org/wiki/Mars_Exploration_Rover">Mars +Exploration Rover</a> project (2004) 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. +Such a "time zone" is not particularly suited for any application +other than the mission itself. </p> <p> Many calendars have been proposed for Mars, but none have achieved -wide acceptance. Astronomers often use Mars Sol Date (MSD) which is a +wide acceptance. +Astronomers often use Mars Sol Date (<abbr>MSD</abbr>) which is a sequential count of Mars solar days elapsed since about 1873-12-29 -12:00 GMT. +12:00 <abbr>GMT</abbr>. </p> <p> 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. +like Earth's. +On other planets, Sun-based time and calendars would work quite +differently. +For example, although Mercury's +<a href="https://en.wikipedia.org/wiki/Rotation_period">sidereal +rotation period</a> 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 +<a href="https://en.wikipedia.org/wiki/Retrograde_motion">retrograde</a>: +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. </p> <p> -Although the tz database does not support time on other planets, it is -documented here in the hopes that support will be added eventually. +Although the <code><abbr>tz</abbr></code> database does not support +time on other planets, it is documented here in the hopes that support +will be added eventually. </p> <p> -Sources: +Sources for time on other planets: </p> + <ul> <li> -Michael Allison and Robert Schmunk, -"<a href="https://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical -Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a>" -(2015-06-30). + Michael Allison and Robert Schmunk, + "<a href="https://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical + Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a>" + (2015-06-30). </li> <li> -Jia-Rui Chong, -"<a href="http://articles.latimes.com/2004/jan/14/science/sci-marstime14">Workdays -Fit for a Martian</a>", Los Angeles Times -(2004-01-14), pp A1, A20-A21. + Jia-Rui Chong, + "<a href="http://articles.latimes.com/2004/jan/14/science/sci-marstime14">Workdays + Fit for a Martian</a>", <cite>Los Angeles Times</cite> + (2004-01-14), pp A1, A20-A21. </li> <li> -Tom Chmielewski, -"<a href="https://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-…">Jet -Lag Is Worse on Mars</a>", The Atlantic (2015-02-26) + Tom Chmielewski, + "<a href="https://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-…">Jet + Lag Is Worse on Mars</a>", <cite>The Atlantic</cite> (2015-02-26) </li> <li> -Matt Williams, -"<a href="https://www.universetoday.com/37481/days-of-the-planets/">How -long is a day on the other planets of the solar system?</a>" -(2017-04-27). + Matt Williams, + "<a href="https://www.universetoday.com/37481/days-of-the-planets/">How + long is a day on the other planets of the solar system?</a>" + (2017-04-27). </li> </ul> - </section> +</section> - <footer> - <hr> -This file is in the public domain, so clarified as of 2009-05-17 by -Arthur David Olson. - </footer> +<footer> + <hr> + This file is in the public domain, so clarified as of 2009-05-17 by + Arthur David Olson. +</footer> </body> </html> -- 2.7.4

1 0

Adding a "test" region?
by Paul G Jan. 26, 2018

Jan. 26, 2018

All this hubbub about the negative SAVE values in the tzdb source code makes it pretty obvious that downstream consumers are making some assumptions about undocumented features of the tzdb code. I'm wondering if it might be worth it to add a new region that contains fictional time zones that have properties that are perfectly valid but are edge cases that might be improperly handled downstream. It's probably a good idea to have this sort of thing in place *before* some region makes a change that actually violates one of these assumptions. A few example test cases I can think of (but I assume others will have *many* other ideas): - Zone with negative DST - Zone with large DST offset and/or large standard offset - Zone with 3, 4 or 5 offsets per year - Zone which goes from STD->DST with no change in offset. - Zone with new rules that don't take place until after 2038 - Zone with arbitrary DST offsets (10m15s, for example) - Zone that corresponds to TAI (e.g. offsets change to compensate for leap seconds) Downstream consumers could then use this in their test suites and be effectively "on notice" that they should be able to handle these sorts of cases, even though we have no examples of them existing in the wild (though there's actually some case to be made for interpreting TAI as a time zone, in which case that one *does* exist in the wild). There is some precedent for this sort of thing in the GREASE mechanism for testing TLS extensibility ( https://tools.ietf.org/html/draft-ietf-tls-grease-00 ), which provides some mechanism for testing whether TLS implementations will break if some arbitrary extensions are added. Best, Paul

12 31

Re: [tz] Irish Standard Time vs Irish Summer Time
by Paul Eggert Jan. 24, 2018

Jan. 24, 2018

On 01/23/2018 05:29 AM, Michael H Deckers wrote: > > The assertion > # ... but there's no > # convenient single notation for the date and time of this > transition > # so we must duplicate the Rule lines. > is clearly wrong when zic allows negative times of day with > the u suffix -- but it is still in australasia in 2018b. Good point. I reworded that in the attached patch, which also cleans up some other stale comments that I discovered while looking into this one. I installed this in the master branch, after 2018c was tagged. > Similarly, the (future) change in meaning for tm_isdst (from an > indicator of daylight saving time to one of non-standard time) > should be applied throughout the whole documentation of tzdb. > For instance, newctime.3.txt says > Tm_isdst is non-zero if summer time is in effect. > and this will probably become false (for the effect of > localtime()) after the change. It's probably better to consistently use the phrase "daylight saving time", as this is common usage (at least in the US) and it maps well to the tm_isdst variable of C. Logically DST can be observed in summer just as easily as in winter, and there's no logical requirement that it must advance the clock: after all, one can "save" daylight at the start of the day, and this is just as easy as "saving" it at the end.

2 1

Re: [tz] 2018c minor issue
by Paul Eggert Jan. 23, 2018

Jan. 23, 2018

On 01/23/2018 02:39 PM, Pascal Werz wrote: > I tried to build the 2018c release of tz code and data and found that > file zishrink.awk line 40: > gsub(/[\f\r\t\v ]+/, " ", line) > erroneously changed all 'v' characters to spaces as '\v' was not > recognized as an escape sequence (hence handled as 'v') on my OS. > Changing the line to > gsub(/[\f\r\t\013 ]+/, " ", line) > or removing '\v' from the regexp allowed the build to be possible again. Thanks for the bug report. I installed the attached, which should appear in the next release. POSIX requires awk to support \v but if mawk can stray from POSIX I suppose macOS awk can too.

2 1

[tz-announce] 2018c release of tz code and data available
by Paul Eggert Jan. 23, 2018

Jan. 23, 2018

The 2018c release of the tz code and data is available. It follows on the 2018a and 2018b releases, which were published but were not announced until now, due to problems discovered late in their release processes. 2018a had a build-failure typo, and 2018a and 2018b both had problems with ICU and Java, downstream packages which do not support a feature (negative DST offsets) used in 2018a and 2018b. The typo has been fixed, and data changes using negative DST offsets have been reverted pending development of a mechanism to export data to platforms lacking support for such data. The 2018a through 2018c releases reflect the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes. This announcement has merged the set of changes made by the three releases, to make it easier to see the difference between 2017c and 2018c; please see the 2018c NEWS file for more details about intermediate versions. Release 2018c - 2018-01-22 23:00:44 -0800 Release 2018b - 2018-01-17 23:24:48 -0800 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. Use Debian-style installation locations, instead of 4.3BSD-style. New zic option -t. Changes to past and future time stamps 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 time stamps 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 time stamps Japanese DST transitions (1948-1951) were Sundays at 00:00, not Saturdays or Sundays at 02:00. (Thanks to Takayuki Nikai.) 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 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.) The build procedure now works around mawk 1.3.3's lack of support for character class expressions. (Problem reported by Ohyama.) 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018c.tar.lz As usual, links to the latest release files are here: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP fromftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit ef4db72f1cbe1f7141f8aa012a624abb0a8d8059 dated 2018-01-22 23:00:44 -0800 and tagged '2018c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 21988e876479e38661d41ea4c7b5218ba14b979739d7ba8d49a2d343bb9f37c654056ab21c046a6652715f012e4ca33c4aa109b1ec3ac5d0244dd3a7ea9ed6d2 tzcode2018c.tar.gz 0575c87c9ffcde7b7f62b0df928d8a0e8d93f832b5ef7227b3d8431686f851f1fd5372c7e768f2979830352433b31df7f3979a00c28ea3973a3a0987ebbfb835 tzdata2018c.tar.gz a1686902f81b4aceba494797e4eb8cdb8c1037ab7a27df9635b7a45ecfd90b8cf7b605a252ad1a8c67394a578f95aa9dff03071bc871120a98328de437c19b4f tzdb-2018c.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40NNsP/i+4WUmbLMMZnnR9FTvRUILo UAHYZRqC1KbdMppKeeyTL6thANvjpMjeYM8V54tzndzrMhBaPc8SpiwVgTevRtKZ wG9BSb8Hx/RDQeBWOjRwFx5/WQ+ha4aK0IFB8KB5gNFLOuyMn+9ZaxSzoEXmNWX0 Ddoizk516lpfGuhZCnPMVtDorebaAby0d3WMCxzEJ2w3gLOI4Aj8WVR2Cl5eTlA/ cpQ+bzLog5lnf+mzs/bJeMlfxPSskAlvIBYk905uPTAT/LDeod+T+BLBfcGEUb5J D64veBERj01NDwVLDRqHG0hdw8aPdMQyTLje6fI7sVh2cu4lGgA7QxHC+aTnmYjt 862/wX7dx2HtfuaIr+6eulAIR3+rix0CMndEXUGLtqnx4WySh5rT++V4crGcgzSH eRl2TOkBBxpYLIK6KtHd31V5WhJfTN2NQOZEFdrxy+Z2pPWZJrhcB9+0tYGoRVs0 ARQdm5I1w5JwiHO7sI0YHWCPZCVhDC2+/Izg668OUIdmFpqXanMAADkT5Qo9frlu 72cnL0MFMB4JCQwbqE1Xa1AOzz6bUG7zUfRDyAH6wZyHIxZgr5PmbbfUfoagOD0J /psdEJNsOUdg+wDou23UVRyt9/WIiZbXKWVTs14DMuqrHLUQAcFQtpYwb/U3z5mR 0I0syyatHweHMeftotgJ =gt0T -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40WkcP/3/QD5VP4YT5/zLPqTE4hLMB iuNFJelf1Iv4hFXYCMhfnU+0MlUfvSBBKLI5uu1vTl48ms33Ku+CL6fKI8uIlwMG v0yTCOxRozMofUcjsm2IfGRlJgAajMPWDOGsD3jocX0Vf14m9siycy4xdBk7vNrs QUKL3zl0XOBQY51ivnYvEK/f8LJZzn7NHizL0VwI0rxO/Oj6o0Q2wWkE61tBS27r znn9lFRWH1Nh+TJ7Yh1mNAd4UOYGL9Q3eoWkl5MzPM3ujjVSdsEXhNLGemPrfE50 RzuvsLgiKqahBpC9Zxy39pqiO+riRKHLlNjxNcCeHw6M5w8/FuBwwozSmdchWaZn gD50k7az4F5nojUgzYTNGV6nW2CGflLLgOeUWMmYUyF999KpOJzLXNFqMuBYqOOu ODI7CJweT0/Ff9jjoKMSqg1rMMDEox/E127ms8uf6qGyjWvp0AQlA5O06bStfpjH HDJog9BcDXb64oiJsIg0K4UqqF1n7jMqiufhz4WhrqPqaTP9qJuorSn5yar/UsGc V2l2C+BdJhmsvQ9vkLrYJNWXks+oQSFJ1dYYpv+zp/MsiBV1/pKaYEXgurRfQBCW eHO57ovm2Pf59dghTnm7SyoiZeqCK/89MWxpX4YbDgzP4ZyBhS2g1/bk7toPajUa idAZsIgmZDmw77UHpPJu =nVJg -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40rDcP/3cxJ0Ri2s3WNCnu1woSJ3KU zRc5lvC4YZRo8/4yqEjzcq8M2eiYs540WqE4kPm9dFSefCOWX6nw5imrU2cM9EfJ XPyrZho+r85uH5KMCgQ9J+AC1HBya4TPdaTPikEYVARBMmkwLtM34FxJz2VnFRhT ZQjDG+ncZNhOBXWu6Mughb6I38Cl19/Dn2iQJ9p0XTay6uytCMceZ+o52bugeWCL HlRkGqZgW9cxFygq3EBEGWN/IcsdFSZqpHLVslD5xeZP294tCW0LsgE/SZ0YP1c3 Dd0KWeC4iYbrETda57XA9+27siXwhT9hVQnXVeykmsmn+TftZHh89A+bVYlglhIi QXRH2pi9OX/8DgsTox3mswAM2OPFiUgdOthwVdnrdHjhWc74SFr7AARSmoIVZHve gKIQXCuTV+mcVKZ6ibHZHs86QQ/jevcLivlQdOO9MMHVNMu5ZjBR6E3QjY5TTwcW 2UT/JEMMluYA+b5xVrGOwWa2g2vU/K1nvOVX73vT3n552djrZ6NholegrVVbcVjO GySPxMwjm1MMlmvXnN0cr4eWzFamVdMMSBkn8X/aBjbHAIvnqiqoxK/9JQf0wEZV lgGETcAvxr540LUuY0R95SO3qy4MXrT5USMDUSnif8BsNoLe5MEExAmVJ3A7W1sP 3/xQouSXzl63eYI3Rvam =WEKZ -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0