- tz - lists.iana.org

[PATCH] Clarify that EST5EDT is problematic in POSIX
by Paul Eggert May 21, 2018

May 21, 2018

* theory.html: Don’t imply that EST5EDT is an OK POSIX TZ string, as POSIX does not specify the DST transitions in this case. Use past tense to describe the typical pre-POSIX behavior. Minor copyediting. --- theory.html | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/theory.html b/theory.html index 53f7cee..298972e 100644 --- a/theory.html +++ b/theory.html @@ -874,15 +874,15 @@ an older <code>zic</code>. <pre><code>TZ='Pacific/Auckland'</code></pre> </li> <li> - POSIX does not define the exact meaning of <code>TZ</code> values like + POSIX does not define the <abbr>DST</abbr> transitions + for <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 + Traditionally the current <abbr>US</abbr> <abbr>DST</abbr> rules + were used to interpret such values, but this meant that the + <abbr>US</abbr> <abbr>DST</abbr> rules were compiled into each + program that did time conversion. This meant that when + <abbr>US</abbr> time conversion rules changed (as in the United + States in 1987), all programs that did time conversion had to be recompiled to ensure proper results. </li> <li> @@ -893,14 +893,14 @@ an older <code>zic</code>. <li> 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 + 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.) + 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 @@ -923,7 +923,7 @@ an older <code>zic</code>. 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, + floating-point type, this was not supported by any practical system, and POSIX.1-2013 and the <code><abbr>tz</abbr></code> code both require <code>time_t</code> to be an integer type. </li> @@ -960,9 +960,9 @@ an older <code>zic</code>. 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). + use legacy <code>TZ</code> values such as "<code>EST5EDT</code>" which + can be used by "new" programs as well as by "old" programs that + assume pre-POSIX <code>TZ</code> values. </p> </li> <li> -- 2.17.0

1 0

[PROPOSED] Use “TZif” for binary files.
by Paul Eggert May 20, 2018

May 20, 2018

Also, mention tzdist-bis and draft-murchison-tzdist-tzif-00. --- Makefile | 8 +++++--- NEWS | 2 ++ theory.html | 15 ++++++++------- tz-link.html | 37 ++++++++++++++++++++++--------------- zic.c | 2 +- 5 files changed, 38 insertions(+), 26 deletions(-) diff --git a/Makefile b/Makefile index 91c30f7..06f7fd6 100644 --- a/Makefile +++ b/Makefile @@ -109,6 +109,8 @@ LIBDIR = $(TOPDIR)/$(USRDIR)/lib # Types to try, as an alternative to time_t. int64_t should be first. TIME_T_ALTERNATIVES = int64_t int32_t uint32_t uint64_t +# What kind of TZif data files to generate. +# (TZif is the binary time zone data format that zic generates.) # If you want only POSIX time, with time values interpreted as # seconds since the epoch (not counting leap seconds), use # REDO= posix_only @@ -129,7 +131,7 @@ TIME_T_ALTERNATIVES = int64_t int32_t uint32_t uint64_t REDO= posix_right -# To install data in text form that has all the information of the binary data, +# To install data in text form that has all the information of the TZif data, # (optionally incorporating leap second information), use # TZDATA_TEXT= tzdata.zi leapseconds # To install text data without leap second information (e.g., because @@ -357,7 +359,7 @@ ZIC= $(zic) $(ZFLAGS) ZFLAGS= -# How to use zic to install tz binary files. +# How to use zic to install TZif files. ZIC_INSTALL= $(ZIC) -d '$(DESTDIR)$(TZDIR)' $(LEAPSECONDS) @@ -605,7 +607,7 @@ INSTALLARGS = \ YEARISTYPE='$(YEARISTYPE)' \ ZIC='$(ZIC)' -# 'make install_data' installs one set of tz binary files. +# 'make install_data' installs one set of TZif files. install_data: zic leapseconds yearistype tzdata.zi $(ZIC_INSTALL) tzdata.zi diff --git a/NEWS b/NEWS index a91f00a..6bd89c2 100644 --- a/NEWS +++ b/NEWS @@ -25,6 +25,8 @@ Unreleased, experimental changes The latter restriction makes room for future extensions (a possibility noted by Tom Lane). + The name "TZif" is now used for the tz binary data format. + Changes to build procedure New 'make' target 'rearguard_tarballs' to build the rearguard diff --git a/theory.html b/theory.html index d5055b2..f2409f4 100644 --- a/theory.html +++ b/theory.html @@ -932,15 +932,16 @@ an older <code>zic</code>. <li> <p> The <code>TZ</code> environment variable is used in generating - the name of a binary file from which time-related information is read + the name of a file from which time-related information is read (or is interpreted à la POSIX); <code>TZ</code> is no longer - constrained to be a three-letter time zone - abbreviation followed by a number of hours and an optional three-letter - daylight time zone abbreviation. + constrained to be a string containing abbreviations + and numeric data as described <a href="#POSIX">above</a>. + The file's format is <dfn><abbr>TZif</abbr></dfn>, + a time zone information format that contains binary data. The daylight saving time rules to be used for a particular <code><abbr>tz</abbr></code> region are encoded in the - binary file; the format of the file - allows U.S., Australian, and other rules to be encoded, and + <abbr>TZif</abbr> file; the format of the file allows <abbr>US</abbr>, + Australian, and other rules to be encoded, and allows for situations where more than two time zone abbreviations are used. </p> @@ -950,7 +951,7 @@ an older <code>zic</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 binary file's name. + to hold the string used to generate the <abbr>TZif</abbr> file's 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> diff --git a/tz-link.html b/tz-link.html index b8b7944..77e06d2 100644 --- a/tz-link.html +++ b/tz-link.html @@ -143,8 +143,10 @@ more errors.</p> After obtaining the code and data files, see the <code>README</code> file for what to do next. The code lets you compile the <code><abbr>tz</abbr></code> source files into -machine-readable binary files, one for each location. It also lets -you read a <code><abbr>tz</abbr></code> binary file and interpret time stamps for that +machine-readable binary files, one for each location. The binary files +are in a special time zone information format (<dfn><abbr>TZif</abbr></dfn>). +The code also lets +you read a <abbr>TZif</abbr> file and interpret time stamps for that location.</p> <h2 id="changes">Changes to the <code><abbr>tz</abbr></code> database</h2> <p> @@ -272,12 +274,17 @@ 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 +transferring time zone data by reference. +The <a href="https://www.ietf.org/mailman/listinfo/tzdist-bis">tzdist-bis +mailing list</a> discusses two Internet drafts: <a id="TZDIST-Geolocate" 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> +href="https://tools.ietf.org/html/rfc5870">'geo' URI</a>, and +<a href="https://tools.ietf.org/html/draft-murchison-tzdist-tzif-00">The +Time Zone Information Format (<abbr>TZif</abbr>)</a> specifies the format of +<abbr>TZif</abbr> data.</li> <li>The <a href="https://tools.ietf.org/html/rfc5545"> Internet Calendaring and Scheduling Core Object Specification (iCalendar)</a> (Internet <abbr>RFC</abbr> 5445) @@ -426,35 +433,35 @@ source into text files, along with a runtime that can read those files. Tcl is freely available under a <abbr>BSD</abbr>-style license.</li> </ul> -<h2 id="binary">Other <code><abbr>tz</abbr></code> binary file readers</h2> +<h2 id="TZif">Other <abbr>TZif</abbr> readers</h2> <ul> <li>The <a href="https://www.gnu.org/software/libc/"><abbr>GNU</abbr> C Library</a> has an independent, thread-safe implementation of -a <code><abbr>tz</abbr></code> binary file reader. +a <abbr>TZif</abbr> file reader. This library is freely available under the LGPL and is widely used in <abbr>GNU</abbr>/Linux systems.</li> <li><a href="https://www.gnome.org">GNOME</a>'s <a href="https://developer.gnome.org/glib/">GLib</a> has -a <code><abbr>tz</abbr></code> binary file reader written in C that +a <abbr>TZif</abbr> file reader written in C that creates a <code>GTimeZone</code> object representing sets of <abbr>UT</abbr> offsets. It is freely available under the <abbr>LGPL</abbr>.</li> <li>The <a href="https://github.com/bloomberg/bde/wiki">BDE Standard Library</a>'s <code>baltzo::TimeZoneUtil</code> component contains a C++ -implementation of a binary file reader. It is freely available under +implementation of a <abbr>TZif</abbr> 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>UT</abbr> and civil time and -can read binary files. It is freely available under the Apache +can read <abbr>TZif</abbr> files. It is freely available under the Apache License.</li> <li><a href="http://bmsi.com/java/#TZ">ZoneInfo.java</a> -is a <code><abbr>tz</abbr></code> binary file reader written in Java. +is a <abbr>TZif</abbr> file reader written in Java. It is freely available under the <abbr>LGPL</abbr>.</li> <li><a href="https://github.com/derickr/timelib">Timelib</a> is a C -library that reads tz binary files and converts +library that reads <abbr>TZif</abbr> 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>, @@ -465,23 +472,23 @@ It is freely available under the <abbr>MIT</abbr> license.</li> JavaScript library that supports date arithmetic that is time zone aware. It is freely available under the <abbr>MIT</abbr> license.</li> <li>Tcl, mentioned <a href="#Tcl">above</a>, also contains a -<code><abbr>tz</abbr></code> binary file reader.</li> +<abbr>TZif</abbr> file reader.</li> <li><a href="http://search.cpan.org/perldoc?DateTime::TimeZone::Tzfile"> DateTime::TimeZone::Tzfile</a> -is a <code><abbr>tz</abbr></code> binary file reader written in Perl. +is a <abbr>TZif</abbr> file reader written in Perl. It is freely available under the same terms as Perl (dual <abbr>GPL</abbr> and Artistic license).</li> <li>The public-domain <a href="https://github.com/dbaron/tz.js">tz.js</a> library contains a Python tool that -converts <code><abbr>tz</abbr></code> binary data into +converts <abbr>TZif</abbr> data into <abbr>JSON</abbr>-format data suitable for use in its JavaScript library for time zone conversion. Dates before 1970 are not supported.</li> <li>The <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 +parses and uses <abbr>TZif</abbr> data. It is freely available under a <abbr>BSD</abbr>-style license.</li> </ul> <h2 id="software">Other <code><abbr>tz</abbr></code>-based time zone software</h2> diff --git a/zic.c b/zic.c index 0c4c384..f1d0bf3 100644 --- a/zic.c +++ b/zic.c @@ -184,7 +184,7 @@ static bool yearistype(zic_t year, const char * type); enum { PERCENT_Z_LEN_BOUND = sizeof "+995959" - 1 }; /* If true, work around a bug in Qt 5.6.1 and earlier, which mishandles - tz binary files whose POSIX-TZ-style strings contain '<'; see + TZif files whose POSIX-TZ-style strings contain '<'; see QTBUG-53071 <https://bugreports.qt.io/browse/QTBUG-53071>. This workaround will no longer be needed when Qt 5.6.1 and earlier are obsolete, say in the year 2021. */ -- 2.7.4

