- tz - lists.iana.org

[PROPOSED PATCH 1/2] Prefer '$(MAKE)' to 'make'
by Paul Eggert May 8, 2015

May 8, 2015

* Makefile (check_public, check_time_t_alternatives) (typecheck): Use '$(MAKE)' instead of 'make'. This has better behavior with GNU 'make' and -j. --- Makefile | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index 6f70979..8d624bc 100644 --- a/Makefile +++ b/Makefile @@ -324,6 +324,8 @@ GZIPFLAGS= -9n ############################################################################### +#MAKE= make + cc= cc CC= $(cc) -DTZDIR=\"$(TZDIR)\" @@ -572,8 +574,8 @@ set-timestamps.out: $(ENCHILADA) # We also do an all-files run to catch links to links. check_public: $(ENCHILADA) - make maintainer-clean - make "CFLAGS=$(GCC_DEBUG_FLAGS)" $(ENCHILADA) all + $(MAKE) maintainer-clean + $(MAKE) "CFLAGS=$(GCC_DEBUG_FLAGS)" $(ENCHILADA) all mkdir tzpublic for i in $(TDATA) ; do \ $(zic) -v -d tzpublic $$i 2>&1 || exit; \ @@ -592,8 +594,8 @@ check_time_t_alternatives: zones=`$(AWK) '/^[^#]/ { print $$3 }' <zone1970.tab` && \ for type in $(TIME_T_ALTERNATIVES); do \ mkdir -p tzpublic/$$type && \ - make clean_misc && \ - make TOPDIR=`pwd`/tzpublic/$$type \ + $(MAKE) clean_misc && \ + $(MAKE) TOPDIR=`pwd`/tzpublic/$$type \ CFLAGS='$(CFLAGS) -Dtime_tz='"'$$type'" \ REDO='$(REDO)' \ install && \ @@ -639,12 +641,12 @@ tzdata$(VERSION).tar.gz.asc: tzdata$(VERSION).tar.gz gpg --armor --detach-sign $? typecheck: - make clean + $(MAKE) clean for i in "long long" unsigned; \ do \ - make CFLAGS="-DTYPECHECK -D__time_t_defined -D_TIME_T \"-Dtime_t=$$i\"" ; \ + $(MAKE) CFLAGS="-DTYPECHECK -D__time_t_defined -D_TIME_T \"-Dtime_t=$$i\"" ; \ ./zdump -v Europe/Rome ; \ - make clean ; \ + $(MAKE) clean ; \ done zonenames: $(TDATA) -- 2.1.0

1 1

[PROPOSED PATCH 1/3] Remove hair from southamerica comment
by Paul Eggert May 4, 2015

May 4, 2015

