- tz - lists.iana.org

User time zones
by Steven Abner Dec. 7, 2011

Dec. 7, 2011

Howdy, I could use some input. I have a different database, lots of reasons for it, which has the attached file as part of the database. I am not an international person, nor is my code yet patented, since the big corps won't take this seriously unless it is. This file was created out of necessity for implementation of operating system functions and a bridge between user and your database, or so I think. Even if you think my thoughts on the intro are invalid, please respond. My initial intent was to submit this for you all to use, but I have already assumed that it will be rejected, the norm! So please, any international users fell free to make suggestive comments. I am in the process of trying to fully automate the list generation, have to hand work some. It has been tested for the strptime(), getdate() and strftime() functions and found not lacking. Of course, this is from test cases I have to think up, since none of the functions I have tested can handle time zones. I am still testing, and re-evaluting for debug-ability and optimizations, so this is not set in concrete. If tz peoples would like to adopt this file, cool! The zic compiler will handle, but your file retrieval will probably need to be altered some. Can't help you there, sorry, different system. There are some notes in the file. In particular this could sate those that aren't fond of the Australia zones and may make Indonesian peoples happy. It addresses, hopefully, French, German and Brazilian peoples too. Off list input also accepted. Steve pheonix(a)zoomtown.com

3 2

Converting from individual cities/states/country names to Windows time zone names
by Daniel White Dec. 6, 2011

Dec. 6, 2011

Hi all, I'm creating a software calculator project, and I'd like my users to be able to convert between time zones using what they're familiar with: country, or city/ state names. So I need to convert from these places to the corresponding Windows time zone, and have been looking for a database online to do so, without success. What I have been able to find is a way to convert from TZID (Olsen) to Windows timezone IDs using this URL: http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/zone_tzid.html So maybe there's a database which maps all the places of the world to TZID, and then I would use a two-step process instead of one. Any help would be much appreciated. When I say 'database', even just a HTML page would do, and then I can extract the right info.

7 14

Fw: Converting from individual cities/states/country names to Windows time zone names
by yoshito_umaoka＠us.ibm.com Dec. 6, 2011

Dec. 6, 2011

