- tz - lists.iana.org

Incorrect Time Zone Data for American/Grand_Turk
by Robert MacGrogan Aug. 4, 2018

Aug. 4, 2018

Hi there. It looks to me like the time zone data for America/Grand_Turk is incorrect in 2018e version of the database. Turks and Caicos switched to supporting daylight savings time in March of 2018. So in summer the correct time for America/Ground_Turk should be GMT -4 and then back to GMT -5 again in the fall. The current database returns times for summer of 2018 as GMT -5, which is incorrect. Thank you. -- Rob MacGrogan | Director of Software Development rmacgrogan(a)flightbridge.com <rmacgrogan(a)flightbridge.com> 850-509-6158 [image: FlightBridge] <http://www.flightbridge.com/> FlightBridge, Inc. 530 Means Street, Suite 405 Atlanta, GA 30318 www.flightbridge.com

7 19

[PROPOSED] One line per metadatum in tzdata.zi
by Paul Eggert July 31, 2018

July 31, 2018

With the new metadata, version lines could be long. E.g., 'make DATAFORM=rearguard REDO=posix_only PACKRATDATA=backzone BACKWARD=' could generate a tzdata.zi line like this: # version 2018e-57-gba7f088,dataform=rearguard,redo=posix_only,ddeps=(backzone,!backward) which is quite a mouthful and is stretching the definition of "version". To avoid the problem, output a separate comment line for each metadata component instead, like this: # version 2018e-57-gba7f088 # dataform rearguard # redo posix_only # ddeps backzone !backward This is easier to read and to parse and should scale better if we add more metadata later. * NEWS: Mention this. * zishrink.awk: Output a separate line for each metadatum. 2018-07-21 Paul Eggert <eggert(a)cs.ucla.edu> Use space, not comma, in tzdata.zi "# version" * zishrink.awk: Use space instead of comma to separate original version string from auxiliary configuration information. This saves two bytes and (more important) is easier for humans to read. --- NEWS | 16 ++++++++-------- zishrink.awk | 20 ++++++++++---------- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/NEWS b/NEWS index 413d649..a3fc622 100644 --- a/NEWS +++ b/NEWS @@ -92,14 +92,14 @@ Unreleased, experimental changes tzdata.zi is now more stable from release to release. (Problem noted by Tom Lane.) It is also a bit shorter. - tzdata.zi's version comment now contains information about which - data format was selected, which input files were used, and how - leap seconds are treated. (Problems noted by Lester Caine and - Brian Inglis.) If the Makefile defaults are used, no text is - appended to the version comment, for backward compatibility. - A redistributor intending to alter its copy of the files should - also append "-SOMETHING" to the 'version' file's first line, where - "SOMETHING" identifies what was changed. + tzdata.zi now can contain comment lines documenting configuration + information, such as which data format was selected, which input + files were used, and how leap seconds are treated. (Problems + noted by Lester Caine and Brian Inglis.) If the Makefile defaults + are used these comment lines are absent, for backward + compatibility. A redistributor intending to alter its copy of the + files should also append "-LABEL" to the 'version' file's first + line, where "LABEL" identifies the redistributor's change. Release 2018e - 2018-05-01 23:42:51 -0700 diff --git a/zishrink.awk b/zishrink.awk index 162e515..74e0de9 100644 --- a/zishrink.awk +++ b/zishrink.awk @@ -287,30 +287,30 @@ BEGIN { # that affect the output of this script, you should append '-SOMETHING' # to the contents of 'version', where SOMETHING identifies what was changed. - if (dataform != "main") { - version = version ",dataform=" dataform - } - if (redo != "posix_right") { - version = version ",redo=" redo - } ndeps = split(deps, dep) ddeps = "" for (i = 1; i <= ndeps; i++) { if (default_dep[dep[i]]) { default_dep[dep[i]]++ } else { - ddeps = ddeps "," dep[i] + ddeps = ddeps " " dep[i] } } for (d in default_dep) { if (default_dep[d] == 1) { - ddeps = ddeps ",!" d + ddeps = ddeps " !" d } } + print "# version", version + if (dataform != "main") { + print "# dataform", dataform + } + if (redo != "posix_right") { + print "# redo " redo + } if (ddeps) { - version = version ",ddeps=(" substr(ddeps, 2) ")" + print "# ddeps" ddeps } - print "# version", version print "# This zic input file is in the public domain." prehash_rule_names() -- 2.7.4

1 0

Getting current tzdb version in use
by Aldrin Martoq Ahumada July 26, 2018

July 26, 2018

Hi, I was looking for a reliable way to get the current tzdb version (something like 2018e), but it seems it doesn’t exists yet. A couple of examples: - In Mac OS 10.13.6, there is a /usr/share/zoneinfo/+VERSION that says 2018c. - In one of my updated Ubuntu 16.04 servers, the only reliable way is to do a dpkg -s tzdata | grep ^Version, and guess the real version from the string “Version: 2017c-0ubuntu0.16.04" - The “tzinfo” ruby library can get the version only if it uses its own version of tzdata, if it uses the OS files, there is no string version. Knowing the current tzdb version is essential for automating timezone updates. I think an appropriate place to put that string is in the binary TZif file itself, so tools like tzinfo can get the current version *of the current timezone in use*, instead of looking some random file like +VERSION in a random directory/folder. Is there any chances for this to happen? Or any other suggestion? Aldrin.

18 51

Re: [tz] Celinograd (Astana)
by Paul Eggert July 20, 2018

July 20, 2018

Marat Nigametzianov wrote: > https://ru.m.wikipedia.org/wiki/Время_в_Казахстане Generally we prefer primary sources, as Wikipedia is less reliable (anybody can edit it). > And this is link to order from 1956 about timezone in USSR > http://astro.uni-altai.ru/~orion/blog/2011/11/novyie-granitsyi-chasovyih-po… Thanks, that source should be quite helpful. Proposed patch attached. This is to commentary only. > Where is a two part of kazahstan and celinograd (astana) is in eastern part > of it, so it always have to be +6 Currently Astana is covered by Asia/Almaty, which already says that the region was at UT +06 from 1930-06-21 until 1981-04-01. So I'm afraid that I don't see why a change to tzdata is needed (other than to commentary).

2 2

Getting current tzdb version in use
by Paul Eggert July 20, 2018

July 20, 2018

