February 2016 - tz - lists.iana.org

proposed time zone package changes (Samoa, Factory, et al.)
by Arthur David Olson Aug. 28, 2019

Aug. 28, 2019

Below find proposed time zone package changes; the executive summary: * Makefile Change LOCALTIME default from "Factory" to "GMT"; do not compile "factory" file (but keep it in the distribution). * Theory Remove reference to "Factory" zone. * australasia Change end of DST in Samoa in 2011 from 2011-04-03 0:00 to 2011-04-03 1:00 (thanks to Raymond Hughes for a reference). * localtime.c Initialize ttinfo structures filled by tzparse (thanks to Ravindra for reporting a valgrind warning). * zic.c Fix generation of POSIX strings for zones with rules using "weekday<=n" forms of dates (thanks to Lei Liu for finding the problem). Also, limit output for non-POSIX-specificable zones defined to follow the same rules every year. (Note that no zones of either of the above types appear in the distribution; these changes cater to add-on zones). If no problems are found, 2010n will appear on 2010-10-25. --ado diff -r -c old/Makefile new/Makefile *** old/Makefile Mon Sep 27 09:24:25 2010 --- new/Makefile Tue Oct 12 12:36:50 2010 *************** *** 1,5 **** # <pre> ! # @(#)Makefile 8.8 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. --- 1,5 ---- # <pre> ! # @(#)Makefile 8.9 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. *************** *** 12,18 **** # make zonenames # to get a list of the values you can use for LOCALTIME. ! LOCALTIME= Factory # If you want something other than Eastern United States time as a template # for handling POSIX-style time zone environment variables, --- 12,18 ---- # make zonenames # to get a list of the values you can use for LOCALTIME. ! LOCALTIME= GMT # If you want something other than Eastern United States time as a template # for handling POSIX-style time zone environment variables, *************** *** 262,269 **** DOCS= README Theory $(MANS) date.1 Makefile PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica ! YDATA= $(PRIMARY_YDATA) pacificnew etcetera factory backward ! NDATA= systemv SDATA= solar87 solar88 solar89 TDATA= $(YDATA) $(NDATA) $(SDATA) TABDATA= iso3166.tab zone.tab --- 262,269 ---- DOCS= README Theory $(MANS) date.1 Makefile PRIMARY_YDATA= africa antarctica asia australasia \ europe northamerica southamerica ! YDATA= $(PRIMARY_YDATA) pacificnew etcetera backward ! NDATA= systemv factory SDATA= solar87 solar88 solar89 TDATA= $(YDATA) $(NDATA) $(SDATA) TABDATA= iso3166.tab zone.tab diff -r -c old/Theory new/Theory *** old/Theory Mon Sep 27 09:24:25 2010 --- new/Theory Tue Oct 12 12:36:50 2010 *************** *** 1,4 **** ! @(#)Theory 8.4 This file is in the public domain, so clarified as of 2009-05-17 by Arthur David Olson. --- 1,4 ---- ! @(#)Theory 8.5 This file is in the public domain, so clarified as of 2009-05-17 by Arthur David Olson. *************** *** 287,294 **** See the file `backward' for most of these older names (e.g. `US/Eastern' instead of `America/New_York'). The other old-fashioned names still supported are ! `WET', `CET', `MET', `EET' (see the file `europe'), ! and `Factory' (see the file `factory'). ----- Time zone abbreviations ----- --- 287,293 ---- See the file `backward' for most of these older names (e.g. `US/Eastern' instead of `America/New_York'). The other old-fashioned names still supported are ! `WET', `CET', `MET', and `EET' (see the file `europe'). ----- Time zone abbreviations ----- diff -r -c old/australasia new/australasia *** old/australasia Mon Sep 27 09:24:27 2010 --- new/australasia Tue Oct 12 13:14:56 2010 *************** *** 1,5 **** # <pre> ! # @(#)australasia 8.18 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. --- 1,5 ---- # <pre> ! # @(#)australasia 8.19 # This file is in the public domain, so clarified as of # 2009-05-17 by Arthur David Olson. *************** *** 487,497 **** # http://www.parliament.gov.ws/documents/acts/Daylight%20Saving%20Act%20%2020… # </a> Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 -11:30 - SAMT 1950 # Samoa Time -11:00 - WST 2010 Sep 26 ! -11:00 1:00 WSDT 2011 Apr 3 -11:00 - WST # Solomon Is --- 487,507 ---- # http://www.parliament.gov.ws/documents/acts/Daylight%20Saving%20Act%20%2020… # </a> + # From Raymond Hughes (2010-10-07): + # Please see + # <a href="http://www.mcil.gov.ws"> + # http://www.mcil.gov.ws + # </a>, + # the Ministry of Commerce, Industry and Labour (sideframe) "Last Sunday + # September 2010 (26/09/10) - adjust clocks forward from 12:00 midnight + # to 01:00am and First Sunday April 2011 (03/04/11) - adjust clocks + # backwards from 1:00am to 12:00am" + Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 -11:30 - SAMT 1950 # Samoa Time -11:00 - WST 2010 Sep 26 ! -11:00 1:00 WSDT 2011 Apr 3 1:00 -11:00 - WST # Solomon Is diff -r -c old/localtime.c new/localtime.c *** old/localtime.c Mon Sep 27 09:24:26 2010 --- new/localtime.c Tue Oct 12 12:36:51 2010 *************** *** 5,11 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 8.14"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 5,11 ---- #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 8.15"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 914,919 **** --- 914,920 ---- register unsigned char * typep; register char * cp; register int load_result; + static struct ttinfo zttinfo; INITIALIZE(dstname); stdname = name; *************** *** 986,991 **** --- 987,993 ---- /* ** Two transitions per year, from EPOCH_YEAR forward. */ + sp->ttis[0] = sp->ttis[1] = zttinfo; sp->ttis[0].tt_gmtoff = -dstoffset; sp->ttis[0].tt_isdst = 1; sp->ttis[0].tt_abbrind = stdlen + 1; *************** *** 1099,1106 **** } /* ** Finally, fill in ttis. - ** ttisstd and ttisgmt need not be handled. */ sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = FALSE; sp->ttis[0].tt_abbrind = 0; --- 1101,1108 ---- } /* ** Finally, fill in ttis. */ + sp->ttis[0] = sp->ttis[1] = zttinfo; sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = FALSE; sp->ttis[0].tt_abbrind = 0; *************** *** 1113,1118 **** --- 1115,1121 ---- dstlen = 0; sp->typecnt = 1; /* only standard time */ sp->timecnt = 0; + sp->ttis[0] = zttinfo; sp->ttis[0].tt_gmtoff = -stdoffset; sp->ttis[0].tt_isdst = 0; sp->ttis[0].tt_abbrind = 0; diff -r -c old/zic.c new/zic.c *** old/zic.c Mon Sep 27 09:24:26 2010 --- new/zic.c Tue Oct 12 13:37:29 2010 *************** *** 3,9 **** ** 2006-07-17 by Arthur David Olson. */ ! static char elsieid[] = "@(#)zic.c 8.22"; #include "private.h" #include "locale.h" --- 3,9 ---- ** 2006-07-17 by Arthur David Olson. */ ! static char elsieid[] = "@(#)zic.c 8.24"; #include "private.h" #include "locale.h" *************** *** 1881,1896 **** register int week; if (rp->r_dycode == DC_DOWGEQ) { ! week = 1 + rp->r_dayofmonth / DAYSPERWEEK; ! if ((week - 1) * DAYSPERWEEK + 1 != rp->r_dayofmonth) return -1; } else if (rp->r_dycode == DC_DOWLEQ) { if (rp->r_dayofmonth == len_months[1][rp->r_month]) week = 5; else { ! week = 1 + rp->r_dayofmonth / DAYSPERWEEK; ! if (week * DAYSPERWEEK - 1 != rp->r_dayofmonth) return -1; } } else return -1; /* "cannot happen" */ (void) sprintf(result, "M%d.%d.%d", --- 1881,1896 ---- register int week; if (rp->r_dycode == DC_DOWGEQ) { ! if ((rp->r_dayofmonth % DAYSPERWEEK) != 1) return -1; + week = 1 + rp->r_dayofmonth / DAYSPERWEEK; } else if (rp->r_dycode == DC_DOWLEQ) { if (rp->r_dayofmonth == len_months[1][rp->r_month]) week = 5; else { ! if ((rp->r_dayofmonth % DAYSPERWEEK) != 0) return -1; + week = rp->r_dayofmonth / DAYSPERWEEK; } } else return -1; /* "cannot happen" */ (void) sprintf(result, "M%d.%d.%d", *************** *** 2018,2023 **** --- 2018,2024 ---- register char * envvar; register int max_abbr_len; register int max_envvar_len; + register int prodstic; /* all rules are min to max */ max_abbr_len = 2 + max_format_len + max_abbrvar_len; max_envvar_len = 2 * max_abbr_len + 5 * 9; *************** *** 2032,2037 **** --- 2033,2039 ---- timecnt = 0; typecnt = 0; charcnt = 0; + prodstic = zonecount == 1; /* ** Thanks to Earl Chew ** for noting the need to unconditionally initialize startttisstd. *************** *** 2053,2058 **** --- 2055,2062 ---- updateminmax(rp->r_loyear); if (rp->r_hiwasnum) updateminmax(rp->r_hiyear); + if (rp->r_lowasnum || rp->r_hiwasnum) + prodstic = FALSE; } } /* *************** *** 2075,2080 **** --- 2079,2094 ---- if (max_year <= INT_MAX - YEARSPERREPEAT) max_year += YEARSPERREPEAT; else max_year = INT_MAX; + /* + ** Regardless of any of the above, + ** for a "proDSTic" zone which specifies that its rules + ** always have and always will be in effect, + ** we only need one cycle to define the zone. + */ + if (prodstic) { + min_year = 1900; + max_year = min_year + YEARSPERREPEAT; + } } /* ** For the benefit of older systems,