> 4) Out of date data > > You may want to map Belarus to (UTC+02:00) Minsk. However, Minsk > (Belarus) is currently using UTC+03:00/no DST. > Microsoft suggests Windows users in Belarus to use (UTC+03:00) > Kakiningrad for now [http://support.microsoft.com/kb/2625508] > BTW, I found Microsoft has already published the update on November 22 [ http://support.microsoft.com/kb/2633952] For this specific instance, display name "(UTC+02:00) Minsk" was changed to "(UTC+02:00) Nicosia", then display name of "(UTC+03:00) Kaliningrad" was changed to "(UTC+03:00) Kaliningrad, Minsk". -Yoshito

1 0

What license IANA is intending to distribute the timezone database under, BSD or public domain
by Fake name Dec. 4, 2011

Dec. 4, 2011

I hope this forum is the correct place to ask this question. This question is intended for the people at IANA. I work for NetApp, and would like to know what license IANA is intending to distribute the timezone database under, BSD or public domain? BSD is referenced in some of the documentation, but in the past people were assuming this was in the public domain until the lawsuit occurred. Thank you in advance for your answer.

7 6

Re: [tz] Rule ChileAQ in antarctica
by Glenn Eychaner Dec. 3, 2011

Dec. 3, 2011

On Dec 2, 2011, at 9:37 PM, tz-request(a)iana.org wrote: > Zone Antarctica/Palmer is currently defined as - > [...] > The comment mentions that Palmer station keeps the same time as Punta > Arenas, Chile. > > However, Rule Chile in southamerica was updated in 2008a, 2010d, 2011c and > 2011e. The rules for Chile after 1999 are defined as below in the current > version. > [...] > If the comment for Antarctica/Palmer is still true, then I think ChileAQ > in antarctica should be also updated. Does anyone know if ChileAQ in > antarctica was intentionally unchanged or, it's just an error? As far as I (one of the people who proposed the Chile 2010/2011 changes) know, it's an error. (I completely forgot about Chile's Antarctic territiory, and that it would appear in a separate file.) Officially, Chile's Antarctic territory is supposed to follow the same rule as the rest of Chile (according to horaoffical.cl). I don't know if that actually happens in practice, or if the other Antarctic territories have also followed all the shifts in Chile's rules. -G. -- Glenn Eychaner (geychaner(a)lco.cl) Telescope Systems Programmer, Las Campanas Observatory

1 0

Rule ChileAQ in antarctica
by yoshito_umaoka＠us.ibm.com Dec. 2, 2011

Dec. 2, 2011

Zone Antarctica/Palmer is currently defined as - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Antarctica/Palmer 0 - zzz 1965 -4:00 ArgAQ AR%sT 1969 Oct 5 -3:00 ArgAQ AR%sT 1982 May -4:00 ChileAQ CL%sT The comment mentions that Palmer station keeps the same time as Punta Arenas, Chile. # From Ethan Dicks (1996-10-06): # It keeps the same time as Punta Arenas, Chile, because, just like us # and the South Pole, that's the other end of their supply line.... # I verified with someone who was there that since 1980, # Palmer has followed Chile. Prior to that, before the Falklands War, # Palmer used to be supplied from Argentina. The rule ChileAQ in antarctica was copied from southamerica file and the current effective rules are below - Rule ChileAQ 1999 max - Oct Sun>=9 4:00u 1:00 S Rule ChileAQ 2000 max - Mar Sun>=9 3:00u 0 - However, Rule Chile in southamerica was updated in 2008a, 2010d, 2011c and 2011e. The rules for Chile after 1999 are defined as below in the current version. Rule Chile 1999 2010 - Oct Sun>=9 4:00u 1:00 S Rule Chile 2011 only - Aug Sun>=16 4:00u 1:00 S Rule Chile 2012 max - Oct Sun>=9 4:00u 1:00 S Rule Chile 2000 2007 - Mar Sun>=9 3:00u 0 - # N.B.: the end of March 29 in Chile is March 30 in Universal time, # which is used below in specifying the transition. Rule Chile 2008 only - Mar 30 3:00u 0 - Rule Chile 2009 only - Mar Sun>=9 3:00u 0 - Rule Chile 2010 only - Apr Sun>=1 3:00u 0 - Rule Chile 2011 only - May Sun>=2 3:00u 0 - Rule Chile 2012 max - Mar Sun>=9 3:00u 0 - If the comment for Antarctica/Palmer is still true, then I think ChileAQ in antarctica should be also updated. Does anyone know if ChileAQ in antarctica was intentionally unchanged or, it's just an error? Thanks, Yoshito

1 0

America/Creston
by Chris Walton Dec. 2, 2011

Dec. 2, 2011

There are two areas within the Canadian province of British Columbia that do not currently observe daylight saving: a) The Creston Valley (includes the town of Creston and surrounding area) b) The eastern half of the Peace River Regional District (includes the cities of Dawson Creek and Fort St. John) Creston does not have a dedicated zone file; it is assumed that residents of Creston should use "America/Dawson_Creek". This assumption can be inferred from a comment that is currently embedded in the tz database's northamerica file; the comment reads: "Matthews and Vincent (1998) write that Creston is like Dawson Creek.". Earlier this year I stumbled across a detailed article about the time keeping history of Creston; it was written by Tammy Hardwick who is the manager of the Creston & District Museum. The article was written in May 2009. http://www.ilovecreston.com/?p=articles&t=spec&ar=260 According to the article, Creston has not changed its clocks since June 1918. i.e. Creston has been stuck on UTC-7 for 93 years. Dawson Creek, on the other hand, changed its clocks as recently as April 1972 (as is correctly reflected in the current tz database). The current tz rules state that a separate zone file should be created for regions that differ after 1970. So... I am proposing the addition of "America/Creston" to the database. Unfortunately the exact date for the time change in June 1918 remains unknown and will be difficult to ascertain. I e-mailed Tammy a few months ago to ask if Sunday June 2 was a reasonable guess. She said it was just as plausible as any other date (in June). She also said that after writing the article she had discovered another time change in 1916; this is the subject of another article which she wrote in October 2010. http://www.creston.museum.bc.ca/index.php?module=comments&uop=view_comment&… Here is a summary of the three clock change events in Creston's history: 1. 1884 or 1885: adoption of Mountain Standard Time (GMT-7) # Exact date unknown 2. Oct 1916: switch to Pacific Standard Time (GMT-8) # Exact date in October unknown; Sunday October 1 is a reasonable guess. 3. June 1918: switch to Pacific Daylight Time (GMT-7) # Exact date in June unknown; Sunday June 2 is a reasonable guess. note#1: On Oct 27/1918 when daylight saving ended in the rest of Canada, Creston did not change its clocks. By not changing the clocks, Creston had effectively transitioned itself back to Mountain Standard Time. note#2: During WWII when the Federal Government legislated a mandatory clock change, Creston did not oblige. Creston was able to claim that it had moved itself back to the Pacific Time Zone and could observe daylight saving (Pacific War Time) without changing the clocks. After the war, Creston conveniently moved itself back to Mountain Standard Time, again with no change to the clocks. note#3: There is no guarantee that Creston will remain on Mountain Standard Time (UTC-7) forever. The subject was debated at least once this year by the town Council. http://www.bclocalnews.com/kootenay_rockies/crestonvalleyadvance/news/11676… Here is a proposed zone entry for the northamerica file: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Creston -7:46:04 - LMT 1884 -7:00 - MST 1916 Oct 1 -8:00 - PST 1918 Jun 2 -8:00 1:00 PDT 1918 Oct 27 2:00 -7:00 - MST 1942 Feb 9 2:00 -8:00 Canada P%sT 1945 Sep 30 2:00 -7:00 - MST Alternatively the dates in Oct 1916 and June 1918 could be omitted since we don't know what they are; this would cause zic to default to Oct 1/1916 and June 1/1918. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Creston -7:46:04 - LMT 1884 -7:00 - MST 1916 Oct -8:00 - PST 1918 Jun -8:00 1:00 PDT 1918 Oct 27 2:00 -7:00 - MST 1942 Feb 9 2:00 -8:00 Canada P%sT 1945 Sep 30 2:00 -7:00 - MST Note the use of the Canada rule in 1942 results in the use of "PWT(pacific war time)" and "PPT(pacific peace time)". The zone.tab entry should look like this: CA +4906-11631 America/Creston Mountain Standard Time - Creston, British Columbia # # # # # # And now one last tidbit: In the first of Tammy's articles she quotes the Friday November 1/1918 edition of the Creston Review. The quote includes these two statements: 'Sunday the CPR went back to the old system of time...' '... The daylight saving scheme was dropped all over Canada at the same time,' These statements refer to a transition from daylight time to standard time that occurred nationally on Sunday October 27/1918. This transition was also documented in the Saturday October 26/1918 edition of the Toronto Star. The Toronto Star articles reads as follows: 'BACK TO OLD TIME - Canada Returns to Orthodox Measurement of Time To-morrow Morning. Ottawa, Oct. 26.---"Daylight saving" comes to an end Sunday morning, October 27, at 2 o'clock, when Canada returns to the orthodox measurement of time. Either the simple ceremony of stopping the clock for an hour or sliding the hands forward 11 hours should be carried out. To turn the hands back would be to injure its mechanism.' My reason for providing these two references to the October 27/1918 transition, is that the tz database currently defines it as being on Thursday October 31 instead of Sunday November 27. This is an error that presumably needs to be corrected in the rules for "Canada", "Regina", "Vanc", "Winn", and "Edm". -chris