1 0

[PROPOSED] ‘white-space: pre-wrap’ to avoid tiny fonts
by Paul Eggert May 16, 2018

May 16, 2018

* theory.html, tz-how-to.html, tz-link.html: Use ‘white-space: pre-wrap’ to avoid tiny font on Android mobile browsers. Migrate this style setting to a <style> element, and be consistent about it in the tz web pages. --- theory.html | 3 +++ tz-how-to.html | 3 +++ tz-link.html | 9 ++++++--- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/theory.html b/theory.html index 0ada9e3..2d6e505 100644 --- a/theory.html +++ b/theory.html @@ -3,6 +3,9 @@ <head> <title>Theory and pragmatics of the tz code and data</title> <meta charset="UTF-8"> + <style> + pre {margin-left: 2em; white-space: pre-wrap;} + </style> </head> <body> diff --git a/tz-how-to.html b/tz-how-to.html index a54f54a..367c6ed 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -5,6 +5,9 @@ <head> <title>How to Read the tz Database</title> <meta http-equiv="Content-type" content='text/html; charset="UTF-8"'> +<style> +pre {margin-left: 2em; white-space: pre-wrap;} +</style> </head> <body> <h2>How to Read the <a href="https://en.wikipedia.org/wiki/Tz_database">tz diff --git a/tz-link.html b/tz-link.html index b8b7944..87241da 100644 --- a/tz-link.html +++ b/tz-link.html @@ -3,6 +3,9 @@ <head> <title>Sources for time zone and daylight saving time data</title> <meta charset="UTF-8"> +<style> +pre {margin-left: 2em; white-space: pre-wrap;} +</style> </head> <body> <h1>Sources for time zone and daylight saving time data</h1> @@ -97,7 +100,7 @@ href="https://en.wikipedia.org/wiki/Unix_shell">shell</a> commands download the latest release's two <a href="https://en.wikipedia.org/wiki/Tar_(computing)">tarballs</a> to a <abbr>GNU</abbr>/Linux or similar host.</p> -<pre style="margin-left: 2em"><code>mkdir tzdb +<pre><code>mkdir tzdb cd tzdb <a href="https://www.gnu.org/software/wget/">wget</a> https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz wget https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz @@ -107,7 +110,7 @@ gzip -dc tzdata-latest.tar.gz | tar -xf - <p>Alternatively, the following shell commands download the same 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> +<pre><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="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 @@ -133,7 +136,7 @@ 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> -<pre style="margin-left: 2em"><code><a href="https://git-scm.com">git</a> clone <a href="https://github.com/eggert/tz">https://github.com/eggert/tz</a> +<pre><code><a href="https://git-scm.com">git</a> clone <a href="https://github.com/eggert/tz">https://github.com/eggert/tz</a> </code></pre> <p> Since version 2012e, each release has been tagged in development repositories. -- 2.17.0

1 0

Brazilian Timezone
by Christian Brackmann May 16, 2018

May 16, 2018

Hello! I wonder about the brazilian timezone you call as "America/Sao_Paulo". In Brazil, São Paulo is just a city (with a very large population indeed), but as oficial time in Brazil we use the capital of Brazil, called "Brasília". Why do you use the city of São Paulo as reference? Our legal local time is Brasilia and not São Paulo. Can you please explain it better? Thank you in advance. Best regards. *--* Prof. Dr. Christian Puhlmann Brackmann Coordenador Geral de Pós-Graduação Pró-Reitoria de Pesquisa, Pós-graduação e Inovação Instituto Federal de Educação, Ciência e Tecnologia Farroupilha (IFFAR) brackmann(a)iffarroupilha.edu.br +55 55 3226 6636 / 98100-1819 ** *“Education is the most powerful weapon which you can use to change the world”*Nelson Mandela

2 1

Gripe about compressed rule set names in tzdata.zi
by Tom Lane May 14, 2018

May 14, 2018

Reviewing the changes between 2018d and 2018e crystallized something that had not been clear to me before: the "compressed" ruleset names used in tzdata.zi are chosen as sequential ASCII characters, or pairs of ASCII letters after the single-character names run out. This means that addition or deletion of a ruleset near the beginning of the file creates semantically-insignificant changes throughout the rest of the file, making it hard to review the diffs to get a sense of what changed, or to eyeball-validate the .zi file. It probably also bloats one's repository if storing tzdata.zi in a source code control system. So I'm wondering if it'd be acceptable to change the compression rule to something that gives more stable results. I've not really experimented to see what would work well, but one simple idea is to take the shortest unique prefix of each original ruleset name. There are other options if shortness is prized well above readability. I wouldn't expect the results to be 100% stable in the face of ruleset additions/deletions, since conflicts could appear or disappear, but 99% would be fine. Regardless of the specifics, this would surely have the effect of making tzdata.zi a bit bigger (although compression would likely buy back much of the delta). So, if nobody but me is annoyed by the current behavior, I'd expect such a proposal to get rejected. I'm willing to do the legwork to develop a concrete patch if it'd be likely to get accepted. regards, tom lane

2 4

new mailing list: tzdist-bis@ietf.org
by Eliot Lear May 11, 2018

May 11, 2018