5 6

Syntax highlighting for Sublime Text
by Gilmore Davidson Aug. 16, 2017

Aug. 16, 2017

Hi, I’ve created some tzdata syntax highlighting rules for the Sublime Text editor: https://packagecontrol.io/packages/zoneinfo <https://packagecontrol.io/packages/zoneinfo> I have no idea if anyone other than me uses that particular text editor for looking at tzdata files. But I thought I’d mention it just in case it’s useful to someone. Cheers, Gil

3 3

Re: [tz] Version in zoneinfo files?
by Guy Harris Feb. 10, 2017

Feb. 10, 2017

On Oct 25, 2015, at 10:55 AM, Paul G <paul(a)ganssle.io> wrote: > I'm not suggesting that it be impossible to create a weird result when asking for the version, just that there's a standard place for the version to go, and preferably the standard default gives you something that you expected. I.e., something that works most of the time is sufficient? So what exactly is the intended use of this version field? > As it is now, you're virtually guaranteed to have a lot of incompatibility because there's nothing you can point to that says, "This is the canonical way to store version information about zoneinfo files", and no standard has emerged on how to do this as is. > > On 10/25/2015 01:51 PM, Guy Harris wrote: >> >> On Oct 25, 2015, at 10:37 AM, Paul G <paul(a)ganssle.io> wrote: >> >>> On 10/25/2015 01:35 PM, Guy Harris wrote: >>> >>>> So where would zic get the version information to put into the binary files? >>> >>> My understanding is that it's the VERSION= line of the Makefile in the tzdata tarballs. >> >> I.e., you're proposing that the value of the VERSION value in the Makefile be passed as an argument to zic, and zic would put the value of that argument into a field in the files? >> >> So, if the goal is to provide a "reliable way to get the version information in a cross-platform way", what would ensure that this field be set properly, for some value of "properly", everywhere that binary tzdata files are generated? >> >> I.e., what is to guarantee that >> >> 1) nobody downstream change VERSION if they aren't changing the zic files from what's distributed >> >> and >> >> 2) people change it "properly" if the files don't correspond to a particular version of files that were distributed (e.g., if some downstream supplier takes 2015q and adds some changes mentioned on the list to it before 2015r comes out with those changes plus other changes, they should call the resulting files something other than "2015q" or "2015r")? >> >