1 1

Fiji DST 2011/12 change (again)
by Ken Rylander Nov. 29, 2011

Nov. 29, 2011

Hi, Another change to the Fiji DST end date. In the TZ database the end date for Fiji DST 2012, is currently Feb 26. This has been changed to Jan 22. >From www.fiji.gov.fj:<http://www.fiji.gov.fj:> Amendments to daylight savings Ministry of Information Oct 17 |13:59 pm The end of daylight saving scheduled initially for the 26th of February 2012 has been brought forward to the 22nd of January 2012. The commencement of daylight saving will remain unchanged and start on the 23rd of October, 2011. An official gazette reflecting this change will be released early this week. -ends- http://www.fiji.gov.fj/index.php?option=com_content&view=article&id=5017:am… Please add to next tz update. Cheers, /Ken ________________________________ Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.

4 7

Reading binary files
by Thom Hehl Nov. 17, 2011

Nov. 17, 2011

OK, I give up. I've tried looking at the source code and it's hopeless. Can someone please explain to me how to read the binary files and turn it into timezone information? All I need to do is write a function that will take a UTC date and convert it into a timezone with a name that I specify and convert it back again. (I understand there are precision issues with the last one.) The code is not commented and I can find no documents. Please, I beg you, help me.

7 9

U.S. abbreviations in 1942
by Garrett Wollman Nov. 15, 2011