Hello everyone, I would like to bring to your attention two drafts that we have formed a mailing list around two drafts: draft-murchison-tzdist-geolocate-01 The Time Zone Data Distribution Service (TZDIST) Geolocate Extension The basic idea behind this draft is, given a geo: URI, please provide provide an appropriate TZID. And draft-murchison-tzdist-tzif-00 The Time Zone Information Format (TZif) This document is the one I've been waiting for a long time: it describes the format that those tz files have been using, and it features as co-authors Paul Eggert and Arthur David Olson. The intent is to do a sort of micro-wg to get both of these docs turned into RFCs. To do that, we need good reviewers, particularly ones who have previously cracked and parsed the tz files (bonus points if you were crazy enough to write out one!!). There is a mailing list for this purpose: tzdist-bis(a)ietf.org. You can join it by going to https://www.ietf.org/mailman/listinfo/tzdist-bis. I look forward to seeing a few of you over there (you know who you are). Eliot

1 0

Time in Macau
by P Chan May 10, 2018

May 10, 2018

Hi, I would like to share some information about the history of time in Macau. All the sources I used can be accessed online. LegisMac http://legismac.safp.gov.mo/legismac/descqry/Descqry.jsf?lang=pt A database for searching titles of legal documents of Macau in Chinese and Portuguese. The term "HORÁRIO DE VERÃO" can be used for searching decrees about summer time. Archives of Macao http://www.archives.gov.mo/en/bo/ It contains images of old official gazettes. The Macao Meteorological and Geophysical Bureau have a page listing the summer time history. But it is not complete and has some mistakes. <http://www.smg.gov.mo/smg/geophysics/c_t_Summer%20Time.htm>http://www.smg.gov.mo/smg/geophysics/e_t_Summer%20Time.htm Macau adopted GMT+8 on 30 Oct 1904 to follow Hong Kong. Clocks were advanced by 25 minutes and 50 seconds. Which means the LMT used was +7:34:10. As stated in the "Portaria N.º 204" dated 21 October 1904 and published in the Official Gazette on 29 October 1904. http://igallery.icm.gov.mo/Images/Archives/BO/MO_AH_PUB_BO_1904_10/MO_AH_PU… Therefore the 1911 decree of Portugal did not change time in Macau. >From LegisMac, here is a list of decrees that changed the time. Decree Gazette no. Gazette date Title DIL 732 BOCM 51 1941.12.20 adoptando medidas excepcionais que garantam o funcionamento de todos os serviços públicos e particulares e restringindo ao mínimo o consumo de alguns géneros e artigos essenciais à vida da colónia. DIL 764 BOCM 9S 1942.04.30 Determinando que sejam adiantadas de uma hora os relógios da colónia e regulando os horários das repartições públicas. DIL 781 BOCM 21 1942.10.10 Substituindo o corpo do artigo 3° do diploma legislativo n° 732 e suas alíneas a) e b), respeitantes às alterações da hora e horário das Repartições Públicas, e revogando o diploma legislativo n° 764. PT 3434 BOCM 8S 1943.04.17 determinando que às 23 horas do dia 30 do corrente mês sejam adiantadas de uma hora os relógios da colónia e regulando o horário das Repartições Públicas. PT 3504 BOCM 20 1943.09.25 regulando o horário das Repartições Públicas e determinando que no dia 30 do corrente, às 23 horas, os relógios sejam atrasados de uma hora. PT 3843 BOCM 39 1945.09.29 regulando o horário das Repartições Públicas e determinando que no dia 30 do corrente, às 24 horas, os relógios sejam atrasados de uma hora. PT 3961 BOCM 17 1946.04.27 Determinando que, a partir das 23 horas do dia 30 do corrente mês, sejam adiantados de uma hora os relógios da Colónia. PT 4026 BOCM 39 1946.09.28 estabelecendo o horário da Repartições Públicas e determinando que no dia 30 do corrente, às 24 horas, os relógios sejam atrasados de uma hora. PT 4153 BOCM 16 1947.04.10 Determinando que, a partir das 23 horas do dia 19 do corrente mês, sejam adiantados de uma hora os relógios da Colónia. PT 4271 BOCM 48 1947.11.29 Determinando que, a aprtir do dia 30 do corrente às 24 horas, os relógios sejam atrasados de uma hora. PT 4374 BOCM 18 1948.05.01 Determina que, a partir das 23 horas do dia 2 do corrente mês, sejam adiantados de uma hora os relógios de Colónia. PT 4465 BOCM 44 1948.10.30 Determina que no dia 31 do corrente mês, às 24 horas, os relógios sejam atrasados de uma hora. PT 4590 BOCM 14 1949.04.02 Determina que, a partir das 23 horas do dia 2 do corrente mês, sejam adiantados de uma hora os relógios da Colónia. PT 4666 BOCM 44 1949.10.29 Determina que no dia 30 do corrente, a 0 hora, os relógios sejam atrasados de uma hora. PT 4771 BOCM 12 1950.03.25 Determina que, a partir das 23 horas do dia 1 do próximo mês de Abril, serão adiantados de uma horas os relógios da Colónia. PT 4838 BOCM 43 1950.10.28 Determina que no dia 28 do corrente, às 24 horas, os relógios sejam atrasados de uma hora. PT 4946 BOCM 12 1951.03.24 Determina que, a partir das 23 horas do dia 31 de Março do corrente ano, serão adiantados de uma hora os relógios desta colónia. PT 5025 BO 43 1951.10.27 Manda que no dia 29 do corrente, às zero horas, os relógios sejam atrasados de uma hora. PT 5149 BO 14 1952.04.05 Determina que a partir das 23 horas do dia 5 de Abril corrente serão adiantados de uma hora os relógios desta província. PT 5251 BO 43 1952.10.25 Determina que no dia 2 do próximo mês de Novembro, às zero horas, os relógios serão atrasados de uma hora. PT 5366 BO 13 1953.03.28 Determina que a partir das 23 horas do dia 4 do próximo mês de Abril serão adiantados de uma hora os relógios desta província. PT 5444 BO 44 1953.10.31 Determina que no dia 31 do corrente, às 24 horas, os relógios sejam atrasados de uma hora. PT 5540 BO 12 1954.03.20 Determina que, a partir das 23 horas de hoje, serão adiantados de uma hora os relógios da Província. PT 5589 BO 44 1954.10.30 Determina que, a partir das 24,00 horas de hoje, 30 do corrente, os relógios sejam atrasados de uma hora. PT 5676 BO 12 1955.03.19 Manda adiantar de uma hora os relógios da Província, a partir das 23 horas de hoje, 19 do corrente. PT 5739 BO 45 1955.11.05 Determina que às 24,00 horas de hoje, 5 de corrente, os relógios sejam atrasados de uma hora. PT 5823 BO 11 1956.03.17 Determina que a partir das 23 horas de hoje, 17 do corrente, serão adiantados de uma hora os relógios da Província. PT 5891 BO 44 1956.11.03 Determina que no dia 4 do corrente mês, às 3 horas e 30 minutos, os relógios sejam atrasados de uma hora. PT 5981 BO 12 1957.03.23 Determina que, a partir das 3,30 horas do dia 24 do corrente mês, sejam adiantados de uma hora os relógios da Província. PT 6064 BO 43 1957.10.26 Determina que no dia 3 do próximo mês do Novembro, às 3 horas e 30 minutos, os relógios sejam atrasados de uma hora. PT 6172 BO 12 1958.03.22 Determina que, a partir das 3,30 horas do dia 23 do corrente mês, sejam adiantados de uma hora os relógios da Província. PT 6243 BO 43 1958.10.25 Determina que no dia 2 do próximo mês do Novembro, às 3 horas e 30 minutos, os relógios sejam atrasados de uma hora. PT 6341 BO 12 1959.03.21 Determina que, a partir das 3,30 horas do dia 22 do corrente, sejam adiantados de uma hora os relógios da Província. PT 6411 BO 43 1959.10.24 Determina que no dia 1 do próximo mês de Novembro, às 3 horas e 30 minutos, os relógios sejam atrasados de uma hora. PT 6514 BO 11 1960.03.12 Determina que, a partir das 3,30 horas do dia 20 do corrente, sejam adiantados de uma hora os relógios da Província. PT 6584 BO 44 1960.10.29 Determina que no dia 6 do próximo mês de Novembro, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 6721 BO 10 1961.03.11 Determina que, a partir das 3,30 horas do dia 19 do corrente, sejam adiantados os relógios da Província. PT 6815 BO 43 1961.10.28 Determina que no dia 5 do próximo mês de Novembro, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 6947 BO 10 1962.03.10 Determina que a partir das 3,30 horas do dia 18 do corrente, sejam adiantados de uma hora os relógios da província. PT 7080 BO 43 1962.10.27 Determina que no dia 4 do próximo mês de Novembro, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 7218 BO 12 1963.03.23 Determina que a partir das 3,30 horas do dia 24 do corrente, sejam adiantados de uma hora os relógios de província. PT 7340 BO 43 1963.10.26 Detremina que a partir da 3,30 horas do dia 3 do próximo mês de Novembro, sejam atrasados de uma hora os relógios da província. PT 7491 BO 11 1964.03.14 Determina que a partir das 3,30 horas do dia 22 do corrente, os relógios sejam adiantados uma hora. PT 7664 BO 43 1964.10.24 Determina que a partir das 3,30 horas do dia 1 do próximo mês de Novembro, sejam atrasados de uma hora os relógios da província. PT 7846 BO 15 1965.04.10 Determina que a partir das 3,30 horas do dia 18 do corrente, os relógios sejam adiantados de uma hora. PT 7979 BO 42 1965.10.16 Determina que, a partir das 2,30 horas do próximo dia 17 do corrente, sejam atrasados de uma hora os relógios da província. PT 8146 BO 15 1966.04.09 Determina que os relógios da província sejam adiantados de uma hora, a partir das 3,30 horas do dia 17 do corrente. PT 8252 BO 41 1966.10.08 Determina que, às 2,30 horas do dia 16 do corrente, os relógios sejam atrasados de uma hora. PT 8429 BO 15 1967.04.15 Manda que no dia 16 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 8540 BO 41 1967.10.14 Manda que, no próximo dis 22 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 8735 BO 15 1968.04.13 Manda que no dia 21 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 8860 BO 41 1968.10.12 Manda que, no próximo dia 20 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 9035 BO 16 1969.04.19 Manda que no dia 20 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 9156 BO 42 1969.10.18 Manda que no dia 19 do corrente, às relógios sejam atrasados de uma hora. PT 9328 BO 15 1970.04.11 Manda que no dia 19 do corrente às 3,30 horas, os relógios sejam adiantados de uma hora. PT 9418 BO 41 1970.10.10 Manda que no dia 18 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 9587 BO 14 1971.04.03 Manda que no dia 18 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 9702 BO 41 1971.10.09 Manda que no dia 17 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 38-A/72 BO 14 1972.04.01 Manda que no dia 16 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 126-A/72 BO 41 1972.10.07 Manda que no dia 22 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 61/73 BO 14 1973.04.07 Manda que no dia 22 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 182/73 BO 40 1973.10.06 Manda que no dia 21 do corrente, às 3.30 horas, os relógios sejam atrasados de uma hora. PT 282/73 BO 51 1973.12.22 Manda que no dia 30 do corrente mês de Dezembro, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 177/74 BO 41 1974.10.12 Manda que no dia 20 do corrente, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 51/75 BO 15 1975.04.12 Manda que no dia 20 do corrente, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 173/75 BO 41 1975.10.11 Manda que no dia 19 do corrente mês, às 3,30 horas, os relógios sejam atrasados de uma hora. PT 67/76/M BO 14 1976.04.03 Manda que no dia 18 de Abril do corrente ano, às 3,30 horas, os relógios sejam adiantados de uma hora. PT 169/76/M BO 41 1976.10.09 Manda que, no dia 17 de Outubro corrente, às 3,30 horas, os relógios, sejam atrasados de uma hora. PT 78/79/M BO 19 1979.05.12 Manda que, no dia 13 de Maio de 1979, os relógios sejam adiantados de uma hora. PT 166/79/M BO 42 1979.10.20 Manda que, no dia 21 de Outubro de 1979, os relógios sejam atrasados de uma hora. Note that DIL 732 does not belong to "HORÁRIO DE VERÃO" according to LegisMac. Here is a list of time change according to the decrees, each change corresponds to each decree. Date Time Change 1941-12-21 Sun 2300 +1 1942-04-30 Thu 2300 +1 1942-11-17 Tue 2300 -1 1943-04-30 Fri 2300 +1 1943-09-30 Thu 2300 -1 1945-09-30 Sun 2400 -1 1946-04-30 Tue 2300 +1 1946-09-30 Mon 2400 -1 1947-04-19 Sat 2300 +1 1947-11-30 Sun 2400 -1 1948-05-02 Sun 2300 +1 1948-10-31 Sun 2400 -1 1949-04-02 Sat 2300 +1 1949-10-30 Sun 0000 -1 1950-04-01 Sat 2300 +1 1950-10-28 Sat 2400 -1 1951-03-31 Sat 2300 +1 1951-10-29 Mon 0000 -1 1952-04-05 Sat 2300 +1 1952-11-02 Sun 0000 -1 1953-04-04 Sat 2300 +1 1953-10-31 Sat 2400 -1 1954-03-20 Sat 2300 +1 1954-10-30 Sat 2400 -1 1955-03-19 Sat 2300 +1 1955-11-05 Sat 2400 -1 1956-03-17 Sat 2300 +1 1956-11-04 Sun 0330 -1 1957-03-24 Sun 0330 +1 1957-11-03 Sun 0330 -1 1958-03-23 Sun 0330 +1 1958-11-02 Sun 0330 -1 1959-03-22 Sun 0330 +1 1959-11-01 Sun 0330 -1 1960-03-20 Sun 0330 +1 1960-11-06 Sun 0330 -1 1961-03-19 Sun 0330 +1 1961-11-05 Sun 0330 -1 1962-03-18 Sun 0330 +1 1962-11-04 Sun 0330 -1 1963-03-24 Sun 0330 +1 1963-11-03 Sun 0330 -1 1964-03-22 Sun 0330 +1 1964-11-01 Sun 0330 -1 1965-04-18 Sun 0330 +1 1965-10-17 Sun 0230 -1 1966-04-17 Sun 0330 +1 1966-10-16 Sun 0230 -1 1967-04-16 Sun 0330 +1 1967-10-22 Sun 0330 -1 1968-04-21 Sun 0330 +1 1968-10-20 Sun 0330 -1 1969-04-20 Sun 0330 +1 1969-10-19 Sun 0330 -1 1970-04-19 Sun 0330 +1 1970-10-18 Sun 0330 -1 1971-04-18 Sun 0330 +1 1971-10-17 Sun 0330 -1 1972-04-16 Sun 0330 +1 1972-10-22 Sun 0330 -1 1973-04-22 Sun 0330 +1 1973-10-21 Sun 0330 -1 1973-12-30 Sun 0330 +1 1974-10-20 Sun 0330 -1 1975-04-20 Sun 0330 +1 1975-10-19 Sun 0330 -1 1976-04-18 Sun 0330 +1 1976-10-17 Sun 0330 -1 1979-05-13 Sun 0330 +1 1979-10-21 Sun 0330 -1 Note that between 1942 and 1945, the time switched between GMT+9 and GMT+10. Also in 1965 and 1965 the DST ended at 2:30am. I actually don't speak Portuguese, please correct me if I'm wrong. Regards, P Chan