20 55

Proposal: validation text file with releases
by Jon Skeet Dec. 19, 2016

Dec. 19, 2016

Background: I'm the primary developer for Noda Time <http://nodatime.org> which consumes the tz data. I'm currently refactoring the code to do this... and I've come across some code (originally ported from Joda Time) which I now understand in terms of what it's doing, but not exactly why. For a little while now, the Noda Time source repo has included a text dump file <https://github.com/nodatime/nodatime/blob/master/src/NodaTime.Test/TestData…>, containing a text dump of every transition (up to 2100, at the moment) for every time zone. It looks like this, picking just one example: Zone: Africa/Maseru LMT: [StartOfTime, 1892-02-07T22:08:00Z) +01:52 (+00) SAST: [1892-02-07T22:08:00Z, 1903-02-28T22:30:00Z) +01:30 (+00) SAST: [1903-02-28T22:30:00Z, 1942-09-20T00:00:00Z) +02 (+00) SAST: [1942-09-20T00:00:00Z, 1943-03-20T23:00:00Z) +03 (+01) SAST: [1943-03-20T23:00:00Z, 1943-09-19T00:00:00Z) +02 (+00) SAST: [1943-09-19T00:00:00Z, 1944-03-18T23:00:00Z) +03 (+01) SAST: [1944-03-18T23:00:00Z, EndOfTime) +02 (+00) I use this file for confidence when refactoring my time zone handling code - if the new code comes up with the same set of transitions as the old code, it's probably okay. (This is just one line of defence, of course - there are unit tests, though not as many as I'd like.) It strikes me that having a similar file (I'm not wedded to the format, but it should have all the same information, one way or another) released alongside the main data files would be really handy for *all* implementors - it would be a good way of validating consistency across multiple platforms, with the release data being canonical. For any platforms which didn't want to actually consume the rules as rules, but just wanted a list of transitions, it could even effectively replace their use of the data. One other benefit: diffing the dump between two releases would make it clear what had changed in *effect*, rather than just in terms of rules. One sticking point is size. The current file for Noda Time is about 4MB, although it zips down to about 300K. Some thoughts around this: - We wouldn't need to distribute it in the same file as the data - just as we have data and code file, there could be a "textdump" file or whatever we'd want to call it. These could be retroactively generated for previous releases, too. - As you can see, there's redundancy in the format above, in that it's a list of "zone intervals" (as I call them in Noda Time) rather than a list of transitions - the end of each interval is always the start of the next interval. - For zones which settle into an infinite daylight saving pattern, I currently generate from the start of time to 2100 (and then a single zone interval for the end of time as Noda Time understands it; we'd need to work out what form that would take, if any). If we decided that "year of release + 30 years" was enough, that would cut down the size considerably. Any thoughts? If the feeling is broadly positive, the next step would be to nail down the text format, then find a willing victim/volunteer to write the C code. (You really don't want me writing C...) Jon