Nov. 15, 2011

The U.S. went on permanent DST for the duration of World War II starting on February 9, 1942. The following quotation from /Broadcasting/ magazine of 1942-02-02 sheds some more light on abbreviations used in the U.S. during the early 1940s: : At present, times for network programs are nationally released in : accordance with their broadcasts on the East Coast and are labelled : EST. In previous years, during the months that daylight saving time : was in effect in certain parts of the country, including New York, : the designation was changed to EDST for that period. : [... T]he MBS publicity department stated that it will follow the : custom of other years and label program times as EDST. NBC said : that [...] Red Netowrk programs would be shown as EST after Feb. 9. : [...] CBS has announced that "concurrent with national daylight : saving beginning Feb. 9, Columbia network's time designation on news : releaess is Eastern Time. This phrase was chosen because the time : is no longer standard and because, with national daylight saving, : EDST seems unessential." -GAWollman

1 0

Barnaby
by Thom Hehl Nov. 9, 2011

Nov. 9, 2011

OK, first pass of http://code.google.com/p/barnaby is available for download of the source. This is a C++ library with two functions: 1) List all of the timezones 2) For a given timezone name, convert UTC to that timezone It will build a DLL for you if you open the project using Visual C++. The timezone data is only version 2011i, so I will need to update it soon. Please let me know any and all feedback. Blessings!

5 7

FW: Barnaby
by Thom Hehl Nov. 8, 2011

Nov. 8, 2011

>You're using zone.tab as a canonical list of timezones, which it isn't. >zone.tab is only useful for selecting timezones via countries; for a >list of all timezones you can serve you should just look at the tzfiles. Did you read the readme? That is the next thing I'm going to fix. >Your usage of time_t is not appropriate. The type you want there is >dictated by the tzfile format, not by libc. The API needs to use time_t, so the usage is dictated by the use case, not by the tzfile, which is why it's appropriate. >You're doing a linear search (in transitionTimesIndex) that should really >be a binary search. Yeah, that can be optimized. The problem with doing a binary search is that you're not looking for an equal condition, but the smallest gap the thing you're looking for fits into. I'm aware that a binary search would improve performance some, but didn't devote time to it yet. Again, this is a beta drop designed to get the job done so I can move on with other priorities that pay money. :) >Overall it looks like you're interpreting (the 32-bit part of) the tzfile >correctly, but I find the code too messy to be sure. >You have some instance methods that should be class methods ("static"). >There is much else that is poor about your object model, but that's all >off topic for this list. Feel free to email me off list as you please for any improvements you might suggest. As I indicated in the read-me there is much room for improvement, but this meets my current needs. Open source is all about refining code over iterations, right? Whatever changes you'd like to suggest will be re-visited when I get some time to come back and work on this more. Thanks for the excellent feedback. -----Original Message----- From: Zefram [mailto:zefram@fysh.org] Sent: Tuesday, November 08, 2011 12:44 PM To: Thom Hehl Cc: tz(a)iana.org Subject: Re: [tz] Barnaby Thom Hehl wrote: >http://code.google.com/p/barnaby You're using zone.tab as a canonical list of timezones, which it isn't. zone.tab is only useful for selecting timezones via countries; for a list of all timezones you can serve you should just look at the tzfiles. Your usage of time_t is not appropriate. The type you want there is dictated by the tzfile format, not by libc. You're doing a linear search (in transitionTimesIndex) that should really be a binary search. Overall it looks like you're interpreting (the 32-bit part of) the tzfile correctly, but I find the code too messy to be sure. You have some instance methods that should be class methods ("static"). There is much else that is poor about your object model, but that's all off topic for this list. -zefram