2 1

'Pyongyang Time' scrapped as North Korea synchronises clocks with the South
by Kim Sungwoo May 9, 2018

May 9, 2018

Hello, I am Sungwoo Kim, leave in Seoul, Republic of Korea. (South Korea) Since 5. 5. 2018, Pyongyang Time - North Korea time - had synchronized with South. We should discussion how we can synchronize PYT to KST with less side-effect. Here is articles include more information and backgrounds. https://www.telegraph.co.uk/news/2018/05/05/pyongyang-time-scrapped-north-k… http://www.xinhuanet.com/english/2018-05/05/c_137158132.htm http://calgarysun.com/news/world/no-more-pyongyang-time-north-korea-changes… https://qz.com/1265352/north-korea-will-reunifying-its-time-zone-with-south…

4 3

China DST
by chan jason May 7, 2018

May 7, 2018

Hi, There are some mistakes in the rules of PRC. The start and end time of DST in China should be 2:00 (i.e. 2:00 to 3:00 at the start and 2:00 to 1:00 at the end). Also in 1988, the start date should be 17 May instead of 10 May. Government notices about summer time: 1986-04-12 http://www.zj.gov.cn/attach/zfgb/198608.pdf p.21-22 (To establish summer time from 1986. On 4 May, set the clocks ahead one hour at 2 am. On 14 September, set the clocks backward one hour at 2 am.) 1987-02-15 http://www.gov.cn/gongbao/shuju/1987/gwyb198703.pdf p.114 (Summer time in 1987 to start from 12 April until 13 September) 1987-09-09 http://www.gov.cn/gongbao/shuju/1987/gwyb198721.pdf p.709 (From 1988, summer time to start from 2 am of the first Sunday of mid-April until 2 am of the first Sunday of mid-September) 1992-03-03 http://www.gov.cn/gongbao/shuju/1992/gwyb199205.pdf p.152 (To suspend summer time from 1992) The first page of People's Daily on 12 April 1988 stating that summer time to begin on 17 April. http://data.people.com.cn/pic/101p/1988/04/1988041201.jpg Proposed rules: Rule PRC 1986 only - May 4 2:00 1:00 D Rule PRC 1986 1991 - Sep Sun>=11 2:00 0 S Rule PRC 1987 1991 - Apr Sun>=11 2:00 1:00 D Regards, P Chan

