- tz - lists.iana.org

Bangladesh's TZ Abbreviation
by Hank W Jan. 18, 2013

Jan. 18, 2013

The online Bangladesh newspaper bdnews24.com repeatedly abbreviates Bangladesh Standard Time as BdST, as opposed to the BDT abbreviation in the current Asia file of the tzdata. For example, the article at http://bdnews24.com/bangladesh/2009/12/31/2010-new-decade-cheered-in, (dated 2010-01-01) states in part, "Clocks went back at 11:59pm on Thursday night--rather than midnight--to restore Bangladesh Standard Time (BdST), GMT+6." I found many similar examples in a search for BdST within the site. Searches for BdDT and BdT yielded nothing. A search for BDT yields many references to their currency, not their time. I searched also for BST and found it referring to Bangladesh Standard Time in articles from about seven or eight years ago, while in articles from the current decade it seems to be referring only to British Summer Time. Hank W. Austin, Texas, U.S.A. Time Guru Wannabe

2 2

Bulletin C number 45
by Denis Excoffier Jan. 18, 2013

Jan. 18, 2013

INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : 33 (0) 1 40 51 22 29 FAX : 33 (0) 1 40 51 22 91 Internet : services.iers(a)obspm.fr Paris, 18 January 2013 Bulletin C 45 To authorities responsible for the measurement and distribution of time INFORMATION ON UTC - TAI NO leap second will be introduced at the end of June 2013. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2012 July 1, 0h UTC, until further notice : UTC-TAI = -35 s Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC, or to confirm that there will be no time step at the next possible date. Daniel GAMBIS Director Earth Orientation Center of IERS Observatoire de Paris, France __________________________________________

1 0

Re: [tz] TZ file comments UTF-8? Bastardized HTML?
by Russ Allbery Jan. 14, 2013

Jan. 14, 2013

Steffen "Daode" Nurpmeso <sdaoden(a)gmail.com> writes: > Russ Allbery <rra(a)stanford.edu> wrote: > |If you do decide to use POD, you may want to pick a different letter than > |I, since I<> is already a POD formatting code (for italics). D<> is safe > |to use; there's no existing formatting code. > Well, that was just what came to my mind on saturday. > Maybe U<> (for URL)? It seems unused. Yup, that would work. > I also can hardly imagine that spreading formatting tags will be > accepted by the actual tz maintainer(s), since otherwise they > might have done it 15 years ago. True. :) > I think the script can easily get extended by another mode which simply > takes an encoding name and reads text from STDIN/file, converting to tz > database-style comment output along the way; i.e., HTML entities. It > would have to decode HTML entities to E<>, which should work, then? > Shouldn't be that hard either. Yup, that would also work and wouldn't be too difficult, since E<> takes the same values as HTML entities. > ..Well i think for L<> to work the way you show it above the POD parser > must be adjusted; or we need to use special tags and make POD treat them > as links. You mean the L<anchor|http://www.example.com/> form? No, that's just standard POD; any POD parser will handle that out of the box. Or do you mean not emitting the contents of U<> and D<>? that would indeed require some tweaks, but not very difficult ones. > I haven't yet used POD any more sophisticated than this: > use Pod::Text; > my $parser = Pod::Text->new(loose => 1, indent => 0, width => 72); > $parser->parse_from_file($0, '-'); > and of course normal module documentation, so some hints how to do > the required task would be appreciated. Basically, you tell Pod::Simple that you accept some additional formatting codes with: $parser->accept_codes(qw(D U)); and then add new cmd_d and cmd_u subs that do whatever they should do with the contents. I can explain more if anyone is interested in going this direction. > It of course all stands and falls with wether these adjustments > will be acceptable for the tz database as such. > I'm not planning to fork the project. Indeed. -- Russ Allbery (rra(a)stanford.edu) <http://www.eyrie.org/~eagle/>

2 3

latest zic mishandles Africa/Cairo past 2038?
by Paul Eggert Jan. 11, 2013

Jan. 11, 2013

When I run the command "make check_public" in the tz distribution, several warnings are generated. I'd like to fix things so that it builds cleanly. Let's start with the first warning: "africa", line 190: warning: no POSIX environment variable for zone Africa/Cairo As I understand it, this warning is saying that zic can't deduce a POSIX-style TZ setting for Africa/Cairo time stamps predicted past 2038. But if you look at the data, there's a straightforward POSIX-style setting for that, namely TZ='EET-2'. My guess is that zic is confused because the most-recent Rule is for 2010. Is my guess correct? Is this a bug in zic.c, which can be fixed?