1 0

Decoding timezone data
by Thom Hehl Nov. 8, 2011

Nov. 8, 2011

OK, so I'm making some progress on my library. I'm attempting to read the timezone information for America/Kentucky/Louisville. When I run through the values for transition times, I get 177 values such as follows: 2661690496, 2693140096, 2759063296, ... The docs say these transition times are in values returned by the c time function, which returns seconds since midnight, 1/1/1970. If that is the case, then the three values above convert to: May 6, 2054 at 2:28:16 PM May 5, 2055 at 2:28:16 PM June 6, 2057 at 2:28:16 PM These are nowhere near the DST conversion dates for these years and are moving forward. This appears incorrect. Can someone show me what I'm doing wrong? Thanks.

5 8

"Standard byte order"
by Thom Hehl Nov. 8, 2011

Nov. 8, 2011

I'm assuming that "Standard byte order" referred to over and over in the docs means Most Significant Byte first? It should really be documented that way. As far as I know, there is no standard byte order.

9 15

Re: [tz] Australian time zone abbreviations
by Shaun Bouckaert Nov. 8, 2011

Nov. 8, 2011

On 6 November 2011 20:51, Eric Ulevik <eulevik(a)gmail.com> wrote: > On Sun, Nov 6, 2011 at 9:20 PM, Shaun Bouckaert > <shaun.bouckaert(a)gmail.com> wrote: > [snip]> http://australia.gov.au/about-australia/our-country/time > [snip]> I believe that the abbreviations used on the federal > government> website should be used. > Time zones in Australia are legislated by acts of state governments, > not the federal government. The acts mostly refer to "summer time" and > "standard time". > > Eg. South Australia: > http://www.austlii.edu.au/au/legis/sa/consol_act/dsa1971165/ > > Regards, > > Eric Ulevik > In the absence of any specific mention in the state legislation of an appropriate abbreviation, and considering the timezones and their abbreviations span multiple states, I see no reason why federal government documentation on the matter shouldn't be recognised, especially considering the only basis for the current system is a couple of AltaVista searches and the opinion of Australian's on the list at the time. Shaun Bouckaert

4 5

Russian TZ Samara has no offset listed since 2010g
by manprsi2 Nov. 7, 2011

Nov. 7, 2011

Hello, Europe/Samara has the follow zone.tab definition since 2010g (no offset listed) RU +5312+05009 Europe/Samara Moscow - Samara, Udmurtia It used to be RU +5312+05009 Europe/Samara Moscow+01 - Samara, Udmurtia Samara changed to Moscow but all the other regions are listed with an offset even if +00 (Volgograd, Moscow) while Samara is not. I can not tell by searching the mail archive if the change this way was intentional or not? Thanks - Manpreet

2 2

Australian time zone abbreviations
by Shaun Bouckaert Nov. 6, 2011

Nov. 6, 2011

Having long been irked by the fact that the abbreviation for Brisbane is EST, as opposed to AEST, I read through the time zone data file and found that the reason for this was a discussion back in 2001. I'm not sure if this existed then, but there is a federal government web page that lists the time zones and their abbreviations. http://australia.gov.au/about-australia/our-country/time ================================================================================ Time zones With a land mass close to 7.7 million square kilometres, Australia is the world’s sixth largest country and is divided into three separate time zones. Australian Eastern Standard Time (AEST) Covers the eastern states of Queensland, New South Wales (with the exception of the town of Broken Hill), Victoria, Tasmania and the Australian Capital Territory. AEST is equal to Coordinated Universal Time plus 10 hours (UTC +10). Australian Central Standard Time (ACST) Covers the state of South Australia, the town of Broken Hill in western New South Wales and the Northern Territory. ACST is equal to Coordinated Universal Time plus 9 ½ hours (UTC +9 ½). Australian Western Standard Time (AWST) Covers Western Australia. AWST is equal to Coordinated Universal Time plus 8 hours (UTC +8). Daylight saving Daylight Saving Time (DST) is the practice of advancing clocks one hour during the warmer months of the year. In Australia, Daylight saving is observed in New South Wales, Victoria, South Australia, Tasmania, and the Australian Capital Territory. Daylight Saving Time begins at 2am (AEST) on the first Sunday in October and ends at 2am (AEST) (which is 3am Australian Eastern Daylight Time) on the first Sunday in April. Where Daylight saving is observed: NSW, ACT,Vic and Tas move from AEST to Australian Eastern Daylight Time (AEDT), and clocks are advanced to UTC +11. SA and the NSW town of Broken Hill move from ACST to Australian Central Daylight Time (ACDT), and clocks are advanced to UTC +10 ½. Daylight saving is not observed in Queensland, the Northern Territory or Western Australia. ================================================================================ I believe that the abbreviations used on the federal government website should be used. Shaun Bouckaert