On 07/19/2018 08:50 AM, lester(a)lsces.co.uk wrote: > The bottom line is that currently we have no way of knowing just what data is > being supplied. Even if the data matches the raw tz version, it may or may not > include the pre-1970 <tel:1970> data archived to backzone. Yes, and this is partly why I have resisted putting version information into the installed files. Version info is typically not available unless you've merely cloned the development Git repository and have made no change to the data or to the 'make' parameters that select or alter the data, a situation that is reasonably rare in practice. It would take quite a bit of effort to get reliable version information in real installations, and nobody knows exactly what would be entailed in that effort. Since many people have requested version info I had compromised by putting a version string into tzdata.zi as a sort of experiment. The experiment has clearly failed so far. That being said, we can improve things a bit by putting into tzdata.zi information about whether the file 'backward' was used, as well as whether the (dicey) file 'backzone' and the (obsolete) file 'pacificnew' were used. We can also record whether the rearguard (or vanguard) data format was selected. Proposed patch attached. Harold, if you're changing your C++ library to look for "unknown", this patch might append some stuff to that "unknown" string.

2 2

rearguard
by Lord Buddha July 18, 2018

July 18, 2018

This would be so much easier (for me;) ) if all data forms were published by IANA. $ awk -v DATAFORM=vanguard -f ziguard.awk africa antarctica asia australasia europe northamerica southamerica etcetera systemv factory backward *malloc(): memory corruptionAborted (core dumped)* On Ubuntu 18.04 trying to get files in rearguard format so I can patch Java & JodaTime.... Need to patch as we need the Fiji change now.

3 4

[PATCH] Give title lines to many files lacking them
by Paul Eggert July 16, 2018

July 16, 2018

--- Makefile | 2 ++ africa | 2 ++ antarctica | 2 ++ asia | 2 ++ australasia | 2 ++ backward | 2 ++ difftime.c | 2 ++ etcetera | 2 ++ europe | 2 ++ factory | 2 ++ localtime.c | 2 ++ newstrftime.3 | 2 ++ northamerica | 2 ++ pacificnew | 2 ++ private.h | 2 ++ southamerica | 2 ++ systemv | 2 ++ tzfile.h | 2 ++ tzselect.ksh | 5 ++--- workman.sh | 1 + yearistype.sh | 1 + zdump.c | 2 ++ zic.c | 2 ++ zoneinfo2tdf.pl | 1 + 24 files changed, 45 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 9e3b8f9..d01bb9a 100644 --- a/Makefile +++ b/Makefile @@ -1,3 +1,5 @@ +# Make and install tzdb code and data. + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/africa b/africa index eb7f8ae..131330e 100644 --- a/africa +++ b/africa @@ -1,3 +1,5 @@ +# tzdb data for Africa and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/antarctica b/antarctica index 866cf4f..1dd9b00 100644 --- a/antarctica +++ b/antarctica @@ -1,3 +1,5 @@ +# tzdb data for Antarctica and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/asia b/asia index 810ef47..7166380 100644 --- a/asia +++ b/asia @@ -1,3 +1,5 @@ +# tzdb data for Asia and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/australasia b/australasia index 938c591..87ba620 100644 --- a/australasia +++ b/australasia @@ -1,3 +1,5 @@ +# tzdb data for Australasia and environs, and for much of the Pacific + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/backward b/backward index a455044..51e10f4 100644 --- a/backward +++ b/backward @@ -1,3 +1,5 @@ +# tzdb links for backward compatibility + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/difftime.c b/difftime.c index 856234a..7b96927 100644 --- a/difftime.c +++ b/difftime.c @@ -1,3 +1,5 @@ +/* Return the difference between two timestamps. */ + /* ** This file is in the public domain, so clarified as of ** 1996-06-05 by Arthur David Olson. diff --git a/etcetera b/etcetera index 1a59630..91ded93 100644 --- a/etcetera +++ b/etcetera @@ -1,3 +1,5 @@ +# tzdb data for ships at sea and other miscellany + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/europe b/europe index 8a8f8f9..a5feb59 100644 --- a/europe +++ b/europe @@ -1,3 +1,5 @@ +# tzdb data for Europe and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/factory b/factory index 5f0573d..d4e7659 100644 --- a/factory +++ b/factory @@ -1,3 +1,5 @@ +# tzdb data for noncommittal factory settings + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/localtime.c b/localtime.c index b217865..6b45254 100644 --- a/localtime.c +++ b/localtime.c @@ -1,3 +1,5 @@ +/* Convert timestamp from time_t to struct tm. */ + /* ** This file is in the public domain, so clarified as of ** 1996-06-05 by Arthur David Olson. diff --git a/newstrftime.3 b/newstrftime.3 index 1fd80df..eee503e 100644 --- a/newstrftime.3 +++ b/newstrftime.3 @@ -1,3 +1,5 @@ +.\" strftime man page +.\" .\" Based on the UCB file whose corrected copyright information appears below. .\" Copyright 1989, 1991 The Regents of the University of California. .\" All rights reserved. diff --git a/northamerica b/northamerica index 06db1a8..ffbda74 100644 --- a/northamerica +++ b/northamerica @@ -1,3 +1,5 @@ +# tzdb data for North and Central America and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/pacificnew b/pacificnew index 7349434..0e6cf07 100644 --- a/pacificnew +++ b/pacificnew @@ -1,3 +1,5 @@ +# tzdb data for proposed US election time (this file is obsolete) + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/private.h b/private.h index 641f905..1ead147 100644 --- a/private.h +++ b/private.h @@ -1,3 +1,5 @@ +/* Private header for tzdb code. */ + #ifndef PRIVATE_H #define PRIVATE_H diff --git a/southamerica b/southamerica index aab355c..67562f2 100644 --- a/southamerica +++ b/southamerica @@ -1,3 +1,5 @@ +# tzdb data for South America and environs + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/systemv b/systemv index d9e2995..24c8f64 100644 --- a/systemv +++ b/systemv @@ -1,3 +1,5 @@ +# tzdb data for System V rules (this file is obsolete) + # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/tzfile.h b/tzfile.h index f7f5caf..27a38cc 100644 --- a/tzfile.h +++ b/tzfile.h @@ -1,3 +1,5 @@ +/* Layout and location of TZif files. */ + #ifndef TZFILE_H #define TZFILE_H diff --git a/tzselect.ksh b/tzselect.ksh index f7d8154..18fce27 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -1,12 +1,11 @@ #!/bin/bash +# Ask the user about the time zone, and output the resulting TZ value to stdout. +# Interact with the user via stderr and stdin. PKGVERSION='(tzcode) ' TZVERSION=see_Makefile REPORT_BUGS_TO=tz(a)iana.org -# Ask the user about the time zone, and output the resulting TZ value to stdout. -# Interact with the user via stderr and stdin. - # Contributed by Paul Eggert. This file is in the public domain. # Porting notes: diff --git a/workman.sh b/workman.sh index 4b3b64a..8fb18a4 100644 --- a/workman.sh +++ b/workman.sh @@ -1,4 +1,5 @@ #! /bin/sh +# Convert manual page troff stdin to formatted .txt stdout. # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. diff --git a/yearistype.sh b/yearistype.sh index dfdcdf0..d674175 100644 --- a/yearistype.sh +++ b/yearistype.sh @@ -1,4 +1,5 @@ #! /bin/sh +: 'Determine whether year is of appropriate type (this file is obsolete).' : 'This file is in the public domain, so clarified as of' : '2006-07-17 by Arthur David Olson.' diff --git a/zdump.c b/zdump.c index 4c61f58..608f288 100644 --- a/zdump.c +++ b/zdump.c @@ -1,3 +1,5 @@ +/* Dump time zone data in a textual format. */ + /* ** This file is in the public domain, so clarified as of ** 2009-05-17 by Arthur David Olson. diff --git a/zic.c b/zic.c index 88153db..9d455b5 100644 --- a/zic.c +++ b/zic.c @@ -1,3 +1,5 @@ +/* Compile .zi time zone data into TZif binary files. */ + /* ** This file is in the public domain, so clarified as of ** 2006-07-17 by Arthur David Olson. diff --git a/zoneinfo2tdf.pl b/zoneinfo2tdf.pl index e05ec01..c8c5591 100755 --- a/zoneinfo2tdf.pl +++ b/zoneinfo2tdf.pl @@ -1,4 +1,5 @@ #! /usr/bin/perl -w +# Summarize .zi input in a .zi-like format. # Courtesy Ken Pizzini. -- 2.7.4

