- tz - lists.iana.org

Question about IANA time zone names
by Avila, Edgar May 15, 2015

May 15, 2015

Hi, I'm a software engineer working on the data modeling group. We are trying to figure out how the IANA time zone names can be described on our message model. At the modem it seems that the time zone names such as America/Costa_Rica or Japan are just a string without restrictions. We wonder whether there is a restriction such as maximum length of characters, pattern of characters to allow, etc. One more question, is it really America/Costa_Rica or Japan a name or an ID? The following is the description we have today in one of our schemas: <xs:simpleType name="IANATimeZoneId_Type"> <xs:annotation> <xs:documentation> Timezone Id represented by IANA. </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"/> </xs:simpleType> Thanks in advance ________________________________ [https://www.aciworldwide.com/photolibrary/ACI_logotag_footer.gif]<http://www.aciworldwide.com> This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.

2 1

Re: [tz] [C/C++ PATCH] Implement -Wshift-negative-value (PR c/65179)
by Paul Eggert May 12, 2015

May 12, 2015

On 05/08/2015 09:59 AM, Joseph Myers wrote: > Paul, although glibc's copy of parts of tzcode is a bit out of date, it > looks like the currenthttps://github.com/eggert/tz.git still has the > problematic code in private.h, relying on left-shifting -1 which has > undefined behavior in C99/C11 (implementation-defined in C90, as per > DR#081). Thanks for reporting that. I installed the attached patch into the experimental tz version on github <https://github.com/eggert/tz>, with the intent that this fix propagate into the next tz release and thus into glibc etc.

3 2

Problem with tzselect and Dominica
by Owen Leibman May 12, 2015

May 12, 2015

Using a freshly downloaded version of tzelect, and choosing 2 (Americas) followed by 18 (Dominica), the following results: ./tzselect: line 469: /usr/share/zoneinfo/ America/Port_of_Spain: No such file or directory ./tzselect: time zone files are not set up correctly I believe that is because Dominica's abbreviation (DM) is actually found in some comments near the head of the file. To avoid this problem, I believe he awk statement at line 463: $1 ~ cc && $4 == region { print $3 } needs to be changed thus to exclude comment lines: $0 !~ /^#/ && $1 ~ cc && $4 == region { print $3 }

2 1

[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