November 2018 - tz - lists.iana.org

[PROPOSED] Bring back attribute_pure for getzname
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

* localtime.c (getzname, getqzname): Bring back ATTRIBUTE_PURE. I was mistaken about GCC not needing this any more, as it’s still needed with GCC 8.2.1 when building with ‘make GCC_INSTRUMENT= CFLAGS='$(GCC_DEBUG_FLAGS)'’. --- localtime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/localtime.c b/localtime.c index 7b72f9c..ac3790a 100644 --- a/localtime.c +++ b/localtime.c @@ -789,7 +789,7 @@ static const int year_lengths[2] = { ** Return a pointer to that character. */ -static const char * +static ATTRIBUTE_PURE const char * getzname(register const char *strp) { register char c; @@ -810,7 +810,7 @@ getzname(register const char *strp) ** We don't do any checking here; checking is done later in common-case code. */ -static const char * +static ATTRIBUTE_PURE const char * getqzname(register const char *strp, const int delim) { register int c; -- 2.19.1

1 0

Will Morocco switch from +01 to +00 during Ramadan next year?
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

Maamar Abdelkader wrote: > The 2019 Ramadan period is supposed to be from May 5th to June 4th. > We usually move clocks back the previous week end and come back to the +1 the week end after. > So it supposed to be sunday april 28 and sunday june 12. > > The government does not announce yet the decision about this temporarily change. > > But it s 99% sure that it will be the case, as the previous years. > > A non official survey was done these days, showing that 64% of asked peopke are ok for moving from +1 to +0 during Ramadan. > > https://leconomiste.com/article/1035870-enquete-l-economiste-sunergia-64-de… > > I will share the official decision once it s published. Thanks for the info. I installed the attached patches into the development version on GitHub to implement this. This patch doesn't exactly agree with the dates you specified (for 2019 it guesses falling back Sunday, May 5 and springing forward Sunday, June 9), but these dates are approximate until an official announcement and a methodical guess is better than no guess at all. Java users, please note that this patch uses negative DST in the main and vanguard formats; in rearguard format Morocco stays in the +00 timezone (instead of moving to +01 last weekend) and observes positive DST in every month but Ramadan.

2 2

Time zone confusion in Morocco
by Paul Eggert Nov. 1, 2018

Nov. 1, 2018

Since 2012 Morocco has been switching from +01 (DST) to +00 (standard time) for Ramadan. In an article in today's Morocco World News, Safaa Kasraoui implies (but does not explicitly state) that Morocco will continue this practice even after its time zone switch last weekend from +00 to +01, and thus that Morocco will switch from +01 (standard time) to +00 (presumably DST) during Ramadan next year. If so, we'll have to change tzdb again, this would be another use of negative DST, and I'll bring back my Emacs-based predictions of Ramadan for Morocco. Kasraoui also reports that MP Abdellatif Ouahbi has called on the Moroccan government to release the study that the government said it had conducted on time change. My guess is that no real study was conducted, that the government knew the change would be controversial, and that it announced the change with so little notice because it didn't want controversy to derail the change. The government's main argument for not using DST was the confusion and "tensions and diseases" of switchover, and its main argument for adopting +01 instead of +00 appears to be to smooth out peaks in electricity consumption, though it appears that there is no data to support either argument. As part of the time zone change, the government also changed school timetables so that schools will start at 09:00 instead of 08:00, effectively canceling the time zone change for schools. It said it will make further measures regarding DST, without giving details. Kasraoui reports, "Clocks set by the internet with Moroccan cities selected as the time zone returned to GMT on Sunday and, as of Wednesday, are still showing the wrong time." Presumably this mostly refers to Android and iOS phones; although my US-baseed Android 9 phone is not updated, the Ubuntu desktop that I'm typing this message on is updated. Ubuntu is downstream from Debian which in turn is downstream from tzdb, and the timeline for my desktop update was as follows (all times UTC): 2018-10-27 05:22:45 2018g timestamped 2018-10-27 05:23:38 2018g committed to development version 2018-10-27 12:10:11 2018g available from iana.org 2018-10-27 13:14:23 2018g created for Debian sid 2018-10-27 15:55:08 2018g announced on tz-announce(a)iana.org 2018-10-28 02:00:00 rule change takes effect in Morocco 2018-10-28 21:51:08 2018g created for Ubuntu bionic 2018-10-30 05:23:27 2018g updated on my desktop The update on my desktop was part of routine maintenance. Although Ubuntu is about as good as it gets in this area for a consumer-facing OS, we should be able to even better. Debian beat the deadline but Ubuntu (downstream from Debian) did not, my desktop had the wrong Morocco time for over two days, and my guess is that almost all cell phones and computers in Morocco still have the wrong data for Morocco. Reference: Kasraoui S. Benabdelkader: 68% of Moroccans Wanted an End to Time Changes. Morocco World News. 2018-10-31 13:44 +01. https://www.moroccoworldnews.com/2018/10/256539/

1 0