18 92

[PATCH 0/5] Standardize zone table comments format
by J William Piggott March 10, 2016

March 10, 2016

Not having a standard format for zone table comments is creating ambiguity. For example: 1 Thule / Pituffik 2 Pohnpei (Ponape) 3 Nova Scotia (peninsula) 4 peninsular Malaysia 5 Eastern Time - Pangnirtung, Nunavut 6 Central Time - Campeche, Yucatán 1 and 2 are different formats for alternate names/spellings. 3 shows a sub-region, but uses the same format as the previous alternate name. 4 places the sub-region before the region, where 3 has it after and uses a different format. 5 and 6 use the same format, but 5 defines a single sub-region while 6 defines two regions. These ambiguities make it impossible to interpret the comments without having prior knowledge of the area. This patch set is an effort to standardize the column 4 comments format as follows: A dash (-) is consistently used to delimit a zone_id prefix, so that was retained. A comma (,) is consistently used to delimit regions, so that was retained. Using a slash (/) to delimit alternate names/spellings is accepted English grammar, so that was chosen. Placing sub-regions after regions facilitates having list items begin in uppercase (which is both aesthetically pleasing and grammatically correct) and improves the usability of a sorted list; so that was chosen. Delimiting sub-regions with with curved braces () is in current practice, so that was chosen. Finally two letter codes for regions/sub-regions are included at the end of the sub-region(s) within the curved braces. Multiple regions grouped with the same sub-region(s) are delimited with a comma between the final region of the group and the sub-region(s). Region sub-region groups are delimited from other regions with a semicolon. At least one zone_id or region must be given. When adding a foreign country code to a zone_id on border locations, add it after the zone_id to accommodate implementations that sort the list. This will group zone_id's together, for example: Mountain Time - Chihuahua (away from US border) Mountain Time US - Chihuahua (near US border) Use full words in favor of abbreviations. This format can be represent as: [zone_id] [-] [region[(sub_region, ... [2_letter_code, ... ])][,|;] ... ] There currently are no zone table comments that model the full specification, so here is an imaginary example of the full spec: Central Scooter Time - Yamaha (YZ); Harley, Davidson, Sprint, (west coast XL, XR, FL, ST); Honda (most locations CB, CR), Suzuki, Kawasaki, Vespa The following changes since commit 99b658c3a129dfd0cb777337575e200656b8ff9d: * NEWS, Theory: Clear up descriptions of tzdata abbreviations. (2016-02-14 12:36:54 -0800) are available in the git repository at: git@github.com:jwpi/tz.git zonetab0215 for you to fetch changes up to cf921321194419bc88104da5d7a3a7cfac0ca47e: Standardize zone table comment format (2016-02-20 11:30:20 -0500) ---------------------------------------------------------------- J William Piggott (5): Holiday Islands does not exist. North of Scoresbysund is named National Park Durango is not a border state Use proper names for Baja California States Standardize zone table comment format australasia | 8 +++ europe | 8 +++ northamerica | 6 +- zone.tab | 240 +++++++++++++++++++++++++++++++-------------------------------- zone1970.tab | 250 +++++++++++++++++++++++++++++++++--------------------------------- 5 files changed, 264 insertions(+), 248 deletions(-) --- 8< Example zone1970.tab comments using the standardized format: Adelaide Island (Rothera Station) Anvers Island (Palmer Station) Holme Bay (Mawson Station) Vestfold Hills (Davis Station) Bailey Peninsula (Casey Station) Lake Vostok (Vostok Station) Adélie Land (Dumont-d'Urville Station) East Ongul Island (Syowa Station) Queen Maud Land (Troll Station) Buenos Aires (BA, CF) Argentina (most locations CB, CC, CN, ER, FM, MN, SE, SF) Salta (SA, LP, NQ, RN) Jujuy (JY) Tucumán (TM) Catamarca (CT), Chubut (CH) La Rioja (LR) San Juan (SJ) Mendoza (MZ) San Luis (SL) Santa Cruz (SC) Tierra del Fuego (TF) Samoa, Midway Lord Howe Island Macquarie Island Tasmania (most locations) Tasmania (King Island) Victoria New South Wales (most locations) New South Wales (Yancowinna) Queensland (most locations) Queensland (Whitsunday Islands) South Australia Northern Territory Western Australia (most locations) Western Australia (Eucla) Atlantic islands Pará (east), Amapá Northeast Brazil (MA, PI, CE, RN, PB) Pernambuco Tocantins Alagoas, Sergipe Bahia South Brazil, Southeast Brazil, (GO, DF, MG, ES, RJ, SP, PR, SC, RS) Mato Grosso do Sul Mato Grosso Pará (west) Rondônia Roraima Amazonas (east) Amazonas (west) Acre Newfoundland, Labrador (southeast) Atlantic Time - Nova Scotia (peninsula), Prince Edward Island Atlantic Time - Nova Scotia (Cape Breton) Atlantic Time - New Brunswick Atlantic Time - Labrador (most locations) Atlantic Standard Time - Quebec (Lower North Shore) Eastern Time - Ontario, Quebec, (most locations) Eastern Time - Ontario, Quebec, (places that did not observe DST 1967-1973) Eastern Time - Ontario (Thunder Bay) Eastern Time - Nunavut (most eastern locations) Eastern Time - Nunavut (Pangnirtung) Central Time - Nunavut (Resolute) Eastern Standard Time - Ontario (Atikokan), Nunavut (Southampton Island) Central Time - Nunavut (central) Central Time - Ontario (west), Manitoba Central Time - Ontario (Rainy River, Fort Frances) Central Standard Time - Saskatchewan (most locations) Central Standard Time - Saskatchewan (midwest) Mountain Time - Alberta, British Columbia (east), Saskatchewan (west) Mountain Time - Nunavut (west) Mountain Time - Northwest Territories (central) Mountain Time - Northwest Territories (west) Mountain Standard Time - British Columbia (Creston) Mountain Standard Time - British Columbia (Dawson Creek, Fort Saint John) Mountain Standard Time - British Columbia (Fort Nelson) Pacific Time - British Columbia (west) Pacific Time - Yukon (south) Pacific Time - Yukon (north) Swiss Time Chile (most locations) Easter Island Beijing Time Xinjiang Time Germany (most locations) Ecuador (mainland) Galápagos Islands Spain (mainland) Ceuta, Melilla Canary Islands Chuuk/Truk, Yap Pohnpei/Ponape Kosrae Greenland (most locations) National Park (east coast) Scoresbysund/Ittoqqortoormiit Thule/Pituffik Java, Sumatra Borneo (west, central) Borneo (east, south), Sulawesi (Celebes), Bali, Nusa Tengarra, Timor (west) New Guinea (West Papua / Irian Jaya), Maluku/Moluccas Gilbert Islands Phoenix Islands Line Islands Kazakhstan (most locations) Qyzylorda/Kyzylorda/Kzyl-Orda Aqtobe/Aktobe Atyrau/Atirau/Gur'yev, Mangghystau/Mankistau West Kazakhstan Marshall Islands (most locations) Kwajalein Mongolia (most locations) Bayan-Ölgii, Govi-Altai, Hovd, Uvs, Zavkhan Dornod, Sükhbaatar Central Time Eastern Standard Time - Quintana Roo Central Time - Campeche, Yucatán Central Time - Durango; Coahuila, Nuevo León, Tamaulipas, (away from US border) Central Time US - Coahuila, Nuevo León, Tamaulipas, (near US border) Mountain Time - Baja California Sur, Nayarit, Sinaloa Mountain Time - Chihuahua (away from US border) Mountain Time US - Chihuahua (near US border) Mountain Standard Time - Sonora Pacific Time US - Baja California Central Time - Bahía de Banderas Malaysia (peninsula) Sabah, Sarawak UTC+2 - Central Africa Time UTC+1 - West Africa Time New Zealand Time Chatham Islands Society Islands Marquesas Islands Gambier Islands Papua New Guinea (most locations) Bougainville Gaza Strip West Bank Portugal (mainland) Madeira Islands Azores Réunion Island, Crozet Islands, Scattered Islands Moscow-01 - Kaliningrad Moscow+00 - Russia (west) Moscow+00 - Crimea Moscow+00 - Caspian Sea Moscow+01 - Samara, Udmurtia Moscow+02 - Urals Moscow+03 - Siberia (west) Moscow+03 - Novosibirsk Moscow+04 - Kemerovo Moscow+04 - Yenisei River Moscow+05 - Lake Baikal Moscow+05 - Zabaykalsky Moscow+06 - Lena River Moscow+06 - Tomponsky, Ust-Maysky Moscow+07 - Amur River Moscow+07 - Sakhalin Island Moscow+07 - Oymyakonsky Moscow+07 - Magadan Moscow+08 - Sakha (east), North Kuril Islands Moscow+09 - Kamchatka Moscow+09 - Bering Sea Kerguelen, St Paul Island, Amsterdam Island Indochina (most locations) Ukraine (most locations) Ruthenia Zaporozh'ye/Zaporizhia, Lugansk/Luhansk (east) Wake Island Eastern Time Eastern Time - Michigan (most locations) Eastern Time - Kentucky (Louisville area) Eastern Time - Kentucky (Wayne) Eastern Time - Indiana (most locations) Eastern Time - Indiana (Daviess, Dubois, Knox, Martin) Eastern Time - Indiana (Pulaski) Eastern Time - Indiana (Crawford) Eastern Time - Indiana (Pike) Eastern Time - Indiana (Switzerland) Central Time Central Time - Indiana (Perry) Central Time - Indiana (Starke) Central Time - Michigan (Dickinson, Gogebic, Iron, Menominee) Central Time - North Dakota (Oliver) Central Time - North Dakota (Morton except Mandan area) Central Time - North Dakota (Mercer) Mountain Time Mountain Time - Idaho (south), Oregon (east) Mountain Standard Time - Arizona (except Navajo) Pacific Time Alaska Time Alaska Time - Alaska Panhandle Alaska Time - Alaska Panhandle (southeast) Alaska Time - Annette Island Alaska Time - Alaska Panhandle (neck) Alaska Time - Alaska (west) Aleutian Islands Hawaii Time Uzbekistan (west) Uzbekistan (east) Vietnam (south)