3 3

leap seconds (srsly)
by Zefram Nov. 4, 2011

Nov. 4, 2011

In a couple of months, a decision is going to be made about possibly ceasing leap seconds in UTC. If that happens, the tz database is going to be thrown into a world of hurt, as "UTC = GMT" gradually ceases to be a viable approximation. Here are the slides from a talk presented a couple of months ago that provides a useful primer on how the decision would interact with civil and legal time: http://www.cacr.caltech.edu/futureofutc/program/presentations/AAS_11-662_Se… All the presentations from the conference where that was presented, discussing mary aspects of the decision, can be found here: http://www.cacr.caltech.edu/futureofutc/program/ (Information forwarded from the leapsecs mailing list.) -zefram

3 2

Leap seconds
by Thom Hehl Nov. 4, 2011

Nov. 4, 2011

The docs specify that the transition time is based on the return value from the time() function. Does that mean that the leap seconds are automatically adjusted based on that value and the transition time is correct or does that mean that it uses the actual time and I have to adjust first with leap seconds if I want an accurate conversion?

2 1

Thread-safe localtime(3) (was Re: Reading binary files)
by Bennett Todd Nov. 3, 2011

Nov. 3, 2011

Am I missing a fundamental, or would it be reasonable to not necessarily expose the data structure for the parsed conversion data, but instead offer explicit parse routine (returning an opaque blob) and convert routine that takes such a blob as a parameter? Then it should be easy to make tzset(3) utterly trivial -- call the zoninfo parser on getenv(TZ) with locking, and localtime(3) likewise trivial, call the real convert routine with the datastructure cached by the latest tzset.

10 17

Re: [tz] Reading binary files
by Thom Hehl Nov. 2, 2011

Nov. 2, 2011

Not if you are writing applications that need high performance processing of multiple timezones and access from multiple languages and platforms. Besides, we're multi-threaded. Changing environment variables is simply not an option. Yikes! Can you say race condition. From: bent(a)latency.net [mailto:bent@latency.net] On Behalf Of Bennett Todd Sent: Wednesday, November 02, 2011 9:09 AM To: Thom Hehl Subject: Re: [tz] Reading binary files The binary files are a distraction. What you want to do is set the environment variable TZ to the name of the zone you want, then call tzset which is what consults the database and prepares for conversion. Then localtime(3) will translate a time_t (seconds since the epoch) to hours, minutes, seconds, etc in the local timezone. For translating back and forth you repeatedly reset TZ, call tzset(3), and localtime(3). Those are the standards for Unix, the native home of the zoneinfo database. If you're on a different system details may vary. But on Unix the database is probably already installed in your system and the subroutines you need are already compiled into the system library.

6 6

tzdata2011n.tar.gz
by Robert Elz Nov. 2, 2011

Nov. 2, 2011