1 0

Celinograd (Astana)
by Marat Nigametzianov July 16, 2018

July 16, 2018

Celinograd (Astana) in 1969 must be +6 UTC not +5 https://www.worldtimezone.com/dst_news/dst_news_ussr-map-1970.html -- Nigametzianov Marat ____________________________________________________________________________ 8 926 568-93-08, ppmarat(a)gmail.com

2 1

Fiji DST 2018/19
by Raymond Kumar July 15, 2018

July 15, 2018

Hi Paul, There is a DST time change in Fiji island from November 4th. http://www.fijitimes.com/government-approves-2018-daylight-saving/ The attached order states: Members of the public are advised to move their clocks one hour ahead at 2am on Sunday November 4. The daylight saving period will end at 3am on Sunday January 13, 2019. Fiji rules in tzdata2018e.tar.gz: There is a need to change the NON DST time from 14th Jan to 13th Jan. Can a new tzdata be generated for Fiji Islands. Rule Fiji 2014 max - Nov Sun>=1 2:00 1:00 - Rule Fiji 2015 max - Jan Sun>=14 3:00 0 - 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.

4 9

Re: [tz] EU Public Consultation on summertime arrangements
by Pierpaolo Bernardi July 11, 2018

July 11, 2018

Not time related. Only for pedantry sake: at the border between San Marino and Italy there *are* controls, by the Italian police. This is due to different tax laws in the two countries, which would make shopping in San Marino very convenient for Italy residents, if they weren't controlled when exiting from RSM for any good bought in RSM, and forced to pay due taxes. FWIW Il giorno 11 luglio 2018, alle ore 09:08, John Wilcock <john(a)tradoc.fr> ha scritto: Le 11/07/2018 à 00:05, Brian Inglis a écrit : > Most people are probably not that aware of European geography [...] Taking the world as a whole, you are no doubt correct, but most of the people at the EU who will be reading Paul's submission will be perfectly aware of European geography! >> I don't see the relevance of "Schengen area" - all current and potential >> Schengen area countries are either EU or EEA/EFTA members. > The Schengen Area also includes non-EU/EEA/EFTA countries Monaco, San Marino, > and the Vatican, which have not signed the Schengen agreement, but have no > borders, so are de facto included. While these three countries are indeed de facto within the Schengen area due to the lack of border *controls* — they do still have borders ;-) — it still seems (at least to me as a European) very odd to mention Schengen purely in order to include its *non*-signatories, especially as the next item in the list is in any case the all-inclusive "other countries not in the EU". -- John

1 0

(no subject)
by Ashish Ahmed July 10, 2018

July 10, 2018

Confirm

1 0

tz-art suggestion
by Steve Jones July 6, 2018

July 6, 2018

Not sure how this was missed, having passed its third birthday, but probably deserves a mention in tz-art: "Daylight Saving Time: How is this still a thing?" https://www.youtube.com/watch?v=br0NW9ufUUw Regards, Steve Jones [image: Emacs!]

3 2

strftime and nonnormalized dates/times
by scs＠eskimo.com July 5, 2018

July 5, 2018