4 4

Update for tz-how-to.html?
by Kerry Shetline May 6, 2018

May 6, 2018

Could we get an update to the tz-how-to.html document which: 1) Explains how to parse tzdata files for vanguard, rearguard, and standard versions? It looks like the way vanguard sections are not commented out, and rearguard sections are, that any third-party parser for tzdata is going to pick up vanguard zones and rules by default, rather than main. What I’d like to know how to parse the tzdata files, directly as they are found in a standard distribution, with rearguard, main, or vanguard results in mind, and without to run "make tarballs” to get a specific version. 2) Demonstrates the usage of the new ’s' and ‘d' suffixes in SAVE columns? Any help with these issues would be much appreciated. -Kerry

2 1

[PROPOSED] Today's North Korea change was at 23:30, not 24:00
by Paul Eggert May 4, 2018

May 4, 2018

* NEWS, asia (Asia/Pyongyang): Implement this. --- NEWS | 5 +++++ asia | 6 +++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 90452b7..79d9d80 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ News for the tz database Unreleased, experimental changes + Changes to past time stamps + + The 2018-05-05 North Korea 30-minute time zone change took place + at 23:30 the previous day, not at 00:00 that day. + Changes to build procedure New 'make' target 'rearguard_tarballs' to build the rearguard diff --git a/asia b/asia index 3d30864..2e829b8 100644 --- a/asia +++ b/asia @@ -1995,6 +1995,10 @@ Rule ROK 1987 1988 - Oct Sun>=8 3:00 0 S # Assembly, as published in Rodong Sinmun. # From Tim Parenti (2018-04-29): # It appears to be the front page story at the top in the right-most column. +# +# From Paul Eggert (2018-05-04): +# The BBC reported that the transition was from 23:30 to 24:00 today. +# https://www.bbc.com/news/world-asia-44010705 # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Seoul 8:27:52 - LMT 1908 Apr 1 @@ -2007,7 +2011,7 @@ Zone Asia/Pyongyang 8:23:00 - LMT 1908 Apr 1 8:30 - KST 1912 Jan 1 9:00 - JST 1945 Aug 24 9:00 - KST 2015 Aug 15 00:00 - 8:30 - KST 2018 May 5 + 8:30 - KST 2018 May 4 23:30 9:00 - KST ############################################################################### -- 2.7.4

1 0

Morocco TZ
by Sebastien WILLEMIJNS May 4, 2018

May 4, 2018

Morocco TZ changes in 8 days... i think the list knew... https://www.africatopsuccess.com/2018/05/03/maroc-changement-dhoraire-dhive… -- --- Sébastien WILLEMIJNS

2 1

Re: [tz] [tz-announce] 2018e release of tz code and data available
by Paul Eggert May 4, 2018

May 4, 2018

On 05/04/2018 07:52 AM, J William Piggott wrote: > On 05/03/2018 08:22 PM, Paul Eggert wrote: > > 8< ... > >> ; effectively the main format now uses vanguard instead of rearguard format. > 8< ... > >> The full effect of this change is only in vanguard format; in rearguard and >> main format, the tm_isdst flag is still zero in winter and nonzero in summer. > ... > > Aren't these to statements contradictory? Yes they are, and that typo wasn't fixed until after the 2018e release was cut. You can see a copy of the fix here: https://mm.icann.org/pipermail/tz/2018-May/026447.html

1 0

[tz-announce] 2018e release of tz code and data available
by Paul Eggert May 3, 2018

May 3, 2018

