- tz - lists.iana.org

Brazil DST called out
by Rodrigo Freire Oct. 16, 2018

Oct. 16, 2018

Government decided to abandon the announced second DST change. So it will start in November 4. https://g1.globo.com/politica/noticia/2018/10/15/planalto-informa-que-nao-h… - RF Sent from a mobile device

1 0

Ethiopia local time
by admin＠afocha.com Oct. 13, 2018

Oct. 13, 2018

Greetings, Although Ethiopia is officially in East Africa Time (UTC +3:00), the local time used in the country adopts a different system where 6:00 AM is interpreted as 12:00 and socially used as such. People will see a clock with the time at 1:30, and they will say this is 7:30. The local time is used by businesses in the country and by government offices. Everyone generally does this conversion in their heads, so at times, someone who is unfamiliar with this system can end up inadvertently scheduling meetings for the wrong time. This method of time tracking was developed and maintained with the premise of associating the clock's starting point of 12:00 with sunrise, which is roughly taking place around 6:00 AM every day. So East Africa Time - 6:00 is the working time used by the vast majority of Ethiopians. Here's an article discussing this time system: https://www.pri.org/stories/2015-01-30/if-you-have-meeting-ethiopia-you-bet… Is it possible to include Ethiopia's local time system into the time zone database? If so, what are the requirements for submitting a new time zone? Thanks for your consideration. Regards, Khalid Duri

17 48

Re: [tz] Europe/Volgograd change from UTC+3 to UTC+4 from 28oct2018
by Paul Eggert Oct. 11, 2018

Oct. 11, 2018

Alexander Fetisov wrote: > Volgograd region in southern Russia (Europe/Volgograd) change timezone from > UTC+3 to UTC+4 from 28oct2018. > > http://sozd.parliament.gov.ru/bill/452878-7 Thanks for the heads-up and the URL. Its supporting info says the transition occurs at 02:00 that day, the usual practice in that region. That web page says "Находится на рассмотрении" which Google Translate renders as "Is pending", and it later says "Срок представления поправок 10.10.2018" which Google Translate renders as "Term for the submission of amendments 10/10/2018", so it sounds like the bill is under consideration but is not yet law and might be amended. Am I correct? If so, we need to know if and when the proposed change becomes definite. If we're pretty sure the law will go in as-is, we might want to update tzdb before October 10 since this is not much notice for downstream users.

3 9

FW: State of Palestine Time zone - need to update
by maysa＠mtit.gov.ps Oct. 10, 2018

Oct. 10, 2018

Dear Sir, I'm contacting you in regard to the time zone data base the field related to the state of Palestine, it's known that Palestine is recognized as a state and it has the Following ISO and Alpha codes, English short name (upper/lower case) Alpha-2 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_e lements> Alpha-3 code <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3#Officially_assigned_code_e lements> Numeric code <https://en.wikipedia.org/wiki/ISO_3166-1_numeric#Officially_assigned_code_e lements> Link to ISO 3166-2 <https://en.wikipedia.org/wiki/ISO_3166-2> subdivision codes <https://en.wikipedia.org/wiki/State_of_Palestine> State of Palestine <https://en.wikipedia.org/wiki/State_of_Palestine> Palestine, State of <https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#PS> PS PSE 275 <https://en.wikipedia.org/wiki/ISO_3166-2:PS> ISO 3166-2:PS PS-JEM Jerusalem <https://en.wikipedia.org/wiki/Jerusalem_Governorate> Al Quds I checked the published data regarding the time zones related to Palestine and noticed that it's not accurate, And hence I would like to ask for an update to the time zone data base related to Palestine to be as follow: PS State of Palestine Asia/AlQuds UTC +3:00 Instead of the following data : PS Palestinian Territory <https://timezonedb.com/time-zones/Asia/Gaza> Asia/Gaza UTC +03:00 PS Palestinian Territory <https://timezonedb.com/time-zones/Asia/Hebron> Asia/Hebron UTC +03:00 Kindly advise if any supporting documents, information or procedures are needed from our side. BR Maysa Monayer Telecom Administration - Deputy General Director Ministry of Telecom and IT (State of Palestine) Mobile: +970-562500044

2 3

Re: [tz] tz Digest, Vol 85, Issue 19 Summer time of Brazil
by Daniel Soares de Oliveira Oct. 9, 2018

Oct. 9, 2018

1 0

Apple Watch Series 4 reboot loop on day of Australian spring-forward transition
by Paul Eggert Oct. 8, 2018

Oct. 8, 2018