I have a question about the strftime function. This is not related to time zones per se, but there are a lot of date/time programming experts here, and of course there's a reference implementation of strftime in tzcode. [Full disclosure: I am posting the same question to StackOverflow: https://stackoverflow.com/questions/51145727/ .] Most definitions of the %H, %M, and %S specifiers (including those in the ANSI/ISO C Standards) contain language like %H is replaced by the hour (24-hour clock) as a decimal number (00-23). Now, that little notation "(00-23)" at the end tells you the range of numbers you're going to see *if the struct tm you're printing was just created by localtime or gmtime*. My question concerns the presence or absence of a requirement that the struct tm being referenced by strftime *must* have been one just generated by localtime or gmtime. I don't think there's such a requirement, but if there isn't, those notations "(00-23)" and "(00-59)" don't really have any normative implications for strftime -- they're more of a misplaced requirement on the values generated by localtime and gmtime. But if strftime doesn't restrict the ranges of the various struct tm fields to their "normal" values, it makes me wonder how much latitude a push-the-boundaries programmer actually has when calling strftime. Are the values as unlimited as they are when calling, say, mktime? To make the question more concrete, it came to me when I found myself writing this code: time_t dt = t2 - t1; struct tm *tmp = gmtime(&dt); if(dt > 86400) tmp->tm_hour += dt / 86400 * 24; strftime(etbuf, sizeof(etbuf), "elapsed: %H:%M:%S", tmp); That is, I'm subtracting two times, and letting gmtime and strftime convert the difference to HH:MM:SS format for me. But if the time delta was more than a day, I'm not printing it as days; I'm just lumping it in with the hours (which, it's true, might end up being a very large number if there were months or years between t1 and t2). So, language lawyer question: Is this legal and portable? When calling strftime, are tm_hour, tm_min, and the rest limited to their normal ranges, or not? (Yes, I've tried it, and nonnormalized values work -- not at all surprisingly -- as expected under the popular implementations, but that's not the question.)

4 6

African Timezones
by Robin Roos July 4, 2018

July 4, 2018

Hi Folks, I am using a Java platform (hosted on Linux and on Windows) in which I find some expected timezones to be missing. I write to enquire whether they are defined at IANA and, if not, whether they can be added. The timezones in question are as follows: Africa/Praia (capital city of Cabo Verde, also known also as Cape Verde) = UTC-1 CVT (Cabo Verde Time) = UTC-1 (one hour West of Greenwich) WAT (West Africa Time) = UTC+1 (one hour East of Greenwich) CAT (Central Africa Time) = UTC+2 (two hours East of Greenwich) EAT (East Africa Time) = UTC+3 (three hours East of Greenwich) My source for this information is: https://www.worldtimezone.com/time-africa24.php Many thanks, Robin.

2 2

"time zone" vs "timezone" in documentation
by Paul Eggert July 4, 2018

July 4, 2018

[I am cc'ing this to the tz mailing list (and changing the subject line) to give tz readers a heads-up about the terminology issue. The question here is: should tzdb man pages say "time zone" or "timezone"? For context please see Michael Kerrisk's email <https://marc.info/?m=152964652828320>, which says: > When I inherited the project, the pages used a mixture of "time zone" > and "timezone", with the former predominant. I nevertheless > standardized on the latter, and although I don't recall for sure, I > suspect it was because that is the spelling used in POSIX. (As an > aside, there's an argument that--because POSIX--tzdb might want to > consider switching spellings.) I'm not religious about the particular > choice (although I have naturally now got used to the particular > choice I made some years ago), but I did make that choice because I > want consistency within the project, and I'm reluctant to introduce > inconsistency. and my response <https://marc.info/?m=152964676331902>, which says: > I deferred to POSIX for "timestamp" versus "time stamp", but > "timezone" is a bridge too far for me. ] On second thought, perhaps I was too hasty. We could distinguish "time zone" in the usual English-language sense (a set of geographic locations that currently share the same standard time offset from UTC) from "timezone" in the POSIX sense (a history and predicted future of UTC offsets, abbreviations and isdst flags). If so, the tzdb documentation could be more careful about using "time zone" for the former and "timezone" for the latter, and this would make for fewer changes to the GNU/Linux man-pages for tzdb. I can look into this and propose an updated set of tzdb-related patches accordingly. If I were designing the terminology from scratch, I wouldn't specify two nearly-identical phrases "time zone" and "timezone" to mean such different things. However, the phrases do have the advantage of existing practice (common English usage and POSIX, respectively).

9 11

[PROPOSED] * tz-link.html (Precision timekeeping): Mention Huygens.
by Paul Eggert June 29, 2018

June 29, 2018

--- tz-link.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tz-link.html b/tz-link.html index 548fbba..7ed1efd 100644 --- a/tz-link.html +++ b/tz-link.html @@ -813,11 +813,15 @@ title="Network Time Protocol">NTP</abbr>: The Network Time Protocol</a> (Internet <abbr>RFC</abbr> 5905) discusses how to synchronize clocks of Internet hosts.</li> +<li>The <a href="https://www.usenix.org/system/files/conference/nsdi18/nsdi18-geng.pdf"><font style="font-variant: small-caps">Huygens</font></a> +family of software algorithms can achieve accuracy to a few tens of +nanoseconds in scalable server farms without special hardware.</li> <li>The <a href="https://www.nist.gov/intelligent-systems-division/ieee-1588">Precision Time Protocol</a> (<abbr title="Institute of Electrical and Electronics Engineers">IEEE</abbr> 1588) -can achieve submicrosecond clock accuracy on a local area network.</li> +can achieve submicrosecond clock accuracy on a local area network +with special-purpose hardware.</li> <li><a href="https://tools.ietf.org/html/rfc4833">Timezone Options for <abbr title="Dynamic Host Configuration Protocol">DHCP</abbr></a> -- 2.17.1

1 0

California will vote on permanent daylight
by Steve Allen June 29, 2018

June 29, 2018

The governor approved AB 807 https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720… Daylight time in California was established by the voters, and must be repealed by the voters, so nothing happens until after an election decides whether to ask the state legislature to consider how permanent daylight time could be achieved. -- 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

1 0

[PROPOSED] Make Makefile safer for parallelism
by Paul Eggert June 27, 2018

June 27, 2018

Although this still does not fully work with GNU Make, it’s better than what we had. * Makefile (TIME_T_ALTERNATIVES_HEAD) (TIME_T_ALTERNATIVES_TAIL): New macros. (TIME_T_ALTERNATIVES): Use them. (TZS_CUTOFF_FLAG): New macro. ($(ZDS)): Use it, so that submakes can use -t instead of -c cutoffs. (EIGHT_YARDS): New macro. (ENCHILADA): Use it. (INSTALL_DATA_DEPS, TZS_NEW_DEPS): New macros. (install_data, posix_only, right_only, posix_packrat, $(TZS_NEW)): Use them to avoid duplicate work with GNU make -j. ($(TZS_NEW), check_zishrink_posix, check_zishrink_right, check_public) (check_time_t_alternatives): Use rule-specific temporary directories so that other rules can run in parallel. ($(TZS_NEW)): Check for sort failure. ($(TZS)): Simply touch it if it doesn’t exist, so that it’s empty. (check_tzs): Treat empty $(TZS) as nonexistent. (check_character_set, check_white_space, check_name_lengths) (check_sorted, check_links, check_tables, check_tzs, check_web) (check_zishrink, check_public): No longer phony. (check_zishrink_posix, check_zishrink_right) (typecheck_long_long, typecheck_unsigned): New rules, so that they can be done in parallel. (clean_misc): Clean the timestamp files that are now made due to rules no longer being phony. (set-timestamps.out): Do not set timestamp of $(TZS). (set-tzs-timestamp.out): New rule. (check_time_t_alternatives): Break into subrules, one for each alternative, so that they can be done in parallel. (tarballs, rearguard_tarballs, traditional_tarballs) (signatures, rearguard_signatures, traditional_signatures): Depend on set-timestamps.out and rearguard.zi. (tzdb-$(VERSION).tar.lz): Depend on set-tzs-timestamp.out. (TYPECHECK_CFLAGS): New macro. --- Makefile | 240 +++++++++++++++++++++++++++++++++++++-------------------------- 1 file changed, 142 insertions(+), 98 deletions(-) diff --git a/Makefile b/Makefile index 2289dff..29058e5 100644 --- a/Makefile +++ b/Makefile @@ -106,8 +106,10 @@ MANDIR = $(TOPDIR)/$(USRSHAREDIR)/man 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 +# Types to try, as an alternative to time_t. +TIME_T_ALTERNATIVES = $(TIME_T_ALTERNATIVES_HEAD) $(TIME_T_ALTERNATIVES_TAIL) +TIME_T_ALTERNATIVES_HEAD = int64_t +TIME_T_ALTERNATIVES_TAIL = 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.) @@ -493,11 +495,14 @@ AWK_SCRIPTS= checklinks.awk checktab.awk leapseconds.awk \ ziguard.awk zishrink.awk MISC= $(AWK_SCRIPTS) zoneinfo2tdf.pl TZS_YEAR= 2050 +TZS_CUTOFF_FLAG= -c $(TZS_YEAR) TZS= to$(TZS_YEAR).tzs TZS_NEW= to$(TZS_YEAR)new.tzs TZS_DEPS= $(PRIMARY_YDATA) asctime.c localtime.c \ private.h tzfile.h zdump.c zic.c -ENCHILADA= $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) $(TZS) tzdata.zi +# EIGHT_YARDS is just a yard short of the whole ENCHILADA. +EIGHT_YARDS = $(COMMON) $(DOCS) $(SOURCES) $(DATA) $(MISC) tzdata.zi +ENCHILADA = $(EIGHT_YARDS) $(TZS) # Consult these files when deciding whether to rebuild the 'version' file. # This list is not the same as the output of 'git ls-files', since @@ -606,14 +611,16 @@ INSTALLARGS = \ YEARISTYPE='$(YEARISTYPE)' \ ZIC='$(ZIC)' +INSTALL_DATA_DEPS = zic leapseconds yearistype tzdata.zi + # 'make install_data' installs one set of TZif files. -install_data: zic leapseconds yearistype tzdata.zi +install_data: $(INSTALL_DATA_DEPS) $(ZIC_INSTALL) tzdata.zi -posix_only: +posix_only: $(INSTALL_DATA_DEPS) $(MAKE) $(INSTALLARGS) LEAPSECONDS= install_data -right_only: +right_only: $(INSTALL_DATA_DEPS) $(MAKE) $(INSTALLARGS) LEAPSECONDS='-L leapseconds' \ install_data @@ -640,7 +647,7 @@ posix_right: posix_only # This obsolescent rule is present for backwards compatibility with # tz releases 2014g through 2015g. It should go away eventually. -posix_packrat: +posix_packrat: $(INSTALL_DATA_DEPS) $(MAKE) $(INSTALLARGS) PACKRATDATA=backzone posix_only zones: $(REDO) @@ -651,29 +658,33 @@ 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 - rm -fr tzs.dir - mkdir tzs.dir - $(zic) -d tzs.dir tzdata.zi + ./zdump -i $(TZS_CUTOFF_FLAG) '$(wd)/'$$(expr $@ : '$.*$.zd') \ + >$@ + +TZS_NEW_DEPS = tzdata.zi zdump zic +$(TZS_NEW): $(TZS_NEW_DEPS) + rm -fr tzs$(TZS_YEAR).dir + mkdir tzs$(TZS_YEAR).dir + $(zic) -d tzs$(TZS_YEAR).dir tzdata.zi $(AWK) '/^L/{print "Link\t" $$2 "\t" $$3}' \ tzdata.zi | LC_ALL=C sort >$@.out wd=`pwd` && \ - set x `$(AWK) '/^Z/{print "tzs.dir/" $$2 ".zd"}' tzdata.zi \ + x=`$(AWK) '/^Z/{print "tzs$(TZS_YEAR).dir/" $$2 ".zd"}' \ + tzdata.zi \ | LC_ALL=C sort -t . -k 2,2` && \ + set x $$x && \ shift && \ ZDS=$$* && \ - $(MAKE) wd="$$wd" TZS_YEAR=$(TZS_YEAR) ZDS="$$ZDS" $$ZDS && \ - sed 's,^TZ=".*tzs\.dir/,TZ=",' $$ZDS >>$@.out - rm -fr tzs.dir + $(MAKE) wd="$$wd" TZS_CUTOFF_FLAG="$(TZS_CUTOFF_FLAG)" \ + ZDS="$$ZDS" $$ZDS && \ + sed 's,^TZ=".*\.dir/,TZ=",' $$ZDS >>$@.out + rm -fr tzs$(TZS_YEAR).dir mv $@.out $@ -# If $(TZS) does not already exist (e.g., old-format tarballs), create it. -# If it exists but 'make check_tzs' fails, a maintainer should inspect the +# If $(TZS) exists but 'make check_tzs' fails, a maintainer should inspect the # failed output and fix the inconsistency, perhaps by running 'make force_tzs'. $(TZS): - $(MAKE) force_tzs + touch $@ force_tzs: $(TZS_NEW) cp $(TZS_NEW) $(TZS) @@ -718,12 +729,14 @@ check_character_set: $(ENCHILADA) leapseconds yearistype.sh zone.tab && \ ! grep -Env $(OK_LINE) $(ENCHILADA); \ } + touch $@ check_white_space: $(ENCHILADA) patfmt=' \t|[\f\r\v]' && pat=`printf "$$patfmt\\n"` && \ ! grep -En "$$pat" $(ENCHILADA) ! grep -n '[[:space:]]$$' \ $$(ls $(ENCHILADA) | grep -Fvx leap-seconds.list) + touch $@ PRECEDES_FILE_NAME = ^(Zone|Link[[:space:]]+[^[:space:]]+)[[:space:]]+ FILE_NAME_COMPONENT_TOO_LONG = \ @@ -732,6 +745,7 @@ FILE_NAME_COMPONENT_TOO_LONG = \ check_name_lengths: $(TDATA_TO_CHECK) backzone ! grep -En '$(FILE_NAME_COMPONENT_TOO_LONG)' \ $(TDATA_TO_CHECK) backzone + touch $@ CHECK_CC_LIST = { n = split($$1,a,/,/); for (i=2; i<=n; i++) print a[1], a[i]; } @@ -744,52 +758,61 @@ check_sorted: backward backzone iso3166.tab zone.tab zone1970.tab LC_ALL=C sort -c $(AWK) '/^[^#]/ $(CHECK_CC_LIST)' zone1970.tab | \ LC_ALL=C sort -cu + touch $@ check_links: checklinks.awk $(TDATA_TO_CHECK) tzdata.zi $(AWK) -f checklinks.awk $(TDATA_TO_CHECK) $(AWK) -f checklinks.awk tzdata.zi + touch $@ check_tables: checktab.awk $(PRIMARY_YDATA) $(ZONETABLES) for tab in $(ZONETABLES); do \ $(AWK) -f checktab.awk -v zone_table=$$tab $(PRIMARY_YDATA) \ || exit; \ done + touch $@ check_tzs: $(TZS) $(TZS_NEW) - diff -u $(TZS) $(TZS_NEW) + if test -s $(TZS); then \ + diff -u $(TZS) $(TZS_NEW); \ + else \ + cp $(TZS_NEW) $(TZS); \ + fi + touch $@ # 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 + touch $@ # Check that zishrink.awk does not alter the data, and that ziguard.awk # preserves main-format data. -check_zishrink: zic leapseconds $(PACKRATDATA) $(TDATA) \ - $(DATAFORM).zi tzdata.zi - for type in posix right; do \ - 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 $(DATAFORM).zi && \ +check_zishrink: check_zishrink_posix check_zishrink_right +check_zishrink_posix check_zishrink_right: \ + zic leapseconds $(PACKRATDATA) $(TDATA) $(DATAFORM).zi tzdata.zi + rm -fr $@.dir $(a)-t.dir $(a)-shrunk.dir + mkdir $@.dir $(a)-t.dir $(a)-shrunk.dir + case $@ in \ + *_right) leap='-L leapseconds';; \ + *) leap=;; \ + esac && \ + $(ZIC) $$leap -d $@.dir $(DATAFORM).zi && \ + $(ZIC) $$leap -d $(a)-shrunk.dir tzdata.zi && \ case $(DATAFORM) in \ main) \ - $(ZIC) $$leap -d time_t.dir/$$type-t $(TDATA) && \ + $(ZIC) $$leap -d $(a)-t.dir $(TDATA) && \ $(AWK) '/^Rule/' $(TDATA) | \ - $(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; \ - done - rm -fr time_t.dir + $(ZIC) $$leap -d $(a)-t.dir - $(PACKRATDATA) && \ + diff -r $@.dir $(a)-t.dir;; \ + esac + diff -r $@.dir $(a)-shrunk.dir + rm -fr $@.dir $(a)-t.dir $(a)-shrunk.dir + touch $@ clean_misc: - rm -f core *.o *.out \ + rm -f *.o *.out $(TIME_T_ALTERNATIVES) \ + check_* core typecheck_* \ date tzselect version.h zdump zic yearistype libtz.a clean: clean_misc rm -fr *.dir *.zi tzdb-*/ $(TZS_NEW) @@ -826,10 +849,10 @@ $(MANTXTS): workman.sh # If git or GNU 'touch' is absent, don't bother to sync with git timestamps. # Also, set the timestamp of each prebuilt file like 'leapseconds' # to be the maximum of the files it depends on. -set-timestamps.out: $(ENCHILADA) +set-timestamps.out: $(EIGHT_YARDS) rm -f $@ if (type git) >/dev/null 2>&1 && \ - files=`git ls-files $(ENCHILADA)` && \ + files=`git ls-files $(EIGHT_YARDS)` && \ touch -md @1 test.out; then \ rm -f test.out && \ for file in $$files; do \ @@ -847,62 +870,74 @@ set-timestamps.out: $(ENCHILADA) exit; \ done touch -cmr `ls -t $(TZDATA_ZI_DEPS) | sed 1q` tzdata.zi - touch -cmr `ls -t $(TZS_DEPS) | sed 1q` $(TZS) touch -cmr `ls -t $(VERSION_DEPS) | sed 1q` version touch $@ +set-tzs-timestamp.out: $(TZS) + touch -cmr `ls -t $(TZS_DEPS) | sed 1q` $(TZS) + touch $@ # The zics below ensure that each data file can stand on its own. # We also do an all-files run to catch links to links. -check_public: - $(MAKE) maintainer-clean - $(MAKE) CFLAGS='$(GCC_DEBUG_FLAGS)' ALL - mkdir -p public.dir - for i in $(TDATA_TO_CHECK) tzdata.zi; do \ - $(zic) -v -d public.dir $$i 2>&1 || exit; \ +check_public: $(VERSION_DEPS) + rm -fr public.dir + mkdir public.dir + ln $(VERSION_DEPS) public.dir + cd public.dir && $(MAKE) CFLAGS='$(GCC_DEBUG_FLAGS)' ALL + for i in $(TDATA_TO_CHECK) public.dir/tzdata.zi; do \ + public.dir/zic -v -d public.dir/zoneinfo $$i 2>&1 || exit; \ done - $(zic) -v -d public.dir $(TDATA_TO_CHECK) + public.dir/zic -v -d public.dir/zoneinfo-all $(TDATA_TO_CHECK) rm -fr public.dir + touch $@ # Check that the code works under various alternative # implementations of time_t. -check_time_t_alternatives: - if diff -q Makefile Makefile 2>/dev/null; then \ - quiet_option='-q'; \ - else \ - quiet_option=''; \ - fi && \ +check_time_t_alternatives: $(TIME_T_ALTERNATIVES) +$(TIME_T_ALTERNATIVES_TAIL): $(TIME_T_ALTERNATIVES_HEAD) +$(TIME_T_ALTERNATIVES): $(VERSION_DEPS) + rm -fr $@.dir + mkdir $@.dir + ln $(VERSION_DEPS) $@.dir + case $@ in \ + int32_t) range=-2147483648,2147483648;; \ + u*) range=0,4294967296;; \ + *) range=-4294967296,4294967296;; \ + esac && \ wd=`pwd` && \ zones=`$(AWK) '/^[^#]/ { print $$3 }' <zone1970.tab` && \ - for type in $(TIME_T_ALTERNATIVES); do \ - mkdir -p time_t.dir/$$type && \ - $(MAKE) clean_misc && \ - $(MAKE) TOPDIR="$$wd/time_t.dir/$$type" \ - CFLAGS='$(CFLAGS) -Dtime_tz='"'$$type'" \ + if test $@ = $(TIME_T_ALTERNATIVES_HEAD); then \ + range_target=; \ + else \ + range_target=to$$range.tzs; \ + fi && \ + (cd $@.dir && \ + $(MAKE) TOPDIR="$$wd/$@.dir" \ + CFLAGS='$(CFLAGS) -Dtime_tz='"'$@'" \ REDO='$(REDO)' \ - install && \ - diff $$quiet_option -r \ - time_t.dir/int64_t/etc \ - time_t.dir/$$type/etc && \ - diff $$quiet_option -r \ - time_t.dir/int64_t/usr/share \ - time_t.dir/$$type/usr/share && \ - case $$type in \ - int32_t) range=-2147483648,2147483647;; \ - uint32_t) range=0,4294967296;; \ - int64_t) continue;; \ - *u*) range=0,10000000000;; \ - *) range=-10000000000,10000000000;; \ - esac && \ - echo checking $$type zones ... && \ - time_t.dir/int64_t/usr/bin/zdump -V -t $$range $$zones \ - >time_t.dir/int64_t.out && \ - time_t.dir/$$type/usr/bin/zdump -V -t $$range $$zones \ - >time_t.dir/$$type.out && \ - diff -u time_t.dir/int64_t.out time_t.dir/$$type.out \ - || exit; \ - done - rm -fr time_t.dir + D=$$wd/$@.dir \ + TZS_YEAR="$$range" TZS_CUTOFF_FLAG="-t $$range" \ + install $$range_target) && \ + test $@ = $(TIME_T_ALTERNATIVES_HEAD) || { \ + (cd $(TIME_T_ALTERNATIVES_HEAD).dir && \ + $(MAKE) TOPDIR="$$wd/$@.dir" \ + TZS_YEAR="$$range" TZS_CUTOFF_FLAG="-t $$range" \ + D=$$wd/$@.dir \ + to$$range.tzs) && \ + diff -u $(TIME_T_ALTERNATIVES_HEAD).dir/to$$range.tzs \ + $@.dir/to$$range.tzs && \ + if diff -q Makefile Makefile 2>/dev/null; then \ + quiet_option='-q'; \ + else \ + quiet_option=''; \ + fi && \ + diff $$quiet_option -r $(TIME_T_ALTERNATIVES_HEAD).dir/etc \ + $@.dir/etc && \ + diff $$quiet_option -r \ + $(TIME_T_ALTERNATIVES_HEAD).dir/usr/share \ + $@.dir/usr/share; \ + } + touch $@ TRADITIONAL_ASC = \ tzcode$(VERSION).tar.gz.asc \ @@ -913,7 +948,8 @@ ALL_ASC = $(TRADITIONAL_ASC) $(REARGUARD_ASC) \ tzdb-$(VERSION).tar.lz.asc tarballs rearguard_tarballs traditional_tarballs \ -signatures rearguard_signatures traditional_signatures: version +signatures rearguard_signatures traditional_signatures: \ + version set-timestamps.out rearguard.zi VERSION=`cat version` && \ $(MAKE) VERSION="$$VERSION" $@_version @@ -963,7 +999,7 @@ tzdata$(VERSION)-rearguard.tar.gz: rearguard.zi set-timestamps.out gzip $(GZIPFLAGS)) >$@.out mv $@.out $@ -tzdb-$(VERSION).tar.lz: set-timestamps.out +tzdb-$(VERSION).tar.lz: set-timestamps.out set-tzs-timestamp.out rm -fr tzdb-$(VERSION) mkdir tzdb-$(VERSION) ln $(ENCHILADA) tzdb-$(VERSION) @@ -979,14 +1015,24 @@ tzdb-$(VERSION).tar.lz.asc: tzdb-$(VERSION).tar.lz $(ALL_ASC): gpg2 --armor --detach-sign $? -typecheck: - $(MAKE) clean - for i in "long long" unsigned; \ - do \ - $(MAKE) CFLAGS="-DTYPECHECK -D__time_t_defined -D_TIME_T \"-Dtime_t=$$i\"" ; \ - ./zdump -v Europe/Rome ; \ - $(MAKE) clean ; \ - done +TYPECHECK_CFLAGS = $(CFLAGS) -DTYPECHECK -D__time_t_defined -D_TIME_T +typecheck: typecheck_long_long typecheck_unsigned +typecheck_long_long typecheck_unsigned: $(VERSION_DEPS) + rm -fr $@.dir + mkdir $@.dir + ln $(VERSION_DEPS) $@.dir + cd $@.dir && \ + case $@ in \ + *_long_long) i="long long";; \ + *_unsigned ) i="unsigned" ;; \ + esac && \ + typecheck_cflags='' && \ + $(MAKE) \ + CFLAGS="$(TYPECHECK_CFLAGS) \"-Dtime_t=$$i\"" \ + TOPDIR="`pwd`" \ + install + $@.dir/zdump -i -c 1970,1971 Europe/Rome + touch $@ zonenames: tzdata.zi @$(AWK) '/^Z/ { print $$2 } /^L/ { print $$3 }' tzdata.zi @@ -1002,9 +1048,7 @@ zic.o: private.h tzfile.h version.h .KEEP_STATE: .PHONY: ALL INSTALL all -.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 check_time_t_alternatives .PHONY: check_zishrink .PHONY: clean clean_misc dummy.zd force_tzs .PHONY: install install_data maintainer-clean names -- 2.7.4

1 0

Europe/Zaporozhye
by Paul G June 26, 2018

June 26, 2018

Recently during a conversation about the tzdb and a colleague of mine mentioned that it seems to be a strange outlier that Europe/Zaporozhye has its own zone, since Zaporozh'ye is not a particularly large city (it's quite close to Donetsk, which he deemed more likely to be the major city in the area). I looked at the source code and saw that it mentions: # Zaporozh'ye and eastern Lugansk oblasts observed DST 1990/1991. (https://github.com/eggert/tz/blob/master/europe#L3850) He seemed to think that this was an absurd notion and that more or less any city in Ukraine would either follow Moscow time or Crimea time, but none of them would have yet a third history. It does seem a bit strange (though perfectly consistent with the weird nonsense everyone else gets up to) that only Zaporozh'ye and eastern Lugansk would follow a different time zone than their immediate neighbors - these are not even contiguous regions. In the timezone-boundary-builder project (https://github.com/evansiroky/timezone-boundary-builder) it seems that only Zaporozhia Oblast is included in the shapefile. We did a cursory search for references (including in the archives of this mailing list and the git history) in English and Russian and couldn't find any reference to Zaporozhia and Lugansk having a different time zone that wasn't derived from this project. So, questions about this: 1. Can anyone point to a reference to the fact that these regions used a different time zone than their neighbors? 2. If no reference is handy, does anyone know on what basis this zone was included in the database in the first place? 3. Is there any clarification as to the geographic extent of the zone? Does it cover Donetsk as well? What part of Lugansk counts as "eastern Lugansk"? Best, Paul

2 1

redundant Rule in proposal for Macao
by Michael H Deckers June 26, 2018

June 26, 2018

In Paul Eggert's proposal for Macao from 2018-05-10, we find +Rule Macau 1949 1951 - Apr Sat>=1 23:00s 1:00 D +Rule Macau 1951 only - Mar 31 23:00s 1:00 D with two successive switches to summer time at 1951-03-31 and 1951-04-07. The later switch has no effect, and can easily be omitted: +Rule Macau 1949 1950 - Apr Sat>=1 23:00s 1:00 D There are several similar cases in tzdb where the specification contains redundant data. For instance, Rule HK 1965 1976 - Apr Sun>=16 3:30 1:00 S Rule HK 1973 only - Dec 30 3:30 1:00 S with two successive switches to summer time at 1973-12-30 and 1974-04-21, the latter having no effect. In this case, removal of the redundancy would require an addtional Rule line, so concise notation could be construed as a reason for retaining the redundancy. Do we have a guideline for such cases? Michael Deckers.

2 1

Re: [tz] [PROPOSED] Use "PST/PDT" for Philippine time
by Paul Eggert June 25, 2018

June 25, 2018

Michael H Deckers wrote: > Fine if this were a generally applied guideline -- but it is not, > see eg America/Adak, Indonesia, and many others. When is this guideline > applied, and when not? The guideline is supposed to be applied reasonably consistently for clear-cut cases such as the Philippines. Alaska and Indonesia are more complicated, since they are not merely a question of what's the name of a time zone; they are also a question of time zone boundaries moving, and where it's not so clear what is being named. For example, a historian today would be unlikely to write "Sitka observed Alaska Standard Time in 1984" because in 1984 the Alaska time zone boundaries were quite different and Sitka was then in the geographically small part of Alaska that was in the same time zone as the Yukon. Unfortunately I don't see a good solution for these more-complicated cases, and am reluctant to change the data if it's likely this would introduce as much or more confusion than it would alleviate. > And all that does not justify the resurrection of an invented abbreviation. First, for the Phillippines it's no longer an abbreviation that exists only because we invented it. It's taken on a life of its own in reliable sources and in national law. And second, I doubt whether these sources got "PST" from tzdb, since tzdb has been using "PHST" for over two decades and used "PST" only briefly before that. Most likely it was independent reinvention.

3 2

Re: [tz] [IANA #985615] Sudan Time Zone change
by ahmed.atyya＠ntc.gov.sd June 25, 2018

June 25, 2018

Dear Sir/ Madam we would like to inform you that the Republic of Sudan is going to change the time zone from (GMT + 3:00) to (GMT+ 2:00) starting from Wednesday 1 November 2017. this is for your information and action if required. Best Regards Dear Mr. Paul We would like to inform you as TZ coordinator that the Republic of Sudan is planning to change its time zone from GMT+ 3:00 to GMT +2:00 ( The original time zone ) starting from 1 November 2017 Please if you can update time zone data base Or you you can tell us what action is needed from Sudan government Best Regards Ahmed Atyya Head of Numbering Section National Telecomm. Corporation – Sudan Phone: +249123499988 Email: ahmed.atyya@ ----- Original Message ----- From: Sabrina Tanamal via RT <iana-questions(a)iana.org> To: ahmed atyya <ahmed.atyya(a)ntc.gov.sd> Sent: Tue, 17 Oct 2017 01:33:06 +0300 (EAT) Subject: [IANA #985615] Sudan Time Zone change Dear Ahmed, Thank you for contacting us. We host the Time Zone Database, but updates are made by the Time Zone Coordinator in consultation with the Time Zone mailing list, in accordance with RFC 6557. Questions about the contents of the database should be sent to the mailing list. For mailing list archives and subscription information, please see http://www.iana.org/time-zones Best regards, Sabrina Tanamal IANA Services Specialist On Mon Oct 16 09:55:06 2017, ahmed.atyya(a)ntc.gov.sd wrote: > Dear Sir/ Madam > > > > > > we would like to inform you that the Republic of Sudan is going to > change the time zone from (GMT + 3:00) to (GMT+ 2:00) starting from > Wednesday 1 November 2017. > > > this is for your information and action if required. > > > > > > Best Regards > > > > > > Ahmed Atyya > > > Head of Numbering Section > > National Telecomm. Corporation – Sudan > > Phone: +249123499988 > > Email: ahmed.atyya(a)ntc.gov.sd

6 19

Re: [tz] [PROPOSED] Use "PST/PDT" for Philippine time
by Paul Eggert June 24, 2018

June 24, 2018

Michael H Deckers wrote: > My second point was about the abbreviation "PDT", as proposed > for Manila summer time (which you have called "invented"), > not the abbreviation "PST" (which you have not called > "invented" in your proposal). Ah, sorry, I misunderstood. With "PDT" I was attempting to follow this guideline in theory.html: > Use a consistent style in a tz region's history. > For example, if history tends to use numeric > abbreviations and a particular entry could go either way, use a > numeric abbreviation. Since most Philippine history used an alphabetic abbreviation, I thought it better to do so with daylight-saving time too. This is consistent with Hong Kong, Taiwan and Korea, all of which have "JST" for time during Japanese occupation because they use alphabetic abbreviations now, and it is in contrast to other locations that use "+09" for timestamps under Japanese occupation. We have competing guidelines here: "be consistent" and "don't invent abbreviations", and it's a judgment call as to which is more important. PS. Many of those "+09"s are sheer guesswork by Shanks, but that's a different story....

1 0

Philippine Standard Time
by Paul Goyette June 23, 2018

June 23, 2018

In the Philippines, there is a national law, Republic Act No. 10535 which declares the official time here as "Philippine Standard Time". The act [1] even specifies use of PST as the abbreviation, although the FAQ provided by PAGASA [2] uses the "acronym PhST to distinguish it from the Pacific Standard Time (PST)." (Interestingly, the act does nothing to define the actual value of Philippine Standard Time; there is no UTC offset or other reference. It simply declares what the time is called, and instructs government agencies to coordinate with PAGASA for synchronization. :) There are references to "Section 6 of Batas Pambansa Bilang 8" [3] (which directs the adoption of the Metric System), but Section 6 merely delegates the task of establishing the definition of "second" to PAGASA. I've been unable so far to find any specific implementing regulation that establishes an official 8-hour offset from GMT.) Not long ago, the TZ database clean-up of "invented" abbreviations removed the PST abbreviation for Asia/Manila, leaving us with no abbreviation. Based on the existence of national law declaring Philippine Standard Time, and formally establishing the abbreviation/acronym, could we please get "PST" (or, if you prefer, "PhST") re-included into the next update of the TZDB? Thanks! References: [1] http://www.officialgazette.gov.ph/2013/05/15/republic-act-no-10535/ [2] https://www1.pagasa.dost.gov.ph/index.php/astronomy/philippine-standard-tim… [3] http://www.chanrobles.com/bataspambansabilang8.htm +------------------+--------------------------+----------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org | +------------------+--------------------------+----------------------------+

6 8

US daylight saving proposals in Texas, California, and Louisiana
by Paul Eggert June 19, 2018

June 19, 2018

This week the Republican Party of Texas is writing its official platform, which contains new planks that call for "abolishing daylight saving time and Texas Child Protective Services". (This quote is from McGaughy's report cited below.) The California State Senate approved a proposal Thursday to move California toward Mountain Standard Time all year (or permanent PDT, if you prefer). The measure would require voter approval in November, plus a second bill and federal approval. The basic idea is similar to the proposal in Florida that Arthur noted in March. Last month the Louisiana legislature overwhelmingly approved a resolution to study a proposal that presumably would also be similar to Florida's, in that Louisiana would move to Eastern Standard Time all year (or permanent CDT, if you prefer). Sources: Bacon-Blood L. Should Louisiana use Daylight Saving Time? State task force will evaluate the options. Times-Picayune. 2018-05-24. https://www.nola.com/politics/index.ssf/2018/05/la_task_force_will_study_me… Luna T. End of daylight saving time inches closer in California. Sacramento Bee. 2018-06-14. https://www.sacbee.com/news/politics-government/capitol-alert/article213187… McGaughy L. New Texas GOP platform calls for abolishing daylight saving, protecting Confederate monuments. Dallas Morning News. 2018-06-18. https://www.dallasnews.com/news/texas-politics/2018/06/16/vote-count-underw…

1 0