The 2018e 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: North Korea switches back to +09 on 2018-05-05. The main format uses negative DST again, for Ireland etc. 'make tarballs' now also builds a rearguard tarball. New 's' and 'd' suffixes in SAVE columns of Rule and Zone lines. Changes to past and future time stamps North Korea switches back from +0830 to +09 on 2018-05-05. (Thanks to Kang Seonghoon, Arthur David Olson, Seo Sanghyeon, and Tim Parenti.) Bring back the negative-DST changes of 2018a, except be more compatible with data parsers that do not support negative DST. Also, this now affects historical time stamps in Namibia and the former Czechoslovakia, not just Ireland. The main format now uses negative DST to model time stamps in Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and Africa/Windhoek (1994/2017). This does not affect UT offsets, only time zone abbreviations and the tm_isdst flag. Also, this does not affect rearguard or vanguard formats; effectively the main format now uses vanguard instead of rearguard format. Data parsers that do not support negative DST can still use data from the rearguard tarball described below. Changes to build procedure The command 'make tarballs' now also builds the tarball tzdataVERSION-rearguard.tar.gz, which is like tzdataVERSION.tar.gz except that it uses rearguard format intended for trailing-edge data parsers. Changes to data format and to code The SAVE column of Rule and Zone lines can now have an 's' or 'd' suffix, which specifies whether the adjusted time is standard time or daylight saving time. If no suffix is given, daylight saving time is used if and only if the SAVE column is nonzero; this is the longstanding behavior. Although this new feature is not used in tzdata, it could be used to specify the legal time in Namibia 1994-2017, as opposed to the popular time (see below). Changes to past time stamps From 1994 through 2017 Namibia observed DST in winter, not summer. That is, it used negative DST, as Ireland still does. This change does not affect UTC offsets; it affects only the tm_isdst flag and the abbreviation used during summer, which is now CAT, not WAST. Although (as noted by Michael Deckers) summer and winter time were both simply called "standard time" in Namibian law, in common practice winter time was considered to be DST (as noted by Stephen Colebourne). The full effect of this change is only in vanguard 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. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2018e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2018e.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2018e.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 4758e88f99c71af65d73ce730e87438466032a5f dated 2018-05-01 23:42:51 -0700 and tagged '2018e' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 4a245cae2d0922b24539a94cf4a8ccc2bba1ee696e0aaefecb41c7c8d78724a7fcea6039909336177b8b26fec8fc47719e3e56ca9839dbaf52f9a4fec84d4717 tzcode2018e.tar.gz d059fcd381b2f6ecdafcd68fdd2a00451d1bf9b1affeb164ae7cabca2e022d499e77f0706ec3f3091b8e84c2211aa66da6c90937108771f1bf070cfebc105cae tzdata2018e.tar.gz afb7569cc9faef6e3d2be16ceef65f8531ac123dac14e3b40a4f54dab916e930b09eb665458e55f98398c4b8c5d108f34985a42bf711b2170de90d819bf0e630 tzdb-2018e.tar.lz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJa6V9nAAoJEO2X6Q5iqn40r+EQAJSt3ap8G8swYPzBg6TstckZ tOxrDcGlRu4km6jzIhHelOwj2Sxw8X/0JyRc09xbGbXGE/mv35DrzKC8ijfazu9pg Mr4eOclfFGq8l48aRag86hR33k62K84Xdl0WrwVFVefhlsRel9i6lXnBFcmgHl/C vSwJXyrZ2DgvZH88B6j8qnYkw/BMbsTKLM1L/3EHxKZqq/TCHS19Z1XbbkF6mm/u 73aHHmXEnpSVol+3aekEKuS+PSdc+loYaAMvibBJ34ci2bc1X1HkOPF30dRSTETW pVtKXp1qFtmHRR07I28l7/jEzmI+XPheCswhOKowWqKe59tA2CTiFnkhuBQUmoZS XDjKpcgvrad9RSES1aVAfVn2iCx78Inu0W8UIWZ/eiMOh0taQH3n7K1KBnLwCEKd rAB9ummGRK787XJEe2/xnH/h0lilU7Ye6EddNwuGf5Q3PlS9brDov66dnIUWi76L uPRTufummczt6XcA9YL0zEhwvAzjSSqQzoga7mXBKSIwakRoKXCIoux+EdQOWNOy /VUMH5NIkND+kRcRdqTXs93Whu7SCV14DKi5j1LL39YC8nqGi0q3u8wndm22AhCr ZR9uMv1Qq1iCXb09sIBfdi7bf0S8348jz1deb/d7jgJ4ISBR7v8UiR3Z/JO8hiPR QSP93j37rjAsFyBSWMxq =knlj -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJa6V9nAAoJEO2X6Q5iqn40qYUQAI21DF4x+Qr9uhMf5UL3u/UI BnLTeDqc4t1oLbuuJsbtgausc/m6EIgo2j9+uadXefnguP4fwKHJ2doReuRZ3njI hGnqP2+yCfTRNrZYBU3p6U+/OJq8r/UBsn9aGxNStcZHe6FswnxXWlzpRNbPdNBC nGeYMs2HOQjcdG08BF1sjGm4FC/NS6bugNhs0EcrMLaVa+c0keRWNg9o7Y/SvrZB awFAMz4LhOog2qxhGWtFgSVRAAj5aEDqugOXZL27VszgGPexiAaMCFyQARIHigIw 959D7RYmpeNuEeP6XbzGFgDO6aMbxahoUpP9cCOUI6qKShtDKnY2XkjPmVQiAfjZ zvpsE1dYbWyVTWqWhWL3z0lPCFN6B4eneY6UXY/KtENRl1jEafKN5/7JqKOMBSRo umE1Jy6qSSz5jLuz5pX59iOXWZETIlwtAW6lKe2s6l9xWPL9R8xXoPvbQRadqDxB uANcGZSrKD1jKuybPJa/6BZRF+FlldCkZVVKSSdXuPLF1HhohlvFZqi1WPmWvGd+ s/1+3OhWzB4BHyrp3Wbtj+ZwCtg9UVbJLBM2bgL9nGEyv/1XSxgLJEp3rneIMpJv AMK8rr3XehXLDkXAfx68Mzs3F4lYEdXk6y9f9ZsVj+IdBotwzzjJWeCfnlmJM52y 8cCrPGUjdneFidV9OZ+J =4LFO -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJa6V9pAAoJEO2X6Q5iqn40EBwP/1fxMc1IozcXCWSm+h/XZ3M+ bImmIdf8Ws/FZC5yXHWkU4n3DZN6A2Xf/dDTDaZPeyhL3rjd6ju0zxTsQpxdqRms FrEiqlq2CpIVe+pY4EeowfsFdKVYIxtiTw9BNytaDOIgYxRmokNUQusaHw2qrZg6 t6giUhH6bh1/YgZakFP65WItjESR8Dg4aJ7X1f8BJkSEyy9I2lnyWOG7LwB8xNvS YRPRjkVqdVXzdS9MtqO+U5b9pe1MvU6q0lRAOwUvZsGfB7fULkdQcS1XaYDVRdPA WdMKqn21S+oRHYzX5/BZHE68uGFlufPohikYfSCO6pk8eqDe0xbkOl6fpgjjqTZf wCAcZBBoCP11lH8Omdu8bW6LJ0q1jkwuCZxmLBPwonInoByPO/TeDstYSp39KCv2 +w0pl87uYe6/IEwSC1bH0HBF8kzcEq5q5JVHLyqwOKrAm6Nfm5sC5vWFhk3GmMGU FGpFLnwUJlTefy9X3ds8zEvmCAiFMisu5cciMRwfCLvTHSObRGEXtp5pxpr0VhBf A6Qc+83JPTwhEWdVQMVbEWRkkJNG50xAwOhjJaClXjjlvJqQtpUPHLR7fRaQWvm8 sCXhh+PeWpgIbbzaE7TzkVu9sLUGiIvbLiP2yNMOuoZp+UUnrsSaswbeCl0bkGe3 LSswAxioa5rs8zd8WtZe =/AeX -----END PGP SIGNATURE----- PS. If your tzdata parser does not yet support negative DST offsets,this particular release's data entries are also available in arearguard-format tarball and signature that does not contain suchoffsets. This is intended to be a temporary transition aid for theseparsers. The URLs are: https://web.cs.ucla.edu/~eggert/tz/release/2018e/tzdata2018e-rearguard.tar.… https://web.cs.ucla.edu/~eggert/tz/release/2018e/tzdata2018e-rearguard.tar.… with the following SHA-512 and GPG checksums: dd92cf2d01388d52731db7569360e3c7e673c3189c8cba807d031fb6b6ce8c115d3f4de3be1c7a6b1e038fa919efdd254cdd4f7731c3130b447dee2c7c5814a4 tzdata2018e-rearguard.tar.gz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJa6V9oAAoJEO2X6Q5iqn40jJMP+gKGNy3VBhJ9B2/plNXta2nH M5fAwJphPXutCv2ums0LPVNbi0FWjPo9T2/6Lmy71vyyusW/9ltS+/bECSnmrZRO VEql2UWghxGMaV3Y2wpFI2XGqepQYsT9Xa1tgXUvXHakQPYe5Osx0J3P50F9ROMy kiWR4VSsSE3IZDiZC32HQjcHsREcUtpgYfn943Zr1Go2FRnp2esnbN0eQtTV5vJW uSYWdfSNWNsSqXR9O2cq9kzCeVKxZjjs2hi1adIrQLzQKy26RXUC9f4tepzRrPfT euHiHUrZXE5p2161Q702P1Nw3zPFrA/SHiFZTpP84mri60RVZTWPP21ityktFukt B+Ebkpd7EwyyFFZB1grbnb1uLc2qkM76gKtIPJAtkWEe7BwwwREh9d/92K/L9XTe opehULRUjX65UyOWNUD9dl3aiy1FHQyWAuX3fRF1u2vrh3WSuIHbO0Uq9RCMQtHP VSY45Ldwv3+PGfyaKlQvftqFAFJ2kjmIC7zQZe5HmBIYG8TIyUCS/P17XZzIrEpw aBNrPe4hV63DSVEvBYLHaCPMMIASASBvSZ2S5Rb2HopAzVd6xOYSvGCqwjdtFpr6 1bD4EeIb2wBxPWH8KFZiSDYK/FpfhuZR7teY6bzG+fsZMtzChP4pcQrebMD3RIPZ RBDXrhtfn+5b78wn6VMM =VPo7 -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Pyongyang Time transition plan announced
by Seo Sanghyeon May 2, 2018

May 2, 2018

Rodong Sinmun 2018-04-30 announced Pyongyang Time transition plan. https://www.nknews.org/kcna/wp-content/uploads/sites/5/2018/04/rodong-2018-… I won't translate, but even if you don't know Korean it should be easy to confirm that the transition date is 2018-05-05. 2018 is Juche 107. Citation should be Decree No. 2232 of April 30, 2018, of the Presidum of the Supreme People's Assembly, as published in Rodong Sinmun. -- Seo Sanghyeon

7 12

[PROPOSED] Fix typos in 2018e historical NEWS
by Paul Eggert May 2, 2018

May 2, 2018

* NEWS: Fix typos in description of 2018e’s changes to historical timestamps in Namibia and Czechoslovakia. --- NEWS | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index e985ce6..90452b7 100644 --- a/NEWS +++ b/NEWS @@ -64,12 +64,12 @@ Release 2018e - 2018-05-01 23:42:51 -0700 both simply called "standard time" in Namibian law, in common practice winter time was considered to be DST (as noted by Stephen Colebourne). The full effect of this change is only in vanguard - format; in rearguard and main format, the tm_isdst flag is still + and main format; in rearguard format, the tm_isdst flag is still zero in winter and nonzero in summer. In 1946/7 Czechoslovakia also observed negative DST in winter. - The full effect of this change is only in vanguard format; in - rearguard and main formats, it is modeled as plain GMT without + The full effect of this change is only in vanguard and main + formats; in rearguard format, it is modeled as plain GMT without daylight saving. Also, the dates of some 1944/5 DST transitions in Czechoslovakia have been changed. -- 2.17.0

1 0

