- tz - lists.iana.org

[PROPOSED 1/2] Czechs had negative DST in 1946/7
by Paul Eggert April 14, 2018

April 14, 2018

* NEWS: Document this. * europe (Czech): Adjust 1945 transition dates to match new source. (Europe/Prague): Likewise. Add negative DST in 1946/7. * tz-link.html: Link to kalendar.beda.cz. * ziguard.awk: Adjust to Czech changes. --- NEWS | 6 ++++++ europe | 24 +++++++++++++++++++++--- tz-link.html | 4 ++++ ziguard.awk | 10 ++++++++++ 4 files changed, 41 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 17492b3..13652fc 100644 --- a/NEWS +++ b/NEWS @@ -29,6 +29,12 @@ Unreleased, experimental changes format; in rearguard and main format, the tm_isdst flag is still zero in winter and nonzero in summer. + In 1946/7 Czechoslovakia also observed negative DST in winter. + The full effect of this change is only in vanguard format; in + rearguard and main formats, it is modeled as plain GMT without + daylight saving. Also, the dates of some 1944/5 DST transitions + in Czechoslovakia have been changed. + Release 2018d - 2018-03-22 07:05:46 -0700 diff --git a/europe b/europe index 20eb4e8..5edb686 100644 --- a/europe +++ b/europe @@ -970,9 +970,21 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 # Please see the 'asia' file for Asia/Nicosia. # Czech Republic / Czechia +# +# From Paul Eggert (2018-04-14): +# The source for Czech data is: Kdy začíná a končí letní čas. +# https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas +# with one correction, taken from: +# Sbírka zákonů a nařízení republiky Československé, částka 92/1946. +# http://ftp.aspi.cz/opispdf/1946/092-1946.pdf +# which says that the winter time (negative DST) starting 1946-12-01 +# was a switch from 03:00 to 02:00 (not from 02:00 to 01:00). +# We know of no English-language name for historical Czech winter time; +# abbreviate it as "GMT", as it happened to be GMT. +# # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S -Rule Czech 1945 only - Apr 8 2:00s 1:00 S -Rule Czech 1945 only - Nov 18 2:00s 0 - +Rule Czech 1945 only - Apr Mon>=1 2:00s 1:00 S +Rule Czech 1945 only - Oct 1 2:00s 0 - Rule Czech 1946 only - May 6 2:00s 1:00 S Rule Czech 1946 1949 - Oct Sun>=1 2:00s 0 - Rule Czech 1947 only - Apr 20 2:00s 1:00 S @@ -981,7 +993,13 @@ Rule Czech 1949 only - Apr 9 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Prague 0:57:44 - LMT 1850 0:57:44 - PMT 1891 Oct # Prague Mean Time - 1:00 C-Eur CE%sT 1944 Sep 17 2:00s + 1:00 C-Eur CE%sT 1945 May 9 + 1:00 Czech CE%sT 1946 Dec 1 3:00 +# Vanguard section, for zic and other parsers that support negative DST. +# 1:00 -1:00 GMT 1947 Feb 23 2:00 +# Rearguard section, for parsers that do not support negative DST. + 0:00 - GMT 1947 Feb 23 2:00 +# End of rearguard section. 1:00 Czech CE%sT 1979 1:00 EU CE%sT # Use Europe/Prague also for Slovakia. diff --git a/tz-link.html b/tz-link.html index 6700c7f..13a824d 100644 --- a/tz-link.html +++ b/tz-link.html @@ -728,6 +728,10 @@ zones & daylight saving time</a>.</dd> <dd>The Hydrographic and Oceanographic Service of the Chilean Navy publishes a <a href="http://www.horaoficial.cl/historia_hora.html" hreflang="es">history of Chile's official time (in Spanish)</a>.</dd> +<dt>Czech Republic</dt> +<dd><a href="https://kalendar.beda.cz/kdy-zacina-a-konci-letni-cas" +hreflang="cs">When daylight saving time starts and ends (in Czech)</a> +summarizes and cites historical DST regulations.</dd> <dt>Germany</dt> <dd>The National Institute for Science and Technology maintains the <a href="https://www.ptb.de/cms/en/fachabteilungen/abt4/fb-44/ag-441/realisation-of-…">Realisation diff --git a/ziguard.awk b/ziguard.awk index 5bfaebb..7cdceab 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -28,6 +28,16 @@ outfile != "main.zi" { in_comment = /^#/ uncomment = comment_out = 0 + # If the line should differ due to Czechoslovakia using negative SAVE values, + # uncomment the desired version and comment out the undesired one. + if (zone == "Europe/Prague" && /1947 Feb 23/) { + if (($(in_comment + 2) != "-") == vanguard) { + uncomment = in_comment + } else { + comment_out = !in_comment + } + } + # If this line should differ due to Ireland using negative SAVE values, # uncomment the desired version and comment out the undesired one. Rule_Eire = /^#?Rule[\t ]+Eire[\t ]/ -- 2.7.4

1 1

[PROPOSED] * europe: Remove "exactly" from comment; it was not exactly right.
by Paul Eggert April 14, 2018

April 14, 2018

--- europe | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/europe b/europe index 3f092a4..20eb4e8 100644 --- a/europe +++ b/europe @@ -2016,7 +2016,7 @@ Rule Neth 1938 1939 - May 15 2:00s 1:00 S Rule Neth 1945 only - Apr 2 2:00s 1:00 S Rule Neth 1945 only - Sep 16 2:00s 0 - # -# Amsterdam Mean Time was +00:19:32.13 exactly, but the .13 is omitted +# Amsterdam Mean Time was +00:19:32.13, but the .13 is omitted # below because the current format requires GMTOFF to be an integer. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Amsterdam 0:19:32 - LMT 1835 -- 2.14.3

1 0

[PROPOSED] Namibia was on DST until 2017-10-24
by Paul Eggert April 9, 2018

April 9, 2018

While we're at it, use negative DST offsets in vanguard format, since Namibia (like Ireland) used negative DST in winter. * NEWS, africa (Namibia, Africa/Windhoek), ziguard.awk: Implement this. --- NEWS | 10 ++++++++++ africa | 19 +++++++++++++++++-- ziguard.awk | 28 +++++++++++++++++++++++++--- 3 files changed, 52 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index 0297fd8..3bbb829 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,15 @@ News for the tz database +Unreleased, experimental changes + + Changes to past time stamps + + For Namibia's transition from +01/+02 to plain +02, change the + transition date from 2017-09-03 at 03:00 to 2017-10-24 at 00:00. + This does not affect UTC offsets, only whether a DST regime was + in place. + + Release 2018d - 2018-03-22 07:05:46 -0700 Briefly: diff --git a/africa b/africa index 2f7217a..e564906 100644 --- a/africa +++ b/africa @@ -992,9 +992,20 @@ Link Africa/Maputo Africa/Lusaka # Zambia # the same time they would normally start DST, the first Sunday in September: # https://www.timeanddate.com/news/time/namibia-new-time-zone.html +# From Paul Eggert (2017-04-05): +# The official date of the time zone change was 2017-10-24. See: +# http://www.lac.org.na/laws/annoSTAT/Namibian%20Time%20Act%209%20of%202017.p… + # RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S +# The following has standard time in summer and negative daylight +# saving time in winter. It is for when negative SAVE values are used. +# For more about this, see the comments in 'europe' for Rule Eire. +#Rule Namibia 1994 only - Mar 21 0:00 -1:00 +01 +#Rule Namibia 1994 2017 - Sep Sun>=1 2:00 0 CAT +#Rule Namibia 1995 2017 - Apr Sun>=1 2:00 -1:00 +01 +# The following is for when SAVE values are always nonnegative. Rule Namibia 1994 only - Mar 21 0:00 0 - -Rule Namibia 1994 2016 - Sep Sun>=1 2:00 1:00 S +Rule Namibia 1994 2017 - Sep Sun>=1 2:00 1:00 S Rule Namibia 1995 2017 - Apr Sun>=1 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 @@ -1003,7 +1014,11 @@ Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 2:00 1:00 SAST 1943 Mar 21 2:00 2:00 - SAST 1990 Mar 21 # independence 2:00 - CAT 1994 Mar 21 0:00 - 1:00 Namibia WA%sT 2017 Sep 3 2:00 +# The next line is for when negative SAVE values are used. +# 2:00 Namibia %s 2017 Oct 24 +# The next line is for when SAVE values are always nonnegative. + 1:00 Namibia WA%sT 2017 Oct 24 +# End of daylight saving. 2:00 - CAT # Niger diff --git a/ziguard.awk b/ziguard.awk index 6da3691..710b630 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -26,6 +26,7 @@ BEGIN { outfile != "main.zi" { in_comment = /^#/ + uncomment = comment_out = 0 # If this line should differ due to Ireland using negative SAVE values, # uncomment the desired version and comment out the undesired one. @@ -37,11 +38,32 @@ outfile != "main.zi" { if ((Rule_Eire \ || (Zone_Dublin_post_1968 && $(in_comment + 3) == "IST/GMT")) \ == vanguard) { - sub(/^#/, "") - } else if (/^[^#]/) { - sub(/^/, "#") + uncomment = in_comment + } else { + comment_out = !in_comment } } + + # If this line should differ due to Namibia using negative SAVE values, + # uncomment the desired version and comment out the undesired one. + Rule_Namibia = /^#?Rule[\t ]+Namibia[\t ]/ + Zone_using_Namibia_rule \ + = (zone == "Africa/Windhoek" && /^#?[\t ]+[12]:00[\t ]/ \ + && $(in_comment + 2) == "Namibia") + if (Rule_Namibia || Zone_using_Namibia_rule) { + if (in_comment == vanguard) { + uncomment = in_comment + } else { + comment_out = !in_comment + } + } + + if (uncomment) { + sub(/^#/, "") + } + if (comment_out) { + sub(/^/, "#") + } } # If a Link line is followed by a Zone line for the same data, comment -- 2.14.3

5 10

[PATCH] * Makefile, strftime.c, zic.8: alternate -> alternative
by Paul Eggert April 9, 2018

April 9, 2018

--- Makefile | 4 ++-- strftime.c | 2 +- zic.8 | 8 ++++---- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index 23599ce..2365d7c 100644 --- a/Makefile +++ b/Makefile @@ -21,7 +21,7 @@ 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). -# Alternately, if you discover you've got the wrong time zone, you can just +# Alternatively, if you discover you've got the wrong time zone, you can just # zic -l rightzone # to correct things. # Use the command @@ -38,7 +38,7 @@ LOCALTIME= GMT # template file are used to determine "spring forward" and "fall back" days and # times; the environment variable itself specifies UT offsets of standard and # daylight saving time. -# Alternately, if you discover you've got the wrong time zone, you can just +# Alternatively, if you discover you've got the wrong time zone, you can just # zic -p rightzone # to correct things. # Use the command diff --git a/strftime.c b/strftime.c index 6da3fb9..e855890 100644 --- a/strftime.c +++ b/strftime.c @@ -224,7 +224,7 @@ label: ** %Ec %EC %Ex %EX %Ey %EY ** %Od %oe %OH %OI %Om %OM ** %OS %Ou %OU %OV %Ow %OW %Oy - ** are supposed to provide alternate + ** are supposed to provide alternative ** representations. */ goto label; diff --git a/zic.8 b/zic.8 index 4251868..97644ac 100644 --- a/zic.8 +++ b/zic.8 @@ -372,7 +372,7 @@ begin the field with a minus sign if time must be subtracted from UT. .TP .B RULES The name of the rules that apply in the time zone or, -alternately, an amount of time to add to local standard time. +alternatively, an amount of time to add to local standard time. If this field is .B \*- then standard time always applies in the time zone. @@ -386,7 +386,7 @@ The pair of characters is used to show where the .q "variable part" of the time zone abbreviation goes. -Alternately, a format can use the pair of characters +Alternatively, a format can use the pair of characters .B %z to stand for the UT offset in the form .RI \(+- hh , @@ -399,7 +399,7 @@ using the shortest form that does not lose information, where and .I ss are the hours, minutes, and seconds east (+) or west (\(mi) of UT. -Alternately, +Alternatively, a slash (/) separates standard and daylight abbreviations. To conform to POSIX, a time zone abbreviation should contain only @@ -455,7 +455,7 @@ field should appear as the field in some zone line. The .B LINK-NAME -field is used as an alternate name for that zone; +field is used as an alternative name for that zone; it has the same syntax as a zone line's .B NAME field. -- 2.7.4

1 0

[PROPOSED 1/2] * .gitignore: Ignore .patch and .tzs files.
by Paul Eggert April 8, 2018

April 8, 2018

--- .gitignore | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitignore b/.gitignore index bc6fc25..1e62d11 100644 --- a/.gitignore +++ b/.gitignore @@ -3,8 +3,10 @@ *.a *.asc *.o +*.patch *.tar.* *.txt +*.tzs *.zi *~ ChangeLog -- 2.14.3

1 1

[PROPOSED] Mention Zone names with two slashes
by Paul Eggert April 6, 2018

April 6, 2018

* theory.html: Mention that some zone names have two slashes, e.g., America/Indiana/Petersburg. Use past tense for Mars Pathfinder. Avoid contractions. Use full zone names in examples and omit no-longer-needed quotes. Add URLs and fix typos. --- theory.html | 105 +++++++++++++++++++++++++++++++++++------------------------- 1 file changed, 61 insertions(+), 44 deletions(-) diff --git a/theory.html b/theory.html index 596b32c..ba57653 100644 --- a/theory.html +++ b/theory.html @@ -53,7 +53,7 @@ However, the database is not designed for and does not suffice for applications requiring accurate handling of all past times everywhere, as it would take far too much effort and guesswork to record all details of pre-1970 civil timekeeping. -Athough some information outside the scope of the database is +Although some information outside the scope of the database is collected in a file <code>backzone</code> that is distributed along with the database proper, this file is less reliable and does not necessarily follow database guidelines. @@ -79,7 +79,7 @@ flip back and forth between two alternatives, and the rules themselves can change at times. Whether and when a <code><abbr>tz</abbr></code> region changes its clock, and even the region's notional base offset from UTC, are variable. -It doesn't even really make sense to talk about a region's +It does not always make sense to talk about a region's "base offset", since it is not necessarily a single number. </p> @@ -92,8 +92,8 @@ Each <code><abbr>tz</abbr></code> region has a unique name that corresponds to a set of time zone rules. 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 <code><abbr>tz</abbr></code> code. +interface that explains the names; for one example, see the +<code>tzselect</code> 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. @@ -137,6 +137,9 @@ 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>'. +Some names are further qualified to help avoid confusion; for example, +'<code>America/Indiana/Petersburg</code>' distinguishes Petersburg, +Indiana from other Petersburgs in America. </p> <p> @@ -159,7 +162,8 @@ in decreasing order of importance: <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>'. + E.g., prefer <code>Asia/Brunei</code> to + <code>Asia/Bandar_Seri_Begawan</code>. Exceptions: see the discussion of legacy names below. </li> <li> @@ -177,8 +181,8 @@ in decreasing order of importance: 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>'. + 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 @@ -193,50 +197,56 @@ in decreasing order of importance: </li> <li> If all the clocks in a region have agreed since 1970, - don't bother to include more than one location + do not 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>'. + prefer <code>America/Costa_Rica</code> to + <code>America/San_Jose</code> and <code>America/Guyana</code> + to <code>America/Georgetown</code>. </li> <li> Keep locations compact. Use cities or small islands, not countries or regions, so that any future changes do not split individual locations into different <code><abbr>tz</abbr></code> regions. - E.g., prefer '<code>Paris</code>' to '<code>France</code>', since + E.g., prefer <code>Europe/Paris</code> to <code>Europe/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>'. + Use mainstream English spelling, e.g., prefer + <code>Europe/Rome</code> to <code>Europe/Roma</code>, and + prefer <code>Europe/Athens</code> to the Greek + <code>Europe/Αθήνα</code> or the Romanized + <code>Europe/Athína</code>. The POSIX file name restrictions encourage this guideline. </li> <li> Use the most populous among locations in a region, - e.g., prefer '<code>Shanghai</code>' to - '<code>Beijing</code>'. + e.g., prefer <code>Asia/Shanghai</code> to + <code>Asia/Beijing</code>. Among locations with similar populations, pick the best-known - location, e.g., prefer '<code>Rome</code>' to - '<code>Milan</code>'. + location, e.g., prefer <code>Europe/Rome</code> to + <code>Europe/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>Atlantic/Canary</code> to + <code>Atlantic/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>' + E.g., prefer <code>America/Cayman</code> to + <code>America/Cayman_Islands</code> and + <code>America/Guatemala</code> to + <code>America/Guatemala_City</code>, but prefer + <code>America/Mexico_City</code> to + <code>America/Mexico</code> because <a href="https://en.wikipedia.org/wiki/Time_in_Mexico">the country of Mexico has several time zones</a>. </li> @@ -245,13 +255,14 @@ in decreasing order of importance: </li> <li> Omit '<code>.</code>' from abbreviations in names. - E.g., prefer '<code>St_Helena</code>' to '<code>St._Helena</code>'. + E.g., prefer <code>Atlantic/St_Helena</code> to + <code>Atlantiic/St._Helena</code>. </li> <li> Do not change established names if they only marginally violate the above guidelines. - For example, don't change the existing name '<code>Rome</code>' to - '<code>Milan</code>' merely because Milan's population has grown + For example, do not change the existing name <code>Europe/Rome</code> to + <code>Europe/Milan</code> merely because Milan's population has grown to be somewhat greater than Rome's. </li> <li> @@ -318,8 +329,10 @@ in decreasing order of importance: 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 + space and '<code>?</code>', but these characters have a + special meaning to the + <a href="https://en.wikipedia.org/wiki/Unix_shell">UNIX shell</a> + 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. @@ -688,7 +701,7 @@ href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanes subsecond accuracy is needed. </li> <li> - Civil time was not based on atomic time before 1972, and we don't + Civil time was not based on atomic time before 1972, and we do not know the history of <a href="https://en.wikipedia.org/wiki/Earth's_rotation">earth's rotation</a> accurately enough to map <a @@ -720,7 +733,7 @@ href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanes 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. + and it is not clear how to apply it here. </li> </ul> @@ -764,7 +777,7 @@ an older <code>zic</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 + Also, POSIX <code>TZ</code> strings cannot deal with daylight saving time rules not based on the Gregorian calendar (as in Iran), or with situations where more than two time zone abbreviations or <abbr>UT</abbr> offsets are used in an area. @@ -874,7 +887,7 @@ an older <code>zic</code>. need access to multiple time zone rulesets. </li> <li> - In POSIX, there's no tamper-proof way for a process to learn the + In POSIX, there is 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 @@ -973,14 +986,16 @@ an older <code>zic</code>. 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 + if such code is moved to "old" systems that do not + provide <code>tzsetwall</code>, you will not be able to generate an executable program. (These 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 + indirectly – and there is no <code>TZ</code> environment variable; portable applications should not, however, rely on this - behavior since it's not the way SVR2 systems behave.) + behavior since it is not the way <a + href="https://en.wikipedia.org/wiki/UNIX_System_V#SVR2"><abbr>SVR2</abbr></a> + systems behave.) </li> <li> Negative <code>time_t</code> values are supported, on systems @@ -1040,7 +1055,7 @@ The vestigial <abbr>API</abbr>s are: <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 + package; it is 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. @@ -1052,7 +1067,9 @@ The vestigial <abbr>API</abbr>s are: zone abbreviation to use. </li> <li> - The <abbr>4.2BSD</abbr> <code>gettimeofday</code> function is not + The <a + href="https://en.wikipedia.org/wiki/History_of_the_Berkeley_Software_Distribution…"><abbr>4.2BSD</abbr></a> + <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 @@ -1061,7 +1078,7 @@ The vestigial <abbr>API</abbr>s are: <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>. + for places that do not 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. @@ -1170,11 +1187,11 @@ They sometimes disagree. <p> 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 +Jet Propulsion Laboratory (JPL) coordinators kept Mars time on +and off during 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. +Some of their family members also adapted to Mars time. Dozens of special Mars watches were built for JPL workers who kept Mars time during the Mars Exploration Rovers mission (2004). These timepieces look like normal Seikos and Citizens but use Mars @@ -1262,7 +1279,7 @@ Sources for time on other planets: 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. + (2004-01-14), pp A1, A20–A21. </li> <li> Tom Chmielewski, -- 2.14.3

2 2

Namibia Time Zone
by Mark Plaatje April 4, 2018

April 4, 2018

Good Day Kindly update your database to reflect that no Daylight Savings Time will be effected in 2018. https://www.timeanddate.com/time/change/namibia/windhoek?year=2018 https://www.namibian.com.na/65921/read/No-time-change-on-Sunday http://www.xinhuanet.com/english/2018-04/03/c_137086167.htm https://www.namibian.com.na/65942/read/Confusion-over-time-change Regards, Mark Plaatje Manager : Fraud Mobile Telecommunications Ltd Tel: +264818882842 Fax: E-mail: MPlaatje(a)mtc.com.na <mailto:MPlaatje@mtc.com.na>http://www.mtc.com.na [X]<http://www.mtc.com.na/> ________________________________ This e-mail message and any attachment are subject to the following terms and conditions http://www.mtc.com.na/legal/disclaimer

3 2

[PROPOSED] New edition of Calendrical Calculations
by Paul Eggert April 3, 2018

April 3, 2018

* theory.html (Calendrical issues): Update Reingold & Dershowitz citation to 4th edition. --- theory.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/theory.html b/theory.html index 4d8726d..596b32c 100644 --- a/theory.html +++ b/theory.html @@ -1155,10 +1155,10 @@ based on guesswork and these guesses may be corrected or improved. 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 -Calculations: Third Edition</a></cite>, Cambridge University Press (2008). +An excellent resource in this area is Edward M. Reingold +and Nachum Dershowitz, <cite><a +href="https://www.cambridge.org/fr/academic/subjects/computer-science/computing-g…">Calendrical +Calculations: The Ultimate Edition</a></cite>, Cambridge University Press (2018). Other information and sources are given in the file '<code>calendars</code>' in the <code><abbr>tz</abbr></code> distribution. They sometimes disagree. -- 2.7.4

4 6

How to force zic output to TZIF?
by Johan Kohler April 3, 2018

April 3, 2018

Hi, I have a tz client that expects the tzdata in format TZIF (that's version \nul). It has become necessary to update the tzdata but it is not feasible to update the client. Is it possible with the current 2018d release to generate output in TZIF format (as opposed to TZIF2 or TZIF3)? If so, what needs to be modified? If not, what is the suggested approach? Thanks, Johan

2 2

Western Australia time zone January 1, 2019
by Paul Eggert April 2, 2018

April 2, 2018

Today the Guardian Express of Perth reported that the government of Western Australia has decided to advance the clocks permanently from +0800 to +0900 on January 1, 2019. Presumably the time will still be called Australian Western Standard Time (AWST), as it will still differ by 30 minutes from ACST (+0930). For now, I suppose we should guess that Australia/Eucla will simultaneously switch from +0845 to +0915 so as to stay halfway between AWST and ACST. Proposed patch attached. The article concludes that the government has made several concessions to residents opposed to the measure, and lists some of them. One is that "people over the age of 60 concerned about colour bleaching from drapes and blinds can apply in writing to have the extra hour of sunshine removed from their area." See: Daylight saving coming to WA in 2019. Guardian Express. 2018-04-01. https://www.communitynews.com.au/guardian-express/news/exclusive-daylight-s…

5 5

US marks centennial of daylight saving
by Paul Eggert March 30, 2018

March 30, 2018

Tonight marks 100 years since the introduction of daylight saving time as United States federal law. On March 30/31, 1918, New York City held a New-Year's-style celebration for the public in Madison Square Garden, along with a reception at the Aldine Club for the elite. The guest of honor was Marcus M. Marks, president of the Daylight Saving Association, and uncle of the now-more-famous Johnny Marks (who was later to write "Rudolph the Red-Nosed Reindeer"). Among other things, Marks got to push the button that advanced the 8-meter clocks atop what is now known as the Met Life Tower. See: Change in time begins tomorrow. Government's new daylight regulation goes into effect at 2 A. M. No confusion expected. New York Times. 1918-03-30. https://www.nytimes.com/packages/html/mobile/change-in-time.pdf

1 0

[PROPOSED] * tz-link.html: Add worldclock.com.
by Paul Eggert March 26, 2018

March 26, 2018

--- tz-link.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tz-link.html b/tz-link.html index 7221777..6700c7f 100644 --- a/tz-link.html +++ b/tz-link.html @@ -239,8 +239,9 @@ These are listed roughly in ascending order of complexity and fanciness. <ul> <li><a href="https://time.is">Time.is</a> shows locations' time and zones.</li> -<li><a href="https://www.timejones.com">TimeJones.com</a> -and <a href="https://timezoneconverterapp.com">Time Zone Converter</a> +<li><a href="https://www.timejones.com">TimeJones.com</a>, +<a href="https://timezoneconverterapp.com">Time Zone Converter</a> and +<a href="http://worldclock.com">The World Clock</a> are time zone converters.</li> <li><a href="http://twiki.org/cgi-bin/xtra/tzdatepick.html">Date and Time Gateway</a> -- 2.7.4

1 0

Re: [tz] [PATCH1/1] Propose new zone for Crozet Islands
by REMI ACIEN March 25, 2018

March 25, 2018

Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 A new zone for Crozet Islands . Why not .

4 5

[PROPOSED] Spelling fixes
by Paul Eggert March 23, 2018

March 23, 2018

--- NEWS | 2 +- asia | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 8afe3a4..0297fd8 100644 --- a/NEWS +++ b/NEWS @@ -39,7 +39,7 @@ Release 2018d - 2018-03-22 07:05:46 -0700 Enderbury and Kiritimati skipped New Year's Eve 1994, not New Year's Day 1995. (Thanks to Kerry Shetline.) - Fix the 1912-01-01 transition for Portugual and its colonies. + Fix the 1912-01-01 transition for Portugal and its colonies. This transition was at 00:00 according to the new UT offset, not according to the old one. Also assume that Cape Verde switched on the same date as the rest, not in 1907. This affects diff --git a/asia b/asia index 998a7d4..7a6294a 100644 --- a/asia +++ b/asia @@ -2658,7 +2658,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # From Sharef Mustafa (2018-03-16): # Palestine summer time will start on Mar 24th 2018 by advancing the # clock by 60 minutes as per Palestinian cabinet decision published on -# the offical website, though the decree did not specify the exact +# the official website, though the decree did not specify the exact # time of the time shift. # http://www.palestinecabinet.gov.ps/Website/AR/NDecrees/ViewFile.ashx?ID=e7a… # -- 2.14.3

1 0

[tz-announce] 2018d release of tz code and data available
by Paul Eggert March 23, 2018

March 23, 2018

The 2018d release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Palestine starts DST a week earlier in 2018. Add support for vanguard and rearguard data consumers. Add subsecond precision to source data format, though not to data. Changes to future time stamps In 2018, Palestine starts DST on March 24, not March 31. Adjust future predictions accordingly. (Thanks to Sharef Mustafa.) Changes to past and future time stamps Casey Station in Antarctica changed from +11 to +08 on 2018-03-11 at 04:00. (Thanks to Steffen Thorsen.) Changes to past time stamps Historical transitions for Uruguay, represented by America/Montevideo, have been updated per official legal documents, replacing previous data mainly originating from the inventions of Shanks & Pottenger. This has resulted in adjustments ranging from 30 to 90 minutes in either direction over at least two dozen distinct periods ranging from one day to several years in length. A mere handful of pre-1991 transitions are unaffected; data since then has come from more reliable contemporaneous reporting. These changes affect various timestamps in 1920-1923, 1936, 1939, 1942-1943, 1959, 1966-1970, 1972, 1974-1980, and 1988-1990. Additionally, Uruguay's pre-standard-time UT offset has been adjusted westward by 7 seconds, from UT-03:44:44 to UT-03:44:51, to match the location of the Observatory of the National Meteorological Institute in Montevideo. (Thanks to Jeremie Bonjour, Tim Parenti, and Michael Deckers.) Enderbury and Kiritimati skipped New Year's Eve 1994, not New Year's Day 1995. (Thanks to Kerry Shetline.) Fix the 1912-01-01 transition for Portugual and its colonies. This transition was at 00:00 according to the new UT offset, not according to the old one. Also assume that Cape Verde switched on the same date as the rest, not in 1907. This affects Africa/Bissau, Africa/Sao_Tome, Asia/Macau, Atlantic/Azores, Atlantic/Cape_Verde, Atlantic/Madeira, and Europe/Lisbon. (Thanks to Michael Deckers.) Fix an off-by-1 error for pre-1913 timestamps in Jamaica and in Turks & Caicos. Changes to past time zone abbreviations MMT took effect in Uruguay from 1908-06-10, not 1898-06-28. There is no clock change associated with the transition. Changes to build procedure The new DATAFORM macro in the Makefile lets the installer choose among three source data formats. The idea is to lessen downstream disruption when data formats are improved. * DATAFORM=vanguard installs from the latest, bleeding-edge format. DATAFORM=main (the default) installs from the format used in the 'africa' etc. files. DATAFORM=rearguard installs from a trailing-edge format. Eventually, elements of today's vanguard format should move to the main format, and similarly the main format's features should eventually move to the rearguard format. * In the current version, the main and rearguard formats are identical and match that of 2018c, so this change does not affect default behavior. The vanguard format currently contains one feature not in the main format: negative SAVE values. This improves support for Ireland, which uses Irish Standard Time (IST, UTC+01) in summer and GMT (UTC) in winter. tzcode has supported negative SAVE values for decades, and this feature should move to the main format soon. However, it will not move to the rearguard format for quite some time because some downstream parsers do not support it. * The build procedure constructs three files vanguard.zi, main.zi, and rearguard.zi, one for each format. 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 do not support negative SAVE values should start using rearguard.zi, so that they will be unaffected when the negative-DST feature moves from vanguard to main. Bleeding-edge Zoneinfo parsers that support the new features already can use vanguard.zi; in this respect, current tzcode is bleeding-edge. The Makefile should now be safe for parallelized builds, and 'make -j to2050new.tzs' is now much faster on a multiprocessor host with GNU Make. When built with -DSUPPRESS_TZDIR, the tzcode library no longer prepends TZDIR/ to file names that do not begin with '/'. This is not recommended for general use, due to its security implications. (From a suggestion by Manuela Friedrich.) Changes to code zic now accepts subsecond precision in expressions like 00:19:32.13, which is approximately the legal time of the Netherlands from 1835 to 1937. However, because it is questionable whether the few recorded uses of non-integer offsets had subsecond precision in practice, there are no plans for tzdata to use this feature. (Thanks to Steve Allen for pointing out the limitations of historical data in this area.) The code is a bit more portable to MS-Windows. Installers can compile with -DRESERVE_STD_EXT_IDS on MS-Windows platforms that reserve identifiers like 'localtime'. (Thanks to Manuela Friedrich). Changes to documentation and commentary theory.html now outlines tzdb's extensions to POSIX's model for civil time, and has a section "POSIX features no longer needed" that lists POSIX API components that are now vestigial. (From suggestions by Steve Summit.) It also better distinguishes time zones from tz regions. (From a suggestion by Guy Harris.) Commentary is now more consistent about using the phrase "daylight saving time", to match the C name tm_isdst. Daylight saving time need not occur in summer, and need not have a positive offset from standard time. Commentary about historical transitions in Uruguay has been expanded with links to many relevant legal documents. (Thanks to Tim Parenti.) Commentary now uses some non-ASCII characters with Unicode value less than U+0100, as they can be useful and should work even with older editors such as XEmacs. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018d.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018d.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 from ftp://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 bd850bce5d292caaa5eba2c2088f6d4ad8024647 dated 2018-03-22 07:05:46 -0700 and tagged '2018d' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: e79a95e235cd384247e4112d5154f30eb7b40f28dab4872ed9153e45bf56569949d0845bc1b9ad24b7a5f9609bdadfc892959dbf0d540dbca79b18398dc4f930 tzcode2018d.tar.gz ee961aedc34e134172523a29fb8a9358f42649d06ffcd2d8a6ad86eeb174a80af5bfc4637e9e52ecdc51fa3d01afef9fff660a69ed72904ff747a59b5634830b tzdata2018d.tar.gz 12c839846c147b83ace915e399fe447f93e83b500327fb4549b6039615f548d7167594168b5c4779ee1f33d7a1b8c2e294aa13cd35823d778617065ad9ad8ea5 tzdb-2018d.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pNAAoJEO2X6Q5iqn40dn8P+gI1f6sWKcA8iuDkRWundwBk Y92iYPChJDbgUSiWw3o+qyFmVUz0P1PZkB3rCTFhtyY8u6zCiO4+6xADyS+le3II iwwIg2yCqPxBXDXYkcFvSrXDuOo1hG009L1k9nKmv6RvO7lvr/o0K/pRQTWKiV2w jS9gPZeZ/ggTdcyaD9tzFNwDe0nCg54rwFs3Gy+YK2+8fNhLmYJCp3WJydza9zgU pBMMP868h1ZY9uWEZcWX3mstyKD4egFRfyHMj4XPVrnGwpMT5u7groiq2TZv/MXV A/HDxa4jU+El6RW0TwAVnGEwUSJ3L3I7B6/Pbf3jf+VCTYkw67cX/WrtSNop1E03 ujPZVqYr5N8HLu/VO/R2R+OccvMZ1X/URehA4068w/+ESG8X8AbRVBYGavpFmnUv uHOeOFgzcJUQqFU1fqAEdhlrYqqbnsRFJN8QX1QWwQs5fUAzNSAkAB+kTEVCAvhK 1xaxlNaZqoWqT0bYvD2TL+VLkPNHvu8RMpa/rhmjE23AWfYuSJsAABNMBpB5t6ux SbBOBeJ+a5a1rZwya0hxeX6A3BCBPXKBjnt8MjBnV1s8Ns4Ng7jQ5ZqOXtlSo4ER fYHbVQITXnE+DbuM1zF6RY1dwmCLvkxpdM5lifgiYCdcDzttsifDdrq5WM+pJsz5 3yTFJFsk6et2ekpHRugZ =MMy8 -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pNAAoJEO2X6Q5iqn40BqwP/A8PU9mzxssBdQirWsuGhN3E +3hk6i7UFLrCHixbpN03y7r8ujkhRvkjLSrA2tcrYEK9t8NLkhQIrnmlVjEOQEcz +qiZWJV55kd2dhk2EE+pc8xXuqRsnId4r/xCF+D2wxl6IZpMEFelRCRiCGgszhDS FSv3UjlnpBv3uB5UgKdOFJKYcTvfOZ5jmpt1O6Ma9YNxqlc2+s8hUBR3VEtzancU +AyCoL/sUrijfGOZPSznhGJJ3lC5LkjkWqC0BYB5EI3YeClVtGWoZlD64jShJhWT pe3CAimaEibz1ty1tGz4Agdd0vQErvyCPQY6wy1pRYPW5wb++JomMVub7Uh7w/6o pvrkVaVqeiWeENoI6NRnmC+ANSaz6/lF61HM36VZ1XaCgmeCDaLHn31WKHRPctse r26++PyCIJwllaTNfGynjkAKUeBJJwwR8a/sjPeqEfEgoDKV1EpQVCBbPna3hmTq 8nzt11WsTNG+aocYr3hevSYiyxEWOLp5O9UaiTtVDc91Mhk2U9E9Fa7Zva35ZhjJ oRPS+AU5GFfWzgiW8XOLURqvwRNqUUudNaXy2wVuzwROdmboyewzB//MBavkI+r+ raI+coG2ZJoPcQmuRCUcjs1+JnNBL3sZT68/jTy2w0LURfUP9V+dUuJgjtRbMCtb Myzq3RCYNI/x3EjU/xcb =ibli -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJas7pOAAoJEO2X6Q5iqn40ursP/02PBDqd4eb8qrKrjScYt+I4 wnXMcjy9AmsfhPq1k1x6ZUI5qIbidrMD9S9m4NwKBGyvGxxcneWWJ5Yoln+K95YJ tCtm40eHypeVUlsXJExv3JB0hJ7d7eY2olbY/DcK6CTYt7R4amGU/ClCQpEIVTz2 HcVeH8oOPRUG0STyzKh2lPF0Wua6LUGp9/nZWgsETsXrAQ8MaC/vlyrjiEJsvwP1 65bOoNiRKiGU7tp6JhFE8v85vLKgkzmHeysWJdMt0aczH1DMwlSWS9ViEauLugK7 K0ERNC22WwEzya0EKmTMcRFHYIT1B9/dg0Tbb2h2KKRqu7kzd2NVr6ap5Cu6ezYO hThz6i09OL6ADSwSk4c6JeUUjX7rGG6DNu0pCQYlNJ9xIhi+U/FAuTvzBfU3uJe3 8akO1UGwUWA/TwtnQTv08uGGia+Wt/GbQStkidZFVvdbXcjSH39GlhRXRWDKSOCv wDVNMkopDQOsxwoFgAE45dacQZh2Qv29eT4pG6Eo2J+eXJR2lb5edQkDZNLk2DcE 6frcVchrdBeaUUSA1+ssH3B+hVwwJ7IX/FCwhKDZgxyy67oqGVChkeUjes4GJ5vB 0t7/XZTORvsH6XwBNDKoXS0fswtZiwhPr3YV1nZHwKCa0OWIs9WsPt587K82Hlsf mROMmzivSut43pdALRCr =zKoc -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

[PROPOSED] * tz-link.html: Tweak URLs.
by Paul Eggert March 22, 2018

March 22, 2018

--- tz-link.html | 56 +++++++++++++++++++++++++++----------------------------- 1 file changed, 27 insertions(+), 29 deletions(-) diff --git a/tz-link.html b/tz-link.html index f3ac4ed..7221777 100644 --- a/tz-link.html +++ b/tz-link.html @@ -7,7 +7,9 @@ <body> <h1>Sources for time zone and daylight saving time data</h1> <p> -Time zone and daylight saving rules are controlled by individual +<a href="https://en.wikipedia.org/wiki/Time_zone">Time zone</a> and +<a href="https://en.wikipedia.org/wiki/Daylight_saving_time">daylight-saving</a> +rules are controlled by individual governments. They are sometimes changed with little notice, and their histories and planned futures are often recorded only fitfully. Here is a summary of attempts to organize and record relevant data in this @@ -20,12 +22,9 @@ time zone database contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies -to <a href="https://en.wikipedia.org/wiki/Time_zone">time zone</a> -boundaries and -<a href="https://en.wikipedia.org/wiki/Daylight_saving_time">daylight-saving</a> -rules. -This database (often called <code>zoneinfo</code> or -<code><abbr>tz</abbr></code>) +to time zone boundaries and daylight saving rules. +This database (known as <code><abbr>tz</abbr></code>, +<code><abbr>tzdb</abbr></code>, or <code>zoneinfo</code>) is used by several implementations, including <a href="https://www.gnu.org/software/libc/">the @@ -109,7 +108,7 @@ gzip -dc tzdata-latest.tar.gz | tar -xf - release in a single-tarball format containing extra data useful for regression testing:</p> <pre style="margin-left: 2em"><code>wget <a href="https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz">https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz</a> -<a href="http://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | tar -xf - +<a href="https://www.nongnu.org/lzip/">lzip</a> -dc tzdb-latest.tar.lz | tar -xf - </code></pre> <p>These commands use convenience links to the latest release of the <code><abbr>tz</abbr></code> database hosted by the @@ -130,7 +129,7 @@ Since version 2016h, each release has contained a text file named The releases are also available in an <a href="ftp://ftp.iana.org/tz/releases/"><abbr title="File Transfer Protocol">FTP</abbr> directory</a> via a -less-secure protocol .</p> +less-secure protocol.</p> <p>Alternatively, a development repository of code and data can be retrieved from <a href="https://github.com">GitHub</a> via the shell command:</p> @@ -192,7 +191,7 @@ href="http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html Java, <a href="http://www.joda.org/joda-time/tz_update.html">Joda-Time</a>, <a href="https://dev.mysql.com/doc/refman/en/time-zone-support.html">MySQL</a>, and <a -href="http://nodatime.org/userguide/tzdb">Noda Time</a> (see below). +href="https://nodatime.org/userguide/tzdb">Noda Time</a> (see below). </p> <p>Sources for the <code><abbr>tz</abbr></code> database are <a href="https://en.wikipedia.org/wiki/UTF-8"><abbr @@ -203,7 +202,7 @@ title="linefeed">LF</abbr></a>, which can be modified by common text editors such as <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>, <a href="https://wiki.gnome.org/Apps/Gedit">gedit</a>, and -<a href="http://www.vim.org">vim</a>. +<a href="https://www.vim.org">vim</a>. Specialized source-file editing can be done via the <a href="https://packagecontrol.io/packages/zoneinfo">Sublime zoneinfo</a> package for <a @@ -258,7 +257,7 @@ timezone information for all countries</a> displays tables of DST rules. Worldwide</a> lets you sort zone names and convert times.</li> <li><a href="https://24timezones.com">24TimeZones</a> has a world time map and a time converter.</li> -<li><a href="http://www.zeitverschiebung.net/en/">Time Difference</a> +<li><a href="https://www.zeitverschiebung.net/en/">Time Difference</a> calculates the current time difference between locations.</li> <li><a href="http://www.wx-now.com">Weather Now</a> and <a href="http://www.thetimenow.com">The Time Now</a> list the weather too.</li> @@ -290,7 +289,7 @@ variant <a href="https://tools.ietf.org/html/rfc6321">xCal</a> title="Extensible Markup Language">XML</abbr></a> format, and a variant <a href="https://tools.ietf.org/html/rfc7265">jCal</a> (Internet <abbr>RFC</abbr> 7265) -uses <a href="http://www.json.org"><abbr +uses <a href="https://www.json.org"><abbr title="JavaScript Object Notation">JSON</abbr></a> format.</li> </ul> <h2 id="compilers">Other <code><abbr>tz</abbr></code> compilers</h2> @@ -374,7 +373,7 @@ License">LGPL</abbr>)</a>.</li> <li><abbr>ICU</abbr> (mentioned <a href="#ICU">above</a>) contains compilers and Java-based libraries.</li> </ul> -<li><a href="http://nodatime.org">Noda Time – Date and +<li><a href="https://nodatime.org">Noda Time – Date and time <abbr>API</abbr> for .NET</a> and <a href="http://www.babiej.demon.nl/Tz4Net/main.htm">TZ4Net</a> are similar to Joda-Time and Time4J, but for the .NET framework instead of @@ -458,7 +457,7 @@ library that reads tz binary files and converts time stamps from one time zone or format to another. It is used by <a href="https://secure.php.net"><abbr title="PHP: Hypertext Preprocessor">PHP</abbr></a>, -<a href="http://hhvm.com"><abbr title="HipHop Virtual Machine">HHVM</abbr></a>, +<a href="https://hhvm.com"><abbr title="HipHop Virtual Machine">HHVM</abbr></a>, and <a href="https://www.mongodb.com">MongoDB</a>. It is freely available under the <abbr>MIT</abbr> license.</li> <li><a href="https://github.com/bigeasy/timezone">Timezone</a> is a @@ -518,7 +517,7 @@ the older, proprietary method of Microsoft Windows 2000 and later, which stores time zone data in the <a href="https://en.wikipedia.org/wiki/Windows_Registry">Windows Registry</a>. The <a -href="http://unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → +href="https://unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → Tzid table</a> or <a href="https://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml"><abbr>XML</abbr> file</a> of the <abbr>CLDR</abbr> data maps proprietary zone IDs @@ -528,7 +527,7 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="http://www.relativedata.com/time-zone-master">Time Zone +<li><a href="https://www.relativedata.com/time-zone-master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version is free.</li> @@ -543,8 +542,8 @@ licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> <li><a href="https://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's time zone history atlases also published in <a -href="http://astrocom.com/astrology-products/software/acs-atlas-software">software</a> -form by <a href="http://astrocom.com">ACS-Starcrafts</a>. +href="https://astrocom.com/astrology-products/software/acs-atlas-software">software</a> +form by <a href="https://astrocom.com">ACS-Starcrafts</a>. These atlases are extensive but unreliable, as Shanks appears to have guessed many <abbr>UT</abbr> offsets and transitions. The atlases cite no sources and do not indicate which entries are guesswork.</li> @@ -552,7 +551,7 @@ sources and do not indicate which entries are guesswork.</li> its own <code>tztab</code>(4) format.</li> <li>Microsoft Windows has proprietary data mentioned <a href="#System.TimeZoneInfo">above</a>.</li> -<li><a href="http://www.worldtimeserver.com">World Time Server</a> +<li><a href="https://www.worldtimeserver.com">World Time Server</a> is another time zone database.</li> <li><a href="http://tycho.usno.navy.mil/tzones.html">World Time Zones</a> contains data from the Time Service Department of the @@ -578,14 +577,14 @@ recent editions. The pictorial quality is good, but the maps do not indicate daylight saving time, and parts of the data are a few years out of date.</li> -<li><a href="http://www.worldtimezone.com">Current time around the world +<li><a href="https://www.worldtimezone.com">Current time around the world and standard time zones map of the world</a> has several fancy time zone maps; it covers Russia particularly well. The maps' pictorial quality is not quite as good as the <abbr>CIA</abbr>'s but the maps are more up to date.</li> <li><a -href="http://blog.poormansmath.net/how-much-is-time-wrong-around-the-world/">How +href="https://blog.poormansmath.net/how-much-is-time-wrong-around-the-world/">How much is time wrong around the world?</a> maps the difference between mean solar and standard time, highlighting areas such as western China where the two differ greatly. It's a bit out of date, unfortunately.</li> @@ -666,9 +665,8 @@ political subdivision data related to time zones.</li> <li><a href="http://home.kpn.nl/vanadovv/time/Multizones.html">Time zone boundaries for multizone countries</a> summarizes legal boundaries between time zones within countries.</li> -<li>Manifold.net's <a -href="http://manifold.net/info/freestuff.shtml">Free Downloads for -Manifold System Users</a> includes a Manifold-format map of +<li><a href="http://manifold.net/info/freestuff.shtml">Manifold Software +– GIS and Database Tools</a> includes a Manifold-format map of world time zone boundaries distributed under the <abbr>GPL</abbr>.</li> <li>A ship within the <a @@ -808,12 +806,12 @@ href="https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol"><abbr>D option for a server to configure a client's time zone and daylight saving settings automatically.</li> <li><a -href="http://www.cv.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical +href="https://www.cv.nrao.edu/~rfisher/Ephemerides/times.html">Astronomical Times</a> explains more abstruse astronomical time scales like <abbr title="Terrestrial Dynamic Time">TDT</abbr>, <abbr title="Geocentric Coordinate Time">TCG</abbr>, and <abbr title="Barycentric Dynamic Time">TDB</abbr>. -<a href="http://www.ucolick.org/~sla/leapsecs/timescales.html">Time +<a href="https://www.ucolick.org/~sla/leapsecs/timescales.html">Time Scales</a> goes into more detail, particularly for historical variants.</li> <li>The <a href="https://www.iau.org"><abbr title="International Astronomical Union">IAU</abbr></a>'s <a @@ -859,7 +857,7 @@ and Klepczynski's 1999 proposal to discontinue leap seconds</a>, discussed further in <a href="https://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf">The leap second: its history and possible future</a>. -<a href="http://www.ucolick.org/~sla/leapsecs/"><abbr>UTC</abbr> +<a href="https://www.ucolick.org/~sla/leapsecs/"><abbr>UTC</abbr> might be redefined without Leap Seconds</a> gives pointers on this contentious issue, which was active until 2015 and could become active @@ -873,7 +871,7 @@ zone names, abbreviations, identifiers, and formats. For example, it contains French translations for "Eastern European Summer Time", "<abbr title="Eastern European Summer Time">EEST</abbr>", and "Bucharest". Its -<a href="http://unicode.org/cldr/charts/latest/by_type/">by-type +<a href="https://unicode.org/cldr/charts/latest/by_type/">by-type charts</a> show these values for many locales. Data values are available in both <abbr title="Locale Data Markup Language">LDML</abbr> (an <abbr>XML</abbr> format) and <abbr>JSON</abbr>. -- 2.7.4

1 0

Re: [tz] proposed tz data changes for Iran, Sri Lanka, Alberta, Thule, etc.
by REMI ACIEN March 21, 2018

March 21, 2018

Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10 For Zone Asia/Seoul +8 :27 :52 . Why not .

3 2

[PROPOSED] Put ziguard.awk in tzdata and tzdb tarballs
by Paul Eggert March 20, 2018

March 20, 2018

(Problem reported by Patsy Franklin.) * Makefile (AWK_SCRIPTS): Add ziguard.awk. --- Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 3c0479a..c69e01b 100644 --- a/Makefile +++ b/Makefile @@ -486,7 +486,8 @@ 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 +AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk \ + ziguard.awk zishrink.awk MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl TZS_YEAR= 2050 TZS= to$(TZS_YEAR).tzs @@ -903,6 +904,9 @@ tarballs traditional_tarballs signatures traditional_signatures: version VERSION=`cat version` && \ $(MAKE) VERSION="$$VERSION" $@_version +# These *_version rules are intended for use if VERSION is set by some +# other means. Ordinarily these rules are used only by the above +# non-_version rules, which set VERSION on the 'make' command line. tarballs_version: traditional_tarballs_version tzdb-$(VERSION).tar.lz traditional_tarballs_version: \ tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz -- 2.14.3

1 0

switches at 1883-11-18 at the same instant
by Michael H Deckers March 20, 2018

March 20, 2018

On 2018-03-19 09:18, Glenn A. Walsh wrote in a post to a different mailing list: > Centennial: Official Enactment of U.S. Time Zones & Daylight Saving Time > A century ago today (March 19), U.S.President Woodrow Wilson signed into law the Standard Time Act of1918, which officially established time zones in the United States aswell as Daylight Saving Time. Although time zones had beenunofficially observed for a few decades. > MORE INFO - CLICK ON IMAGE OR LINK --- LIKE THIS POST? - PLEASE SHARE! > Link >>> http://spacewatchtower.blogspot.com/2018/03/centennial-official-enactment-o… > The link describes (among many other things) how the Allegheny Observatory synchronized the switch of US railway times to grid time zones. As one would expect, the switch was done at a single instant, when UT was 1883-11-18 + 18 h. This differs from the current description in tzdb which uses different instants for different target time zones -- not a likely choice for simplifying a nationwide railway schedule. Thus I propose: - Zone America/Los_Angeles -7:52:58 - LMT 1883 Nov 18 12:07:02 + Zone America/Los_Angeles -7:52:58 - LMT 1883 Nov 18 10:07:02 - Zone America/Boise -7:44:49 - LMT 1883 Nov 18 12:15:11 + Zone America/Boise -7:44:49 - LMT 1883 Nov 18 10:15:11 - Zone America/Phoenix -7:28:18 - LMT 1883 Nov 18 11:31:42 + Zone America/Phoenix -7:28:18 - LMT 1883 Nov 18 10:31:42 - Zone America/Denver -6:59:56 - LMT 1883 Nov 18 12:00:04 + Zone America/Denver -6:59:56 - LMT 1883 Nov 18 11:00:04 - Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 12:12:53 + Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 11:12:53 - Zone America/North_Dakota/New_Salem -6:45:39 - LMT 1883 Nov 18 12:14:21 + Zone America/North_Dakota/New_Salem -6:45:39 - LMT 1883 Nov 18 11:14:21 - Zone America/North_Dakota/Center -6:45:12 - LMT 1883 Nov 18 12:14:48 + Zone America/North_Dakota/Center -6:45:12 - LMT 1883 Nov 18 11:14:48 - Zone America/New_York -4:56:02 - LMT 1883 Nov 18 12:03:58 + Zone America/New_York -4:56:02 - LMT 1883 Nov 18 13:03:58 Michael Deckers.

3 5

[PROPOSED] Update .PHONY list
by Paul Eggert March 20, 2018

March 20, 2018

* Makefile (.PHONY): Update to match current Makefile contents. --- Makefile | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 979c0a2..3c0479a 100644 --- a/Makefile +++ b/Makefile @@ -964,14 +964,17 @@ zic.o: private.h tzfile.h version.h .KEEP_STATE: .PHONY: ALL INSTALL all -.PHONY: check check_character_set check_links +.PHONY: check check_character_set check_links check_name_lengths .PHONY: check_public check_sorted check_tables .PHONY: check_time_t_alternatives check_tzs check_web check_white_space .PHONY: check_zishrink -.PHONY: clean clean_misc force_tzs +.PHONY: clean clean_misc dummy.zd force_tzs .PHONY: install install_data maintainer-clean names .PHONY: posix_only posix_packrat posix_right .PHONY: public right_only right_posix signatures signatures_version -.PHONY: tarballs tarballs_version typecheck +.PHONY: tarballs tarballs_version +.PHONY: traditional_signatures traditional_signatures_version +.PHONY: traditional_tarballs traditional_tarballs_version +.PHONY: typecheck .PHONY: zonenames zones .PHONY: $(ZDS) -- 2.14.3

1 0

Re: [tz] [PATCH] * asia (Asia/Seoul) correct DST.
by REMI ACIEN March 19, 2018

March 19, 2018

For Zone Asia/Seoul LMT + 8 :26 :52 . Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10

2 1

Re: [tz] more on Palm Springs
by Paul Eggert March 18, 2018

March 18, 2018

Steve Allen wrote: > If inserting the Palm Springs story into tzdb is going to happen then > UCR has scanned copies of the local paper. Thanks for the URLs. Another city of two-timers, eh? Proposed patches attached.

1 0

[PATCH] * backzone: Chillicothe, city of two-timers.
by Paul Eggert March 18, 2018

March 18, 2018

--- backzone | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/backzone b/backzone index 71cb066..de247f0 100644 --- a/backzone +++ b/backzone @@ -274,6 +274,16 @@ Zone America/Cayman -5:25:32 - LMT 1890 # Georgetown -5:07:10 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST +# United States +# +# From Paul Eggert (2018-03-18): +# America/Chillicothe would be tricky, as it was a city of two-timers: +# "To prevent a constant mixup at Chillicothe, caused by the courthouse +# clock running on central time and the city running on 'daylight saving' +# time, a third hand was added to the dial of the courthouse clock." +# -- Ohio news in brief. The Cedarville Herald. 1920-05-21;43(21):1 (col. 5) +# https://digitalcommons.cedarville.edu/cedarville_herald/794 + # Canada Zone America/Coral_Harbour -5:32:40 - LMT 1884 -5:00 NT_YK E%sT 1946 -- 2.14.3

1 0

Keeping track of Japanese Era data
by Florian Weimer March 17, 2018

March 17, 2018

Would the tz project be interested in keeping track of the Japanese Era information? glibc currently stores it as part of its locale data, but I think this causes some issues (particularly with downstream builds). Thanks, Florian

4 3

Palestine summer time 2018
by Sharef Mustafa March 16, 2018

March 16, 2018

Hi, Palestine summer time will start on Mar 24th 2018 by advancing the clock by 60 minutes as per Palestinian cabinet decision published on the offical website, though the decree did not specify the exact time of the time shift., http://www.palestinecabinet.gov.ps/Website/AR/NDecrees/ViewFile.ashx?ID=e7a… this affects Asia/Gaza & Asia/Hebron time zones. BR Sharef Mustafa

2 1

Phone glitch leaves some Hobartians behind the times
by Gilmore Davidson March 16, 2018

March 16, 2018

http://www.abc.net.au/news/2018-03-16/time-glitch-leaves-some-hobart-reside… <http://www.abc.net.au/news/2018-03-16/time-glitch-leaves-some-hobart-reside…> “[National telecom provider] Telstra has apologised for a fault that caused thousands of Tasmanian customers to have the wrong time displayed on their phones. The issue affecting Android operating systems caused widespread confusion, with many people reporting being late to work after their phones were running an hour early."

3 2

Casey time zone change
by Steffen Thorsen March 14, 2018

March 14, 2018

Australian Antarctic Division informed us: With the conclusion of the Australian Antarctica Division’s aviation program for the 2017/18 season, please change your time for Casey station to *UTC +8* on Sunday 11th March (this change will take place on 11th March at 4am (UTC +11)). Best regards, Steffen Thorsen - timeanddate.com

3 3

Permanent DST in Florida: step 2 of 4 completed
by Arthur David Olson March 12, 2018

March 12, 2018

"The Florida Senate passed the Sunshine Protection Act on Tuesday, three weeks after the state’s House of Representatives, and sent it to Gov. Rick Scott..." https://www.nytimes.com/2018/03/08/us/daylight-saving-time-florida.html?smi… (I have hopes for a new CBS hit series, "DST: Miami.") (Less frivolously, discussions about using EDT, AST, or FST--and how to set tm_isdst--can begin in earnest.) @dashdashado

6 7

[PATCH] * tz-art.html: Add a Veep episode.
by Paul Eggert March 12, 2018

March 12, 2018

--- tz-art.html | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/tz-art.html b/tz-art.html index 480b9e1..9624d8c 100644 --- a/tz-art.html +++ b/tz-art.html @@ -81,19 +81,19 @@ doing so got a crook trying to be declared dead to emerge a bit too early from the titular enclosure. </li> <li> -The 1960s ITC television series <em>The Prisoner</em> included an episode -entitled "The Chimes of Big Ben" in which our protagonist tumbled to +"The Chimes of Big Ben", <em>The Prisoner</em>, episode 2, ITC, 1967-10-06. +Our protagonist tumbles to the fraudulent nature of a Poland-to-England escape upon hearing "Big Ben" chiming on Polish local time. </li> <li> -The series <em>Seinfeld</em> included an episode entitled "The Susie," first -broadcast 1997-02-13, in which Kramer decides that daylight saving time +"The Susie", <em>Seinfeld</em>, season 8, episode 15, NBC, 1997-02-13. +Kramer decides that daylight saving time isn't coming fast enough, so he sets his watch ahead an hour. </li> <li> -The "20 Hours in America" episode of <em>The West Wing</em>, -first aired 2002-09-25, contained a <a +"20 Hours in America", <em>The West Wing</em>, season 4, episodes 1–2, +2002-09-25, contained a <a href="https://www.youtube.com/watch?v=-J1NHzQ1sgc">scene</a> that saw White House staffers stranded in Indiana; they thought they had time to catch Air Force One but were done in by intra-Indiana local time changes. @@ -165,6 +165,11 @@ CBS, 2016-01-17. The applicability of a contract hinges on the time zone associated with a video timestamp. </li> +<li> +"Justice", <em>Veep</em>, season 6, episode 4, HBO, 2017-05-07. +Jonah's inability to understand DST ends up impressing a wealthy +backer who sets him up for a 2020 presidential run. +</li> </ul> <h2>Books, plays, and magazines</h2> <ul> -- 2.14.3

1 0

Regarding timezone upgrade from 2017c to 2018c
by Debananda Pal March 12, 2018

March 12, 2018

Hi, While upgrading to 2018c timezone, I found below changes : ./etc/localtime ./etc/localtime ==> Newly added ./etc/zoneinfo/localtime -> GMT ==> This entry is removed ./etc/zoneinfo/GMT ./etc/zoneinfo/GMT ==> Changed to ==> ./etc/zoneinfo/GMT link ./etc/localtime ./etc/zoneinfo/US/Pacific-New -> ../America/Los_Angeles ==> This entry is removed ./etc/zoneinfo/Africa/Sao_Tome -> ../Atlantic/St_Helena ==> Changed to ==> ./etc/zoneinfo/Africa/Sao_Tome ./etc/zoneinfo/Africa/Sao_Tome Please let me know, if the above changes are expected according to 2018c TZ database change. Regards, D Pal

3 9

Misspelling of Kyiv in the Time Zone Database
by Mykola Moroziuk March 5, 2018

March 5, 2018

Greetings. I noticed that name of the capital of Ukraine is misspelled. In the Time Zone Database it's written as "Kiev" which is wrong. This spelling is wrong since it's transliteration of russian variant of the city's name - "Киев". The right spelling of the city's name is "Kyiv", since in Ukrainian it's written as "Київ", and pronunciation of "Kyiv" is the closest to the "Київ". Please, consider changing the name of the city from "Kiev" to "Kyiv", Thanks. Respectfully, Mykola Moroziuk

2 1

[PROPOSED] * tz-link.html: Link to Google Time Zone Data.
by Paul Eggert March 5, 2018

March 5, 2018

--- tz-link.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tz-link.html b/tz-link.html index 0fc4bc6..f3ac4ed 100644 --- a/tz-link.html +++ b/tz-link.html @@ -182,6 +182,8 @@ data yourself. System-specific instructions for installing the latest <code><abbr>tz</abbr></code> data have also been published for <a href="https://www.ibm.com/developerworks/aix/library/au-aix-olson-time-zone/index…"><abbr>AIX</abbr></a>, <a +href="https://play.google.com/store/apps/details?id=com.google.android.timezone.d…">Android</a>, +<a href="http://userguide.icu-project.org/datetime/timezone"><abbr title="International Components for Unicode">ICU</abbr></a>, <a href="https://developer.ibm.com/javasdk/support/dst/jtzu/"><abbr>IBM</abbr></a> -- 2.7.4

1 0

[PROPOSED] * australasia: Mention Pearce 2017 for Queensland.
by Paul Eggert Feb. 27, 2018

Feb. 27, 2018

--- australasia | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/australasia b/australasia index c7c0ea7..32ad61e 100644 --- a/australasia +++ b/australasia @@ -1086,6 +1086,13 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # South Australian time even though it's located in Western Australia. # Queensland + +# From Paul Eggert (2018-02-26): +# I lack access to the following source for Queensland DST: +# Pearce C. History of daylight saving time in Queensland. +# Queensland Hist J. 2017 Aug;23(6):389-403 +# https://search.informit.com.au/documentSummary;dn=994682348436426;res=IELHSS + # From George Shepherd via Simon Woodhead via Robert Elz (1991-03-06): # # The state of QUEENSLAND.. [ Courtesy Qld. Dept Premier Econ&Trade Devel ] # # [ Dec 1990 ] -- 2.7.4

1 0

Converting cities to tz identifiers (tangent)
by John Hawkinson Feb. 26, 2018

Feb. 26, 2018

This is a bit of a rambling tangent, so sorry. I recently had to find tz zones for ~100 American cities, and the process did not go quite as smoothly as I had expected. I figured that a review of theory.html and tz-link.html would tell me the best way to do this, and it didn't really work out that way. The result was that I found myself just reading the "northamererica" file and knocking out the states that were unambiguous, and then checking the rest against timeanddate.com or time.is. It seems wrong that this appeared to be the easiest approach at this scale, so I wonder what others would suggest (with the benefit of hindsight). And then, in most cases, converting the zones via "backward" to the "US/Eastern" American political because doing so seemed more "stable." * I was expecting theory.html to give me a little more guidance on the "right" way to do this. As best as I can tell, the "right" (no pun intended) answer is that I should geolocate each city to longitude/latitude (using some unspecified resource, which seems fine), then use one of the datasets or tools at https://data.iana.org/time-zones/tz-link.html#boundaries to convert those locations to zones. This seemed a bit much. * I was also a little surprised to not find someone with a handy list of United States states and territory mappings to tz identifiers (for those cases where the state/territory/district uniquely mapped to a tzid). Other than the comments in "northamerica" (which are not quite as structured as one might like, but are pretty good). * Then I was faced with the question of what the most stable identifier to use was. For instance, take Boston, Massachusetts. I could record it as America/New_York, or as US/Eastern. For instance, at some point in the future, either Boston or New York might exit the Eastern time zone. Cases: Case 1: If that New York exited and Boston didn't, picking US/Eastern would clearly be the more stable choice. Case 2: And if Boston exited and New York didn't, it wouldn't matter which I chose, I'd have to update my mapping when Boston moved. Case 3: If New York and Boston both exited US/Eastern and went the same way, then America/New_York would be the better choice. Case 4: If New York and Boston both exited US/Eastern and did different things, it's not clear which is the better choice, but similar to Case 2. Lather rinse repeat for 50 states + some territories and DC. My conclusion was that in general, for most locations, the US/* ("backward") form seemed the better choice. (Both Massachusetts and Florida seem to have current proposals to depart US/Eastern and America/New_York.) * So, I'm curious if this anecdote triggers any reactions. Did I miss an obvious way to address this more simply? Is it horrible to have made use of third party websites that lack any sort of auditable authority but are probably correct anyhow. Is this just not a problem that people have to solve with any frequency? Does someone (Paul?) want to convince me that it's Wrong to use the "backward" zones, for the narrow (but common) case of United States of America cities? Thanks for any thoughts. --jhawk(a)mit.edu John Hawkinson

17 32

Need to update Kansas City, MO
by Kevin DeCapite Feb. 25, 2018

Feb. 25, 2018

I would like to propose a change to the database to account for Kansas City, Missouri, USA as having not observed DST between 1946 - 1965. Please see the source book referenced in the link (page 87 in the actual printed pages, standard PDF is the best way to view it): https://archive.org/details/time-changes-in-usa-1966 <https://archive.org/details/time-changes-in-usa-1966> I can also confirm the accuracy of at least this piece of information through testimony. What are the procedures for formally proposing, reviewing & accepting/rejecting such changes? Thank you. --- Kevin DeCapite kevin(a)decapite.net 562.355.8222

2 1

AP & WFLA-TV: Florida House OKs bill asking to skip Daylight Saving Time
by Vance, Frank Feb. 24, 2018

Feb. 24, 2018

http://wfla.com/2018/02/14/florida-house-oks-bill-asking-to-skip-daylight-s… "The [Florida] House voted 103-11 to approve the bill to ask Congress to let Florida remain in Daylight Saving Time all year, meaning while the rest of the Eastern United States sets their clocks back in the fall, Florida wouldn't." Regards, F

7 8

SGT abbreviation is missing from the IANA tz database
by Lu, Can Feb. 21, 2018

Feb. 21, 2018

Hi Paul, Hope you're well. By way of introduction, this is Can, working as a software developer in BAML. We noticed that Asia/Singapore had its SGT abbreviation dropped in tzdb 2017, and the reason being is that the zone abbreviation doesn't correspond to any real-world usage. But it's actually not entirely true, SGT is very commonly used in Singapore and it's also a standard abbreviation for Singapore time. Please refer to: https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations and https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations Wondering if it's possible to add SGT back to IANA db as I believe this change will cause breaks to other libraries rely on it. (We're using pytz for python development). I am happy to discuss and appreciate any thoughts you may have on it. Thanks, Can ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.

4 4

[PROPOSED] Parallelize the main part of 'make to2050new.tzs'
by Paul Eggert Feb. 21, 2018

Feb. 21, 2018

This improves real-time performance of 'make -j4 to2050new.tzs' by a factor of about 3.5 (from 120 s to 34 s) on my old 4-core desktop, which runs Fedora 27 x86-64 atop an AMD Phenom II X4 910e. * Makefile (ZDS): New macro. ($(ZDS)): New rule. All targets are phony. ($(TZS_NEW)): Use it in a submake that is parallelized by GNU make -j. (check_links): Depend on tzdata.zi, fixing a dependency bug. * NEWS: Mention this. --- Makefile | 29 ++++++++++++++++++++--------- NEWS | 4 ++++ 2 files changed, 24 insertions(+), 9 deletions(-) diff --git a/Makefile b/Makefile index fc15c3e..835f34b 100644 --- a/Makefile +++ b/Makefile @@ -640,19 +640,29 @@ posix_packrat: zones: $(REDO) +# dummy.zd is not a real file; it is mentioned here only so that the +# top-level 'make' does not have a syntax error. +ZDS = dummy.zd +# Rule used only by submakes invoked by the $(TZS_NEW) rule. +# It is separate so that GNU 'make -j' can run instances in parallel. +$(ZDS): zdump + ./zdump -i -c $(TZS_YEAR) '$(wd)/'$$(expr $@ : '$.*$.zd') >$@ + $(TZS_NEW): tzdata.zi zdump zic - mkdir -p tzs.dir + rm -fr tzs.dir + mkdir tzs.dir $(zic) -d tzs.dir tzdata.zi $(AWK) '/^L/{print "Link\t" $$2 "\t" $$3}' \ tzdata.zi | LC_ALL=C sort >$@.out wd=`pwd` && \ - zones=`$(AWK) -v wd="$$wd" \ - '/^Z/{print wd "/tzs.dir/" $$2}' tzdata.zi \ - | LC_ALL=C sort` && \ - ./zdump -i -c $(TZS_YEAR) $$zones >>$@.out - sed 's,^TZ=".*tzs\.dir/,TZ=",' $@.out >$@.sed.out - rm -fr tzs.dir $@.out - mv $@.sed.out $@ + set x `$(AWK) '/^Z/{print "tzs.dir/" $$2 ".zd"}' tzdata.zi \ + | LC_ALL=C sort -t . -k 2,2` && \ + shift && \ + ZDS=$$* && \ + $(MAKE) wd="$$wd" TZS_YEAR=$(TZS_YEAR) ZDS="$$ZDS" $$ZDS && \ + sed 's,^TZ=".*tzs\.dir/,TZ=",' $$ZDS >>$@.out + rm -fr tzs.dir + mv $@.out $@ # If $(TZS) does not already exist (e.g., old-format tarballs), create it. # If it exists but 'make check_tzs' fails, a maintainer should inspect the @@ -730,7 +740,7 @@ check_sorted: backward backzone iso3166.tab zone.tab zone1970.tab $(AWK) '/^[^#]/ $(CHECK_CC_LIST)' zone1970.tab | \ LC_ALL=C sort -cu -check_links: checklinks.awk $(TDATA_TO_CHECK) +check_links: checklinks.awk $(TDATA_TO_CHECK) tzdata.zi $(AWK) -f checklinks.awk $(TDATA_TO_CHECK) $(AWK) -f checklinks.awk tzdata.zi @@ -964,3 +974,4 @@ zic.o: private.h tzfile.h version.h .PHONY: public right_only right_posix signatures signatures_version .PHONY: tarballs tarballs_version typecheck .PHONY: zonenames zones +.PHONY: $(ZDS) diff --git a/NEWS b/NEWS index 3d18e89..1d2827e 100644 --- a/NEWS +++ b/NEWS @@ -79,6 +79,10 @@ Unreleased, experimental changes already can use vanguard.zi; in this respect, current tzcode is bleeding-edge. + The Makefile should now be safe for parallelized builds, and 'make + -j to2050new.tzs' is now much faster on a multiprocoessor host + with GNU Make. + When built with -DSUPPRESS_TZDIR, the tzcode library no longer prepends TZDIR/ to file names that do not begin with '/'. This is not recommended for general use, due to its security implications. -- 2.14.3

1 0

timezone history of Uruguay
by Jeremie Bonjour Feb. 20, 2018

Feb. 20, 2018

I submitted this information because it is not correct on the iana. org website. Greetings! Source: http://www.armada.mil.uy/ContenidosPDFs/sohma/web/almanaque/almanaque_2018.… Army Force of Uruguay http://www.armada.mil.uy .:Armada Nacional - Marina de Uruguay:.<http://www.armada.mil.uy/> www.armada.mil.uy Embarcación demorada La Armada Nacional, a través del Centro Coordinador de Búsqueda y Rescate en el Mar (MRCC), está realizando la búsqueda de un pesquero ... Almanac 2018, page 38 [cid:4e5339c0-4b51-4184-b33a-ad63059bec3a] Saludos. Jeremie Bonjour (+598) 093 81 21 71

4 9

Sol 5000 for Opportunity
by Tim Parenti Feb. 18, 2018

Feb. 18, 2018

Today, 16 February 2018, at 01:26:20.092 UTC, it is 01:01:06 Coordinated Mars Time on Mars Sol Date 51235, which corresponds to midnight HLST (hybrid local solar time) at the beginning of mission sol 5000 for the Opportunity (MER-B) rover at its mission reference longitude. The sol will last, of course, for 24 hours 39 minutes 35.244 seconds, ending on 17 February 2018 at 02:05:55.336 UTC. Curiosity will observe its mission sol 2000 next month, reckoned in mean solar time at its landing site, from 2018-03-22 13:24:49.020 UTC to 2018-03-23 14:04:24.264 UTC. -- Tim Parenti

5 7

apply Portuguese decree of 1911-05-30
by Michael H Deckers Feb. 17, 2018

Feb. 17, 2018

The decree [http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf] of 1911-05-30, mentioned for Europe/Lisbon prescribes time zone time scales for continental Portugal, Madeira, Azores, Cabo Verde, Guinea-Bissau, São Tomé, Angola, and Moçambique. It is currently not applied to all of these locations, and its article 5 is not correctly applied: " Art. 5.º Estas disposições entrarão em vigor no instante em que, segundo o artigo 2.º, começar o dia civil 1 de [j]aneiro de 1912, devendo então todos os relogios ser adeantados ou atrasados convenientemente, conforme as alineas seguintes:"... -- These dispositions shall enter into force at the instant at which, -- according to the 2nd article, the civil day January 1, 1912 begins, -- all clocks therefore having to be advanced or set back correspondingly, -- conforming with the following sections:.... (Article 2 specifies the various time zone time scales GMT + 00 h, GMT - 02 h, etc to be used in Portugal from 1912-01-01 onward.) The following proposals contain the necessary corrections. I have also tried to indicate exactly which data are implied by the source. I see this as a small step to make the tzdb data traceable to its sources, and thus to clarify the uncertainty of tzdb data (when they are estimated, or derived from less reliable sources). The format of these indications can certainly be improved. +# [pt 1911] decree https://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf of 1911-05-30 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada - -1:54:32 - HMT 1912-01-01 # Horta Mean Time +# [pt 1911] specifies UNTIL date, time & new GMTOFF: + -1:54:32 - HMT 1912-01-01 02:00u # Horta Mean Time -2:00 Port -02/-01 1942 Apr 25 22:00s # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal - -1:07:36 - FMT 1912-01-01 # Funchal Mean Time +# [pt 1911] specifies UNTIL date, time & new GMTOFF: + -1:07:36 - FMT 1912-01-01 01:00u # Funchal Mean Time -1:00 Port -01/+00 1942 Apr 25 22:00s # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Lisbon -0:36:45 - LMT 1884 - -0:36:45 - LMT 1912 Jan 1 # Lisbon Mean Time +# [pt 1911] specifies UNTIL date, time & unrounded old (-00:36:44.68) and new GMTOFF: + -0:36:45 - LMT 1912 Jan 1 00:00u # Lisbon Mean Time 0:00 Port WE%sT 1966 Apr 3 2:00 The correction for Europe/Lisbon is an example where I think that Paul Eggert's proposal for GMTOFF values with fractional seconds would be helpful. [pt 1911] specifies Cabo Verde to use UT - 02 h since 1912-01-01 02:00Z. Currently, tzdb has a switch to UT - 02 h in 1907 without source (Shanks by default). This switch would precede the one in [pt 1911] which appears to be unlikely (admittedly, we know from Guernsey on 1913-06-18 that such conclusions may be wrong). # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Atlantic/Cape_Verde -1:34:04 - LMT 1907 # Praia +# [pt 1911] specifies UNTIL date, time & new GMTOFF: +# Ignore [Shanks] specifying UNTIL year 1907, no date, no time. +Zone Atlantic/Cape_Verde -1:34:04 - LMT 1912-01-01 02:00u # Praia -2:00 - -02 1942 Sep # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Africa/Bissau -1:02:20 - LMT 1912 Jan 1 +# [pt 1911] specifies UNTIL date, time & new GMTOFF: +Zone Africa/Bissau -1:02:20 - LMT 1912 Jan 1 01:00u # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Sao_Tome 0:26:56 - LMT 1884 - -0:36:32 - LMT 1912 # Lisbon Mean Time +# [pt 1911] specifies UNTIL date, time & new GMTOFF: + -0:36:32 - LMT 1912-01-01 00:00u # Lisbon Mean Time 0:00 - GMT 2018 Jan 1 01:00 Note that Lisbon Mean Time as in [pt 1911] and in [Milne 1899] differs from the GMTOFF given here for it (from Shanks?). # Zone NAME GMTOFF RULES FORMAT [UNTIL] -Zone Asia/Macau 7:34:20 - LMT 1912 Jan 1 +# [pt 1911] specifies UNTIL date, time & new GMTOFF: +Zone Asia/Macau 7:34:20 - LMT 1911-12-31 16:00u 8:00 Macau C%sT In backzone: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Luanda 0:52:56 - LMT 1892 - 0:52:04 - LMT 1912 Jan 1 +# [pt 1911] specifies UNTIL date, time & new GMTOFF: + 0:52:04 - LMT 1911-12-31 23:00u 1:00 - WAT The decree specifies that Goa (Panaji) and Timor (Aisa/Dili) should keep the time scale of the adjacent colonies. Michael Deckers.

2 1

[PATCH 1/2] Improve use of non-ASCII symbols in commentary
by Paul Eggert Feb. 16, 2018

Feb. 16, 2018

From: Paul Eggert <eggert(a)Penguin.CS.UCLA.EDU> Go back to using °, ±, etc. in commentary. This was prompted by my recent minor cleanup change of “34°” to “34 degrees” for Uruguay commentary. As it happens, this cleanup wasn't really needed for XEmacs, and it's annoying to have to use longwinded workarounds for common symbols. * Makefile (UNUSUAL_OK_CHARSET): New macro. (OK_CHAR): Use it. (check_character_set): Check Makefile seperately, since its UNUSUAL_OK_CHARSET can be a non-SAFE_LINE now. * NEWS: Mention this. --- Makefile | 22 +++++++++++++++------- NEWS | 6 +++++- asia | 11 +++++------ australasia | 4 ++-- backzone | 6 +++--- europe | 14 +++++++------- northamerica | 5 ++--- southamerica | 2 +- zone1970.tab | 2 +- 9 files changed, 41 insertions(+), 31 deletions(-) diff --git a/Makefile b/Makefile index 47acbbd..fc15c3e 100644 --- a/Makefile +++ b/Makefile @@ -408,13 +408,19 @@ SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' +# Non-ASCII non-letters that OK_CHAR allows, as these characters are +# useful in commentary. XEmacs 21.5.34 displays them correctly, +# presumably because they are Latin-1. +UNUSUAL_OK_CHARSET= °±½¾× + # OK_CHAR matches any character allowed in the distributed files. -# This is the same as SAFE_CHAR, except that multibyte letters are -# also allowed so that commentary can contain people's names and quote -# non-English sources. For non-letters the sources are limited to -# ASCII renderings for the convenience of maintainers whose text editors -# mishandle UTF-8 by default (e.g., XEmacs 21.4.22). -OK_CHAR= '[][:alpha:]'$(SAFE_CHARSET)'-]' +# This is the same as SAFE_CHAR, except that UNUSUAL_OK_CHARSET and +# multibyte letters are also allowed so that commentary can contain a +# few safe symbols and people's names and can quote non-English sources. +# Other non-letters are limited to ASCII renderings for the +# convenience of maintainers using XEmacs 21.5.34, which by default +# mishandles Unicode characters U+0100 and greater. +OK_CHAR= '[][:alpha:]$(UNUSUAL_OK_CHARSET)'$(SAFE_CHARSET)'-]' # SAFE_LINE matches a line of safe characters. # SAFE_SHARP_LINE is similar, except any OK character can follow '#'; @@ -689,8 +695,10 @@ check_character_set: $(ENCHILADA) sharp='#' && \ ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) \ - CONTRIBUTING LICENSE Makefile README \ + CONTRIBUTING LICENSE README \ version tzdata.zi && \ + ! grep -Env $(SAFE_LINE)'|^UNUSUAL_OK_CHARSET='$(OK_CHAR)'*$$' \ + Makefile && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA_TO_CHECK) backzone \ leapseconds yearistype.sh zone.tab && \ ! grep -Env $(OK_LINE) $(ENCHILADA); \ diff --git a/NEWS b/NEWS index b83cce9..1e2cfdf 100644 --- a/NEWS +++ b/NEWS @@ -108,6 +108,10 @@ Unreleased, experimental changes with links to many relevant legal documents. (Thanks to Tim Parenti.) + Commentary now uses some non-ASCII characters with Unicode value + less than U+0100, as they can be useful and should work even with + older editors such as XEmacs. + Release 2018c - 2018-01-22 23:00:44 -0800 @@ -1009,7 +1013,7 @@ Release 2016b - 2016-03-12 17:30:14 -0800 Comments in zone tables have been improved. (Thanks to J William Piggott.) tzselect again limits its menu comments so that menus fit on a - 24x80 alphanumeric display. + 24×80 alphanumeric display. A new web page tz-how-to.html. (Thanks to Bill Seymour.) diff --git a/asia b/asia index 63d2fb0..5c2fc50 100644 --- a/asia +++ b/asia @@ -1478,8 +1478,7 @@ Rule Japan 1950 1951 - May Sat>=1 24:00 1:00 D # From Hideyuki Suzuki (1998-11-09): # 'Tokyo' usually stands for the former location of Tokyo Astronomical -# Observatory: 139 degrees 44' 40.90" E (9h 18m 58.727s), -# 35 degrees 39' 16.0" N. +# Observatory: 139° 44' 40.90" E (9h 18m 58.727s), 35° 39' 16.0" N. # This data is from 'Rika Nenpyou (Chronological Scientific Tables) 1996' # edited by National Astronomical Observatory of Japan.... # JST (Japan Standard Time) has been used since 1888-01-01 00:00 (JST). @@ -1487,10 +1486,10 @@ Rule Japan 1950 1951 - May Sat>=1 24:00 1:00 D # From Hideyuki Suzuki (1998-11-16): # The ordinance No. 51 (1886) established "standard time" in Japan, -# which stands for the time on 135 degrees E. +# which stands for the time on 135° E. # In the ordinance No. 167 (1895), "standard time" was renamed to "central # standard time". And the same ordinance also established "western standard -# time", which stands for the time on 120 degrees E.... But "western standard +# time", which stands for the time on 120° E.... But "western standard # time" was abolished in the ordinance No. 529 (1937). In the ordinance No. # 167, there is no mention regarding for what place western standard time is # standard.... @@ -3097,9 +3096,9 @@ Zone Asia/Tashkent 4:37:11 - LMT 1924 May 2 # and is the basis for the information below. # # The 1906 transition was effective July 1 and standardized Indochina to -# Phù Liễn Observatory, legally 104 deg. 17'17" east of Paris. +# Phù Liễn Observatory, legally 104° 17' 17" east of Paris. # It's unclear whether this meant legal Paris Mean Time (00:09:21) or -# the Paris Meridian (2 deg. 20'14.03" E); the former yields 07:06:30.1333... +# the Paris Meridian (2° 20' 14.03" E); the former yields 07:06:30.1333... # and the latter 07:06:29.333... so either way it rounds to 07:06:30, # which is used below even though the modern-day Phù Liễn Observatory # is closer to 07:06:31. Abbreviate Phù Liễn Mean Time as PLMT. diff --git a/australasia b/australasia index 4f96458..c7c0ea7 100644 --- a/australasia +++ b/australasia @@ -1610,7 +1610,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # From Howie Phelps (1999-11-10), who talked to a Pitcairner via shortwave: # Betty Christian told me yesterday that their local time is the same as -# Pacific Standard Time. They used to be 1/2 hour different from us here in +# Pacific Standard Time. They used to be ½ hour different from us here in # Sacramento but it was changed a couple of years ago. @@ -1649,7 +1649,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # 12 hours and 20 minutes ahead of GMT. When New Zealand adjusted its # standard time in 1940s, Tonga had the choice of subtracting from its # local time to come on the same standard time as New Zealand or of -# advancing its time to maintain the differential of 13 degrees +# advancing its time to maintain the differential of 13° # (approximately 50 minutes ahead of New Zealand time). # # Because His Majesty King Tāufaʻāhau Tupou IV, then Crown Prince diff --git a/backzone b/backzone index cc724aa..2071110 100644 --- a/backzone +++ b/backzone @@ -409,7 +409,7 @@ Zone Asia/Bahrain 3:22:20 - LMT 1920 # Manamah # From Paul Eggert (2014-08-21): # In tomorrow's The Hindu, Nitya Menon reports that India had two civil time # zones starting in 1884, one in Bombay and one in Calcutta, and that railways -# used a third time zone based on Madras time (80 deg. 18'30" E). Also, +# used a third time zone based on Madras time (80° 18' 30" E). Also, # in 1881 Bombay briefly switched to Madras time, but switched back. See: # http://www.thehindu.com/news/cities/chennai/madras-375-when-madras-clocked-… #Zone Asia/Chennai [not enough info to complete] @@ -532,7 +532,7 @@ Zone Europe/Belfast -0:23:40 - LMT 1880 Aug 2 # Data from Joseph S. Myers # https://mm.icann.org/pipermail/tz/2013-September/019883.html # References to be added -# LMT is for Town Church, St. Peter Port, 49 degrees 27'17"N 2 degrees 32'10"W +# LMT is for Town Church, St. Peter Port, 49° 27' 17" N, 2° 32' 10" W. Zone Europe/Guernsey -0:10:09 - LMT 1913 Jun 18 0:00 GB-Eire %s 1940 Jul 2 1:00 C-Eur CE%sT 1945 May 8 @@ -566,7 +566,7 @@ Zone Europe/Isle_of_Man -0:17:55 - LMT 1883 Mar 30 0:00s # Data from Joseph S. Myers # https://mm.icann.org/pipermail/tz/2013-September/019883.html # References to be added -# LMT is for Parish Church, St. Helier, 49 degrees 11'0.57"N 2 degrees 6'24.33"W +# LMT is for Parish Church, St. Helier, 49° 11' 0.57" N, 2° 6' 24.33" W. Zone Europe/Jersey -0:08:26 - LMT 1898 Jun 11 16:00u 0:00 GB-Eire %s 1940 Jul 2 1:00 C-Eur CE%sT 1945 May 8 diff --git a/europe b/europe index 8aab26e..6bbb49d 100644 --- a/europe +++ b/europe @@ -117,8 +117,8 @@ # along the towpath within a few yards of it.' # # I have a one inch to one mile map of London and my estimate of the stone's -# position is 51 degrees 28' 30" N, 0 degrees 18' 45" W. The longitude should -# be within about +-2". The Ordnance Survey grid reference is TQ172761. +# position is 51° 28' 30" N, 0° 18' 45" W. The longitude should +# be within about ±2". The Ordnance Survey grid reference is TQ172761. # # [This yields GMTOFF = -0:01:15 for London LMT in the 18th century.] @@ -158,7 +158,7 @@ # after-hours daylight in which to pursue his research. # In 1895 he presented a paper to the Wellington Philosophical Society # that proposed a two-hour daylight-saving shift. See: -# Hudson GV. On seasonal time-adjustment in countries south of lat. 30 deg. +# Hudson GV. On seasonal time-adjustment in countries south of lat. 30°. # Transactions and Proceedings of the New Zealand Institute. 1895;28:734 # http://rsnz.natlib.govt.nz/volume/rsnz_28/rsnz_28_00_006110.html # Although some interest was expressed in New Zealand, his proposal @@ -2594,13 +2594,13 @@ Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr # From Vladimir Karpinsky (2014-07-08): # LMT in Moscow (before Jul 3, 1916) is 2:30:17, that was defined by Moscow -# Observatory (coordinates: 55 deg. 45'29.70", 37 deg. 34'05.30").... +# Observatory (coordinates: 55° 45' 29.70", 37° 34' 05.30").... # LMT in Moscow since Jul 3, 1916 is 2:31:01 as a result of new standard. # (The info is from the book by Byalokoz ... p. 18.) # The time in St. Petersburg as capital of Russia was defined by # Pulkov observatory, near St. Petersburg. In 1916 LMT Moscow # was synchronized with LMT St. Petersburg (+30 minutes), (Pulkov observatory -# coordinates: 59 deg. 46'18.70", 30 deg. 19'40.70") so 30 deg. 19'40.70" > +# coordinates: 59° 46' 18.70", 30° 19' 40.70") so 30° 19' 40.70" > # 2h01m18.7s = 2:01:19. LMT Moscow = LMT St.Petersburg + 30m 2:01:19 + 0:30 = # 2:31:19 ... # @@ -3429,7 +3429,7 @@ Zone Atlantic/Canary -1:01:36 - LMT 1922 Mar # Las Palmas de Gran C. # three degrees, or twelve minutes of time, to the west of the # meridian of the Observatory of Stockholm". The law is dated 1878-05-31. # -# The observatory at that time had the meridian 18 degrees 03' 30" +# The observatory at that time had the meridian 18° 03' 30" # eastern longitude = 01:12:14 in time. Less 12 minutes gives the # national standard time as 01:00:14 ahead of GMT.... # @@ -3533,7 +3533,7 @@ Zone Europe/Stockholm 1:12:12 - LMT 1879 Jan 1 # From Alois Treindl (2013-09-11): # The Federal regulations say # https://www.admin.ch/opc/de/classified-compilation/20071096/index.html -# ... the meridian for Bern mean time ... is 7 degrees 26' 22.50". +# ... the meridian for Bern mean time ... is 7° 26' 22.50". # Expressed in time, it is 0h29m45.5s. # From Pierre-Yves Berger (2013-09-11): diff --git a/northamerica b/northamerica index dabca97..f4e38f8 100644 --- a/northamerica +++ b/northamerica @@ -424,8 +424,7 @@ Zone America/North_Dakota/New_Salem -6:45:39 - LMT 1883 Nov 18 12:14:21 # ...according to the Census Bureau, the largest city is Beulah (although # it's commonly referred to as Beulah-Hazen, with Hazen being the next # largest city in Mercer County). Google Maps places Beulah's city hall -# at 47 degrees 15' 51" N, 101 degrees 46' 40" W, which yields an offset -# of 6h47'07". +# at 47° 15' 51" N, 101° 46' 40" W, which yields an offset of 6h47'07". Zone America/North_Dakota/Beulah -6:47:07 - LMT 1883 Nov 18 12:12:53 -7:00 US M%sT 2010 Nov 7 2:00 @@ -458,7 +457,7 @@ Zone America/Denver -6:59:56 - LMT 1883 Nov 18 12:00:04 # California, northern Idaho (Benewah, Bonner, Boundary, Clearwater, # Kootenai, Latah, Lewis, Nez Perce, and Shoshone counties, Idaho county # north of the Salmon River, and the towns of Burgdorf and Warren), -# Nevada (except West Wendover), Oregon (except the northern 3/4 of +# Nevada (except West Wendover), Oregon (except the northern ¾ of # Malheur county), and Washington # From Paul Eggert (2016-08-20): diff --git a/southamerica b/southamerica index d97343e..c6c461c 100644 --- a/southamerica +++ b/southamerica @@ -1694,7 +1694,7 @@ Link America/Port_of_Spain America/Tortola # Virgin Islands (UK) # auspices of the National Institute for the Prediction of Time. It is unclear # exactly what offset was used during this period, though Ley No. 7200 of # 1920-04-23 used the Observatory of the National Meteorological Institute in -# Montevideo (S 34 deg. 54'33", W 056 deg. 12'45") as its reference meridian, +# Montevideo (34° 54' 33" S, 56° 12' 45" W) as its reference meridian, # retarding legal time by 15 minutes 9 seconds from 1920-04-30 24:00, # resulting in UT-04. Assume the corresponding LMT of UT-03:44:51 (given on # page 725 of the Proceedings of the Second Pan-American Scientific Congress, diff --git a/zone1970.tab b/zone1970.tab index a3b6b04..2d90ed7 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -12,7 +12,7 @@ # of ISO 3166 2-character country codes. See the file 'iso3166.tab'. # 2. Latitude and longitude of the zone's principal location # in ISO 6709 sign-degrees-minutes-seconds format, -# either +-DDMM+-DDDMM or +-DDMMSS+-DDDMMSS, +# either ±DDMM±DDDMM or ±DDMMSS±DDDMMSS, # first latitude (+ is north), then longitude (+ is east). # 3. Zone name used in value of TZ environment variable. # Please see the theory.html file for how zone names are chosen. -- 2.14.3

2 3

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

Reason for removal of several TZ
by Thomas M Steenholdt Jan. 23, 2018

Jan. 23, 2018

Hi guys, Almost a year ago, commit 2999bb5bee719acbba8b9dd50fb9fb00c7788623 removed several TZ abbreviations and I'm trying to understand this. For my own use, what I'm after is WGT/WGST which are now "simply -03". WGT/WGST has been in tzdata for a long time, so the removal causes certain things to go belly up. The change was only implemented in Ubuntu recently, which is why this only turned into a problem for me now. WGT/WGST seems to be a widely accepted abbreviation for the West Greenland Time zone. So can someone explain to me the reason behind the removal and what would needed to get it re-implemented? Thanks. /Thomas

40 174

Irish Standard Time vs Irish Summer Time
by Neil Fuller Jan. 22, 2018

Jan. 22, 2018

Just to weigh in from an Android OS perspective: the Europe/Dublin DST convention change is also problematic for the Android platform. Most of what I would want to say has been said. Like many, I missed the discussion in December about this change and I'm not sure I would have grasped the full impact if I had. I monitor the announcements list so it would have been most useful to me if this change had been flagged ahead of time there. I started looking at 2018a when I saw discussion internally to Google and I was surprised I hadn't seen an official announcement. It might help to understand the impact of this change and the indirect influence and interactions that the tzdata has in Android so I've included some information below on my ongoing assessment as an FYI. The NITZ standard[1] is probably the worst interaction I've seen so far. In the meantime Android will probably have to take the same approach that ICU has and patch the IANA data, or wait for 2018c to hopefully reverse the convention back to what it was before. As always, thanks to all of you for keeping the world turning! Neil. ------------- The latest Android code is downstream from both OpenJDK and ICU, with some of it's own time zone code on the side. There is a custom implementation of classes like java.util.TimeZone, but also code for time zone detection used in smartphone devices. Android will be exposed to any problems that the ICU/OpenJDK maintainers mentioned, plus any in other OS libraries used that I haven't looked at yet. Android uses tzdata in some places for transition calculations, but refers to ICU for things like names. There may be other interactions. If the tzdata had one interpretation, and ICU had another, Android's formatting code might return (for example) Irish Standard Time in Winter. I found a long-standing bug in the Android java.util.TimeZone code that forces the DST adjustment to always be >= 0 and another elsewhere that (obviously incorrectly) assumes DST always means +1 hour. The time zone detection code on Android can use the time zone offset data it has available on device and compare it against information sent by the carrier via NITZ[1] to see if it can identify the user's time zone. The NITZ documentation says: "When the LTZ is compensated for DST (summertime), the serving PLMN shall provide a DST parameter to indicate this. The adjustment for DST can be +1h or +2h." I'm looking into whether carriers / networks in Ireland have made the same interpretation as the new IANA data. I suspect their hands are tied by the NITZ standard which would probably prevent them passing a negative number. There's probably a feedback loop here between the NITZ standard, what carriers will send and what devices can accept that might take a while to stabilize on any new convention, if it happens at all. >From a support perspective, Android has three cohorts to deal with: 1) Devices running older versions of Android for which OEMs are still providing over-the-air (OTA) system image updates. These can potentially take code patches to correct issues. 2) Devices running older versions of Android that have the ability to receive time zone rules data updates but not code. 3) Latest code under development for future Android releases. If the Europe/Dublin change "sticks" in tzdata, the likely course for supporting existing devices would be to patch the Android tzdata and pretend the Europe/Dublin shift hasn't happened. Future devices could potentially support negative DST adjustments if all the problems are caught in advance. [1] https://en.wikipedia.org/wiki/NITZ , see reference 1 for the standard I quoted -- Google UK Limited Registered Office: 6 Pancras Square, London, N1C 4AG Registered in England Number: 3977902

4 4

Changing times
by Arthur David Olson Jan. 22, 2018

Jan. 22, 2018

In days of old, there was only one consumer of the time zone data files: the time zone compiler that's part of the IANA package. Today there are multiple consumers. My sense: that multiplication predominates over any change in maintenance approach as a complicating factor. @dashdashado

1 0

The Japanese time zone rule is wrong.
by 二階隆幸 Jan. 22, 2018

Jan. 22, 2018

Hello, I'm Takayuki Nikai. I will report mistakes in Japanese time zone rules. Under Japanese law the daylight savings time boundary is written as 0:00, but tzdata is defined as 2:00. Also, the end of daylight saving time is Sunday, not Saturday. The source of information is Japanese law. http://www.shugiin.go.jp/internet/itdb_housei.nsf/html/houritsu/00219480428… http://www.shugiin.go.jp/internet/itdb_housei.nsf/html/houritsu/00719500331… > 四月の第一土曜日の午後十二時から九月の第二土曜日の翌日の午前零時までの間 > 第一条及び第二条第一項中「四月」を「五月」に改める。 In summary, it is written as follows. From 24:00 on the first Saturday in May, Until 0:00 on the day after the second Saturday in September. However, in Time Zone Database (2018a (Released 2018-01-12) which is currently distributed, it is starting from 2:00 as follows and it is wrong. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER / S Rule Japan 1948 only - May Sun>=1 2:00 1:00 D Rule Japan 1948 1951 - Sep Sat>=8 2:00 0 S Rule Japan 1949 only - Apr Sun>=1 2:00 1:00 D Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D I think that it will be correct as follows. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER / S Rule Japan 1948 only - May Sun>=1 0:00 1:00 D Rule Japan 1948 1951 - Sep Sun>=8 0:00 0 S Rule Japan 1949 only - Apr Sun>=1 0:00 1:00 D Rule Japan 1950 1951 - May Sun>=1 0:00 1:00 D An error will occur in past date time analysis. Please consider modification. -- +--------------------------------------------------------+ HealthCare Relations Co., Ltd. 二階隆幸 Nikai Takayuki 〒101-0054 東京都千代田区神田錦町3-13−7 名古路ビル本館1F TEL 042-485-7130 +--------------------------------------------------------+

2 2

tzdb-2018b does not work after make clean
by 大山俊成 Jan. 22, 2018

Jan. 22, 2018

Hello, I'm Ohyama. I downloaded tzdb-2018b.tar.lz and did as followings make TOPDIR=$HOME/tzdir install $HOME/tzdir/usr/bin/zdump -v America/Los_Angeles it works good ! But once I do clean by make clean And again make TOPDIR=$HOME/tzdir install $HOME/tzdir/usr/bin/zdump -v America/Los_Angeles it does not works.(error message "America/Los_Angeles: No such file or directory") Something wrong with me?

2 4

cppcheck in-efficiencies
by Khamit Ardashev Jan. 21, 2018

Jan. 21, 2018

I use cppcheck to scan my code, and it found these in-efficiencies, Could somebody fix them ? date/tz.cpp:755: performance: Variable 'u' is assigned in constructor body. Consider performing initialization in initialization list. date/date.h:7218: performance: Function parameter 'format' should be passed by reference. date/tz.cpp:220: performance: Function parameter 'path' should be passed by reference. date/tz.cpp:2417: performance: Function parameter 'format' should be passed by reference. Khamit Ardashev Flextrade Systems

2 1

The Y2038 problem is 20 years away
by Tim Parenti Jan. 19, 2018

Jan. 19, 2018

It is now 03:14 UTC on 19 January 2018. Twenty years from now, POSIX and POSIX-based timestamps, which have more-or-less been counting seconds since 1970, will reach 2^31 and thus overflow signed 32-bit integers. Since all sorts of forward-looking date arithmetic abounds, it is inevitable that there are still active applications that will mishandle this. Twenty years out is an interesting point when more of those seams might start to show, and left unpatched, that would only increase as we approach 2038. It's much like Y2K, but in binary… and with seconds. So keep your eyes peeled in the near future for anything suddenly thinking it'll somehow be December 1901 in the slightly-more-distant future. You have some insight into just why that'll be happening. -- Tim Parenti

6 7

Re: [tz] Irish Standard Time vs Irish Summer Time
by Patsy Franklin Jan. 19, 2018

Jan. 19, 2018

Hi, Will a resolution/patch be available for this soon? Thanks, Patsy

1 0

video about Samoa's 2011 timezone switch
by Zefram Jan. 19, 2018

Jan. 19, 2018

An entertaining video about timezones, with particular reference to Samoa's 2011 move across the International Date Line: https://www.youtube.com/watch?v=rARMsjh4Zu0 -zefram

1 0

broken compression in archive
by Zefram Jan. 18, 2018

Jan. 18, 2018

I'm doing some work on how to access historical tzdb versions, and I noticed that tz{code,data}94d.tar.Z are, despite their names, uncompressed tar files. To be precise, I refer to the files with these SHA-512 hashes: 9872b757ee3a8bf0ed3de1f0875f878b977b34bd2b60440b23a8c7308a7514d12a5d5d283387973e61b75e1a8eebd27009aab78eee4e12f1f1a5593f71941328 tzcode94d.tar.Z e1524951a5c261cc8eef1f3adadf5ebf8143293745fda9411a0090d6bb6e19f899dd7a6e55fe2f8f490a167a3da392020e49b369984bc1f5cbed87d664eb58de tzdata94d.tar.Z They're unique, in the present archive <ftp://ftp.iana.org/tz/releases/>, in having a mismatch between format and filename suffix. I think these files should be replaced, in the archive, with actual compressed (with compress(1)) versions of these tars, under the same name, so that the names are no longer misleading and they are in the same format as the surrounding files. The other way to make the names no longer misleading is to rename these files, dropping the ".Z" suffix, but this approach has the problem that these files would (still) have a different format from all the other tarballs. Note that this mismatch is not a mistake made in the original release of 94d, and the replacement that I'm proposing would not erase a record of the original release files. The original 94d release was of *gzipped* tar files, which are not in the present archive. Actual releases switched from .Z to .gz at 93g, but the archive files switch at tzdata95c and tzcode95d. Obviously someone recompressed the intervening tarballs somewhere along the chain of custody that led to the present archive, and it appears that the failure to (re)compress 94d happened in that process. -zefram

4 6

Fwd: Issue with tzdata2018a.tar.gz Europe/Dublin Rule
by Vicky Jan. 18, 2018

Jan. 18, 2018

Hi, while parsing the data i found the issue in rule Europe/Dublin Negative DST.. Previous version or not in any other file there is no negative dst. DST either start and end . # The following is like GB-Eire and EU, except with standard time in # summer and negative daylight saving time in winter. # 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 Rule Eire 1972 1980 - Oct Sun>=23 2:00u -1:00 GMT Rule Eire 1981 max - Mar lastSun 1:00u 0 IST Rule Eire 1981 1989 - Oct Sun>=23 1:00u -1:00 GMT Rule Eire 1990 1995 - Oct Sun>=22 1:00u -1:00 GMT Rule Eire 1996 max - Oct lastSun 1:00u -1:00 GMT Please explain why -ve dst offset compared with other files. Regards, Vaibhav

1 0

Re: [tz] Build error on tzdb-2018a
by Paul Eggert Jan. 17, 2018

Jan. 17, 2018

Matias Fonzo wrote: > I can't update tzdb-2018a, I am getting this error: > > make: *** No rule to make target 'pacificnew', needed by 'version'. Thanks for reporting this packaging problem, which was not detected by the checks that I do before making a distribution. I have installed the attached patch to the development version; please give it a try. Because this problem was caught before I announced 2018a, I will hold off on making an announcement. Instead, I plan to wait a day or so for review of this patch, and then release 2018b with this patch.

2 3

tzdata2018a released
by Seán Coffey Jan. 17, 2018

Jan. 17, 2018

It looks like 2018a has been released with a typo on the release date stamp : (Released 2010-01-12) [1] No announcement was sent to the announcement mailing list. Can the administration of such releases be made more transparent please ? The same type of admin issue happened during 2017. regards, Sean. [1] https://www.iana.org/time-zones

2 1

Missing pacificnew data file
by Kerry Shetline Jan. 17, 2018

Jan. 17, 2018

Hi, I just downloaded the 2018a distribution of the tz database, with code. I tried to do a “make” and the make failed due to the missing pacificnew file. Copying that file from 2017c fixed the problem. The Java tool tzupdater also fails because of this missing file. I realize it might be that you are deliberately getting rid of this file, but your own make process is broken with the file missing, and I imagine other tools for updating time zone data besides tzupdater will also fail due to this file being gone. If you accidentally left pacificnew out, you might need to re-release the distribution. If getting rid of it was intentional, you’ll have to update your make process, or perhaps include a blank or commented-out copy of pacificnew. I also didn’t notice any changes in Brazil or Ireland as I expected to see from the release notes, which possibly is another problem. -Kerry

2 1

Brazil moves DST start to November
by Steffen Thorsen Jan. 17, 2018

Jan. 17, 2018

According to many media sources, next year's DST start in Brazil will move to the first Sunday of November, and it will stay like that for the years after. Some examples in Portugese: https://noticias.r7.com/economia/por-eleicao-temer-reduz-periodo-de-horario… https://exame.abril.com.br/brasil/por-eleicao-temer-reduz-periodo-de-horari… We have made a brief English summary: https://www.timeanddate.com/news/time/brazil-delays-dst-2018.html Best regards, Steffen Thorsen - timeanddate.com

4 7

Canada/East-Saskatchewan
by Derick Rethans Jan. 16, 2018

Jan. 16, 2018

Hi, I saw that the PHP build with the new timezone database (2017.3) failed due to Canada/East-Saskatchewan suddenly being gone. What's up with that? https://travis-ci.org/php/php-src/jobs/291636544#L1280 cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Like Xdebug? Consider a donation: https://xdebug.org/donate.php twitter: @derickr and @xdebug

6 9

leap-seconds.list file is out of date
by R. Bonomi Jan. 15, 2018

Jan. 15, 2018

The iana.org file only contains info through Bulletin C54, but Bulletin C55 is out. Reference: the leap-seconds.list file at usno.mil

3 2

Mongolian time zone.
by Phake Nick Jan. 13, 2018

Jan. 13, 2018

Currently, tz database say Mongolia use UTC+7/8/9 as timezone. However, after quick google search, I found a question about time of Mongolia in a Mongolia question and answer time at [1]. The page itself is facing technical problem to me so I accessed it via Google cache which I subsequently thrown the cache into Google translate and archived the result at [2]. According to the page from 2016, three different users of the site answered the question with same answer, and all of them are saying Mongolia have three different timezone: 6, 7, 8. This is different from the information recorded in tz database. So, is the information in tz database incorrect? And then, another question on the site [3] (archived in [4]) asked about when did Mongolia start officially using the world time and someone answered since 1997. What does that mean? (On the other hand, another answer to a similar question say 1961... [5][6] or is that an error in machine translation?) [1]: http://acyy.mn/3379/монгол-улс-хэд-хэддүгээр-цагын-бүсэд-оршдог-вэ [2]: http://archive.is/y3jpH [3]: http://acyy.mn/8620/монгол-хэдэн-оноос-дэлхийн-бүсийн-цагийг-хэрэглэж-эхлэс… [4]: http://archive.is/PQBVk [5]: http://acyy.mn/7379/му-хэдэн-оноос-дэлхийн-цагийг-баримтлах-болсон-бэ [6]: http://archive.is/e39nW

2 1

Sao Tome Principe change of time zone
by Steffen Thorsen Jan. 9, 2018

Jan. 9, 2018

Multiple sources tell that Sao Tome changed from UTC to UTC+1 as they entered the year 2018: https://www.dn.pt/lusa/interior/relogios-avancam-uma-hora-em-sao-tome-e-pri… http://pt.rfi.fr/sao-tome-e-principe/20180101-sao-tome-e-principe-muda-de-h… http://www.stp-press.st/2017/12/23/sao-tome-e-principe-vai-mudar-hora-a-par… So it seems the Africa/Sao_Tome zone needs to activated again! Our English summary: https://www.timeanddate.com/news/time/sao-tome-principe-time-zone-change.ht… Best regards, Steffen Thorsen - timeanddate.com

3 3

[PATCH] * northamerica: Add note re Chicago time before 1883.
by Paul Eggert Jan. 8, 2018

Jan. 8, 2018

--- northamerica | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/northamerica b/northamerica index 505300a..a014126 100644 --- a/northamerica +++ b/northamerica @@ -348,6 +348,18 @@ Zone America/New_York -4:56:02 - LMT 1883 Nov 18 12:03:58 # Nebraska, eastern North Dakota, Oklahoma, eastern South Dakota, # western Tennessee, most of Texas, Wisconsin +# From Paul Eggert (2018-01-07): +# In 1869 the Chicago Astronomical Society contracted with the city to keep +# time. Though delayed by the Great Fire, by 1880 a wire ran from the +# Dearborn Observatory (on the University of Chicago campus) to City Hall, +# which then sent signals to police and fire stations. However, railroads got +# their time signals from the Allegheny Observatory, the Madison Observatory, +# the Ann Arbor Observatory, etc., so their clocks did not agree with each +# other or with the city's official time. The confusion took some years to +# clear up. See: +# Moser M. How Chicago gave America its time zones. Chicago. 2018-01-04. +# http://www.chicagomag.com/city-life/January-2018/How-Chicago-Gave-America-I… + # From Larry M. Smith (2006-04-26) re Wisconsin: # https://docs.legis.wisconsin.gov/statutes/statutes/175.pdf # is currently enforced at the 01:00 time of change. Because the local -- 2.7.4

1 0

Three time zones meeting at one location
by Paul Eggert Dec. 29, 2017

Dec. 29, 2017

In yesterday's My Modern Met, Jessica Stewart says that in over 20 locations in the world, three different time zones converge. Surveyor Generals Corner in Australia and Treriksrøysa (for the point where Finland, Norway, and Russia meet) are two examples. For time zone hounds it may be an amusing read, if only to spot the mistakes. Stewart J. Places around the world where three time zones meet in the same spot. My Modern Met. 2017-12-28. https://mymodernmet.com/three-different-time-zones-facts/

1 0

Lithuania calls on EU to stop adjusting clocks for daylight savings
by Lord Buddha Dec. 23, 2017

Dec. 23, 2017

https://www.theguardian.com/world/2017/dec/22/lithuania-calls-on-eu-to-stop…

1 0

Transitions after those included in zoneinfo binaries?
by Paul G Dec. 21, 2017

Dec. 21, 2017

I recently noticed a discrepancy between the python-dateutil and pytz libraries when calculating offsets for dates after the last included transition in the zonefile binaries. What it boils down to is that when it runs out of transitions, python-dateutil selects the "standard" offset and pytz assumes that after the last transition the value "holds". In the southern hemisphere, this produces two different behaviors. Obviously there's no "right" answer here, since these are predictions about what time zones will be applied 20 years in the future (and even if the rules stayed the same, the "end date" is entirely artificial). Still, I wonder if it might be worth a bit of discussion and possibly a note in the Theory file? Barring a representation of the data that exposes the rules directly (in which case no such artificial limitation would be necessary), I think either fallback is defensible. Best, Paul

7 10

Complexities of time rendered graphically
by Steve Jones Dec. 19, 2017

Dec. 19, 2017

Folks: Today's XKCD comic is amusing: https://xkcd.com/1930/ Steve Jones [image: Emacs!]

3 5

default value of TZDEFAULT
by scs＠eskimo.com Dec. 18, 2017

Dec. 18, 2017

[This is a tzcode issue, not tzdata. Your regular discussion of zone definition and naming issues will resume shortly. :-) ] Consider this simple little program: #include <stdio.h> #include <time.h> int main() { time_t t = time(NULL); struct tm *tmp = localtime(&t); puts(asctime(tmp)); return 0; } There's nothing special about this program (that's the point). But suppose I download tzcode or tzdb and then compile the little program (call it lt.c) along with a just-built localtime(), like this: make localtime.o cc -o lt lt.c localtime.o But if I then run 'lt', it is likely not to work -- there's a pretty good chance it will print the current time in UTC, not my local time zone. If it fails, one reason is that it didn't successfully find my system's already-installed tz files. (That is, I made no attempt to build or install any new tz files.) The reason it didn't find them is obvious enough, and the Makefile contains all the hints I need: TOPDIR= /usr/local # "Compiled" time zone information is placed in the "TZDIR" directory # (and subdirectories). # Use an absolute path name for TZDIR unless you're just testing the software. # TZDIR_BASENAME should not contain "/" and should not be ".", ".." or empty. TZDIR_BASENAME= zoneinfo TZDIR= $(TOPDIR)/etc/$(TZDIR_BASENAME) And, sure enough, on my system, the already-installed tz files are not in /usr/local, they're in /usr/share. So it looks like if I change TOPDIR to /usr/share, or TZDIR to /usr/share/zoneinfo, I should be able to fix it. But no! It still doesn't work, and the reason is, my user environment doesn't have the TZ environment variable set; I'm assuming that the system's default time zone will be used. And, out of the box, the tzcode distribution assumes that the local time zone is defined by a file 'localtime' *in TZDIR*; that is, it essentially assumes that TZDEFAULT is $TZDIR/localtime. But some (perhaps even many) systems put it in /etc/localtime. That's where my (MacOS) system puts it, and a lot of Linux systems put it there, too. The upshot is that on such a system, if you compile and use localtime.c straight out of the tzcode distribution, it won't find your localtime file, and will end up falling back to UTC unless TZ is set. Since the Makefile already lets you set your own version of TZDIR (overriding the setting in tzfile.h), I think it makes sense to do the same thing for TZDEFAULT. Patch attached. With this patch in place, and with the Makefile edited to say TZDEFAULT = "/etc/localtime" fresh compiles of localtime.o correctly find my system's localtime file, and the lt program finally prints local time, as expected. (This tweak to TZDEFAULT's usage helps the extraction case -- that is, when the code tries to fetch the default zone, but not necessarily the tz file building case. I'm not sure whether 'make install' will do the right thing when TZDEFAULT is set, but it definitely doesn't do the right thing if DESTDIR and TZDEFAULT are both set. Is using DESTDIR supported? The Makefile should probably document it if so.) Diagnosing problems involving misconfigured TZDIR and TZDEFAULT variables can be surprisingly difficult. The localtime code doesn't have any way of telling you it's having trouble finding tz files in general, or the localtime file in particular. I'll address that issue in a separate thread. Steve Summit scs(a)eskimo.com

4 10

setting TZ and calling localtime_r
by scs＠eskimo.com Dec. 18, 2017

Dec. 18, 2017

There's code in tzcode (and, I suspect not coincidentally, glibc's localtime implementation as well) to not call the internal version of tzset on calls to localtime_r, but rather only on calls to localtime. The justification is that Posix says localtime_r doesn't need to update the global tzname variable. I don't have a copy of the Posix spec handy, so I can't check: does Posix also say that localtime_r doesn't need to check for and make use of a possibly-changed value of TZ? As implemented (both in tzcode and glibc), it doesn't. If a program calls localtime, then calls setenv to set a new value of TZ, then calls localtime again, it works as expected, but if it calls localtime_r, setenv, localtime_r, it doesn't. (The workaround, of course, is to call localtime_r, setenv, tzset, localtime_r.)

5 4

Kyiv
by gocdoms gocdoms Dec. 18, 2017

Dec. 18, 2017

Hello! City Kyiv is not Kiev. The *founder* of Kyiv is *Kyi*. Not Kie! Please see attached picture.

14 24

Asia/Shanghai (was: Re: Kyiv)
by Phake Nick Dec. 15, 2017

Dec. 15, 2017

Speaking of which, after reading naming convention of zones, wouldn't it still be better to rename the zone to Asia/Beijing mowadays? As almost all users are referring to the zone as "Beijing Time", if in any case there are different time standard emerge that caused Beijing and Shamghai to use different tome standard instead, then it would be more likely for the zone's user to think the Beijing time is a time being continued while Shanghai time would be another new time. In order to reflect the line of thinking and thus when future communication or ammendment easier when things really do change, would such renaming make sense? 2017年12月16日 03:20 於 "Garrett Wollman" <wollman(a)csail.mit.edu> 寫道： > > Contrast the case (which thankfully we do not have to deal with) of > the capital city of the People's Republic of China. In English, it > used to be called "Peking", and in fact in the name of the university > and of the duck dish it still is. The PRC government made a concerted > campaign to change the name used by English speakers to be "Beijing", > which is a phonetic representation of the name of the city in Mandarin > (putonghua). This has to a very large extent worked, and now most > English texts say "Beijing" and not "Peking" (although many people > still don't pronounce it "correctly" because the letters in hanyu > pinyin don't have the same sound values as they do in English). > However, in many languages *other than English*, the name of the city > has not changed -- AFAIK it's still "Pékin" in French, for example.

3 2

tzdata gpg key
by Zura Kutchava Dec. 8, 2017

Dec. 8, 2017

Dear Friends, On https://data.iana.org/time-zones/releases/ I found packages and signatures, but cannot find gpg key to veryfing them. Can you be so kind to tell me where is gpg key for verifying? I am building linux from scratch and writing script for downloading and verifying main packages, so your help will be very important. Thanks beforehand, Regards.

2 1

Europe/Kiev
by Bohdan Vovchuk Dec. 7, 2017

Dec. 7, 2017

Hello. Please change timezone *Europe/Kiev* to *Europe/Kyiv* because first variation is wrong. Ukrainian timezone should be changed to Europe/Kyiv. Kyiv - is a one and only correct international transliteration. -- *Regards, Bohdan Vovchuk*

2 1

Filling the gaps ...
by Lester Caine Dec. 5, 2017

Dec. 5, 2017

The main problem that everybody seems to be skirting around is that the tz database has NO interest in exactly where someone is located and there is no remit TO manage that. Even tzdist which was the latest attempt to plug a major distribution hole has no remit on supplying the correct data for a particular location! Both are simply managing the set of rules that anybody can use where ever they are. Importantly allowing third parts to work out a local time for some elsewhere in the world. Some other data source is really needed to serve up the CURRENT set of rules for a location, and that is probably only currently possible using geonames.org which uses the current timezone_id and it's own simplified timeZone.txt table! What is missing is any historic (or ongoing) changes to that information, such as a location that was using one tz rule set but moved to another. In addition any pre-1970 material can not be identified. tzdist has the remit and tools to fill one of the holes that tz on it's own can not and that is historic changes TO the rule sets. My interest in the tz database came from a major problem with material that had been normalised to UTC time but there was no record as to what rules had been used TO normalise the data, so one could not verify if the CURRENT tz rules were appropriate for establishing the then local times. As Paul has quite rightly pointed out, much historic data was invented, so CORRECTING the data when more accurate information is established is perfectly correct, but one needs to be able to also establish just which rules have changed and one can then adjust the material that is now suspect ( - IF APPROPRIATE ;) ) The whole point of tzdist was to sort current day problems, so if a mobile device with a stored calendar lands in a new location where there has been an 'unscheduled' change of tz rules that change CAN be propagated quickly without needing a full tz update but that will only work if someone is actually running the primary tzdist source. Moving forward, that primary tzdist source needs to maintain a full historic record prior to 1970 since it also provides the base from which rules for historic data normalization can be managed. It allows for the tz timezone_id's to be used to identify the base rule sets, but allows new rule sets to be created ... just without any rules on just how THAT is managed :( Potentially any geonameid could have it's own individual tzdist dataset and track the history of changes as a location moves from one political jurisdiction to another and show it's simple solar time as appropriate. Something that neither tzdist or tz is actually mandated to supply? Merging geonames.org with openstreetmap.org one gets graphic displays of the area that timezones CURRENTLY cover, but one can not establish if the same offsets applied back in the 1960's when DST local times are well documented. And both databases throw away the historic data to those mappings along with a whole load of other historic material. While the vast majority of users probably could not care less, the annoyance here is that the material existed so it's not as if we are asking for extra work, just a mechanism that remembers that say in 2014 the Crimea moved from one set of tz rules to another. Once the mechanism is in place, then as new historic material comes to light, the historic record can be corrected and tzdist has the mechanism for that in relation to timezone rules. So as a start ... what has happened to tzdist. The full historic record of tz changes can provide a complete set of data that has been used over the last 20 years and as new changes are logged in now they can be pushed to tzdist while also maintaining tz distribution for off-line population systems. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

3 3

[PROPOSED] Pacify GCC 7.2.1 x86-64 -Wmaybe-uninitialized
by Paul Eggert Dec. 4, 2017

Dec. 4, 2017

* zdump.c (main): Add an INITIALIZE to pacify gcc 7.2.1 20170915 (Red Hat 7.2.1-2) on x86-64 with -Wmaybe-uninitialized, which otherwise incorrectly warns that ‘ab’ might be used uninitialized. Clarify the expression that confused GCC (though the clarification is evidently not enough). --- zdump.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/zdump.c b/zdump.c index 3cd4f42..60a027e 100644 --- a/zdump.c +++ b/zdump.c @@ -552,6 +552,7 @@ main(int argc, char *argv[]) } if (t < cutlotime) t = cutlotime; + INITIALIZE (ab); tm_ok = my_localtime_rz(tz, &t, &tm) != NULL; if (tm_ok) { ab = saveabbr(&abbrev, &abbrevsize, &tm); @@ -567,11 +568,10 @@ main(int argc, char *argv[]) : cuthitime); struct tm *newtmp = localtime_rz(tz, &newt, &newtm); bool newtm_ok = newtmp != NULL; - if (! (tm_ok & newtm_ok - ? (delta(&newtm, &tm) == newt - t - && newtm.tm_isdst == tm.tm_isdst - && strcmp(abbr(&newtm), ab) == 0) - : tm_ok == newtm_ok)) { + if (tm_ok != newtm_ok + || (tm_ok && (delta(&newtm, &tm) != newt - t + || newtm.tm_isdst != tm.tm_isdst + || strcmp(abbr(&newtm), ab) != 0))) { newt = hunt(tz, argv[i], t, newt); newtmp = localtime_rz(tz, &newt, &newtm); newtm_ok = newtmp != NULL; -- 2.14.3

1 0

Very cool app that uses yout TZ Database
by Anton Skorniakov Dec. 4, 2017

Dec. 4, 2017

Hello! First of all, I want to thank you very much for such cool time zones database, we are using it in our product. I want to suggest adding one more cool and simple free web based time zone converter app https://timezoneconverterapp.com/ to this page https://data.iana.org/time-zones/tz-link.html (“Web sites using recent versions of the tz database” section). I am one of the creators of this app and of course, it uses IANA TZ Database. Thank you! _________________ Anton

2 1

Fwd: New Version Notification for draft-murchison-tzdist-tzif-00.txt
by Ken Murchison Nov. 27, 2017

Nov. 27, 2017

FYI. This is our initial effort at "officially" documenting the time zone data binary format and defining a MIME type for it so it can be used with the Time Zone Distribution Service. -------- Forwarded Message -------- Subject: New Version Notification for draft-murchison-tzdist-tzif-00.txt Date: Mon, 27 Nov 2017 04:58:00 -0800 From: internet-drafts(a)ietf.org To: Arthur David Olson <arthurdavidolson(a)gmail.com>, Paul Eggert <eggert(a)cs.ucla.edu>, Ken Murchison <murch(a)fastmailteam.com>, Arthur Olson <arthurdavidolson(a)gmail.com>, Kenneth Murchison <murch(a)fastmailteam.com> A new version of I-D, draft-murchison-tzdist-tzif-00.txt has been successfully submitted by Kenneth Murchison and posted to the IETF repository. Name: draft-murchison-tzdist-tzif Revision: 00 Title: The Time Zone Information Format (TZif) Document date: 2017-11-26 Group: Individual Submission Pages: 12 URL: https://www.ietf.org/internet-drafts/draft-murchison-tzdist-tzif-00.txt Status: https://datatracker.ietf.org/doc/draft-murchison-tzdist-tzif/ Htmlized: https://tools.ietf.org/html/draft-murchison-tzdist-tzif-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-murchison-tzdist-tzif-00 Abstract: This document defines the Time Zone Information File Format for representing and exchanging time zone information, independent of any particular service or protocol. A MIME media type for this format is also defined. Open Issues o Need to review definitions of terms. o Should we require TZDIST servers to always return a particular format (2 or 3) with/without leap seconds? Or should we allow the client to choose what they want (via parameters on the MIME type)? o Are we referencing the correct and most current versions of the relevant POSIX specs? o Is the MIME registration complete and correct (e.g. any security or privacy considerations)? Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat

1 0

FW: Beginner's help request
by Daniel Ford Nov. 25, 2017

Nov. 25, 2017

Oops, looks like I was mistaken. Howard's library appears to be not (specifically) for Arduino, but a C++ library for Windows (and maybe other) platforms. Maybe it will compile in the Arduino IDE, though I suspect it will be problematic, if possible at all. And I've so far found only one TZdb mirror that keeps a current copy of the data - very disappointing. It's a shame the whole TZdb scheme is so user-unfriendly. Quite discouraging. Regards, Daniel -----Original Message----- From: Daniel Ford [mailto:dfnojunk@gmail.com] Sent: Saturday, November 04, 2017 7:03 PM To: 'Time zone mailing list' Subject: RE: [tz] Beginner's help request Woohoo! I've discovered (and downloaded) an Arduino library, written by Howard E. Hinnant: "This timezone library is a complete parser of the IANA timezone database. It provides for an easy way to access all of the data in this database, using the types from "date.h" and <chrono>. The IANA database also includes data on leap seconds, and this library provides utilities to compute with that information as well." All I need to find now are established TZdb mirrors that keep their copy up-to-date, so I don't overload the master TZdb with queries. Can anyone point me to any, please? Regards, Daniel --------------- Daniel Ford (Gerroa, Australia)

7 20

Beginner's help request
by Daniel Ford Nov. 21, 2017

Nov. 21, 2017

I'm looking to develop a 'world clock' that could be sold to anyone (with Internet access via a Wi-Fi AP) anywhere in the world, that will display their local time, taking into account DST if/when applicable. Given that DST 'rules' can change at the whim of governments, my firmware will need to annually look up 'current' DST rules from the web. After much searching, it seems that your TZ Database is the best supported such reference for time zone rules. But I'm having great difficulty working out how I might access its mine of information... (I'll understand if you don't have time to help out a beginner, and maybe then you could refer me to a help site for TZ database applications.) I'm a hardware engineer with some programming experience, particularly assembler (various MCUs) and some C, but little or no experience in other languages. I'm developing this clock on an Arduino-like platform (NodeMCU, which has in-built Wi-Fi). My development tools run on a Win7Pro64 PC. The tools that you kindly provide for your database appear to be geared primarily towards Linux/Unix platforms, and I have no idea how I might convert them for a NodeMCU! I'm looking for some 'simple' way to access the desired TZ/DST information, preferably using simple string searches. For my application, all I'm interested in are the *current* rules. The wealth of history in your db is undoubtedly of interest to many, but for me is just 'clutter' to be searched through. But writing a program to find those rules for a particular locality has me stumped right now. I can't expect my dumb users to know a letter code for their time-zone/DST-rules, so all I'm expecting them to select from program-generated lists are: (1) their world region (Europe, Asia, Australasia, etc), and (2) the name of a major city in their time-zone with the same DST rules they follow. Let's take a concrete example: say my user has nominated 'Australasia' and 'Hobart'. So I look in your Australasia file and do a (manual at this stage) search for 'Hobart', but find only one reference to it (other than in comments). The jumble of numbers and letters there do not (clearly) tell me when DTS starts or ends. So how could I possibly write some code to find out that required information?? I've looked through the TZ_database-2017b.tar file for some sort of 'how-to' explanation of what all the file contents mean and how to programmatically search for a specific TZ, but have so far found nothing. Ideally, what I'd like to see is a text-only table of just current TZ/DST rules for each region/locality (they could all fit into a single file with all the historical data and comments removed), perhaps in the clear form used by Jack Christensen in his excellent Arduino Timezone library examples, such as... // Australia Eastern Time Zone (Sydney, Melbourne, Hobart) TimeChangeRule aEDT = {"AEDT", First, Sun, Oct, 2, 660}; TimeChangeRule aEST = {"AEST", First, Sun, Apr, 3, 600}; TimezoneExt ausET("NSW, Vic, Tas", aEDT, aEST); // Australia Eastern Time Zone (Brisbane) TimezoneExt QldT("Queensland", aEST, aEST); // no DST in Qld! ... which clearly tells me in a program-searchable way that in the main eastern states DST starts on the first Sunday in October at 2am, becoming UTC offset +11 hours (660 minutes), and ends on the first Sunday in April at 3am, reverting to UTC offset +10 hours. Couldn't be simpler! Any help in using the TZ database will be much appreciated (and acknowledged in my source code). Regards, Daniel --------------- Daniel Ford (Gerroa, Australia) "My loathings are simple: stupidity, oppression, crime, cruelty, soft music." - Vladimir Nabokov

17 63

[PROPOSED] Update TZDIST citation.
by Paul Eggert Nov. 21, 2017

Nov. 21, 2017

* tz-link.htm: Update TZDIST URL and discussion. (Thanks to Ken Murchison for the heads-up.) --- tz-link.htm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 0684ed1..edf8eec 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -267,10 +267,10 @@ href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with <a href="https://tools.ietf.org/html/rfc7809">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for -transferring time zone data by reference. The (expired) draft <a +transferring time zone data by reference. The draft <a id="TZDIST-Geolocate" -href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-00">TZDIST -Geolocate Extension</a> would have let a client determine its time zone region +href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-01">TZDIST +Geolocate Extension</a> lets a client determine its time zone region from its geographic location using a <a href="https://tools.ietf.org/html/rfc5870">'geo' URI</a>.</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> -- 2.7.4

1 0

[PROPOSED] * tz-link.htm: Improve citations to ISO standards.
by Paul Eggert Nov. 21, 2017

Nov. 21, 2017

--- tz-link.htm | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 93bcbae..0684ed1 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -318,8 +318,11 @@ Database Parser</a> is a <a href="https://en.wikipedia.org/wiki/C%2B%2B">C++</a> parser and runtime library that is <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0355r4.html">moving -forward</a> for inclusion in the <a -href="https://isocpp.org/std/the-standard">ISO C++ standard</a>. +forward</a> for inclusion in the next iteration of <a +href="https://isocpp.org/std/the-standard"><em><abbr +title="International Organization for Standardization">ISO</abbr> +International Standard ISO/IEC 14882:2017(E) – Programming +Language C++</em></a>. It is freely available under the <abbr title="Massachusetts Institute of Technology">MIT</abbr> license.</li> <li><a id="ICU" href="http://site.icu-project.org">International Components for @@ -862,10 +865,9 @@ both <abbr title="Locale Data Markup Language">LDML</abbr> the international standard date and time notation</a> is a good summary of <a -href="https://www.iso.org/standard/40874.html"><abbr -title="International Organization for Standardization">ISO</abbr> +href="https://www.iso.org/standard/40874.html"><abbr><em>ISO</abbr> 8601:2004 – Data elements and interchange formats – Information -interchange – Representation of dates and times</a>.</li> +interchange – Representation of dates and times</em></a>.</li> <li> <a href="https://www.w3.org/TR/xmlschema-2/#dateTime"><abbr>XML</abbr> Schema: Datatypes – dateTime</a> specifies a format inspired by -- 2.7.4

1 0

Earth rotation
by Arthur David Olson Nov. 19, 2017

Nov. 19, 2017

Seems there's a correlation between leap seconds and earthquakes. "Upsurge in big earthquakes predicted for 2018 as Earth rotation slows." https://www.theguardian.com/world/2017/nov/18/2018-set-to-be-year-of-big-ea… @dashdashado

2 1

IANA and Microsoft mentioned in Wired article
by Matt Johnson Nov. 15, 2017

Nov. 15, 2017

A college of mine from the Windows time zone servicing team was recently interviewed for Wired magazine. https://www.wired.com/story/microsoft-time-lords/ I was happy to see the reporter included details about the critical contributions that the IANA TZDB brings to the table as well. Thanks everyone! Matt Johnson (Microsoft)

1 0

Please include Montreal
by Sébastien Bouchard Nov. 14, 2017

Nov. 14, 2017

It would be nice if Montreal was included in your database. There are smaller cities that are listed. I am using the latest Linux Mint Mate (18.2) and i had to choose Toronto to get into the right timezone. Montreal is not there. It doesn't matter much to me but there are some people here who will find it strange. Toronto is like... in another country. It's about History and the French people in Canada... [1492899431935_logo3-rouge+gris-Sb=64px.png] <https://sites.google.com/view/sb-junior/> sites.google.com/ <https://sites.google.com/view/sb-junior/>view/sb-junior/<https://sites.google.com/view/sb-junior/><https://sites.google.com/view/sb-junior/><https://sites.google.com/view/sb-junior/>

12 21

tzfile(5)
by Ken Murchison Nov. 13, 2017

Nov. 13, 2017

All, Is https://github.com/eggert/tz/blob/master/tzfile.5 the normative reference for the binary format of tzdata? I thinking about writing an I-D to register application/tzfile as a MIME type for use with TZDist <https://tools.ietf.org/html/rfc7808> and I obviously need a reference to the file format. Or should I document the format in the draft? Does anyone want to suggest a different name for the format? -- Kenneth Murchison Cyrus Development Team FastMail Pty Ltd

3 2

draft-murchison-tzdist-geolocate-01
by Ken Murchison Nov. 13, 2017

Nov. 13, 2017

All, I'd appreciate any and all comments on this updated draft. I have a working implementation that I can probably put on an externally facing server if folks are interested. https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-01 -- Kenneth Murchison Cyrus Development Team FastMail Pty Ltd

2 1

[PROPOSED] * tz-link.htm: Improve citations to ISO standards.
by Paul Eggert Nov. 13, 2017

Nov. 13, 2017

--- tz-link.htm | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 93bcbae..0684ed1 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -318,8 +318,11 @@ Database Parser</a> is a <a href="https://en.wikipedia.org/wiki/C%2B%2B">C++</a> parser and runtime library that is <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0355r4.html">moving -forward</a> for inclusion in the <a -href="https://isocpp.org/std/the-standard">ISO C++ standard</a>. +forward</a> for inclusion in the next iteration of <a +href="https://isocpp.org/std/the-standard"><em><abbr +title="International Organization for Standardization">ISO</abbr> +International Standard ISO/IEC 14882:2017(E) – Programming +Language C++</em></a>. It is freely available under the <abbr title="Massachusetts Institute of Technology">MIT</abbr> license.</li> <li><a id="ICU" href="http://site.icu-project.org">International Components for @@ -862,10 +865,9 @@ both <abbr title="Locale Data Markup Language">LDML</abbr> the international standard date and time notation</a> is a good summary of <a -href="https://www.iso.org/standard/40874.html"><abbr -title="International Organization for Standardization">ISO</abbr> +href="https://www.iso.org/standard/40874.html"><abbr><em>ISO</abbr> 8601:2004 – Data elements and interchange formats – Information -interchange – Representation of dates and times</a>.</li> +interchange – Representation of dates and times</em></a>.</li> <li> <a href="https://www.w3.org/TR/xmlschema-2/#dateTime"><abbr>XML</abbr> Schema: Datatypes – dateTime</a> specifies a format inspired by -- 2.7.4

1 0

Re: [tz] [PATCH] add attribute nonstring
by Paul Eggert Nov. 12, 2017

Nov. 12, 2017

Thanks for mentioning the problem with GCC 8. If the intent of __attribute__((__nonstring__)) is to consistently mark char arrays that are not necessarily null-terminated strings, then lots of data structures in the tzdb code would need to be marked with this attribute. For example, every member of tzfile.h's 'struct tzhead' would have the attribute, because they are all char arrays that might not be null-terminated. Looking at the proposed glibc patch, it seems its intent is more modest. All it's trying to do is to pacify GCC 8 so that GCC doesn't complain about calls to strncpy and strncat. In that case, a simpler and cleaner fix for tzdb is to stop using strncpy and strncat. (I suspect that the main reason tzdb uses strncpy is that its code is so old that it predates the widespread availability of memcpy.) So I installed the attached patch into tzdb's zic.c and it should be part of the next tzdb release. Perhaps you can this idea elsewhere in the rest of the glibc patch too. It would be a lot of work to consistently change glibc to use __attribute__((__nonstring__)) for its documented purpose. If glibc can avoid calling strncpy and strncat, it won't need __NONSTRING; if not, then I suggest changing this: /* Describes a char array that is not necessarily a NUL-terminated string. */ # define __NONSTRING __attribute__ ((__nonstring__)) to something more like this: /* Describes a char array whose address can safely be passed as the first argument to strncpy and strncat, as the char array is not necessarily a NUL-terminated string. */ # define __NONSTRING __attribute__ ((__nonstring__)) in sys/cdefs.h, so that the more-modest goal of the patch is clearer to the reader. I'll CC: this to tz(a)iana.org as a heads-up there.

2 1

Was Azerbaijan the first government to cite tzdb?
by Paul Eggert Nov. 11, 2017

Nov. 11, 2017

When Azerbaijan's Ministry of Transport, Communications and High Technologies said late last month that Azerbaijan would stay at +04, its announcement mentioned the TZ database. See: [Azerbaijan will not translate time] (in Russian). Sputnik. 2017-10-29. https://news.rambler.ru/caucasus/38277699-azerbaydzhan-ne-stanet-perevodit-… Initially I thought this was a first, but it turns out that the same ministry also mentioned tzdb (though not by name) in March 2016, here: Recommendations in connection with abolition of daylight saving time. http://www.mincom.gov.az/media-en/news-2/details/12011 (Azerbaijani and Russian translations are available.) Is the March 2016 announcement the first time a government has cited tzdb, or can readers come up with earlier examples?

7 9

Time zones, daylight saving, and cancer risk
by Paul Eggert Nov. 11, 2017

Nov. 11, 2017

In 2011 Mikhail Borisenkov of the Komi Science Center in Syktyvkar, Russia reported that latitude and longitude can affect cancer rates. In particular he found that in Russia, position within a time zone explained 15% of the variability in female breast cancer mortality. Similar results have now been reported in the US. Neil Caporaso and colleagues at the National Cancer Institute in Bethesda, Maryland recently found a significant association between time zone position and cancer incidence. They estimated that the risk of breast cancer is 12% higher at the western extreme of a US time zone compared to the eastern extreme. Other cancers show similar (but smaller) effects. A plausible explanation is that ill-timed light increases cancer risk by disrupting circadian rhythm. This effect has been known for some time in other respects: for example, blind women have a significantly lower risk for breast cancer, possibly because melatonin offers a protective effect and nocturnal exposure to visible light suppresses melatonin secretion. This is currently an active area of research: the 2017 Nobel Prizes in Physiology or Medicine went to circadian-rhythm researchers. Perhaps we should not take Ben Franklin's "early to bed and early to rise" advice to an extreme, as daylight saving time (or more generally, moving time zones eastward) can significantly increase cancer risk. ---- Stevens RG. Breast cancer risk higher in western parts of time zones; is electric light to blame? The Conversation. 2017-10-19. https://theconversation.com/breast-cancer-risk-higher-in-western-parts-of-t… Gu F, Xu S, Devesa SS et al. Longitude position in a time zone and cancer risk in the United States. Cancer Epidem Biomarkers Prev. 2017-08-01;26(8):1306-11 http://dx.doi.org/10.1158/1055-9965.EPI-16-1029 Borisenkov MF. Latitude of residence and position in time zone are predictors of cancer incidence, cancer mortality, and life expectancy at birth. Chronobiology Int. 2011-01-13;28(2):155-62. http://dx.doi.org/10.3109/07420528.2010.541312

1 0

Fwd: Howard Hinnant's tz Library (was Beginner's help request)
by Bill Seymour Nov. 9, 2017

Nov. 9, 2017

Oops...meant this for the list, not just Daniel. --bs ---------- Forwarded message ---------- From: Bill Seymour <stdbill.h(a)pobox.com> Date: Wed, Nov 8, 2017 at 2:16 PM Subject: Howard Hinnant's tz Library (was Beginner's help request) To: Daniel Ford <dfnojunk(a)gmail.com> Yes, Howard's (exquisite in my opinion) library is specifically for C++, and is moving forward for inclusion in the ISO standard. (Indeed, a subgroup gave it unanimous consent just this morning.) >From http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0355r4.html: "The implementation has been ported to Windows, Linux, Android, macOS and iOS." I've BCCd Howard in case he has anything more to say about it (although I wouldn't be surprised if he already follows this list anyway). --Bill Seymour On Wed, Nov 8, 2017 at 12:38 AM, Daniel Ford <dfnojunk(a)gmail.com> wrote: > Oops, looks like I was mistaken. Howard's library appears to be not (specifically) for Arduino, but a C++ library for Windows (and maybe other) platforms. Maybe it will compile in the Arduino IDE, though I suspect it will be problematic, if possible at all. > > And I've so far found only one TZdb mirror that keeps a current copy of the data - very disappointing. It's a shame the whole TZdb scheme is so user-unfriendly. Quite discouraging. > > Regards, > Daniel > > > > -----Original Message----- > From: Daniel Ford [mailto:dfnojunk@gmail.com] > Sent: Saturday, November 04, 2017 7:03 PM > To: 'Time zone mailing list' > Subject: RE: [tz] Beginner's help request > > Woohoo! I've discovered (and downloaded) an Arduino library, written by Howard E. Hinnant: > > "This timezone library is a complete parser of the IANA timezone database. It provides for an easy way to access all of the data in this database, using the types from "date.h" and <chrono>. The IANA database also includes data on leap seconds, and this library provides utilities to compute with that information as well." > > All I need to find now are established TZdb mirrors that keep their copy up-to-date, so I don't overload the master TZdb with queries. Can anyone point me to any, please? > > Regards, > Daniel > --------------- > Daniel Ford (Gerroa, Australia)

2 1

Regarding Wikipedia entry
by Jens Tröger Nov. 8, 2017

Nov. 8, 2017

Hi, This is regarding the following table: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List I believe that the links in the first column CC are incorrect: they link to [[ISO_3166-1:CI|CI]] (link to the country) instead of [[ISO_3166-2:CI|CI]] (link to the timezone page) That applies to _all_ entries in the first column. Cheers, Jens -- Jens Tröger http://savage.light-speed.de/

9 12

Turkey reintroduces DST next year
by Kıvanç Yazan Nov. 8, 2017

Nov. 8, 2017

Turkey will roll hours back on 10/28/2018 04:00AM. This means going back to EU rule after two years of staying in UTC+3. Here's a link to news article: https://www.cnnturk.com/turkiye/son-dakika-yaz-saati-uygulamasi-sona-erecek Here's a link to official paper: http://www.resmigazete.gov.tr/eskiler/2017/10/20171028-5.pdf A proposed patch is attached, thanks! Sincerely, Kivanc Yazan

4 6

[PROPOSED] Cite "Eerie, Indiana was a few dimensions ahead of its time"
by Paul Eggert Nov. 8, 2017

Nov. 8, 2017

* tz-art.htm: Add URL. --- tz-art.htm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tz-art.htm b/tz-art.htm index 920d6e7..429dd63 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -144,6 +144,9 @@ hinges on whether or not Russia observes daylight saving time. "The Lost Hour", <em>Eerie, Indiana</em>, episode 10, NBC, 1991-12-01. Despite Indiana's then-lack of DST, Marshall changes his clock with unusual consequences. +See "<a +href="https://www.avclub.com/eerie-indiana-was-a-few-dimensions-ahead-of-its-time…"><em>Eerie, +Indiana</em> was a few dimensions ahead of its time</a>". </li> <li> "Time Tunnel", <em>The Adventures of Pete & Pete</em>, season 2, episode 5, -- 2.7.4

4 7

vlog on personal timezones
by Zefram Nov. 8, 2017

Nov. 8, 2017

Here's a vlog that may be of interest to people on this list. It's CGP Grey, whose "Daylight Saving Time Explained" video has previously been mentioned here, taking a three-day trip to Las Vegas (America/Los_Angeles) from Britain (Europe/London). Rather than live with the jet lag, he decides to keep his circadian rhythm on London time throughout the trip. As he comments, the 24-hour culture of Las Vegas is particularly amenable to maintaining a non-local timezone. https://www.youtube.com/watch?v=f-mHLBD64HM -zefram

2 1

[PROPOSED] Be more consistent about UT vs UTC
by Paul Eggert Nov. 8, 2017

Nov. 8, 2017

* NEWS, africa, asia, australasia, europe, localtime.c: * newctime.3, newtzset.3, northamerica, southamerica, theory.html: * tz-link.htm, tzselect.ksh, zdump.c, zic.8, zic.c: Be more consistent about using "UT" instead of "UTC" when talking about timestamps that might predate the introduction of UTC. * tzselect.ksh: Use AEST instead of the (obsolescent) abbreviation GST when talking about UT offsets. --- NEWS | 29 +++++++++++++++++------------ africa | 2 +- asia | 14 +++++++------- australasia | 4 ++-- europe | 6 +++--- localtime.c | 2 +- newctime.3 | 2 +- newtzset.3 | 20 ++++++++++---------- northamerica | 2 +- southamerica | 4 ++-- theory.html | 6 +++--- tz-link.htm | 14 +++++++------- tzselect.ksh | 5 +++-- zdump.c | 14 +++++++------- zic.8 | 4 ++-- zic.c | 2 +- 16 files changed, 68 insertions(+), 62 deletions(-) diff --git a/NEWS b/NEWS index de81afc..2254650 100644 --- a/NEWS +++ b/NEWS @@ -33,6 +33,11 @@ Unreleased, experimental changes that have snprintf and use pre-C99 compilers. (Problem reported by Jon Skeet.) + Changes to code + + Diagnostis and commentary are now more careful about + distinguishing UT from UTC. + Release 2017c - 2017-10-20 14:49:34 -0700 @@ -929,8 +934,8 @@ Release 2015f - 2015-08-10 18:06:56 -0700 (Thanks to Jon Skeet and Arthur David Olson.) Constraints on simultaneity are now documented. - The two characters '%z' in a zone format now stand for the UTC - offset, e.g., '-07' for seven hours behind UTC and '+0530' for + The two characters '%z' in a zone format now stand for the UT + offset, e.g., '-07' for seven hours behind UT and '+0530' for five hours and thirty minutes ahead. This better supports time zone abbreviations conforming to POSIX.1-2001 and later. @@ -1053,13 +1058,13 @@ Release 2015c - 2015-04-11 08:55:55 -0700 The spring 1988 transition was 1988-10-09, not 1988-10-02. The fall 1990 transition was 1990-03-11, not 1990-03-18. - Assume no UTC offset change for Pacific/Easter on 1890-01-01, + Assume no UT offset change for Pacific/Easter on 1890-01-01, and omit all transitions on Pacific/Easter from 1942 through 1946 since we have no data suggesting that they existed. One more zone has been turned into a link, as it differed from an existing zone only for older time stamps. As usual, - this change affects UTC offsets in pre-1970 time stamps only. + this change affects UT offsets in pre-1970 time stamps only. The zone's old contents have been moved to the 'backzone' file. The affected zone is America/Montreal. @@ -1089,7 +1094,7 @@ Release 2015b - 2015-03-19 23:28:11 -0700 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: America/Antigua, America/Cayman, Pacific/Midway, and Pacific/Saipan. @@ -1141,7 +1146,7 @@ Release 2015a - 2015-01-29 22:35:20 -0800 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Asia/Aden, Asia/Bahrain, Asia/Kuwait, and Asia/Muscat. @@ -1188,7 +1193,7 @@ Release 2014j - 2014-11-10 17:37:11 -0800 Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, - these changes affect UTC offsets in pre-1970 time stamps only. + these changes affect UT offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Addis_Ababa, Africa/Asmara, Africa/Dar_es_Salaam, Africa/Djibouti, Africa/Kampala, @@ -1278,7 +1283,7 @@ Release 2014h - 2014-09-25 18:59:03 -0700 Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, - these changes affect UTC offsets in pre-1970 timestamps only. + these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Blantyre, Africa/Bujumbura, Africa/Gaborone, Africa/Harare, Africa/Kigali, Africa/Lubumbashi, @@ -1363,7 +1368,7 @@ Release 2014g - 2014-08-28 12:31:23 -0700 Some more zones have been turned into links, when they differed from existing zones only for older timestamps. As usual, - these changes affect UTC offsets in pre-1970 timestamps only. + these changes affect UT offsets in pre-1970 timestamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: Africa/Bangui, Africa/Brazzaville, Africa/Douala, Africa/Kinshasa, Africa/Libreville, Africa/Luanda, @@ -1513,7 +1518,7 @@ Release 2014f - 2014-08-05 17:42:36 -0700 standard and daylight saving time the abbreviations are AEST and AEDT instead of the former EST for both; similarly, ACST/ACDT, ACWST/ACWDT, and AWST/AWDT are now used instead of the former CST, CWST, and WST. - This change does not affect UTC offsets, only time zone abbreviations. + This change does not affect UT offsets, only time zone abbreviations. (Thanks to Rich Tibbett and many others.) Asia/Novokuznetsk shifts from NOVT to KRAT (remaining on UT +07) @@ -1550,8 +1555,8 @@ Release 2014f - 2014-08-05 17:42:36 -0700 Treindl sent helpful translations of two papers by Guo Qingsheng.) Some zones have been turned into links, when they differed from existing - zones only for older UTC offsets where data entries were likely invented. - These changes affect UTC offsets in pre-1970 timestamps only. This is + zones only for older UT offsets where data entries were likely invented. + These changes affect UT offsets in pre-1970 timestamps only. This is similar to the change in release 2013e, except this time for western Africa. The affected zones are: Africa/Bamako, Africa/Banjul, Africa/Conakry, Africa/Dakar, Africa/Freetown, Africa/Lome, diff --git a/africa b/africa index 3a60bc2..be44580 100644 --- a/africa +++ b/africa @@ -425,7 +425,7 @@ Link Africa/Nairobi Indian/Mayotte # # The Nautical Almanac for the Year 1970, p 264, is the source for -0:44:30. # -# In 1972 Liberia was the last country to switch from a UTC offset +# In 1972 Liberia was the last country to switch from a UT offset # that was not a multiple of 15 or 20 minutes. The 1972 change was on # 1972-01-07, according to an entry dated 1972-01-04 on p 330 of: # Presidential Papers: First year of the administration of diff --git a/asia b/asia index ac39af3..91076fd 100644 --- a/asia +++ b/asia @@ -50,7 +50,7 @@ # 9:00 KST KDT Korea when at +09 # 9:30 ACST Australian Central Standard Time # Otherwise, these tables typically use numeric abbreviations like +03 -# and +0330 for integer hour and minute UTC offsets. Although earlier +# and +0330 for integer hour and minute UT offsets. Although earlier # editions invented alphabetic time zone abbreviations for every # offset, this did not reflect common practice. # @@ -647,17 +647,17 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # time", in which abolished the adoption of Western Standard Time in # western islands (listed above), which means the whole Japan # territory, including later occupations, adopt Japan Central Time -# (UTC+9). The adoption began on Oct 1, 1937. The original text can +# (UT+9). The adoption began on Oct 1, 1937. The original text can # be found on Wikisource: # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # -# That is, the time zone of Taipei switched to UTC+9 on Oct 1, 1937. +# That is, the time zone of Taipei switched to UT+9 on Oct 1, 1937. # From Yu-Cheng Chuang (2014-07-02): -# I've found more evidence about when the time zone was switched from UTC+9 -# back to UTC+8 after WW2. I believe it was on Sep 21, 1945. In a document +# I've found more evidence about when the time zone was switched from UT+9 +# back to UT+8 after WW2. I believe it was on Sep 21, 1945. In a document # during Japanese era [1] in which the officer told the staff to change time -# zone back to Western Standard Time (UTC+8) on Sep 21. And in another +# zone back to Western Standard Time (UT+8) on Sep 21. And in another # history page of National Cheng Kung University [2], on Sep 21 there is a # note "from today, switch back to Western Standard Time". From these two # materials, I believe that the time zone change happened on Sep 21. And @@ -1505,7 +1505,7 @@ Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # # ...the Showa Emperor announced Ordinance No. 529 of Showa Year 12 ... which # means the whole Japan territory, including later occupations, adopt Japan -# Central Time (UTC+9). The adoption began on Oct 1, 1937. +# Central Time (UT+9). The adoption began on Oct 1, 1937. # https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # Zone NAME GMTOFF RULES FORMAT [UNTIL] diff --git a/australasia b/australasia index 5f7c86d..9a968e4 100644 --- a/australasia +++ b/australasia @@ -683,8 +683,8 @@ Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara # From Steffen Thorsen (2012-07-25) # ... we double checked by calling hotels and offices based in Tokelau asking # about the time there, and they all told a time that agrees with UTC+13.... -# Shanks says UTC-10 from 1901 [but] ... there is a good chance the change -# actually was to UTC-11 back then. +# Shanks says UT-10 from 1901 [but] ... there is a good chance the change +# actually was to UT-11 back then. # # From Paul Eggert (2012-07-25) # A Google Books snippet of Appendix to the Journals of the House of diff --git a/europe b/europe index cf6d7e4..7bca59b 100644 --- a/europe +++ b/europe @@ -2772,9 +2772,9 @@ Zone Asia/Omsk 4:53:30 - LMT 1919 Nov 14 # # https://regnum.ru/news/society/1957270.html # has some historical data for Altai Krai: -# before 1957: west part on UTC+6, east on UTC+7 -# after 1957: UTC+7 -# since 1995: UTC+6 +# before 1957: west part on UT+6, east on UT+7 +# after 1957: UT+7 +# since 1995: UT+6 # http://barnaul.rusplt.ru/index/pochemu_altajskij_kraj_okazalsja_v_neprivych… # confirms that and provides more details including 1995-05-28 transition date. diff --git a/localtime.c b/localtime.c index 2e1d621..9b8266a 100644 --- a/localtime.c +++ b/localtime.c @@ -1982,7 +1982,7 @@ time2sub(struct tm *const tmp, && ((BIGGEST (INT_FAST32_MIN, LONG_MIN) + yourtm.TM_GMTOFF) <= mytm.TM_GMTOFF)))) { - /* MYTM matches YOURTM except with the wrong UTC offset. + /* MYTM matches YOURTM except with the wrong UT offset. YOURTM.TM_GMTOFF is plausible, so try it instead. It's OK if YOURTM.TM_GMTOFF contains uninitialized data, since the guess gets checked. */ diff --git a/newctime.3 b/newctime.3 index 8b89935..b376ae1 100644 --- a/newctime.3 +++ b/newctime.3 @@ -191,7 +191,7 @@ extra initial argument specifying the time zone to be used for conversion. If .B zone -is null, UTC is used; otherwise, +is null, UT is used; otherwise, .B zone should be have been allocated by .I tzalloc diff --git a/newtzset.3 b/newtzset.3 index c3e22dc..beee20a 100644 --- a/newtzset.3 +++ b/newtzset.3 @@ -61,7 +61,7 @@ If the implied call to .B tzalloc fails, .I tzset -falls back on UTC. +falls back on Universal Time (UT). .PP If .B TZ @@ -74,7 +74,7 @@ in the system time conversion information directory, is used. If .B TZ is the empty string, -Universal Time (UT) is used, with the abbreviation "UTC" +UT is used, with the abbreviation "UTC" and without leap second correction; please see .IR newctime (3) for more about UT, UTC, and leap seconds. If @@ -256,22 +256,22 @@ extensions to POSIX. .TP .B EST5 stands for US Eastern Standard -Time (EST), 5 hours behind UTC, without daylight saving. +Time (EST), 5 hours behind UT, without daylight saving. .TP .B FJT\*-12FJST,M11.1.0,M1.3.4/75 stands for Fiji Time (FJT) and Fiji Summer Time (FJST), 12 hours ahead -of UTC, springing forward on November's first Sunday at 02:00, and +of UT, springing forward on November's first Sunday at 02:00, and falling back on January's third Thursday at 75:00 (i.e., 03:00 on the first Sunday on or after January 18). .TP .B IST\*-2IDT,M3.4.4/26,M10.5.0 stands for Israel Standard Time (IST) and Israel Daylight Time (IDT), -2 hours ahead of UTC, springing forward on March's fourth +2 hours ahead of UT, springing forward on March's fourth Thursday at 26:00 (i.e., 02:00 on the first Friday on or after March 23), and falling back on October's last Sunday at 02:00. .TP .B WART4WARST,J1/0,J365/25 -stands for Western Argentina Summer Time (WARST), 3 hours behind UTC. +stands for Western Argentina Summer Time (WARST), 3 hours behind UT. There is a dummy fall-back transition on December 31 at 25:00 daylight saving time (i.e., 24:00 standard time, equivalent to January 1 at 00:00 standard time), and a simultaneous spring-forward transition on @@ -282,9 +282,9 @@ is a placeholder. .TP .B WGT3WGST,M3.5.0/\*-2,M10.5.0/\*-1 stands for Western Greenland Time (WGT) and Western Greenland Summer -Time (WGST), 3 hours behind UTC, where clocks follow the EU rules of -springing forward on March's last Sunday at 01:00 UTC (\-02:00 local -time) and falling back on October's last Sunday at 01:00 UTC +Time (WGST), 3 hours behind UT, where clocks follow the EU rules of +springing forward on March's last Sunday at 01:00 UT (\-02:00 local +time) and falling back on October's last Sunday at 01:00 UT (\-01:00 local time). .PP If no @@ -297,7 +297,7 @@ by the file .B posixrules in the system time conversion information directory are used, with the -standard and summer time offsets from UTC replaced by those specified by +standard and summer time offsets from UT replaced by those specified by the .I offset values in diff --git a/northamerica b/northamerica index e5d3eca..505300a 100644 --- a/northamerica +++ b/northamerica @@ -1896,7 +1896,7 @@ Zone America/Edmonton -7:33:52 - LMT 1906 Sep # manager of the Creston & District Museum. The article was written in May 2009. # http://www.ilovecreston.com/?p=articles&t=spec&ar=260 # According to the article, Creston has not changed its clocks since June 1918. -# i.e. Creston has been stuck on UTC-7 for 93 years. +# i.e. Creston has been stuck on UT-7 for 93 years. # Dawson Creek, on the other hand, changed its clocks as recently as April 1972. # Unfortunately the exact date for the time change in June 1918 remains diff --git a/southamerica b/southamerica index bbae226..e0b3265 100644 --- a/southamerica +++ b/southamerica @@ -25,7 +25,7 @@ # https://www.jstor.org/stable/1774359 # # These tables use numeric abbreviations like -03 and -0330 for -# integer hour and minute UTC offsets. Although earlier editions used +# integer hour and minute UT offsets. Although earlier editions used # alphabetic time zone abbreviations, these abbreviations were # invented and did not reflect common practice. @@ -1068,7 +1068,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # From Paul Eggert (2015-04-03): # Shanks & Pottenger says America/Santiago introduced standard time in -# 1890 and rounds its UTC offset to 70W40; guess that in practice this +# 1890 and rounds its UT offset to 70W40; guess that in practice this # was the same offset as in 1916-1919. It also says Pacific/Easter # standardized on 109W22 in 1890; assume this didn't change the clocks. # diff --git a/theory.html b/theory.html index 965135d..3e686a0 100644 --- a/theory.html +++ b/theory.html @@ -598,7 +598,7 @@ POSIX has the following properties and limitations. 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><UTC+10></code>'; this allows + 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> @@ -646,7 +646,7 @@ POSIX has the following properties and limitations. </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 UTC, + 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: @@ -678,7 +678,7 @@ POSIX has the following properties and limitations. 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 UTC" to get + 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.) diff --git a/tz-link.htm b/tz-link.htm index 835df40..2a8a486 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -432,7 +432,7 @@ It is freely available under the <abbr>LGPL</abbr>.</li> implementation of a binary file reader. It is freely available under the Apache License.</li> <li><a href="https://github.com/google/cctz">CCTZ</a> is a simple C++ -library that translates between <abbr>UTC</abbr> and civil time and +library that translates between <abbr>UT</abbr> and civil time and can read binary files. It is freely available under the Apache License.</li> <li><a href="http://bmsi.com/java/#TZ">ZoneInfo.java</a> @@ -660,7 +660,7 @@ world time zone boundaries distributed under the href="https://en.wikipedia.org/wiki/Territorial_waters">territorial waters</a> of any nation uses that nation's time. In international waters, time zone boundaries are meridians 15° apart, except that -<abbr>UTC</abbr>−12 and <abbr>UTC</abbr>+12 are each 7.5° +<abbr>UT</abbr>−12 and <abbr>UT</abbr>+12 are each 7.5° wide and are separated by the 180° meridian (not by the International Date Line, which is for land and territorial waters only). A captain can change ship's @@ -884,10 +884,10 @@ protocols.</li> Formats on the Web</a> surveys web- and Internet-oriented date and time formats.</li> <li>Alphabetic time zone abbreviations should not be used as unique -identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in +identifiers for <abbr>UT</abbr> offsets as they are ambiguous in practice. For example, in English-speaking North America -"<abbr>CST</abbr>" denotes 6 hours behind <abbr>UTC</abbr>, -but in China it denotes 8 hours ahead of <abbr>UTC</abbr>, +"<abbr>CST</abbr>" denotes 6 hours behind <abbr>UT</abbr>, +but in China it denotes 8 hours ahead of <abbr>UT</abbr>, and French-speaking North Americans prefer "<abbr title="Heure Normale du Centre">HNC</abbr>" to "<abbr>CST</abbr>". The <code><abbr>tz</abbr></code> @@ -895,7 +895,7 @@ database contains English abbreviations for many time stamps; unfortunately some of these abbreviations were merely the database maintainers' inventions, and are gradually being removed.</li> <li>Numeric time zone abbreviations typically count hours east of -<abbr>UTC</abbr>, e.g., +09 for Japan and +<abbr>UT</abbr>, e.g., +09 for Japan and −10 for Hawaii. However, the <abbr>POSIX</abbr> <code><abbr>TZ</abbr></code> environment variable uses the opposite convention. For example, one might use <code><abbr>TZ</abbr>="<abbr @@ -909,7 +909,7 @@ confusion, handle old time stamps better, and insulate you better from any future changes to the rules. One should never set <abbr>POSIX</abbr> <code><abbr>TZ</abbr></code> to a value like <code>"GMT-9"</code>, though, since this would incorrectly imply that -local time is nine hours ahead of <abbr>UTC</abbr> and the time zone +local time is nine hours ahead of <abbr>UT</abbr> and the time zone is called "<abbr>GMT</abbr>".</li> </ul> <h2 id="see-also">See also</h2> diff --git a/tzselect.ksh b/tzselect.ksh index 759ba5f..d71a95e 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -342,8 +342,9 @@ while while echo >&2 'Please enter the desired value' \ 'of the TZ environment variable.' - echo >&2 'For example, GST-10 is a zone named GST' \ - 'that is 10 hours ahead (east) of UTC.' + echo >&2 'For example, AEST-10 is a zone named AEST' \ + 'that is 10 hours ahead (east) of UT' + echo >&2 'and does not observe daylight saving time.' read TZ $AWK -v TZ="$TZ" 'BEGIN { tzname = "(<[[:alnum:]+-]{3,}>|[[:alpha:]]{3,})" diff --git a/zdump.c b/zdump.c index d4e6084..3cd4f42 100644 --- a/zdump.c +++ b/zdump.c @@ -265,7 +265,7 @@ tzfree(timezone_t env) } #endif /* ! USE_LOCALTIME_RZ */ -/* A UTC time zone, and its initializer. */ +/* A UT time zone, and its initializer. */ static timezone_t gmtz; static void gmtzinit(void) @@ -280,7 +280,7 @@ gmtzinit(void) } } -/* Convert *TP to UTC, storing the broken-down time into *TMP. +/* Convert *TP to UT, storing the broken-down time into *TMP. Return TMP if successful, NULL otherwise. This is like gmtime_r(TP, TMP), except typically faster if USE_LOCALTIME_RZ. */ static struct tm * @@ -730,8 +730,8 @@ adjusted_yday(struct tm const *a, struct tm const *b) } #endif -/* If A is the broken-down local time and B the broken-down UTC for - the same instant, return A's UTC offset in seconds, where positive +/* If A is the broken-down local time and B the broken-down UT for + the same instant, return A's UT offset in seconds, where positive offsets are east of Greenwich. On failure, return LONG_MIN. If T is nonnull, *T is the timestamp that corresponds to A; call @@ -847,10 +847,10 @@ format_local_time(char *buf, size_t size, struct tm const *tm) : my_snprintf(buf, size, "%02d", hh)); } -/* Store into BUF, of size SIZE, a formatted UTC offset for the +/* Store into BUF, of size SIZE, a formatted UT offset for the localtime *TM corresponding to time T. Use ISO 8601 format +HHMMSS, or -HHMMSS for timestamps west of Greenwich; use the - format -00 for unknown UTC offsets. If the hour needs more than + format -00 for unknown UT offsets. If the hour needs more than two digits to represent, extend the length of HH as needed. Otherwise, omit SS if SS is zero, and omit MM too if MM is also zero. @@ -925,7 +925,7 @@ format_quoted_string(char *buf, size_t size, char const *p) %f zone name %L local time as per format_local_time - %Q like "U\t%Z\tD" where U is the UTC offset as for format_utc_offset + %Q like "U\t%Z\tD" where U is the UT offset as for format_utc_offset and D is the isdst flag; except omit D if it is zero, omit %Z if it equals U, quote and escape %Z if it contains nonalphabetics, and omit any trailing tabs. */ diff --git a/zic.8 b/zic.8 index ab95b08..43ef2ce 100644 --- a/zic.8 +++ b/zic.8 @@ -366,7 +366,7 @@ is used to show where the of the time zone abbreviation goes. Alternately, a format can use the pair of characters .B %z -to stand for the UTC offset in the form +to stand for the UT offset in the form .RI \(+- hh , .RI \(+- hhmm , or @@ -376,7 +376,7 @@ using the shortest form that does not lose information, where .IR mm , and .I ss -are the hours, minutes, and seconds east (+) or west (\(mi) of UTC. +are the hours, minutes, and seconds east (+) or west (\(mi) of UT. Alternately, a slash (/) separates standard and daylight abbreviations. diff --git a/zic.c b/zic.c index a3d7383..82e653d 100644 --- a/zic.c +++ b/zic.c @@ -2055,7 +2055,7 @@ abbroffset(char *buf, zic_t offset) minutes = offset % MINSPERHOUR; offset /= MINSPERHOUR; if (100 <= offset) { - error(_("%%z UTC offset magnitude exceeds 99:59:59")); + error(_("%%z UT offset magnitude exceeds 99:59:59")); return "%z"; } else { char *p = buf; -- 2.7.4

7 11

I'm sure everyone has seen this... but...
by merlyn＠stonehenge.com Nov. 8, 2017

Nov. 8, 2017

https://www.youtube.com/watch?v=-5wpm-gesOY -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/Dart consulting, Technical writing, Comedy, etc. etc. Still trying to think of something clever for the fourth line of this .sig

2 1

Apple watch crashes if daylight time ends
by Steve Allen Nov. 6, 2017

Nov. 6, 2017

https://www.reddit.com/r/AppleWatch/comments/7aqiw1/series_3_crashes_when_a… Reports that Apple watchOS 4.1 crashes if asked about today's weather (not tomorrow's, etc.) in a zone which is about to end daylight time. -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

3 2

Massachusetts time zone report
by Steve Allen Nov. 4, 2017

Nov. 4, 2017

Massachusetts has approved a 47 page report on its time zone http://www.eileendonoghue.org/special-commission-approves-time-zone-report/ it cautiously recommends moving to permanent Atlantic standard time. -- Steve Allen <sla(a)ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m

3 3

Article proposes end of DST, adds interesting historic reference
by Steve Jones Nov. 4, 2017

Nov. 4, 2017

Interesting/amusing article on Fox News this morning (using the wayback machine link to reduce the oppressive spam: https://web.archive.org/web/20171104061246/http://www.foxnew s.com/opinion/2017/11/04/its-time-for-daylight-saving-time- to-fall-back-forever.html The best part was a link to an old gizmodo article containing a well-researched historical reference to Ben Franklin's original proposal for a DST-like policy: https://gizmodo.com/ben-franklins-daylight-saving-time-proposal-was-writte- 1456363759 Further clicking led me to the full letter from Ben: http://www.webexhibits.org/daylightsaving/franklin3.html which I think is tz-art worthy. Steve Jones [image: Emacs!]

2 1

Re: [tz] [IANA #985615] Sudan Time Zone change
by Mohammed Elsir Osman Alebeid Nov. 3, 2017

Nov. 3, 2017

Dear Eggert, This is Mohammed Elsir from Zain, the first mobile operator in Sudan. Actually our mobile network sends the correct time zone which is GMT+2 as seen in below trace. [cid:image015.png@01D353DB.A197A6D0] The thing is that some devices such as most of feature/legacy/old phones accept the sent time zone and change time correctly. But some Android device such as Samsung, Huawei, Lenovo and part of HTC reject the provided time zone and display the time zone based on lookup table inside the handset. Below is an example from Lenovo P2. [cid:image016.png@01D353DB.A197A6D0] Some Handset manufactures such as apple sent messages over the internet asking for handset restart to get the new time zone. Below is an examples. [cid:image003.png@01D353DD.1DA00320] I do appreciate your kind support to contact Android handset manufactures such as Samsung, Huawei and Lenovo asking them about 1. Why their handsets reject the network provided time zone. 2. How can they solve this issue? Should you need further discussion I am available on Skype @ mohammed_elsir_64 or WhatsApp @ +249912311500. Just let me know the appropriate time for you to discuss further. Thanks in advance for your kind support. Best Regards, Mohammed Elsir M.Sc., PMP,ITIL-SO From: Ahmed Ali Ahmed Ali Sent: Wednesday, November 01, 2017 8:18 PM To: Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>; Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com>; Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com> Cc: Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com>; Nizar Musa <Nizar.Musa(a)sd.zain.com>; Ali Boosh <Ali.Boosh(a)sd.zain.com>; Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com> Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears, Please check the below feedback from IANA Thanks, Sent from Samsung Mobile -------- Original message -------- From: ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> Date:11/01/2017 20:19 (GMT+03:00) To: Faisal El Muftah , Ahmed Ali Ahmed Ali , Regulatory , Hiba Abbas Yousif Eltigani , Mohamed Gaafar Ibrahim Bashir Corporate Services - MTN - Sudan , Nafisa Mahmoud Karamalla Corporate Services - MTN - Sudan , Mohammed Abdelraheem Abdelmagid Elkhalifa , Munir Taha Elkabashi Hassan Elfaki Cc: abdelhafiz , Afaf Nijomi , yahia , mohamed elhaj Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears Please find below email from IANA for your kind revision to find the way out; we will also discuss the proposal of Sudan Embassy regards Ahmed Atyya ----- Forwarded Message ----- From: "Paul Eggert" <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>> To: "ahmed atyya" <ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd>> Cc: "yahia" <yahia(a)ntc.gov.sd<mailto:yahia@ntc.gov.sd>>, "Matt Johnson" <mj1856(a)hotmail.com<mailto:mj1856@hotmail.com>>, "Time Zone Mailing List" <tz(a)iana.org<mailto:tz@iana.org>>, "itisalat" <itisalat(a)ntc.gov.sd<mailto:itisalat@ntc.gov.sd>>, "abdin" <abdin(a)ntc.gov.sd<mailto:abdin@ntc.gov.sd>>, "nadir" <nadir(a)ntc.gov.sd<mailto:nadir@ntc.gov.sd>>, "abdelhafiz" <abdelhafiz(a)ntc.gov.sd<mailto:abdelhafiz@ntc.gov.sd>> Sent: Wednesday, November 1, 2017 7:57:00 PM Subject: Re: [tz] [IANA #985615] Sudan Time Zone change On 11/01/2017 01:35 AM, ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> wrote: > With respect to the topic, please be updated that the change was applied successfully, Apple > handsets did the update automatically but Android handsets didn’t. In what sense didn't they change? My Android phone's time zone menu has entries for Cairo, Harare, and Nairobi, but not for Khartoum. If it is a matter of the user's time zone settings, users need to change from (say) Nairobi time to Cairo time. On the other hand, if it is a matter of the time zone supplied from the cellular service company, then this is something for your local cell company to address. > We kindly request to communicate with Google in order to update Android OS with the changes > for the handsets take the time automatically. As I understand it, Google engineers monitor this mailing list and so already know about the time zone change. There is a gap between the time that Google releases software updates, and the time that phones actually change. For example, even though I have a Google Nexus 6P phone and live in the United States, my phone is well behind Google's release schedule: it upgraded over-the-air to Android 8.0 Oreo only last night, even though Oreo was released on August 21 *. Other manufacturers' Android phones are even slower to update. This underscores the importance of governments announcing time zone changes well in advance: we currently recommend one years' advance notice. When other countries have run into similar problems, they've had some luck by contacting the U.S. State Department and asking for its help in adjusting the priorities of commercial providers. I suggest that you contact the U.S. Deputy Chief of Mission in Sudan and ask for his advice for how to proceed. See: https://sd.usembassy.gov/our-relationship/dcm/ https://sd.usembassy.gov/embassy/khartoum/offices-departments/public-affair… From what you tell me, though, the problem is likely to involve the protocols used by your local cellular service providers (that is, the problem may not be in Android at all), so they'll need to be in contact with their suppliers too. [cid:image001.png@01D353B6.A6960840] Ahmed Ahmedali Market Power & Competition Advance Specialist Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : +249912398071 Email : Ahmed.Ahmedali(a)sd.zain.com<mailto:Ahmed.Ahmedali@sd.zain.com> Web : www.zain.com<http://www.zain.com> [cid:image005.jpg@01D353DD.1DA00320]<https://twitter.com/ZainSudan> [cid:image007.jpg@01D353DD.1DA00320] <https://facebook.com/ZainSudan/?fref=ts> [cid:image009.jpg@01D353DD.1DA00320] <https://plus.google.com/110542740934974723351> [cid:image011.jpg@01D353DD.1DA00320] <https://instagram.com/zainsudan/> [cid:image013.jpg@01D353DD.1DA00320] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image023.png@01D353DD.1DA00320] <https://youtube.com/user/ZainSudanTV> [cid:image014.png@01D353B6.A6960840] [cid:image2acf2f.BMP@a4b5ec2d.4c95cc79] Mohammed Elsir Osman CT Infrastructure Operation Team Leader Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : ++249912311500 Office : +24990001-3256 Email : Mohammed.ElsirOsman(a)sd.zain.com Web : www.zain.com [cid:image1d8d7d.PNG@e9fa88a4.43aeded8]<https://twitter.com/ZainSudan> [cid:imaged5af34.PNG@146f7ddf.4e95af19] <https://facebook.com/ZainSudan/?fref=ts> [cid:image95f784.PNG@eb17dd26.4eb485d3] <https://plus.google.com/110542740934974723351> [cid:imageb1c854.JPG@2f1af4fa.4680f52e] <https://instagram.com/zainsudan/> [cid:imagead7fe1.PNG@0e87976d.42b9ff22] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image108d42.PNG@d8c0b630.439783e1] <https://youtube.com/user/ZainSudanTV> [cid:image400fba.PNG@9f5f39e1.45ab1906]

4 3

Regarding changes of time format the Philippines
by Arati Nov. 3, 2017

Nov. 3, 2017

Hi , We are using tzdb for all our customers. With latest update of tzdb to 2017a, one of the customer came back with issue in time format display in logs. The timezone for this Customer is Asia/Manila i.e. Philippines. Before use on 2017a tzdb , the time displayed is as follows 2017-10-31 16:47:33.930 +0800 After using 2017a tzdb time displayed as 2017-10-31 08:48:38.056 +0000 We observed the same issue using perl DateTime module too. We could see that the time format for this zone is changed from PH%sT to +08/+09. This change is there only in asia file.(Note reverting back this change and recompiling tzdb resolves the issue) We are looking for a solution for this. We are not clear whether some dependent library needs to be upgraded , or it is a bug in tzdb. Kindly address the query and help to resolve the issue. Thanks & Regards, Arati =========================================================== Learn how to protect users, data, and applications with security engineered for the public cloud by Barracuda. http://barracuda.com DISCLAIMER: This e-mail and any attachments to it contain confidential and proprietary material of Barracuda, its affiliates or agents, and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. ===========================================================

4 7

Re: [tz] [IANA #985615] Sudan Time Zone change
by Zhouyuxiang Nov. 3, 2017

Nov. 3, 2017

Dears, I'm not that sure. But I guess this is same problem as mine([time zone problem about 2017c] (Zefram)). This just happen in Android system now. Because the tzcode2017c.tar.gz has one error. external\icu\tools\update-tzdata.py Android use this script to update the tz data from IANA via internet. But africa file and backzone file have a duplicated data that made the update script error: # South Sudan Zone Africa/Juba 2:06:24 - LMT 1931 2:00 Sudan CA%sT 2000 Jan 15 12:00 3:00 - EAT So android device could not update the time zone data normally. I deleted one in backzone, then it worked in local. And Zefram told me "No one noticed in advance of release because few people use 'backzone'". So I infer that the old phone and ios system will not use backzone data, so they could update normally. I think you have two way to solve this problem. 1.Wait IANA modify the "backzone" data, so the internet updating could work. 2.Let Android device Manufacturers do this update themselves: a. Delete the duplicated data as I did. b. Modify the update-tzdata.py to update time zone data without internet. ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Nov 2017 11:19:09 +0000 From: Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com> To: "eggert(a)cs.ucla.edu" <eggert(a)cs.ucla.edu> Cc: Ali Boosh <Ali.Boosh(a)sd.zain.com>, "itisalat(a)ntc.gov.sd" <itisalat(a)ntc.gov.sd>, "abdin(a)ntc.gov.sd" <abdin(a)ntc.gov.sd>, "nadir(a)ntc.gov.sd" <nadir(a)ntc.gov.sd>, "tz(a)iana.org" <tz(a)iana.org>, Nizar Musa <Nizar.Musa(a)sd.zain.com>, "abdelhafiz(a)ntc.gov.sd" <abdelhafiz(a)ntc.gov.sd>, Ahmed Ali Ahmed Ali <Ahmed.Ahmedali(a)sd.zain.com>, "yahia(a)ntc.gov.sd" <yahia(a)ntc.gov.sd>, Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com>, Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>, Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com>, Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com> Subject: Re: [tz] [IANA #985615] Sudan Time Zone change Message-ID: <BE1CCE5C566B134083665B1FF5684AE58BCDD6E4(a)sr-ark-mbxb.sd.zain.com> Content-Type: text/plain; charset="utf-8" Dear Eggert, This is Mohammed Elsir from Zain, the first mobile operator in Sudan. Actually our mobile network sends the correct time zone which is GMT+2 as seen in below trace. [cid:image015.png@01D353DB.A197A6D0] The thing is that some devices such as most of feature/legacy/old phones accept the sent time zone and change time correctly. But some Android device such as Samsung, Huawei, Lenovo and part of HTC reject the provided time zone and display the time zone based on lookup table inside the handset. Below is an example from Lenovo P2. [cid:image016.png@01D353DB.A197A6D0] Some Handset manufactures such as apple sent messages over the internet asking for handset restart to get the new time zone. Below is an examples. [cid:image003.png@01D353DD.1DA00320] I do appreciate your kind support to contact Android handset manufactures such as Samsung, Huawei and Lenovo asking them about 1. Why their handsets reject the network provided time zone. 2. How can they solve this issue? Should you need further discussion I am available on Skype @ mohammed_elsir_64 or WhatsApp @ +249912311500. Just let me know the appropriate time for you to discuss further. Thanks in advance for your kind support. Best Regards, Mohammed Elsir M.Sc., PMP,ITIL-SO From: Ahmed Ali Ahmed Ali Sent: Wednesday, November 01, 2017 8:18 PM To: Ahmed Ibrahim Ahmed Abdelkareem <Ahmed.AbdElkareem(a)sd.zain.com>; Mohammed Elsir Osman Alebeid <Mohammed.ElsirOsman(a)sd.zain.com>; Mugahed Bakri Mohammed Alhag <Mugahed.Bakri(a)sd.zain.com> Cc: Faisal El Muftah <Faisal.Nourelhuda(a)sd.zain.com>; Nizar Musa <Nizar.Musa(a)sd.zain.com>; Ali Boosh <Ali.Boosh(a)sd.zain.com>; Badr Eldin Abdalla Mohamed Nour <Badr.Nour(a)sd.zain.com> Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears, Please check the below feedback from IANA Thanks, Sent from Samsung Mobile -------- Original message -------- From: ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> Date:11/01/2017 20:19 (GMT+03:00) To: Faisal El Muftah , Ahmed Ali Ahmed Ali , Regulatory , Hiba Abbas Yousif Eltigani , Mohamed Gaafar Ibrahim Bashir Corporate Services - MTN - Sudan , Nafisa Mahmoud Karamalla Corporate Services - MTN - Sudan , Mohammed Abdelraheem Abdelmagid Elkhalifa , Munir Taha Elkabashi Hassan Elfaki Cc: abdelhafiz , Afaf Nijomi , yahia , mohamed elhaj Subject: Fwd: [tz] [IANA #985615] Sudan Time Zone change Dears Please find below email from IANA for your kind revision to find the way out; we will also discuss the proposal of Sudan Embassy regards Ahmed Atyya ----- Forwarded Message ----- From: "Paul Eggert" <eggert(a)cs.ucla.edu<mailto:eggert@cs.ucla.edu>> To: "ahmed atyya" <ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd>> Cc: "yahia" <yahia(a)ntc.gov.sd<mailto:yahia@ntc.gov.sd>>, "Matt Johnson" <mj1856(a)hotmail.com<mailto:mj1856@hotmail.com>>, "Time Zone Mailing List" <tz(a)iana.org<mailto:tz@iana.org>>, "itisalat" <itisalat(a)ntc.gov.sd<mailto:itisalat@ntc.gov.sd>>, "abdin" <abdin(a)ntc.gov.sd<mailto:abdin@ntc.gov.sd>>, "nadir" <nadir(a)ntc.gov.sd<mailto:nadir@ntc.gov.sd>>, "abdelhafiz" <abdelhafiz(a)ntc.gov.sd<mailto:abdelhafiz@ntc.gov.sd>> Sent: Wednesday, November 1, 2017 7:57:00 PM Subject: Re: [tz] [IANA #985615] Sudan Time Zone change On 11/01/2017 01:35 AM, ahmed.atyya(a)ntc.gov.sd<mailto:ahmed.atyya@ntc.gov.sd> wrote: > With respect to the topic, please be updated that the change was > applied successfully, Apple handsets did the update automatically but Android handsets didn?t. In what sense didn't they change? My Android phone's time zone menu has entries for Cairo, Harare, and Nairobi, but not for Khartoum. If it is a matter of the user's time zone settings, users need to change from (say) Nairobi time to Cairo time. On the other hand, if it is a matter of the time zone supplied from the cellular service company, then this is something for your local cell company to address. > We kindly request to communicate with Google in order to update > Android OS with the changes for the handsets take the time automatically. As I understand it, Google engineers monitor this mailing list and so already know about the time zone change. There is a gap between the time that Google releases software updates, and the time that phones actually change. For example, even though I have a Google Nexus 6P phone and live in the United States, my phone is well behind Google's release schedule: it upgraded over-the-air to Android 8.0 Oreo only last night, even though Oreo was released on August 21 *. Other manufacturers' Android phones are even slower to update. This underscores the importance of governments announcing time zone changes well in advance: we currently recommend one years' advance notice. When other countries have run into similar problems, they've had some luck by contacting the U.S. State Department and asking for its help in adjusting the priorities of commercial providers. I suggest that you contact the U.S. Deputy Chief of Mission in Sudan and ask for his advice for how to proceed. See: https://sd.usembassy.gov/our-relationship/dcm/ https://sd.usembassy.gov/embassy/khartoum/offices-departments/public-affair… From what you tell me, though, the problem is likely to involve the protocols used by your local cellular service providers (that is, the problem may not be in Android at all), so they'll need to be in contact with their suppliers too. [cid:image001.png@01D353B6.A6960840] Ahmed Ahmedali Market Power & Competition Advance Specialist Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : +249912398071 Email : Ahmed.Ahmedali(a)sd.zain.com<mailto:Ahmed.Ahmedali@sd.zain.com> Web : www.zain.com<http://www.zain.com> [cid:image005.jpg@01D353DD.1DA00320]<https://twitter.com/ZainSudan> [cid:image007.jpg@01D353DD.1DA00320] <https://facebook.com/ZainSudan/?fref=ts> [cid:image009.jpg@01D353DD.1DA00320] <https://plus.google.com/110542740934974723351> [cid:image011.jpg@01D353DD.1DA00320] <https://instagram.com/zainsudan/> [cid:image013.jpg@01D353DD.1DA00320] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image023.png@01D353DD.1DA00320] <https://youtube.com/user/ZainSudanTV> [cid:image014.png@01D353B6.A6960840] [cid:image2acf2f.BMP@a4b5ec2d.4c95cc79] Mohammed Elsir Osman CT Infrastructure Operation Team Leader Zain SD Al Mogran, Zain Building Al Ghaba Street P.O Box: 13588 Khartoum Sudan Mobile : ++249912311500 Office : +24990001-3256 Email : Mohammed.ElsirOsman(a)sd.zain.com Web : www.zain.com [cid:image1d8d7d.PNG@e9fa88a4.43aeded8]<https://twitter.com/ZainSudan> [cid:imaged5af34.PNG@146f7ddf.4e95af19] <https://facebook.com/ZainSudan/?fref=ts> [cid:image95f784.PNG@eb17dd26.4eb485d3] <https://plus.google.com/110542740934974723351> [cid:imageb1c854.JPG@2f1af4fa.4680f52e] <https://instagram.com/zainsudan/> [cid:imagead7fe1.PNG@0e87976d.42b9ff22] <https://linkedin.com/company/3224878?trk=tyah&trkInfo=clickedVertical%3Acom…> [cid:image108d42.PNG@d8c0b630.439783e1] <https://youtube.com/user/ZainSudanTV> [cid:image400fba.PNG@9f5f39e1.45ab1906]

1 0

Ulaanbaatar Time Zone Correction
by Brian M. Vibert Nov. 2, 2017

Nov. 2, 2017

Hello, Looking into the asia file, I see a listing comment for # From Ganbold Tsagaankhuu (2017-02-09): # Mongolian Government meeting has concluded today to cancel daylight # saving time adoption in Mongolia. Source: http://zasag.mn/news/view/16192 Which is correct, however, it appears that the change has not been propagated to the Zone as seen here # Ulaanbaatar, a.k.a. Ulan Bataar, Ulan Bator, Urga Zone Asia/Ulaanbaatar 7:07:32 - LMT 1905 Aug 7:00 - +07 1978 8:00 Mongol +08/+09 It should just be 8:00 across the board at all times. -- *Brian M. Vibert | L3 Technical Support Engineer* *e: **bvibert(a)instructure.com <bvibert(a)instructure.com>* *c: 801.913.4236| **instructure.com* <http://www.instructure.com/> <https://www.instructure.com/>

2 1

[time zone problem about 2017c]
by Zhouyuxiang Nov. 2, 2017

Nov. 2, 2017

Dear all: Hello. I'm a user of time zone data in IANA. Lately I found a problem when I used it in Android O system. external\icu\tools\update-tzdata.py I used the tool in the below path to deal with the data tzcode2017c.tar.gz<https://www.iana.org/time-zones/repository/releases/tzcode2017c.tar.gz>. Then the error occurred. Finally I found the way to solve it. It seemed that africa file and backzone file have a duplicated data: # South Sudan Zone Africa/Juba 2:06:24 - LMT 1931 2:00 Sudan CA%sT 2000 Jan 15 12:00 3:00 - EAT I deleted one in backzone, then it worked. Now I'm wondering if this is mistake. And what are the influences?

2 1

Data loss on FTP Server
by Nathan Winters Nov. 1, 2017

Nov. 1, 2017

Hello, I've been using the FTP server to access Timezone Info for a while now and it seems the directory I was using (/tz/data) has lost all of its files. Additionally, I'm unable to view the data for the most recent release ( tzdb-2017c/ <ftp://ftp.iana.org/tz/tzdb-2017c/>). Has anything changed recently? Thanks, Nate

13 24

[PROPOSED] Guess that Tonga has canceled DST
by Paul Eggert Nov. 1, 2017

Nov. 1, 2017

(Thanks to David Wade.) * NEWS, australasia (Tonga): Guess DST has been canceled. --- NEWS | 6 ++++++ australasia | 14 ++++++++++++-- 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 4e98ef7..28b46b8 100644 --- a/NEWS +++ b/NEWS @@ -7,6 +7,7 @@ Unreleased, experimental changes Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. + Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. @@ -28,6 +29,11 @@ Unreleased, experimental changes Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. + Tonga has likely ended its experiment with DST, and will not + adjust its clocks on 2017-11-05. Although Tonga has not announced + whether it will continue to observe DST, the IATA is assuming that + it will not. (Thanks to David Wade.) + Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) diff --git a/australasia b/australasia index ae2cd72..5f7c86d 100644 --- a/australasia +++ b/australasia @@ -704,8 +704,8 @@ Rule Tonga 1999 only - Oct 7 2:00s 1:00 S Rule Tonga 2000 only - Mar 19 2:00s 0 - Rule Tonga 2000 2001 - Nov Sun>=1 2:00 1:00 S Rule Tonga 2001 2002 - Jan lastSun 2:00 0 - -Rule Tonga 2016 max - Nov Sun>=1 2:00 1:00 S -Rule Tonga 2017 max - Jan Sun>=15 3:00 0 - +Rule Tonga 2016 only - Nov Sun>=1 2:00 1:00 S +Rule Tonga 2017 only - Jan Sun>=15 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tongatapu 12:19:20 - LMT 1901 12:20 - +1220 1941 @@ -1626,6 +1626,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # day in 2011. Assume also that the Samoas follow the US and New # Zealand's "ST"/"DT" style of daylight-saving abbreviations. + # Tonga # From Paul Eggert (1996-01-22): @@ -1720,6 +1721,15 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # Assume Tonga will observe DST from the first Sunday in November at 02:00 # through the third Sunday in January at 03:00, like Fiji, for now. +# From David Wade (2017-10-18): +# In August government was disolved by the King. The current prime minister +# continued in office in care taker mode. It is easy to see that few +# decisions will be made until elections 16th November. +# +# From Paul Eggert (2017-10-18): +# For now, guess that DST is discontinued. That's what the IATA is guessing. + + # Wake # From Vernice Anderson, Personal Secretary to Philip Jessup, -- 2.13.6

4 3

The misaligned borders of South Australia
by Gilmore Davidson Nov. 1, 2017

Nov. 1, 2017

An interesting piece of trivia/history popped up in the news today. The borders of South Australia (and hence the boundaries of some Australian time zones) look like straight lines on most maps, but have some kinks in them. Most notably for this mailing list, part of the eastern border is misaligned due to an incorrect timekeeping reference from GMT. http://www.abc.net.au/news/2017-11-01/why-south-australias-borders-are-anyt… <http://www.abc.net.au/news/2017-11-01/why-south-australias-borders-are-anyt…> > It was meant to run along the 141st meridian line of longitude. > But longitude is measured with time references to Greenwich Mean Time — and watches were not that great in the 1800s. > The result was a 3.6-kilometre gap where the borders were meant to have met. > > "Fundamentally the difference came down to a discrepancy that the nation had at the time," Mr Burdett said. > "The longitude that had been determined for Fort Macquarie [Australia's reference point] was out by two minutes. > "Hence ours was out by two minutes and the discrepancy ended up in that border." Cheers, Gil

1 0

Turks & Caicos to resume DST; details unclear
by Paul Eggert Oct. 31, 2017

Oct. 31, 2017

According to an article published in the Bahamas website Magnetic Media, the cabinet of Turks & Caicos decided on Thursday to resume the practice of daylight saving time starting in 2018. The article does not give enough details to update the database (it confuses summer with winter time, among other things). My guess is that Turks & Caicos will revert to its pre-2015 practice of staying in sync with New York, which means that tzdb's predictions for its UTC offsets will become wrong in November 2018, and the abbreviations and tm_isdst flag will become wrong some time between March and November 2018 (although the article implies April, this could well be an error). When the cabinet and/or the Turks & Caicos Weekly News get around to publishing the details of the decision, we should be able to update tzdb to reflect this change with some accuracy. Gordon Z. PDM to reinstate Daylight Savings Time. Magnetic Media 2017-07-20. http://magneticmediatv.com/2017/07/pdm-to-reinstate-daylight-savings-time/ ("PDM" is the People's Democratic Movement.)

4 4

A bill to move Polish time (Europe/Warsaw) permanently to UTC+2
by Sergiusz Wolicki Oct. 29, 2017

Oct. 29, 2017

An internal committee of the Polish parlament (Sejm) has unanimously voted in favor of a bill to stop DST changes and to introduce permanent Central European Summer Time (GMT+2). The law would come in force in autumn 2018. The bill still needs to be voted by Sejm, then Senat (upper house), and then must be signed by the President, so it is far from being the actual law. The bill is not considered conflicting with EU regulations, which only require DST changes to be synchronized across EU but do not actually mandate the use of DST. Reference in Polish: http://wiadomosci.gazeta.pl/wiadomosci/7,114883,22499682,nie-bedziemy-przes… The website <http://sejm.gov.pl/Sejm8.nsf/PrzebiegProc.xsp?nr=1852> of the Sejm has not yet been updated with the result of the voting. Thanks, Sergiusz

7 7

Bug in Latest Release of TZ Database ie 2017c
by Sahil Sethi Oct. 28, 2017

Oct. 28, 2017

Hi Team As decided by Sudan Government to change time zone from GMT+3 to GMT+2, we were testing TZ update from 2017b --> 2017c and we encountered the following error : Linux TZ version : 2017b --> 2017c ... Failed | "backzone", line 149: duplicate zone name Africa/Juba (file "africa", line 1107) | "backzone", line 150: input line of unknown type | "backzone", line 151: input line of unknown type On little debugging we found that in former version there was a link between Africa/Khartoum & Africa/Juba zones in africa file and Africa/Juba zone entry existed in "backzone" file but in later version same zone entry of Africa/Juba exists in both files ie "africa" & "backzone", causing trouble. Looking forward for an acknowledgement. Regards Sahil Sethi Sr Software Engineer GlogbalLogic, India

2 1

2017c zdump outputs "No such file or directory"
by 大山俊成 Oct. 27, 2017

Oct. 27, 2017

Hi, Previously, I tryed 2017b like the following. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles It works good . Now I tryed 2017c as the same way. make TOPDIR=$HOME/tzdir install $HOME/tzdir/etc/zdump -v America/Los_Angeles But , zdump outputs "America/Los_Angeles: No such file or Directory" Something wrong with me?

3 7

why do Africa/Juba and backzone/Africa/Juba differ?
by Michael Deckers Oct. 24, 2017

Oct. 24, 2017

Puzzles me in 2017c: Africa/Juba and backzone/Africa/Juba differ in their astronomical longitudes: in zone1970.tab: SS +0451+03137 Africa/Juba in zone.tab: SS +0451+03136 Africa/Juba and (correspondingly) in the local mean time used before the switch to zone time in 1931: in africa: Zone Africa/Juba 2:06:28 - LMT 1931 in backzone: Zone Africa/Juba 2:06:24 - LMT 1931 Why? And do we need the backzone entry at all? Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Anyone else having snprintf issues with 2017c?
by Jon Skeet Oct. 24, 2017

Oct. 24, 2017

The tzvalidate <https://github.com/nodatime/tzvalidate> travis build is failing, with both clang and gcc, with this error: zdump.c:803:1: error: static declaration of ‘snprintf’ follows non-static declaration snprintf(char *s, size_t size, char const *format, ...) ^ make: *** [zdump.o] Error 1 It's building fine for me locally, so I'm not quite sure what's wrong. We're currently building on trusty - I may try another distro... The snprintf changes were introduced on June 13th <https://github.com/eggert/tz/commit/399180580f65bcad63cf996997068366cadaf53…>. It's been too long since I've done a lot of C to easily work out what's going on. I'll investigate further myself tomorrow, but I thought I'd just see if anyone else had seen this before then. Jon

7 9

installargs loses part of backward
by Zefram Oct. 23, 2017

Oct. 23, 2017

New in the 2017c release, there's a bug in how INSTALLARGS in the Makefile passes the BACKWARD variable down to an inferior make process. Because the definition of INSTALLARGS doesn't put quotes around the value part of BACKWARD, and because BACKWARD is actually (by default) a space-separated list of two files, the inferior make only gets the first file in its BACKWARD value, treating the second file as something to ensure is up to date (which of course it already is). So the inferior make omits one of the BACKWARD files (pacificnew) from whatever it does. The practical effect of this is that when building the binary zone files by, for example, "make posix_only", without having previously done "make tzdata.zi", the US/Pacific-New link is omitted. It's missing from the directory of binary outputs, and missing from the tzdata.zi file that is created as a side effect of building them (thus affecting anything that later tries to use tzdata.zi). That's the only zone name affected, because it's the only zone name defined in the lost source file. If "make tzdata.zi" is done first then that will create a correct tzdata.zi, and subsequent building of the binary zone files will then include the link. This was spotted by my automation, which sanity checks the directory of generated binary zone files against a list of zone names that it extracts from the source files. I think this a sensible check, and that it ought to pass. The fix is that the definition of INSTALLARGS should quote $(BACKWARD), the same way it quotes $(PACKRATDATA). Or perhaps it should not set BACKWARD at all, just like it doesn't set YDATA et al. (But perhaps it should *also* set YDATA et al.) -zefram

3 4

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

Oct. 23, 2017

The 2017c release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Briefly: Northern Cyprus switches from +03 to +02/+03 on 2017-10-29. Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. Tonga likely switches from +13/+14 to +13 on 2017-11-05. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. A new file tzdata.zi now holds a small text copy of all data. The zic input format has been regularized slightly. Changes to future time stamps Northern Cyprus has decided to resume EU rules starting 2017-10-29, thus reinstituting winter time. Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted. (Thanks to Dominic Fok.) Adjust future predictions accordingly. Namibia will switch from +01 with DST to +02 all year on 2017-09-03 at 02:00. This affects UT offsets starting 2018-04-01 at 02:00. (Thanks to Steffen Thorsen.) Sudan will switch from +03 to +02 on 2017-11-01. (Thanks to Ahmed Atyya and Yahia Abdalla.) South Sudan is not switching, so Africa/Juba is no longer a link to Africa/Khartoum. Tonga has likely ended its experiment with DST, and will not adjust its clocks on 2017-11-05. Although Tonga has not announced whether it will continue to observe DST, the IATA is assuming that it will not. (Thanks to David Wade.) Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) Changes to past time stamps Namibia switched from +02 to +01 on 1994-03-21, not 1994-04-03. (Thanks to Arthur David Olson.) Detroit did not observe DST in 1967. Use railway time for Asia/Kolkata before 1941, by switching to Madras local time (UT +052110) in 1870, then to IST (UT +0530) in 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. Europe/Dublin's 1946 and 1947 fallback transitions occurred at 02:00 standard time, not 02:00 DST. (Thanks to Michael Deckers.) Pacific/Apia and Pacific/Pago_Pago switched from Antipodean to American time in 1892, not 1879. (Thanks to Michael Deckers.) Adjust the 1867 transition in Alaska to better reflect the historical record, by changing it to occur on 1867-10-18 at 15:30 Sitka time rather than at the start of 1867-10-17 local time. Although strictly speaking this is accurate only for Sitka, the rest of Alaska's blanks need to be filled in somehow. Fix off-by-one errors in UT offsets for Adak and Nome before 1867. (Thanks to Michael Deckers.) Add 7 s to the UT offset in Asia/Yangon before 1920. Changes to zone names Remove Canada/East-Saskatchewan from the 'backward' file, as it exceeded the 14-character limit and was an unused misnomer anyway. Changes to build procedure To support applications that prefer to read time zone data in text form, two zic input files tzdata.zi and leapseconds are now installed by default. The commands 'zic tzdata.zi' and 'zic -L leapseconds tzdata.zi' can reproduce the tzdata binary files without and with leap seconds, respectively. To prevent these two new files from being installed, use 'make TZDATA_TEXT=', and to suppress leap seconds from the tzdata text installation, use 'make TZDATA_TEXT=tzdata.zi'. 'make BACKWARD=' now suppresses backward-compatibility names like 'US/Pacific' that are defined in the 'backward' and 'pacificnew' files. 'make check' now works on systems that lack a UTF-8 locale, or that lack the nsgmls program. Set UTF8_LOCALE to configure the name of a UTF-8 locale, if you have one. Y2K runtime checks are no longer enabled by default. Add -DDEPRECATE_TWO_DIGIT_YEARS to CFLAGS to enable them, instead of adding -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU to disable them. (New name suggested by Brian Inglis.) The build procedure for zdump now works on AIX 7.1. (Problem reported by Kees Dekker.) Changes to code zic and the reference runtime now reject multiple leap seconds within 28 days of each other, or leap seconds before the Epoch. As a result, support for double leap seconds, which was obsolescent and undocumented, has been removed. Double leap seconds were an error in the C89 standard; they have never existed in civil timekeeping. (Thanks to Robert Elz and Bradley White for noticing glitches in the code that uncovered this problem.) zic now warns about use of the obsolescent and undocumented -y option, and about use of the obsolescent TYPE field of Rule lines. zic now allows unambiguous abbreviations like "Sa" and "Su" for weekdays; formerly it rejected them due to a bug. Conversely, zic no longer considers non-prefixes to be abbreviations; for example, it no longer accepts "lF" as an abbreviation for "lastFriday". Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". Similarly, zic now accepts the unambiguous abbreviation "L" for "Link" in ordinary context and for "Leap" in leap-second context. Conversely, zic no longer accepts non-prefixes such as "La" as abbreviations for words like "Leap". zic no longer accepts leap second lines in ordinary input, or ordinary lines in leap second input. Formerly, zic sometimes warned about this undocumented usage and handled it incorrectly. The new macro HAVE_TZNAME governs whether the tzname external variable is exported, instead of USG_COMPAT. USG_COMPAT now governs only the external variables "timezone" and "daylight". This change is needed because the three variables are not in the same category: although POSIX requires tzname, it specifies the other two variables as optional. Also, USG_COMPAT is now 1 or 0: if not defined, the code attempts to guess it from other macros. localtime.c and difftime.c no longer require stdio.h, and .c files other than zic.c no longer require sys/wait.h. zdump.c no longer assumes snprintf. (Reported by Jonathan Leffler.) Calculation of time_t extrema works around a bug in GCC 4.8.4 (Reported by Stan Shebs and Joseph Myers.) zic.c no longer mistranslates formats of line numbers in non-English locales. (Problem reported by Benno Schulenberg.) Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) Changes to documentation and commentary The two new files 'theory.html' and 'calendars' contain the contents of the removed file 'Theory'. The goal is to document tzdb theory more accessibly. The zic man page now documents abbreviation rules. tz-link.htm now covers how to apply tzdata changes to clients. (Thanks to Jorge Fábregas for the AIX link.) It also mentions MySQL. The leap-seconds.list URL has been updated to something that is more reliable for tzdb. (Thanks to Tim Parenti and Brian Inglis.) Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2017c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2017c.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 from ftp://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 812e509d5a30657f8e99ec51cedac7d4229ed784 dated 2017-10-20 14:49:34 -0700 and tagged '2017c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 0d8c3e07b0de9015a137602450468ceb6358312a50eeda2a860882367107b8ba9ef275880b292570a671b9910afc54e6209e1e642387d246bc9c08c4ff660ffb tzcode2017c.tar.gz feb5c544e617b30c73a397e5a1c51f9847d0fddf1dfa0f9ace2e6f686786f09b666937b2048e07075c84593fc584bd5a25d639fce70eca9735267df28621ab4c tzdata2017c.tar.gz f877cd48bde0e342b9f71490befd7890682c87e9f542480b2e412b3ae08bd284516a3015588222c1fad8e3ec40a0428986404c3b660d7c88da92c1a2b6af10b4 tzdb-2017c.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFEAAoJEO2X6Q5iqn40JnoP/i8JCoxp5Vb+oxD2F8hz85+S ikzzi0+l5vMifyI9+/kxU/V+W1YvLC3zbUMLN6moE65WryjRnXCJXfTzNyFUON0H Dg7a1al0mNcq5D4YIvR6C/O5SJdRNW6VNW0A0owXV8ZafAzUbe5ICoUKQ69DC3ps jKXjO9qsyxne7rqjaqCyJAGVRHdx82p7XRvr5JCtU5vEGoclCDglWN4cUP09019q azA1eYfqkqS+uf3KzPVc8e/0slAdXOqOib7NNFY/Y90wFUlKuhgHdOXVy9bIvdeP PQmNlXNi1TC/gYNtqdxoeCsWSnOCMW9f/v9vBZTB8Oh8Ycm6U+YSAKZxlaVP5zUa VEnyMxDjKOD6YcqGHqx035TFxaAfaDDvDRACcA98SdTcBr7TgY4Ubxv0kCQ007Vr BYesKUcVpE8/wsh6dDHbaZzK01bJkJYGr44UZBwOwAbbkyCG+HDv3J6eg4UphQq0 HITxJLsaiJcJnR/l8YVSrzSHXIftwRIhGbab3BFuPAN7nDEZFrhUkZdMwac4B6E8 gsVxLYK3SJyFz9Jx7D4oDBN+Nxt+54O3/GXYVtAF0k2hiytd6UFaIr1WsmdSVLzA kmBQNiyqJ9jOPJ75B/r4x15JRZfNFDKJZ7AMqo6QthKZrurK93uuR20OKZmklnLr Vwcz+6pYTUf9bRrRfyXg =drdL -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nFvAAoJEO2X6Q5iqn40dFwP/31AK4shXM+vRKf28szHxBwk gTHTka+WMvQdhRtkgQvRXDQo1q9QiI/t4l3x0TpxkkuZATA6Yf1AhV7ugFFfl8Ia 0bc+8uXnv8XnpZ3Qbk57B6J6LEsaMOeaXv1vIZ6x8E/oaDECAV4o2+dpDl5kdNTr O6hcUZwY1Rd8CcJCvOPSFfRV1kNcPXCaKQPh0Z5uohqC7DLmxhtagsiMeUmzInV/ Q1bPOJXF4sD9X7A6hKqk4oyFQvJrYjv/JeM5eoreHIXdSLqvvwhhqCSMx6A76NDA 1/rKFZxqBLojlLmG07SXsCMC9OmD2m709sHKPx0foixhlmB9QJjDm62EjPPwfXd9 AH/3jxolQQq8DCC4XyqLblzPORfFNwZ4vWC3QpTNsQOdqBdkKpfNYXIZTxGL/8Ti 6GtCwmp2E5+gXoV1uTHY51nLNjuI47XdUReh+eBWAWh95gJiKspStHebWLFsbUhg /YM9K9efhu5UaA3BxJn3SpXR43zeNDSUOmyIB+kyRQZDXSK/K0ukwgZPMzq8QuR8 aFB7K0YztC8P6SXIGOgMsWuVp06Cx4QQAdnvy9pcx0iDUUNoh/n+isvwfBCvvUvq ETDnuGYxsUTjlDvORG1VHg14sr4AdyTl3PH12cOscVP4fq5JV91cE4FBHwjD3jSx Lp4Yb/wfGxGLgqPmpY/I =C3sx -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJZ6nF3AAoJEO2X6Q5iqn40NeQP/iuhDY14PgMC6Y4NjghAv/hZ lv3TV1E9t9bWc1S4whVQMqU8cXKMd0FddIYajylefPyEb/OwxB4R7/9IDlr1qlKG NkwOWsIrmqp60yFAdSGO2sfwkAcYZlLrujU/Bh0rFy2LFbMSFL4fTfB9WnCjWmqk pX5ioFn8L+uRrVCVQf3ruoFZcAF0D+wRSGLyAb3TAxR6dr2Bq8B0eOQsRtcfPwaL 4nBy/Fa85G3BVqSMtJhJXNIK1Vat4qd8wDU8Wr9cVjImefvVGypgCom1DlOTFD/r 5+kAIXr4RPn0t7af1ue8pNVIo6NuLfEfql59JzDREgYyl2HzwfS93+Ga+/YLR9Xz rSL7nOSDhjoo66SD0TAGNEXuRhfm3IJb81NIqIyP3IV0BpnoPyZSN5ZgNNPZwIqy tfXp/jEO1JoPBNuF+S3/RucABYKkEVLrZT5RdRrmHXxVbORop+2g3ZRKYtUeuT9P ablFWRihBao7+5Enj5hMxkfivzRUgF1+Speai6uDWFfuO/wteqntYvKVIawCWN53 +IqkpBVit0LdkA7YYgBJ4SW7wfOwRRidHANWrjEMzyajP1rfFuc3Kh0N1erIdpeV 74yYcEcHZK7dU2vki331d0xr08chB215Cz/Z1Zbm2IQxxz09g0jfYrkYijFfpxuf vyMRiNaT/Hp+EpEroVP0 =0r0r -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Fiji DST Change
by Raymond Kumar Oct. 20, 2017

Oct. 20, 2017

Hi, Can you please advise by when new version of tzdata will be out. As there were some changes to Fiji DST. Thanks, Raymond Kumar Head of Billing & Products +679-7015315 ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

2 1

[PATCH] * tz-link.htm: Update for moved and expired URLs.
by Paul Eggert Oct. 20, 2017

Oct. 20, 2017

--- tz-link.htm | 29 +++++++++-------------------- 1 file changed, 9 insertions(+), 20 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 03259d2..e7a7c8f 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -267,9 +267,10 @@ href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with <a href="https://tools.ietf.org/html/rfc7809">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for -transferring time zone data by reference. The draft <a id="TZDIST-Geolocate" +transferring time zone data by reference. The (expired) draft <a +id="TZDIST-Geolocate" href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-00">TZDIST -Geolocate Extension</a> lets a client determine its time zone region +Geolocate Extension</a> would have let a client determine its time zone region from its geographic location using a <a href="https://tools.ietf.org/html/rfc5870">'geo' URI</a>.</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> @@ -504,9 +505,6 @@ href="https://www.oracle.com/java/index.html">Oracle Java</a> contains a copy of a subset of a recent <code><abbr>tz</abbr></code> database in a Java-specific format.</li> -<li><a href="https://kimmo.suominen.com/sw/timezone/">Time Zone</a> is -a <a href="https://wordpress.org">WordPress</a> plugin. It is freely -available under a <abbr>BSD</abbr>-style license.</li> <li><a href="http://www.relativedata.com/time-zone-master">Time Zone Master</a> is a Microsoft Windows clock program that can automatically download, compile and use <code>tz</code> releases. The Basic version @@ -589,7 +587,8 @@ maps</a> contains <a href="https://en.wikipedia.org/wiki/Shapefile">shapefiles</a> of sets of <code><abbr>tz</abbr></code> regions. This includes <a href="http://efele.net/maps/tz/world/">tz_world</a>, a shapefile -for all the world's regions</li> +for all the world's regions. These maps are no longer maintained and +are superseded by the Timezone Boundary Builder.</li> <li><a href="https://github.com/straup/whereonearth-timezone">Whereonearth-timezone</a> is in <a href="https://tools.ietf.org/html/rfc7946">GeoJSON</a> format @@ -633,10 +632,7 @@ the <a href="https://timezonedb.com">Time Zone Database & API</a>. Commercial network API access is provided by <a href="https://askgeo.com">AskGeo</a> and <a href="https://www.geogarage.com/blog/news-1/post/geogarage-time-zone-api-31">GeoGarage</a>. -Also, an <a -href="https://mm.icann.org/pipermail/tz/2016-October/024309.html">experimental -server</a> is available for the TZDIST Geolocate Extension mentioned -<a href="#TZDIST-Geolocate">above</a>.</li> +</li> <li>"<a href="https://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-…">How to get a time zone from a location using latitude and longitude @@ -648,13 +644,10 @@ political subdivision data related to time zones.</li> zone boundaries for multizone countries</a> summarizes legal boundaries between time zones within countries.</li> <li>Manifold.net's <a -href="http://manifold.net/info/freestuff.shtml">Free Stuff for +href="http://manifold.net/info/freestuff.shtml">Free Downloads for Manifold System Users</a> includes a Manifold-format map of world time zone boundaries distributed under the <abbr>GPL</abbr>.</li> -<li>The GeoCommunity lists several commercial sources for <a -href="http://spatialnews.geocomm.com/features/timezones/">International -Time Zones and Time Zone Data</a>.</li> <li>A ship within the <a href="https://en.wikipedia.org/wiki/Territorial_waters">territorial waters</a> of any nation uses that nation's time. In international @@ -723,7 +716,7 @@ href="ftp://ftp.cs.huji.ac.il/pub/tz/announcements" hreflang="he">announcements (in Hebrew)</a>.</dd> <dt>Italy</dt> <dd>The National Institute of Metrological Research maintains a -<a href="http://www.inrim.it/res/tf/ora_legale_i.shtml">table of civil time +<a href="http://www.nanospin.eu/res/tf/ora_legale_i.shtml">table of civil time (in Italian)</a>.</dd> <dt>Mexico</dt> <dd>The Investigation and Analysis Service of the Mexican Library of @@ -763,7 +756,7 @@ Time Zone Proceedings</a> lists changes to time zone boundaries.</dd> <h2 id="precision">Precision timekeeping</h2> <ul> <li><a -href="http://literature.agilent.com/litweb/pdf/5965-7984E.pdf">The +href="http://leapsecond.com/hpan/an1289.pdf">The Science of Timekeeping</a> is a thorough introduction to the theory and practice of precision timekeeping.</li> <li><a href="http://www.ntp.org"><abbr @@ -882,10 +875,6 @@ protocols.</li> <a href="https://www.hackcraft.net/web/datetime/">Date & Time Formats on the Web</a> surveys web- and Internet-oriented date and time formats.</li> -<li> -<a href="http://exit109.com/~ghealton/y2k/yrexamples.html">The -Best of Dates, the Worst of Dates</a> covers many problems encountered -by software developers when handling dates and time stamps.</li> <li>Alphabetic time zone abbreviations should not be used as unique identifiers for <abbr>UTC</abbr> offsets as they are ambiguous in practice. For example, in English-speaking North America -- 2.7.4

1 0

Tonga
by Lord Buddha Oct. 18, 2017

Oct. 18, 2017

To DST or not to DST. Currently the TZ DB has Tonga moving to DST on the 5th November. In 2016 they announced they were resuming DST, in the only reference to that I could quickly find <http://matangitonga.to/tag/daylight-saving?page=1>, does not state that this was for one year or whether the resumption was also for successive years. No reference for the change was added to the TZ DB. IATA it seems have taken it as being for a single year and so do not have DST starting this year. Given the discrepancy between IANA and IATA (besides the letter T), does any body have any authoritative/corroborating source for either position. /David

4 11

[PROPOSED] Northern Cyprus to reintroduce winter time
by Paul Eggert Oct. 18, 2017

Oct. 18, 2017

* NEWS, asia (Asia/Famagusta): Switch back to +02/+03 with EU rules. --- NEWS | 7 ++++++- asia | 9 ++++++++- 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index d570ec7..4e98ef7 100644 --- a/NEWS +++ b/NEWS @@ -2,7 +2,9 @@ News for the tz database Unreleased, experimental changes - Briefly: Fiji ends DST 2018-01-14, not 2018-01-21. + Briefly: + Northern Cyprus switches from +03 to +02/+03 on 2017-10-29. + Fiji ends DST 2018-01-14, not 2018-01-21. Namibia switches from +01/+02 to +02 on 2018-04-01. Sudan switches from +03 to +02 on 2017-11-01. Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. @@ -11,6 +13,9 @@ Unreleased, experimental changes Changes to future time stamps + Northern Cyprus has decided to resume EU rules starting + 2017-10-29, thus reinstituting winter time. + Fiji ends DST 2018-01-14 instead of the 2018-01-21 previously predicted. (Thanks to Dominic Fok.) Adjust future predictions accordingly. diff --git a/asia b/asia index 5ce916d..ac39af3 100644 --- a/asia +++ b/asia @@ -785,6 +785,12 @@ Zone Asia/Macau 7:34:20 - LMT 1912 Jan 1 # Looks like the time zone split in Cyprus went through last night. # http://cyprus-mail.com/2016/10/30/cyprus-new-division-two-time-zones-now-re… +# From Paul Eggert (2017-10-18): +# Northern Cyprus will reinstate winter time on October 29, thus +# staying in sync with the rest of Cyprus. See: Anastasiou A. +# Cyprus to remain united in time. Cyprus Mail 2017-10-17. +# https://cyprus-mail.com/2017/10/17/cyprus-remain-united-time/ + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Cyprus 1975 only - Apr 13 0:00 1:00 S Rule Cyprus 1975 only - Oct 12 0:00 0 - @@ -802,7 +808,8 @@ Zone Asia/Nicosia 2:13:28 - LMT 1921 Nov 14 Zone Asia/Famagusta 2:15:48 - LMT 1921 Nov 14 2:00 Cyprus EE%sT 1998 Sep 2:00 EUAsia EE%sT 2016 Sep 8 - 3:00 - +03 + 3:00 - +03 2017 Oct 29 1:00u + 2:00 EUAsia EE%sT # Classically, Cyprus belongs to Asia; e.g. see Herodotus, Histories, I.72. # However, for various reasons many users expect to find it under Europe. -- 2.7.4

1 0

Palestine summer time end 2017
by Sharef Mustafa Oct. 18, 2017

Oct. 18, 2017

Hi, According to Palestinian cabinet decision on Tue Oct 17th 2017, the summer time will end on Sat Oct 28th 2017 , the clock will be returned 60 minutes at 01:00 AM here is the link to the press release of the Palestinian cabinet http://www.palestinecabinet.gov.ps/Website/ar/ViewDetails?ID=41158 below links to few news portal who published the news. (in Arabic) http://www.maannews.net/Content.aspx?id=926062 http://aqsatv.ps/post/14832/%D8%A7%D9%84%D8%AA%D9%88%D9%82%D9%8A%D8%AA-%D8%… http://www.pbc.ps/News/%D9%85%D8%AC%D9%84%D8%B3-%D8%A7%D9%84%D9%88%D8%B2%D8… <http://www.pbc.ps/News/%D9%85%D8%AC%D9%84%D8%B3-%D8%A7%D9%84%D9%88%D8%B2%D8…> BR

2 1

[PROPOSED] Assume South Sudan is not changing
by Paul Eggert Oct. 18, 2017

Oct. 18, 2017

Although we have not heard from the government of South Sudan, for now, guess they will not change to stay in sync with Sudan. * NEWS: Mention this. * africa (Africa/Juba): Now a Zone, with the previous contents of Africa/Khartoum except for the initial LMT. * zone1970.tab (Africa/Juba): New entry. --- NEWS | 3 ++- africa | 5 ++++- zone1970.tab | 3 ++- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index b0afb21..04d6f39 100644 --- a/NEWS +++ b/NEWS @@ -20,7 +20,8 @@ Unreleased, experimental changes at 02:00. (Thanks to Steffen Thorsen.) Sudan will switch from +03 to +02 on 2017-11-01. - (Thanks to Ahmed Atyya.) + (Thanks to Ahmed Atyya.) South Sudan is not switching, so + Africa/Juba is no longer a link to Africa/Khartoum. Turks & Caicos will switch from -04 all year to -05 with US DST on 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 diff --git a/africa b/africa index 04ca8db..4a1915c 100644 --- a/africa +++ b/africa @@ -1097,7 +1097,10 @@ Zone Africa/Khartoum 2:10:08 - LMT 1931 2:00 - CAT # South Sudan -Link Africa/Khartoum Africa/Juba +# Zone NAME GMTOFF RULES FORMAT [UNTIL] +Zone Africa/Juba 2:06:28 - LMT 1931 + 2:00 Sudan CA%sT 2000 Jan 15 12:00 + 3:00 - EAT # Swaziland # See Africa/Johannesburg. diff --git a/zone1970.tab b/zone1970.tab index 8b828e6..455e797 100644 --- a/zone1970.tab +++ b/zone1970.tab @@ -316,10 +316,11 @@ RU +6445+17729 Asia/Anadyr MSK+09 - Bering Sea SA,KW,YE +2438+04643 Asia/Riyadh SB -0932+16012 Pacific/Guadalcanal SC -0440+05528 Indian/Mahe -SD,SS +1536+03232 Africa/Khartoum +SD +1536+03232 Africa/Khartoum SE +5920+01803 Europe/Stockholm SG +0117+10351 Asia/Singapore SR +0550-05510 America/Paramaribo +SS +0451+03137 Africa/Juba SV +1342-08912 America/El_Salvador SY +3330+03618 Asia/Damascus TC +2128-07108 America/Grand_Turk -- 2.13.6

1 0

[PROPOSED 1/2] * northamerica: Cite McLeod on legal time in Labrador.
by Paul Eggert Oct. 14, 2017

Oct. 14, 2017

--- northamerica | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/northamerica b/northamerica index ec5772d..e5d3eca 100644 --- a/northamerica +++ b/northamerica @@ -1254,11 +1254,13 @@ Rule Canada 2007 max - Nov Sun>=1 2:00 0 S # Newfoundland and Labrador -# From Paul Eggert (2000-10-02): -# Matthews and Vincent (1998) write that Labrador should use NST/NDT, -# but the only part of Labrador that follows the rules is the -# southeast corner, including Port Hope Simpson and Mary's Harbour, -# but excluding, say, Black Tickle. +# From Paul Eggert (2017-10-14): +# Legally Labrador should observe Newfoundland time; see: +# McLeod J. Labrador time - legal or not? St. John's Telegram, 2017-10-07 +# http://www.thetelegram.com/news/local/labrador-time--legal-or-not-154860/ +# Matthews and Vincent (1998) write that the only part of Labrador +# that follows the rules is the southeast corner, including Port Hope +# Simpson and Mary's Harbour, but excluding, say, Black Tickle. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule StJohns 1917 only - Apr 8 2:00 1:00 D -- 2.7.4

1 1

Soma SAVE format
by J William Piggott Oct. 3, 2017

Oct. 3, 2017

Is there a reason that Somoa SAVE time format is: SAVE 1 0 1 0 1 When others are formated like: SAVE 1:00 0 1:00 0 1:00

2 1

[PATCH 1/3] * Theory: fix typo in previous change
by Paul Eggert Oct. 2, 2017

Oct. 2, 2017

--- Theory | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Theory b/Theory index 3e88173..328423a 100644 --- a/Theory +++ b/Theory @@ -10,7 +10,7 @@ Theory and pragmatics of the tz code and data Time and date functions Interface stability Calendrical issues - Time and time zones on Mars + Time and time zones on other planets ----- Scope of the tz database ----- -- 2.7.4

1 2

[PATCH] Mention time on Mercury, Venus, etc.
by Paul Eggert Oct. 1, 2017

Oct. 1, 2017

* Theory: Mention time on planets in our solar system other than Earth and Mars, and cite Williams 2017. --- Theory | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/Theory b/Theory index b223935..3e88173 100644 --- a/Theory +++ b/Theory @@ -810,7 +810,7 @@ Mittelalters und der Neuzeit_, herausgegeben von Dr. O. Grotefend (Hannover: Hahnsche Buchhandlung, 1941), pp. 26-28. ------ Time and time zones on Mars ----- +----- Time and time zones on other planets ----- Some people's work schedules use Mars time. Jet Propulsion Laboratory (JPL) coordinators have kept Mars time on and off at least since 1997 @@ -844,7 +844,20 @@ wide acceptance. Astronomers often use Mars Sol Date (MSD) which is a sequential count of Mars solar days elapsed since about 1873-12-29 12:00 GMT. -The tz database does not currently support Mars time, but it is +In our solar system, Mars is the planet with time and calendar most +like Earth's. On other planets, Sun-based time and calendars would +work quite differently. For example, although Mercury's sidereal +rotation period is 58.646 Earth days, Mercury revolves around the Sun +so rapidly that an observer on Mercury's equator would see a sunrise +only every 175.97 Earth days, i.e., a Mercury year is 0.5 of a Mercury +day. Venus is more complicated, partly because its rotation is +slightly retrograde: its year is 1.92 of its days. Gas giants like +Jupiter are trickier still, as their polar and equatorial regions +rotate at different rates, so that the length of a day depends on +latitude. This effect is most pronounced on Neptune, where the day is +about 12 hours at the poles and 18 hours at the equator. + +Although the tz database does not support time on other planets, it is documented here in the hopes that support will be added eventually. Sources: @@ -860,6 +873,10 @@ Jia-Rui Chong, "Workdays Fit for a Martian", Los Angeles Times Tom Chmielewski, "Jet Lag Is Worse on Mars", The Atlantic (2015-02-26) <https://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-…> +Matt Williams, "How long is a day on the other planets of the solar +system?" <https://www.universetoday.com/37481/days-of-the-planets/> +(2017-04-27). + ----- This file is in the public domain, so clarified as of 2009-05-17 by -- 2.7.4

1 0

Turkey law about DST has been annulled
by Dempsey, Peter Sept. 28, 2017

Sept. 28, 2017

Hi, Just to inform you about the breaking news in Turkey with regards to DST: http://www.sozcu.com.tr/2017/ekonomi/son-dakika-haberi-yaz-saati-uygulamasi… The Council of State have annulled the law that resulted in Turkey in no longer using DST. It is still not certain what the next actions that the Government will take but I will keep you informed accordingly. Best regards, Pete Pete Dempsey Application Engineer | Verint Customer Engagement Solutions email peter.dempsey(a)verint.com<mailto:peter.dempsey@verint.com> office +90-216-687-0822 mobile +90-532-581-5995 This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.

3 4

[PROPOSED] Prefer https: URLs and bring some URLs up to date
by Paul Eggert Sept. 26, 2017

Sept. 26, 2017

Change http: URLs to use https: when either will work. Fix some broken URLs while we're at it. The toughest get here was the Rowayton Clamdigger's V-J Day issue. At this point I'd guess most of the http: URLs are broken; however, fixing them all is beyond the scope of this patch. * CONTRIBUTING: Mention preference for https: in URLs. * CONTRIBUTING, NEWS, Theory, africa, antarctica, asia, australasia: * backzone, europe, northamerica, southamerica, strftime.c: * tz-art.htm, tz-link.htm, tzselect.ksh, zic.c: Update URLs to prefer https:. Fix a few broken ones. --- CONTRIBUTING | 16 ++++++++---- NEWS | 2 +- Theory | 10 ++++---- africa | 48 ++++++++++++++++++------------------ antarctica | 8 +++--- asia | 66 +++++++++++++++++++++++++------------------------- australasia | 32 ++++++++++++------------ backzone | 6 ++--- europe | 66 +++++++++++++++++++++++++------------------------- northamerica | 79 +++++++++++++++++++++++++++++++----------------------------- southamerica | 30 +++++++++++------------ strftime.c | 2 +- tz-art.htm | 4 +-- tz-link.htm | 78 +++++++++++++++++++++++++++++------------------------------ tzselect.ksh | 8 +++--- zic.c | 2 +- 16 files changed, 233 insertions(+), 224 deletions(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index 22addd2..6ce6bfd 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -5,20 +5,26 @@ change timekeeping rules erratically and sometimes with little warning, the data entries do not cover all of civil time before 1970, and undoubtedly errors remain in the code and data. Feel free to fill gaps or fix mistakes, and please email improvements -to tz(a)iana.org for use in the future. +to tz(a)iana.org for use in the future. In your email, please give +reliable sources that reviewers can check. + +----- + +Developers can contribute technical changes to the source code and +data as follows. To email small changes, please run a POSIX shell command like 'diff -u old/europe new/europe >myfix.patch', and attach myfix.patch to the email. For more-elaborate changes, please read the Theory file and browse -the mailing list archives <http://mm.icann.org/pipermail/tz/> for -examples of patches that tend to work well. Ideally, additions to +the mailing list archives <https://mm.icann.org/pipermail/tz/> for +examples of patches that tend to work well. Additions to data should contain commentary citing reliable sources as -justification. +justification. Citations should use https: URLs if available. Please submit changes against either the latest release in -<ftp://ftp.iana.org/tz/> or the master branch of the development +<https://www.iana.org/time-zones> or the master branch of the development repository. If you use Git the following workflow may be helpful: * Copy the development repository. diff --git a/NEWS b/NEWS index 55c06f7..660a3fe 100644 --- a/NEWS +++ b/NEWS @@ -2341,7 +2341,7 @@ Release 2013a - 2013-02-27 09:20:35 -0800 Many changes affect historical timestamps before 1940. These were deduced from: Milne J. Civil time. Geogr J. 1899 - Feb;13(2):173-94 <http://www.jstor.org/stable/1774359>. + Feb;13(2):173-94 <https://www.jstor.org/stable/1774359>. Changes affecting the code: diff --git a/Theory b/Theory index 1bed8d2..b223935 100644 --- a/Theory +++ b/Theory @@ -293,7 +293,7 @@ Errors in the tz database arise from many sources: typically found to be incorrect. * For the UK the tz database relies on years of first-class work done by - Joseph Myers and others; see <http://www.polyomino.org.uk/british-time/>. + Joseph Myers and others; see <https://www.polyomino.org.uk/british-time/>. Other countries are not done nearly as well. * Sometimes, different people in the same city would maintain clocks @@ -377,7 +377,7 @@ Errors in the tz database arise from many sources: Proc Royal Soc A. 2016 Dec 7;472:20160404. http://dx.doi.org/10.1098/rspa.2016.0404 Also see: Espenak F. Uncertainty in Delta T (ΔT). - http://eclipse.gsfc.nasa.gov/SEhelp/uncertainty2004.html + https://eclipse.gsfc.nasa.gov/SEhelp/uncertainty2004.html * The relationship between POSIX time (that is, UTC but ignoring leap seconds) and UTC is not agreed upon after 1972. Although the POSIX @@ -650,7 +650,7 @@ 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, Calendrical Calculations: Third Edition, Cambridge University Press (2008) -<http://emr.cs.iit.edu/home/reingold/calendar-book/third-edition/>. +<https://www.cs.tau.ac.il/~nachum/calendar-book/third-edition/>. Other information and sources are given below. They sometimes disagree. @@ -851,14 +851,14 @@ Sources: Michael Allison and Robert Schmunk, "Technical Notes on Mars Solar Time as Adopted by the Mars24 Sunclock" -<http://www.giss.nasa.gov/tools/mars24/help/notes.html> (2012-08-08). +<https://www.giss.nasa.gov/tools/mars24/help/notes.html> (2012-08-08). Jia-Rui Chong, "Workdays Fit for a Martian", Los Angeles Times <http://articles.latimes.com/2004/jan/14/science/sci-marstime14> (2004-01-14), pp A1, A20-A21. Tom Chmielewski, "Jet Lag Is Worse on Mars", The Atlantic (2015-02-26) -<http://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-m…> +<https://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-…> ----- diff --git a/africa b/africa index da1ca57..30a8e5e 100644 --- a/africa +++ b/africa @@ -26,7 +26,7 @@ # # For data circa 1899, a common source is: # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94. -# http://www.jstor.org/stable/1774359 +# https://www.jstor.org/stable/1774359 # # A reliable and entertaining source about time zones is # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997). @@ -218,7 +218,7 @@ Rule Egypt 2006 only - Sep 21 24:00 0 - # saving time in Egypt will end in the night of 2007-09-06 to 2007-09-07. # From Jesper Nørgaard Welen (2007-08-15): [The following agree:] # http://www.nentjes.info/Bill/bill5.htm -# http://www.timeanddate.com/worldclock/city.html?n=53 +# https://www.timeanddate.com/worldclock/city.html?n=53 # From Steffen Thorsen (2007-09-04): The official information...: # http://www.sis.gov.eg/En/EgyptOnline/Miscellaneous/000002/02070000000000000… Rule Egypt 2007 only - Sep Thu>=1 24:00 0 - @@ -256,8 +256,8 @@ Rule Egypt 2007 only - Sep Thu>=1 24:00 0 - # timeanddate[2] and another site I've found[3] also support that. # # [1] https://bugzilla.redhat.com/show_bug.cgi?id=492263 -# [2] http://www.timeanddate.com/worldclock/clockchange.html?n=53 -# [3] http://wwp.greenwichmeantime.com/time-zone/africa/egypt/ +# [2] https://www.timeanddate.com/worldclock/clockchange.html?n=53 +# [3] https://wwp.greenwichmeantime.com/time-zone/africa/egypt/ # From Arthur David Olson (2009-04-20): # In 2009 (and for the next several years), Ramadan ends before the fourth @@ -267,10 +267,10 @@ Rule Egypt 2007 only - Sep Thu>=1 24:00 0 - # From Steffen Thorsen (2009-08-11): # We have been able to confirm the August change with the Egyptian Cabinet # Information and Decision Support Center: -# http://www.timeanddate.com/news/time/egypt-dst-ends-2009.html +# https://www.timeanddate.com/news/time/egypt-dst-ends-2009.html # # The Middle East News Agency -# http://www.mena.org.eg/index.aspx +# https://www.mena.org.eg/index.aspx # also reports "Egypt starts winter time on August 21" # today in article numbered "71, 11/08/2009 12:25 GMT." # Only the title above is available without a subscription to their service, @@ -320,7 +320,7 @@ Rule Egypt 2007 only - Sep Thu>=1 24:00 0 - # Thursday of April.... Clocks will still be turned back for Ramadan, but # dates not yet announced.... # http://almogaz.com/news/weird-news/2015/04/05/1947105 ... -# http://www.timeanddate.com/news/time/egypt-starts-dst-2015.html +# https://www.timeanddate.com/news/time/egypt-starts-dst-2015.html # From Ahmed Nazmy (2015-04-20): # Egypt's ministers cabinet just announced ... that it will cancel DST at @@ -447,11 +447,11 @@ Zone Africa/Monrovia -0:43:08 - LMT 1882 # From Even Scharning (2012-11-10): # Libya set their time one hour back at 02:00 on Saturday November 10. -# http://www.libyaherald.com/2012/11/04/clocks-to-go-back-an-hour-on-saturday/ +# https://www.libyaherald.com/2012/11/04/clocks-to-go-back-an-hour-on-saturda… # Here is an official source [in Arabic]: http://ls.ly/fb6Yc # # Steffen Thorsen forwarded a translation (2012-11-10) in -# http://mm.icann.org/pipermail/tz/2012-November/018451.html +# https://mm.icann.org/pipermail/tz/2012-November/018451.html # # From Tim Parenti (2012-11-11): # Treat the 2012-11-10 change as a zone change from UTC+2 to UTC+1. @@ -462,7 +462,7 @@ Zone Africa/Monrovia -0:43:08 - LMT 1882 # From Even Scharning (2013-10-25): # The scheduled end of DST in Libya on Friday, October 25, 2013 was # cancelled yesterday.... -# http://www.libyaherald.com/2013/10/24/correction-no-time-change-tomorrow/ +# https://www.libyaherald.com/2013/10/24/correction-no-time-change-tomorrow/ # # From Paul Eggert (2013-10-25): # For now, assume they're reverting to the pre-2012 rules of permanent UT +02. @@ -515,7 +515,7 @@ Zone Africa/Tripoli 0:52:44 - LMT 1920 # basis.... # It seems that Mauritius observed daylight saving time from 1982-10-10 to # 1983-03-20 as well, but that was not successful.... -# http://www.timeanddate.com/news/time/mauritius-daylight-saving-time.html +# https://www.timeanddate.com/news/time/mauritius-daylight-saving-time.html # From Alex Krivenyshev (2008-06-25): # http://economicdevelopment.gov.mu/portal/site/Mainhomepage/menuitem.a42b241… @@ -583,7 +583,7 @@ Zone Africa/Tripoli 0:52:44 - LMT 1920 # http://lexpress.mu/Story/3398~Beebeejaun---Les-objectifs-d-%C3%A9conomie-d-… # # Our wrap-up: -# http://www.timeanddate.com/news/time/mauritius-dst-will-not-repeat.html +# https://www.timeanddate.com/news/time/mauritius-dst-will-not-repeat.html # From Arthur David Olson (2009-07-11): # The "mauritius-dst-will-not-repeat" wrapup includes this: @@ -615,7 +615,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # be one hour ahead of GMT between 1 June and 27 September, according to # Communication Minister and Government Spokesman, Khalid Naciri...." # -# http://www.worldtimezone.net/dst_news/dst_news_morocco01.html +# http://www.worldtimezone.com/dst_news/dst_news_morocco01.html # http://en.afrik.com/news11892.html # From Alex Krivenyshev (2008-05-09): @@ -628,7 +628,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # From Patrice Scattolin (2008-05-09): # According to this article: -# http://www.avmaroc.com/actualite/heure-dete-comment-a127896.html +# https://www.avmaroc.com/actualite/heure-dete-comment-a127896.html # (and republished here: <http://www.actu.ma/heure-dete-comment_i127896_0.html>) # the changes occur at midnight: # @@ -650,7 +650,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # posted in English). # # The following Google query will generate many relevant hits: -# http://www.google.com/search?hl=en&q=Conseil+de+gouvernement+maroc+heure+av… +# https://www.google.com/search?hl=en&q=Conseil+de+gouvernement+maroc+heure+a… # From Steffen Thorsen (2008-08-27): # Morocco will change the clocks back on the midnight between August 31 @@ -661,7 +661,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # http://www.menara.ma/fr/Actualites/Maroc/Societe/ci.retour_a_l_heure_gmt_a_… # # We have some further details posted here: -# http://www.timeanddate.com/news/time/morocco-ends-dst-early-2008.html +# https://www.timeanddate.com/news/time/morocco-ends-dst-early-2008.html # From Steffen Thorsen (2009-03-17): # Morocco will observe DST from 2009-06-01 00:00 to 2009-08-21 00:00 according @@ -671,7 +671,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # (French) # # Our summary: -# http://www.timeanddate.com/news/time/morocco-starts-dst-2009.html +# https://www.timeanddate.com/news/time/morocco-starts-dst-2009.html # From Alexander Krivenyshev (2009-03-17): # Here is a link to official document from Royaume du Maroc Premier Ministre, @@ -694,7 +694,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # http://www.lavieeco.com/actualites/4099-le-maroc-passera-a-l-heure-d-ete-gm… # (French) # Our page: -# http://www.timeanddate.com/news/time/morocco-starts-dst-2010.html +# https://www.timeanddate.com/news/time/morocco-starts-dst-2010.html # From Dan Abitol (2011-03-30): # ...Rules for Africa/Casablanca are the following (24h format) @@ -711,7 +711,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # They said that the decision was already taken. # # More articles in the press -# http://www.yabiladi.com/articles/details/5058/secret-l-heure-d-ete-maroc-le… +# https://www.yabiladi.com/articles/details/5058/secret-l-heure-d-ete-maroc-l… # http://www.lematin.ma/Actualite/Express/Article.asp?id=148923 # http://www.lavieeco.com/actualite/Le-Maroc-passe-sur-GMT%2B1-a-partir-de-dim @@ -803,7 +803,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # 1433 (18 April 2012) and the decision of the Head of Government of # 16 N. 3-29-15 Chaaban 1435 (4 June 2015). # Source (french): -# http://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/ +# https://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/ # # From Milamber (2015-06-09): # http://www.mmsp.gov.ma/fr/actualites.aspx?id=863 @@ -812,7 +812,7 @@ Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis # [The gov.ma announcement] would (probably) make the switch on 2015-07-19 go # from 03:00 to 04:00 rather than from 02:00 to 03:00, as in the patch.... # I think the patch is correct and the quoted text is wrong; the text in -# <http://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/> agrees +# <https://lnt.ma/le-maroc-reculera-dune-heure-le-dimanche-14-juin/> agrees # with the patch. # From Paul Eggert (2015-06-08): @@ -963,7 +963,7 @@ Link Africa/Maputo Africa/Lusaka # Zambia # observes Botswana time, we have no details about historical practice. # In the meantime people there can use Africa/Gaborone. # See: Immanuel S. The Namibian. 2017-02-23. -# http://www.namibian.com.na/51480/read/Time-change-divides-lawmakers +# https://www.namibian.com.na/51480/read/Time-change-divides-lawmakers # From Steffen Thorsen (2017-08-09): # Namibia is going to change their time zone to what is now their DST: @@ -1130,11 +1130,11 @@ Link Africa/Khartoum Africa/Juba # According to several news sources, Tunisia will not observe DST this year. # (Arabic) # http://www.elbashayer.com/?page=viewn&nid=42546 -# http://www.babnet.net/kiwidetail-15295.asp +# https://www.babnet.net/kiwidetail-15295.asp # # We have also confirmed this with the US embassy in Tunisia. # We have a wrap-up about this on the following page: -# http://www.timeanddate.com/news/time/tunisia-cancels-dst-2009.html +# https://www.timeanddate.com/news/time/tunisia-cancels-dst-2009.html # From Alexander Krivenyshev (2009-03-17): # Here is a link to Tunis Afrique Presse News Agency diff --git a/antarctica b/antarctica index 3332d66..d9c132a 100644 --- a/antarctica +++ b/antarctica @@ -26,7 +26,7 @@ # Heard Island, McDonald Islands (uninhabited) # previously sealers and scientific personnel wintered # Margaret Turner reports -# http://web.archive.org/web/20021204222245/http://www.dstc.qut.edu.au/DST/ma… +# https://web.archive.org/web/20021204222245/http://www.dstc.qut.edu.au/DST/m… # (1999-09-30) that they're UT +05, with no DST; # presumably this is when they have visitors. # @@ -47,7 +47,7 @@ # http://www.aad.gov.au/default.asp?casid=37079 # # We have more background information here: -# http://www.timeanddate.com/news/time/antarctica-new-times.html +# https://www.timeanddate.com/news/time/antarctica-new-times.html # From Steffen Thorsen (2010-03-10): # We got these changes from the Australian Antarctic Division: ... @@ -62,7 +62,7 @@ # - Mawson station stays on UTC+5. # # Background: -# http://www.timeanddate.com/news/time/antartica-time-changes-2010.html +# https://www.timeanddate.com/news/time/antartica-time-changes-2010.html # From Steffen Thorsen (2016-10-28): # Australian Antarctica Division informed us that Casey changed time @@ -145,7 +145,7 @@ Zone Indian/Kerguelen 0 - -00 1950 # Port-aux-Français # # year-round base in the main continent # Dumont d'Urville, Île des Pétrels, -6640+14001, since 1956-11 -# <http://en.wikipedia.org/wiki/Dumont_d'Urville_Station> (2005-12-05) +# <https://en.wikipedia.org/wiki/Dumont_d'Urville_Station> (2005-12-05) # # Another base at Port-Martin, 50km east, began operation in 1947. # It was destroyed by fire on 1952-01-14. diff --git a/asia b/asia index 5057802..5ce916d 100644 --- a/asia +++ b/asia @@ -26,7 +26,7 @@ # # For data circa 1899, a common source is: # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94. -# http://www.jstor.org/stable/1774359 +# https://www.jstor.org/stable/1774359 # # For Russian data circa 1919, a source is: # Byalokoz EL. New Counting of Time in Russia since July 1, 1919. @@ -131,7 +131,7 @@ Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 # From Steffen Thorsen (2016-03-17): # ... the Azerbaijani Cabinet of Ministers has cancelled switching to # daylight saving time.... -# http://www.azernews.az/azerbaijan/94137.html +# https://www.azernews.az/azerbaijan/94137.html # http://vestnikkavkaza.net/news/Azerbaijani-Cabinet-of-Ministers-cancels-day… # http://en.apa.az/xeber_azerbaijan_abolishes_daylight_savings_ti_240862.html @@ -172,11 +172,11 @@ Zone Asia/Baku 3:19:24 - LMT 1924 May 2 # the 19th and 20th, and they have not set the end date yet. # # Some sources: -# http://in.reuters.com/article/southAsiaNews/idINIndia-40017620090601 +# https://in.reuters.com/article/southAsiaNews/idINIndia-40017620090601 # http://bdnews24.com/details.php?id=85889&cid=2 # # Our wrap-up: -# http://www.timeanddate.com/news/time/bangladesh-daylight-saving-2009.html +# https://www.timeanddate.com/news/time/bangladesh-daylight-saving-2009.html # From A. N. M. Kamrus Saadat (2009-06-15): # Finally we've got the official mail regarding DST start time where DST start @@ -327,7 +327,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # # From Jesper Nørgaard Welen (2006-07-14): # I have investigated the timezones around 1970 on the -# http://www.astro.com/atlas site [with provinces and county +# https://www.astro.com/atlas site [with provinces and county # boundaries summarized below].... A few other exceptions were two # counties on the Sichuan side of the Xizang-Sichuan border, # counties Dege and Baiyu which lies on the Sichuan side and are @@ -479,7 +479,7 @@ Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # From David Cochrane (2014-03-26): # Just a confirmation that Ürümqi time was implemented in Ürümqi on 1 Feb 1986: -# http://content.time.com/time/magazine/article/0,9171,960684,00.html +# https://content.time.com/time/magazine/article/0,9171,960684,00.html # From Luther Ma (2014-04-22): # I have interviewed numerous people of various nationalities and from @@ -636,7 +636,7 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # (both in Okinawa) adopt the Western Standard Time which is based on # 120E. The adoption began from Jan 1, 1896. The original text can be # found on Wikisource: -# http://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時) +# https://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時) # ... This could be the first adoption of time zone in Taiwan, because # during the Qing Dynasty, it seems that there was no time zone # declared officially. @@ -649,7 +649,7 @@ Zone Asia/Hong_Kong 7:36:42 - LMT 1904 Oct 30 # territory, including later occupations, adopt Japan Central Time # (UTC+9). The adoption began on Oct 1, 1937. The original text can # be found on Wikisource: -# http://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 +# https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # # That is, the time zone of Taipei switched to UTC+9 on Oct 1, 1937. @@ -862,7 +862,7 @@ Zone Asia/Tbilisi 2:59:11 - LMT 1880 # From João Carrascalão, brother of the former governor of East Timor, in # East Timor may be late for its millennium -# <http://etan.org/et99c/december/26-31/30ETMAY.htm> (1999-12-26/31): +# <https://etan.org/et99c/december/26-31/30ETMAY.htm> (1999-12-26/31): # Portugal tried to change the time forward in 1974 because the sun # rises too early but the suggestion raised a lot of problems with the # Timorese and I still don't think it would work today because it @@ -890,7 +890,7 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 # India # From Ian P. Beacock, in "A brief history of (modern) time", The Atlantic -# http://www.theatlantic.com/technology/archive/2015/12/the-creation-of-moder… +# https://www.theatlantic.com/technology/archive/2015/12/the-creation-of-mode… # (2015-12-22): # In January 1906, several thousand cotton-mill workers rioted on the # outskirts of Bombay.... They were protesting the proposed abolition of @@ -1087,7 +1087,7 @@ Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov # From Reuters (2007-09-16), with a heads-up from Jesper Nørgaard Welen: # ... the Guardian Council ... approved a law on Sunday to re-introduce # daylight saving time ... -# http://uk.reuters.com/article/oilRpt/idUKBLA65048420070916 +# https://uk.reuters.com/article/oilRpt/idUKBLA65048420070916 # # From Roozbeh Pournader (2007-11-05): # This is quoted from Official Gazette of the Islamic Republic of @@ -1186,7 +1186,7 @@ Zone Asia/Tehran 3:25:44 - LMT 1916 # http://www.aswataliraq.info/look/article.tpl?id=2047&IdLanguage=17&IdPublic… # # We have published a short article in English about the change: -# http://www.timeanddate.com/news/time/iraq-dumps-daylight-saving.html +# 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 @@ -1494,12 +1494,12 @@ Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # From Yu-Cheng Chuang (2013-07-12): # ...the Meiji Emperor announced Ordinance No. 167 of Meiji Year 28 "The clause # about standard time" ... The adoption began from Jan 1, 1896. -# http://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時) +# https://ja.wikisource.org/wiki/標準時ニ關スル件_(公布時) # # ...the Showa Emperor announced Ordinance No. 529 of Showa Year 12 ... which # means the whole Japan territory, including later occupations, adopt Japan # Central Time (UTC+9). The adoption began on Oct 1, 1937. -# http://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 +# https://ja.wikisource.org/wiki/明治二十八年勅令第百六十七號標準時ニ關スル件中改正ノ件 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tokyo 9:18:59 - LMT 1887 Dec 31 15:00u @@ -1561,7 +1561,7 @@ Zone Asia/Tokyo 9:18:59 - LMT 1887 Dec 31 15:00u # Official, in Arabic: # http://www.petra.gov.jo/public_news/Nws_NewsDetails.aspx?Menu_ID=&Site_Id=2… # ... Our background/permalink about it -# http://www.timeanddate.com/news/time/jordan-reverses-dst-decision.html +# https://www.timeanddate.com/news/time/jordan-reverses-dst-decision.html # ... # http://www.petra.gov.jo/Public_News/Nws_NewsDetails.aspx?lang=2&site_id=1&N… # ... says midnight for the coming one and 1:00 for the ones in the future @@ -1919,9 +1919,9 @@ Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 # between 1987 and 1988 ... # From Sanghyuk Jung (2014-10-29): -# http://mm.icann.org/pipermail/tz/2014-October/021830.html +# https://mm.icann.org/pipermail/tz/2014-October/021830.html # According to the Korean Wikipedia -# http://ko.wikipedia.org/wiki/한국_표준시 +# https://ko.wikipedia.org/wiki/한국_표준시 # [oldid=12896437 2014-09-04 08:03 UTC] # DST in Republic of Korea was as follows.... And I checked old # newspapers in Korean, all articles correspond with data in Wikipedia. @@ -2143,7 +2143,7 @@ Zone Indian/Maldives 4:54:00 - LMT 1880 # Male # +08:00 instead. Different sources appear to disagree with the tz # database on this, e.g.: # -# http://www.timeanddate.com/worldclock/city.html?n=1026 +# https://www.timeanddate.com/worldclock/city.html?n=1026 # http://www.worldtimeserver.com/current_time_in_MN.aspx # # both say GMT+08:00. @@ -2273,7 +2273,7 @@ Zone Asia/Kathmandu 5:41:16 - LMT 1920 # help reduce load shedding by approving the closure of commercial centres at # 9pm and moving clocks forward by one hour for the next three months. ...." # -# http://www.worldtimezone.net/dst_news/dst_news_pakistan01.html +# http://www.worldtimezone.com/dst_news/dst_news_pakistan01.html # http://www.dailytimes.com.pk/default.asp?page=2008%5C05%5C15%5Cstory_15-5-2… # From Arthur David Olson (2008-05-19): @@ -2339,7 +2339,7 @@ Zone Asia/Kathmandu 5:41:16 - LMT 1920 # # We have confirmed this year's end date with both with the Ministry of # Water and Power and the Pakistan Electric Power Company: -# http://www.timeanddate.com/news/time/pakistan-ends-dst09.html +# https://www.timeanddate.com/news/time/pakistan-ends-dst09.html # From Christoph Göhre (2009-10-01): # [T]he German Consulate General in Karachi reported me today that Pakistan @@ -2521,7 +2521,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # # We are not sure if Gaza will do the same, last year they had a different # end date, we will keep this page updated: -# http://www.timeanddate.com/news/time/westbank-gaza-dst-2009.html +# https://www.timeanddate.com/news/time/westbank-gaza-dst-2009.html # From Alexander Krivenyshev (2009-09-02): # Seems that Gaza Strip will go back to Winter Time same date as West Bank. @@ -2559,7 +2559,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # the clocks were set back one hour at 2010-08-11 00:00:00 local time in # Gaza and the West Bank. # Some more background info: -# http://www.timeanddate.com/news/time/westbank-gaza-end-dst-2010.html +# https://www.timeanddate.com/news/time/westbank-gaza-end-dst-2010.html # From Steffen Thorsen (2011-08-26): # Gaza and the West Bank did go back to standard time in the beginning of @@ -2569,7 +2569,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # # http://www.maannews.net/eng/ViewDetails.aspx?ID=416217 # Additional info: -# http://www.timeanddate.com/news/time/palestine-dst-2011.html +# https://www.timeanddate.com/news/time/palestine-dst-2011.html # From Alexander Krivenyshev (2011-08-27): # According to the article in The Jerusalem Post: @@ -2579,7 +2579,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # The Hamas government said on Saturday that it won't observe summertime after # the Muslim feast of Id al-Fitr, which begins on Tuesday..." # ... -# http://www.jpost.com/MiddleEast/Article.aspx?id=235650 +# https://www.jpost.com/MiddleEast/Article.aspx?id=235650 # http://www.worldtimezone.com/dst_news/dst_news_gazastrip05.html # The rules for Egypt are stolen from the 'africa' file. @@ -2600,7 +2600,7 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # http://safa.ps/details/news/74352/%D8%A8%D8%AF%D8%A1-%D8%A7%D9%84%D8%AA%D9%… # # Our brief summary: -# http://www.timeanddate.com/news/time/gaza-west-bank-dst-2012.html +# https://www.timeanddate.com/news/time/gaza-west-bank-dst-2012.html # From Steffen Thorsen (2013-03-26): # The following news sources tells that Palestine will "start daylight saving @@ -2620,11 +2620,11 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # From Steffen Thorsen (2015-03-03): # Sources such as http://www.alquds.com/news/article/view/id/548257 -# and http://www.raya.ps/ar/news/890705.html say Palestine areas will +# and https://www.raya.ps/ar/news/890705.html say Palestine areas will # start DST on 2015-03-28 00:00 which is one day later than expected. # # From Paul Eggert (2015-03-03): -# http://www.timeanddate.com/time/change/west-bank/ramallah?year=2014 +# https://www.timeanddate.com/time/change/west-bank/ramallah?year=2014 # says that the fall 2014 transition was Oct 23 at 24:00. # From Hannah Kreitem (2016-03-09): @@ -2648,8 +2648,8 @@ Zone Asia/Karachi 4:28:12 - LMT 1907 # # From Paul Eggert (2016-10-19): # It's also consistent with predictions in the following URLs today: -# http://www.timeanddate.com/time/change/gaza-strip/gaza -# http://www.timeanddate.com/time/change/west-bank/hebron +# https://www.timeanddate.com/time/change/gaza-strip/gaza +# https://www.timeanddate.com/time/change/west-bank/hebron # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule EgyptAsia 1957 only - May 10 0:00 1:00 S @@ -2712,7 +2712,7 @@ Zone Asia/Hebron 2:20:23 - LMT 1900 Oct # Philippines, issued a proclamation announcing that 1844-12-30 was to # be immediately followed by 1845-01-01; see R.H. van Gent's # History of the International Date Line -# http://www.staff.science.uu.nl/~gent0113/idl/idl_philippines.htm +# https://www.staff.science.uu.nl/~gent0113/idl/idl_philippines.htm # The rest of the data entries are from Shanks & Pottenger. # From Jesper Nørgaard Welen (2006-04-26): @@ -2976,7 +2976,7 @@ Rule Syria 2007 only - Nov Fri>=1 0:00 0 - # We have not found any sources saying anything about when DST ends this year. # # Our summary -# http://www.timeanddate.com/news/time/syria-dst-starts-march-27-2009.html +# https://www.timeanddate.com/news/time/syria-dst-starts-march-27-2009.html # From Steffen Thorsen (2009-10-27): # The Syrian Arab News Network on 2009-09-29 reported that Syria will @@ -3003,7 +3003,7 @@ Rule Syria 2007 only - Nov Fri>=1 0:00 0 - # http://www.sana.sy/ara/2/2012/03/26/408215.htm # # Our brief summary: -# http://www.timeanddate.com/news/time/syria-dst-2012.html +# https://www.timeanddate.com/news/time/syria-dst-2012.html # From Arthur David Olson (2012-03-27): # Assume last Friday in March going forward XXX. @@ -3086,7 +3086,7 @@ Zone Asia/Tashkent 4:37:11 - LMT 1924 May 2 # is quoted verbatim in: # http://www.thoigian.com.vn/?mPage=P80D01 # is translated by Brian Inglis in: -# http://mm.icann.org/pipermail/tz/2014-October/021654.html +# https://mm.icann.org/pipermail/tz/2014-October/021654.html # and is the basis for the information below. # # The 1906 transition was effective July 1 and standardized Indochina to diff --git a/australasia b/australasia index d62189f..ae2cd72 100644 --- a/australasia +++ b/australasia @@ -293,7 +293,7 @@ Zone Indian/Cocos 6:27:40 - LMT 1900 # http://www.fiji.gov.fj/index.php?option=com_content&view=article&id=1096:33… # # A bit more background info here: -# http://www.timeanddate.com/news/time/fiji-dst-ends-march-2010.html +# https://www.timeanddate.com/news/time/fiji-dst-ends-march-2010.html # From Alexander Krivenyshev (2010-10-24): # According to Radio Fiji and Fiji Times online, Fiji will end DST 3 @@ -560,7 +560,7 @@ Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 # The World War II entries below are instead based on Arawa-Kieta. # The Japanese occupied Kieta in July 1942, # according to the Pacific War Online Encyclopedia -# http://pwencycl.kgbudge.com/B/o/Bougainville.htm +# https://pwencycl.kgbudge.com/B/o/Bougainville.htm # and seem to have controlled it until their 1945-08-21 surrender. # # The Autonomous Region of Bougainville switched from UT +10 to +11 @@ -598,7 +598,7 @@ Link Pacific/Pago_Pago Pacific/Midway # in US minor outlying islands # Sunday of April 2011." # # Background info: -# http://www.timeanddate.com/news/time/samoa-dst-plan-2009.html +# https://www.timeanddate.com/news/time/samoa-dst-plan-2009.html # # Samoa's Daylight Saving Time Act 2009 is available here, but does not # contain any dates: @@ -689,7 +689,7 @@ Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara # From Paul Eggert (2012-07-25) # A Google Books snippet of Appendix to the Journals of the House of # Representatives of New Zealand, Session 1948, -# <http://books.google.com/books?id=ZaVCAQAAIAAJ>, page 65, says Tokelau +# <https://books.google.com/books?id=ZaVCAQAAIAAJ>, page 65, says Tokelau # was "11 hours slow on G.M.T." Go with Thorsen and assume Shanks & Pottenger # are off by an hour starting in 1901. @@ -759,7 +759,7 @@ Zone Pacific/Funafuti 11:56:52 - LMT 1901 # Operation Fishbowl shot (Tightrope, 1962-11-04).... [See] Herman Hoerlin, # "The United States High-Altitude Test Experience: A Review Emphasizing the # Impact on the Environment", Los Alamos LA-6405, Oct 1976. -# http://www.fas.org/sgp/othergov/doe/lanl/docs1/00322994.pdf +# https://www.fas.org/sgp/othergov/doe/lanl/docs1/00322994.pdf # See the table on page 4 where he lists GMT and local times for the tests; a # footnote for the JI tests reads that local time is "JI time = Hawaii Time # Minus One Hour". @@ -825,7 +825,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # # For data circa 1899, a common source is: # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94. -# http://www.jstor.org/stable/1774359 +# https://www.jstor.org/stable/1774359 # # A reliable and entertaining source about time zones is # Derek Howse, Greenwich time and longitude, Philip Wilson Publishers (1997). @@ -972,7 +972,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # AEST ACST AWST AEDT ACDT # # Parliamentary Library (2008-11-10) -# http://www.aph.gov.au/binaries/library/pubs/rp/2008-09/09rp14.pdf +# https://www.aph.gov.au/binaries/library/pubs/rp/2008-09/09rp14.pdf # EST CST WST preferred for standard time; AEST AEDT ACST ACDT also used # # The Transport Safety Bureau has an extensive series of accident reports, @@ -1008,13 +1008,13 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # # NSW (including LHI and Broken Hill): # Standard Time Act 1987 (updated 1995-04-04) -# http://www.austlii.edu.au/au/legis/nsw/consol_act/sta1987137/index.html +# https://www.austlii.edu.au/au/legis/nsw/consol_act/sta1987137/index.html # ACT # Standard Time and Summer Time Act 1972 -# http://www.austlii.edu.au/au/legis/act/consol_act/stasta1972279/index.html +# https://www.austlii.edu.au/au/legis/act/consol_act/stasta1972279/index.html # SA # Standard Time Act, 1898 -# http://www.austlii.edu.au/au/legis/sa/consol_act/sta1898137/index.html +# https://www.austlii.edu.au/au/legis/sa/consol_act/sta1898137/index.html # From David Grosz (2005-06-13): # It was announced last week that Daylight Saving would be extended by @@ -1412,7 +1412,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # the ACT for all 52 weeks of the year... # # We have a wrap-up here: -# http://www.timeanddate.com/news/time/south-australia-extends-dst.html +# https://www.timeanddate.com/news/time/south-australia-extends-dst.html ############################################################################### # New Zealand @@ -1466,7 +1466,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # From Paul Eggert (2014-07-14): # Chatham Island time was formally standardized on 1957-01-01 by # New Zealand's Standard Time Amendment Act 1956 (1956-10-26). -# http://www.austlii.edu.au/nz/legis/hist_act/staa19561956n100244.pdf +# https://www.austlii.edu.au/nz/legis/hist_act/staa19561956n100244.pdf # According to Google Books snippet view, a speaker in the New Zealand # parliamentary debates in 1956 said "Clause 78 makes provision for standard # time in the Chatham Islands. The time there is 45 minutes in advance of New @@ -1581,7 +1581,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # the Norfolk Island Museum and the Australian Bureau of Meteorology's # Norfolk Island station, and found no record of Norfolk observing DST # other than in 1974/5. See: -# http://www.timeanddate.com/time/australia/norfolk-island.html +# https://www.timeanddate.com/time/australia/norfolk-island.html # Pitcairn @@ -1615,7 +1615,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # ordaining - by a masterpiece of diplomatic flattery - that # the Fourth of July should be celebrated twice in that year." # This happened in 1892, according to the Evening News (Sydney) of 1892-07-20. -# http://www.staff.science.uu.nl/~gent0113/idl/idl.htm +# https://www.staff.science.uu.nl/~gent0113/idl/idl.htm # Although Shanks & Pottenger says they both switched to UT -11:30 # in 1911, and to -11 in 1950. many earlier sources give -11 @@ -1732,7 +1732,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # making calculation of time in Washington difficult if not almost # impossible. # -# http://www.trumanlibrary.org/wake/meeting.htm +# https://www.trumanlibrary.org/oralhist/andrsonv.htm # From Paul Eggert (2003-03-23): # We have no other report of DST in Wake Island, so omit this info for now. @@ -1760,7 +1760,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # an international standard, there are some places on the high seas where the # correct date is ambiguous. -# From Wikipedia <http://en.wikipedia.org/wiki/Time_zone> (2005-08-31): +# From Wikipedia <https://en.wikipedia.org/wiki/Time_zone> (2005-08-31): # Before 1920, all ships kept local apparent time on the high seas by setting # their clocks at night or at the morning sight so that, given the ship's # speed and direction, it would be 12 o'clock when the Sun crossed the ship's diff --git a/backzone b/backzone index 255c4a6..32bd0f1 100644 --- a/backzone +++ b/backzone @@ -540,7 +540,7 @@ Zone Europe/Belfast -0:23:40 - LMT 1880 Aug 2 # Guernsey # Data from Joseph S. Myers -# http://mm.icann.org/pipermail/tz/2013-September/019883.html +# https://mm.icann.org/pipermail/tz/2013-September/019883.html # References to be added # LMT is for Town Church, St. Peter Port, 49 degrees 27'17"N 2 degrees 32'10"W Zone Europe/Guernsey -0:10:09 - LMT 1913 Jun 18 @@ -555,7 +555,7 @@ Zone Europe/Guernsey -0:10:09 - LMT 1913 Jun 18 # # From Lester Caine (2013-09-04): # The Isle of Man legislation is now on-line at -# <http://www.legislation.gov.im>, starting with the original Statutory +# <https://www.legislation.gov.im>, starting with the original Statutory # Time Act in 1883 and including additional confirmation of some of # the dates of the 'Summer Time' orders originating at # Westminster. There is a little uncertainty as to the starting date @@ -574,7 +574,7 @@ Zone Europe/Isle_of_Man -0:17:55 - LMT 1883 Mar 30 0:00s # Jersey # Data from Joseph S. Myers -# http://mm.icann.org/pipermail/tz/2013-September/019883.html +# https://mm.icann.org/pipermail/tz/2013-September/019883.html # References to be added # LMT is for Parish Church, St. Helier, 49 degrees 11'0.57"N 2 degrees 6'24.33"W Zone Europe/Jersey -0:08:26 - LMT 1898 Jun 11 16:00u diff --git a/europe b/europe index 8cc55e8..5b3b4e5 100644 --- a/europe +++ b/europe @@ -37,14 +37,14 @@ # [PDF] (1914-03) # # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94 -# <http://www.jstor.org/stable/1774359>. He writes: +# <https://www.jstor.org/stable/1774359>. He writes: # "It is requested that corrections and additions to these tables # may be sent to Mr. John Milne, Royal Geographical Society, # Savile Row, London." Nowadays please email them to tz(a)iana.org. # # Byalokoz EL. New Counting of Time in Russia since July 1, 1919. # This Russian-language source was consulted by Vladimir Karpinsky; see -# http://mm.icann.org/pipermail/tz/2014-August/021320.html +# https://mm.icann.org/pipermail/tz/2014-August/021320.html # The full Russian citation is: # Бялокоз, Евгений Людвигович. Новый счет времени в течении суток # введенный декретом Совета народных комиссаров для всей России с 1-го @@ -187,7 +187,7 @@ # foundations of civilization throughout the world. # -- "A Silent Toast to William Willett", Pictorial Weekly; # republished in Finest Hour (Spring 2002) 1(114):26 -# http://www.winstonchurchill.org/images/finesthour/Vol.01%20No.114.pdf +# https://www.winstonchurchill.org/publications/finest-hour/finest-hour-114/a… # From Paul Eggert (2015-08-08): # The OED Supplement says that the English originally said "Daylight Saving" @@ -225,8 +225,8 @@ # official designation; the reply of the 21st was that there wasn't # but he couldn't think of anything better than the "Double British # Summer Time" that the BBC had been using informally. -# http://www.polyomino.org.uk/british-time/bbc-19410418.png -# http://www.polyomino.org.uk/british-time/ho-19410421.png +# https://www.polyomino.org.uk/british-time/bbc-19410418.png +# https://www.polyomino.org.uk/british-time/ho-19410421.png # From Sir Alexander Maxwell in the above-mentioned letter (1941-04-21): # [N]o official designation has as far as I know been adopted for the time @@ -243,13 +243,13 @@ # the history of summer time legislation in the United Kingdom. # Since 1998 Joseph S. Myers has been updating # and extending this list, which can be found in -# http://www.polyomino.org.uk/british-time/ +# https://www.polyomino.org.uk/british-time/ # From Joseph S. Myers (1998-01-06): # # The legal time in the UK outside of summer time is definitely GMT, not UTC; # see Lord Tanlaw's speech -# http://www.publications.parliament.uk/pa/ld199798/ldhansrd/vo970611/text/70… +# https://www.publications.parliament.uk/pa/ld199798/ldhansrd/vo970611/text/7… # (Lords Hansard 11 June 1997 columns 964 to 976). # From Paul Eggert (2006-03-22): @@ -295,7 +295,7 @@ # Irish 'public feeling (was) outraged by forcing of English time on us'." # -- Parsons M. Dublin lost its time zone - and 25 minutes - after 1916 Rising. # Irish Times 2014-10-27. -# http://www.irishtimes.com/news/politics/dublin-lost-its-time-zone-and-25-mi… +# https://www.irishtimes.com/news/politics/dublin-lost-its-time-zone-and-25-m… # From Joseph S. Myers (2005-01-26): # Irish laws are available online at <http://www.irishstatutebook.ie>. @@ -631,7 +631,7 @@ Rule Russia 1996 2010 - Oct lastSun 2:00s 0 - # Council of Ministers of the USSR from 1989-03-14 No. 227. # # I did not find full texts of these acts. For the 1989 one we have -# title at http://base.garant.ru/70754136/ : +# title at https://base.garant.ru/70754136/ : # "About change in calculation of time on the territories of # Lithuanian SSR, Latvian SSR and Estonian SSR, Astrakhan, # Kaliningrad, Kirov, Kuybyshev, Ulyanovsk and Uralsk oblasts". @@ -662,7 +662,7 @@ Rule Russia 1996 2010 - Oct lastSun 2:00s 0 - # http://bmockbe.ru/events/?ID=7583 # # Medvedev signed a law on the calculation of the time (in russian): -# http://www.regnum.ru/news/polit/1413906.html +# https://www.regnum.ru/news/polit/1413906.html # From Arthur David Olson (2011-06-15): # Take "abolishing daylight saving time" to mean that time is now considered @@ -789,7 +789,7 @@ Zone Europe/Vienna 1:05:21 - LMT 1893 Apr # Sources (Russian language): # http://www.belta.by/ru/all_news/society/V-Belarusi-otmenjaetsja-perexod-na-… # http://naviny.by/rubrics/society/2011/09/16/ic_articles_116_175144/ -# http://news.tut.by/society/250578.html +# https://news.tut.by/society/250578.html # # From Alexander Bokovoy (2014-10-09): # Belarussian government decided against changing to winter time.... @@ -1110,7 +1110,7 @@ Zone America/Thule -4:35:08 - LMT 1916 Jul 28 # Pituffik air base # for their standard and summer times. He says no, they use "suveaeg" # (summer time) and "talveaeg" (winter time). -# From The Baltic Times <http://www.baltictimes.com/> (1999-09-09) +# From The Baltic Times <https://www.baltictimes.com/> (1999-09-09) # via Steffen Thorsen: # This year will mark the last time Estonia shifts to summer time, # a council of the ruling coalition announced Sept. 6.... @@ -1162,7 +1162,7 @@ Zone Europe/Tallinn 1:39:00 - LMT 1880 # This is documented in Heikki Oja: Aikakirja 2007, published by The Almanac # Office of University of Helsinki, ISBN 952-10-3221-9, available online (in # Finnish) at -# http://almanakka.helsinki.fi/aikakirja/Aikakirja2007kokonaan.pdf +# https://almanakka.helsinki.fi/aikakirja/Aikakirja2007kokonaan.pdf # # Page 105 (56 in PDF version) has a handy table of all past daylight savings # transitions. It is easy enough to interpret without Finnish skills. @@ -1175,7 +1175,7 @@ Zone Europe/Tallinn 1:39:00 - LMT 1880 # From Konstantin Hyppönen (2014-06-13): # [Heikki Oja's book Aikakirja 2013] -# http://almanakka.helsinki.fi/images/aikakirja/Aikakirja2013kokonaan.pdf +# https://almanakka.helsinki.fi/images/aikakirja/Aikakirja2013kokonaan.pdf # pages 104-105, including a scan from a newspaper published on Apr 2 1942 # say that ... [o]n Apr 2 1942, 24 o'clock (which means Apr 3 1942, # 00:00), clocks were moved one hour forward. The newspaper @@ -1305,7 +1305,7 @@ Zone Europe/Paris 0:09:21 - LMT 1891 Mar 15 0:01 # From Jörg Schilling (2002-10-23): # In 1945, Berlin was switched to Moscow Summer time (GMT+4) by -# http://www.dhm.de/lemo/html/biografien/BersarinNikolai/ +# https://www.dhm.de/lemo/html/biografien/BersarinNikolai/ # General [Nikolai] Bersarin. # From Paul Eggert (2003-03-08): @@ -1845,14 +1845,14 @@ Zone Europe/Malta 0:58:04 - LMT 1893 Nov 2 0:00s # Valletta # Following Moldova and neighboring Ukraine- Transnistria (Pridnestrovie)- # Tiraspol will go back to winter time on October 30, 2011. # News from Moldova (in russian): -# http://ru.publika.md/link_317061.html +# https://ru.publika.md/link_317061.html # From Roman Tudos (2015-07-02): # http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=355077 # From Paul Eggert (2015-07-01): # The abovementioned official link to IGO1445-868/2014 states that # 2014-10-26's fallback transition occurred at 03:00 local time. Also, -# http://www.trm.md/en/social/la-30-martie-vom-trece-la-ora-de-vara +# https://www.trm.md/en/social/la-30-martie-vom-trece-la-ora-de-vara # says the 2014-03-30 spring-forward transition was at 02:00 local time. # Guess that since 1997 Moldova has switched one hour before the EU. @@ -1924,7 +1924,7 @@ Zone Europe/Monaco 0:29:32 - LMT 1891 Mar 15 # Amsterdam mean time. # The data entries before 1945 are taken from -# http://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm +# https://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Neth 1916 only - May 1 0:00 1:00 NST # Netherlands Summer Time @@ -2005,7 +2005,7 @@ Zone Europe/Oslo 0:43:00 - LMT 1895 Jan 1 # so it must have diverged from Oslo time during the war, as Oslo was # keeping Berlin time. # -# <http://home.no.net/janmayen/history.htm> says that the meteorologists +# <https://www.jan-mayen.no/history.htm> says that the meteorologists # burned down their station in 1940 and left the island, but returned in # 1941 with a small Norwegian garrison and continued operations despite # frequent air attacks from Germans. In 1943 the Americans established a @@ -2043,7 +2043,7 @@ Rule Poland 1945 only - Apr 29 0:00 1:00 S Rule Poland 1945 only - Nov 1 0:00 0 - # For 1946 on the source is Kazimierz Borkowski, # Toruń Center for Astronomy, Dept. of Radio Astronomy, Nicolaus Copernicus U., -# http://www.astro.uni.torun.pl/~kb/Artykuly/U-PA/Czas2.htm#tth_tAb1 +# https://www.astro.uni.torun.pl/~kb/Artykuly/U-PA/Czas2.htm#tth_tAb1 # Thanks to Przemysław Augustyniak (2005-05-28) for this reference. # He also gives these further references: # Mon Pol nr 13, poz 162 (1995) <http://www.abc.com.pl/serwis/mp/1995/0162.htm> @@ -2077,7 +2077,7 @@ Zone Europe/Warsaw 1:24:00 - LMT 1880 # # From Paul Eggert (2014-08-11), after a heads-up from Stephen Colebourne: # According to a Portuguese decree (1911-05-26) -# http://dre.pt/pdf1sdip/1911/05/12500/23132313.pdf +# https://dre.pt/application/dir/pdf1sdip/1911/05/12500/23132313.pdf # Lisbon was at -0:36:44.68, but switched to GMT on 1912-01-01 at 00:00. # Round the old offset to -0:36:45. This agrees with Willett but disagrees # with Shanks, who says the transition occurred on 1911-05-24 at 00:00 for @@ -2259,7 +2259,7 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # 2011 No. 725" and contains no other dates or "effective date" information. # # Another source is -# http://www.rg.ru/2011/09/06/chas-zona-dok.html +# https://rg.ru/2011/09/06/chas-zona-dok.html # which, according to translate.google.com, begins "Resolution of the # Government of the Russian Federation on August 31, 2011 N 725" and also # contains "Date first official publication: September 6, 2011 Posted on: @@ -2267,7 +2267,7 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # does not contain any "effective date" information. # # Another source is -# http://en.wikipedia.org/wiki/Oymyakonsky_District#cite_note-RuTime-7 +# https://en.wikipedia.org/wiki/Oymyakonsky_District#cite_note-RuTime-7 # which, in note 8, contains "Resolution No. 725 of August 31, 2011... # Effective as of after 7 days following the day of the official publication" # but which does not contain any reference to September 6, 2011. @@ -2350,7 +2350,7 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # with maintenance only and represent our best guesses as to which regions # are covered by each zone. They are not meant to be taken as an authoritative # listing. The region codes listed come from -# http://en.wikipedia.org/w/?title=Federal_subjects_of_Russia&oldid=611810498 +# https://en.wikipedia.org/w/?title=Federal_subjects_of_Russia&oldid=611810498 # and are used for convenience only; no guarantees are made regarding their # future stability. ISO 3166-2:RU codes are also listed for first-level # divisions where available. @@ -2515,7 +2515,7 @@ Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr # http://www.kaliningradka.ru/site_pc/cherez/index.php?ELEMENT_ID=40091 # says that Kaliningrad decided not to be an exception 2 days before the # 1991-03-31 switch and one person at -# http://izhevsk.ru/forum_light_message/50/682597-m8369040.html +# https://izhevsk.ru/forum_light_message/50/682597-m8369040.html # says he remembers that Samara opted out of the 1992-01-19 exception # 2 days before the switch. # @@ -2587,7 +2587,7 @@ Zone Europe/Simferopol 2:16:24 - LMT 1880 3:00 - MSK 1997 Mar lastSun 1:00u # From Alexander Krivenyshev (2014-03-17): # time change at 2:00 (2am) on March 30, 2014 -# http://vz.ru/news/2014/3/17/677464.html +# https://vz.ru/news/2014/3/17/677464.html # From Paul Eggert (2014-03-30): # Simferopol and Sevastopol reportedly changed their central town clocks # late the previous day, but this appears to have been ceremonial @@ -2770,7 +2770,7 @@ Zone Asia/Omsk 4:53:30 - LMT 1919 Nov 14 # suggests that Altai Republic transitioned to Moscow+3 on # 1995-05-28. # -# http://regnum.ru/news/society/1957270.html +# https://regnum.ru/news/society/1957270.html # has some historical data for Altai Krai: # before 1957: west part on UTC+6, east on UTC+7 # after 1957: UTC+7 @@ -3144,8 +3144,8 @@ Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 # districts, but have very similar populations. In fact, Wikipedia currently # lists them both as having 3528 people, exactly 1668 males and 1860 females # each! (Yikes!) -# http://en.wikipedia.org/w/?title=Srednekolymsky_District&oldid=603435276 -# http://en.wikipedia.org/w/?title=Verkhnekolymsky_District&oldid=594378493 +# https://en.wikipedia.org/w/?title=Srednekolymsky_District&oldid=603435276 +# https://en.wikipedia.org/w/?title=Verkhnekolymsky_District&oldid=594378493 # Assume this is a mistake, albeit an amusing one. # # Looking at censuses, the populations of the two municipalities seem to have @@ -3466,7 +3466,7 @@ Zone Europe/Stockholm 1:12:12 - LMT 1879 Jan 1 # # From Alois Treindl (2013-09-11): # The Federal regulations say -# http://www.admin.ch/opc/de/classified-compilation/20071096/index.html +# https://www.admin.ch/opc/de/classified-compilation/20071096/index.html # ... the meridian for Bern mean time ... is 7 degrees 26' 22.50". # Expressed in time, it is 0h29m45.5s. @@ -3543,9 +3543,9 @@ Zone Europe/Zurich 0:34:08 - LMT 1853 Jul 16 # See above comment. # According to the articles linked below, Turkey will change into summer # time zone (GMT+3) on March 28, 2011 at 3:00 a.m. instead of March 27. # This change is due to a nationwide exam on 27th. -# http://www.worldbulletin.net/?aType=haber&ArticleID=70872 +# https://www.worldbulletin.net/?aType=haber&ArticleID=70872 # Turkish: -# http://www.hurriyet.com.tr/ekonomi/17230464.asp?gid=373 +# https://www.hurriyet.com.tr/yaz-saati-uygulamasi-bir-gun-ileri-alindi-17230… # From Faruk Pasin (2014-02-14): # The DST for Turkey has been changed for this year because of the @@ -3681,7 +3681,7 @@ Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # http://www.segodnya.ua/news/14290482.html # # Deputies cancelled the winter time (in Russian) -# http://www.pravda.com.ua/rus/news/2011/09/20/6600616/ +# https://www.pravda.com.ua/rus/news/2011/09/20/6600616/ # # From Philip Pizzey (2011-10-18): # Today my Ukrainian colleagues have informed me that the diff --git a/northamerica b/northamerica index e45d9a5..ec5772d 100644 --- a/northamerica +++ b/northamerica @@ -105,10 +105,13 @@ # Last night I heard part of a rebroadcast of a 1945 Arch Oboler radio drama. # In the introduction, Oboler spoke of "Eastern Peace Time." # An AltaVista search turned up: -# http://rowayton.org/rhs/hstaug45.html +# https://web.archive.org/web/20000926032210/http://rowayton.org/rhs/hstaug45… # "When the time is announced over the radio now, it is 'Eastern Peace # Time' instead of the old familiar 'Eastern War Time.' Peace is wonderful." # (August 1945) by way of confirmation. +# +# From Paul Eggert (2017-09-23): +# This was the V-J Day issue of the Clamdigger, a Rowayton, CT newsletter. # From Joseph Gallant citing # George H. Douglas, _The Early Days of Radio Broadcasting_ (1987): @@ -257,7 +260,7 @@ Zone PST8PDT -8:00 US P%sT # HST and HDT are standardized abbreviations for Hawaii-Aleutian # standard and daylight times. See section 9.47 (p 234) of the # U.S. Government Printing Office Style Manual (2008) -# http://www.gpo.gov/fdsys/pkg/GPO-STYLEMANUAL-2008/pdf/GPO-STYLEMANUAL-2008.… +# https://www.gpo.gov/fdsys/pkg/GPO-STYLEMANUAL-2008/pdf/GPO-STYLEMANUAL-2008… # From Arthur David Olson, 2005-08-09 # The following was signed into law on 2005-08-08. @@ -346,7 +349,7 @@ Zone America/New_York -4:56:02 - LMT 1883 Nov 18 12:03:58 # western Tennessee, most of Texas, Wisconsin # From Larry M. Smith (2006-04-26) re Wisconsin: -# http://www.legis.state.wi.us/statutes/Stat0175.pdf ... +# https://docs.legis.wisconsin.gov/statutes/statutes/175.pdf # is currently enforced at the 01:00 time of change. Because the local # "bar time" in the state corresponds to 02:00, a number of citations # are issued for the "sale of class 'B' alcohol after prohibited @@ -355,7 +358,7 @@ Zone America/New_York -4:56:02 - LMT 1883 Nov 18 12:03:58 # From Douglas R. Bomberg (2007-03-12): # Wisconsin has enacted (nearly eleventh-hour) legislation to get WI # Statue 175 closer in synch with the US Congress' intent.... -# http://www.legis.state.wi.us/2007/data/acts/07Act3.pdf +# https://docs.legis.wisconsin.gov/2007/related/acts/3 # From an email administrator of the City of Fort Pierre, SD (2015-12-21): # Fort Pierre is technically located in the Mountain time zone as is @@ -402,7 +405,7 @@ Zone America/North_Dakota/New_Salem -6:45:39 - LMT 1883 Nov 18 12:14:21 # ...it appears that Mercer County, North Dakota, changed from the # mountain time zone to the central time zone at the last transition from # daylight-saving to standard time (on Nov. 7, 2010): -# http://www.gpo.gov/fdsys/pkg/FR-2010-09-29/html/2010-24376.htm +# https://www.gpo.gov/fdsys/pkg/FR-2010-09-29/html/2010-24376.htm # http://www.bismarcktribune.com/news/local/article_1eb1b588-c758-11df-b472-0… # From Andy Lipscomb (2011-01-24): @@ -453,7 +456,7 @@ Zone America/Denver -6:59:56 - LMT 1883 Nov 18 12:00:04 # legal time, and is not part of the data here.) See: # Ross SA. An energy crisis from the past: Northern California in 1948. # Working Paper No. 8, Institute of Governmental Studies, UC Berkeley, -# 1973-11. http://escholarship.org/uc/item/8x22k30c +# 1973-11. https://escholarship.org/uc/item/8x22k30c # # In another measure to save electricity, DST was instituted from 1948-03-14 # at 02:01 to 1949-01-16 at 02:00, with the governor having the option to move @@ -474,8 +477,8 @@ Zone America/Denver -6:59:56 - LMT 1883 Nov 18 12:00:04 # which established DST from April's last Sunday at 01:00 until September's # last Sunday at 02:00. This was amended by 1962's Proposition 6, which changed # the fall-back date to October's last Sunday. See: -# http://repository.uchastings.edu/cgi/viewcontent.cgi?article=1501&context=c… -# http://repository.uchastings.edu/cgi/viewcontent.cgi?article=1636&context=c… +# https://repository.uchastings.edu/cgi/viewcontent.cgi?article=1501&context=… +# https://repository.uchastings.edu/cgi/viewcontent.cgi?article=1636&context=… # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER Rule CA 1948 only - Mar 14 2:01 1:00 D @@ -569,7 +572,7 @@ Zone America/Los_Angeles -7:52:58 - LMT 1883 Nov 18 12:07:02 # It seems Metlakatla did go off PST on Sunday, November 1, changing # their time to AKST and are going to follow Alaska's DST, switching # between AKST and AKDT from now on.... -# http://www.krbd.org/2015/10/30/annette-island-times-they-are-a-changing/ +# https://www.krbd.org/2015/10/30/annette-island-times-they-are-a-changing/ # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Juneau 15:02:19 - LMT 1867 Oct 19 15:33:32 @@ -658,7 +661,7 @@ Zone America/Adak 12:13:22 - LMT 1867 Oct 19 12:44:35 # "Hawaiian Time" by Robert C. Schmitt and Doak C. Cox appears on pages 207-225 # of volume 26 of The Hawaiian Journal of History (1992). As of 2010-12-09, # the article is available at -# http://evols.library.manoa.hawaii.edu/bitstream/10524/239/2/JL26215.pdf +# https://evols.library.manoa.hawaii.edu/bitstream/10524/239/2/JL26215.pdf # and indicates that standard time was adopted effective noon, January # 13, 1896 (page 218), that in "1933, the Legislature decreed daylight # saving for the period between the last Sunday of each April and the @@ -757,7 +760,7 @@ Zone America/Boise -7:44:49 - LMT 1883 Nov 18 12:15:11 # Indiana # # For a map of Indiana's time zone regions, see: -# http://en.wikipedia.org/wiki/Time_in_Indiana +# https://en.wikipedia.org/wiki/Time_in_Indiana # # From Paul Eggert (2007-08-17): # Since 1970, most of Indiana has been like America/Indiana/Indianapolis, @@ -984,7 +987,7 @@ Zone America/Kentucky/Louisville -5:43:02 - LMT 1883 Nov 18 12:16:58 # From Paul Eggert (2001-07-16): # The final rule was published in the # Federal Register 65, 160 (2000-08-17), pp 50154-50158. -# http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=2000_register&doc… +# https://www.gpo.gov/fdsys/pkg/FR-2000-08-17/html/00-20854.htm # Zone America/Kentucky/Monticello -5:39:24 - LMT 1883 Nov 18 12:20:36 -6:00 US C%sT 1946 @@ -1010,7 +1013,7 @@ Zone America/Kentucky/Monticello -5:39:24 - LMT 1883 Nov 18 12:20:36 # West Wendover, NV officially switched from Pacific to mountain time on # 1999-10-31. See the # Federal Register 64, 203 (1999-10-21), pp 56705-56707. -# http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=1999_register&doc… +# https://www.gpo.gov/fdsys/pkg/FR-1999-10-21/html/99-27240.htm # However, the Federal Register says that West Wendover already operated # on mountain time, and the rule merely made this official; # hence a separate tz entry is not needed. @@ -1051,7 +1054,7 @@ Zone America/Kentucky/Monticello -5:39:24 - LMT 1883 Nov 18 12:20:36 # by billowing columns of smoke that ascended in an unbroken wall north of the # ballpark." See: Dow B. Detroit '67: As violence unfolded, Tigers played two # at home vs. Yankees. Detroit Free Press 2017-07-23. -# http://www.freep.com/story/sports/mlb/tigers/2017/07/23/detroit-tigers-1967… +# https://www.freep.com/story/sports/mlb/tigers/2017/07/23/detroit-tigers-196… # # Most of Michigan observed DST from 1973 on, but was a bit late in 1975. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER @@ -1120,7 +1123,7 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # [PDF] (1914-03) # # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94 -# <http://www.jstor.org/stable/1774359>. +# <https://www.jstor.org/stable/1774359>. # # See the 'europe' file for Greenland. @@ -1166,19 +1169,19 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # The British Columbia government announced yesterday that it will # adjust daylight savings next year to align with changes in the # U.S. and the rest of Canada.... -# http://www2.news.gov.bc.ca/news_releases_2005-2009/2006AG0014-000330.htm +# https://archive.news.gov.bc.ca/releases/news_releases_2005-2009/2006AG0014-… # ... # Nova Scotia # Daylight saving time will be extended by four weeks starting in 2007.... -# http://www.gov.ns.ca/just/regulations/rg2/2006/ma1206.pdf +# https://www.novascotia.ca/just/regulations/rg2/2006/ma1206.pdf # # [For New Brunswick] the new legislation dictates that the time change is to # be done at 02:00 instead of 00:01. -# http://www.gnb.ca/0062/acts/BBA-2006/Chap-19.pdf +# https://www.gnb.ca/0062/acts/BBA-2006/Chap-19.pdf # ... # Manitoba has traditionally changed the clock every fall at 03:00. # As of 2006, the transition is to take place one hour earlier at 02:00. -# http://web2.gov.mb.ca/laws/statutes/ccsm/o030e.php +# https://web2.gov.mb.ca/laws/statutes/ccsm/o030e.php # ... # [Alberta, Ontario, Quebec] will follow US rules. # http://www.qp.gov.ab.ca/documents/spring/CH03_06.CFM @@ -1192,7 +1195,7 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # http://www.hoa.gov.nl.ca/hoa/bills/Bill0634.htm # ... # Yukon -# http://www.gov.yk.ca/legislation/regs/oic2006_127.pdf +# https://www.gov.yk.ca/legislation/regs/oic2006_127.pdf # ... # N.W.T. will follow US rules. Whoever maintains the government web site # does not seem to believe in bookmarks. To see the news release, click the @@ -1213,8 +1216,8 @@ Zone America/Menominee -5:50:27 - LMT 1885 Sep 18 12:00 # time and daylight saving time arrangements in Canada circa 1998. # # National Research Council Canada maintains info about time zones and DST. -# http://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html -# http://www.nrc-cnrc.gc.ca/eng/services/time/faq/index.html#Q5 +# https://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html +# https://www.nrc-cnrc.gc.ca/eng/services/time/faq/index.html#Q5 # Its unofficial information is often taken from Matthews and Vincent. # From Paul Eggert (2006-06-27): @@ -1455,7 +1458,7 @@ Zone America/Moncton -4:19:08 - LMT 1883 Dec 9 # http://www.justice.gouv.qc.ca/english/publications/generale/temps-minganie-… # that the coastal strip from just east of Natashquan to Blanc-Sablon # observes Atlantic standard time all year round. -# http://www.assnat.qc.ca/Media/Process.aspx?MediaId=ANQ.Vigie.Bll.DocumentGe… +# https://www.assnat.qc.ca/Media/Process.aspx?MediaId=ANQ.Vigie.Bll.DocumentG… # says this common practice was codified into law as of 2007. # For lack of better info, guess this practice began around 1970, contra to # Shanks & Pottenger who have this region observing AST/ADT. @@ -1983,7 +1986,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # * 1967. Paragraph 28(34)(g) of the Interpretation Act, S.C. 1967-68, # c. 7 defines Yukon standard time as UTC-9.... # see Interpretation Act, R.S.C. 1985, c. I-21, s. 35(1). -# [http://canlii.ca/t/7vhg] +# [https://www.canlii.org/en/ca/laws/stat/rsc-1985-c-i-21/latest/rsc-1985-c-i-…] # * C.O. 1973/214 switched Yukon to PST on 1973-10-28 00:00. # * O.I.C. 1980/02 established DST. # * O.I.C. 1987/056 changed DST to Apr firstSun 2:00 to Oct lastSun 2:00. @@ -2048,7 +2051,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # hours behind Greenwich Time. # # * Yukon Standard Time defined as Pacific Standard Time, YCO 1973/214 -# http://www.canlii.org/en/yk/laws/regu/yco-1973-214/latest/yco-1973-214.html +# https://www.canlii.org/en/yk/laws/regu/yco-1973-214/latest/yco-1973-214.html # C.O. 1973/214 INTERPRETATION ACT ... # # 1. Effective October 28, 1973 Commissioner's Order 1967/59 is hereby @@ -2063,7 +2066,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # http://? - no online source found # # * Yukon Daylight Saving Time, YOIC 1987/56 -# http://www.canlii.org/en/yk/laws/regu/yoic-1987-56/latest/yoic-1987-56.html +# https://www.canlii.org/en/yk/laws/regu/yoic-1987-56/latest/yoic-1987-56.html # O.I.C. 1987/056 INTERPRETATION ACT ... # # In every year between @@ -2075,7 +2078,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # Dated ... 9th day of March, A.D., 1987. # # * Yukon Daylight Saving Time 2006, YOIC 2006/127 -# http://www.canlii.org/en/yk/laws/regu/yoic-2006-127/latest/yoic-2006-127.ht… +# https://www.canlii.org/en/yk/laws/regu/yoic-2006-127/latest/yoic-2006-127.h… # O.I.C. 2006/127 INTERPRETATION ACT ... # # 1. In Yukon each year the time for general purposes shall be 7 hours @@ -2089,7 +2092,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # 3. This order comes into force January 1, 2007. # # * Interpretation Act, RSY 2002, c 125 -# http://www.canlii.org/en/yk/laws/stat/rsy-2002-c-125/latest/rsy-2002-c-125.… +# https://www.canlii.org/en/yk/laws/stat/rsy-2002-c-125/latest/rsy-2002-c-125… # From Rives McDow (1999-09-04): # Nunavut ... moved ... to incorporate the whole territory into one time zone. @@ -2132,7 +2135,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # From Michaela Rodrigue, writing in the # Nunatsiaq News (1999-11-19): -# http://www.nunatsiaq.com/archives/nunavut991130/nvt91119_17.html +# http://www.nunatsiaqonline.ca/archives/nunavut991130/nvt91119_17.html # Clyde River, Pangnirtung and Sanikiluaq now operate with two time zones, # central - or Nunavut time - for government offices, and eastern time # for municipal offices and schools.... Igloolik [was similar but then] @@ -2150,7 +2153,7 @@ Zone America/Creston -7:46:04 - LMT 1884 # Central Time and Southampton Island [in the Central zone] is not # required to use daylight savings. -# From <http://www.nunatsiaq.com/archives/nunavut001130/nvt21110_02.html> +# From <http://www.nunatsiaqonline.ca/archives/nunavut001130/nvt21110_02.html> # Nunavut now has two time zones (2000-11-10): # The Nunavut government would allow its employees in Kugluktuk and # Cambridge Bay to operate on central time year-round, putting them @@ -2481,7 +2484,7 @@ Zone America/Dawson -9:17:40 - LMT 1900 Aug 20 # http://gaceta.diputados.gob.mx/Gaceta/61/2009/dic/V2-101209.html # # Our page: -# http://www.timeanddate.com/news/time/north-mexico-dst-change.html +# https://www.timeanddate.com/news/time/north-mexico-dst-change.html # From Arthur David Olson (2010-01-20): # The page @@ -2900,7 +2903,7 @@ Zone America/Costa_Rica -5:36:13 - LMT 1890 # San José # http://www.nnc.cubaweb.cu/marzo-2008/cien-1-11-3-08.htm # # Some more background information is posted here: -# http://www.timeanddate.com/news/time/cuba-starts-dst-march-16.html +# https://www.timeanddate.com/news/time/cuba-starts-dst-march-16.html # # The article also says that Cuba has been observing DST since 1963, # while Shanks (and tzdata) has 1965 as the first date (except in the @@ -2947,7 +2950,7 @@ Zone America/Costa_Rica -5:36:13 - LMT 1890 # San José # http://granma.co.cu/2011/03/08/nacional/artic01.html # # Our info: -# http://www.timeanddate.com/news/time/cuba-starts-dst-2011.html +# https://www.timeanddate.com/news/time/cuba-starts-dst-2011.html # # From Steffen Thorsen (2011-10-30) # Cuba will end DST two weeks later this year. Instead of going back @@ -2957,7 +2960,7 @@ Zone America/Costa_Rica -5:36:13 - LMT 1890 # San José # http://www.radioangulo.cu/noticias/cuba/17105-cuba-restablecera-el-horario-… # # Our page: -# http://www.timeanddate.com/news/time/cuba-time-changes-2011.html +# https://www.timeanddate.com/news/time/cuba-time-changes-2011.html # # From Steffen Thorsen (2012-03-01) # According to Radio Reloj, Cuba will start DST on Midnight between March @@ -2967,7 +2970,7 @@ Zone America/Costa_Rica -5:36:13 - LMT 1890 # San José # http://www.radioreloj.cu/index.php/noticias-radio-reloj/71-miscelaneas/7529… # # Our info on it: -# http://www.timeanddate.com/news/time/cuba-starts-dst-2012.html +# https://www.timeanddate.com/news/time/cuba-starts-dst-2012.html # From Steffen Thorsen (2012-11-03): # Radio Reloj and many other sources report that Cuba is changing back @@ -3162,8 +3165,8 @@ Zone America/Guatemala -6:02:04 - LMT 1918 Oct 5 # From Steffen Thorsen (2016-03-12): # Jean Antoine, editor of www.haiti-reference.com informed us that Haiti # are not going on DST this year. Several other resources confirm this: ... -# http://www.radiotelevisioncaraibes.com/presse/heure_d_t_pas_de_changement_d… -# http://www.vantbefinfo.com/changement-dheure-pas-pour-haiti/ +# https://www.radiotelevisioncaraibes.com/presse/heure_d_t_pas_de_changement_… +# https://www.vantbefinfo.com/changement-dheure-pas-pour-haiti/ # http://news.anmwe.com/haiti-lheure-nationale-ne-sera-ni-avancee-ni-reculee-… # From Steffen Thorsen (2017-03-12): @@ -3362,7 +3365,7 @@ Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre # Turks and Caicos # # From Chris Dunn in -# http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415007 +# https://bugs.debian.org/415007 # (2007-03-15): In the Turks & Caicos Islands (America/Grand_Turk) the # daylight saving dates for time changes have been adjusted to match # the recent U.S. change of dates. diff --git a/southamerica b/southamerica index a07da71..bbae226 100644 --- a/southamerica +++ b/southamerica @@ -22,7 +22,7 @@ # # For data circa 1899, a common source is: # Milne J. Civil time. Geogr J. 1899 Feb;13(2):173-94. -# http://www.jstor.org/stable/1774359 +# https://www.jstor.org/stable/1774359 # # These tables use numeric abbreviations like -03 and -0330 for # integer hour and minute UTC offsets. Although earlier editions used @@ -265,8 +265,8 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # # Es inminente que en San Luis atrasen una hora los relojes # (It is imminent in San Luis clocks one hour delay) -# http://www.lagaceta.com.ar/nota/253414/Economia/Es-inminente-que-en-San-Lui… -# http://www.worldtimezone.net/dst_news/dst_news_argentina02.html +# https://www.lagaceta.com.ar/nota/253414/Economia/Es-inminente-que-en-San-Lu… +# http://www.worldtimezone.com/dst_news/dst_news_argentina02.html # From Jesper Nørgaard Welen (2008-01-18): # The page of the San Luis provincial government @@ -385,7 +385,7 @@ Rule Arg 2008 only - Oct Sun>=15 0:00 1:00 S # Perhaps San Luis operates on the legal fiction that it is at -04 # with perpetual summer time, but ordinary usage typically seems to # just say it's at -03; see, for example, -# http://es.wikipedia.org/wiki/Hora_oficial_argentina +# https://es.wikipedia.org/wiki/Hora_oficial_argentina # We've documented similar situations as being plain changes to # standard time, so let's do that here too. This does not change UTC # offsets, only tm_isdst and the time zone abbreviations. One minor @@ -716,7 +716,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # (Portuguese) # # We have a written a short article about it as well: -# http://www.timeanddate.com/news/time/brazil-dst-2008-2009.html +# https://www.timeanddate.com/news/time/brazil-dst-2008-2009.html # # From Alexander Krivenyshev (2011-10-04): # State Bahia will return to Daylight savings time this year after 8 years off. @@ -725,7 +725,7 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # In Portuguese: # http://g1.globo.com/bahia/noticia/2011/10/governador-jaques-wagner-confirma… -# http://noticias.terra.com.br/brasil/noticias/0,,OI5390887-EI8139,00-Bahia+v… +# https://noticias.terra.com.br/brasil/noticias/0,,OI5390887-EI8139,00-Bahia+… # From Guilherme Bernardes Rodrigues (2011-10-07): # There is news in the media, however there is still no decree about it. @@ -751,16 +751,16 @@ Zone America/La_Paz -4:32:36 - LMT 1890 # From Rodrigo Severo (2012-10-16): # Tocantins state will have DST. -# http://noticias.terra.com.br/brasil/noticias/0,,OI6232536-EI306.html +# https://noticias.terra.com.br/brasil/noticias/0,,OI6232536-EI306.html # From Steffen Thorsen (2013-09-20): # Tocantins in Brazil is very likely not to observe DST from October.... # http://conexaoto.com.br/2013/09/18/ministerio-confirma-que-tocantins-esta-f… # We will keep this article updated when this is confirmed: -# http://www.timeanddate.com/news/time/brazil-starts-dst-2013.html +# https://www.timeanddate.com/news/time/brazil-starts-dst-2013.html # From Steffen Thorsen (2013-10-17): -# http://www.timeanddate.com/news/time/acre-amazonas-change-time-zone.html +# https://www.timeanddate.com/news/time/acre-amazonas-change-time-zone.html # Senator Jorge Viana announced that Acre will change time zone on November 10. # He did not specify the time of the change, nor if western parts of Amazonas # will change as well. @@ -1078,16 +1078,16 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # http://www.webexhibits.org/daylightsaving/chile.html # This contains a copy of this official table: # Cambios en la hora oficial de Chile desde 1900 (retrieved 2008-03-30) -# http://web.archive.org/web/20080330200901/http://www.horaoficial.cl/cambio.… +# https://web.archive.org/web/20080330200901/http://www.horaoficial.cl/cambio… # [1] needs several corrections, though. # # The first set of corrections is from: # [2] History of the Official Time of Chile # http://www.horaoficial.cl/ing/horaof_ing.html (retrieved 2012-03-06). See: -# http://web.archive.org/web/20120306042032/http://www.horaoficial.cl/ing/hor… +# https://web.archive.org/web/20120306042032/http://www.horaoficial.cl/ing/ho… # This is an English translation of: # Historia de la hora oficial de Chile (retrieved 2012-10-24). See: -# http://web.archive.org/web/20121024234627/http://www.horaoficial.cl/horaof.… +# https://web.archive.org/web/20121024234627/http://www.horaoficial.cl/horaof… # A fancier Spanish version (requiring mouse-clicking) is at: # http://www.horaoficial.cl/historia_hora.html # Conflicts between [1] and [2] were resolved as follows: @@ -1363,10 +1363,10 @@ Link America/Curacao America/Kralendijk # Caribbean Netherlands # Milne says the Central and South American Telegraph Company used -5:24:15. # # From Alois Treindl (2016-12-15): -# http://www.elcomercio.com/actualidad/hora-sixto-1993.html +# https://www.elcomercio.com/actualidad/hora-sixto-1993.html # ... Whether the law applied also to Galápagos, I do not know. # From Paul Eggert (2016-12-15): -# http://www.elcomercio.com/afull/modificacion-husohorario-ecuador-presidente… +# https://www.elcomercio.com/afull/modificacion-husohorario-ecuador-president… # This says President Sixto Durán Ballén signed decree No. 285, which # established DST from 1992-11-28 to 1993-02-05; it does not give transition # times. The people called it "hora de Sixto" ("Sixto hour"). The change did @@ -1778,7 +1778,7 @@ Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 # hours of presidential broadcasts, hours of lines,' quipped comedian # Jean Mary Curró ...". See: Cawthorne A, Kai D. Venezuela scraps # half-hour time difference set by Chavez. Reuters 2016-04-15 14:50 -0400 -# http://www.reuters.com/article/us-venezuela-timezone-idUSKCN0XC2BE +# https://www.reuters.com/article/us-venezuela-timezone-idUSKCN0XC2BE # # From Matt Johnson (2016-04-20): # ... published in the official Gazette [2016-04-18], here: diff --git a/strftime.c b/strftime.c index 1ffe618..6da3fb9 100644 --- a/strftime.c +++ b/strftime.c @@ -352,7 +352,7 @@ label: ** (01-53)." ** (ado, 1993-05-24) ** -** From <http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html> by Markus Kuhn: +** From <https://www.cl.cam.ac.uk/~mgk25/iso-time.html> by Markus Kuhn: ** "Week 01 of a year is per definition the first week which has the ** Thursday in this year, which is equivalent to the week which contains ** the fourth day of January. In other words, the first week of a new year diff --git a/tz-art.htm b/tz-art.htm index 82e8704..d0d6c4d 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -20,7 +20,7 @@ Arizona's daylight-saving enclaves quite well.</li> with Time & Timezones – Computerphile</a>" (2013; 10:12) delves into problems that programmers have with timekeeping.</li> <li> -<a href="http://www.rferl.org/a/28375932.html">All The Time In The World: +<a href="https://www.rferl.org/a/28375932.html">All The Time In The World: Explaining The Mysteries Of Time Zones</a>" (2017; 2:15) briefly says why France has more time zones than Russia. <li> @@ -177,7 +177,7 @@ reading a paper. Available versions include <a href="http://www.literature.org/Works/Jules-Verne/eighty">an English translation</a>, and -<a href="http://fourmilab.ch/etexts/www/tdm80j">the original French</a> +<a href="https://fourmilab.ch/etexts/www/tdm80j">the original French</a> "with illustrations from the original 1873 French-language edition". </li> <li> diff --git a/tz-link.htm b/tz-link.htm index 346fec8..3cfa5c5 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -4,13 +4,13 @@ <html> <head profile="http://dublincore.org/documents/2008/08/04/dc-html/"> <title>Sources for time zone and daylight saving time data</title> -<link rel="schema.DC" href="http://purl.org/DC/elements/1.1/"> +<link rel="schema.DC" href="https://purl.org/DC/elements/1.1/"> <meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> <meta name="DC.Title" content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2017-09-20"> +<meta name="DC.Date" content="2017-09-23"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -51,9 +51,9 @@ C Library</a> (used in <abbr title="Operating System">OS</abbr></a>, <a href="https://www.freebsd.org">Free<abbr title="Berkeley Software Distribution">BSD</abbr></a>, -<a href="http://netbsd.org">Net<abbr>BSD</abbr></a>, -<a href="http://www.openbsd.org">Open<abbr>BSD</abbr></a>, -<a href="http://www.chromium.org/chromium-os">Chromium OS</a>, +<a href="https://netbsd.org">Net<abbr>BSD</abbr></a>, +<a href="https://www.openbsd.org">Open<abbr>BSD</abbr></a>, +<a href="https://www.chromium.org/chromium-os">Chromium OS</a>, <a href="https://cygwin.com">Cygwin</a>, <a href="http://www.delorie.com/djgpp/"><abbr title="DJ's GNU Programming Platform">DJGPP</abbr></a>, @@ -61,12 +61,12 @@ title="DJ's GNU Programming Platform">DJGPP</abbr></a>, <a href="https://www.mysql.com">MySQL</a>, <a href="https://en.wikipedia.org/wiki/WebOS"><abbr title="Web Operating System">webOS</abbr></a>, -<a href="http://ibm.com/aix"><abbr +<a href="https://ibm.com/aix"><abbr title="Advanced Interactive eXecutive">AIX</abbr></a>, <a href="https://en.wikipedia.org/wiki/BlackBerry_10">BlackBerry 10</a>, -<a href="http://www.apple.com/ios/"><abbr +<a href="https://www.apple.com/ios/"><abbr title="iPhone OS">iOS</abbr></a>, -<a href="http://www.apple.com/macos/">macOS</a>, +<a href="https://www.apple.com/macos/">macOS</a>, <a href="https://www.microsoft.com/en-us/windows">Microsoft Windows</a>, <a href="https://www.hpe.com/info/openvms">Open<abbr title="Virtual Memory System">VMS</abbr></a>, @@ -180,7 +180,7 @@ less than a year's notice there is a good chance that some computer-based clocks will operate incorrectly after the change, due to delays in propagating updates to software and data. The shorter the notice, the more likely clock problems will arise; see "<a -href="http://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/">On +href="https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/">On the Timing of Time Zone Changes</a>" for examples. </p> <p> @@ -219,7 +219,7 @@ as <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>, Specialized source-file editing can be done via the <a href="https://packagecontrol.io/packages/zoneinfo">Sublime zoneinfo</a> package for <a -href="http://www.sublimetext.com">Sublime Text</a> and the <a +href="https://www.sublimetext.com">Sublime Text</a> and the <a href="https://marketplace.visualstudio.com/items?itemName=gilmoreorless.vscode-zo…">VSCode zoneinfo</a> extension for <a href="https://code.visualstudio.com">Visual Studio Code</a>. @@ -248,7 +248,7 @@ database's style.</li> These are listed roughly in ascending order of complexity and fanciness. </p> <ul> -<li><a href="http://time.is">Time.is</a> shows locations' +<li><a href="https://time.is">Time.is</a> shows locations' time and zones in a simple format.</li> <li><a href="https://www.timejones.com">TimeJones.com</a> is a simple time zone converter.</li> @@ -263,7 +263,7 @@ Converter</a> uses a pulldown menu.</li> <li><a href="http://home.kpn.nl/vanadovv/time/TZworld.html">Complete timezone information for all countries</a> displays tables of DST rules. -<li><a href="http://www.timeanddate.com/worldclock/">The World Clock – +<li><a href="https://www.timeanddate.com/worldclock/">The World Clock – Worldwide</a> lets you sort zone names and convert times.</li> <li><a href="http://www.zeitverschiebung.net/en/">Time Difference</a> calculates the current time difference between locations.</li> @@ -328,7 +328,7 @@ transition in the <code><abbr>tz</abbr></code> database.</li> Database Parser</a> is a <a href="https://en.wikipedia.org/wiki/C%2B%2B">C++</a> parser and runtime library. It is freely available under the -<a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons +<a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International Public License</a>.</li> <li><a name="ICU" href="http://site.icu-project.org">International Components for Unicode (<abbr>ICU</abbr>)</a> contains C/C++ and <a @@ -341,7 +341,7 @@ into an <abbr>ICU</abbr>-specific format. <abbr>ICU</abbr> is freely available under a <abbr>BSD</abbr>-style license.</li> <li>The <a href="https://github.com/lau/tzdata">Tzdata</a> package for -the <a href="http://elixir-lang.org">Elixir</a> language downloads +the <a href="https://elixir-lang.org">Elixir</a> language downloads and compiles tz source and exposes <abbr title="Application Program Interface">API</abbr>s for use. It is freely available under the <abbr @@ -363,7 +363,7 @@ and time <abbr>API</abbr></a> contains a class <code><abbr>tz</abbr></code> source into a binary format. It inspired Java 8 <code>java.time</code>, which its users should migrate to once they can assume Java 8 or later. It is available under the <a -href="http://www.apache.org/licenses/LICENSE-2.0">Apache License</a>.</li> +href="https://www.apache.org/licenses/LICENSE-2.0">Apache License</a>.</li> <li><a href="https://github.com/MenoData/Time4J/">Time4J – Advanced date, time and interval library for Java</a> contains a class <code>net.time4j.tool.TimezoneRepositoryCompiler</code> that compiles @@ -385,8 +385,8 @@ and a <abbr>BSD</abbr>-style license, respectively.</li> <li><a href="https://en.wikipedia.org/wiki/JavaScript">JavaScript</a>-based compilers and libraries include: <ul> -<li><a href="http://momentjs.com/timezone/">Moment Timezone</a> is a -plugin for the <a href="http://momentjs.com">Moment.js</a> date +<li><a href="https://momentjs.com/timezone/">Moment Timezone</a> is a +plugin for the <a href="https://momentjs.com">Moment.js</a> date manipulation library. It is freely available under the <abbr>MIT</abbr> license.</li> <li><a href="https://github.com/mde/timezone-js">TimezoneJS.Date</a>'s @@ -398,13 +398,13 @@ the <abbr>MIT</abbr> license.</li> </ul> <li><a href="https://github.com/JuliaTime/">JuliaTime</a> contains a compiler from <code><abbr>tz</abbr></code> source into -<a href="http://julialang.org/">Julia</a>. It is freely available +<a href="https://julialang.org/">Julia</a>. It is freely available under the <abbr>MIT</abbr> license.</li> <li><a href="http://pytz.sourceforge.net">pytz – World Timezone Definitions for Python</a> compiles <code><abbr>tz</abbr></code> source into <a href="https://www.python.org">Python</a>. It is freely available under a <abbr>BSD</abbr>-style license.</li> -<li><a href="http://tzinfo.github.io">TZInfo – +<li><a href="https://tzinfo.github.io">TZInfo – Ruby Timezone Library</a> compiles <code><abbr>tz</abbr></code> source into <a href="https://www.ruby-lang.org/en/">Ruby</a>. @@ -416,7 +416,7 @@ library that compiles <code><abbr>tz</abbr></code> source into a time zone repository whose format is either proprietary or an <abbr>XML</abbr>-encoded representation.</li> -<li><a name="Tcl" href="http://tcl.tk">Tcl</a> +<li><a name="Tcl" href="https://tcl.tk">Tcl</a> contains a developer-oriented parser that compiles <code><abbr>tz</abbr></code> source into text files, along with a runtime that can read those files. Tcl is freely available under a <abbr>BSD</abbr>-style @@ -467,7 +467,7 @@ converts <code><abbr>tz</abbr></code> binary data into in its JavaScript library for time zone conversion. Dates before 1970 are not supported.</li> <li>The <a -href="http://hackage.haskell.org/package/timezone-olson">timezone-olson</a> +href="https://hackage.haskell.org/package/timezone-olson">timezone-olson</a> package contains <a href="https://www.haskell.org">Haskell</a> code that parses and uses <code><abbr>tz</abbr></code> binary data. It is freely available under a <abbr>BSD</abbr>-style license.</li> @@ -506,9 +506,9 @@ the older, proprietary method of Microsoft Windows 2000 and later, which stores time zone data in the <a href="https://en.wikipedia.org/wiki/Windows_Registry">Windows Registry</a>. The <a -href="http://www.unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → +href="http://unicode.org/cldr/charts/latest/supplemental/zone_tzid.html">Zone → Tzid table</a> or <a -href="http://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml"><abbr>XML</abbr> +href="https://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml"><abbr>XML</abbr> file</a> of the <abbr>CLDR</abbr> data maps proprietary zone IDs to <code><abbr>tz</abbr></code> names. <li><a @@ -531,7 +531,7 @@ licenses</a> to <code><abbr>tz</abbr></code> contributors.</li> </ul> <h2 id="other-dbs">Other time zone databases</h2> <ul> -<li><a href="http://www.astro.com/atlas">Time-zone Atlas</a> +<li><a href="https://www.astro.com/atlas">Time-zone Atlas</a> is Astrodienst's Web version of Shanks and Pottenger's time zone history atlases also published in <a href="http://astrocom.com/astrology-products/software/acs-atlas-software">software</a> @@ -549,7 +549,7 @@ is another time zone database.</li> contains data from the Time Service Department of the <abbr>US</abbr> Naval Observatory.</li> <li>The <a -href="http://www.iata.org/publications/store/Pages/standard-schedules-information…">Standard +href="https://www.iata.org/publications/store/Pages/standard-schedules-informatio…">Standard Schedules Information Manual</a> of the International Air Transport Association gives current time zone rules for airports served by commercial aviation.</li> @@ -562,7 +562,7 @@ title="Central Intelligence Agency">CIA</abbr>)</a> publishes a <a href="https://www.cia.gov/library/publications/the-world-factbook/graphics/ref_ma…">time zone map</a>; the <a -href="http://www.lib.utexas.edu/maps/world.html">Perry–Castañeda +href="https://www.lib.utexas.edu/maps/world.html">Perry–Castañeda Library Map Collection</a> of the University of Texas at Austin has copies of recent editions. @@ -590,11 +590,11 @@ services and other sources.</p> <ul> <li><a href="https://github.com/evansiroky/timezone-boundary-builder">Timezone Boundary Builder</a> extracts -<a href="http://www.openstreetmap.org">Open Street Map</a> data to build +<a href="https://www.openstreetmap.org">Open Street Map</a> data to build boundaries of <code><abbr>tz</abbr></code> regions. Its code is freely available under the <abbr>MIT</abbr> license, and its data entries are freely available under the -<a href="http://opendatacommons.org/licenses/odbl/">Open Data Commons +<a href="https://opendatacommons.org/licenses/odbl/">Open Data Commons Open Database License</a>. The maps' borders appear to be quite accurate.</li> <li><a href="http://efele.net/maps/tz/"><abbr>TZ</abbr> timezones maps</a> contains <a @@ -650,7 +650,7 @@ href="https://mm.icann.org/pipermail/tz/2016-October/024309.html">experimental server</a> is available for the TZDIST Geolocate Extension mentioned <a href="#TZDIST-Geolocate">above</a>.</li> <li>"<a -href="http://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-l…">How +href="https://stackoverflow.com/questions/16086962/how-to-get-a-time-zone-from-a-…">How to get a time zone from a location using latitude and longitude coordinates?</a>" discusses other geolocation possibilities.</li> <li><a href="http://statoids.com/statoids.html">Administrative @@ -680,7 +680,7 @@ common.</li> </ul> <h2 id="civil">Civil time concepts and history</h2> <ul> -<li><a href="http://physics.nist.gov/time">A +<li><a href="https://www.nist.gov/pml/time-and-frequency-division/popular-links/walk-thr…">A Walk through Time</a> surveys the evolution of timekeeping.</li> <li><a href="http://www.webexhibits.org/daylightsaving/">About Daylight @@ -692,7 +692,7 @@ deal with civil time.</li> <li><a href="http://seizethedaylight.com/dst/">A Brief History of Daylight Saving Time</a> summarizes some of the contentious history of <abbr>DST</abbr>.</li> -<li><a href="http://www.staff.science.uu.nl/~gent0113/idl/idl.htm">A History of +<li><a href="https://www.staff.science.uu.nl/~gent0113/idl/idl.htm">A History of the International Date Line</a> tells the story of the most important time zone boundary.</li> <li><a href="http://statoids.com/tconcept.html">Basic Time @@ -702,7 +702,7 @@ Zone Concepts</a> discusses terminological issues behind time zones.</li> <dl> <dt>Australia</dt> <dd>The Parliamentary Library has commissioned a <a -href="http://www.aph.gov.au/binaries/library/pubs/rp/2009-10/10rp10.pdf">research +href="https://www.aph.gov.au/binaries/library/pubs/rp/2009-10/10rp10.pdf">research paper on daylight saving time in Australia</a>. The Bureau of Meteorology publishes a list of <a href="http://www.bom.gov.au/climate/averages/tables/dst_times.shtml">Implementation @@ -719,7 +719,7 @@ Portuguese)</a>.</dd> <dt>Canada</dt> <dd>National Research Council Canada publishes current and some older information about <a -href="http://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html">time +href="https://www.nrc-cnrc.gc.ca/eng/services/time/time_zones.html">time zones & daylight saving time</a>.</dd> <dt>Chile</dt> <dd>The Hydrographic and Oceanographic Service of the Chilean Navy publishes a @@ -727,7 +727,7 @@ zones & daylight saving time</a>.</dd> Chile's official time (in Spanish)</a>.</dd> <dt>Germany</dt> <dd>The National Institute for Science and Technology maintains the <a -href="http://www.ptb.de/cms/en/fachabteilungen/abt4/fb-44/ag-441/realisation-of-l…">Realisation +href="https://www.ptb.de/cms/en/fachabteilungen/abt4/fb-44/ag-441/realisation-of-…">Realisation of Legal Time in Germany</a>.</dd> <dt>Israel</dt> <dd>The Interior Ministry periodically issues <a @@ -745,7 +745,7 @@ hreflang="es">history of Mexican local time (in Spanish)</a>.</dd> <dt>Malaysia</dt> <dd>See Singapore <a href="#Singapore">below</a>.</dd> <dt>Netherlands</dt> -<dd><a href="http://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm" +<dd><a href="https://www.staff.science.uu.nl/~gent0113/wettijd/wettijd.htm" hreflang="nl">Legal time in the Netherlands (in Dutch)</a> covers the history of local time in the Netherlands from ancient times.</dd> <dt>New Zealand</dt> @@ -843,10 +843,10 @@ cloud service providers.</li> <li>The <a href="https://pairlist6.pair.net/mailman/listinfo/leapsecs">Leap Second Discussion List</a> covers <a -href="http://www2.unb.ca/gge/Resources/gpsworld.november99.pdf">McCarthy +href="https://www2.unb.ca/gge/Resources/gpsworld.november99.pdf">McCarthy and Klepczynski's 1999 proposal to discontinue leap seconds</a>, discussed further in -<a href="http://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf">The +<a href="https://www.cl.cam.ac.uk/~mgk25/time/metrologia-leapsecond.pdf">The leap second: its history and possible future</a>. <a href="http://www.ucolick.org/~sla/leapsecs/"><abbr>UTC</abbr> might be redefined @@ -862,12 +862,12 @@ zone names, abbreviations, identifiers, and formats. For example, it contains French translations for "Eastern European Summer Time", "<abbr title="Eastern European Summer Time">EEST</abbr>", and "Bucharest". Its -<a href="http://www.unicode.org/cldr/charts/latest/by_type/">by-type +<a href="http://unicode.org/cldr/charts/latest/by_type/">by-type charts</a> show these values for many locales. Data values are available in both <abbr title="Locale Data Markup Language">LDML</abbr> (an <abbr>XML</abbr> format) and <abbr>JSON</abbr>. <li> -<a href="http://www.cl.cam.ac.uk/~mgk25/iso-time.html">A summary of +<a href="https://www.cl.cam.ac.uk/~mgk25/iso-time.html">A summary of the international standard date and time notation</a> is a good summary of <a diff --git a/tzselect.ksh b/tzselect.ksh index d2c3a6d..759ba5f 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -17,9 +17,9 @@ REPORT_BUGS_TO=tz(a)iana.org # If your host lacks both Bash and the Korn shell, you can get their # source from one of these locations: # -# Bash <http://www.gnu.org/software/bash/bash.html> +# Bash <https://www.gnu.org/software/bash/> # Korn Shell <http://www.kornshell.com/> -# Public Domain Korn Shell <http://www.cs.mun.ca/~michael/pdksh/> +# MirBSD Korn Shell <https://www.mirbsd.org/mksh.htm> # # For portability to Solaris 9 /bin/sh this script avoids some POSIX # features and common extensions, such as $(...) (which works sometimes @@ -29,8 +29,8 @@ REPORT_BUGS_TO=tz(a)iana.org # If your host lacks awk, or has an old awk that does not conform to Posix, # you can use either of the following free programs instead: # -# Gawk (GNU awk) <http://www.gnu.org/software/gawk/> -# mawk <http://invisible-island.net/mawk/> +# Gawk (GNU awk) <https://www.gnu.org/software/gawk/> +# mawk <https://invisible-island.net/mawk/> # Specify default values for environment variables if they are unset. diff --git a/zic.c b/zic.c index 765fe7d..a3d7383 100644 --- a/zic.c +++ b/zic.c @@ -934,7 +934,7 @@ static zic_t const max_time = MAXVAL(zic_t, TIME_T_BITS_IN_FILE); Ade PAR, Aghanim N, Armitage-Caplan C et al. Planck 2013 results. I. Overview of products and scientific results. arXiv:1303.5062 2013-03-20 20:10:01 UTC - <http://arxiv.org/pdf/1303.5062v1> [PDF] + <https://arxiv.org/pdf/1303.5062v1> [PDF] Page 36, Table 9, row Age/Gyr, column Planck+WP+highL+BAO 68% limits gives the value 13.798 plus-or-minus 0.037 billion years. -- 2.13.5

2 2

[PROPOSED] Switch tz-link.htm, tz-art.htm to HTML 5
by Paul Eggert Sept. 24, 2017

Sept. 24, 2017

* Makefile (check_web): Just check tz-how-to.html, since nsgmls does not grok HTML 5. * tz-art.htm, tz-link.htm: Switch to HTML 5. * tz-link.htm: Remove old Dublin Core stuff, since it didn’t validate and was probably not that useful anyway. * tz-how-to.html: Leave this as HTML 4.01, as going to 5 would require CSS. Add charset directive so that it validates even if the web server supplies no charset. --- Makefile | 6 ++++-- tz-art.htm | 38 ++++++++++++++++++-------------------- tz-how-to.html | 5 ++++- tz-link.htm | 34 ++++++++++------------------------ 4 files changed, 36 insertions(+), 47 deletions(-) diff --git a/Makefile b/Makefile index 6be254b..fa755ad 100644 --- a/Makefile +++ b/Makefile @@ -674,8 +674,10 @@ check_tables: checktab.awk $(PRIMARY_YDATA) $(ZONETABLES) check_tzs: $(TZS) $(TZS_NEW) diff -u $(TZS) $(TZS_NEW) -check_web: $(WEB_PAGES) - $(VALIDATE_ENV) $(VALIDATE) $(VALIDATE_FLAGS) $(WEB_PAGES) +# This checks only the HTML 4.01 strict page. +# To check the the other pages, use <https://validator.w3.org/>. +check_web: tz-how-to.html + $(VALIDATE_ENV) $(VALIDATE) $(VALIDATE_FLAGS) tz-how-to.html # Check that tzdata.zi generates the same binary data that its sources do. check_zishrink: tzdata.zi zic leapseconds $(PACKRATDATA) $(TDATA) diff --git a/tz-art.htm b/tz-art.htm index d0d6c4d..d7a27ae 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -1,9 +1,7 @@ -<!DOCTYPE html -PUBLIC "-//W3C//DTD HTML 4.01//EN" -"http://www.w3.org/TR/html4/strict.dtd"> -<html> +<!DOCTYPE html> +<html lang="en"> <head> -<meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> +<meta charset="UTF-8"> <title>Time and the Arts</title> </head> <body> @@ -226,7 +224,7 @@ arranged by Russ Long and Karrin Allyson"</td></tr> <tr><td>ADO Rating</td><td>1 star</td></tr> <tr><td><a href="http://www.allmusic.com/album/i-didnt-know-about-you-mw0000618657">AMG Rating</a></td><td>4 stars</td></tr> <tr><td>Penguin Rating</td><td>3.5 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Kevin Mahogany</td></tr> <tr><td>CD</td><td>Double Rainbow</td></tr> <tr><td>Copyright Date</td><td>1993</td></tr> @@ -241,7 +239,7 @@ Lewis Nash, drums</td></tr> <tr><td>ADO Rating</td><td>1.5 stars</td></tr> <tr><td><a href="http://www.allmusic.com/album/double-rainbow-mw0000620371">AMG Rating</a></td><td>3 stars</td></tr> <tr><td>Penguin Rating</td><td>3 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Joe Williams</td></tr> <tr><td>CD</td><td>Here's to Life</td></tr> <tr><td>Copyright Date</td><td>1994</td></tr> @@ -255,7 +253,7 @@ Telarc, "Triple Play" (CD-83461)</td></tr> <tr><td>ADO Rating</td><td>black dot</td></tr> <tr><td><a href="http://www.allmusic.com/album/heres-to-life-mw0000623648">AMG Rating</a></td><td>2 stars</td></tr> <tr><td>Penguin Rating</td><td>3 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Charles Fambrough</td></tr> <tr><td>CD</td><td>Keeper of the Spirit</td></tr> <tr><td>Copyright Date</td><td>1995</td></tr> @@ -288,7 +286,7 @@ Tom Waits' "Purple Avenue"</td></tr> <tr><td>ADO Rating</td><td>2.5 stars</td></tr> <tr><td><a href="http://www.allmusic.com/album/blame-it-on-my-youth-mw0000274303">AMG Rating</a></td><td>3 stars</td></tr> <tr><td>Penguin Rating</td><td>unrated</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Milt Hinton</td></tr> <tr><td>CD</td><td>Old Man Time</td></tr> <tr><td>Copyright Date</td><td>1990</td></tr> @@ -319,7 +317,7 @@ is available.</td></tr> <tr><td>ADO Rating</td><td>3 stars</td></tr> <tr><td><a href="http://www.allmusic.com/album/old-man-time-mw0000269353">AMG Rating</a></td><td>4.5 stars</td></tr> <tr><td>Penguin Rating</td><td>3 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Alan Broadbent</td></tr> <tr><td>CD</td><td>Pacific Standard Time</td></tr> <tr><td>Copyright Date</td><td>1995</td></tr> @@ -333,7 +331,7 @@ Frank Gibson, Jr., drums</td></tr> <tr><td>ADO Rating</td><td>1 star</td></tr> <tr><td><a href="http://www.allmusic.com/album/pacific-standard-time-mw0000645433">AMG Rating</a></td><td>4 stars</td></tr> <tr><td>Penguin Rating</td><td>3.5 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Anthony Braxton/Richard Teitelbaum</td></tr> <tr><td>CD</td><td>Silence/Time Zones</td></tr> <tr><td>Copyright Date</td><td>1996</td></tr> @@ -347,7 +345,7 @@ Leroy Jenkins, violin and miscellaneous instruments; Richard Teitelbaum, modular moog and micromoog synthesizer</td></tr> <tr><td>ADO Rating</td><td>black dot</td></tr> <tr><td><a href="http://www.allmusic.com/album/silence-time-zones-mw0000595735">AMG Rating</a></td><td>4 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Charles Gayle</td></tr> <tr><td>CD</td><td>Time Zones</td></tr> <tr><td>Copyright Date</td><td>2006</td></tr> @@ -357,7 +355,7 @@ Richard Teitelbaum, modular moog and micromoog synthesizer</td></tr> <tr><td>Personnel</td><td>Charles Gayle, piano</td></tr> <tr><td>ADO Rating</td><td>1 star</td></tr> <tr><td><a href="http://www.allmusic.com/album/time-zones-mw0000349642">AMG Rating</a></td><td>4.5 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>The Get Up Kids</td></tr> <tr><td>CD</td><td>Eudora</td></tr> <tr><td>Copyright Date</td><td>2001</td></tr> @@ -366,7 +364,7 @@ Richard Teitelbaum, modular moog and micromoog synthesizer</td></tr> <tr><td>Total Time</td><td>65:12</td></tr> <tr><td>Notes</td><td>Includes the song "Central Standard Time." Thanks to Colin Bowern for this information.</td></tr> <tr><td><a href="http://www.allmusic.com/album/eudora-mw0000592063">AMG Rating</a></td><td>2.5 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Coldplay</td></tr> <tr><td>Song</td><td>Clocks</td></tr> @@ -378,7 +376,7 @@ Richard Teitelbaum, modular moog and micromoog synthesizer</td></tr> Grammy Awards. Co-written and performed by Chris Martin, great-great-grandson of DST inventor William Willett. The song's first line is "Lights go out and I can't be saved".</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Jaime Guevara</td></tr> <tr><td>Song</td><td><a @@ -390,7 +388,7 @@ hora es</a></td></tr> (1992–3). Its lyrics include "Amanecía en mitad de la noche, los guaguas iban a clase sin sol" ("It was dawning in the middle of the night, the buses went to class without sun"). -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Irving Kahal and Harry Richman</td></tr> <tr><td>Song</td><td>There Ought to be a Moonlight Saving Time</td></tr> @@ -401,7 +399,7 @@ and many others. The phrase "Moonlight saving time" also appears in the 1995 country song "Not Enough Hours in the Night" written by Aaron Barker, Kim Williams and Rob Harbin and performed by Doug Supernaw.</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>The Microscopic Septet</td></tr> <tr><td>CD</td><td>Lobster Leaps In</td></tr> @@ -413,7 +411,7 @@ Supernaw.</td></tr> <tr><td><a href="http://www.allmusic.com/album/lobster-leaps-in-mw0000794929">AMG Rating</a></td><td>3.5 stars</td></tr> <tr><td>ADO Rating</td><td>2 stars</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Bob Dylan</td></tr> <tr><td>CD</td><td>The Times They Are a-Changin'</td></tr> @@ -424,7 +422,7 @@ Supernaw.</td></tr> <tr><td><a href="http://www.allmusic.com/album/the-times-they-a-changin-mw0000202344">AMG Rating</a></td><td>4.5 stars</td></tr> <tr><td>ADO Rating</td><td>1.5 stars</td></tr> <tr><td>Notes<td>The title song is also available on "Bob Dylan's Greatest Hits" and "The Essential Bob Dylan."</td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Luciana Souza</td></tr> <tr><td>CD</td><td>Tide</td></tr> @@ -437,7 +435,7 @@ Supernaw.</td></tr> <tr><td>Notes<td>Includes the song "Fire and Wood" with the lyric "The clocks were turned back you remember/Think it's still November." </td></tr> -<tr><td> </td></tr> +<tr><td> </td><td></td></tr> <tr><td>Artist</td><td>Ken Nordine</td></tr> <tr><td>CD</td><td>You're Getting Better: The Word Jazz Dot Masters</td></tr> <tr><td>Copyright Date</td><td>2005</td></tr> diff --git a/tz-how-to.html b/tz-how-to.html index 91a0d48..6007c5e 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -2,7 +2,10 @@ PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> -<head><title>How to Read the tz Database</title></head> +<head> +<title>How to Read the tz Database</title> +<meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> +</head> <body> <h2>How to Read the <a href="https://en.wikipedia.org/wiki/Tz_database">tz Database</a> Source Files</h2> diff --git a/tz-link.htm b/tz-link.htm index 3cfa5c5..09edf0b 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -1,22 +1,8 @@ -<!DOCTYPE html - PUBLIC "-//W3C//DTD HTML 4.01//EN" - "http://www.w3.org/TR/html4/strict.dtd"> -<html> -<head profile="http://dublincore.org/documents/2008/08/04/dc-html/"> +<!DOCTYPE html> +<html lang="en"> +<head> <title>Sources for time zone and daylight saving time data</title> -<link rel="schema.DC" href="https://purl.org/DC/elements/1.1/"> -<meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> -<meta name="DC.Title" - content="Sources for time zone and daylight saving time data"> -<meta name="DC.Creator" content="Eggert, Paul"> -<meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2017-09-23"> -<meta name="DC.Description" - content="Sources of information about time zones and daylight saving time"> -<meta name="DC.Identifier" - content="https://www.iana.org/time-zones/repository/tz-link.htm"> -<meta name="Keywords" - content="database,daylight saving,DST,time zone,timezone,tz,zoneinfo"> +<meta charset="UTF-8"> </head> <body> <h1>Sources for time zone and daylight saving time data</h1> @@ -279,7 +265,7 @@ href="https://tools.ietf.org/html/rfc7808">TZDIST</a> (Internet <abbr>RFC</abbr> 7808), a time zone data distribution service, along with <a href="https://tools.ietf.org/html/rfc7809">CalDAV</a> (Internet <abbr>RFC</abbr> 7809), a calendar access protocol for -transferring time zone data by reference. The draft <a name="TZDIST-Geolocate" +transferring time zone data by reference. The draft <a id="TZDIST-Geolocate" href="https://tools.ietf.org/html/draft-murchison-tzdist-geolocate-00">TZDIST Geolocate Extension</a> lets a client determine its time zone region from its geographic location using a <a @@ -330,7 +316,7 @@ Database Parser</a> is a runtime library. It is freely available under the <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International Public License</a>.</li> -<li><a name="ICU" href="http://site.icu-project.org">International Components for +<li><a id="ICU" href="http://site.icu-project.org">International Components for Unicode (<abbr>ICU</abbr>)</a> contains C/C++ and <a href="https://en.wikipedia.org/wiki/Java_%28programming_language%29">Java</a> libraries for internationalization that @@ -416,7 +402,7 @@ library that compiles <code><abbr>tz</abbr></code> source into a time zone repository whose format is either proprietary or an <abbr>XML</abbr>-encoded representation.</li> -<li><a name="Tcl" href="https://tcl.tk">Tcl</a> +<li><a id="Tcl" href="https://tcl.tk">Tcl</a> contains a developer-oriented parser that compiles <code><abbr>tz</abbr></code> source into text files, along with a runtime that can read those files. Tcl is freely available under a <abbr>BSD</abbr>-style @@ -499,7 +485,7 @@ data (mentioned <a href="#CLDR">below</a>) used by <a href="https://en.wikipedia.org/wiki/Windows_Runtime">Windows Runtime</a> classes such as <a href="https://msdn.microsoft.com/en-us/library/windows/apps/windows.globalization…"><code>DateTimeFormatter</code></a>. -<a name="System.TimeZoneInfo" +<a id="System.TimeZoneInfo" href="https://blogs.msdn.microsoft.com/bclteam/2007/06/07/exploring-windows-time-…">Exploring Windows Time Zones with <code>System.TimeZoneInfo</code></a> describes the older, proprietary method of Microsoft Windows 2000 and later, @@ -755,7 +741,7 @@ Daylight Saving</a>. The privately-maintained <a href="http://astrologyschool.com/nztime.html">History of New Zealand time</a> has more details.</dd> <dt>Singapore</dt> -<dd><a name="Singapore" +<dd><a id="Singapore" href="http://www.math.nus.edu.sg/aslaksen/teaching/timezone.html">Why is Singapore in the "Wrong" Time Zone?</a> details the history of legal time in Singapore and Malaysia.</dd> @@ -856,7 +842,7 @@ again.</li> </ul> <h2 id="notation">Time notation</h2> <ul> -<li>The <a name="CLDR" href="http://cldr.unicode.org">Unicode Common Locale Data +<li>The <a id="CLDR" href="http://cldr.unicode.org">Unicode Common Locale Data Repository (<abbr>CLDR</abbr>) Project</a> has localizations for time zone names, abbreviations, identifiers, and formats. For example, it contains French translations for "Eastern European Summer Time", -- 2.13.5

1 0

[PROPOSED] * tz-how-to.html: Update URLs.
by Paul Eggert Sept. 24, 2017

Sept. 24, 2017

--- tz-how-to.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tz-how-to.html b/tz-how-to.html index a94759e..91a0d48 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -519,7 +519,7 @@ usage</i>, which is not necessarily “correct” by law. For example, the last line in <code>Zone</code> <code>Pacific/Honolulu</code> (shown below) gives “HST” for “Hawaii standard time” even though the -<a href="http://www.law.cornell.edu/uscode/html/uscode15/usc_sec_15_00000263----000-…">legal</a> +<a href="https://www.law.cornell.edu/uscode/text/15/263">legal</a> name for that time zone is “Hawaii-Aleutian standard time.” This author has read that there are also some places in Australia where popular time zone names differ from the legal ones. @@ -531,7 +531,7 @@ the abbreviations. They are intended to be the values returned through the <a href="https://en.wikipedia.org/wiki/C_(programming_language)">C</a>’s <a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/strftime.html"><code>strftime</code></a> function in the -<a href="http://www.chemie.fu-berlin.de/chemnet/use/info/libc/libc_19.html#SEC324">“C” locale</a>. +<a href="http://kirste.userpage.fu-berlin.de/chemnet/use/info/libc/libc_19.html#SEC3…">“C” locale</a>. <li>If there is no generally-accepted abbreviation for a time zone, a numeric offset is used instead, e.g., <code>+07</code> for 7 hours -- 2.13.5

1 0

Namibia
by Ömer Kardaş Sept. 20, 2017

Sept. 20, 2017

It appears that Namibia adopts new time zone. According to timeanddate.com Namibia will stay on Daylight Saving Time (DST) all year, effectively adding 1 hour to its standard time. The Namibian Time Bill was approved by the National Council on Monday, August 8, 2017 after public hearings where the majority was in support of the bill. https://www.timeanddate.com/news/time/namibia-new-time-zone.html

2 1

Alberta Tory leadership candidate petitions to drop DST and move to CT
by Brian Inglis Sept. 19, 2017

Sept. 19, 2017

On the final day of the fall sitting on Tuesday, Alberta Progressive Conservative leadership candidate, Vermilion-Lloydminster MLA Richard Starke presented a petition to the legislature calling for repeal of the Daylight Saving Time Act and a move to Central Time (from Mountain Time), to be decided by a referendum. The stories linked below are all from the same news org and under the same byline. The latter two have a vote button at the bottom to poll readers' opinions, each currently running about 80/20 in favour of dropping DST, and/or possibly also of switching to permanent CT, depending on whether the voters read the question or just clicked. http://calgaryherald.com/news/politics/pc-leadership-candidate-starke-calls… http://www.edmontonjournal.com/news/politics/leadership+candidate+starke+ca… http://www.calgarysun.com/2016/12/14/to-keep-or-ditch-daylight-saving-time-… http://www.edmontonsun.com/2016/12/14/to-keep-or-ditch-daylight-saving-time… -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

6 14

About Asia/Hanoi
by Meno Hochschild Sept. 10, 2017

Sept. 10, 2017

Should there be a link between Asia/Hanoi and Asia/Ho_Chi_Minh in TZDB? Background of my question is an issue reported on the ThreetenBP-issue-tracker (see: https://github.com/ThreeTen/threetenbp/issues/57) where someone has observed a crash on its Android mobile phone using Asia/Hanoi as system tz (resided in OS) while the extra tz-distribution of an external library (ThreetenBP) does not contain that identifier (probably because it is in the backzone-file of TZDB). With best regards Meno

2 3

Update frequency has dropped off(?)
by Paul Holland Sept. 5, 2017

Sept. 5, 2017

Last update was in March (2017b). Last year there were many updates (10?). Does this mean (1) the database has stabilised; or (2) it is no longer actively maintained? Just curious :-D Cheers, Paul E: paul(a)holland.name

4 4

Time zones in xkcd #1883
by Tim Parenti Aug. 30, 2017

Aug. 30, 2017

Today's xkcd by Randall Munroe (2017-08-30) shows how time zones can throw a wrench into supervillians' plans: https://www.xkcd.com/1883/ -- Tim Parenti

2 2

Fiji DST change?
by Magnus Bengtsson Aug. 28, 2017

Aug. 28, 2017

IATA has sent out the following message: " Please be advised of the following 2017/18 DST dates for Fiji. Please amend the entry for Fiji in Appendix F of your SSIM MAR17 issue to reflect the following: Country Time Standard - - - DST Start - - - - - - DST End - - - DST Name Zone Variation Time Date Time Date Variation Fiji FJ +1200 1400 04NOV17 1400 13JAN18 +1300 " The end date (13JAN18) does not seem to conform to the current rule in tzdata2017b. I can't find any information about this on http://www.fiji.gov.fj Does anyone have any more information? /Magnus Bengtsson

4 3

[PROPOSED] Adjust official transition for Turks & Caicos
by Paul Eggert Aug. 27, 2017

Aug. 27, 2017

* NEWS: Adjust. * northamerica (America/Grand_Turk): Switch 2018-03-11 03:00, not 2018-04-01. --- NEWS | 2 +- northamerica | 8 +++++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 0909112..55c06f7 100644 --- a/NEWS +++ b/NEWS @@ -19,7 +19,7 @@ Unreleased, experimental changes at 02:00. (Thanks to Steffen Thorsen.) Turks & Caicos will switch from -04 all year to -05 with US DST on - 2018-04-01 at 00:00. This affects UT offsets starting 2018-11-04 + 2018-03-11 at 03:00. This affects UT offsets starting 2018-11-04 at 02:00. (Thanks to Steffen Thorsen.) Changes to past time stamps diff --git a/northamerica b/northamerica index 42529de..93655fa 100644 --- a/northamerica +++ b/northamerica @@ -3390,12 +3390,18 @@ Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre # Time, during the winter months with effect from April 2018 ... # https://www.gov.uk/government/news/turks-and-caicos-post-cabinet-meeting-st… # +# From Paul Eggert (2018-08-26): +# The date of effect of the spring 2018 change appears to be March 11, +# which makes more sense. See: Hamilton D. Time change back +# by March 2018 for TCI. Magnetic Media. 2018-08-25. +# http://magneticmediatv.com/2017/08/time-change-back-by-march-2018-for-tci/ +# # 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:00 - EST 1979 -5:00 US E%sT 2015 Nov Sun>=1 2:00 - -4:00 - AST 2018 Apr + -4:00 - AST 2018 Mar 11 3:00 -5:00 US E%sT # British Virgin Is -- 2.7.4

3 3

[PATCH] * tz-art.htm (Jokes): Add Keillor joke on tz security.
by Paul Eggert Aug. 25, 2017

Aug. 25, 2017

--- tz-art.htm | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tz-art.htm b/tz-art.htm index abe8eb3..a42361f 100644 --- a/tz-art.htm +++ b/tz-art.htm @@ -549,6 +549,14 @@ yesterday daylight [saving] time ended. Right now it's basically midnight." (Conan O'Brien on the 2010-11-08 premiere of <em>Conan</em>.) </li> <li> +"And now, driving to California, I find that I must enter a password +in order to change the time zone on my laptop clock. Evidently, +someone is out to mess up my schedule and my clock must be secured." +(Garrison Keillor, +"<a href="http://www.garrisonkeillor.com/weve-never-been-here-before/">We've +never been here before</a>", 2017-08-22) +</li> +<li> "Well, in my time zone that's all the time I have, but maybe in your time zone I haven't finished yet. So stay tuned!" (Goldie Hawn, <em>Rowan & Martin's Laugh-In</em> No. 65, 1970-03-09) -- 2.7.4

1 0

Fixed typos
by Dominique Pellé Aug. 21, 2017

Aug. 21, 2017

Hi Following patch fixes various typos: diff --git a/asia b/asia index e26ef1b..7518e0c 100644 --- a/asia +++ b/asia @@ -900,7 +900,7 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 # From Paul Eggert (2017-04-20): # Good luck trying to nail down old timekeeping records in India. # "... in the nineteenth century ... Madras Observatory took its magnetic -# measurements in Göttingen time, its meterological measurements on Madras +# measurements in Göttingen time, its metrological measurements on Madras # (local) time, dropped its time ball on Greenwich (ocean navigator's) time, # and distributed civil (local time)." -- Bartky IR. Selling the time: # 19th-century timekeeping in america. Stanford U Press (2000), 247 note 19. @@ -917,7 +917,7 @@ Zone Asia/Dili 8:22:20 - LMT 1912 Jan 1 # # "In 1870 ... Madras time - 'now used by the telegraph and regulated from the # only government observatory' - was suggested as a standard railway time, -# first to be dopted on the Great Indian Peninsular Railway (GIPR).... +# first to be adopted on the Great Indian Peninsular Railway (GIPR).... # Calcutta, Bombay, and Karachi, were to be allowed to continue with their # local time for civil purposes." - Prasad R. Tracks of Change: Railways and # Everyday Life in Colonial India. Cambridge University Press (2016), 145. diff --git a/australasia b/australasia index 6bf0f0a..1e38db7 100644 --- a/australasia +++ b/australasia @@ -1306,7 +1306,7 @@ Zone Pacific/Wallis 12:15:20 - LMT 1901 # http://abc.net.au/news/regionals/neweng/monthly/regeng-22jul1999-1.htm # (1999-07-22). For now, we'll wait to see if this really happens. # -# Victoria will following NSW. See: +# Victoria will follow NSW. See: # Vic to extend daylight saving (1999-07-28) # http://abc.net.au/local/news/olympics/1999/07/item19990728112314_1.htm # diff --git a/backzone b/backzone index 69f6a95..255c4a6 100644 --- a/backzone +++ b/backzone @@ -559,7 +559,7 @@ Zone Europe/Guernsey -0:10:09 - LMT 1913 Jun 18 # Time Act in 1883 and including additional confirmation of some of # the dates of the 'Summer Time' orders originating at # Westminster. There is a little uncertainty as to the starting date -# of the first summer time in 1916 which may have be announced a +# of the first summer time in 1916 which may have been announced a # couple of days late. There is still a substantial number of # documents to work through, but it is thought that every GB change # was also implemented on the island. diff --git a/europe b/europe index 0620db6..8cc55e8 100644 --- a/europe +++ b/europe @@ -2303,7 +2303,7 @@ Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct # http://itar-tass.com/obschestvo/1333711 # http://www.pravo.gov.ru:8080/page.aspx?111660 # http://www.kremlin.ru/acts/46279 -# From October 26, 2014 the new Russian time zone map will looks like this: +# From October 26, 2014 the new Russian time zone map will look like this: # http://www.worldtimezone.com/dst_news/dst_news_russia-map-2014-07.html # From Paul Eggert (2006-03-22): diff --git a/southamerica b/southamerica index 6038c3b..a07da71 100644 --- a/southamerica +++ b/southamerica @@ -1076,7 +1076,7 @@ Zone America/Rio_Branco -4:31:12 - LMT 1914 # the following source, cited by Oscar van Vlijmen (2006-10-08): # [1] Chile Law # http://www.webexhibits.org/daylightsaving/chile.html -# This contains a copy of a this official table: +# This contains a copy of this official table: # Cambios en la hora oficial de Chile desde 1900 (retrieved 2008-03-30) # http://web.archive.org/web/20080330200901/http://www.horaoficial.cl/cambio.… # [1] needs several corrections, though.

6 7

Fiji DST change
by Dominic Fok Aug. 21, 2017

Aug. 21, 2017

Hi all, Here is a daylight saving order for Fiji DST in 2018 to finish on the 14th, rather than the 21st (local time). I believe IATA have also sent out a similar memo. Could tzdatabase be updated please? Thanks, D Good planets are hard to find - please think of the environment before you print this email. ____________________________________________________________________ CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Air New Zealand immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Air New Zealand. _____________________________________________________________________ For more information on the Air New Zealand Group, visit us online at http://www.airnewzealand.com _____________________________________________________________________

3 2

Madras Observatory reports [RE: Fixed typos]
by Gent, R.H. van (Rob) Aug. 20, 2017

Aug. 20, 2017

In the 19th century it was quite common for an astronomical observatory to also make meteorological and magnetic observations. https://archive.org/details/meteorological1841to45madruoft https://archive.org/details/magneticalobser00indgoog The 19th-century Madras Observatory reports can be found at http://adsabs.harvard.edu/historical.html Rob van Gent -----Original Message----- From: tz-bounces(a)iana.org [mailto:tz-bounces@iana.org] On Behalf Of J William Piggott Sent: 20 August 2017 14:22 To: Ice Karma (J. Connell) 「氷宿縁」; Time Zone Mailing List Subject: Re: [tz] Fixed typos On 08/20/2017 12:17 AM, Ice Karma (J. Connell) 7¿ wrote: > I suspect "meterological" in the first diff hunk should actually read > "meteorological", rather than "metrological". It seems unlikely that the Madras Observatory was making weather reports. I imagine the author intended to write "astronomical" measurements. However, since it is written as a direct quote the mistake should be left as is, possibly with [sic]? > > â¬Ice Karma >

1 0

Syntax highlighting for Sublime Text
by Gilmore Davidson Aug. 16, 2017

Aug. 16, 2017

Hi, I’ve created some tzdata syntax highlighting rules for the Sublime Text editor: https://packagecontrol.io/packages/zoneinfo <https://packagecontrol.io/packages/zoneinfo> I have no idea if anyone other than me uses that particular text editor for looking at tzdata files. But I thought I’d mention it just in case it’s useful to someone. Cheers, Gil

3 3

[PROPOSED] * NEWS: Add "Briefly:" for changes so far.
by Paul Eggert Aug. 10, 2017

Aug. 10, 2017

--- NEWS | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/NEWS b/NEWS index 69b6a8b..808959a 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ News for the tz database Unreleased, experimental changes + Briefly: Namibia switches from +01/+02 to +02 on 2018-04-01. + Turks & Caicos switches from -04 to -05/-04 on 2018-11-04. + A new file tzdata.zi now holds a small text copy of all data. + The zic input format has been regularized slightly. + Changes to future time stamps Namibia will switch from +01 with DST to +02 all year on -- 2.7.4

1 0

Namibia to change time zone/go permanent DST
by Steffen Thorsen Aug. 10, 2017

Aug. 10, 2017

Namibia is going to change their time zone to what is now their DST: https://www.newera.com.na/2017/02/23/namibias-winter-time-might-be-repealed/ This video is from the government decision: https://www.nbc.na/news/na-passes-namibia-time-bill-repealing-1994-namibia-… We have made the assumption so far that they will change their time zone at the same time they would normally start DST, the first Sunday in September: https://www.timeanddate.com/news/time/namibia-new-time-zone.html Best regards, Steffen

4 6

Israel POSIX timezone string error on release 2017b?
by André Domingos Brízido Aug. 8, 2017

Aug. 8, 2017

Hello According to the Linux manual (http://man7.org/linux/man-pages/man5/tzfile.5.html) the last line of the time zone database may contain the POSIX timezone string, which is the case of the files generated by following the instructions in https://www.iana.org/time-zones/repository/tz-link.html I've downloaded the latest release (2017b) and I obtain the following POSIX string for Israel: [/usr/share/zoneinfo]# tail -n 1 Israel IST-2IDT,M3.4.4/26,M10.5.0 But if I understood correctly, the POSIX specification (http://pubs.opengroup.org/onlinepubs/9699919799/) states that the value '26' is out of range. It should be between zero and 24. My linux system does not display the correct timezone if I use the string 'IST-2IDT,M3.4.4/26,M10.5.0' as the contents of /etc/TZ. Best regards Andre Brizido

4 6

[PROPOSED] Improve tzfile.5 formatting and clarity
by Paul Eggert Aug. 7, 2017

Aug. 7, 2017

* tzfile.5: Break out field descriptions into bulleted lists, to make them easier to follow. This does not change the technical content of the spec, just its presentation. --- tzfile.5 | 77 ++++++++++++++++++++++++++++++++++++++++------------------------ 1 file changed, 48 insertions(+), 29 deletions(-) diff --git a/tzfile.5 b/tzfile.5 index 52c5301..b7dc828 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -10,17 +10,29 @@ tzfile \- time zone information \\$3\*(lq\\$1\*(rq\\$2 .. The time zone information files used by -.IR tzset (3) -begin with the magic characters "TZif" to identify them as -time zone information files, -followed by a character identifying the version of the file's format -(as of 2013, either an ASCII NUL, or '2', or '3') -followed by fifteen bytes containing zeroes reserved for future use, -followed by six four-byte integer values +.BR tzset (3) +are typically found under a directory with a name like +.IR /usr/share/zoneinfo . +These files begin with a 44-byte header containing the following fields: +.IP * 2 +The magic four-byte ASCII sequence +.q "TZif" +identifies the file as a time zone information file. +.IP * +A byte identifying the version of the file's format +(as of 2017, either an ASCII NUL, or +.q "2", +or +.q "3" ). +.IP * +Fifteen bytes containing zeros reserved for future use. +.IP * +Six four-byte integer values written in a standard byte order (the high-order byte of the value is written first). These values are, in order: +.RS .TP .I tzh_ttisgmtcnt The number of UT/local indicators stored in the file. @@ -40,28 +52,30 @@ The number of local time types for which data entries are stored in the file (must not be zero). .TP .I tzh_charcnt -The number of characters of time zone abbreviation strings +The number of bytes of time zone abbreviation strings stored in the file. +.RE .PP -The above header is followed by +The above header is followed by the following fields, whose lengths +vary depend on the contents of the header: +.IP * 2 .I tzh_timecnt four-byte signed integer values sorted in ascending order. These values are written in standard byte order. Each is used as a transition time (as returned by -.IR time (2)) +.BR time (2)) at which the rules for computing local time change. -Next come +.IP * .I tzh_timecnt one-byte unsigned integer values; each one tells which of the different types of local time types described in the file is associated with the time period starting with the same-indexed transition time. -These values serve as indices into an array of -.I ttinfo -structures (with +These values serve as indices into the next field. +.IP * .I tzh_typecnt -entries) that appears next in the file; -these structures are defined as follows: +.I ttinfo +entries, each defined as follows: .in +.5i .sp .nf @@ -87,20 +101,19 @@ gives the number of seconds to be added to UT, tells whether .I tm_isdst should be set by -.I localtime (3) +.BR localtime (3) and .I tt_abbrind -serves as an index into the array of time zone abbreviation characters +serves as an index into the array of time zone abbreviation bytes that follow the .I ttinfo structure(s) in the file. -.PP -Then there are +.IP * .I tzh_leapcnt pairs of four-byte values, written in standard byte order; the first value of each pair gives the nonnegative time (as returned by -.IR time(2)) +.BR time (2)) at which a leap second occurs; the second gives the .I total @@ -109,16 +122,14 @@ starting at the given time. The pairs of values are sorted in ascending order by time. Each transition is for one leap second, either positive or negative; transitions always separated by at least 28 days minus 1 second. -.PP -Then there are +.IP * .I tzh_ttisstdcnt standard/wall indicators, each stored as a one-byte value; they tell whether the transition times associated with local time types were specified as standard time or wall clock time, and are used when a time zone file is used in handling POSIX-style time zone environment variables. -.PP -Finally there are +.IP * .I tzh_ttisgmtcnt UT/local indicators, each stored as a one-byte value; they tell whether the transition times associated with local time types @@ -126,7 +137,9 @@ were specified as UT or local time, and are used when a time zone file is used in handling POSIX-style time zone environment variables. .PP -.I Localtime +The +.BR localtime (3) +function uses the first standard-time .I ttinfo structure in the file @@ -137,11 +150,12 @@ if either .I tzh_timecnt is zero or the time argument is less than the first transition time recorded in the file. -.PP +.SS Version 2 format For version-2-format time zone files, the above header and data are followed by a second header and data, identical in format except that eight bytes are used for each transition time or leap second time. +(Leap second counts remain four bytes.) After the second header and data comes a newline-enclosed, POSIX-TZ-environment-variable-style string for use in handling instants after the last transition time stored in the file @@ -154,7 +168,7 @@ then if a last transition time is in July, the transition's local time type must specify a daylight-saving time abbreviated .q "WEST" that is one hour east of UT. -.PP +.SS Version 3 format For version-3-format time zone files, the POSIX-TZ-style string may use two minor extensions to the POSIX TZ format, as described in .IR newtzset (3). @@ -166,6 +180,11 @@ between daylight saving and standard time. .PP Future changes to the format may append more data. .SH SEE ALSO -newctime(3), newtzset(3), zdump(8), zic(8) +.BR time (2), +.BR localtime (3), +.BR tzset (3), +.BR tzselect (8), +.BR zdump (8), +.BR zic (8) .\" This file is in the public domain, so clarified as of .\" 1996-06-05 by Arthur David Olson. -- 2.7.4

2 3

[PROPOSED] Minor tz-link updates.
by Paul Eggert Aug. 1, 2017

Aug. 1, 2017

* tz-link.htm: Add Noda Time updater. Add a downloading header, and simplify text editor discussion. --- tz-link.htm | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index 803727b..589c781 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -10,7 +10,7 @@ content="Sources for time zone and daylight saving time data"> <meta name="DC.Creator" content="Eggert, Paul"> <meta name="DC.Contributor" content="Olson, Arthur David"> -<meta name="DC.Date" content="2017-07-08"> +<meta name="DC.Date" content="2017-08-01"> <meta name="DC.Description" content="Sources of information about time zones and daylight saving time"> <meta name="DC.Identifier" @@ -105,6 +105,7 @@ Universal Time</a> (<abbr>UTC</abbr>). The database also records when daylight saving time was in use, along with some time zone abbreviations such as <abbr>EST</abbr> for Eastern Standard Time in the <abbr>US</abbr>.</p> +<h2 id="download">Downloading the <code><abbr>tz</abbr></code> database</h2> <p> The following <a href="https://en.wikipedia.org/wiki/Unix_shell">shell</a> commands download @@ -196,9 +197,10 @@ title="International Components for Unicode">ICU</abbr></a>, <a href="https://developer.ibm.com/javasdk/support/dst/jtzu/"><abbr>IBM</abbr></a> and <a href="http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html">Oracle</a> -Java, <a href="http://www.joda.org/joda-time/tz_update.html">Joda-Time</a>, +Java, <a href="http://www.joda.org/joda-time/tz_update.html">Joda-Time</a>, <a +href="https://dev.mysql.com/doc/refman/en/time-zone-support.html">MySQL</a>, and <a -href="https://dev.mysql.com/doc/refman/en/time-zone-support.html">MySQL</a>. +href="http://nodatime.org/userguide/tzdb">Noda Time</a> (see below). </p> <p>Sources for the <code><abbr>tz</abbr></code> database are <a href="https://en.wikipedia.org/wiki/UTF-8"><abbr @@ -209,14 +211,11 @@ title="linefeed">LF</abbr></a>, which can be modified by common text editors such as <a href="https://www.gnu.org/software/emacs/">GNU Emacs</a>, <a href="https://wiki.gnome.org/Apps/Gedit">gedit</a>, and -<a href="http://www.vim.org">vim</a>. One -editor has a package to simplify editing further:</p> -<ul> -<li><a href="https://packagecontrol.io/packages/zoneinfo">Sublime -zoneinfo</a> is a <a href="http://www.sublimetext.com">Sublime -Text</a> package for syntax highlighting <code><abbr>tz</abbr></code> -source files.</li> -</ul> +<a href="http://www.vim.org">vim</a>. The <a +href="http://www.sublimetext.com">Sublime Text</a> editor has +a <a href="https://packagecontrol.io/packages/zoneinfo">Sublime +zoneinfo</a> package to simplify editing further. +</p> <p> For further information about updates, please see <a href="https://tools.ietf.org/html/rfc6557">Procedures for -- 2.7.4

1 0

[PROPOSED] Detroit did not observe DST in 1967
by Paul Eggert July 27, 2017

July 27, 2017

* NEWS: Document this. * northamerica (Detroit): Remove bogus 1967 rules that were taken from Shanks. --- NEWS | 2 ++ northamerica | 15 +++++++++++++-- 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 64d5c91..93633a5 100644 --- a/NEWS +++ b/NEWS @@ -4,6 +4,8 @@ Unreleased, experimental changes Changes to past time stamps + Detroit did not observe DST in 1967. + Use railway time for Asia/Kolkata before 1941, by switching to Madras local time (UT +052110) in 1870, then to IST (UT +0530) in 1906. Also, treat 1941-2's +0630 as DST, like 1942-5. diff --git a/northamerica b/northamerica index 651681d..b42aeb4 100644 --- a/northamerica +++ b/northamerica @@ -1040,12 +1040,23 @@ Zone America/Kentucky/Monticello -5:39:24 - LMT 1883 Nov 18 12:20:36 # one hour in 1914." This change is not in Shanks. We have no more # info, so omit this for now. # +# From Paul Eggert (2017-07-26): +# Although Shanks says Detroit observed DST in 1967 from 06-14 00:01 +# until 10-29 00:01, I now see multiple reports that this is incorrect. +# For example, according to a 50-year anniversary report about the 1967 +# Detroit riots and a major-league doubleheader on 1967-07-23, "By the time +# the last fly ball of the doubleheader settled into the glove of leftfielder +# Lenny Green, it was after 7 p.m. Detroit did not observe daylight saving +# time, so light was already starting to fail. Twilight was made even deeper +# by billowing columns of smoke that ascended in an unbroken wall north of the +# ballpark." See: Dow B. Detroit '67: As violence unfolded, Tigers played two +# at home vs. Yankees. Detroit Free Press 2017-07-23. +# http://www.freep.com/story/sports/mlb/tigers/2017/07/23/detroit-tigers-1967… +# # Most of Michigan observed DST from 1973 on, but was a bit late in 1975. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER Rule Detroit 1948 only - Apr lastSun 2:00 1:00 D Rule Detroit 1948 only - Sep lastSun 2:00 0 S -Rule Detroit 1967 only - Jun 14 2:00 1:00 D -Rule Detroit 1967 only - Oct lastSun 2:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Detroit -5:32:11 - LMT 1905 -6:00 - CST 1915 May 15 2:00 -- 2.13.3

1 0

Re: [tz] libc-2.25.90.pot
by Paul Eggert July 20, 2017

July 20, 2017

On 07/20/2017 07:57 AM, Siddhesh Poyarekar wrote: > Oh I meant PRIdLINENO, not PRIdMAX. I suppose using PRIdMAX directly > might work since gettext seems to recognize the other PRI* macros. Yes, PRIdMAX should work. The zic.c code uses the macro (as opposed to just %jd) to be portable to pre-C99 libraries. I installed the attached patch into the upstream tzdb sources; the zic.c part of it should work for glibc too. Thanks for reporting the problem.

1 0

[PROPOSED] Use more up-to-date citation for leap seconds
by Paul Eggert July 18, 2017

July 18, 2017

* leapseconds.awk: Cite Levine 2016 instead of Quinn 1991. --- leapseconds.awk | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/leapseconds.awk b/leapseconds.awk index 405ce3a..66eb64d 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -17,11 +17,9 @@ BEGIN { print "# The International Earth Rotation and Reference Systems Service" print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1" print "# (which measures the true angular orientation of the earth in space); see" - print "# Terry J Quinn, The BIPM and the accurate measure of time," - print "# Proc IEEE 79, 7 (July 1991), 894-905 <http://dx.doi.org/10.1109/5.84965>," - print "# reprinted in: Hackman C, Sullivan DB (eds), Time and frequency measurement," - print "# American Association of Physics Teachers (1996)," - print "# <http://tf.nist.gov/general/pdf/1168.pdf>, 75-86." + print "# Levine J. Coordinated Universal Time and the leap second." + print "# URSI Radio Sci Bull. 2016;89(4):30-6. doi:10.23919/URSIRSB.2016.7909995" + print "# http://ieeexplore.ieee.org/document/7909995/" print "# There were no leap seconds before 1972, because the official mechanism" print "# accounting for the discrepancy between atomic time and the earth's rotation" print "# did not exist until the early 1970s." -- 2.7.4

3 3

Pedantic correction to Theory regarding size of time zone names
by Howard Hinnant July 16, 2017

July 16, 2017

Line 91 of Theory: https://github.com/eggert/tz/blob/master/Theory#L91 reads: > A file name component must not exceed 14 characters … I found one exception to this rule: The Link: Canada/East-Saskatchewan in backward. East-Saskatchewan is 17 characters. I recommend simply changing the 14 to 17. Howard

4 5

Unix time_t hits 1.5Gs early Friday UTC
by Brian Inglis July 14, 2017

July 14, 2017

Unix time_t will hit 1 500 000 000 at 2017 Jul 14 Fri 02:40:00+0000 which is Thursday evening in North America: $ for city in Vancouver Edmonton Regina Winnipeg Toronto Halifax St_Johns; do TZ=America/$city date -d@1500000000 +%c\ %Z; done 2017 Jul 13 Thu 19:40:00 PDT 2017 Jul 13 Thu 20:40:00 MDT 2017 Jul 13 Thu 20:40:00 CST 2017 Jul 13 Thu 21:40:00 CDT 2017 Jul 13 Thu 22:40:00 EDT 2017 Jul 13 Thu 23:40:00 ADT 2017 Jul 14 Fri 00:10:00 NDT and on some other time scales, which may not be aligned to UTC: $ gpstime.sh @1500000000 2017 Jul 14 Fri 02:40:00+0000 JD 2457948.611111 MJD 57948.111111 ToD 9599 NTP 3708988800 Unix 1500000000 TAI-UTC 37 TAI-GPS 19 GPS-UTC 18 GPS We 1957 Cy 1 Wn 933 Wa 165 ToW 441618 DoW 5 ToD 9618 As usual there will be some Europeans staying up late to celebrate and party. Unix time won't hit 1.5Gis until: $ gpstime.sh @`bc <<< 2^30*3/2` 2021 Jan 14 Thu 08:25:36+0000 JD 2459228.851111 MJD 59228.351111 ToD 30336 NTP 3819601536 Unix 1610612736 TAI-UTC 37 TAI-GPS 19 GPS-UTC 18 GPS We 2140 Cy 2 Wn 92 Wa 92 ToW 375954 DoW 4 ToD 30354 and it will be a while before it hits 2Gs: $ gpstime.sh @2000000000 2033 May 18 Wed 03:33:20+0000 JD 2463735.648148 MJD 63735.148148 ToD 12799 NTP 4208988800 Unix 2000000000 TAI-UTC 37 TAI-GPS 19 GPS-UTC 18 GPS We 2784 Cy 2 Wn 736 Wa 224 ToW 272018 DoW 3 ToD 12818 -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

3 2

Use GST abbreviation for Asia/Dubai, Asia/Muscat
by Mohamed Akram July 14, 2017

July 14, 2017

I noticed Asia/Dubai and Asia/Muscat currently use +04, but there is an existing abbreviation (GST - Gulf Standard Time).

3 3

Etc/GMT timezone offsets are inverted
by Pedro A. López-Valencia July 11, 2017

July 11, 2017

I just noticed that all GMT+- timezones are inverted so that GMT+5 is really GMT-5. This applies to all GMT-offset timezone definitions. -- https://about.me/palopezv

2 1

IERS Bulletin C54
by Michael Deckers July 11, 2017

July 11, 2017

The IERS has issued Bulletin C54 which assures that no leap second will occur near 2018-01-01. Interestingly, the issue date 2017-07-06 in the txt version at [https://datacenter.iers.org/eop/-/somos/5Rgv/getTX/16/bulletinc-054.txt] differs from the issue date 2017-07-09 in the xml version at [https://datacenter.iers.org/eop/-/somos/5Rgv/latestXL/16/bulletinc-054.txt/…] Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

5 7

backzone/Europe/Guernsey
by Michael Deckers July 10, 2017

July 10, 2017

For the connoisseurs of olde time stamps: The "LMT location" for backzone/Europe/Guernsey is given as "49.27N -2.33E" -- seemingly in degrees and decimal fractions of degrees. But the point ( +49.27°, -2.33° ) = ( +49°16′12″, -002°19′48″ ) is in open waters about 15 km south of Guernsey and east of Sark in the Channel. The point ( +49°27′, -002°33′ ), however, is in St Peter Port on the island, so that arc minutes and not hundredths of degrees must be meant. This also agrees with zone.tab. Hence: -# LMT Location - 49.27N -2.33E - St.Peter Port +# LMT Location - 49°27′N -2°33′E - St.Peter Port -Zone Europe/Guernsey -0:09:19 - LMT 1913 Jun 18 +Zone Europe/Guernsey -0:10:12 - LMT 1913 Jun 18 Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 3

Re: [tz] TZ & AIX
by Paul Eggert July 8, 2017

July 8, 2017

Jorge Fábregas wrote: > https://www.ibm.com/developerworks/aix/library/au-aix-olson-time-zone/index… Thanks for the heads-up. I installed the attached.

2 1

Orillia's 1912 DST pops up again in Toronto Star
by Paul Eggert July 8, 2017

July 8, 2017

Today's Toronto Star reports on the two-week daylight saving time interlude in Orillia, Ontario. Today's article doesn't mention the same newspaper's 1997-10-14 article on the same topic, and it's not clear what's new this time around. Still, the story is amusingly told. Proposed patch attached.

1 0

DST in the (odd) news
by Arthur David Olson July 7, 2017

July 7, 2017

"Alarm clock removed from family's home after 14 years of daily beeping" "Over the years, it beeped at 6.50pm or 7.50pm each day, depending on whether Daylight [Saving] Time was in place." https://www.theguardian.com/us-news/2017/jul/07/alarm-clock-wall-pennsylvan… @dashdashado

1 0

[PROPOSED] Avoid zic problems with errno == EOVERFLOW
by Paul Eggert June 26, 2017

June 26, 2017

Although this patch does not fix any bugs, it makes zic’s ‘stat’ calls less likely to fail unnecessarily with errno == EOVERFLOW, and this should be a bit faster in some cases. Problem reported by Nick Alcock in: https://sourceware.org/ml/libc-alpha/2017-06/msg01264.html * private.h (_FILE_OFFSET_BITS, _LARGE_FILES) (_DARWIN_USE_64_BIT_INODE): New macros. --- private.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/private.h b/private.h index f5e39b5..2e8415e 100644 --- a/private.h +++ b/private.h @@ -102,6 +102,16 @@ /* Enable strtoimax on pre-C99 Solaris 11. */ #define __EXTENSIONS__ 1 +/* To avoid having 'stat' fail unnecessarily with errno == EOVERFLOW, + enable large files on GNUish systems ... */ +#ifndef _FILE_OFFSET_BITS +# define _FILE_OFFSET_BITS 64 +#endif +/* ... and on AIX ... */ +#define _LARGE_FILES 1 +/* ... and enable large inode numbers on Mac OS X 10.5 and later. */ +#define _DARWIN_USE_64_BIT_INODE 1 + /* ** Nested includes */ -- 2.9.4

1 0

[PROPOSED] Port to GCC 4.8.4
by Paul Eggert June 16, 2017

June 16, 2017

Problem reported by Stan Shebs and Joseph Myers in: https://sourceware.org/ml/libc-alpha/2017-06/msg00741.html * NEWS, Makefile: Document this. * private.h (HAVE_GENERIC): New macro, so that we do not use _Generic with GCC 4.8. (TIME_T_MIN_NO_PADDING, TIME_T_MAX_NO_PADDING): New macros. (TIME_T_MIN, TIME_T_MAX): Rename from time_t_min and time_t_max, and turn them into macros so that problems are less likely to occur for subset uses like glibc where these macros are never expanded. All uses changed. Use new macros to work around GCC 4.8 bug. --- Makefile | 1 + NEWS | 3 +++ date.c | 2 +- localtime.c | 26 +++++++++++++------------- private.h | 60 ++++++++++++++++++++++++++++++++++++++++-------------------- 5 files changed, 58 insertions(+), 34 deletions(-) diff --git a/Makefile b/Makefile index 2b31f3f..347ece7 100644 --- a/Makefile +++ b/Makefile @@ -142,6 +142,7 @@ LDLIBS= # -DHAVE_DECL_ASCTIME_R=0 if <time.h> does not declare asctime_r # -DHAVE_DECL_ENVIRON if <unistd.h> declares 'environ' # -DHAVE_DIRECT_H if mkdir needs <direct.h> (MS-Windows) +# -DHAVE_GENERIC=0 if _Generic does not work # -DHAVE_GETTEXT if 'gettext' works (e.g., GNU/Linux, FreeBSD, Solaris) # -DHAVE_INCOMPATIBLE_CTIME_R if your system's time.h declares # ctime_r and asctime_r incompatibly with the POSIX standard diff --git a/NEWS b/NEWS index ca4fd8e..cfdd620 100644 --- a/NEWS +++ b/NEWS @@ -94,6 +94,9 @@ Unreleased, experimental changes zdump.c no longer assumes snprintf. (Reported by Jonathan Leffler.) + Calculation of time_t extrema works around a bug in GCC 4.8.4 + (Reported by Stan Shebs and Joseph Myers.) + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) diff --git a/date.c b/date.c index b29e162..2cc533f 100644 --- a/date.c +++ b/date.c @@ -97,7 +97,7 @@ main(const int argc, char *argv[]) secs = strtoimax (optarg, &endarg, 0); if (*endarg || optarg == endarg) errno = EINVAL; - else if (! (time_t_min <= secs && secs <= time_t_max)) + else if (! (TIME_T_MIN <= secs && secs <= TIME_T_MAX)) errno = ERANGE; if (errno) { perror(optarg); diff --git a/localtime.c b/localtime.c index 8c944f3..2e1d621 100644 --- a/localtime.c +++ b/localtime.c @@ -464,17 +464,17 @@ tzloadbody(char const *name, struct state *sp, bool doextend, sp->charcnt = charcnt; /* Read transitions, discarding those out of time_t range. - But pretend the last transition before time_t_min - occurred at time_t_min. */ + But pretend the last transition before TIME_T_MIN + occurred at TIME_T_MIN. */ timecnt = 0; for (i = 0; i < sp->timecnt; ++i) { int_fast64_t at = stored == 4 ? detzcode(p) : detzcode64(p); - sp->types[i] = at <= time_t_max; + sp->types[i] = at <= TIME_T_MAX; if (sp->types[i]) { time_t attime - = ((TYPE_SIGNED(time_t) ? at < time_t_min : at < 0) - ? time_t_min : at); + = ((TYPE_SIGNED(time_t) ? at < TIME_T_MIN : at < 0) + ? TIME_T_MIN : at); if (timecnt && attime <= sp->ats[timecnt - 1]) { if (attime < sp->ats[timecnt - 1]) return EINVAL; @@ -524,7 +524,7 @@ tzloadbody(char const *name, struct state *sp, bool doextend, /* Leap seconds cannot occur before the Epoch. */ if (tr < 0) return EINVAL; - if (tr <= time_t_max) { + if (tr <= TIME_T_MAX) { /* Leap seconds cannot occur more than once per UTC month, and UTC months are at least 28 days long (minus 1 second for a negative leap second). Each leap second's @@ -1795,12 +1795,12 @@ increment_overflow_time(time_t *tp, int_fast32_t j) { /* ** This is like - ** 'if (! (time_t_min <= *tp + j && *tp + j <= time_t_max)) ...', + ** 'if (! (TIME_T_MIN <= *tp + j && *tp + j <= TIME_T_MAX)) ...', ** except that it does the right thing even if *tp + j would overflow. */ if (! (j < 0 - ? (TYPE_SIGNED(time_t) ? time_t_min - j <= *tp : -1 - j < *tp) - : *tp <= time_t_max - j)) + ? (TYPE_SIGNED(time_t) ? TIME_T_MIN - j <= *tp : -1 - j < *tp) + : *tp <= TIME_T_MAX - j)) return true; *tp += j; return false; @@ -1936,8 +1936,8 @@ time2sub(struct tm *const tmp, /* ** Do a binary search (this works whatever time_t's type is). */ - lo = time_t_min; - hi = time_t_max; + lo = TIME_T_MIN; + hi = TIME_T_MAX; for ( ; ; ) { t = lo / 2 + hi / 2; if (t < lo) @@ -1954,12 +1954,12 @@ time2sub(struct tm *const tmp, } else dir = tmcomp(&mytm, &yourtm); if (dir != 0) { if (t == lo) { - if (t == time_t_max) + if (t == TIME_T_MAX) return WRONG; ++t; ++lo; } else if (t == hi) { - if (t == time_t_min) + if (t == TIME_T_MIN) return WRONG; --t; --hi; diff --git a/private.h b/private.h index 2b07251..f5e39b5 100644 --- a/private.h +++ b/private.h @@ -27,6 +27,21 @@ #define HAVE_DECL_ASCTIME_R 1 #endif +#if !defined HAVE_GENERIC && defined __has_extension +# if __has_extension(c_generic_selections) +# define HAVE_GENERIC 1 +# else +# define HAVE_GENERIC 0 +# endif +#endif +/* _Generic is buggy in pre-4.9 GCC. */ +#if !defined HAVE_GENERIC && defined __GNUC__ +# define HAVE_GENERIC (4 < __GNUC__ + (9 <= __GNUC_MINOR__)) +#endif +#ifndef HAVE_GENERIC +# define HAVE_GENERIC (201112 <= __STDC_VERSION__) +#endif + #ifndef HAVE_GETTEXT #define HAVE_GETTEXT 0 #endif /* !defined HAVE_GETTEXT */ @@ -561,27 +576,32 @@ time_t time2posix_z(timezone_t, time_t) ATTRIBUTE_PURE; #define MINVAL(t, b) \ ((t) (TYPE_SIGNED(t) ? - TWOS_COMPLEMENT(t) - MAXVAL(t, b) : 0)) -/* The minimum and maximum finite time values. This implementation - assumes no padding if time_t is signed and either the compiler is - pre-C11 or time_t is not one of the standard signed integer types. */ -#if 201112 <= __STDC_VERSION__ -static time_t const time_t_min - = (TYPE_SIGNED(time_t) - ? _Generic((time_t) 0, - signed char: SCHAR_MIN, short: SHRT_MIN, - int: INT_MIN, long: LONG_MIN, long long: LLONG_MIN, - default: MINVAL(time_t, TYPE_BIT(time_t))) - : 0); -static time_t const time_t_max - = (TYPE_SIGNED(time_t) - ? _Generic((time_t) 0, - signed char: SCHAR_MAX, short: SHRT_MAX, - int: INT_MAX, long: LONG_MAX, long long: LLONG_MAX, - default: MAXVAL(time_t, TYPE_BIT(time_t))) - : -1); +/* The extreme time values, assuming no padding. */ +#define TIME_T_MIN_NO_PADDING MINVAL(time_t, TYPE_BIT(time_t)) +#define TIME_T_MAX_NO_PADDING MAXVAL(time_t, TYPE_BIT(time_t)) + +/* The extreme time values. These are macros, not constants, so that + any portability problem occur only when compiling .c files that use + the macros, which is safer for applications that need only zdump and zic. + This implementation assumes no padding if time_t is signed and + either the compiler lacks support for _Generic or time_t is not one + of the standard signed integer types. */ +#if HAVE_GENERIC +# define TIME_T_MIN \ + _Generic((time_t) 0, \ + signed char: SCHAR_MIN, short: SHRT_MIN, \ + int: INT_MIN, long: LONG_MIN, long long: LLONG_MIN, \ + default: TIME_T_MIN_NO_PADDING) +# define TIME_T_MAX \ + (TYPE_SIGNED(time_t) \ + ? _Generic((time_t) 0, \ + signed char: SCHAR_MAX, short: SHRT_MAX, \ + int: INT_MAX, long: LONG_MAX, long long: LLONG_MAX, \ + default: TIME_T_MAX_NO_PADDING) \ + : (time_t) -1) #else -static time_t const time_t_min = MINVAL(time_t, TYPE_BIT(time_t)); -static time_t const time_t_max = MAXVAL(time_t, TYPE_BIT(time_t)); +# define TIME_T_MIN TIME_T_MIN_NO_PADDING +# define TIME_T_MAX TIME_T_MAX_NO_PADDING #endif /* -- 2.9.4

1 0

[PROPOSED] Port check_time_t_alternatives to June 8 AIX fix
by Paul Eggert June 16, 2017

June 16, 2017

* private.h (TZ_TIME_T): Declare strftime. This is helpful now that we use our own strftime. Declare strftime_l too, if present. --- private.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/private.h b/private.h index 982ddf3..2b07251 100644 --- a/private.h +++ b/private.h @@ -424,6 +424,12 @@ typedef time_tz tz_time_t; char *ctime(time_t const *); char *ctime_r(time_t const *, char *); double difftime(time_t, time_t) ATTRIBUTE_CONST; +size_t strftime(char *restrict, size_t, char const *restrict, + struct tm const *restrict); +# if HAVE_STRFTIME_L +size_t strftime_l(char *restrict, size_t, char const *restrict, + struct tm const *restrict, locale_t); +# endif struct tm *gmtime(time_t const *); struct tm *gmtime_r(time_t const *restrict, struct tm *restrict); struct tm *localtime(time_t const *); -- 2.9.4

1 0

Re: [tz] 1 s error in America/Adak and America/Nome
by Paul Eggert June 15, 2017

June 15, 2017

On 06/10/2017 07:42 AM, Michael H Deckers wrote: > I do not understand the evidence for the proposed changes. A change of > time scale by 24 h is only observable though the day of the week and > the day number in a calendar (which may be combined with a switch of > calendars), but not through the time of day. > > Where two successive days are observed as Sundays, this is evidence > for the change of time scale having occurred at the instant between > the two. Yes. However, the the question is whether America/Sitka should record the time kept by those in formal control of Sitka, or the time kept by Toomas Ahllund and his fellow workers who made the transition on Sunday in order to have a longer weekend. If the former, the transition should be at 15:30 Friday (Gregorian); if the latter, it should presumably be at 00:00 Sunday (Gregorian). I chose the former, partly because it reflects formal transfer of control, and partly because we have a specific time-of-day recorded for it. > And if a precise instant for the acquisition of Alaska is > to be taken as the instant of the time zone change, then this > assumption > should be applied to all locations (where nothing else is known). > But the proposed changes to tzdb amount to the change happening when > UT = 1867-10-19 + 00:41:37 h for Yakutat > UT = 1867-10-19 + 00:31:13 h for Sitka, Juneau, Metlakatla > UT = 1867-10-19 + 00:31:03 h for Adak, Nome > UT = 1867-10-19 + 00:30:59 h for Anchorage > I do not see support for such variations. Thanks for reporting that; those were due to bugs in my calculations. I installed the attached patch to fix the bugs, and to try to clarify the point you mentioned.

5 12

[PROPOSED] Remove incorrect #endif comments
by Paul Eggert June 14, 2017

June 14, 2017

--- localtime.c | 2 +- private.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/localtime.c b/localtime.c index 1f5bbb2..8c944f3 100644 --- a/localtime.c +++ b/localtime.c @@ -94,7 +94,7 @@ static const char gmt[] = "GMT"; */ #ifndef TZDEFRULESTRING #define TZDEFRULESTRING ",M3.2.0,M11.1.0" -#endif /* !defined TZDEFDST */ +#endif struct ttinfo { /* time type information */ int_fast32_t tt_gmtoff; /* UT offset in seconds */ diff --git a/private.h b/private.h index e6cb21d..982ddf3 100644 --- a/private.h +++ b/private.h @@ -33,7 +33,7 @@ #ifndef HAVE_INCOMPATIBLE_CTIME_R #define HAVE_INCOMPATIBLE_CTIME_R 0 -#endif /* !defined INCOMPATIBLE_CTIME_R */ +#endif #ifndef HAVE_LINK #define HAVE_LINK 1 -- 2.9.4

1 0

[PROPOSED] Remove old Y2K code
by Paul Eggert June 14, 2017

June 14, 2017

The circa-1996 runtime tests to catch potential Y2K problems are no longer worth the maintenance hassle, as the Y2K transition was done many years ago. * Makefile, NEWS: Mention this. * strftime.c (YEAR_2000_NAME, IN_NONE, IN_SOME, IN_THIS, IN_ALL): Remove. All uses removed. (strftime): Do not warn about Y2K problems. (_fmt): Omit last (warning) arg; all uses changed. --- Makefile | 3 --- NEWS | 2 ++ strftime.c | 71 ++++++++++++-------------------------------------------------- 3 files changed, 15 insertions(+), 61 deletions(-) diff --git a/Makefile b/Makefile index 07f4f77..65915ea 100644 --- a/Makefile +++ b/Makefile @@ -162,9 +162,6 @@ LDLIBS= # than what POSIX specifies, assuming local time is UT. # For example, N is 252460800 on AmigaOS. # -Dlocale_t=XXX if your system uses XXX instead of locale_t -# -DNO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU=1 -# if you do not want run time warnings about formats that may cause -# year 2000 grief # -Dssize_t=long on hosts like MS-Windows that lack ssize_t # -DTHREAD_SAFE to make localtime.c thread-safe, as POSIX requires; # not needed by the main-program tz code, which is single-threaded. diff --git a/NEWS b/NEWS index 2c86e90..40285bf 100644 --- a/NEWS +++ b/NEWS @@ -81,6 +81,8 @@ Unreleased, experimental changes other two variables as optional. Also, USG_COMPAT is now 1 or 0: if not defined, the code attempts to guess it from other macros. + Y2K runtime checks have been removed, as Y2K was years ago. + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows and Solaris. (Thanks to Kees Dekker for reporting the problems.) diff --git a/strftime.c b/strftime.c index 173ff8b..9df4176 100644 --- a/strftime.c +++ b/strftime.c @@ -101,19 +101,9 @@ static const struct lc_time_T C_time_locale = { static char * _add(const char *, char *, const char *); static char * _conv(int, const char *, char *, const char *); -static char * _fmt(const char *, const struct tm *, char *, const char *, - int *); +static char * _fmt(const char *, const struct tm *, char *, const char *); static char * _yconv(int, int, bool, bool, char *, char const *); -#ifndef YEAR_2000_NAME -#define YEAR_2000_NAME "CHECK_STRFTIME_FORMATS_FOR_TWO_DIGIT_YEARS" -#endif /* !defined YEAR_2000_NAME */ - -#define IN_NONE 0 -#define IN_SOME 1 -#define IN_THIS 2 -#define IN_ALL 3 - #if HAVE_STRFTIME_L size_t strftime_l(char *s, size_t maxsize, char const *format, struct tm const *t, @@ -128,24 +118,9 @@ size_t strftime(char *s, size_t maxsize, const char *format, const struct tm *t) { char * p; - int warn; tzset(); - warn = IN_NONE; - p = _fmt(format, t, s, s + maxsize, &warn); -#ifndef NO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU - if (warn != IN_NONE && getenv(YEAR_2000_NAME) != NULL) { - fprintf(stderr, "\n"); - fprintf(stderr, "strftime format \"%s\" ", format); - fprintf(stderr, "yields only two digits of years in "); - if (warn == IN_SOME) - fprintf(stderr, "some locales"); - else if (warn == IN_THIS) - fprintf(stderr, "the current locale"); - else fprintf(stderr, "all locales"); - fprintf(stderr, "\n"); - } -#endif /* !defined NO_RUN_TIME_WARNINGS_ABOUT_YEAR_2000_PROBLEMS_THANK_YOU */ + p = _fmt(format, t, s, s + maxsize); if (p == s + maxsize) return 0; *p = '\0'; @@ -153,8 +128,7 @@ strftime(char *s, size_t maxsize, const char *format, const struct tm *t) } static char * -_fmt(const char *format, const struct tm *t, char *pt, - const char *ptlim, int *warnp) +_fmt(const char *format, const struct tm *t, char *pt, const char *ptlim) { for ( ; *format; ++format) { if (*format == '%') { @@ -200,18 +174,10 @@ label: true, false, pt, ptlim); continue; case 'c': - { - int warn2 = IN_SOME; - - pt = _fmt(Locale->c_fmt, t, pt, ptlim, &warn2); - if (warn2 == IN_ALL) - warn2 = IN_THIS; - if (warn2 > *warnp) - *warnp = warn2; - } + pt = _fmt(Locale->c_fmt, t, pt, ptlim); continue; case 'D': - pt = _fmt("%m/%d/%y", t, pt, ptlim, warnp); + pt = _fmt("%m/%d/%y", t, pt, ptlim); continue; case 'd': pt = _conv(t->tm_mday, "%02d", pt, ptlim); @@ -232,7 +198,7 @@ label: pt = _conv(t->tm_mday, "%2d", pt, ptlim); continue; case 'F': - pt = _fmt("%Y-%m-%d", t, pt, ptlim, warnp); + pt = _fmt("%Y-%m-%d", t, pt, ptlim); continue; case 'H': pt = _conv(t->tm_hour, "%02d", pt, ptlim); @@ -296,10 +262,10 @@ label: pt, ptlim); continue; case 'R': - pt = _fmt("%H:%M", t, pt, ptlim, warnp); + pt = _fmt("%H:%M", t, pt, ptlim); continue; case 'r': - pt = _fmt("%I:%M:%S %p", t, pt, ptlim, warnp); + pt = _fmt("%I:%M:%S %p", t, pt, ptlim); continue; case 'S': pt = _conv(t->tm_sec, "%02d", pt, ptlim); @@ -322,7 +288,7 @@ label: } continue; case 'T': - pt = _fmt("%H:%M:%S", t, pt, ptlim, warnp); + pt = _fmt("%H:%M:%S", t, pt, ptlim); continue; case 't': pt = _add("\t", pt, ptlim); @@ -424,7 +390,6 @@ label: pt = _conv(w, "%02d", pt, ptlim); else if (*format == 'g') { - *warnp = IN_ALL; pt = _yconv(year, base, false, true, pt, ptlim); @@ -439,7 +404,7 @@ label: ** "date as dd-bbb-YYYY" ** (ado, 1993-05-24) */ - pt = _fmt("%e-%b-%Y", t, pt, ptlim, warnp); + pt = _fmt("%e-%b-%Y", t, pt, ptlim); continue; case 'W': pt = _conv((t->tm_yday + DAYSPERWEEK - @@ -452,21 +417,12 @@ label: pt = _conv(t->tm_wday, "%d", pt, ptlim); continue; case 'X': - pt = _fmt(Locale->X_fmt, t, pt, ptlim, warnp); + pt = _fmt(Locale->X_fmt, t, pt, ptlim); continue; case 'x': - { - int warn2 = IN_SOME; - - pt = _fmt(Locale->x_fmt, t, pt, ptlim, &warn2); - if (warn2 == IN_ALL) - warn2 = IN_THIS; - if (warn2 > *warnp) - *warnp = warn2; - } + pt = _fmt(Locale->x_fmt, t, pt, ptlim); continue; case 'y': - *warnp = IN_ALL; pt = _yconv(t->tm_year, TM_YEAR_BASE, false, true, pt, ptlim); @@ -559,8 +515,7 @@ label: #endif continue; case '+': - pt = _fmt(Locale->date_fmt, t, pt, ptlim, - warnp); + pt = _fmt(Locale->date_fmt, t, pt, ptlim); continue; case '%': /* -- 2.9.4

8 12

Re: [tz] defensive value for define on Solaris causes load of timerule to fail
by Kees Dekker June 13, 2017

June 13, 2017

Retry, now to the mailing list as well. >> So, FILENAME_MAX is probably the better choice, but may be, a >> >> #if FILENAME_MAX < 260 >> #undef FILENAME_MAX >> #define FILENAME_MAX 260 >> #endif >> >> code part is needed? Then FILENAME_MAX is at a defined minimum value >> (of course, the limit of 260 is also quite an arbitrary choice). >I don't like the idea of redefining `FILENAME_MAX`. Just use some >reasonably large value of our choosing for the length of `fullname`. >Even with a modern GNU/Linux `FILENAME_MAX` value of 4096 (on my system >at least), the `fullname` member of `union local_storage` is smaller >than the `u` member. Anything else is also ok, but the union now does not have 'take largest value of somethong' for the fullname member. It is also ok for me to say: #if FILENAME_MAX < 260 #define TZ_FILENAME_MAX 260 #else #define TZ_FILENAME_MAX FILENAME_MAX #endif And use TZ_FILENAME_MAX in the union. My message is just to say 'please take care for platforms where FILENAME_MAX is arbitrary (too) short'. And the value of 14, as used on Solaris, is too short, as some time rules already exceed this length. It makes no sense (i.e. it does not help for the other platforms) in this case that Linux has a much bigger value for this define. As I have checked now, on most platforms, except Solaris, it is 260. Linux uses (as one of the few) a larger value. I've checked HPUX, AIX, Windows, Solaris and several Linux flavors. Kees

7 10

core dumps on AIX7.1 and HPUX11.31 and tzcode 2017B.
by Kees Dekker June 13, 2017

June 13, 2017

Hi, When using the IANA tz data and code (version 2017B) on AIX and/or HPUX, I got core dumps. I was not able to figure out the root cause, but after I had renamed the timezone, daylight and tzname variables to something else (i.e., prefixed with olson_), the error disappeared. A similar crash happened on AIX 7.2, but in only one test case (compared to all our test cases on AIX 7.1 and HPUX 11.31). I don't have a good explanation for the different behavior between AIX 7.1 and 7.2. The tz code was incorporated into two parts of our product: 1. The tzcode was built with USG_COMPAT enabled, i.e. timezone, daylight and tzname symbols are used and incorporated into our binaries 2. The tzcode was also built into a shared library that uses another shared library that calls some of the time functions from libc (e.g. tzset(), or gettimeofday()) BTW: in our code, I'm renaming (using defines) all tz functions too, and prefix them with 'olson_'. So, at symbol level, no duplicates between system functions and TZ code functions should exist. In our code, the error happened under the following circumstances: 1. A binary of us is using the tz library (using USG_COMPAT) 2. That binary loads dynamically (with dlopen(), with RTLD_GLOBAL flag) another shared library of us, also containing the tz library 3. A 3rd party shared library was loaded by our own shared library. Also with dlopen/RTLD_GLOBAL flag. Both our binary (#1) a shared library (#2) were creating using export lists/versions scripts. None of the tz code or variables was exported. And our shared library is using a flag that forces the loader to perform 'innermost symbol resolution' (in such way that C++ exceptions still work). The 3rd party library was either the Oracle or DB2 client database library. Both perform a call to libc that triggers a time function (gettimeofday() or tzset()). The core dump happens in libc, on one of the time functions, called by the 3rd party shared library. Using IANA tz functions from our binaries, without loading 3rd party shared libraries works fine. Hypothesis: the fact that the tzcode (compiled with USG_COMPAT) changes (one of) the (libc exported) timezone, daylight, tzname, causes the time functions in libc to crash. Notes: a. making timezone, daylight, tzname static in the IANA localtime.c and added a get_xxx function did not help either. b. Building without USG_COMPAT did not help either. It is quite strange that none of these both (#a and #b) did help, but I lack time to do more research. As I now have a suitable workaround (by renaming/prefixing involved variables), it is fine for me now. This mail is just intended to inform about conflicts/core dumps, most probably related to 'similar named' variables with the system libc (and thus generate a trap on some platforms). If the tz code can get changed (ever/in the future) to prevent such conflicts, it would be great. No other action is needed (by me) for now. Regards, Kees

2 5

[PROPOSED] Commentary fixes
by Paul Eggert June 12, 2017

June 12, 2017

* Makefile: Mention constraints on TZDIR_BASENAME. * asctime.c: Remove obsolete comment, as zdump now uses snprintf. --- Makefile | 1 + asctime.c | 3 --- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 05b40bb..07f4f77 100644 --- a/Makefile +++ b/Makefile @@ -49,6 +49,7 @@ TOPDIR= /usr/local # "Compiled" time zone information is placed in the "TZDIR" directory # (and subdirectories). # Use an absolute path name for TZDIR unless you're just testing the software. +# TZDIR_BASENAME should not contain "/" and should not be ".", ".." or empty. TZDIR_BASENAME= zoneinfo TZDIR= $(TOPDIR)/etc/$(TZDIR_BASENAME) diff --git a/asctime.c b/asctime.c index 1613f78..de681ce 100644 --- a/asctime.c +++ b/asctime.c @@ -99,9 +99,6 @@ asctime_r(register const struct tm *timeptr, char *buf) ** (e.g., timeptr->tm_mday) when processing "%Y". */ strftime(year, sizeof year, "%Y", timeptr); - /* - ** We avoid using snprintf since it's not available on all systems. - */ sprintf(result, ((strlen(year) <= 4) ? ASCTIME_FMT : ASCTIME_FMT_B), wn, mn, -- 2.9.4

2 2

defensive value for define on Solaris causes load of timerule to fail
by Kees Dekker June 12, 2017

June 12, 2017

Hi, The FILENAME_MAX macro, as used in the local_storage union in localtime.c, has on Solaris the very low/defensive value of 14 (from stdio.h). Please consider using PATH_MAX, from limits.h instead, as that value is (usually) 250 or beyond. Or anything else, that can hold reasonable lengths of file names. Loading zonefiles now fails on Solaris if a filename exceeds the used macro. Regards, Kees

2 2

Re: [tz] [PROPOSED] Clean up configuration of tzname etc.
by vanadovv＠hetnet.nl June 9, 2017

June 9, 2017

I found a small language error. Sorry I can't produce a diff/patch. The error can be found as follows: >----Origineel Bericht---- >Van : eggert(a)cs.ucla.edu >Datum : 09/06/2017 02:50 >Aan : tz(a)iana.org >Onderwerp : [tz] [PROPOSED] Clean up configuration of tzname etc. > ...... ...... >diff --git a/strftime.c b/strftime.c >index 4b9fd2c..d09a0db 100644 >--- a/strftime.c >+++ b/strftime.c ....... >@@ -513,20 +509,20 @@ label: > ** altzone and timezone), and the > ** magic might not have the correct > ** offset. Doing things correctly is >- ** tricky and requires disobeying C99; >+ ** tricky and requires disobeying the standard; > ** see GNU C strftime for details. > ** For now, punt and conform to the > ** standard, even though it's incorrect. > ** >- ** C99 says that %z must be replaced by the >- ** empty string if the time zone is not >+ ** C99 and later that %z must be replaced by >+ ** the empty string if the time zone is not ..... The error is: >+ ** C99 and later that %z must be replaced by This should be: >+ ** C99 and later say that %z must be replaced by --------------- Yours, Oscar van Vlijmen [ends]

2 1

1 s error in America/Adak and America/Nome
by Michael H Deckers June 9, 2017

June 9, 2017

The switch from 1867-10-18 to 1867-10-17 in Alaska is incorrectly represented as a jump from 1867-10-18 to 1867-10-17 + 00:00:01 h in the time scales for Adak and for Nome. Proposed corrections: -Zone America/Adak 12:13:21 - LMT 1867 Oct 18 +Zone America/Adak 12:13:22 - LMT 1867 Oct 18 -11:46:38 - LMT 1900 Aug 20 12:00 -Zone America/Nome 12:58:21 - LMT 1867 Oct 18 +Zone America/Nome 12:58:22 - LMT 1867 Oct 18 -11:01:38 - LMT 1900 Aug 20 12:00 Michael Deckers.

2 1

[PROPOSED] Clean up configuration of tzname etc.
by Paul Eggert June 9, 2017

June 9, 2017

This documents a bit of software archaeology better. tzname is standardized by POSIX, whereas timezone and daylight are standardized by POSIX SI, so allow them to be configured separately. * Makefile, NEWS, Theory: Document this. * date.c, strftime.c, zdump.c (tzname): Remove decl; private.h declares tzname as needed now. * localtime.c (tzname, timezone, daylight, altzone): Also define if TZ_TIME_T. However, define only if the relevant other macro (HAVE_TZNAME, USG_COMPAT, ALTZONE) is set or defined. (update_tzname_etc, settzname): Set tzname only if HAVE_TZNAME. At the end, simplify ifdef by using TZ_TIME_T. * newctime.3: Document optional vars and fields more carefully. * private.h (USG_COMPAT): Set default from _XOPEN_VERSION. All uses changed to assume it is 1 or 0. (HAVE_TZNAME): Set default from that and from _POSIX_VERSION. (TZ_TIME_T): New macro. (daylight, timezone, tzname, altzone): Rename if needed to avoid collision with standard library. (tzname): Declare if (!HAVE_POSIX_DECLS || TZ_TIME_T) && HAVE_TZNAME. (timezone, daylight): Declare if (!HAVE_POSIX_DECLS || TZ_TIME_T) && USG_COMPAT, not if not defined and !HAVE_POSIX_DECLS. (altzone): Declare even if not defined. (tzsetwall, offtime, timegm, timelocal, timeoff, time2posix) (posix2time, posix2time_z, time2posix_z): Use TZ_TIME_T instead of (defined time_tz). * strftime.c (_fmt): * zdump.c (abbr): Use tzname only if HAVE_TZNAME. --- Makefile | 37 +++++++++++++++++++++++---------- NEWS | 8 +++++++ Theory | 6 +++--- date.c | 1 - localtime.c | 34 ++++++++++++++++-------------- newctime.3 | 46 ++++++++++++++++++++++++++--------------- private.h | 69 ++++++++++++++++++++++++++++++++++++++++++++++--------------- strftime.c | 38 ++++++++++++++++------------------ zdump.c | 9 ++++---- 9 files changed, 160 insertions(+), 88 deletions(-) diff --git a/Makefile b/Makefile index 476f259..e6d497d 100644 --- a/Makefile +++ b/Makefile @@ -164,6 +164,7 @@ LDLIBS= # not needed by the main-program tz code, which is single-threaded. # Append other compiler flags as needed, e.g., -pthread on GNU/Linux. # -Dtime_tz=\"T\" to use T as the time_t type, rather than the system time_t +# This is intended for internal use only; it mangles external names. # -DTZ_DOMAIN=\"foo\" to use "foo" for gettext domain name; default is "tz" # -DTZ_DOMAINDIR=\"/path\" to use "/path" for gettext directory; # the default is system-supplied, typically "/usr/lib/locale" @@ -199,12 +200,6 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common \ -Wno-address -Wno-format-nonliteral -Wno-sign-compare \ -Wno-type-limits -Wno-unused-parameter # -# If you want to use System V compatibility code, add -# -DUSG_COMPAT -# to the end of the "CFLAGS=" line. This arrange for "timezone" and "daylight" -# variables to be kept up-to-date by the time conversion functions. Neither -# "timezone" nor "daylight" is described in X3J11's work. -# # If your system has a "GMT offset" field in its "struct tm"s # (or if you decide to add such a field in your system's "time.h" file), # add the name to a define such as @@ -216,6 +211,31 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common \ # and define NO_TM_ZONE to suppress any guessing. These two fields are not # required by POSIX, but are widely available on GNU/Linux and BSD systems. # +# The next batch of options control support for external variables +# exported by tzcode. In practice these variables are less useful +# than TM_GMTOFF and TM_ZONE. However, most of them are standardized. +# # +# # To omit or support the external variable "tzname", add one of: +# # -DHAVE_TZNAME=0 +# # -DHAVE_TZNAME=1 +# # to the "CFLAGS=" line. "tzname" is required by POSIX 1988 and later. +# # If not defined, the code attempts to guess HAVE_TZNAME from other macros. +# # Warning: unless time_tz is also defined, HAVE_TZNAME=1 can cause +# # crashes when combined with some platforms' standard libraries, +# # presumably due to memory allocation issues. +# # +# # To omit or support the external variables "timezone" and "daylight", add +# # -DUSG_COMPAT=0 +# # -DUSG_COMPAT=1 +# # to the "CFLAGS=" line; "timezone" and "daylight" are inspired by +# # Unix Systems Group code and are required by POSIX 2008 (with XSI) and later. +# # If not defined, the code attempts to guess USG_COMPAT from other macros. +# # +# # To support the external variable "altzone", add +# # -DALTZONE +# # to the end of the "CFLAGS=" line; although "altzone" appeared in +# # System V Release 3.1 it has not been standardized. +# # If you want functions that were inspired by early versions of X3J11's work, # add # -DSTD_INSPIRED @@ -253,11 +273,6 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common \ # -DALL_STATE # to the end of the "CFLAGS=" line. Storage is obtained by calling malloc. # -# If you want an "altzone" variable (a la System V Release 3.1), add -# -DALTZONE -# to the end of the "CFLAGS=" line. -# This variable is not described in X3J11's work. -# # NIST-PCTS:151-2, Version 1.4, (1993-12-03) is a test suite put # out by the National Institute of Standards and Technology # which claims to test C and Posix conformance. If you want to pass PCTS, add diff --git a/NEWS b/NEWS index 99f5d64..44135ae 100644 --- a/NEWS +++ b/NEWS @@ -57,6 +57,14 @@ Unreleased, experimental changes ordinary lines in leap second input. Formerly, zic sometimes warned about this undocumented usage and handled it incorrectly. + The new macro HAVE_TZNAME governs whether the tzname external + variable is exported, instead of USG_COMPAT. USG_COMPAT now + governs only the external variables "timezone" and "daylight". + This change is needed because the three variables are not in the + same category: although POSIX requires tzname, it specifies the + other two variables as optional. Also, USG_COMPAT is now 1 or 0: + if not defined, the code attempts to guess it from other macros. + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows. (Thanks to Kees Dekker for reporting the problems.) diff --git a/Theory b/Theory index 2bfadc6..8aeccb2 100644 --- a/Theory +++ b/Theory @@ -581,9 +581,9 @@ Points of interest to folks with other systems: 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 - tzname[localtime(&clock)->tm_isdst] to learn the correct time - zone abbreviation to use. Alternatively, use - localtime(&clock)->tm_zone if this has been enabled. + localtime(&clock)->tm_zone (if TM_ZONE is defined) or + tzname[localtime(&clock)->tm_isdst] (if HAVE_TZNAME is defined) + to learn the correct time zone abbreviation to use. * The 4.2BSD gettimeofday function is not used in this package. This formerly let users obtain the current UTC offset and DST flag, diff --git a/date.c b/date.c index 269825d..0d64b8a 100644 --- a/date.c +++ b/date.c @@ -45,7 +45,6 @@ #if !HAVE_POSIX_DECLS extern char * optarg; extern int optind; -extern char * tzname[]; #endif static int retval = EXIT_SUCCESS; diff --git a/localtime.c b/localtime.c index 8f103aa..b23fe43 100644 --- a/localtime.c +++ b/localtime.c @@ -188,20 +188,21 @@ static int lcl_is_set; static struct tm tm; -#if !HAVE_POSIX_DECLS +#if !HAVE_POSIX_DECLS || TZ_TIME_T +# if HAVE_TZNAME char * tzname[2] = { (char *) wildabbr, (char *) wildabbr }; -# ifdef USG_COMPAT +# endif +# if USG_COMPAT long timezone; int daylight; # endif -#endif - -#ifdef ALTZONE +# ifdef ALTZONE long altzone; -#endif /* defined ALTZONE */ +# endif +#endif /* Initialize *S to a value based on GMTOFF, ISDST, and ABBRIND. */ static void @@ -263,8 +264,10 @@ detzcode64(const char *const codep) static void update_tzname_etc(struct state const *sp, struct ttinfo const *ttisp) { +#if HAVE_TZNAME tzname[ttisp->tt_isdst] = (char *) &sp->chars[ttisp->tt_abbrind]; -#ifdef USG_COMPAT +#endif +#if USG_COMPAT if (!ttisp->tt_isdst) timezone = - ttisp->tt_gmtoff; #endif @@ -280,16 +283,17 @@ settzname(void) register struct state * const sp = lclptr; register int i; - tzname[0] = tzname[1] = (char *) wildabbr; -#ifdef USG_COMPAT +#if HAVE_TZNAME + tzname[0] = tzname[1] = (char *) (sp ? wildabbr : gmt); +#endif +#if USG_COMPAT daylight = 0; timezone = 0; -#endif /* defined USG_COMPAT */ +#endif #ifdef ALTZONE altzone = 0; #endif /* defined ALTZONE */ if (sp == NULL) { - tzname[0] = tzname[1] = (char *) gmt; return; } /* @@ -304,10 +308,10 @@ settzname(void) &sp->ttis[ sp->types[i]]; update_tzname_etc(sp, ttisp); -#ifdef USG_COMPAT +#if USG_COMPAT if (ttisp->tt_isdst) daylight = 1; -#endif /* defined USG_COMPAT */ +#endif } } @@ -2286,9 +2290,9 @@ posix2time(time_t t) #endif /* defined STD_INSPIRED */ -#if defined time_tz || EPOCH_LOCAL || EPOCH_OFFSET != 0 +#if TZ_TIME_T -# ifndef USG_COMPAT +# if !USG_COMPAT # define daylight 0 # define timezone 0 # endif diff --git a/newctime.3 b/newctime.3 index 169c919..8b89935 100644 --- a/newctime.3 +++ b/newctime.3 @@ -7,7 +7,7 @@ asctime, ctime, difftime, gmtime, localtime, mktime \- convert date and time .el ds - \- .B #include <time.h> .PP -.B extern char *tzname[2]; +.BR "extern char *tzname[];" " /\(** (optional) \(**/" .PP .B char *ctime(time_t const *clock); .PP @@ -213,7 +213,7 @@ includes the following fields: .RS .PP .nf -.ta .5i +\w'long tm_gmtoff;\0\0'u +.ta 2n +\w'long tm_gmtoff;nn'u int tm_sec; /\(** seconds (0\*(en60) \(**/ int tm_min; /\(** minutes (0\*(en59) \(**/ int tm_hour; /\(** hours (0\*(en23) \(**/ @@ -223,21 +223,11 @@ includes the following fields: int tm_wday; /\(** day of week (Sunday = 0) \(**/ int tm_yday; /\(** day of year (0\*(en365) \(**/ int tm_isdst; /\(** is summer time in effect? \(**/ - char \(**tm_zone; /\(** abbreviation of time zone name \(**/ - long tm_gmtoff; /\(** offset from UT in seconds \(**/ + char \(**tm_zone; /\(** time zone abbreviation (optional) \(**/ + long tm_gmtoff; /\(** offset from UT in seconds (optional) \(**/ .fi .RE .PP -The -.I tm_zone -and -.I tm_gmtoff -fields exist, and are filled in, only if arrangements to do -so were made when the library containing these functions was -created. -There is no guarantee that these fields will continue to exist -in this form in future releases of this code. -.PP .I Tm_isdst is non-zero if summer time is in effect. .PP @@ -246,6 +236,21 @@ is the offset (in seconds) of the time represented from UT, with positive values indicating east of the Prime Meridian. The field's name is derived from Greenwich Mean Time, a precursor of UT. +.PP +In +.B struct tm +the +.I tm_zone +and +.I tm_gmtoff +fields exist, and are filled in, only if arrangements to do +so were made when the library containing these functions was +created. +Similarly, the +.B tzname +variable is optional. +There is no guarantee that these fields and this variable will +continue to exist in this form in future releases of this code. .SH FILES .ta \w'/usr/local/etc/zoneinfo/posixrules\0\0'u /usr/local/etc/zoneinfo time zone information directory @@ -277,12 +282,19 @@ and point to static data overwritten by each call. The +.B tzname +variable (once set) and the .B tm_zone field of a returned .B "struct tm" -points to a static array of characters, which -can be overwritten by later calls to -.IR tzset . +both point to an array of characters that +can be freed or overwritten by later calls to the functions +.IR localtime , +.IR tzfree , +and +.IR tzset , +if these functions affect the time zone information that specifies the +abbreviation in question. The remaining functions and data are thread-safe. .PP .IR Asctime , diff --git a/private.h b/private.h index 1e61592..ad9fcb9 100644 --- a/private.h +++ b/private.h @@ -153,6 +153,22 @@ # endif #endif +#ifndef USG_COMPAT +# ifndef _XOPEN_VERSION +# define USG_COMPAT 0 +# else +# define USG_COMPAT 1 +# endif +#endif + +#ifndef HAVE_TZNAME +# if _POSIX_VERSION < 198808 && !USG_COMPAT +# define HAVE_TZNAME 0 +# else +# define HAVE_TZNAME 1 +# endif +#endif + #ifndef F_OK #define F_OK 0 #endif /* !defined F_OK */ @@ -339,6 +355,12 @@ typedef unsigned long uintmax_t; ** typical platforms. */ #if defined time_tz || EPOCH_LOCAL || EPOCH_OFFSET != 0 +# define TZ_TIME_T 1 +#else +# define TZ_TIME_T 0 +#endif + +#if TZ_TIME_T # ifdef LOCALTIME_IMPLEMENTATION static time_t sys_time(time_t *x) { return time(x); } # endif @@ -393,6 +415,20 @@ typedef time_tz tz_time_t; # define tzset tz_tzset # undef tzsetwall # define tzsetwall tz_tzsetwall +# if HAVE_TZNAME +# undef tzname +# define tzname tz_tzname +# endif +# if USG_COMPAT +# undef daylight +# define daylight tz_daylight +# undef timezone +# define timezone tz_timezone +# endif +# ifdef ALTZONE +# undef altzone +# define altzone tz_altzone +# endif char *ctime(time_t const *); char *ctime_r(time_t const *, char *); @@ -422,18 +458,17 @@ extern char *asctime_r(struct tm const *restrict, char *restrict); extern char **environ; #endif -#if !HAVE_POSIX_DECLS -# ifdef USG_COMPAT -# ifndef timezone +#if TZ_TIME_T || !HAVE_POSIX_DECLS +# if HAVE_TZNAME +extern char *tzname[]; +# endif +# if USG_COMPAT extern long timezone; -# endif -# ifndef daylight extern int daylight; -# endif # endif #endif -#if defined ALTZONE && !defined altzone +#ifdef ALTZONE extern long altzone; #endif @@ -443,25 +478,25 @@ extern long altzone; */ #ifdef STD_INSPIRED -# if !defined tzsetwall || defined time_tz +# if TZ_TIME_T || !defined tzsetwall void tzsetwall(void); # endif -# if !defined offtime || defined time_tz +# if TZ_TIME_T || !defined offtime struct tm *offtime(time_t const *, long); # endif -# if !defined timegm || defined time_tz +# if TZ_TIME_T || !defined timegm time_t timegm(struct tm *); # endif -# if !defined timelocal || defined time_tz +# if TZ_TIME_T || !defined timelocal time_t timelocal(struct tm *); # endif -# if !defined timeoff || defined time_tz +# if TZ_TIME_T || !defined timeoff time_t timeoff(struct tm *, long); # endif -# if !defined time2posix || defined time_tz +# if TZ_TIME_T || !defined time2posix time_t time2posix(time_t); # endif -# if !defined posix2time || defined time_tz +# if TZ_TIME_T || !defined posix2time time_t posix2time(time_t); # endif #endif @@ -495,10 +530,10 @@ time_t mktime_z(timezone_t restrict, struct tm *restrict); timezone_t tzalloc(char const *); void tzfree(timezone_t); # ifdef STD_INSPIRED -# if !defined posix2time_z || defined time_tz +# if TZ_TIME_T || !defined posix2time_z time_t posix2time_z(timezone_t, time_t) ATTRIBUTE_PURE; # endif -# if !defined time2posix_z || defined time_tz +# if TZ_TIME_T || !defined time2posix_z time_t time2posix_z(timezone_t, time_t) ATTRIBUTE_PURE; # endif # endif @@ -649,7 +684,7 @@ char *ctime_r(time_t const *, char *); ** or ** isleap(a + b) == isleap(a % 400 + b % 400) ** This is true even if % means modulo rather than Fortran remainder -** (which is allowed by C89 but not C99). +** (which is allowed by C89 but not by C99 or later). ** We use this to avoid addition overflow problems. */ diff --git a/strftime.c b/strftime.c index 4b9fd2c..d09a0db 100644 --- a/strftime.c +++ b/strftime.c @@ -73,7 +73,7 @@ static const struct lc_time_T C_time_locale = { /* ** x_fmt - ** C99 requires this format. + ** C99 and later require this format. ** Using just numbers (as here) makes Quakers happier; ** it's also compatible with SVR4. */ @@ -81,7 +81,7 @@ static const struct lc_time_T C_time_locale = { /* ** c_fmt - ** C99 requires this format. + ** C99 and later require this format. ** Previously this code used "%D %X", but we now conform to C99. ** Note that ** "%a %b %d %H:%M:%S %Y" @@ -105,10 +105,6 @@ static char * _fmt(const char *, const struct tm *, char *, const char *, int *); static char * _yconv(int, int, bool, bool, char *, char const *); -#if !HAVE_POSIX_DECLS -extern char * tzname[]; -#endif - #ifndef YEAR_2000_NAME #define YEAR_2000_NAME "CHECK_STRFTIME_FORMATS_FOR_TWO_DIGIT_YEARS" #endif /* !defined YEAR_2000_NAME */ @@ -223,7 +219,7 @@ label: case 'E': case 'O': /* - ** C99 locale modifiers. + ** Locale modifiers of C99 and later. ** The sequences ** %Ec %EC %Ex %EX %Ey %EY ** %Od %oe %OH %OI %Om %OM @@ -483,19 +479,19 @@ label: case 'Z': #ifdef TM_ZONE pt = _add(t->TM_ZONE, pt, ptlim); -#else +#elif HAVE_TZNAME if (t->tm_isdst >= 0) pt = _add(tzname[t->tm_isdst != 0], pt, ptlim); #endif /* - ** C99 says that %Z must be replaced by the - ** empty string if the time zone is not - ** determinable. + ** C99 and later say that %Z must be + ** replaced by the empty string if the + ** time zone is not determinable. */ continue; case 'z': -#if defined TM_GMTOFF || defined USG_COMPAT || defined ALTZONE +#if defined TM_GMTOFF || USG_COMPAT || defined ALTZONE { long diff; char const * sign; @@ -505,7 +501,7 @@ label: diff = t->TM_GMTOFF; # else /* - ** C99 says that the UT offset must + ** C99 and later say that the UT offset must ** be computed by looking only at ** tm_isdst. This requirement is ** incorrect, since it means the code @@ -513,20 +509,20 @@ label: ** altzone and timezone), and the ** magic might not have the correct ** offset. Doing things correctly is - ** tricky and requires disobeying C99; + ** tricky and requires disobeying the standard; ** see GNU C strftime for details. ** For now, punt and conform to the ** standard, even though it's incorrect. ** - ** C99 says that %z must be replaced by the - ** empty string if the time zone is not + ** C99 and later that %z must be replaced by + ** the empty string if the time zone is not ** determinable, so output nothing if the ** appropriate variables are not available. */ if (t->tm_isdst < 0) continue; if (t->tm_isdst == 0) -# ifdef USG_COMPAT +# if USG_COMPAT diff = -timezone; # else continue; @@ -543,9 +539,11 @@ label: #ifdef TM_ZONE negative = t->TM_ZONE[0] == '-'; #else - negative - = (t->tm_isdst < 0 - || tzname[t->tm_isdst != 0][0] == '-'); + negative = t->tm_isdst < 0; +# if HAVE_TZNAME + if (tzname[t->tm_isdst != 0][0] == '-') + negative = true; +# endif #endif } if (negative) { diff --git a/zdump.c b/zdump.c index 7cde3d3..b69b1e9 100644 --- a/zdump.c +++ b/zdump.c @@ -77,7 +77,6 @@ extern int getopt(int argc, char * const argv[], const char * options); extern char * optarg; extern int optind; -extern char * tzname[]; #endif /* The minimum and maximum finite time values. */ @@ -997,9 +996,11 @@ abbr(struct tm const *tmp) #ifdef TM_ZONE return tmp->TM_ZONE; #else - return (0 <= tmp->tm_isdst && tzname[0 < tmp->tm_isdst] - ? tzname[0 < tmp->tm_isdst] - : ""); +# if HAVE_TZNAME + if (0 <= tmp->tm_isdst && tzname[0 < tmp->tm_isdst]) + return tzname[0 < tmp->tm_isdst]; +# endif + return ""; #endif } -- 2.9.4

1 0

[PATCH 1/2] * Makefile (check_character_set): Fix typo in filename.
by Paul Eggert June 8, 2017

June 8, 2017

--- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index c3ef931..476f259 100644 --- a/Makefile +++ b/Makefile @@ -605,7 +605,7 @@ check_character_set: $(ENCHILADA) ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) \ CONTRIBUTING LICENSE Makefile README \ - version tzdata.ic && \ + version tzdata.zi && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA) backzone \ leapseconds yearistype.sh zone.tab && \ ! grep -Env $(OK_LINE) $(ENCHILADA) -- 2.7.4

1 1

[PATCH 1/2] Fix zic parsing of abbreviated line codes
by Paul Eggert June 2, 2017

June 2, 2017

* NEWS: Document this. * zic.8: Document more clearly that "Zone" etc. can be abbreviated. * zic.c (line_codes): Remove, replacing with ... (zi_line_codes, leap_line_codes): ... these new constants. (infile): Use them to distinguish context more accurately. Remove no-longer-applicable warning. --- NEWS | 9 +++++++++ zic.8 | 9 ++++++++- zic.c | 16 +++++++++------- 3 files changed, 26 insertions(+), 8 deletions(-) diff --git a/NEWS b/NEWS index 0a76781..99f5d64 100644 --- a/NEWS +++ b/NEWS @@ -48,6 +48,15 @@ Unreleased, experimental changes Also, zic warns about the undocumented usage with a "last-" prefix, e.g., "last-Fri". + Similarly, zic now accepts the unambiguous abbreviation "L" for + "Link" in ordinary context and for "Leap" in leap-second context. + Conversely, zic no longer accepts non-prefixes such as "La" as + abbreviations for words like "Leap". + + zic no longer accepts leap second lines in ordinary input, or + ordinary lines in leap second input. Formerly, zic sometimes + warned about this undocumented usage and handled it incorrectly. + Several minor changes have been made to the code to make it a bit easier to port to MS-Windows. (Thanks to Kees Dekker for reporting the problems.) diff --git a/zic.8 b/zic.8 index 6fee96d..ab95b08 100644 --- a/zic.8 +++ b/zic.8 @@ -147,7 +147,14 @@ Any line that is blank (after comment stripping) is ignored. Non-blank lines are expected to be of one of three types: rule lines, zone lines, and link lines. .PP -Names (such as month names) must be in English and are case insensitive. +Names must be in English and are case insensitive. +They appear in several contexts, and include month and weekday names +and keywords such as +.BR "maximum" , +.BR "only" , +.BR "Rolling" , +and +.BR "Zone" . A name can be abbreviated by omitting all but an initial prefix; any abbreviation must be unambiguous in context. .PP diff --git a/zic.c b/zic.c index 33cb4e7..ff71af6 100644 --- a/zic.c +++ b/zic.c @@ -298,10 +298,13 @@ struct lookup { static struct lookup const * byword(const char * string, const struct lookup * lp); -static struct lookup const line_codes[] = { +static struct lookup const zi_line_codes[] = { { "Rule", LC_RULE }, { "Zone", LC_ZONE }, { "Link", LC_LINK }, + { NULL, 0 } +}; +static struct lookup const leap_line_codes[] = { { "Leap", LC_LEAP }, { NULL, 0} }; @@ -1114,6 +1117,8 @@ infile(const char *name) } else if (wantcont) { wantcont = inzcont(fields, nfields); } else { + struct lookup const *line_codes + = name == leapsec ? leap_line_codes : zi_line_codes; lp = byword(fields[0], line_codes); if (lp == NULL) error(_("input line of unknown type")); @@ -1130,11 +1135,7 @@ infile(const char *name) wantcont = false; break; case LC_LEAP: - if (name != leapsec) - warning(_("%s: Leap line in non leap" - " seconds file %s"), - progname, name); - else inleap(fields, nfields); + inleap(fields, nfields); wantcont = false; break; default: /* "cannot happen" */ @@ -1586,7 +1587,8 @@ rulesub(struct rule *rp, const char *loyearp, const char *hiyearp, ** Day work. ** Accept things such as: ** 1 - ** last-Sunday + ** lastSunday + ** last-Sunday (undocumented; warn about this) ** Sun<=20 ** Sun>=7 */ -- 2.9.4

1 2

mend historical data of Europe/Dublin
by Michael Deckers June 1, 2017

June 1, 2017

Europe/Dublin currently has the two fall backs in 1946 and 1947 going from 02:00 to 01:00, one hour before the corresponding two jumps in Europe/London. This is wrong; both should go from 03:00 to 02:00. For 1947, the "Summer Time Order, 1947" at [http://www.irishstatutebook.ie/eli/1947/sro/71/made/en/print.html] gives the time of the switch as "two o'clock, West-European time", where "West-European time" means GMT according to the "Summer Time Act, 1925", section 4, at [http://www.irishstatutebook.ie/eli/1925/act/8/enacted/en/print.html] For 1946, the "Summer Time Order, 1926" at [http://www.irishstatutebook.ie/eli/1926/sro/919/made/en/print.html] specifies the time of the switch in the same manner. Hence I propose to change Zone Europe/Dublin as follows: # Zone NAME GMTOFF RULES FORMAT [UNTIL] - 0:00 1:00 IST 1946 Oct 6 2:00 + 0:00 1:00 IST 1946 Oct 6 2:00s 0:00 - GMT 1947 Mar 16 2:00 - 0:00 1:00 IST 1947 Nov 2 2:00 + 0:00 1:00 IST 1947 Nov 2 2:00s 0:00 - GMT 1948 Apr 18 2:00 Michael Deckers. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

proposed changes for Win32 and a improved mktime() algorithm
by Kees Dekker May 30, 2017

May 30, 2017

Hello, I've a patch (diff/patch format) attached, which is the result of a longer period of testing (and delays due to other duties). The patch has been created against 2017B code. And I've tried to limit my changes to a minimum. The patch comprises changes for 5 files, where most of the changes are in private.h and localtime.c. The changes are (summarized list): 1. Win32/Visual Studio (2015) port. Related to including header files + handling of the Windows style backslash (by adding some macros) 2. Adding a faster (and more efficient) algorithm for mktime(). Instead of the binary search another approach is used, but also results in different ambiguous boundaries for switching from DST to non-DST. 3. Adding a possibility not to use putenv(). Putenv() may result in leaking memory, as it is unsure putenv() behaves on different platforms. As long as set & get of a TZ variable is within the TZ library, there is no need to use putenv()/getenv() at all. Also note that putenv/getenv on Windows are thread-unsafe (and I did not like to use the GetEnvironmentString/SetEnvironmentString() counterparts). 4. Solved some platform (e.g. HPUX) specific errors/warnings (initializing + some fixed char buffers). Indeed, making some compilers happy (there is more than gcc only). I'm not sure whether the way how I provide this patch is the recommended way. If another way is preferred, please let me know. If more information is needed, please ask. I added as much as possible the comments in the affected source files itself, but I can imagine that still some questions left. It is not my intention to see 'good luck with this patch'. If there is another preferred method to chop this patch in chunks, please let me know. Regards, Kees

11 43