8 49

zic changes (2/2)
by Arthur David Olson March 9, 2016

March 9, 2016

And now, the update. These changes arrange things so that binary files include "transition" entries for minimum time values; these entries eliminate localtime guesswork in handling low-valued time stamps. The bad news: binary files grow slightly as a result of these changes. The good news: there are no changes in the output of "zdump -v" applied to before-and-after versions of all the binary files generated by a "make install." Changes are attached and appear in mangled form below; these are relative to the github version of zic.c after the rollback in the earlier message today. @dashdashado 1.2 2805 lines 1.4 2813 lines *** /tmp/,azic.c 2014-05-01 01:51:36.998933800 -0400 --- /tmp/,bzic.c 2014-05-01 01:51:37.092534000 -0400 *************** *** 1480,1493 **** fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; - if (isdsts[0] == 0) - while (fromi < timecnt && attypes[fromi].type == 0) - ++fromi; /* handled by default rule */ for ( ; fromi < timecnt; ++fromi) { ! if (toi != 0 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + gmtoffs[toi == 1 ? 0 ! : attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; --- 1480,1490 ---- fromi = 0; while (fromi < timecnt && attypes[fromi].at < min_time) ++fromi; for ( ; fromi < timecnt; ++fromi) { ! if (toi > 1 && ((attypes[fromi].at + gmtoffs[attypes[toi - 1].type]) <= ! (attypes[toi - 1].at + ! gmtoffs[attypes[toi - 2].type]))) { attypes[toi - 1].type = attypes[fromi].type; continue; *************** *** 1532,1537 **** --- 1529,1541 ---- --timecnt32; ++timei32; } + /* + ** Output an INT32_MIN "transition" if appropriate--see below. + */ + if (timei32 > 0 && ats[timei32] > INT32_MIN) { + --timei32; + ++timecnt32; + } while (leapcnt32 > 0 && !is32(trans[leapcnt32 - 1])) --leapcnt32; while (leapcnt32 > 0 && !is32(trans[leapi32])) { *************** *** 1698,1704 **** #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! puttzcode(ats[i], fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; --- 1702,1713 ---- #undef DO for (i = thistimei; i < thistimelim; ++i) if (pass == 1) ! /* ! ** Output an INT32_MIN "transition" ! ** if appropriate--see above. ! */ ! puttzcode(((ats[i] < INT32_MIN) ? ! INT32_MIN : ats[i]), fp); else puttzcode64(ats[i], fp); for (i = thistimei; i < thistimelim; ++i) { unsigned char uc; *************** *** 2176,2183 **** if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else if (stdoff != 0) ! addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break; --- 2185,2191 ---- if (usestart) { addtt(starttime, type); usestart = FALSE; ! } else addtt(min_time, type); } else for (year = min_year; year <= max_year; ++year) { if (useuntil && year > zp->z_untilrule.r_hiyear) break;

7 22

[PATCH] Broken link: Website has disappeared
by Sanjeev Feb. 29, 2016

Feb. 29, 2016

* tz-link.htm --- tz-link.htm | 3 --- 1 file changed, 3 deletions(-) diff --git a/tz-link.htm b/tz-link.htm index bd92f64..c519669 100644 --- a/tz-link.htm +++ b/tz-link.htm @@ -200,9 +200,6 @@ time zone converter.</li> <li><a href="http://twiki.org/cgi-bin/xtra/tzdatepick.html">Date and Time Gateway</a> lets you see the <code><abbr>TZ</abbr></code> values directly.</li> -<li><a -href="http://convertit.com/Go/ConvertIt/World_Time/Current_Time.ASP">Current -Time in 1000 Places</a> uses descriptions of the values.</li> <li><a href="http://www.timezoneconverter.com/cgi-bin/tzc.tzc">Time Zone Converter</a> uses a pulldown menu.</li> -- 2.7.0

3 2

2015g: Is the 1:00 under Pacific/Norfolk "Rules" a typo?
by Marvel, Jim (CPCOE) Feb. 29, 2016

Feb. 29, 2016

Hello, Is the 1:00 under Pacific/Norfolk "Rules" a typo? # Norfolk # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Norfolk 11:11:52 - LMT 1901 # Kingston 11:12 - NMT 1951 # Norfolk Mean Time 11:30 - NFT 1974 Oct 27 02:00 # Norfolk T. 11:30 1:00 NFST 1975 Mar 2 02:00 11:30 - NFT 2015 Oct 4 02:00 11:00 - NFT thanks Jim Marvel

5 5

[PROPOSED PATCH] * NEWS: × → x, to pacify ‘make check_character_set’.
by Paul Eggert Feb. 28, 2016

Feb. 28, 2016

--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index f3499d7..e4dc2b5 100644 --- a/NEWS +++ b/NEWS @@ -31,7 +31,7 @@ Unreleased, experimental changes Comments in zone tables have been improved. (Thanks to J William Piggott.) tzselect again limits its menu comments so that menus fit on a - 24×80 alphanumeric display. + 24x80 alphanumeric display. In the Theory file, the description of possible time zone abbreviations in tzdata has been cleaned up, as the old description was unclear and -- 2.5.0

1 0

[PATCH] Allow use of <direct.h> from Microsoft Windows to fix mkdir() parameters
by Ian Abbott Feb. 28, 2016

Feb. 28, 2016

This is an alternative to a patch by Esben Haabendal, titled "Fix MinGW builds by adding MKDIR_TAKES_ONE_ARG", posted on Feb 23. Esben's patch made "private.h" optionally include <sys/stat.h> to get at Microsoft's mkdir function, but I think that only works in MinGW, and relies on MinGW's <io.h> header (included by <sys/stat.h>) optionally declaring the mkdir function. The mkdir function is also deprecated by Microsoft. New code should call _mkdir instead. Both functions only take a single parameter. This patch makes "private.h" optionally include <direct.h> (and also <io.h>, due to MinGW's behavior), controlled by the HAVE_DIRECT_H macro, and defines mkdir(path, mode) as macro calling _mkdir(path). With this patch, tz builds successfully in a MSYS2 MingW-w64 Win32 or Win64 environment using the following command line: make CFLAGS="-DHAVE_SYS_WAIT_H=0 -DHAVE_DIRECT_H=1 -DHAVE_LINK=0 -DHAVE_SYMLINK=0 -DHAVE_LOCALTIME_R=0" There are some warnings about 'tzname' being redeclared without dllimport attribute, when compiling zdump.c and localtime.c, but the resulting zdump executable seems to work. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti(a)mev.co.uk> )=- -=( Web: http://www.mev.co.uk/ )=-

2 7