[PROPOSED] Port better to GCC 8
by Paul Eggert May 1, 2018

May 1, 2018

* private.h (ATTRIBUTE_MALLOC): New macro. Use this and related macros starting with GCC 3.0, not GCC 2.96 which was not an official release. * zdump.c (xmalloc): * zic.c (emalloc, ecpyalloc): Use it to pacify -Wsuggest-attribute=malloc with GCC 8. --- private.h | 4 +++- zdump.c | 2 +- zic.c | 4 ++-- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/private.h b/private.h index 705544e..641f905 100644 --- a/private.h +++ b/private.h @@ -342,12 +342,14 @@ typedef unsigned long uintmax_t; #define SIZE_MAX ((size_t) -1) #endif -#if 2 < __GNUC__ + (96 <= __GNUC_MINOR__) +#if 3 <= __GNUC__ # define ATTRIBUTE_CONST __attribute__ ((const)) +# define ATTRIBUTE_MALLOC __attribute__ ((__malloc__)) # define ATTRIBUTE_PURE __attribute__ ((__pure__)) # define ATTRIBUTE_FORMAT(spec) __attribute__ ((__format__ spec)) #else # define ATTRIBUTE_CONST /* empty */ +# define ATTRIBUTE_MALLOC /* empty */ # define ATTRIBUTE_PURE /* empty */ # define ATTRIBUTE_FORMAT(spec) /* empty */ #endif diff --git a/zdump.c b/zdump.c index 1081648..a4d9108 100644 --- a/zdump.c +++ b/zdump.c @@ -136,7 +136,7 @@ sumsize(size_t a, size_t b) /* Return a pointer to a newly allocated buffer of size SIZE, exiting on failure. SIZE should be nonzero. */ -static void * +static void * ATTRIBUTE_MALLOC xmalloc(size_t size) { void *p = malloc(size); diff --git a/zic.c b/zic.c index 90ae1f4..31f1092 100644 --- a/zic.c +++ b/zic.c @@ -447,7 +447,7 @@ memcheck(void *ptr) return ptr; } -static void * +static void * ATTRIBUTE_MALLOC emalloc(size_t size) { return memcheck(malloc(size)); @@ -459,7 +459,7 @@ erealloc(void *ptr, size_t size) return memcheck(realloc(ptr, size)); } -static char * +static char * ATTRIBUTE_MALLOC ecpyalloc (char const *str) { return memcheck(strdup(str)); -- 2.17.0

1 0

[PROPOSED] Use GCC 8 for debugging
by Paul Eggert April 30, 2018

April 30, 2018

* Makefile (GCC_DEBUG_FLAGS): Use flags appropriate for GCC 8. --- Makefile | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 3ac1a67..21fa488 100644 --- a/Makefile +++ b/Makefile @@ -236,14 +236,16 @@ GCC_DEBUG_FLAGS = -DGCC_LINT -g3 -O3 -fno-common \ $(GCC_INSTRUMENT) \ -Wall -Wextra \ -Walloc-size-larger-than=100000 -Warray-bounds=2 \ - -Wbad-function-cast -Wcast-align -Wdate-time \ + -Wbad-function-cast -Wcast-align=strict -Wdate-time \ -Wdeclaration-after-statement -Wdouble-promotion \ -Wformat=2 -Wformat-overflow=2 -Wformat-signedness -Wformat-truncation \ -Winit-self -Wjump-misses-init -Wlogical-op \ -Wmissing-declarations -Wmissing-prototypes -Wnested-externs \ -Wold-style-definition -Woverlength-strings -Wpointer-arith \ - -Wshadow -Wshift-overflow=2 -Wstrict-prototypes -Wstringop-overflow=5 \ + -Wshadow -Wshift-overflow=2 -Wstrict-prototypes -Wstringop-overflow=4 \ + -Wstringop-truncation -Wsuggest-attribute=cold \ -Wsuggest-attribute=const -Wsuggest-attribute=format \ + -Wsuggest-attribute=malloc \ -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure \ -Wtrampolines -Wundef -Wuninitialized -Wunused \ -Wvariadic-macros -Wvla -Wwrite-strings \ -- 2.17.0

1 0

DPRK to revert to UTC+9 from UTC+8:30
by Kang Seonghoon April 30, 2018

April 30, 2018

On 2018-04-29 (+09:00), according to Yoon Young-chan, senior presidental secretary for public relations of South Korea, has announced that North Korea will revert its time zone from UTC+8:30 (PYT; Pyongyang Time) back to UTC+9 (KST; Korea Standard Time), in lieu of the recent Panmunjom Declaration. Yet another time to change tzdata? Source: South and North agreed to unify PYT to KST, Yonhap News http://m.yna.co.kr/kr/contents/?cid=AKR20180429018500001 (no English translation exists right now) -- -- Kang Seonghoon | https://mearie.org/ -- Opinions expressed in this email do not necessarily represent the views of my employer. --

4 4

North Korea timezone to become GMT+9 from May 5 2018
by Phake Nick April 30, 2018

April 30, 2018

The URL to the announcement cannot be directly copied, but you can access www.kcna.kp then select "English" on top right hand corner, and then there will be an article titled "SPA Presidium of DPRK Decides to Reset Pyongyang Time" which talk about the upcoming change in time in North Korea. Media outside North Korea have reported about it too. However, there are no info with respect to exactly which moment in May 5 are they switching their timezone

3 3

North Korea to match South Korea's time zone
by Arthur David Olson April 29, 2018

April 29, 2018

A tweet from Jef Poskanzer... https://twitter.com/jef_poskanzer/status/990430801903865856 ...alerted me to North Korea's plan to match South Korea's time zone. An AP item on the matter... https://apnews.com/301adfec088647c1b1cbc69eb4b0949a ...cites South Korean President Moon Jae-in's spokesperson Yoon Young-chan; referring to North Korean leader Kim Jong Un, " Yoon said Kim...revealed plans to re-adjust its current time zone to match the South’s." No word in the AP item on specifics of the plan. @dashdashado

2 1

[PROPOSED] Support zi parsers that mishandle negative DST offsets
by Paul Eggert April 22, 2018

April 22, 2018

