Will Morocco switch from +01 to +00 during Ramadan next year?
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-des...
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.
Personally, I feel like it is premature to bring back the Ramadan DST suspension period. The cited articles appear to be opinions and surveys only. I would like to see something, anything, from an official source saying that they will do this before it is released in the tzdb. Thanks, Matt -----Original Message----- From: tz <tz-bounces@iana.org> On Behalf Of Paul Eggert Sent: Thursday, November 1, 2018 10:52 AM To: Maamar Abdelkader <A.MAAMAR@iam.ma> Cc: Mounir EL MOKHTARI <momokhtari@gmail.com>; Adlouni mehdi <adlounimehdi@gmail.com>; Time zone mailing list <tz@iana.org>; Imad Bidaoui <imad.bida8@gmail.com> Subject: [tz] Will Morocco switch from +01 to +00 during Ramadan next year? 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flecon omiste.com%2Farticle%2F1035870-enquete-l-economiste-sunergia-64-des-ma rocains-plebiscitent-le-gmt-pendant-ramadan&data=02%7C01%7Cmatt.jo hnson%40microsoft.com%7C90c8e6b5dd484f218a3408d64022cdec%7C72f988bf86f 141af91ab2d7cd011db47%7C1%7C0%7C636766915604936547&sdata=gDoCFpaY% 2FQc93ra%2FNubOdY%2B2i8fhibLoRtg0yk%2B91sY%3D&reserved=0
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.
On 11/1/18 10:59 AM, Matt Johnson (AZURE) wrote:
The cited articles appear to be opinions and surveys only. I would like to see something, anything, from an official source
I'd also like to see something official. However, the Moroccan government appears to have made last week's announcement at the last minute to suppress political controversy that could have derailed the change, and it's not implausible that they'll do something similar for next year's Ramadan change - which would be a real problem for us and our downstream data users. When there's a conflict between "official" and "practical" time for past timestamps, I have preferred "practical" time on the grounds that users typically prefer the timestamps they actually used. This recently came up for El Paso, which would require its own Zone line if tzdata merely recorded official US time zone legislation; but tzdata doesn't do that, and instead reflects the timestamps that the vast majority of El Pasoans actually used during the period in question. Similarly, for Morocco we now have the situation where the government's officially announced plans do not currently include a Ramadan fallback. Here, too, we have a conflict between "official" and "practical" time, the main difference being that here the timestamps in question are predicted timestamps, not past timestamps. This is a judgment call, and I could certainly see the call going the other way in other circumstances. However, in this particular instance the case for including the guessed change is reasonably compelling: people on the ground are telling us that a Ramadan fallback is most likely what will happen, a poll has been published saying there's a broad consensus for a fallback, and Morocco has been doing such fallbacks for five years already. tzdata is always guessing about the future, and it's better to make the best guess we can even when the guess isn't official yet. (Besides, if we guess wrong now we can always fix it later. :-)
participants (2)
-
Matt Johnson (AZURE) -
Paul Eggert