1 0

[PATCH 2/2] Move 'make check' to Ubuntu 12.10.
by Paul Eggert Jan. 11, 2013

Jan. 11, 2013

Checking the Busingen patch caused me to realize I needed to upgrade the Makefile to match a new file location in Ubuntu 12.10. I pushed this to github as well and plan to put it into the next release. * Makefile (SGML_DTDDIR): New macro, for easier porting. Update to file name used in Ubuntu 12.10. (SGML_SEARCH_PATH): Use SGML_DTDDIR. --- Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index feec727..2b256f5 100644 --- a/Makefile +++ b/Makefile @@ -246,9 +246,10 @@ AWK= awk KSHELL= /bin/bash # The path where SGML DTDs are kept. -# The default is appropriate for Ubuntu. +# The default is appropriate for Ubuntu 12.10. SGML_TOPDIR= /usr -SGML_SEARCH_PATH= $(SGML_TOPDIR)/share/xml/xhtml/schema/dtd/REC-html401-19991224 +SGML_DTDDIR= $(SGML_TOPDIR)/share/xml/w3c-sgml-lib/schema/dtd +SGML_SEARCH_PATH= $(SGML_DTDDIR)/REC-html401-19991224 # The catalog file(s) to use when validating. SGML_CATALOG_FILES= HTML4.cat -- 1.7.10.4

1 0

CST for both DST and standard time in Australia/South?
by kavi＠postpro.net Jan. 7, 2013

Jan. 7, 2013

Please see https://bugs.php.net/bug.php?id=63777 The upshot: Australia/South observes daylight savings time, but the tzdata entry specifies 'CST' as the abbreviation year round. Is this a problem?

2 1

Re: [tz] "non-standard" timezones
by Shawn Steele Jan. 7, 2013

Jan. 7, 2013

> Typically, I think, people use what is coming from the tz database, unchanged. > And in the exceptions, they typically edit an existing entry rather than come up with a new name. > And in the exceptions to *that*, they typically use a name similar to the names already > in the database, rather than an unusual name. That sounds logical, but are there *any* known cases where people make exceptions to the standard? Even if they're reusing names? Especially if they're reusing names? (Reusing names for different behavior seems bad for interop). -Shawn

3 2

"non-standard" timezones
by Shawn Steele Jan. 5, 2013

Jan. 5, 2013

Hoping someone can provide examples or something. Are there cases where people are using their own Timezone data? (I'm thinking like a company or research station or something that doesn't snap to some "normal" tz for some reason) Any examples? For non-standard timezones is there a recommendation for naming conventions? (Eg: etc/mine ?) In several systems it's possible to adjust the Timezone data, and, of course someone could edit and install their own versions of the tzdb data on systems that consume it, but I'm curious if it ever happens in practice? Thanks, Shawn

2 3

timezone db error
by Mayuresh Kathe Dec. 29, 2012

Dec. 29, 2012

Hello, there's an error while representing a timezone in your database. May I know who to communicate and interact with regarding getting it corrected? Thanks. ~Mayuresh -- Simplicity can be Marvelously Powerful.

5 8

Non-ASCII chars in southamerica file
by Andy Heninger Dec. 27, 2012

Dec. 27, 2012

In the southamerica data file we have several Latin-1 encoded non-ASCII characters. The other data files are 100% ASCII Here they are: $ grep -nP "[\\x80-\\xff]" * southamerica:384:# There's also a note in only one of the major national papers (La Naci�n) at southamerica:390:# (...) anunci� que el pr�ximo domingo a las 00:00 los puntanos deber�n southamerica:393:# A partir de entonces, San Luis establecer� el huso horario propio de southamerica:395:# 2009, el cambio horario quedar� comprendido entre las 00:00 del tercer southamerica:396:# domingo de marzo y las 24:00 del segundo s�bado de octubre. southamerica:815:# I just send a e-mail to Zulmira Brand�o at I think it's fine to allow non-ASCII in comments, but would strongly request that the files be UTF-8 encoded. Anything else leads to immense confusion over what charset is in use. -- Andy

4 3