Typo in africa timezone file
In https://www.ietf.org/timezones/data/africa I found the following lines: # From Gunther Vermier (2015-05-13): # our Egypt office confirms that the change will be at 15 May "midnight" (24:00) I think the timestamp (2015-05-13) is not correct there. Should it say 2014-05-13 instead? -- +-------------------------------------------+ | Marcel Telka e-mail: marcel@telka.sk | | homepage: http://telka.sk/ | | jabber: marcel@jabber.sk | +-------------------------------------------+
Thanks for spotting that. I applied the attached patch to the experimental version.
The relatively new use of 24:00 for a transition time is less than ideal. While zic can be unambiguous in its interpretation, it is just an interpretation even if that interpretation is correct/authoritative. The data is published and interpreted by other applications too and or read by humans. To me the instant 2015-05-13 24:00 actually means 2015-05-14 00:00.... The instance 2015-05-13 24:00 does not really exist because at the very instant you roll over to 00:00 on the next date. But this is not zic's interpretation ? Currently we have just Africa/Cairo and Asia/Dhaka using 24:00 as a transition time. Should not these be updated to avoid 24:00 and the ambiguity that arises. Because of this ambiguity, as an international airline, we never schedule any flights to depart of arrive at midnight (00:00 or 24:00). Anyway, the use of 24:00 _seems_ to have broken the JodaTime library. On 4 September 2014 06:15, Marcel Telka <marcel@telka.sk> wrote:
In https://www.ietf.org/timezones/data/africa I found the following lines:
# From Gunther Vermier (2015-05-13): # our Egypt office confirms that the change will be at 15 May "midnight" (24:00)
I think the timestamp (2015-05-13) is not correct there. Should it say 2014-05-13 instead?
-- +-------------------------------------------+ | Marcel Telka e-mail: marcel@telka.sk | | homepage: http://telka.sk/ | | jabber: marcel@jabber.sk | +-------------------------------------------+
On 11 September 2014 00:45, "" <lord.buddha@gmail.com> wrote:
To me the instant 2015-05-13 24:00 actually means 2015-05-14 00:00....
This is correct, and this is how zic interprets it.
Currently we have just Africa/Cairo and Asia/Dhaka using 24:00 as a transition time.
There are a few others; namely, America/Montreal, Asia/Amman, Asia/Gaza, Asia/Hebron, and Europe/Helsinki.
Should not these be updated to avoid 24:00 and the ambiguity that arises.
On the contrary, 24:00 is meant to be quite *un*ambiguous. We can't stop governments from ambiguously declaring that rules start "at midnight" without specifying which one. But we can be clear, when representing those rules, about which midnight we understand to be the correct one to use. In some cases, that's simpler to express with 00:00; in others, with 24:00. Africa/Cairo's main (non-Ramadan) rules for the near future are most succinctly expressed with one of each: Rule Egypt 2014 max - Sep lastThu 24:00 0 - Rule Egypt 2015 2019 - Apr lastFri 0:00s 1:00 S Anyway, the use of 24:00 _seems_ to have broken the JodaTime library.
That may be, but if so, it's been broken for five years. http://mm.icann.org/pipermail/tz/2014-June/020964.html -- Tim Parenti
Tim Parenti wrote:
24:00 is meant to be quite *un*ambiguous.
"24:00" also has been standardized for many years. This includes not only ISO 8601 but also older standards, going back at least to a resolution proposed by the great lunar photographer Lewis Rutherford and adopted by the International Meridian Conference in 1884. See: http://www.cl.cam.ac.uk/~mgk25/iso-time.html http://en.wikipedia.org/wiki/24-hour_clock
participants (4)
-
"" -
Marcel Telka -
Paul Eggert -
Tim Parenti