While using the tz source to test some other program I found an unwanted hair space (U+200A) in the commentary. Fix this, and adjust Makefile to catch this sort of thing in the future. * Makefile (SAFE_CHARSET): Exclude ] and -, as they're now the invoker's responsibility. Invoker changed. (NONSYM_CHAR): Remove, replacing with ... (OK_CHAR): ... this new macro. All uses changed. (NONSYM_LINE, VALID_LINE): Remove, replacing with ... (OK_LINE): ... this new macro. All uses changed. (check_character_set): Simplify test, and report all non-ASCII non-letters. Remove the exception for Makefile, as it no longer needs to contain non-OK characters. * southamerica: Replace an inadvertent hair space with a space. --- Makefile | 30 ++++++++++++++---------------- southamerica | 2 +- 2 files changed, 15 insertions(+), 17 deletions(-) diff --git a/Makefile b/Makefile index b398727..c3b23c8 100644 --- a/Makefile +++ b/Makefile @@ -292,23 +292,24 @@ TAB_CHAR= ' ' SAFE_CHARSET1= $(TAB_CHAR)' !\"'$$sharp'$$%&'\''()*+,./0123456789:;<=>?@' SAFE_CHARSET2= 'ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\^_`' SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' -SAFE_CHARSET= ]$(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3)- -SAFE_CHAR= '['$(SAFE_CHARSET)']' -# NONSYM_CHAR is a regular expression that matches any character -# except for a small number of symbols, where we prefer to stick with +SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) +SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' + +# OK_CHAR matches any character allowed in the distributed files. +# This is the same as SAFE_CHAR, except that multibyte letters are +# also allowed so that commentary can contain people's names and quote +# non-English sources. For non-letters the sources are limited to # ASCII renderings for the convenience of maintainers whose text editors # mishandle UTF-8 by default (e.g., XEmacs 21.4.22). -NONSYM_CHAR= '[^–—°′″≈≠≤≥±−×÷∞←→↔·•§¶«»‘’‚‛“”„‟‹›「」『』〝〞〟]' +OK_CHAR= '[][:alpha:]'$(SAFE_CHARSET)'-]' # SAFE_LINE matches a line of safe characters. -# SAFE_SHARP_LINE is similar, except any character can follow '#'; +# SAFE_SHARP_LINE is similar, except any OK character can follow '#'; # this is so that comments can contain non-ASCII characters. -# NONSYM_LINE matches a line of non-symbols. -# VALID_LINE matches a line of any validly-encoded characters. +# OK_LINE matches a line of OK characters. SAFE_LINE= '^'$(SAFE_CHAR)'*$$' -SAFE_SHARP_LINE='^'$(SAFE_CHAR)'*('$$sharp$(NONSYM_CHAR)'*)?$$' -NONSYM_LINE= '^'$(NONSYM_CHAR)'*$$' -VALID_LINE= '^.*$$' +SAFE_SHARP_LINE='^'$(SAFE_CHAR)'*('$$sharp$(OK_CHAR)'*)?$$' +OK_LINE= '^'$(OK_CHAR)'*$$' # Flags to give 'tar' when making a distribution. # Try to use flags appropriate for GNU tar. @@ -475,14 +476,11 @@ check: check_character_set check_white_space check_links check_sorted \ check_character_set: $(ENCHILADA) LC_ALL=en_US.utf8 && export LC_ALL && \ sharp='#' && \ - ! grep -Env $(SAFE_LINE) $(MANS) date.1 $(MANTXTS) \ + ! grep -Env $(SAFE_LINE) Makefile $(MANS) date.1 $(MANTXTS) \ $(MISC) $(SOURCES) $(WEB_PAGES) && \ ! grep -Env $(SAFE_SHARP_LINE) $(TDATA) backzone \ iso3166.tab leapseconds yearistype.sh zone.tab && \ - test $$(grep -Ecv $(SAFE_SHARP_LINE) Makefile) -eq 1 && \ - ! grep -Env $(NONSYM_LINE) CONTRIBUTING NEWS README Theory \ - $(MANS) date.1 zone1970.tab && \ - ! grep -Env $(VALID_LINE) $(ENCHILADA) + ! grep -Env $(OK_LINE) $(ENCHILADA) check_white_space: $(ENCHILADA) ! grep -En ' '$(TAB_CHAR)"|$$(printf '[\f\r\v]')" $(ENCHILADA) diff --git a/southamerica b/southamerica index be63a88..6bbc2c8 100644 --- a/southamerica +++ b/southamerica @@ -30,7 +30,7 @@ # I suggest the use of _Summer time_ instead of the more cumbersome # _daylight-saving time_. _Summer time_ seems to be in general use # in Europe and South America. -# -- E O Cutler, _New York Times_ (1937-02-14), quoted in +# -- E O Cutler, _New York Times_ (1937-02-14), quoted in # H L Mencken, _The American Language: Supplement I_ (1960), p 466 # # Earlier editions of these tables also used the North American style -- 2.1.4

2 4

Re: [tz] Kyiv time zone
by sam.ua April 29, 2015

April 29, 2015

Dear Florian. perhaps you are not aware of the history between Ukraine and Russia. Let me remind you that Moscow has pursued the destruction of Ukraine, Ukrainians and the Ukrainian language and culture for many centuries. This ethnic cleansing continues today with the Russification of Ukraine. Once you destroy a nation's identity --their language, culture and history, it's quite easy to convert them into mindless robots, who are easy prey for the imperialist. Even in 1991, as we achieved our long overdue independence , Ukrane was over 80-90% pro-Russian. after two plus decades those same people, who were once slaves to the empire, have been schooled on the true history of Ukraine and understand just how devious Moscow was in it's ethnic cleansing of the Ukrainian people. Little over a year ago we got rid of the last remaining remnant of that Soviet-Russian past - the Putin puppet Yanykovych. Our cities are nearly rid of Lenin and Stalin - two monsters that murdered tens of millions of Ukrainians, but as the links you provided show, that past is still a part of the present. We are gradually getting rid of it. The issue of Kyiv vs Kiev is precisely the past vs the present. Kyiv is today, it's also what it was in the old Ruthenian-Ukrainian chronicles that date back to the 9th century. It became Kiev under Russian rule and now it's once again Kyiv. The war in Eastern Ukraine - the invasion by Russia, is a last attempt too keep Ukraine under Russia's orbit. we don't want that. My generation doesn't want that. Once again Kyiv vs Kiev is a part of that ugly past. I can promise you that all of our sites will one day be Kyiv and that the term will be the one used wide-spread and worldwide. But we need to do this one step at a time and wikipedia is a big part of this. This has to be corrected and the general population will then become familiar and accept the new word, it's very easy to spell and pronounce. I kindly ask that you respect our history, our past and what is currently happening in eastern Ukraine. it's no accident that where the Russian population - 15% of Ukraine's population. lives and breathes, there is a war. the same way Stalin killed my forefathers and replaced them with Russians from Russia, we are battling for the existence of our own unique identity. Kyiv is and will always be the proper transliterated version of our capital. there is no argument today that can supercede that. Thank you kindly, Simon Kostenko ---- On сб, 28 бер 2015 11:27:35 +0200 Florian Weimer<fw(a)deneb.enyo.de> wrote ---- * Simon: >> Many government web sites in the Ukraine still use the “Kiev” >> transliteration > For example? “While the Obama administration has publicly acknowledged it is considering supplying Kiev with arms, backed by hardline EU countries like Poland and Lithuania, German Chancellor Angela Merkel has vehemently opposed the move.” <http://www.kmu.gov.ua/control/en/publish/article?art_id=248025420>

11 10

Database and Code compatibility
by Thomas v. Karlsson April 28, 2015

April 28, 2015

Hi, I would like to know the compatibility constraints between the code and the datebase. Is the code forward and backward compatible with the database binaries? I.e can code read older and newer version of database binaries? Or do the code and the database need to be version sync with each other? Thanks Thomas Karlsson

2 1

ASEAN time shelved for now
by Paul Eggert April 27, 2015

April 27, 2015

ASEAN foreign ministers decided yesterday to put the proposal for a common (UTC+8) time zone "in abeyance", i.e., they'll keep looking at it but it's not going to happen any time soon if ever. Agence France-Presse. Too early for common SE Asia time zone. The Sun (Malaysia) 2015-04-26. http://www.thesundaily.my/news/1396105

1 0

Re: [tz] Belarus is listed in MSK timezone
by Matt Johnson April 25, 2015

April 25, 2015

Yes , but when you say "identifier", I think "Europe/Minsk", not "MSK". Do you consider both to be identifying a rule set? ________________________________ From: Lester Caine<mailto:lester@lsces.co.uk> Sent: ‎4/‎3/‎2015 1:15 AM To: tz(a)iana.org<mailto:tz@iana.org> Subject: Re: [tz] Belarus is listed in MSK timezone On 03/04/15 08:22, Matt Johnson wrote: > How can we even hope to achieve time zone abbreviations that follow what > people use on the ground if some places don't use abbreviations at all? While on one hand the bulk of the current rules are well established, some edge cases simply need a unique identifier for the internal rule set being referred to. I'll repeat what I keep saying ... the local 'conversion' of the descriptions is not something that the TZ database has any control over, and in some cases the internal identifiers are simply that ... internal ... only requiring that they uniquely identify a particular rule set. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

11 33

Micronations?
by Matt Johnson April 24, 2015

April 24, 2015

I read an article today about a newly formed country:http://www.businessinsider.com/liberland-this-newly-declared-microc… Which got me thinking - What is the rule/guideline for tzdb treatment of micronations? According to it's wikipedia article (http://en.wikipedia.org/wiki/Liberland) it's currently following CET/CEST. It's on the Croatia/Serbia border, so if modeled in the TZDB it would probably be something simple like: Link Europe/Belgrade Europe/Liberpolis # Liberland Now, I'm not suggesting we add this now - but just wondering at what point we would recognize a micronation? If they were granted an ISO3166 country code, would they show up in zone.tab/zone1970.tab? If they changed their time zone or DST rules, should they get their own zone entry? What if they were never recongnized broadly, but still changed their time conventions? Do we have a policy on this? For that matter - is there a list of general policies documented anywhere?

2 2

Egypt cancels DST permanently
by Paul Eggert April 24, 2015

April 24, 2015

Yesterday the office of Egyptian President El-Sisi announced his decision to abandon DST permanently. This increases the likelihood of the correctness of our guess in 2015d for no DST in Africa/Cairo after 2015. Although the proposed patch (attached) was too late to make the cutoff for 2015d, it affects only commentary.

1 0

[tz-announce] 2015d release of tz code and data available
by Paul Eggert April 24, 2015

April 24, 2015

The 2015d release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes affecting future time stamps Egypt will not observe DST in 2015 and will consider canceling it permanently. For now, assume no DST indefinitely. (Thanks to Ahmed Nazmy and Tim Parenti.) Changes affecting past time stamps America/Whitehorse switched from UTC-9 to UTC-8 on 1967-05-28, not 1966-07-01. Also, Yukon's time zone history is documented better. (Thanks to Brian Inglis and Dennis Ferguson.) Change affecting past and future time zone abbreviations The abbreviations for Hawaii-Aleutian standard and daylight times have been changed from HAST/HADT to HST/HDT, as per US Government Printing Office style. This affects only America/Adak since 1983, as America/Honolulu was already using the new style. Changes affecting code zic has some minor performance improvements. Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2015d.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2015d.tar.gz The files are also available via HTTP as follows: http://www.iana.org/time-zones/repository/releases/tzcode2015d.tar.gz http://www.iana.org/time-zones/repository/releases/tzdata2015d.tar.gz As usual, links to the latest release files are here: http://www.iana.org/time-zones/repository/tzcode-latest.tar.gz http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz ftp://ftp.iana.org/tz/tzcode-latest.tar.gz ftp://ftp.iana.org/tz/tzdata-latest.tar.gz Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 6b36adfdd6baf6e4724bf19fcb090a43722a2522 dated Fri Apr 24 08:09:46 2015 -0700 and tagged '2015d' in the experimental github repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: 2cb4faced839d02e6313a7aacca4d2dfe6454186d9864ee4aa034f7280442e6a751cec2285bde2d5712962b733e107a46f2282469f6510b42d93972d6c34424a tzcode2015d.tar.gz 37b5aa3c5e0d601c8b20fac08d7267c398a836e4190ef85625d5e86a806ba1baceb2315ba81a9a6c854eae4fce40e9c8f90cf5adade3f48ad443f77c221d8983 tzdata2015d.tar.gz Here are the GPG checksums for the release files: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJVOl3RAAoJEO2X6Q5iqn40BtMP/1opNPVcTRK/GFw7wQXpegzS mGM4R1LXua2txG1P8gEkeNHimRqeDWixI/crg4sOoKAb10wvkf70lAI3cVRCMHS+ F4zL3JQJktj/LXBJGmNOwonTdz0mBQASF7DnxX8mL+/QpyKZSy4pTRQDIBKhzlKM PuIpVT6HYXLzi+L2jim2W3EU/7Ja0pOB0pFJNGoJ2SGhja2jvj3Ae3hzfsyXbcQI kQ4Eo7k6hCu0FP7YtGg8D2CqGvXTrErUNI8gTIvT2mV8aDy9j6SbAl0XrTz1UASU lrzwQ/GgGhLeYFMriCCo5zf+H8pjm4+N4JniEf30lIB06CGspQg3ZhchdrexHfWM j+exPhzadR+qQMEdQ95oiY/J5u4N1ykE9WGdianFUlINklCqejImYYKAzMWzFQSs GACVxBp9WWZ1VEAU3eag6TyVKJGiQMtpaGolpVnCaU1JTcFAxpFmOZ55BosS8J/w c+cqke7zTtFfaPJhuylSOca95lAEd14HP+nAFxvGwIhX8z3FbM8pRlOW+rV2wIYH UUAPrSKu+QFTvOl1+TnrydE9cHjbmDC2Vknz1SGel7e2USXTEB4UvgzVyr5E7qf6 ckKB7l6LRIfIXlJSojcF06P2Xz4UJlIbzwA1oXpaK7g9H4YZMGDqIB5HhBRVZx6p KG2eiGYTmCnJt3Gk6SY2 =cvHz -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJVOl3RAAoJEO2X6Q5iqn401YgP/igT318zjaLcBATJ2pQ7aMj1 WrtkZ+m/Urt5pkgtNxtx608eXKTZbs5g9YeJHFS3eN74y8JIrTfNaBiPWNeG0x8m nc83Jvs++B9A8JFjAAjhZVl2TbGTpD5r9FGqQXmIX4qKsB5W1b+OGW3OtXM9vNGK ZVC6TEp/wEuqt3dmjhirLihmdj1W/+2aowlm7PAPhJY9R3QdYJ2dRh8WRvGRSxtc EIorFKgfNOWJJnKCk+YPeK4xPxivNw43nYAy6UnavJYPjTpHxaAx47533R7nm6Cy b2JMdpQSRv4TZrnfz0OzXV/qhJskZNxgf6LR0/3uMSzX1VBO1Wywpmg2wIuij5qo POG8dJr+TsVL3O539DTQ1nYqV0kCzfWirTML9ipF/jwEeG/EFBjkNM6g5eyJLrZp 7Ej4dTbiqmde/Ajh5ECW4AdNQqTaR35BBLtj2PR415dBGhiFMxR30TyX16rbGVWX Mb5abkkS1v4NxLtvi5mtJJl5JNLrYEW/nOqwrIeEEBY2BvvZdeJVqHlXWeBoY9P+ vSQoN9/gCFSQd5olmVVnuP+mqwzyipG8UUsyr7IAyeRc4bRPRyHkC8FdXy+lmrfP HJaPVcPDm6ZFW7BAFw/fqJC6DJj7I48qzKnHb7O9qtkzXjL+wW8kR6SidxANcMa/ 6lJlIHLlXKjj57lVsQHt =zE0V -----END PGP SIGNATURE----- _______________________________________________ tz-announce mailing list tz-announce(a)iana.org https://mm.icann.org/mailman/listinfo/tz-announce

1 0

Egypt 30th Aug DST cancellation
by Mohamed Raouf, Vodafone Egypt April 24, 2015

April 24, 2015

Dear Sirs, On behalf of Vodafone Egypt, I'm writing to inquire about DST package to cancel time change for year 2015 in Egypt. Due to some political decisions, Egyptian government decided to cancel DST that was planned on 30th of April 2015. It is needed to have and updated java package tzdata2015 that is developed by IANA. Below is an official confirmation that DST will be canceled for this year http://www.timeanddate.com/time/change/egypt/cairo Yousry Sincerely, [Description: Description: cid:image001.png@01CEE047.637D02C0]<http://www.vodafone.com.eg/> Mohamed Raouf Charging Services Support Senior Engineer Charging, Mediation & IN Technology Department Vodafone Egypt Mobile: +201002005333 Email: mohamed.raouf(a)vodafone.com<mailto:mohamed.raouf@vodafone.com> Vodafone Egypt, Smart Village : Vodafone C3 Building, Cairo/Alex. Desert Road KM 28- 6th of October City, Egypt ************************************************************************************************************************* The content of this document is classified as Vodafone Egypt S.A.E. Confidential and Proprietary Information. The recipient hereby is committed to hold in strict confidence the contents of this (e-mail, document, information) and not to disclose to any third party without the prior written consent of Vodafone Egypt S.A.E. Recipient will be held liable for any unauthorized disclosure. If you have received this message in error, please notify the sender by return e-mail and delete the message in its entirety, including any attachments. http://www.vodafone.com.eg *************************************************************************************************************************

3 2