Benjamin Mayo reports in 9to5Mac that last weekend's spring-forward clock transition in Australia caused the Apple Watch Series 4 to go into a reboot loop when displaying the day's timeline in the Activity complication on the Infograph Modular face. The watch reboots, attempts to display the timeline again, and reboots again, over and over. Apparently the application has trouble with a 23-hour day. Apple solved the problem by - doing nothing yet. After 23 hours of rebooting, an Australian user's watch (if it still has power left) reboots, sees a new day with 24 hours, and displays a nice 24-hour timeline again. Mayo writes, "Obviously, Apple will need to release a bug-fix software update to stop this problem from happening again." There's no word yet on what the current Apple software will do when faced with a 25-hour day. Mayo B. Some Apple Watch Series 4 models repeatedly crashing and rebooting due to daylight saving time bug. 9to5Mac. 2018-10-07 04:31 -07. https://9to5mac.com/2018/10/07/apple-watch-series-4-crash-loop-bug/

1 0

Re: [tz] [PROPOSED] Improve leapseconds support
by Hal Murray Oct. 7, 2018

Oct. 7, 2018

eggert(a)cs.ucla.edu said: > * NEWS, leapseconds.awk: Add support for leap seconds at the ends of months > other than June and December. A leap second other than June or December is probably an error in the input data. I would leave the check and add a big comment. Maybe write the code so that it is a simple edit to disable the check. I think there is provision for an intermediate stage between Jun/Dec and every month. Apr/Jun/Sep/Dec. -- These are my opinions. I hate spam.

5 7

[PROPOSED] Improve leapseconds support
by Paul Eggert Oct. 6, 2018

Oct. 6, 2018

(Inspired by a suggestion from Chris Woodbury.) * NEWS, leapseconds.awk: Add support for leap seconds at the ends of months other than June and December. --- NEWS | 5 +++-- leapseconds.awk | 34 +++++++++++++++++++++++++--------- 2 files changed, 28 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index e9f5366..9780cc8 100644 --- a/NEWS +++ b/NEWS @@ -86,8 +86,9 @@ Unreleased, experimental changes transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. - leapseconds.awk now outputs "#updated" and "#expires" comments. - (Inspired by a suggestion from Chris Woodbury.) + leapseconds.awk now outputs "#updated" and "#expires" comments, + and supports leap seconds at the ends of months other than June + and December. (Inspired by suggestions from Chris Woodbury.) Changes to documentation diff --git a/leapseconds.awk b/leapseconds.awk index 6b069b3..ea0567c 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -35,9 +35,25 @@ BEGIN { print "# Leap YEAR MON DAY 23:59:59 - R/S" print "" print "# If the leap second is Rolling (R) the given time is local time (unused here)." - print "# If the leap second is Stationary (S) the given time is UTC." - print "" - print "# Leap YEAR MONTH DAY HH:MM:SS CORR R/S" + + monthabbr[ 1] = "Jan" + monthabbr[ 2] = "Feb" + monthabbr[ 3] = "Mar" + monthabbr[ 4] = "Apr" + monthabbr[ 5] = "May" + monthabbr[ 6] = "Jun" + monthabbr[ 7] = "Jul" + monthabbr[ 8] = "Aug" + monthabbr[ 9] = "Sep" + monthabbr[10] = "Oct" + monthabbr[11] = "Nov" + monthabbr[12] = "Dec" + for (i in monthabbr) { + monthnum[monthabbr[i]] = i + monthlen[i] = 31 + } + monthlen[2] = 28 + monthlen[4] = monthlen[6] = monthlen[9] = monthlen[11] = 30 } /^#\tUpdated through/ || /^#\tFile expires on:/ { @@ -62,14 +78,14 @@ BEGIN { } else { sign = "23:59:59\t-" } - if (month == "Jan") { + m = monthnum[month] - 1 + if (m == 0) { year--; - month = "Dec"; - day = 31 - } else if (month == "Jul") { - month = "Jun"; - day = 30 + m = 12 } + month = monthabbr[m] + day = monthlen[m] + day += m == 2 && year % 4 == 0 && (year % 100 != 0 || year % 400 == 0) printf "Leap\t%s\t%s\t%s\t%s\tS\n", year, month, day, sign } old_TAI_minus_UTC = TAI_minus_UTC -- 2.17.1

1 0

Rename Ukrainian cities to their official transliterated names
by Volodymyr Kostyrko Oct. 5, 2018

Oct. 5, 2018