This is intended to provide a way to support both clients that require data to have only positive DST offsets, and clients that do not have this restriction. * Makefile (XDST, SDST): New macros. (TZDATA_ZI_DEPS): Add zidst.awk. (DSTDATA_ZI_DEPS): New macro. (all): Depend on fulldata.zi and pdstdata.zi. (fulldata.zi pdstdata.zi): New rule. (tzdata.zi): Use $(XDST)data.zi instead of reading original source. (check_zishrink): Check zidst.awk, too. (clean): Remove all *.zi files, not just tzdata.zi. * NEWS, europe: Mention this. * zidst.awk: New file. --- Makefile | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++----------- NEWS | 30 ++++++++++++++++++++++++++++++ europe | 39 ++++++++++++++++++++++----------------- zidst.awk | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 154 insertions(+), 28 deletions(-) create mode 100644 zidst.awk diff --git a/Makefile b/Makefile index 8c84cd9..92ddb80 100644 --- a/Makefile +++ b/Makefile @@ -10,6 +10,26 @@ 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. + # 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 @@ -463,7 +483,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= zishrink.awk version $(TDATA) $(PACKRATDATA) +TZDATA_ZI_DEPS= zidst.awk zishrink.awk version $(TDATA) $(PACKRATDATA) +DSTDATA_ZI_DEPS= zidst.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 @@ -500,7 +521,8 @@ VERSION_DEPS= \ SHELL= /bin/sh -all: tzselect yearistype zic zdump libtz.a $(TABDATA) +all: tzselect yearistype zic zdump libtz.a $(TABDATA) \ + fulldata.zi pdstdata.zi ALL: all date $(ENCHILADA) @@ -535,11 +557,15 @@ version: $(VERSION_DEPS) printf '%s\n' "$$V" >$@.out mv $@.out $@ -# This file can be tailored by setting BACKWARD, PACKRATDATA, etc. -tzdata.zi: $(TZDATA_ZI_DEPS) +# 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) \ + >$@.out + mv $@.out $@ +tzdata.zi: $(XDST)data.zi version version=`sed 1q version` && \ LC_ALL=C $(AWK) -v version="$$version" -f zishrink.awk \ - $(TDATA) $(PACKRATDATA) >$@.out + $(XDST)data.zi >$@.out mv $@.out $@ version.h: version @@ -721,17 +747,32 @@ check_tzs: $(TZS) $(TZS_NEW) 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) +# 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_zishrink: zic leapseconds $(PACKRATDATA) $(TDATA) \ + $(XDST)data.zi tzdata.zi for type in posix right; do \ - mkdir -p time_t.dir/$$type time_t.dir/$$type-shrunk && \ + mkdir -p time_t.dir/$$type time_t.dir/$$type-$(SDST) \ + time_t.dir/$$type-shrunk && \ case $$type in \ right) leap='-L leapseconds';; \ *) leap=;; \ esac && \ - $(ZIC) $$leap -d time_t.dir/$$type $(TDATA) && \ - $(AWK) '/^Rule/' $(TDATA) | \ + $(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) && \ + $(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);; \ + esac && \ $(ZIC) $$leap -d time_t.dir/$$type-shrunk tzdata.zi && \ diff -r time_t.dir/$$type time_t.dir/$$type-shrunk || exit; \ done @@ -741,7 +782,7 @@ clean_misc: rm -f core *.o *.out \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc - rm -fr *.dir tzdata.zi tzdb-*/ $(TZS_NEW) + rm -fr *.dir *.zi tzdb-*/ $(TZS_NEW) maintainer-clean: clean @echo 'This command is intended for maintainers to use; it' diff --git a/NEWS b/NEWS index 4f763c0..c455f3c 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,36 @@ News for the tz database Unreleased, experimental changes + Briefly: + Support zi parsers that mishandle negative DST offsets + + 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. + Changes to code The code is a bit more portable to MS-Windows. (Thanks to Manuela diff --git a/europe b/europe index 6c1ccbe..5aeda33 100644 --- a/europe +++ b/europe @@ -508,11 +508,27 @@ Link Europe/London Europe/Jersey Link Europe/London Europe/Guernsey Link Europe/London Europe/Isle_of_Man -# From Paul Eggert (2018-01-19): +# From Paul Eggert (2018-01-30): +# In January 2018 we discovered that the negative DST offsets in the +# Eire rules cause problems with tests for ICU: +# 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. +# # The following is like GB-Eire and EU, except with standard time in # summer and negative daylight saving time in winter. -# Although currently commented out, this will need to become uncommented -# once the ICU/OpenJDK workaround is removed; see below. +# This rule set is active in fulldata.zi and is commented out in +# pdstdata.zi. # 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 @@ -533,24 +549,13 @@ 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 -# From Paul Eggert (2018-01-18): -# The next line should look like this: +# The next line is active in fulldata.zi and commented out in pdstdata.zi. # 1:00 Eire IST/GMT -# However, in January 2018 we discovered that the Eire rules cause -# problems with tests for ICU: -# 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, use a traditional approximation for -# time stamps after 1971-10-31 02:00 UTC, to give ICU and OpenJDK -# developers breathing room to fix bugs. This approximation has -# correct UTC offsets, but results in tm_isdst flags are the reverse -# of what they should be. This workaround is temporary and should be -# removed reasonably soon. +# These three lines are active in pdstdata.zi and commented out in +# fulldata.zi. 1:00 - IST 1971 Oct 31 2:00u 0:00 GB-Eire GMT/IST 1996 0:00 EU GMT/IST -# End of workaround for ICU and OpenJDK bugs. ############################################################################### diff --git a/zidst.awk b/zidst.awk new file mode 100644 index 0000000..7885e9a --- /dev/null +++ b/zidst.awk @@ -0,0 +1,50 @@ +# 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 } -- 2.14.3

7 14

[PATCH] Fix ziguard.awk Namibia invalid assumption
by Paul Eggert April 22, 2018

April 22, 2018

* ziguard.awk: Don’t assume input is in rearguard format. --- ziguard.awk | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ziguard.awk b/ziguard.awk index 7cdceab..dbe64d6 100644 --- a/ziguard.awk +++ b/ziguard.awk @@ -63,7 +63,11 @@ outfile != "main.zi" { || (1994 <= $(in_comment + 4) && $(in_comment + 4) <= 2017) \ || in_comment + 3 == NF)) if (Rule_Namibia || Zone_using_Namibia_rule) { - if (in_comment == vanguard) { + if ((Rule_Namibia \ + ? ($(in_comment + 9) ~ /^-/ \ + || ($(in_comment + 9) == 0 && $(in_comment + 10) == "CAT")) \ + : $(in_comment + 1) == "2:00" && $(in_comment + 2) == "Namibia") \ + == vanguard) { uncomment = in_comment } else { comment_out = !in_comment -- 2.14.3

1 0

[PROPOSED] Update and/or clean up POSIX version info
by Paul Eggert April 15, 2018

April 15, 2018

--- asctime.c | 12 +++--------- localtime.c | 7 +++---- theory.html | 2 +- 3 files changed, 7 insertions(+), 14 deletions(-) diff --git a/asctime.c b/asctime.c index a55f785..56c54b3 100644 --- a/asctime.c +++ b/asctime.c @@ -1,3 +1,5 @@ +/* asctime and asctime_r a la POSIX and ISO C, except pad years before 1000. */ + /* ** This file is in the public domain, so clarified as of ** 1996-06-05 by Arthur David Olson. @@ -29,7 +31,7 @@ ** leading zeroes to get the newline in the traditional place. ** The -4 ensures that we get four characters of output even if ** we call a strftime variant that produces fewer characters for some years. -** The ISO C 1999 and POSIX 1003.1-2004 standards prohibit padding the year, +** The ISO C and POSIX standards prohibit padding the year, ** but many implementations pad anyway; most likely the standards are buggy. */ #ifdef __GNUC__ @@ -64,10 +66,6 @@ static char buf_asctime[MAX_ASCTIME_BUF_SIZE]; -/* -** A la ISO/IEC 9945-1, ANSI/IEEE Std 1003.1, 2004 Edition. -*/ - char * asctime_r(register const struct tm *timeptr, char *buf) { @@ -117,10 +115,6 @@ asctime_r(register const struct tm *timeptr, char *buf) } } -/* -** A la ISO/IEC 9945-1, ANSI/IEEE Std 1003.1, 2004 Edition. -*/ - char * asctime(register const struct tm *timeptr) { diff --git a/localtime.c b/localtime.c index b6b82bb..5b5a5b1 100644 --- a/localtime.c +++ b/localtime.c @@ -88,9 +88,8 @@ static const char gmt[] = "GMT"; /* ** The DST rules to use if TZ has no rules and we can't load TZDEFRULES. ** Default to US rules as of 2017-05-07. -** POSIX 1003.1 section 8.1.1 says that the default DST rules are -** implementation dependent; for historical reasons, US rules are a -** common default. +** POSIX does not specify the default DST rules; +** for historical reasons, US rules are a common default. */ #ifndef TZDEFRULESTRING #define TZDEFRULESTRING ",M3.2.0,M11.1.0" @@ -2211,7 +2210,7 @@ timeoff(struct tm *tmp, long offset) #ifdef STD_INSPIRED /* -** IEEE Std 1003.1-1988 (POSIX) legislates that 536457599 +** IEEE Std 1003.1 (POSIX) says that 536457599 ** shall correspond to "Wed Dec 31 23:59:59 UTC 1986", which ** is not the case if we are accounting for leap seconds. ** So, we provide the following conversion routines for use diff --git a/theory.html b/theory.html index b27b212..fc2102b 100644 --- a/theory.html +++ b/theory.html @@ -68,7 +68,7 @@ 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 +Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018 Edition. Because the database's scope encompasses real-world changes to civil timekeeping, its model for describing time is more complex than the -- 2.7.4

1 0

[PROPOSED] * europe: Adjust to kalendar.beda.cz correction.
by Paul Eggert April 15, 2018

April 15, 2018

--- europe | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/europe b/europe index 160be9f..6b97fd0 100644 --- a/europe +++ b/europe @@ -971,14 +971,9 @@ Zone Europe/Sofia 1:33:16 - LMT 1880 # Czech Republic / Czechia # -# From Paul Eggert (2018-04-14): -# The source for Czech data is: Kdy začíná a končí letní čas. +# From Paul Eggert (2018-04-15): +# The source for Czech data is: Kdy začíná a končí letní čas. 2018-04-15. # 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. # -- 2.14.3

1 0