The file ftp://munnari.oz.au/pub/tzdata2011n.tar.gz ...is now available; this reflects changes circulated last week, and weekend, on the time zone mailing list, and summarised here. There are three changes of note - most urgently, Cuba (America/Havana) has extended summer time by two weeks, now to end on Nov 13, rather than the (already past) Oct 30. Second, the Pridnestrovian Moldavian Republic (Europe/Tiraspol) decided not to split from the rest of Moldova after all, and consequently that zone has been removed (again) and reinstated in the "backward" file as a link to Europe/Chisinau. And third, the end date for Fiji's summer time this summer was moved forward from the earlier planned Feb 26, to Jan 22. Apart from that, Moldova (MD) returns to a single entry in zone.tab (and the incorrect syntax that was in the 2011m version of that file is so fixed - it woudl have been fixed in a different way had this change not happened - that's the "missing" sccs version id). Once again, no signatures, but hash digests using several different algorithms are appended to this message so you can verify the file that you fetch. These were generated using the pkgtools/digest program from NetBSD's pkgsrc. kre MD5 (tzdata2011n.tar.gz) = 20dbfb28efa008ddbf6dd34601ea40fa RMD160 (tzdata2011n.tar.gz) = 4a2a06ada05aca1ea99767caa1b23c6fcb88bcd3 SHA1 (tzdata2011n.tar.gz) = 5435fae9844dc89f9d418aa956e161e23d1babdf SHA512 (tzdata2011n.tar.gz) = 2081fa44f00ace6539ecc1296f454fb96bb4afa61114ffbc58f46f82ef8ba2cfa22d7e48456a293502433dccca6d921db8f70d6c6e18a074996cfeb74534d2df TIGER (tzdata2011n.tar.gz) = 28b009b1e0e7126c2430270efd1aae89237be7c00b3ad2a5 WHIRLPOOL (tzdata2011n.tar.gz) = e7004894829c63baef91fd5fbc14b77a7fbd92ae2a6e001f279c8b1169bd5be009ae07af336ddaca148eadeba3383896b247a19c9e72d894e80ad60fc896f3f3

3 3

Query about update in timezone database
by Mangala Arjun Nov. 2, 2011

Nov. 2, 2011

Hi, I am new member to this mailing list. When an update for timezone database is present , will it be intimated in this mailing list ? Thanks and Regards Mangala Arjun

4 3

Rule Russia incorrect
by Konstantin Kivi Nov. 2, 2011

Nov. 2, 2011

Time Zone Data v. 2011m (Released 24 October 2011) file contains a line ---------------------------------------------------------------------------------- Rule Russia 1993 2010 - Mar lastSun 2:00s 1:00 S ---------------------------------------------------------------------------------- which I believe means that last change to summer time was in 2010. This is incorrect, because this (2011) year we actually have changed time on last Sunday of March (by moving clock forward) I believe that for historical purposes the rule must looks as follows ---------------------------------------------------------------------------------- Rule Russia 1993 2011 - Mar lastSun 2:00s 1:00 S ---------------------------------------------------------------------------------- On the other hand Rule --------------------------------------------------------------------------------------- Rule Russia 1996 2010 - Oct lastSun 2:00s 0 - ----------------------------------------------------------------------------------------- is correct, because Russia stopped using Daylight Savings Time switching because of a federal law "On calculation of time" signed by President Dmitry Medvedev on June 9, 2011 -- Sincerely yours, Konstantin Kivi <konst(a)sirena2000.ru> IT Director, Comtech-N JSC Moscow, Russia, +7-495-941-60-02

6 6

Re: [tz] Sydney, Australia (and other places) DST indication (or lack thereof)
by Willy＠willylorenzo.com Nov. 1, 2011

Nov. 1, 2011

I appreciate the info. Several of the links given in the Australasia file are broken, which, of course, makes it impossible to review the referenced source, but I can see that this is a muddled subject. The only suggestion I would make is that if the "S" in EST is referring to both "standard" and "summer", then the FORMAT should be EST/EST...and maybe a "# (S)tandard/(S)ummer" comment added. At the very least it clearly indicates the decision that's been made for daylight saving time representation. As to what it should be...I'll leave that to the Australians (oh wait...isn't that the problem to begin with?) ;) On Mon Oct 31 12:55:06 2011 "Bill Tiede" <billt(a)chaossoftware.com> wrote: > For WorldTimeServer.com at least, we used two government sources for our time zone abbreviations for Australia: > > 1. Australia.gov.au at http://australia.gov.au/about-australia/our-country/time > > 2. Australian Government Bureau of Meteorology at http://www.bom.gov.au/climate/averages/tables/daysavtm.shtml > > There has been plenty of discussion in the past about how official these abbreviations are or how widely accepted within Australia these are, so keep in mind I'm not trying to reopen debate or anything, just responding to the question about where we got the idea to call it what we have. > > Best Regards, > Bill Tiede > > www.ChaosSoftware.com; www.WorldTimeServer.com

2 1