Hello. This is my first attempt on patching tz database. Hope I did everything right. Included patch renames Kiev to Kyiv, Uzhgorod to Uzhhorod and Zaporozhye to Zaporizhzhia according to official transliteration rules that came in effect 2014. According to Google search most sites are already using Uzhhorod and Zaporizhzhia to name cities, while with Kyiv it's a little bit complicated, as it's the capital so it's name was appearing on a huge list of sites throughout years... I'm just trying to bring a little bit of lawful sanity… Thanks in advance. -- Sphinx of black quartz judge my vow.

16 31

[PROPOSED] Improve leapseconds.awk commentary
by Paul Eggert Oct. 5, 2018

Oct. 5, 2018

(Inspired by a suggestion by Chris Woodbury.) * NEWS: Mention this. * leapseconds.awk: Improve commentary in output file. Output "#updated" and "#expires" comments that reproduce the updated and expiry timestamps in the input file. --- NEWS | 3 +++ leapseconds.awk | 36 +++++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 11 deletions(-) diff --git a/NEWS b/NEWS index 395d9a8..e9f5366 100644 --- a/NEWS +++ b/NEWS @@ -86,6 +86,9 @@ Unreleased, experimental changes transition (or for all time stamps if there are no transitions), just as DST strings specifying DST have always done. + leapseconds.awk now outputs "#updated" and "#expires" comments. + (Inspired by a suggestion from Chris Woodbury.) + Changes to documentation New restrictions: A Rule name must start with a character that diff --git a/leapseconds.awk b/leapseconds.awk index 66eb64d..6b069b3 100644 --- a/leapseconds.awk +++ b/leapseconds.awk @@ -8,21 +8,25 @@ BEGIN { print "# This file is in the public domain." print "" print "# This file is generated automatically from the data in the public-domain" - print "# leap-seconds.list file, which is copied from:" - print "# ftp://ftp.nist.gov/pub/time/leap-seconds.list" + print "# leap-seconds.list file, which can be copied from" + print "# <ftp://ftp.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>" + print "# or <ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list>." print "# For more about leap-seconds.list, please see" print "# The NTP Timescale and Leap Seconds" - print "# https://www.eecis.udel.edu/~mills/leap.html" + print "# <https://www.eecis.udel.edu/~mills/leap.html>." print "" print "# The International Earth Rotation and Reference Systems Service" print "# periodically uses leap seconds to keep UTC to within 0.9 s of UT1" - print "# (which measures the true angular orientation of the earth in space); see" - print "# Levine J. Coordinated Universal Time and the leap second." + print "# (which measures the true angular orientation of the earth in space)" + print "# and publishes leap second data in a copyrighted file" + print "# <https://hpiers.obspm.fr/iers/bul/bulc/Leap_Second.dat>." + print "# See: Levine J. Coordinated Universal Time and the leap second." print "# URSI Radio Sci Bull. 2016;89(4):30-6. doi:10.23919/URSIRSB.2016.7909995" - print "# http://ieeexplore.ieee.org/document/7909995/" + print "# <https://ieeexplore.ieee.org/document/7909995>." print "# There were no leap seconds before 1972, because the official mechanism" print "# accounting for the discrepancy between atomic time and the earth's rotation" - print "# did not exist until the early 1970s." + print "# did not exist." print "" print "# The correction (+ or -) is made at the given time, so lines" print "# will typically look like:" @@ -30,18 +34,19 @@ BEGIN { print "# or" print "# Leap YEAR MON DAY 23:59:59 - R/S" print "" - print "# If the leapsecond is Rolling (R) the given time is local time." - print "# If the leapsecond is Stationary (S) the given time is UTC." + print "# If the leap second is Rolling (R) the given time is local time (unused here)." + print "# If the leap second is Stationary (S) the given time is UTC." print "" print "# Leap YEAR MONTH DAY HH:MM:SS CORR R/S" } -/^ *$/ { next } - /^#\tUpdated through/ || /^#\tFile expires on:/ { last_lines = last_lines $0 "\n" } +/^#[$][ \t]/ { updated = $2 } +/^#[@][ \t]/ { expires = $2 } + /^#/ { next } { @@ -71,5 +76,14 @@ BEGIN { } END { + # The difference between the NTP and POSIX epochs is 70 years + # (including 17 leap days), each 24 hours of 60 minutes of 60 + # seconds each. + epoch_minus_NTP = ((1970 - 1900) * 365 + 17) * 24 * 60 * 60 + + print "" + print "# POSIX timestamps for the data in this file:" + printf "#updated %s\n", updated - epoch_minus_NTP + printf "#expires %s\n", expires - epoch_minus_NTP printf "\n%s", last_lines } -- 2.17.1

1 0