- tz - lists.iana.org

ISO 8601:1986 revision has started!
by kuhn＠cs.purdue.edu July 7, 1997

July 7, 1997

I just got an interesting reply from Mr. Louis Visser <Louis.Visser(a)nni.nl> on my question whether there is any work going on to revise ISO 8601 soon: ISO TC 154 decided in 1996 to revise ISO 8601. Four member bodies responded to the calls for participation in the WG preparing the revision: Sweden, Austria, Yugoslavia and the Netherlands. I am coordinating the work of the WG. A first proposal for the revision has been prepared late 1996; a second proposal is expected in a month time. Please take your copy of ISO 8601 and think about what you would like to see changed in the next revision of ISO 8601. Some topics I could think of that might be addressed in a revision are: - the "ugly T" (allow a space alternatively) - profiles for easy reference in other standards (which ones?) - BNF syntax description - replace many of the ---DD style notations by shorter ones - allow second 60 (leap second) - decimal fraction of a day (1997-100.5 is noon) - third sunday of February 1997 as 1997-02-3-7 ??? - years < 0001 and > 9999 (suggestions?) - add (modified) julian date notation - calendar indicator? - time zone rule descriptors? - sliding window interpretation of YY (Y2K)? - ... [I don't think each of them is a good idea, this list is just intended as a brain storming trigger to keep you thinking about alternatives.] May be, I'll start a Web page collecting ideas for improving ISO 8601. I hope, I can organize a copy of the existing revision proposal and make it somehow available online. I'd love to hear about any suggestions that you might have! Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

1 0

Hong Kong
by Garrett Wollman June 30, 1997

June 30, 1997

Someone on the NTP newsgroup pointed out that China uses a single time zone for the entire country. Does anyone out there on this list know whether Hong Kong will be allowed to keep its current timezone after the takeover? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman(a)lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick

1 0

ISO 8601 and the horrible "T"
by Misha Wolf June 27, 1997

June 27, 1997

Stu Weibel has given me permission to quote from his private mail: > Where you have YYYY-MM-DDThh:mm-hh:mm, is it possible to interpose a > seperator other than T that makes it clearer to the human eye where > the date ends and Time begins? I suspect the answer to this is that > such a separator would knock the profile out of whack with 8601, but > I thought I'd ask anyhow. The "T" is, I think, the most despised aspect of the ISO 8601 standard but I think we're stuck with it. Some relevant quotes from the standard: [T] is used as a time designator to indicate the start of the representation of the time of day in combined date and time of day expressions; The space character shall not be used in the representations. The only suggestion I have seen for getting rid of the "T" is a kind of trick: We say that we are representing not a "combined date and time" but rather a separate date and a time. We then place them next to each other, separated by our favourite character. If "*" represents our favourite character, we get: 1994-11-05*08:15:30-05:00 instead of: 1994-11-05T08:15:30-05:00 The problem with this solution is precisely that it is a trick. In reality, we are dealing with a single date-with-time and it confuses things to pretend that we're not. Also, there must be lots of software out there which is ISO 8601-conformant and would choke on our favourite character. I suggest we decide that this stuff isn't primarily for human consumption and make use of it, warts and all. ------------------------------------------------------------------------ Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

2 1

Atlantic Monthly coverage of 2000/2001
by ado June 26, 1997

June 26, 1997

See http://www.theatlantic.com/issues/97jul/preview.htm for a very brief blurb on the magazine's article entitled "Zero" regarding when the millenium comes; see the magazine itself for details. Your correspondent was disappointed that there was no replay of the joke from Saul Bass's film "Why Man Creates:" First cartoon charcter: I've discovered the zero. Second cartoon character: What? First cartoon character: Nothing, nothing. --ado

1 0

Re: Draft profile of ISO 8601
by Misha Wolf June 26, 1997

June 26, 1997

Pete Ciuffetti has given me permission to quote his private mail: > In your levels of granularity, what do you think about allowing year-only, > "YYYY" and year-month "YYYY-MM". This would help solve a need I perceive > in our database design at SilverPlatter. Most of our records are > bibliographic and they specify the date of publication for some described > item like a book or journal. Typically this is just a year, like "1997" or > it is a year and month, "Feb 1997", sometimes a day is specified. > > In my metadata, I'd like to store whatever granularity that makes sense for > the published item and I would like all the dates to conform to a standard. > But no standard seems to consider these broader levels of granularity. ISO 8601 does. I would be very happy to add these options to the profile. > Also, in these broad levels for comparison purposes, I suggest implied > values would be 01 for an unspecified month, and 01 for an unspecified day. For the moment, I have backed away from suggesting how dates of differing granularities be compared, as it is contentious. > Regards, > Pete Ciuffetti > SilverPlatter ------------------------------------------------------------------------ Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

Profile of ISO 8601 (draft) - RESEND
by Misha Wolf June 26, 1997

June 26, 1997

Please accept my apologies if you have seen this message. I originally sent it over 24 hours ago but have not seen it reflected back. As I don't know where the problem lies, I've decided to resend the message. ------------------------------------------------------------------------ Introduction ============ This note defines a profile of [ISO 8601], the International Standard for the representation of dates and times. A discussion of [ISO 8601] is available at [KUHN]. [ISO 8601] describes a large number of date/time formats. To reduce the scope for error and the complexity of software, it is useful to restrict the supported formats to a small number. This profile defines a few date/time formats, likely to satisfy most requirements. The profile may be adopted by standards which require an unambiguous representation of dates and times. As different standards have their own requirements regarding granularity and flexibility, this profile offers a number of options. An adopting standard must specify which of these options it permits. Summary ======= This profile of [ISO 8601] defines four levels of granularity: 1. Date only 2. Date plus hours and minutes 3. Date plus hours, minutes and seconds 4. Date plus hours, minutes, seconds and decimal fractions of a second An adopting standard must permit one or more of these options. This profile defines two ways of handling time zone offsets: 1. Times are expressed in UTC, with a special UTC designator ("Z"). 2. Times are expressed in local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes behind UTC. An adopting standard must permit one or both of these options, unless the standard does not permit granularity options 2, 3 and 4. This profile does not specify how many digits may be used to represent the decimal fraction of a second. An adopting standard must specify both the minimum number of digits (a number greater than or equal to one) and the maximum number of digits (the maximum may be stated to be "unlimited"), unless the standard does not permit granularity option 4. The formats =========== 1. Date only ------------- The format is: YYYY-MM-DD Example: 1994-11-05 This example corresponds to November 5, 1994. 2. Date plus hours and minutes ------------------------------- If times are expressed in UTC, the format is: YYYY-MM-DDThh:mmZ Example: 1994-11-05T13:15Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm+hh:mm or: YYYY-MM-DDThh:mm-hh:mm Example: 1994-11-05T08:15-05:00 Both the examples in this section correspond to November 5, 1994, 8:15 am, US Eastern Standard Time. 3. Date plus hours, minutes and seconds ---------------------------------------- If times are expressed in UTC, the format is: YYYY-MM-DDThh:mm:ssZ Example: 1994-11-05T13:15:30Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm:ss+hh:mm or: YYYY-MM-DDThh:mm:ss-hh:mm Example: 1994-11-05T08:15:30-05:00 Both the examples in this section correspond to November 5, 1994, 8:15:30 am, US Eastern Standard Time. 4. Date plus hours, minutes, seconds and decimal fractions of a second ----------------------------------------------------------------------- The number of seconds is followed by a dot and one or more digits representing a decimal fraction of a second. An adopting standard must specify both the minimum and the maximum number of digits, as described earlier. If times are expressed in UTC, the format is: YYYY-MM-DDThh:mm:ss.sZ Example: 1994-11-05T13:15:30.45Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm:ss.s+hh:mm or: YYYY-MM-DDThh:mm:ss.s-hh:mm Example: 1994-11-05T08:15:30.45-05:00 Both the examples in this section correspond to November 5, 1994, 8:15:30.45 am, US Eastern Standard Time. References ========== [ISO 8601] "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO 8601:1988(E), International Organization for Standardization, June, 1988. [KUHN] "A Summary of the International Standard Date and Time Notation", Markus Kuhn, <http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html>, 1996-11-05. [NEWMAN] "Date and Time on the Internet", Chris Newman, <draft-newman-datetime-01.txt>, January 1997. ------------------------------------------------------------------------ Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

RE: Draft profile of ISO 8601
by Olson, Arthur David June 26, 1997

June 26, 1997

> Treatment of missing elements: > In some cases, software components may need to compare a date/time using > coarser granularity with one using finer granularity. [One option:] The missing > portions are deemed to be equal to zero. This is the approach now taken in the time zone information files. --ado

1 0

Profile of ISO 8601 (draft)
by Misha Wolf June 25, 1997

June 25, 1997

Introduction ============ This note defines a profile of [ISO 8601], the International Standard for the representation of dates and times. A discussion of [ISO 8601] is available at [KUHN]. [ISO 8601] describes a large number of date/time formats. To reduce the scope for error and the complexity of software, it is useful to restrict the supported formats to a small number. This profile defines a few date/time formats, likely to satisfy most requirements. The profile may be adopted by standards which require an unambiguous representation of dates and times. As different standards have their own requirements regarding granularity and flexibility, this profile offers a number of options. An adopting standard must specify which of these options it permits. Summary ======= This profile of [ISO 8601] defines four levels of granularity: 1. Date only 2. Date plus hours and minutes 3. Date plus hours, minutes and seconds 4. Date plus hours, minutes, seconds and decimal fractions of a second An adopting standard must permit one or more of these options. This profile defines two ways of handling time zone offsets: 1. Times are expressed in UTC, with a special UTC designator ("Z"). 2. Times are expressed in local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes behind UTC. An adopting standard must permit one or both of these options, unless the standard does not permit granularity options 2, 3 and 4. This profile does not specify how many digits may be used to represent the decimal fraction of a second. An adopting standard must specify both the minimum number of digits (a number greater than or equal to one) and the maximum number of digits (the maximum may be stated to be "unlimited"), unless the standard does not permit granularity option 4. The formats =========== 1. Date only ------------- The format is: YYYY-MM-DD Example: 1994-11-05 This example corresponds to November 5, 1994. 2. Date plus hours and minutes ------------------------------- If times are expressed in UTC, the format is: YYYY-MM-DDThh:mmZ Example: 1994-11-05T13:15Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm+hh:mm or: YYYY-MM-DDThh:mm-hh:mm Example: 1994-11-05T08:15-05:00 Both the examples in this section correspond to November 5, 1994, 8:15 am, US Eastern Standard Time. 3. Date plus hours, minutes and seconds ---------------------------------------- If times are expressed in UTC, the format is: YYYY-MM-DDThh:mm:ssZ Example: 1994-11-05T13:15:30Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm:ss+hh:mm or: YYYY-MM-DDThh:mm:ss-hh:mm Example: 1994-11-05T08:15:30-05:00 Both the examples in this section correspond to November 5, 1994, 8:15:30 am, US Eastern Standard Time. 4. Date plus hours, minutes, seconds and decimal fractions of a second ----------------------------------------------------------------------- The number of seconds is followed by a dot and one or more digits representing a decimal fraction of a second. An adopting standard must specify both the minimum and the maximum number of digits, as described earlier. If times are expressed in UTC, the format is: YYYY-MM-DDThh:mm:ss.sZ Example: 1994-11-05T13:15:30.45Z If times are expressed in local time, together with a time zone offset, the format is: YYYY-MM-DDThh:mm:ss.s+hh:mm or: YYYY-MM-DDThh:mm:ss.s-hh:mm Example: 1994-11-05T08:15:30.45-05:00 Both the examples in this section correspond to November 5, 1994, 8:15:30.45 am, US Eastern Standard Time. References ========== [ISO 8601] "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO 8601:1988(E), International Organization for Standardization, June, 1988. [KUHN] "A Summary of the International Standard Date and Time Notation", Markus Kuhn, <http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html>, 1996-11-05. [NEWMAN] "Date and Time on the Internet", Chris Newman, <draft-newman-datetime-01.txt>, January 1997. ------------------------------------------------------------------------ Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

The Year 2000 Problem Listserv
by Monty Solomon June 25, 1997

June 25, 1997

Begin forwarded message: Date: Mon, 23 Jun 1997 23:16:12 -0700 From: Susan Evoy <sevoy(a)Sunnyside.COM> Subject: The Year 2000 Problem Listserv The Year 2000 problem is getting increasing attention and is a matter of growing concern in this country and abroad. There are forums for discussion of technical aspects of the problem but none that focus on the economic, social and political implications. If you would be interested in participating in a forum on the y2k (year two thousand) problem join the cpsr-2yk listserv! To subscribe to this list, you should send a message to listserv(a)cpsr.org In the body of the message, write: subscribe cpsr-y2k <firstname> <last name> Norman Kurland (kurlandn(a)crisny.org) will be the moderator of the list. Here is a possible opening question: What are the most critical economic, political and social consequences of the Year 2000 Problem? How should computer professionals be dealing with them? CPSR=Computer Professionals for Social Responsibility http://www.cpsr.org/dox/home.html cpsr(a)cpsr.org P.O. Box 717 Palo Alto, CA 94302 Phone: (415)322-3778 Fax: (415)322-4748

1 0

Re: Draft profile of ISO 8601
by Misha Wolf June 24, 1997

June 24, 1997

Dan Connolly wrote: > > Misha Wolf wrote: > > > 2. Date plus hours and minutes > > ------------------------------- > > > > The format is one of: YYYY-MM-DDThh:mmZ > > YYYY-MM-DDThh:mm+hh:mm > > YYYY-MM-DDThh:mm-hh:mm > > A major benefit of using YYYY-MM-DD over the Internet > traditional Tue, 30 Jan 1997... format is that string > comparisons work for date comparisons; e.g. you don't > have to go through heroics to sort log files by date. > > By including timezone stuff (+hh:mm), you lose that > benefit. > > Is there some motivation for including +yy:mm that > offsets this loss? [Note: For "+yy:mm" read "+hh:mm"] I'm not sure which of the following you are asking: Q1. Why have time zone info? Q2. Why not require that all dates/times be normalised to UTC when entered. Answer to Q1: A time is only meaningful within a time zone. Answers to Q2: a) I'm defining a profile with various options (this can be viewed as a family of profiles), such that each adopting standard can choose the appropriate options. For many purposes, the actual time zone is important. PICS, for instance, requires the time zone. b) The normalisation to UTC can easily be done prior to date/time collation/comparison. It involves just an addition or subtraction. ----------------------------------------------------------------------- Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

Europe/Zurich
by Florian La Roche June 24, 1997

June 24, 1997

Why do you list Zurich for switzerland? (CH) The capital of the swiss is Bern. Thanks, Florian La Roche

1 0

Draft profile of ISO 8601
by Misha Wolf June 22, 1997

June 22, 1997

Though I have been reluctant to write a profile of [ISO 8601], the W3C HTML WG has decided it wants the spec for Cougar (the next version of HTML) to reference a date/time profile and I've been actioned to produce this profile by the end of next week. This note lists some preliminary thoughts for comment. If you want to find out more about [ISO 8601], visit [KUHN]. I wrote a few days ago that my goal is a profile which is: - conformant, - widely adopted, - easy to understand, - not too permissive, - not too restrictive, - electronically available. The way to reconcile some of these requirements is to provide a profile allowing several options, especially regarding granularity. Other standards could refer to the profile and state which option has/have been adopted. A rough sketch follows. I have borrowed some phrases from [KUHN]. Granularity =========== This profile of [ISO 8601] defines four levels of granularity: 1. Date only ------------- The format is: YYYY-MM-DD 2. Date plus hours and minutes ------------------------------- The format is one of: YYYY-MM-DDThh:mmZ YYYY-MM-DDThh:mm+hh:mm YYYY-MM-DDThh:mm-hh:mm where: Z indicates that the date/time uses Universal Time (UTC), +hh:mm indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC, -hh:mm indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes behind UTC. 3. Date plus hours, minutes and seconds ---------------------------------------- The format is one of: YYYY-MM-DDThh:mm:ssZ YYYY-MM-DDThh:mm:ss+hh:mm YYYY-MM-DDThh:mm:ss-hh:mm 4. Date plus hours, minutes, seconds and decimal fractions of seconds ---------------------------------------------------------------------- The format is one of those shown in option 3, with the insertion, immediately after "ss", of either a full stop or a comma, followed immediately by one or more digits representing a decimal fraction of a second, eg: YYYY-MM-DDThh:mm:ss.ddZ YYYY-MM-DDThh:mm:ss.dd+hh:mm YYYY-MM-DDThh:mm:ss.dd-hh:mm If adopting this granularity option, the adopting standard must state how many digits may be used to represent a decimal fraction of a second, eg: 2 digits, 1-3 digits, 1-99 digits, any number of digits. Treatment of missing elements ============================= In some cases, software components may need to compare a date/time using coarser granularity with one using finer granularity. This shall be done as described below. Granularity options 2-4 ----------------------- The missing portions are deemed to be equal to zero. Thus the following all represent the same date/time: 1997-06-20T12:34Z 1997-06-20T12:34:00Z 1997-06-20T12:34:00.00Z 1997-06-20T12:34:00.000000000000000000000000000Z Granularity option 1 -------------------- An isolated date is treated as if it had the following string appended: T12:00Z For example: 1997-06-20 is treated as if it were: 1997-06-20T12:00Z This approach, proposed by Charles Wicksteed, has the advantage that at 1997-06-20T12:00Z, most of the world would agree that the current date is 1997-06-20. Comments? ~~~ [ISO 8601] "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO 8601:1988(E), International Organization for Standardization, June, 1988. [KUHN] "A Summary of the International Standard Date and Time Notation", Markus Kuhn, <http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html>, 1996-11-05. [NEWMAN] "Date and Time on the Internet", Chris Newman, <draft-newman-datetime-01.txt>, January 1997. ----------------------------------------------------------------------- Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

2 1

Date/time on the Internet
by Misha Wolf June 18, 1997

June 18, 1997

Increasing numbers of Internet-related protocols and standards need to reference dates/times in a standard manner. The base standard mostly used for this purpose is [ISO 8601]. This agreement on one base standard is a Good Thing. A note for folks working with dates where YYYY < 0000 or YYYY > 9999: I know ISO 8601 isn't right for you. You'll need to use another standard which fits your requirement. Sorry. ISO 8610 is a *very* permissive standard and so each Internet-related protocol/standard is making up its own profile of ISO 8601. That is a Bad Thing. Some of these are conformant profiles; others are not. And that's a Very Bad Thing. Some of the profiles are more restrictive; others are less so. An example of a non-conformant profile is that used by PICS 1.1 [REC-PICS-labels-961031]; see the extract below. This profile is non-conformant in that it separates the YYYY and MM and DD portions using the character "." instead of "-". The PICS profile is also surprisingly restrictive, in that it does not permit seconds to be included. An example of a conformant profile is that used by [draft-newman-datetime-01.txt]. This profile is also rather restrictive for some Internet-related protocols and standards, in that it mandates the use of hours, minutes and seconds. Some users may wish to specify only a date when creating metadata. Chris has agreed to make the time portion optional in his next draft. I would suggest we need a single profile which is: - conformant, - widely adopted, - easy to understand, - not too permissive, - not too restrictive, - electronically available. We also need to persuade the people specifying forthcoming standards such as PICS-NG, Cougar, etc, to use this profile. So, how do we proceed? Chris Newman's Internet Draft has two further disadvantages: (i) it's an Internet Draft (rather than an RFC) and (ii) it is made rather large and intimidating by catering for dates/times in the future and the associated mish-mash (did I spell that right?) of time zones. One possibility would be for Chris, who is currently busy on other important stuff, to find the time to split his Internet Draft into two: (i) a quickie covering just a profile of ISO 8601 and (ii) another, covering the more complex stuff. Another possibility would be for someone else to do the job (I'm not volunteering). Comments? A note on distribution: I have not found a single suitable forum for this topic, so I suggest it be discussed on the open lists (meta2(a)mrrl.lut.ac.uk) and (www-html(a)w3.org) and request that you send your responses to those two lists. I'll forward this initial message to a few other relevant lists, mostly closed ones, to give people on those lists notice of this thread. REFERENCES: [ISO 8601] "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO 8601:1988(E), International Organization for Standardization, June, 1988. [REC-PICS-labels-961031] "PICS Label Distribution Label Syntax and Communication Protocols", Version 1.1, W3C Recommendation 31-October-96. [draft-newman-datetime-01.txt] "Date and Time on the Internet", Chris Newman, Internet Draft, January 1997. An extract from [REC-PICS-labels-961031] follows: quoted-ISO-date :: '"'YYYY'.'MM'.'DD'T'hh':'mmStz'"' based on the ISO 8601:1988 date and time standard, restricted to the specific form described here: YYYY :: four-digit year MM :: two-digit month (01=January, etc.) DD :: two-digit day of month (01 through 31) hh :: two digits of hour (00 through 23) (am/pm NOT allowed) mm :: two digits of minute (00 through 60) S :: sign of time zone offset from UTC ('+' or '-') tz :: four digit amount of offset from UTC (e.g., 1512 means 15 hours and 12 minutes) For example, "1994.11.05T08:15-0500" is a valid quoted-ISO-date denoting November 5, 1994, 8:15 am, US Eastern Standard Time Note: The ISO standard allows considerably greater flexibility than that described here. PICS requires precisely the syntax described here -- neither the time nor the time zone may be omitted, none of the alternate formats are permitted, and the punctuation must be as specified here. ----------------------------------------------------------------------- Misha Wolf Email: misha.wolf(a)reuters.com 85 Fleet Street Standards Manager Voice: +44 171 542 6722 London EC4P 4AJ Reuters Limited Fax : +44 171 542 8314 UK ------------------------------------------------------------------------ Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

help
by Michael.Matschir＠zamg.ac.at June 11, 1997

June 11, 1997

1 0

Small patches for tzcode1997e.tar.gz
by Andreas Jaeger June 4, 1997

June 4, 1997

Hi, I've send the following mail already once to the list but neither get an reply nor find it in tzarchive. Let's give it another try. I've noticed that tzcode1997e has some prototype definitions that don't match the actual function headers. I've appended a patch for private.h and also for scheck.c (I think that both parameters should be the same) and hope you can use it. Thanks for a really good package. Cheers, Andreas diff -cr tzcode1997e/private.h tz/private.h *** tzcode1997e/private.h Sun May 4 00:52:23 1997 --- tz/private.h Wed May 21 16:56:12 1997 *************** *** 176,188 **** ** Private function declarations. */ char * icalloc P((int nelem, int elsize)); ! char * icatalloc P((char * old, const char * new)); ! char * icpyalloc P((const char * string)); ! char * imalloc P((int n)); ! void * irealloc P((void * pointer, int size)); ! void icfree P((char * pointer)); ! void ifree P((char * pointer)); ! char * scheck P((const char *string, char *format)); /* --- 176,188 ---- ** Private function declarations. */ char * icalloc P((int nelem, int elsize)); ! char * icatalloc P((char * const old, const char * const new)); ! char * icpyalloc P((const char * const string)); ! char * imalloc P((const int n)); ! void * irealloc P((void * const pointer, const int size)); ! void icfree P((char * const pointer)); ! void ifree P((char * const pointer)); ! char * scheck P((const char * const string, const char * const format)); /* diff -cr tzcode1997e/scheck.c tz/scheck.c *** tzcode1997e/scheck.c Sun May 4 00:52:25 1997 --- tz/scheck.c Wed May 21 16:52:54 1997 *************** *** 11,17 **** char * scheck(string, format) const char * const string; ! char * const format; { register char * fbuf; register const char * fp; --- 11,17 ---- char * scheck(string, format) const char * const string; ! const char * const format; { register char * fbuf; register const char * fp; -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)alma.student.uni-kl.de http://www.student.uni-kl.de/~ajaeger/

1 0

spamming
by Sue Ann Bowling June 2, 1997

June 2, 1997

Is it possible to set up a filter such that only messages from outsiders and new list members (say for less than a month) be monitored? Sue Ann Bowling, Geophysical Institute, University of Alaska Fairbanks Professional URL http://climate.gi.alaska.edu/Bowling/Bowling.html Dog URL http://www.mcf.com/bowlingsite/dogpage.html

1 0

spam
by ado May 27, 1997

May 27, 1997

Right now the time zone list is handled on a UNIX system; mail sent to "tz" gets forwarded (as a result of an "/etc/aliases" entry) to the addresses that appear in a file maintained by hand. If anyone can recommend a filtering program to use in the /etc/aliases entry, I'd appreciate hearing from you by electronic mail to arthur_david_olson(a)nih.gov --ado

1 0

Re: Re: Answers to questions, spam problems
by Dave Skinner May 27, 1997

May 27, 1997

> > Dave Skinner writes: > > > I agree that the spammers should be stopped, and if that takes > > > monitoring postings before they are actually posted, then so be it. > > > Chris Carrier writes: > > The only posts that would be monitored/moderated would be those from > > non-tz subscribers; not an undue burden. > Dik Winters writes: > I do not believe that. Currently spammers are using throw-away accounts, > shortly they will be using throw-away subscribtions. Not to dwell on this subject for too long, but I tend to agree with Chris Carrier on this one, and I'm the one at the top of this sequence of quotes. I grew up where burglaries were rare, but did occur. So, we locked our doors when we left the house. By comparison, we had friends in rural Ohio who never locked their doors when they left the house; there was no need. Now, I live in one of the maze of cities and towns that make up the greater Los Angeles area, and there are many areas, that fortunately do not include the one in which I live, but which are nearby, that not only feel they need to lock their doors, but also the need to put bars on their own windows, which can really get in the way of the fire department should there be a fire. The point of this analogy is that letting subscriber articles through unmonitored is working for now as witnessed by Chris Carrier writes: > So the list moderator decided to require that all posts sent from non- > subscribers be cleared through him. Posts from subscribers are still > automatically posted. No spam has appeared on the list since this > policy was adopted five months ago. I would say we have been, up till now, operating like my friends in Ohio. At the point where we feel the spam has gotton bad enough, and I am not sure we are at that point yet, but if and when we get to that point, then we should do the equivalent of locking our doors, i.e. we probably should have non-subscriber articles be monitored. If that gets the job done, then we should leave our anti-spam security measures at that level. At a later time if the spammers start using "throw-away subscriptions" as Dik Winters fears, and if the spam again becomes a significant problem, then we should regretfully do the equivalent of adding the bars to our own windows as well. We can always take this more draconian precaution, but I really hate giving up freedoms, and adding work to the maintainers of this list, unless it really becomes necessary. We should not make the cure worse than the disease. Although I am switching analogies as I state the following, I really do not think we should have representatives of the post office, so to speak, censoring our mail simply to avoid that portion which is junk mail. Dave Skinner

1 0

Re: Answers to questions, spam problems
by Dik.Winter＠cwi.nl May 25, 1997

May 25, 1997

> >I totally agree that the spammers should be stopped, and if that takes > >monitoring postings before they are actually posted, then so be it. > > The only posts that would be monitored/moderated would be those from non-tz > subscribers; not an undue burden. I do not believe that. Currently spammers are using throw-away accounts, shortly they will be using throw-away subscribtions. dik

1 0

Answers to questions, spam problems
by Chris Carrier May 24, 1997

May 24, 1997

Joe Celko [71062.1056(a)compuserve.com] quotes me: >>... the growth of standard time laws. Don't remember much more about it, >>but the full story is in "The History of American Time." >Would you mind giving me the full reference for that book? Unfortunately I don't have a full reference. I remember it came out about 1990, and forget the author's name. It deals mostly with the establishment of standard time, with the last chapter devoted to daylight time. sharris(a)apple.com also quotes me: >Another, related mailing list I subscribe to, CALNDR-L, >run by Rick McCarty of East Carolina University, was suffering from spam >Can you tell me a bit about this list you are referring to, and how one can >subscribe? The list is about calendars: actual and proposed, along with related subjects, like the number of days in a year and the change in that number (which of course is related to leap seconds). It's been up since last October. To subscribe, send a one-line email SUBSCRIBE CALNDR-L to LISTSERV(a)ECUVM.CIS.ECU.EDU. In December members of CALNDR-L started to receive spam from various sources. So the list moderator decided to require that all posts sent from non- subscribers be cleared through him. Posts from subscribers are still automatically posted. No spam has appeared on the list since this policy was adopted five months ago. Although it is possible that a subscriber could send spam, anyone who did would be expelled from the list and everyone on the list is a sensible person who would not do such a thing. I would advocate a similar policy here on tz to stop spam. Dave Skinner (dave(a)kirdu.jpl.nasa.gov) wrote: >I totally agree that the spammers should be stopped, and if that takes >monitoring postings before they are actually posted, then so be it. The only posts that would be monitored/moderated would be those from non-tz subscribers; not an undue burden. Chris

1 0

Re: ["Matthias Urlichs" <smurf@work.smurf.noris.de>] POSIX vs "right" time difference
by Paul Eggert May 23, 1997

May 23, 1997

Date: Thu, 22 May 1997 15:06:40 +0200 (Funky) From: "Matthias Urlichs" <smurf(a)work.smurf.noris.de> the POSIX time zone files ignore leap seconds, i.e. are based on GMT, while the 'right' timezone take leap seconds into account. The base difference between those, according to "date", is 20 seconds (soon to be 21). That's wrong. The difference between UTC and TAI ("atomic time") is actually 30 (soon to be 31) seconds; the 10 seconds come from the fact that UTC and TAI were initially synchronized in 1958, and in 1972 it was realized that they've drifted apart... instant 10-second insertion. That's not what happened. There was no 10-second insertion in 1972. The atomic timekeepers didn't wake up from a 14-year sleep and notice that the world's clocks had drifted! Here's a more accurate description of what happened. Before 1972, UTC was adjusted continuously, without using leap seconds. At the moment of the POSIX Epoch (1970-01-01 00:00:00 UTC), UTC and TAI differed, not by an integral number of seconds, but by a fractional number. The difference between UTC and TAI did not become an integer until 1972, when the leap second regime was introduced. Therefore, it is impossible, on a system with integral time_t, to simultaneously support both "right" and POSIX times accurately before 1972. In some sense, the "right" approach yields undefined times before 1972, since the "right" approach assumes leap seconds. But we could attempt to extend the "right" approach by guessing what it would have been like had it existed. That is, with an integral time_t, we could _approximate_ "right" times before 1972 by consulting historical tables of the difference between UTC and TAI, and rounding to the nearest integer. This is unsatisfactory (not least because such tables understandably do not go back to times before atomic clocks were introduced!), but it is probably the best that we can do with the "right" approach assuming integral time_t. I view this improvement as a low-priority task since very few people use the "right" approach these days; the people who care about leap seconds are using other interfaces. Furthermore, the philosophy of the tz package is to describe times as they actually appeared at the time; it's hard to combine this with the notion of gedanken atomic clocks ticking away in, say, 1901.

1 0

Re: How to stop spammers ...
by Dave Skinner May 22, 1997

May 22, 1997

I totally agree that the spammers should be stopped, and if that takes monitoring postings before they are actually posted, then so be it. Dave Skinner

1 0

BC case, Oliver Wendell Holmes
by Chris Carrier May 22, 1997

May 22, 1997

Fascinating post about British Columbia time. It reminds me of something Oliver Wendell Holmes, when he was on the Massachusetts Supreme Court, ruled on some date after 1883-11-18 but before the adoption of the Standard Time Act of 1918. The LMT of a point in Massachusetts is approximately GMT-4:45, and EST=GMT-5:00. Holmes in his majority opinion wrote that the time of day specified in contracts, etc... was LMT regardless of what the railroads said, unless a governmental body chose to specify otherwise, which no doubt spurred the growth of standard time laws. Don't remember much more about it, but the full story is in "The History of American Time."

1 0

How to stop spammers on tz
by Chris Carrier May 22, 1997

May 22, 1997

jones(a)mr.med.ge.com wrote: >Direct [ i.e. junk ] E-Mail advertising is perhaps the stupidest marketing >idea ever. I completely agree. Another, related mailing list I subscribe to, CALNDR-L, run by Rick McCarty of East Carolina University, was suffering from spam attack until the moderator closed the list to all non-subscribers. A non- subscriber now has to write the moderator, and if the post is relavent, it is posted; if it is spam, it is now. I think ado should do the same thing here. Chris Carrier

1 0

legal reasoning and time-of-day
by 699156＠ican.net May 21, 1997

May 21, 1997

This isn't strictly on-topic, but I though readers of this list would be interested in a recent summary trial in the Supreme Court of British Columbia, Smith Bros. & Wilson (B.C.) Ltd. v. British Columbia Hydro and Power Authority. A key issue was the legal meaning of the term "11:00 a.m.". The ambiguity arose because a time of day expressed in that format is ambiguous: it can refer either to an instant (i.e. exactly eleven hours after midnight) or a 60-second period (i.e. the period more than eleven hours after midnight but less than eleven hours one minute after midnight). Here, a $13-million contract turned on this fine distinction. The defendant B.C. Hydro had issued tender instructions for the contract stating a closing time of "11:00 a.m. local time". The bid of the plaintiff Smith Bros. and Wilson was submitted when B.C. Hydro's clock said 11:01, and stamped accordingly. However, at trial, there was evidence from one of B.C. Hydro's own engineers that the clock was approximately one minute fast, compared to Pacific Standard Time determined with reference to the U.S. Naval Observatory clock in Washington D.C. This part of the judgment makes interesting reading, because the engineer had done the testing for his report two weeks after the day the tenders were due, but was still able to find (based on certain assumptions) the clock's differential on the tendering day. Since the clock was about a minute fast, the plaintiff's bid was actually submitted at 11:00, not 11:01. But this still wasn't good enough, because the court held that 11:00, in its everyday meaning of "the period from 11:00:00 to just before 11:01:00", was not what was meant by the tender instructions. Rather, the tender instructions were read to mean bids could be submitted up to 10:59:59, but not one second after that. The judge stated: [33] B.C. Hydro and Smith Bros. cited cases in which expressions like "until the 1st day of July next", for example, were used. See: Re Smith and McPherson (1921), 51 O.L.R. 457 (App. Div.). The purport of those decisions is that the whole of the named day was intended to be included. The argument is that if the naming of a day imports the whole of that day, the stating of time in hours and minutes should import the whole of that minute as being included in the calculation of the time limit. I do not agree with this analogy. In my opinion, 11:00 a.m. describes a precise point in time, not the time that exists between 11:00 a.m. and 11:01 a.m., whereas, when a date is stated, it is common knowledge and usage that that named day is a 24 hour period from midnight to midnight. The full text of the reasons for judgment is available on the web at http://www.courts.gov.bc.ca/jdb-txt/sc/97/03/s97-0302.txt and there is an article on the case in The Lawyer's Weekly, 21 March 1997, p. 16. M. Englander

1 0

Please remove tz@elsie.nci.nih.gov from your mailing list
by Rob Jones 4-6597 MR Sys May 21, 1997

May 21, 1997

Direct [ i.e. junk ] E-Mail advertising is perhaps the stupidest marketing idea ever. Think of how upset people would be if they received advertising through snail-mail that came postage due... That is how I feel when I receive junk Email. It costs disc space and time. And these costs are forced upon the recepient. It causes me to make note of the compaines that have sent me EMail and I refuse to send them any business. The above opinions are my own, not my employer's. And my apologies to those on the cc: that were not interested in this, but I thought it only fair to let you all know, since I am requesting something that impacts all on the list. -- Rob Jones P.S. If your company is good at promoting sites on the WEB, you should be able to promote your own without using such offensive tactics.

1 0

Is Your Web Site A Secret?
by owl＠owlsnest.com May 20, 1997

May 20, 1997

Is your web site the best kept secret on the Internet? We'll promote it to 50 search engines and indexes for $85 and complete the job in 2 business days. Satisfaction is guaranteed! If you have a great product, but are not getting many inquiries from your Web site, you may not be adequately listed on the Web's search engines and indexes. Millions of viewers daily use these facilities to find the products and services they are looking for. But if your site is not listed, no one will see it. Listings on most of these services are free. However, locating and filling out the forms required to get a listing can take several days, and most people just don't have the time to do it. That is why we offer a web site promotion service. WHAT'S THE DEAL? We will submit your site to 50 indexes and search engines for $85. We will accept the return of this E-mail, with the form below filled out, as an order. We will bill you upon completion of the promotion. Our terms are net 15 days from date of invoice. Satisfaction guaranteed! HOW LONG WILL IT TAKE? Generally, we complete the submissions within 48 hours of receiving your order. It can take any individual search engine or index up to three weeks to process your submission, although most are much faster. WHAT SEARCH ENGINES AND INDEXES ARE INCLUDED IN THE PROMOTION? The list changes from time to time. This is our current list: Abaweb!, Alta Vista, Been There, BizWeb, Central Source Yellow Pages, Enterpreneurs on the Web, Excite, Four11, Galaxy, I-Network I-Systems Spiral Business Directory, I-World Web Pointer, Infoseek, Inktomi, Innovator's Network Yellow Pages, Internet Mall, Jayde Online Directory, Jumpcity, Jumper Hot Links, Linkmaster, Lycos, Magellan, Mega Mall, Net-Happenings, Net Navigator, Net Mall, NTG's List, NYNEX Big Yellow, One World Plaza, OnLine's WWWeb Index, Rex, Starting Point, Truenorth, URL Tree, Virtual Lynx, Web Point, WebCentral, Web Venture Hotlist, Webcrawler, Websurf, Win Mag/NetGuide Hotspots, WhatUSeek, Worldwide Announce Archive, WWW Business Yellow Pages, World Wide Yellow Pages, WWW Worm, YelloWWWeb. HOW WILL I KNOW THAT YOU HAVE PROMOTED MY SITE? When we have completed the promotion, we will send you an HTML file as an attachment to your E-mail bill. Save this file to your disk, and view it through your Web browser. It provides links to the search engine we submitted your site to, plus any comments we received from them when we did it. ARE THERE ANY GUARANTEES? We do not require prepayment. Your satisfaction is guaranteed or you don't pay the bill. WHO IS OWL'S EYE PRODUCTIONS? We are a web site promotion company located at: Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Phone: (914) 278-4933 Fax: (914) 278-4507 Email: owl(a)owlsnest.com HOW DO I ORDER? The easiest way to order is by e-mail. Just hit the REPLY button on your e-mail program and fill out the following information. (This information will be posted to the search engines/indexes): Your name: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: URL: http:// Site Title: Description (about 25 words): Key words (maximum of 25, in descending order of importance): Proofs (Where shall we e-mail proofs): If billing a different address, please complete the following: Addressee: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: We will bill via Email. (7519) Terms: By returning this document via Email, you agree as follows: You have the authority to purchase this service on behalf of your company. Terms are net 15 days. Accounts sent to collections will be liable for collection costs. You agree to protect and indemnify Owl's Eye Productions, Inc. in any claim for libel, copyright violations, plagiarism, or privacy and other suits or claims based on the content or subject matter of your site. WHAT HAPPENS NEXT? When we receive your order, we will input the information into our system, and send you a proof. After we process any corrections, we will run your promotion, capturing any comments from search engines as we go. We will incorporate these into an HTML-formatted report to you, which we will attach to your bill. ===Web Promotions=====Press Releases=====Link Exchanges========= Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Ph: 914-278-4933 Fx: 914-278-4507 E-mail: owlseye(a)owlsnest.com

1 0

World Time Zone Map
by Chuck Ellis May 10, 1997

May 10, 1997

I am re-sending this message in the absence of any indication it was received the first time it was sent. -Chuck Ellis Gentlemen: I have completed a Beta of a 1:1,000,000-scale world vector map of time zones and associated attribute data, including applicable Rule, ISO Country Codes, etc. In reviewing the tz archive postings, it became clear that some of you are working towards the same end. Therefore, I am posting the Beta to our company's FTP site in the hope that we can join forces to accelerate the development of this most useful map and data set. Background: I am a partner in MaconUSA, LLC, a digital mapping company based in Boston whose chief products are digital vector maps (with attached attribute data) of the world's political, administrative, civil, postal and telcomm boundaries. MaconUSA is the US "sister" company to Macon GmbH (Waghausel, Germany), which manufactures a suite of desktop mapping products for the European market. While we distribute primarily into the GIS market, our maps are for the most part focused on demographic, sales and marketing applications. We have developed comprehensive boundary and features sets for Europe and the US, and are in the process of completing a Mexican/Caribbean/Central American/South American Map set. We are Data Partners to virtually all of the major GIS application companies, such as ESRI, MapInfo, AutoDesk, Tactician, et al; our European maps are a (new) free inclusion in all of ESRI's shipping products. We have fielded numerous requests over the past year from our customers for both an accurate/current worldwide time zone map, and an equivalent map delineating telephone country and area code boundaries; the time zone map is the completion of part one of this development effort. While we are obviously a for-profit company, we are interested in a cooperative and public-interest effort regarding the time zone map. I would envision such cooperation including joint posting/maintenance of a time zone-map web page freely accessible to the worldwide public, participation in ongoing standards-oriented work (such as it is or may become), etc. The TZ archives maintained at elsie.nci.nih.gov appear to be as close to a defacto standards repository as a non-authoritative listserv can be; in the absence of any greater authority, we would prefer to work actively with it. Time zone Map: Three compressed files are posted at ftp://maconusa.com -- time zone.zip timezon2.zip time zone3.zip The first file (time zone.zip) contains time zone.* (the primary time zone vector map and its attached attribute database); a rough readme.txt file for overview; tz_struc.txt which describes the attribute database in detail; city_550.* (the "top" 550 cities in the world as map points with tz atributes); mid_mif.txt (which is a detailed description of MapInfo's ASCII vector map-file format that all boundary, point, and other map layers are written to, and is enough of a lingua franca to be transportable across many GIS and CAD applications). The second file (timezon2.zip) contains city_11k.* (a gazetteer of the "top" 11,000 cities in the world as map points with tz atributes); airport.* (a second gazetteer of 14,000+ airports worldwide as map points with tz attributes); ports.* (a third gazetteer of 4,500+ Ports around the world plotted as map points with tz attributes); overlay.* (a simple grid of the old 1884 GMT time zone lines for reference viewing; and ????struc.txt files detailing the file layouts for the gazetteer attribute databases. The third file (timezon3.zip) contains city_80k.* (a massive gazetteer of 80,000 cities around the world plotted as map points with associated tz attributes). All three files are password protected. The password is: proeger The files have been zipped with pkzip v. 2.04g Map Description: The map is based upon Macon's own ISO-3166 standard world map, a commercial product that is updated semi-annually. In turn, Macon's world map is based upon the original 1:1,000,000 DCW with a significant number of boundaries redrawn and/or updated to reflect current ISO-3166 definitions. The Datum is WGS1984; this particular map is current to December 31, 1996. The map was created in MapInfo, and has not yet been cleaned/processed with ArcInfo into a topological coverage (this will happen soon); the polygons are drawn in an essentially connect-the-dots sequence with preliminary shared-border snapping and de-duping. Please refer to the mid_mif.txt file for a detailed description of MapInfo's ASCII vector format. The 34 unique UTC-Offsets have been assigned colors according to a west-to-east spectral graduation using the Netscape 256-color chart (which is also Windows-compliant); these can be ignored or changed at will. The gazetteer points are derived from different sources. A significant number of just-onshore points appear slightly offshore due to being digitized from lower-scale maps and/or different datums; these have been properly attributed with tz data, but will be positionally adjusted in the final release. Nevertheless, the gazetteer collection has been included at this time because it is powerful testament to the primary advantage of defining detailed time zone polygons: a simple point-in-polygon operation can in one pass assign tz attributes to a virtually limitless number of map objects. Specific Time zone Notes: We have had to take some liberties in this beta version: 1) Asia/Timor -- A specific objective in producing this file was maintenance of strict ISO-3166 compliance; in this case, the principal requirement was simply including every country in the ISO roster. To wit, we added a new time zone, Asia/Timor, to represent East Timor. It has been assigned the (default) rule, No_DST, which matches its neighboring zone, Asia/Ujung_Pandang. 2) Atlantic/Madeira -- Even though Atlantic/Madeira is a duplicate of Europe/Lisbon, it was left as a distinct zone for cartographic purposes; linking far-flung polygons into one object can cause problems in many mapping applications when, for example, centroids are calculated, labels are auto-placed, or MBR (minimum-bounding-rectangle) calculations are involved. 3) America/Dawson_Creek -- this boundary is approximate only, due to a lack of any refining information. 4) America/Regina, America/Winnipeg -- these boundaries obey all available notes from the archives, but are simply invented using provincial sub-boundaries and meridians/parallels in the absence of any meaningful feature definitions 5) America/Scoresbysund -- this boundary is approximate only, albeit probably very close 6) America/Thule -- same as (4) above 7) Asia/Aqtau, Asia/Aqtobe, Asia/Alma-Ata -- these boundaries were created using current provincial sub-boundaries in the absence of any refining data 8) Africa/Kinshasha, Africa/Lubumbashi -- same as (7) above 9) Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Magadan -- the boundaries between these zones are not well-defined; we used a CIA map from 1994 at a scale of 1:5,000,000 to approximate these 10) America/Manaus, America/Fortaleza -- we defaulted the split between these two zones as a simple east-west meridian dividing Para 11) The attached tz attribute database defaults the ending year for currently-active Rules to 1999 for now to ease the burden on application developers using the data; this is obviously quite artificial, and any suggestions for how to handle this would be appreciated 12) The default Rule for countries with no active DST assignations is "No_DST" 13) Historical Zone and Rule information is for the most part not included; only in the case of a current Zone using a current Rule with a (provided) onset-date was the start-year included; we are happy to change this based on agreed-upon suggestions, but the drawing of historical zones is well beyond our scope. Viewing the Time zone Map: We apologize for not providing the tz map in a directly-viewable format just yet. We are currently embedding the map with its associated database into an applet which I will upload in the coming weeks. Those wishing to view the map at this time have the following alternatives: a) Use MapInfo-- both the MapInfo Desktop and MapInfo Professional products can import mid-mif files directly, since it is the intermediate ASCII format for both applications b) Use ArcView, BusinessMap, ArcInfo, or ArcCAD-- all ESRI products can import mid-mif files directly c) Use Microsoft Excel Version 7 or higher, or Microsoft Office95 or higher-- these newer versions of Excel contain a feature called DataMap which can draw, color and query a MapInfo-BINARY format map directly; I will be posting the time zone map in this format in the next day or so as timezon4.zip at ftp://www.maconusa.com d) Use Any CAD Software-- I will be posting a .DXF version of the map in the next day or so as timezon5.zip at ftp://maconusa.com e) Write Your Own Viewer-- the mid-mif ASCII vector map format is quite simple, though with all of the applications out there capable of directly handling mid-mif, you're probably better off waiting for the Excel or CAD versions to post in the next day or so, or our own embedded viewer to post within the next couple of weeks. Continued Development: We are quite committed to upgrading, updating, and generally improving this map. Any specific zone comments relating to how/where the boundaries are drawn are most useful if they provide or describe (in order of preference): the actual map, or a reference to where we can find it; underlying sub-boundaries (such as administrative or statistical or poitical or postal or municipal) comprising the zone; major land or water features which delineate a boundary or part of boundary; a "legal" description (such as "follow rickety river six miles south, then east along provincial boundary..."); corrections/additions/deletions to the list of cities/towns included in a zone (you may find the gazetteer of 80,000 cities posted as noted above useful as a starter here). Comments or Questions: Please contact Chuck Ellis, at MaconUSA, 214 Lincoln Street, Suite 115, Allston, MA 02134, Tel 617-254-2295, Fax 617-254-2883, e-mail chuck_ellis(a)msn.com. Respects, Chuck Ellis VP, R&D MaconUSA, LLC

1 0

ISO 3166 and the "tz" Database
by Dave Skinner May 10, 1997

May 10, 1997

First of all, in case you were not aware of the fact, 3 of the 238 different ISO 3166 "countries" listed in file "tzdata/iso3166.tab" have no corresponding zone in the "tz" database. They are BV Bouvet Island HM Heard Island & McDonald Islands TP East Timor Bouvet Island is described in file "tzdata/antarctica" as # Norway - territories # Bouvet (uninhabited) Heard Island & McDonald Islands is described in file "tzdata/antarctica" as # Australia - territories # Heard Island, McDonald Islands No other information about Heard Island & McDonald Islands is provided. As for "East Timor", it is an area that both Indonesia and Portugal claim sovereignty over which is not recognized by the United Nations, or so says the 1996 edition of the CIA World Factbook. I can find no reference to "Timor", let alone "East Timor", in any of the "tzdata/*" files except, of course, "tzdata/iso3166.tab". Next, if the "tz" database is REALLY going to adhere to ISO 3166, then the definitions of the various zones should be grouped by the "countries" defined therein. Currently, this is not the case. The following is a complete list of the ISO 3166 countries that have multiple zone entries in the "tz" database. AQ Antarctica AR Argentina AU Australia BR Brazil CA Canada CL Chile CN China EC Ecuador ES Spain FM Micronesia GB Britain (UK) GL Greenland ID Indonesia IL Israel JP Japan KI Kiribati KZ Kazakhstan MH Marshall Islands ML Mali MX Mexico MY Malaysia NZ New Zealand PF French Polynesia PT Portugal RU Russia SJ Svalbard & Jan Mayen UA Ukraine UM US minor outlying islands US United States ZR Zaire There are 30 of them. As reported in my most recent previous email, 23 of these "countries" currently have multiple internal time zones, i.e. multiple areas that differ in how and when they observe the time that they do, but that is irrelevent here. By inspection, I found that the country groupings in the following five continent files tzdata/antarctica tzdata/asia tzdata/australasia tzdata/europe tzdata/northamerica do not, in general, follow the ISO 3166 groupings identified in file "tzdata/zone.tab" from which the above list was extracted. In particular, the following differences have been identified. AQ Antarctica Zone Indian/Kerguelen, that is defined in file "tzdata/antarctica" as part of the Antarctica definitions therein, is part of the "country" identified by the 2-letter country code "TF" for "French Southern & Antarctic Lands" with respect to ISO 3166, which does not appear in the above list. CN China China is identified as the "People's Republic of China" in file "tzdata/asia". This compares to just "China" with respect to ISO 3166. GB Britain (UK) Great Britain is identified as "United Kingdom" in file "tzdata/europe". This compares to "Britain (UK)" with respect to ISO 3166. Zone Europe/Dublin, that is defined in file "tzdata/europe" as part of the so-called "United Kingdom" definitions therein, is part if the country identified by the 2-letter country code "IE" for "Ireland" with respect to ISO 3166, which does not appear in the above list. GL Greenland Zones America/Thule, America/Godthab, and America/Scoresbysund, that are defined in file "tzdata/europe" as part of the Denmark definitions therein, are part of the "country" identified by the 2-letter country code "GL" for "Greenland" with respect to ISO 3166. Zone Atlantic/Faeroe, that is defined in file "tzdata/europe" as part of the Denmark definitions therein, is part of the "country" identified by the 2-letter country code "FO" for "Faeroe Islands" with respect to ISO 3166, which does not appear in the above list. Zone Europe/Copenhagen, that is defined in file "tzdata/europe" as part of the Denmark definitions therein, is part of the country of "Denmark" with its 2-letter country code "DK", with respect to ISO 3166, which does not appear in the above list. IL Israel Zone Asia/Gaza is defined in file "tzdata/asia" as part of a separate set of definitions for "Palestine" therein instead of as part of the corresponding Israel definitions. Yet, Asia/Gaza is part of the country identified by the 2-letter country code "IL" for "Israel" with respect to ISO 3166. SJ Svalbard & Jan Mayen Zone Atlantic/Jan_Mayen, that is defined in file "tzdata/europe" as part of the Norway definitions therein, is part of the "country" identified by the 2-letter country code "SJ" for "Svalbard & Jan Mayen" with respect to ISO 3166. Zone Arctic/Longyearbyen, that is linked to Europe/Oslo in file "tzdata/europe" as part of the Norway definitions therein, is part of the "country" identified by the 2-letter country code "SJ" for "Svalbard & Jan Mayen" with respect to ISO 3166. Zone Europe/Oslo, that is defined in file "tzdata/europe" as part of the Norway definitions therein, is part of the country of Norway with its 2-letter country code "NO" with respect to ISO 3166, which does not appear in the above list. UM US minor outlying islands Zones Pacific/Johnston and Pacific/Wake are individually defined in file "tzdata/australasia" instead of being grouped together under a set of definitions labeled "US Minor Outlying Islands", as would be expected by being part of the "country" identified by the 2-letter country code "UM" for "US minor outlying islands" with respect to ISO 3166. Zone Pacific/Midway is defined in file "tzdata/northamerica" as part of the United States definitions therein instead of in file "tzdata/australasia" along with zones Pacific/Johnston and Pacific/Wake as part of a set of definitions labeled "US Minor Outlying Islands" as would be indicated by being part of the country identified by the 2-letter country code "UM" for "US minor outlying islands" with respect to ISO 3166. KP Korea (North) and KR Korea (South) Zones Asia/Pyongyang and Asia/Seoul are defined in file "tzdata/asia" as part of the "Korea" definitions therein, but there should be separate sets of Korea (North) definitions, which would include zone Asia/Pyongyang, and Korea (South) definitions, which would include zone Asia/Seoul. This is what separate 2-letter country codes "KP" for "Korea (North)" and "KR" for "Korea (South)" indicate with respect to ISO 3166. Dave Skinner dave(a)kirdu.jpl.nasa.gov

1 0

Re: Daylight Extra and UK General Election
by peter＠aldie.co.uk May 9, 1997

May 9, 1997

Chris Carrier <72157.3334(a)CompuServe.COM> wrote: > As most of you know, on May 1 the United Kingdom had a General Election for > Parliament and Labor got in with a substantial majority. Chris, I'm surprised. I wouldn't have thought you would have missed a detail like this. It is the Labour Party, currently trading under the brand name New Labour. :-) > The results of one race might be interesting to some of us: the seat held by > John Butterfill (Con., Bournemouth West). Butterfill in 1995 introduced a > bill, known as the Daylight Extra Bill, which would have put the UK on summer > time in winter and double summer time in summer, to synchronise it with the > rest of the EU. There was an attempt to force it out of committee; this > requires the assent of 100 MPs (out of, I believe, a total number of 630) and > the Bill received the support of 93. What actually happened was there were insufficient MPs to force a vote on closing the debate, so a vote could be taken on the Bill itself. Only 93 were present, so presumably the debate rambled on without coming to any conclusion. This was at the stage called second reading, which is before the Bill would have been considered in detail by a committee of MPs. There were 650 MPs in the old Parliament, 659 in the new one. The fact that only 93 were present out of 650 was not particularly suprising. There aren't actually enough seats for all of them anyway. > What I would like to ask is if anyone saw anything concerning Daylight Extra > during the General Election as a whole or in Bournemouth West specifically. Much as we might wish it otherwise, discussion of the policies relating to time of any of the major parties was notable only by its complete absence. A `grep -i time' through the manifesto text of each of the three major parties (Labour, Conservative, Liberal Democrat) finds nothing relevent at all. A search though The Times between 1 March 97 and 30 April 97 for `daylight extra' also shows no hits. I didn't read all the election coverage in the papers I read but I didn't spot anything; neither did I hear anything on radio news. I admit I am a long way from Bournmouth, but I doubt it was much different down there. People here may get worked up about proposed changes to Summer Time arrangements and changes of timezone when a specific proposal appears but otherwise it really isn't an issue at all. Peter Ilieve peter(a)aldie.co.uk

1 0

Daylight Extra and UK General Election
by Chris Carrier May 9, 1997

May 9, 1997

As most of you know, on May 1 the United Kingdom had a General Election for Parliament and Labor got in with a substantial majority. The results of one race might be interesting to some of us: the seat held by John Butterfill (Con., Bournemouth West). Butterfill in 1995 introduced a bill, known as the Daylight Extra Bill, which would have put the UK on summer time in winter and double summer time in summer, to synchronise it with the rest of the EU. There was an attempt to force it out of committee; this requires the assent of 100 MPs (out of, I believe, a total number of 630) and the Bill received the support of 93. (Note to anyone: I would appreciate clarification/correction to any of this.) I was able to get the results of Bournemouth West last weekend, and Butterfill managed to retain his seat, but he lost 14 percentage points, which was comparable to the Conservative loss of support in the rest of the UK, so his sponsorship of Daylight Extra didn't seem to either help or hurt him. What I would like to ask is if anyone saw anything concerning Daylight Extra during the General Election as a whole or in Bournemouth West specifically. Chris Carrier

1 0

Re: World Timezone Map
by Dave Skinner May 9, 1997

May 9, 1997

I was ever so glad to receive the recent email fro Chuck Ellis of MaconUSA, LLC. I have been busy behind the scenes collecting and organizing the boundary data for the time zone map capability previously discussed in the tz archive at elsie.nci.nih.gov. This was without the knowledge of, or data from, maconusa.com. I wanted to respond to Chuck Ellis' email in a timely fashion, and in lieu of what I read in that email, I wanted to introduce my internal time zone boundary numbering scheme for the current set of countries with multiple internal time zones that I have been working on to facilitate discussion of the status and accuracy of the boundary data associated with these key otherwise missing boundaries. Following up on the ISO-3166 work already done with respect to the Time Zone Database (tz), I organized my efforts around that standard as well. So, high level compatibility with maconusa.com should already be achieved. Likewise, I gathered the 1:1,000,000 scale Digital Chart of the World (DCW) data and augmented it with 1:100,000 USGS state and county data from the 1990 census. I realized that many of the poltical boundaries had changed since 1992, when the version of DCW to which I obtained access was released. I was hoping to update that with the Vector Smart Map Level 0 (VMap0) data once I could get my hands on it. I was also prepared to work backward from the .pdf map files that are posted by the CIA as part of their web page providing access to "The World Factbook 1996", as a last resort. There is an actual a time zone map of the world published there as well, for what it is worth. This web page is located at or near http://www.odci.gov/cia/publications/nsolo/wfb-all.htm AS Chuck Ellis' email arrived, I still did not have accurate data for, or descriptions of, the time zone boundaries inside of countries with multiple time zones, although boundaries 05.01, 06.01, 07.01, 15.01, and 17.01 in the attached table may simply be the distinction between the mainland and the island(s) in question. As for viewing map data, I acquired a copy of GRASS and Grassland (a beta copy for SunOS5 from LAS, Inc. of Canada of the latter) which permit the viewing of VPF (DCW, VMap0) and SDTS (USGS) file formats. I am really new at all of this. So, exactly how to proceed to take any of the various .zip files at maconusa.com and to make use of these Unix-based viewers would be appreciated. (I would prefer to stay Unix-based, if that is at all possible.) The goal, as Chuck Ellis observed, should most definitely be to create a set of time zone polygons, because the ability to automatically update the gazetteer whenever a change is introduced is straightforward, simple, and an already solved problem with already written available code. Anyhow, here is the ISO-3166 sorted list of internal time zone boundaries to which I have been alluding. Of the 30 ISO-3166 "countries" with multiple zones in the tz database, there are only 23 which currently have multiple time zones. These 23 countries have 69 internal boundaries by my current tally. As we are all aware, multiple time zones include the distinction between the boundaries when Daylight Savings Time is in effect, e.g. the distinction between the U.S. Eastern Time Zone with and without that portion of Indiana that does not observe daylight savings time attached in the standard time October-to-April period (boundary 22.07) and in the daylight time April-to-October period (boundary 22.08), respectively, of any given year. Note that Antarctica and Greenland boundaries isolate the tz zones in question from the rest of the land mass, as opposed to separating a series of mostly vertical strips from each other like the boundaries of the other 21 ISO-3166 "countries" listed below. Dave Skinner dave(a)kirdu.jpl.nasa.gov 818-354-0114 (voice) 818-393-9900 (fax) --------------------------------------------------------------------------- 01. AQ Antarctica ------------------------------------------------------------- 01.01 |Antarctica/Palmer --4:00 ChileAQ -------------------------------------------------------------| ------------------------------------------------------------- 01.02 |Antarctica/Mawson +6:00 None -------------------------------------------------------------| ------------------------------------------------------------- 01.03 |Antarctica/Casey +8:00 None -------------------------------------------------------------| ------------------------------------------------------------- 01.04 |Antarctica/DumontDUrville +10:00 None -------------------------------------------------------------| ------------------------------------------------------------- 01.05 |Antarctica/McMurdo +12:00 NZAQ -------------------------------------------------------------| 02. AU Australia Indian/Christmas +7:00 None ------------------------------------------------------------- 02.01 Australia, Western Australia/Perth +8:00 None ------------------------------------------------------------- 02.02 Australia, Central Australia/Adelaide +9:30 AS ----------------------------------------------------- 02.03 Australia/Darwin +9:30 Aus --> None ------------------------------------------------------------- 02.04 Australia, Eastern Australia/Brisbane +10:00 AQ --> None ----------------------------------------------------- 02.05 Australia/Hobart +10:00 AT ----------------------------------------------------- 02.06 Australia/Sydney +10:00 AN ------------------------------------------------------------- 02.07 Australia/Lord_Howe +10:30 LH 03. BR Brazil America/Porto_Acre --5:00 None ------------------------------------------------------------- 03.01 Brazil, Western America/Cuiaba --4:00 Brazil ----------------------------------------------------- 03.02 America/Manaus --4:00 None ------------------------------------------------------------- 03.03 Brazil, Eastern America/Fortaleza --3:00 None ----------------------------------------------------- 03.04 America/Sao_Paulo --3:00 Brazil ------------------------------------------------------------- 03.05 America/Noronha --2:00 None 04. CA Canada Canada, Pacific America/Vancouver --8:00 Vanc ------------------------------------------------------------- 04.01 Canada, Mountain America/Dawson_Creek --7:00 None ----------------------------------------------------- 04.02 America/Edmonton --7:00 Edm ------------------------------------------------------------- 04.03 Canada, Central America/Regina --6:00 None ----------------------------------------------------- 04.04 America/Winnipeg --6:00 Winn ------------------------------------------------------------- 04.05 Canada, Eastern America/Montreal --5:00 Mont ------------------------------------------------------------- 04.06 Canada, Atlantic America/Halifax --4:00 Halifax ------------------------------------------------------------- 04.07 Canada, Newfoundland America/St_Johns --3:30 StJohns 05. CL Chile Pacific/Easter --6:00 Chile ------------------------------------------------------------- 05.01 America/Santiago --4:00 Chile 06. EC Ecuador Pacific/Galapagos --6:00 None ------------------------------------------------------------- 06.01 America/Guayaquil --5:00 None 07. ES Spain Atlantic/Canary +0:00 EU ------------------------------------------------------------- 07.01 Europe/Madrid +1:00 EU 08. FM Micronesia Pacific/Yap +10:00 None ------------------------------------------------------------- 08.01 Pacific/Ponape (Pohnpei) +11:00 None ------------------------------------------------------------- 08.02 Pacific/Kosrae +12:00 None 09. GL Greenland ------------------------------------------------------------- 09.01 |America/Thule --4:00 Thule -------------------------------------------------------------| ------------------------------------------------------------- 09.02 |America/Godthab (Nuuk) --3:00 EU -------------------------------------------------------------| ------------------------------------------------------------- 09.03 |America/Scoresbysund (Ittoqqortoormiit) --1:00 EU -------------------------------------------------------------| 10. ID Indonesia Asia/Jakarta +7:00 None ------------------------------------------------------------- 10.01 Asia/Ujung_Pandang +8:00 None ------------------------------------------------------------- 10.02 Asia/Jayapura +9:00 None 11. JP Japan Asia/Ishigaki +8:00 None ------------------------------------------------------------- 11.01 Asia/Tokyo +9:00 None 12. KI Kiribati Pacific/Tarawa +12:00 None ------------------------------------------------------------- 12.01 Pacific/Enderbury +13:00 None ------------------------------------------------------------- 12.02 Pacific/Kiritimati +14:00 None 13. KZ Kazakhstan Asia/Aqtau +4:00 E--Eur ------------------------------------------------------------- 13.01 Asia/Aqtobe +5:00 E--Eur ------------------------------------------------------------- 13.02 Asia/Alma--Ata +6:00 E-Eur 14. MX Mexico Mexico, Pacific America/Tijuana --8:00 Mexico ------------------------------------------------------------- 14.01 Mexico, Mountain America/Mazatlan --7:00 Mexico ------------------------------------------------------------- 14.02 Mexico, Central America/Mexico_City --6:00 Mexico 15. NZ New_Zealand Pacific/Auckland +12:00 NZ ------------------------------------------------------------- 15.01 Pacific/Chatham +12:45 Chatham 16. PF French_Polynesia Pacific/Tahiti --10:00 None ------------------------------------------------------------- 16.01 Pacific/Marquesas --9:30 None ------------------------------------------------------------- 16.02 Pacific/Gambier --9:00 None 17. PT Portugal Atlantic/Azores --1:00 EU ------------------------------------------------------------- 17.01 Europe/Lisbon +0:00 EU 18. RU Russia Europe/Kaliningrad +2:00 Russia ------------------------------------------------------------- 18.01 Europe/Moscow +3:00 Russia ------------------------------------------------------------- 18.02 Europe/Samara +4:00 Russia ------------------------------------------------------------- 18.03 Europe/Yekaterinburg +5:00 Russia ------------------------------------------------------------- 18.04 Asia/Novosibirsk +6:00 Russia ------------------------------------------------------------- 18.05 Asia/Krasnoyarsk +7:00 Russia ------------------------------------------------------------- 18.06 Asia/Irkutsk +8:00 Russia ------------------------------------------------------------- 18.07 Asia/Yakutsk +9:00 Russia ------------------------------------------------------------- 18.08 Asia/Vladivostok +10:00 Russia ------------------------------------------------------------- 18.09 Asia/Magadan +11:00 Russia ------------------------------------------------------------- 18.10 Asia/Kamchatka +12:00 Russia ------------------------------------------------------------- 18.11 Asia/Anadyr +13:00 Russia 19. SJ Svalbard_&_Jan_Mayen Atlantic/Jan_Mayen (Svalbard) --1:00 None ------------------------------------------------------------- 19.01 Arctic/Longyearbyen +1:00 EU 20. UA Ukraine Europe/Kiev +2:00 EU ------------------------------------------------------------- 20.01 Europe/Simferopol +3:00 Crimea 21. UM US_minor_outlying_islands Pacific/Midway --11:00 None ------------------------------------------------------------- 21.01 United_States, Samoa Pacific/Johnston --10:00 None ------------------------------------------------------------- 21.02 Pacific/Wake +12:00 None 22. US United_States United_States, Hawaii--Aleutian America/Adak --10:00 US ----------------------------------------------------- 22.01 Pacific/Honolulu --10:00 None ------------------------------------------------------------- 22.02 United_States, Alaska America/Anchorage --9:00 US ------------------------------------------------------------- 22.03 United_States, Pacific America/Los_Angeles --8:00 US ------------------------------------------------------------- 22.04 United_States, Mountain America/Denver --7:00 US ----------------------------------------------------- 22.05 America/Phoenix --7:00 None ------------------------------------------------------------- 22.06 United_States, Central America/Chicago --6:00 US ------------------------------------------------------------- 22.07 United_States, Eastern America/Indianapolis --5:00 None ----------------------------------------------------- 22.08 America/New_York --5:00 US 23. ZR Zaire Africa/Kinshasa +1:00 None ------------------------------------------------------------- 23.01 Africa/Lubumbashi +2:00 None

1 0

World Timezone Map
by Chuck Ellis May 8, 1997

May 8, 1997

Gentlemen: I have completed a Beta of a 1:1,000,000-scale world vector map of timezones and associated attribute data, including applicable Rule, ISO Country Codes, etc. In reviewing the tz archive postings, it became clear that some of you are working towards the same end. Therefore, I am posting the Beta to our company's FTP site in the hope that we can join forces to accelerate the development of this most useful map and data set. Background: I am a partner in MaconUSA, LLC, a digital mapping company based in Boston whose chief products are digital vector maps (with attached attribute data) of the world's political, administrative, civil, postal and telcomm boundaries. MaconUSA is the US "sister" company to Macon GmbH (Waghausel, Germany), which manufactures a suite of desktop mapping products for the European market. While we distribute primarily into the GIS market, our maps are for the most part focused on demographic, sales and marketing applications. We have developed comprehensive boundary and features sets for Europe and the US, and are in the process of completing a Mexican/Caribbean/Central American/South American Map set. We are Data Partners to virtually all of the major GIS application companies, such as ESRI, MapInfo, AutoDesk, Tactician, et al; our European maps are a (new) free inclusion in all of ESRI's shipping products. We have fielded numerous requests over the past year from our customers for both an accurate/current worldwide timezone map, and an equivalent map delineating telephone country and area code boundaries; the timezone map is the completion of part one of this development effort. While we are obviously a for-profit company, we are interested in a cooperative and public-interest effort regarding the timezone map. I would envision such cooperation including joint posting/maintenance of a timezone-map web page freely accessible to the worldwide public, participation in ongoing standards-oriented work (such as it is or may become), etc. The TZ archives maintained at elsie.nci.nih.gov appear to be as close to a defacto standards repository as a non-authoritative listserv can be; in the absence of any greater authority, we would prefer to work actively with it. Timezone Map: Three compressed files are posted at ftp://maconusa.com -- timezone.zip timezon2.zip timezone3.zip The first file (timezone.zip) contains timezone.* (the primary timezone vector map and its attached attribute database); a rough readme.txt file for overview; tz_struc.txt which describes the attribute database in detail; city_550.* (the "top" 550 cities in the world as map points with tz atributes); mid_mif.txt (which is a detailed description of MapInfo's ASCII vector map-file format that all boundary, point, and other map layers are written to, and is enough of a lingua franca to be transportable across many GIS and CAD applications). The second file (timezon2.zip) contains city_11k.* (a gazetteer of the "top" 11,000 cities in the world as map points with tz atributes); airport.* (a second gazetteer of 14,000+ airports worldwide as map points with tz attributes); ports.* (a third gazetteer of 4,500+ Ports around the world plotted as map points with tz attributes); overlay.* (a simple grid of the old 1884 GMT timezone lines for reference viewing; and ????struc.txt files detailing the file layouts for the gazetteer attribute databases. The third file (timezon3.zip) contains city_80k.* (a massive gazetteer of 80,000 cities around the world plotted as map points with associated tz attributes). All three files are password protected. The password is: proeger The files have been zipped with pkzip v. 2.04g Map Description: The map is based upon Macon's own ISO-3166 standard world map, a commercial product that is updated semi-annually. In turn, Macon's world map is based upon the original 1:1,000,000 DCW with a significant number of boundaries redrawn and/or updated to reflect current ISO-3166 definitions. The Datum is WGS1984; this particular map is current to December 31, 1996. The map was created in MapInfo, and has not yet been cleaned/processed with ArcInfo into a topological coverage (this will happen soon); the polygons are drawn in an essentially connect-the-dots sequence with preliminary shared-border snapping and de-duping. Please refer to the mid_mif.txt file for a detailed description of MapInfo's ASCII vector format. The 34 unique UTC-Offsets have been assigned colors according to a west-to-east spectral graduation using the Netscape 256-color chart (which is also Windows-compliant); these can be ignored or changed at will. The gazetteer points are derived from different sources. A significant number of just-onshore points appear slightly offshore due to being digitized from lower-scale maps and/or different datums; these have been properly attributed with tz data, but will be positionally adjusted in the final release. Nevertheless, the gazetteer collection has been included at this time because it is powerful testament to the primary advantage of defining detailed timezone polygons: a simple point-in-polygon operation can in one pass assign tz attributes to a virtually limitless number of map objects. Specific Timezone Notes: We have had to take some liberties in this beta version: 1) Asia/Timor -- A specific objective in producing this file was maintenance of strict ISO-3166 compliance; in this case, the principal requirement was simply including every country in the ISO roster. To wit, we added a new timezone, Asia/Timor, to represent East Timor. It has been assigned the (default) rule, No_DST, which matches its neighboring zone, Asia/Ujung_Pandang. 2) Atlantic/Madeira -- Even though Atlantic/Madeira is a duplicate of Europe/Lisbon, it was left as a distinct zone for cartographic purposes; linking far-flung polygons into one object can cause problems in many mapping applications when, for example, centroids are calculated, labels are auto-placed, or MBR (minimum-bounding-rectangle) calculations are involved. 3) America/Dawson_Creek -- this boundary is approximate only, due to a lack of any refining information. 4) America/Regina, America/Winnipeg -- these boundaries obey all available notes from the archives, but are simply invented using provincial sub-boundaries and meridians/parallels in the absence of any meaningful feature definitions 5) America/Scoresbysund -- this boundary is approximate only, albeit probably very close 6) America/Thule -- same as (4) above 7) Asia/Aqtau, Asia/Aqtobe, Asia/Alma-Ata -- these boundaries were created using current provincial sub-boundaries in the absence of any refining data 8) Africa/Kinshasha, Africa/Lubumbashi -- same as (7) above 9) Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Magadan -- the boundaries between these zones are not well-defined; we used a CIA map from 1994 at a scale of 1:5,000,000 to approximate these 10) America/Manaus, America/Fortaleza -- we defaulted the split between these two zones as a simple east-west meridian dividing Para 11) The attached tz attribute database defaults the ending year for currently-active Rules to 1999 for now to ease the burden on application developers using the data; this is obviously quite artificial, and any suggestions for how to handle this would be appreciated 12) The default Rule for countries with no active DST assignations is "No_DST" 13) Historical Zone and Rule information is for the most part not included; only in the case of a current Zone using a current Rule with a (provided) onset-date was the start-year included; we are happy to change this based on agreed-upon suggestions, but the drawing of historical zones is well beyond our scope. Viewing the Timezone Map: We apologize for not providing the tz map in a directly-viewable format just yet. We are currently embedding the map with its associated database into an applet which I will upload in the coming weeks. Those wishing to view the map at this time have the following alternatives: a) Use MapInfo-- both the MapInfo Desktop and MapInfo Professional products can import mid-mif files directly, since it is the intermediate ASCII format for both applications b) Use ArcView, BusinessMap, ArcInfo, or ArcCAD-- all ESRI products can import mid-mif files directly c) Use Microsoft Excel Version 7 or higher, or Microsoft Office95 or higher-- these newer versions of Excel contain a feature called DataMap which can draw, color and query a MapInfo-BINARY format map directly; I will be posting the timezone map in this format in the next day or so as timezon4.zip at ftp://www.maconusa.com d) Use Any CAD Software-- I will be posting a .DXF version of the map in the next day or so as timezon5.zip at ftp://maconusa.com e) Write Your Own Viewer-- the mid-mif ASCII vector map format is quite simple, though with all of the applications out there capable of directly handling mid-mif, you're probably better off waiting for the Excel or CAD versions to post in the next day or so, or our own embedded viewer to post within the next couple of weeks. Continued Development: We are quite committed to upgrading, updating, and generally improving this map. Any specific zone comments relating to how/where the boundaries are drawn are most useful if they provide or describe (in order of preference): the actual map, or a reference to where we can find it; underlying sub-boundaries (such as administrative or statistical or poitical or postal or municipal) comprising the zone; major land or water features which delineate a boundary or part of boundary; a "legal" description (such as "follow rickety river six miles south, then east along provincial boundary..."); corrections/additions/deletions to the list of cities/towns included in a zone (you may find the gazetteer of 80,000 cities posted as noted above useful as a starter here). Comments or Questions: Please contact Chuck Ellis, at MaconUSA, 214 Lincoln Street, Suite 115, Allston, MA 02134, Tel 617-254-2295, Fax 617-254-2883, e-mail chuck_ellis(a)msn.com. Respects, Chuck Ellis VP, R&D MaconUSA, LLC

1 0

new versions of tzcode and tzdata
by ado May 3, 1997

May 3, 1997

The files ftp://elsie.nci.nih.gov/pub/tzcode1997e.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1997f.tar.gz are now available. These incorporate the fixes to zic's error handling that were recently circulated on the tz list, as well as changes inspired by the item circulated on Slovenia. The description of Web resources has been htmlified for browsing convenience, and a new piece of tz-related music has been added to the "Music" file. --ado

1 0

-v option support
by tpm＠hi.com May 1, 1997

May 1, 1997

The zic(8) man page describes the -v option as -v Complain if a year that appears in a data file is out- side the range of years representable by time(2) values. However this functionality appears to have been removed from the code. It is not clear whether this description should have been removed from the man page or whether the functionality was unintentionally removed from the code. If the general consensus is that the man page is correct then some code similar to the following could be added to implement it. I am open to issues and alternatives. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> *************** *** 129,134 **** --- 263,269 ---- static void usage P((void)); static void writezone P((const char * name)); static int yearistype P((int year, const char * type)); + static void year_noise_check P((int year)); #if !(HAVE_STRERROR - 0) static char * strerror P((int)); *************** *** 141,148 **** --- 276,285 ---- static int linenum; static time_t max_time; static int max_year; + static int max_year_representable; static time_t min_time; static int min_year; + static int min_year_representable; static int noise; static const char * rfilename; static int rlinenum; *************** *** 649,654 **** --- 824,831 ---- } min_year = TM_YEAR_BASE + gmtime(&min_time)->tm_year; max_year = TM_YEAR_BASE + gmtime(&max_time)->tm_year; + min_year_representable = min_year; + max_year_representable = max_year; } *************** *** 1278,1288 **** rp->r_yrtype = NULL; else { if (rp->r_loyear == rp->r_hiyear) { ! error(_("typed single year")); return; } rp->r_yrtype = ecpyalloc(typep); } if (rp->r_loyear < min_year && rp->r_loyear > 0) min_year = rp->r_loyear; /* --- 1463,1478 ---- rp->r_yrtype = NULL; else { if (rp->r_loyear == rp->r_hiyear) { ! error(MSGSTR(ONEYEAR,"typed single year")); return; } rp->r_yrtype = ecpyalloc(typep); } + if (noise) + { + year_noise_check(rp->r_loyear); + year_noise_check(rp->r_hiyear); + } if (rp->r_loyear < min_year && rp->r_loyear > 0) min_year = rp->r_loyear; /* *************** *** 2169,2179 **** l = i; if ((i < 0 && l >= 0) || (i == 0 && l != 0) || (i > 0 && l <= 0)) { (void) fprintf(stderr, ! _("%s: %d did not sign extend correctly\n"), progname, i); (void) exit(EXIT_FAILURE); } return l; } /* --- 2365,2399 ---- l = i; if ((i < 0 && l >= 0) || (i == 0 && l != 0) || (i > 0 && l <= 0)) { (void) fprintf(stderr, ! MSGSTR(BADSIGN,"%s: %d did not sign extend correctly.\n"), progname, i); (void) exit(EXIT_FAILURE); } return l; + } + + static void + year_noise_check(year) + int year; + { + if ( ( (year < min_year_representable) || + (year > max_year_representable) ) && + ( (year != INT_MIN) && (year != INT_MAX) ) ) + { + static char *format; + static char *message; + + if (!format) + { + format = MSGSTR(UNREPYEAR, "unrepresentable year: %d"); + } + if (!message) + { + message = emalloc(strlen(format) + 32); + } + (void) sprintf(message, format, year); + warning(message); + } } /* <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Note that MSGSTR() is a simple macro that invokes catgets(3) on systems which support the X/Open interfaces. ---------------------------------------------------------------------- Timothy Patrick Murphy tpm(a)hi.com Voice: (617) 890-0444 Hitachi Computer Products Fax: (617) 890-4998 1601 Trapelo Rd., Waltham, MA 02154, USA ----------------------------------------------------------------------

1 0

warning string missing
by tpm＠hi.com May 1, 1997

May 1, 1997

The warning() function in zic.c contains the following code. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> static void warning(string) const char * const string; { char * cp; cp = ecpyalloc("warning: "); cp = ecatalloc(cp, string); error(string); ifree(cp); --errors; } <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< It appears the argument to error() should be cp instead of string. -- ------ ---------------------------------------------------------------------- Timothy Patrick Murphy tpm(a)hi.com Voice: (617) 890-0444 Hitachi Computer Products Fax: (617) 890-4998 1601 Trapelo Rd., Waltham, MA 02154, USA ----------------------------------------------------------------------

1 0

Missing break statement
by tpm＠hi.com April 30, 1997

April 30, 1997

In the rulesub() function in zic.c there is the following switch statement. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> switch (lowerit(*ep)) { case 's': /* Standard */ rp->r_todisstd = TRUE; rp->r_todisgmt = FALSE; *ep = '\0'; break; case 'w': /* Wall */ rp->r_todisstd = FALSE; rp->r_todisgmt = FALSE; *ep = '\0'; case 'g': /* Greenwich */ case 'u': /* Universal */ case 'z': /* Zulu */ rp->r_todisstd = TRUE; rp->r_todisgmt = TRUE; *ep = '\0'; break; } <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< It appears the break statement is missing from the end of the 'w' case. ---------------------------------------------------------------------- Timothy Patrick Murphy tpm(a)hi.com Voice: (617) 890-0444 Hitachi Computer Products Fax: (617) 890-4998 1601 Trapelo Rd., Waltham, MA 02154, USA ----------------------------------------------------------------------

1 0

zoneinfo package under IRIX?
by Mark White April 29, 1997

April 29, 1997

Hi-- I've been writing some code to convert between timezones on Linux, using zoneinfo (compiling with -lz) Basically, I create a struct tm, populate it with user entered data, then t = mktime(tm); setenv("TZ","Australia/Brisbane",1); tzset(); newtm = localtime(&t); /* then later...*/ setenv("TZ","Australia/Brisbane",1) tzset(); newtm = localtime(&t); I'm compiling with cc, linking in (-lz -L/usr/local/lib) the libz.a, which compiles cleanly under IRIX 5.3. This code works *perfectly* under Linux (redhat 2.0.18). Am I missing something about the zoneinfo package? Thanks in advance, Mark White Tandem Computers Int'l Inc. m.white(a)pacific.tandem.com +61 4 1155 3351 +61 7 3218 3650 (fax)

2 1

Increased web site traffic
by RHill＠TheHost.com April 23, 1997

April 23, 1997

Now you can register your Web Page in over 550 Internet indexes for only $249.00 and watch your traffic soar! The Central Registry has helped thousands of sites like yours greatly improve the performance of their Web Page. The more indexes you are registered in, the more traffic your Web Page is going to receive. Being registered in "the top" indexes is not enough. Why not have your Web Page registered in every index throughout the world that will generate extra traffic for you? The Central Registry is the leader in Web Page registration and promotion. We are the oldest and most well established service of this type on the Internet. We process more Web Page registrations than all of our competitors combined. The Central Registry is the only service that dynamically asks you for the exact same information each index requests, assuring accurate and thorough registration. Unlike most services, we do not exclude indexes with larger input forms and various detailed categories. No other registration service can compare to our value, professionalism and performance. Please come visit our web page today at: http://www.CentralRegistry.com and see what some of our customers have had to say about the overwhelming traffic increases they have seen as a result of being registered everywhere. Thank you. Sincerely, John Thomas The Central Registry JThomas(a)CentralRegistry.com http://www.CentralRegistry.com

1 0

How to compile the zoneinfo files
by Ronman Shen April 23, 1997

April 23, 1997

Hello, this is Ronman Shen from SJCS/ISE. Thank you for your attention. I've changed the file "/usr/share/lib/zoneinfo/asia" to make the system display correct time. But I don't know to how to compile the file now. Can you tell me that? May the force be with you. Sincerely Yours, Ronman Shen +---------------------------------------------------------------- | Email: Ronman.Shen(a)ise.ptt.js.cn | Addr : 15F, 309# North Zhongshan Rd., Nanjing, P.R.China | Tel : +86(25)341-3410 FAX: +86(25)341-3967 +---------------------------------------------------------------- | Anything that can go wrong will go wrong. +----------------------------------------------------------------

1 0

Re: Timezone changes reported in IATA manual
by gwil＠mindspring.com April 7, 1997

April 7, 1997

Chris Carrier <72157.3334(a)CompuServe.COM> wrote: > Gwillim Law > INTERNET:gwil@mindspring.com wrote on the > Subj: Timezone changes reported in IATA manual > > >Brazil has changed the end of DST [...] > > I presume you mean "beginning of DST" rather than end, because all of Brazil > that uses DST is substantially south of the equator, IIRC. You're right, sorry for the slip. -- Gwillim Law Gwillim Law gwil(a)mindspring.com

1 0

suggestion on the timezone lib
by ib＠wupperonline.de April 6, 1997

April 6, 1997

I'm using your timezone package which is great and noticed that during installation a library called 'libz' had been created. Unfortunately that name conflicts with a data compression library (zlib). Wouldn't be 'libtz' a more appropriate name for the library from the (t)ime(z)one packages? Ingo

1 0

zoneinfo data for Slovenia/Ljubljana
by Metod Kozelj April 4, 1997

April 4, 1997

Hello, recently I've had a closer look at the timezone info which is available in with the zoneinfo libraries. I've found an error which concerns our country Slovenia. The info says we used 'fixed' Central European Time until 1983. This is not correct. Law, called 'Law on calculating of time', was adopted in october 1982. It efectively put in power the 'EU' rule and thus in 1983 we already had summer time. Therefore, the section concerning Slovenia/Ljubljana should read like this: > # Slovenia > # Zone NAME GMTOFF RULES FORMAT [UNTIL] > Zone Europe/Ljubljana 0:58:04 - LMT 1884 > 1:00 - CET 1941 Apr 18 23:00 > 1:00 C-Eur CE%sT 1945 May 8 2:00s > 1:00 1:00 CEST 1945 Sep 16 2:00s > 1:00 - CET 1982 > 1:00 EU CE%sT The same error is present in sections for the following states/towns: Yugoslavia/Belgrade Bosnia and Herzegovina/Sarajevo Macedonia/Skopje Croatia/Zagreb as we have all been in the same state at that time. With kind regards, -- Metod Kozelj Hydrometeorological institute of Slovenia mailto:Metod.Kozelj@rzs-hm.si http://www.rzs-hm.si/people/Metod.Kozelj/

1 0

Re: mea culpa
by Dik.Winter＠cwi.nl March 31, 1997

March 31, 1997

> It really is next week when many United States locales change clocks. Your timing was good, your locale was wrong. Europe switched last Sunday. dik

1 0

mea culpa
by ado March 31, 1997

March 31, 1997

It really is next week when many United States locales change clocks. --ado

1 0

Is Your Web Site A Secret?
by owl＠owlsnest.com March 31, 1997

March 31, 1997

Is your web site the best kept secret on the Internet? We'll promote it to 50 search engines and indexes for $85 and complete the job in 2 business days. Satisfaction is guaranteed! If you have a great product, but are not getting many inquiries from your Web site, you may not be adequately listed on the Web's search engines and indexes. Millions of viewers daily use these facilities to find the products and services they are looking for. But if your site is not listed, no one will see it. Listings on most of these services are free. However, locating and filling out the forms required to get a listing can take several days, and most people just don't have the time to do it. That is why we offer a web site promotion service. WHAT'S THE DEAL? We will submit your site to 50 indexes and search engines for $85. We will accept the return of this E-mail, with the form below filled out, as an order. We will bill you upon completion of the promotion. Our terms are net 15 days from date of invoice. Satisfaction guaranteed! HOW LONG WILL IT TAKE? Generally, we complete the submissions within 48 hours of receiving your order. It can take any individual search engine or index up to three weeks to process your submission, although most are much faster. WHAT SEARCH ENGINES AND INDEXES ARE INCLUDED IN THE PROMOTION? The list changes from time to time. This is our current list: Abaweb!, Alta Vista, Been There, BizWeb, Central Source Yellow Pages, Enterpreneurs on the Web, Excite, Four11, Galaxy, I-Network I-Systems Spiral Business Directory, I-World Web Pointer, Infoseek, Inktomi, Innovator's Network Yellow Pages, Internet Mall, Jayde Online Directory, Jumpcity, Jumper Hot Links, Linkmaster, Lycos, Magellan, Mega Mall, Net-Happenings, Net Navigator, Net Mall, NTG's List, NYNEX Big Yellow, One World Plaza, OnLine's WWWeb Index, Rex, Starting Point, Truenorth, URL Tree, Virtual Lynx, Web Point, WebCentral, Web Venture Hotlist, Webcrawler, Websurf, Win Mag/NetGuide Hotspots, WhatUSeek, Worldwide Announce Archive, WWW Business Yellow Pages, World Wide Yellow Pages, WWW Worm, YelloWWWeb. HOW WILL I KNOW THAT YOU HAVE PROMOTED MY SITE? When we have completed the promotion, we will send you an HTML file as an attachment to your E-mail bill. Save this file to your disk, and view it through your Web browser. It provides links to the search engine we submitted your site to, plus any comments we received from them when we did it. ARE THERE ANY GUARANTEES? We do not require prepayment. Your satisfaction is guaranteed or you don't pay the bill. WHO IS OWL'S EYE PRODUCTIONS? We are a web site promotion company located at: Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Phone: (914) 278-4933 Fax: (914) 278-4507 Email: owl(a)owlsnest.com HOW DO I ORDER? The easiest way to order is by e-mail. Just hit the REPLY button on your e-mail program and fill out the following information. (This information will be posted to the search engines/indexes): Your name: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: URL: http:// Site Title: Description (about 25 words): Key words (maximum of 25, in descending order of importance): Proofs (Where shall we e-mail proofs): If billing a different address, please complete the following: Addressee: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: We will bill via Email. (7310) Terms: By returning this document via Email, you agree as follows: You have the authority to purchase this service on behalf of your company. Terms are net 15 days. Accounts sent to collections will be liable for collection costs. You agree to protect and indemnify Owl's Eye Productions, Inc. in any claim for libel, copyright violations, plagiarism, or privacy and other suits or claims based on the content or subject matter of your site. WHAT HAPPENS NEXT? When we receive your order, we will input the information into our system, and send you a proof. After we process any corrections, we will run your promotion, capturing any comments from search engines as we go. We will incorporate these into an HTML-formatted report to you, which we will attach to your bill. ===Web Promotions=====Press Releases=====Link Exchanges========= Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Ph: 914-278-4933 Fx: 914-278-4507 E-mail: owlseye(a)owlsnest.com

1 0

Time zone files in tzdata96i.tar.gz
by Brian Candler March 30, 1997

March 30, 1997

Package: tzdata95i.tar.gz [from RedHat zoneinfo-96i-4.i386.rpm] Symptom: The timezone /usr/lib/zoneinfo/Etc/GMT-6 does not work correctly; if you use it, then set your clock using ntpdate, the system clock is 12 hours out. However if you use a different zoneinfo (e.g. America/Belize) it works fine. I believe the problem is in file "etcetera" in the tzdata package: ... Zone Etc/GMT-6 6 - GMT-6 Zone Etc/GMT-5 5 - GMT-5 Zone Etc/GMT-4 4 - GMT-4 ... Zone Etc/GMT+4 -4 - GMT+4 Zone Etc/GMT+5 -5 - GMT+5 Zone Etc/GMT+6 -6 - GMT+6 ... It appears that the zone offsets in column 3 have the wrong sign - can you check if this is the case? Regards, Brian Candler.

2 1

tzcode1997d.tar.gz and tzdata1997e.tar.gz
by ado March 29, 1997

March 29, 1997

The files ftp://elsie.nci.nih.gov/pub/tzcode1997d.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1997e.tar.gz are now available; these incorporate Paul Eggert's latest suggestions. Remember that many United States locales change clocks within the next 24 hours; if you're affected, be sure to keep your time zone expertise credentials in order. --ado

1 0

proposed changes to tz data from 1997-02 IATA tables, etc.
by Paul Eggert March 29, 1997

March 29, 1997

Here are proposed changes for for the following countries, taken from the changes in the 1997-02 IATA tables reported by Gwillim Law. Brazil Cuba Libya Mongolia New Caledonia Paraguay Sri Lanka [with transition time found via Deja News] This change also incorporates the simpler (and hopefully more accurate) prediction for Israel that I mentioned earlier on this list. Also, it contains commentary updates for several locations (mostly peri-Antarctic islands) that should be self-explanatory, and it adds some new URL references and removes one or two dangling URLs. =================================================================== RCS file: RCS/WWW,v retrieving revision 1996.5 retrieving revision 1996.5.1.1 diff -c -r1996.5 -r1996.5.1.1 *** WWW 1996/01/06 14:08:24 1996.5 --- WWW 1997/03/29 07:34:37 1996.5.1.1 *************** *** 1,6 **** # '@(#)WWW 7.3' ! # From Paul Eggert <eggert(a)twinsun.com> (1995-11-03) # # The Web has several other sources for time zone and daylight savings data. # Here are some recent links that may be of interest. --- 1,6 ---- # '@(#)WWW 7.3' ! # From Paul Eggert <eggert(a)twinsun.com> (1997-03-28) # # The Web has several other sources for time zone and daylight savings data. # Here are some recent links that may be of interest. *************** *** 10,15 **** --- 10,20 ---- # A text-based source for tables of current time throughout the world. # Its point-and-click interface accesses a recent version of the tz data. # + # WORLDTIME: interactive atlas, time info, public holidays + # http://www.worldtime.com/ + # Interactive world atlas with information on local time, sunrise and sunset, + # and public holidays in several hundred cities around the world. + # # Local Times Around the World # http://www.hilink.com.au/times/ # This text-based system contains links to local time servers *************** *** 18,38 **** # # World Time Zones # http://tycho.usno.navy.mil/tzones.html ! # US Naval Observatory data, used as the source for `usno1995'. # # Standard Time Zones of the World ! # http://www.odci.gov/cia/publications/95fact/802389.gif [54 kB] ! # http://www.odci.gov/cia/publications/95fact/802389h.gif [1317 kB] ! # A static time zone map, available in both low-resolution and ! # high-resolution versions. The quality is good, but the map does not ! # indicate summer time, and parts of the data are a few years out of date. ! # ! # VIBE's World Map ! # http://pathfinder.com/vibe/vibeworld ! # An active time zone map. You can point to the map and find out what ! # time it is at that location. The map and data are not as good as ! # other sources. ! ############################################################################### # From Manavendra Thakur <Manavendra_Thakur(a)NeXT.COM> (1995-11-06) --- 23,64 ---- # # World Time Zones # http://tycho.usno.navy.mil/tzones.html ! # US Naval Observatory data, used as the source for the usno* files. # # Standard Time Zones of the World ! # http://www.odci.gov/cia/publications/nsolo/rmap-gif/802483.gif [75 kB] ! # http://www.odci.gov/cia/publications/nsolo/rmap-tif/802483.tif [1 MB] ! # http://www.odci.gov/cia/publications/nsolo/rmap-pdf/802483.pdf [3 MB] ! # A static time zone map, available in multiple resolutions. ! # The quality is good, but the map does not indicate summer time, ! # and parts of the data are a few years out of date. ! # ! # Detailed World Clock information ! # http://www.stud.unit.no/USERBIN/steffent/timezones.pl ! # A map of cities and a list of UTC offsets and current DST rules in each city. ! # ! # The Time of Internet ! # http://pisolo.cstv.to.cnr.it/toi/uk/toi.html ! # Good descriptions of Time Zones and daylight savings time, with diagrams. ! # The time zone map is out of date, however. ! # ! # A Few Facts Concerning RGO, GMT, and UT, by Richard B. Langley ! # http://community.bellcore.com/mbr/gmt-explained.html ! # This answers questions like ``What is the difference between GMT and UTC?'' ! # ! # Daylight Saving Time -- Saving Time, Saving Energy ! # http://www.energy.ca.gov/energy/daylightsaving.html ! # A history of DST in the US. ! # ! # Yahoo! - Science:Weights and Measures:Measurements:Time:Daylight Savings Time ! # http://www.yahoo.com/Science/Weights_and_Measures/Measurements/Time/Dayligh… ! # The famous Internet indexing service Yahoo! collects its time zone info here. ! # ! # International Air Transport Association ! # http://www.iata.org/ ! # The source for the IATA SSIM, which gives current time zone rules for ! # all the airports served by commercial aviation. ! # ############################################################################### # From Manavendra Thakur <Manavendra_Thakur(a)NeXT.COM> (1995-11-06) =================================================================== RCS file: RCS/africa,v retrieving revision 1996.13 retrieving revision 1996.13.1.1 diff -c -r1996.13 -r1996.13.1.1 *** africa 1996/11/24 01:07:36 1996.13 --- africa 1997/03/29 07:34:37 1996.13.1.1 *************** *** 403,410 **** Rule Libya 1987 1989 - Apr 1 0:00 1:00 S Rule Libya 1987 1990 - Oct 1 0:00 0 - Rule Libya 1990 only - May 4 0:00 1:00 S ! Rule Libya 1996 max - Mar 30 2:00s 1:00 S ! Rule Libya 1996 max - Sep 30 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 1:00 Libya CE%sT 1959 --- 403,412 ---- Rule Libya 1987 1989 - Apr 1 0:00 1:00 S Rule Libya 1987 1990 - Oct 1 0:00 0 - Rule Libya 1990 only - May 4 0:00 1:00 S ! Rule Libya 1996 only - Mar 30 2:00s 1:00 S ! Rule Libya 1996 only - Sep 30 2:00s 0 - ! Rule Libya 1997 max - Mar lastThu 2:00s 1:00 S ! Rule Libya 1997 max - Oct Thu>=1 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 1:00 Libya CE%sT 1959 *************** *** 525,533 **** -0:06 - SHT 1951 # St Helena Time (?) 0:00 - GMT # The other parts of the St Helena territory are similar: ! # Tristan da Cunha: on GMT, says Whitman ! # Ascension: on GMT, says usno1995 ! # Gough, Inaccessible, Nightingale: no information, but probably GMT # Sao Tome and Principe # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 527,536 ---- -0:06 - SHT 1951 # St Helena Time (?) 0:00 - GMT # The other parts of the St Helena territory are similar: ! # Tristan da Cunha: on GMT, say Whitman and the CIA ! # Ascension: on GMT, says usno1995 and the CIA ! # Gough (scientific station since 1955): on GMT, says the CIA ! # Inaccessible, Nightingale: no information, but probably GMT # Sao Tome and Principe # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 577,583 **** Zone Africa/Johannesburg 1:52:00 - LMT 1892 Feb 8 1:30 - SAT 1903 Mar 2:00 SA SA%sT ! # Prince Edward Is # no information # Sudan --- 580,587 ---- Zone Africa/Johannesburg 1:52:00 - LMT 1892 Feb 8 1:30 - SAT 1903 Mar 2:00 SA SA%sT ! # Marion and Prince Edward Is ! # weather station since 1947 # no information # Sudan =================================================================== RCS file: RCS/antarctica,v retrieving revision 1997.3 retrieving revision 1997.3.1.1 diff -c -r1997.3 -r1997.3.1.1 *** antarctica 1997/03/03 17:21:51 1997.3 --- antarctica 1997/03/29 07:34:37 1997.3.1.1 *************** *** 1,8 **** # @(#)antarctica 7.7 ! # From Paul Eggert (1997-01-20): # To keep things manageable, we list only locations occupied year-round; ! # see <URL:http://earth.agu.org/amen/nations.html> (1996-05-24). # Unless otherwise specified, we have no time zone information. # # Except for the French entries, --- 1,9 ---- # @(#)antarctica 7.7 ! # From Paul Eggert (1997-03-28): # To keep things manageable, we list only locations occupied year-round; ! # see <URL:http://earth.agu.org/amen/nations.html> (1996-05-24) ! # and <URL:http://www.spri.cam.ac.uk/bob/periant.htm> (1996-09-05). # Unless otherwise specified, we have no time zone information. # # Except for the French entries, *************** *** 29,35 **** # 5 others # Australia - territories ! # Heard Island, McDonald Islands # # year-round bases # Casey, Bailey Peninsula, since 1969 --- 30,36 ---- # 5 others # Australia - territories ! # Heard Island, McDonald Islands (uninhabited) # # year-round bases # Casey, Bailey Peninsula, since 1969 *************** *** 70,78 **** # # Martin-de-Vivies Base, Amsterdam Island, -374105+0773155, since 1950 # Alfred-Faure Base, Crozet Islands, -462551+0515152, since 1964 ! # Port-aux-Francais, Kerguelen Islands, -492110+0701303, since 1951 # ! # St Paul Island - near Amsterdam, uninhabited since 1927 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Kerguelen 0 - ___ 1950 # Port-aux-Francais --- 71,80 ---- # # Martin-de-Vivies Base, Amsterdam Island, -374105+0773155, since 1950 # Alfred-Faure Base, Crozet Islands, -462551+0515152, since 1964 ! # Port-aux-Francais, Kerguelen Islands, -492110+0701303, since 1951; ! # a whaling and sealing station operated 1908-14, 1920-29, and 1951-56 # ! # St Paul Island - near Amsterdam, uninhabited since 1931 # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Kerguelen 0 - ___ 1950 # Port-aux-Francais *************** *** 107,114 **** # King Sejong, King George Island, since 1988 # New Zealand - claims ! # Balleny Islands ! # Scott Island # # year-round base # Scott, Ross Island, since 1957-01, is like Antarctica/McMurdo. --- 109,116 ---- # King Sejong, King George Island, since 1988 # New Zealand - claims ! # Balleny Islands (never inhabited) ! # Scott Island (never inhabited) # # year-round base # Scott, Ross Island, since 1957-01, is like Antarctica/McMurdo. *************** *** 124,133 **** Rule NZAQ 1990 max - Mar Sun>=15 2:00s 0 S # Norway - territories ! # Bouvet (uninhabited) # # claims ! # Peter I Island (uninhabited) # Poland - year-round base # Arctowski, King George Island, since 1977 --- 126,135 ---- Rule NZAQ 1990 max - Mar Sun>=15 2:00s 0 S # Norway - territories ! # Bouvet (never inhabited) # # claims ! # Peter I Island (never inhabited) # Poland - year-round base # Arctowski, King George Island, since 1977 *************** *** 147,153 **** --- 149,159 ---- # # British Antarctic Territories (BAT) claims # South Orkney Islands + # scientific station from 1903 + # whaling station at Signy I 1920-1926 # South Shetland Islands + # whaling station at Deception I 1912-1931 + # scientific station from 1943 # # year-round bases # Halley, Coates Land, -7535-2619, since 1956-01-06 =================================================================== RCS file: RCS/asia,v retrieving revision 1997.3 retrieving revision 1997.3.1.2 diff -c -r1997.3 -r1997.3.1.2 *** asia 1997/03/04 14:58:18 1997.3 --- asia 1997/03/29 07:34:37 1997.3.1.2 *************** *** 508,515 **** # From Ephraim Silverberg (ephraim(a)cs.huji.ac.il) 1997-03-04: - # Zone Information Compiler (ZIC) File for the State of Israel (1989-2009) - # According to the Office of the Secretary General of the Ministry of # Interior, there is NO set rule for Daylight-Savings/Standard time changes. # Each year they decide anew what havoc to wreak on the country. However, --- 508,513 ---- *************** *** 525,551 **** # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0:00 S ! Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0:00 S ! Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0:00 S ! Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0:00 S ! Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0:00 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0:00 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0:00 S # The dates for 1996 were determined by the Minister of Interior of the # time, Haim Ramon. The official announcement regarding 1996-1998 --- 523,549 ---- # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0 S ! Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0 S ! Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0 S ! Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0 S ! Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0 S # The dates for 1996 were determined by the Minister of Interior of the # time, Haim Ramon. The official announcement regarding 1996-1998 *************** *** 560,599 **** # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1996 only - Mar 15 0:00 1:00 D ! Rule Zion 1996 only - Sep 16 0:00 0:00 S ! Rule Zion 1997 only - Mar 21 0:00 1:00 D ! Rule Zion 1997 only - Sep 14 0:00 0:00 S ! Rule Zion 1998 only - Mar 20 0:00 1:00 D ! Rule Zion 1998 only - Oct 18 0:00 0:00 S ! ! # These rules are probably wrong, but they are close approximations (usually ! # within a few weeks): ! ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1999 only - Apr 11 0:00 1:00 D ! Rule Zion 1999 only - Sep 5 0:00 0:00 S ! Rule Zion 2000 only - Apr 30 0:00 1:00 D ! Rule Zion 2000 only - Sep 24 0:00 0:00 S ! Rule Zion 2001 only - Apr 15 0:00 1:00 D ! Rule Zion 2001 only - Sep 9 0:00 0:00 S ! Rule Zion 2002 only - Apr 7 0:00 1:00 D ! Rule Zion 2002 only - Sep 1 0:00 0:00 S ! Rule Zion 2003 only - Apr 27 0:00 1:00 D ! Rule Zion 2003 only - Sep 21 0:00 0:00 S ! Rule Zion 2004 only - Apr 18 0:00 1:00 D ! Rule Zion 2004 only - Sep 12 0:00 0:00 S ! Rule Zion 2005 only - May 1 0:00 1:00 D ! Rule Zion 2005 only - Sep 25 0:00 0:00 S ! Rule Zion 2006 only - Apr 23 0:00 1:00 D ! Rule Zion 2006 only - Sep 17 0:00 0:00 S ! Rule Zion 2007 only - Apr 15 0:00 1:00 D ! Rule Zion 2007 only - Sep 9 0:00 0:00 S ! Rule Zion 2008 only - Apr 27 0:00 1:00 D ! Rule Zion 2008 only - Sep 21 0:00 0:00 S ! Rule Zion 2009 only - Apr 19 0:00 1:00 D ! Rule Zion 2009 only - Sep 13 0:00 0:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 --- 558,577 ---- # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule Zion 1996 only - Mar 15 0:00 1:00 D + Rule Zion 1996 only - Sep 16 0:00 0 S + Rule Zion 1997 only - Mar 21 0:00 1:00 D + Rule Zion 1997 only - Sep 14 0:00 0 S + Rule Zion 1998 only - Mar 20 0:00 1:00 D + Rule Zion 1998 only - Oct 18 0:00 0 S + + # From Paul Eggert (1997-03-15): + # Here are guesses for rules after 1998. + # They are probably wrong, but they are more likely than no DST at all. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1999 max - Mar Fri>=15 0:00 1:00 D ! Rule Zion 1999 max - Sep Sun>=15 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 *************** *** 810,816 **** Rule Mongol 1985 1990 - Sep lastSun 3:00 0 - Rule Mongol 1991 max - Mar lastSun 0:00 1:00 S Rule Mongol 1991 1995 - Sep lastSun 0:00 0 - ! Rule Mongol 1996 max - Oct Fri>=22 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug # 6:00 - DART 1978 # Dariv Time --- 788,795 ---- Rule Mongol 1985 1990 - Sep lastSun 3:00 0 - Rule Mongol 1991 max - Mar lastSun 0:00 1:00 S Rule Mongol 1991 1995 - Sep lastSun 0:00 0 - ! Rule Mongol 1996 only - Oct Fri>=22 0:00 0 - ! Rule Mongol 1997 max - Sep lastSun 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug # 6:00 - DART 1978 # Dariv Time *************** *** 909,914 **** --- 888,898 ---- # reported ``the country's standard time will be put forward by one hour at # midnight Friday (1830 GMT) `in the light of the present power crisis'.'' # Transitions before 1996 are from Shanks (1991). + # + # From Dharmasiri Senanayake, Sri Lanka Media Minister (1996-10-24), as quoted + # in <URL:news:54rka5$m5h@mtinsc01-mgt.ops.worldnet.att.net> (1996-10-26): + # With effect from 12.30 a.m. on 26th October 1996 + # Sri Lanka will be six (06) hours ahead of GMT. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Colombo 5:19:24 - LMT 1880 *************** *** 917,923 **** 5:30 0:30 IHST 1942 Sep 5:30 1:00 IST 1945 Oct 16 2:00 5:30 - IST 1996 May 25 0:00 ! 6:30 - LKT # Sri Lanka Time # Syria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 901,908 ---- 5:30 0:30 IHST 1942 Sep 5:30 1:00 IST 1945 Oct 16 2:00 5:30 - IST 1996 May 25 0:00 ! 6:30 - LKT 1996 Oct 26 0:30 ! 6:00 - LKT # Syria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S =================================================================== RCS file: RCS/australasia,v retrieving revision 1997.1 retrieving revision 1997.1.2.1 diff -c -r1997.1 -r1997.1.2.1 *** australasia 1997/01/21 14:11:10 1997.1 --- australasia 1997/03/29 07:40:34 1997.1.2.1 *************** *** 170,176 **** # no indigenous inhabitants; only meteorologists # no information # ! # Macquarie, Manihiki, Penrhyn, Rakehanga # no information --- 170,181 ---- # no indigenous inhabitants; only meteorologists # no information # ! # Macquarie ! # permanent occupation (scientific station) since 1948; ! # sealing and penguin oil station operated 1888-1917 ! # no information ! # ! # Manihiki, Penrhyn, Rakehanga # no information *************** *** 277,282 **** --- 282,290 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule NC 1977 1978 - Dec Sun>=1 0:00 1:00 S Rule NC 1978 1979 - Feb 27 0:00 0 - + Rule NC 1996 only - Dec 1 2:00s 1:00 S + Rule NC 1997 max - Mar Sun>=1 2:00s 0 - + Rule NC 1997 max - Nov lastSun 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Noumea 11:05:48 - LMT 1912 Jan 13 11:00 NC NC%sT *************** *** 315,322 **** Zone Pacific/Chatham 12:45 Chatham CHA%sT ! # Antipodes Is, Kermadec Is ! # uninhabited except by research personnel; probably like Pacific/Auckland ############################################################################### --- 323,335 ---- Zone Pacific/Chatham 12:45 Chatham CHA%sT ! # Auckland Is ! # uninhabited ! ! # Campbell I ! # minor whaling stations operated 1909-14 ! # scientific station operated 1941-1995 ! # was probably like Pacific/Auckland ############################################################################### =================================================================== RCS file: RCS/europe,v retrieving revision 1996.14 retrieving revision 1996.14.1.1 diff -c -r1996.14 -r1996.14.1.1 *** europe 1996/12/28 02:42:05 1996.14 --- europe 1997/03/29 07:34:37 1996.14.1.1 *************** *** 630,639 **** # came into force on 16 November. It restates the dates from the EC # seventh Summer Time Directive.... # ! # From Peter Ilieve <peter(a)aldie.co.uk> (1996-04-20): ! # Proposals for the eighth directive were supposed to have been produced ! # by the Commission by 1 Jan 96. They have not yet appeared (I asked just ! # before Easter). # From Peter Ilieve <peter(a)memex.co.uk> (1994-03-28): # The [GB-Eire] end date of 22 October [1995] conflicts with your current rule --- 630,647 ---- # came into force on 16 November. It restates the dates from the EC # seventh Summer Time Directive.... # ! # From Peter Ilieve <peter(a)aldie.co.uk> (1997-03-28): ! # The [European] Transport Council discussed the proposed Eighth Directive ! # on 11 March and agreed [to] it, so it moves forward to the next stage, ! # from a Commission proposal to a Common Position.... What this means is: ! # ! # - The eighth directive proposal rules have been accepted. ! # These are the same as the current rules (last Sunday in March and last ! # Sunday in October). The rules will run until 2001. ! # ! # - The French have had their request to abandon summer time turned down. ! # They have been promised some sort of review in 1999 which might change ! # the rules for 2000 and 2001. # From Peter Ilieve <peter(a)memex.co.uk> (1994-03-28): # The [GB-Eire] end date of 22 October [1995] conflicts with your current rule =================================================================== RCS file: RCS/northamerica,v retrieving revision 1996.14 retrieving revision 1996.14.1.1 diff -c -r1996.14 -r1996.14.1.1 *** northamerica 1996/12/28 02:42:05 1996.14 --- northamerica 1997/03/29 07:34:37 1996.14.1.1 *************** *** 1141,1154 **** Rule Cuba 1972 1974 - Oct 8 0:00 0 S Rule Cuba 1975 1977 - Oct lastSun 0:00 0 S Rule Cuba 1978 only - May 7 0:00 1:00 D ! Rule Cuba 1978 1980 - Oct Sun>=8 0:00 0 S Rule Cuba 1979 1980 - Mar Sun>=15 0:00 1:00 D Rule Cuba 1981 1985 - May Sun>=5 0:00 1:00 D - Rule Cuba 1981 1990 - Oct Sun>=8 0:00 0 S Rule Cuba 1986 1989 - Mar Sun>=14 0:00 1:00 D Rule Cuba 1990 max - Apr Sun>=1 0:00 1:00 D Rule Cuba 1991 1995 - Oct Sun>=8 0:00s 0 S ! Rule Cuba 1996 max - Oct Sun>=1 0:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Havana -5:29:28 - LMT 1890 --- 1141,1154 ---- Rule Cuba 1972 1974 - Oct 8 0:00 0 S Rule Cuba 1975 1977 - Oct lastSun 0:00 0 S Rule Cuba 1978 only - May 7 0:00 1:00 D ! Rule Cuba 1978 1990 - Oct Sun>=8 0:00 0 S Rule Cuba 1979 1980 - Mar Sun>=15 0:00 1:00 D Rule Cuba 1981 1985 - May Sun>=5 0:00 1:00 D Rule Cuba 1986 1989 - Mar Sun>=14 0:00 1:00 D Rule Cuba 1990 max - Apr Sun>=1 0:00 1:00 D Rule Cuba 1991 1995 - Oct Sun>=8 0:00s 0 S ! Rule Cuba 1996 only - Oct Sun>=1 0:00s 0 S ! Rule Cuba 1997 max - Oct Sun>=8 0:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Havana -5:29:28 - LMT 1890 =================================================================== RCS file: RCS/southamerica,v retrieving revision 1996.14 retrieving revision 1996.14.1.1 diff -c -r1996.14 -r1996.14.1.1 *** southamerica 1996/12/28 02:42:05 1996.14 --- southamerica 1997/03/29 07:34:37 1996.14.1.1 *************** *** 267,276 **** Rule Brazil 1990 1991 - Feb Sun>=11 0:00 0 S Rule Brazil 1990 1992 - Oct Sun>=20 0:00 1:00 D Rule Brazil 1992 only - Feb 9 0:00 0 S ! Rule Brazil 1993 max - Oct Sun>=11 0:00 1:00 D Rule Brazil 1993 only - Jan 31 0:00 0 S Rule Brazil 1994 1995 - Feb Sun>=15 0:00 0 S Rule Brazil 1996 max - Feb Sun>=11 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] # --- 267,277 ---- Rule Brazil 1990 1991 - Feb Sun>=11 0:00 0 S Rule Brazil 1990 1992 - Oct Sun>=20 0:00 1:00 D Rule Brazil 1992 only - Feb 9 0:00 0 S ! Rule Brazil 1993 1995 - Oct Sun>=11 0:00 1:00 D Rule Brazil 1993 only - Jan 31 0:00 0 S Rule Brazil 1994 1995 - Feb Sun>=15 0:00 0 S Rule Brazil 1996 max - Feb Sun>=11 0:00 0 S + Rule Brazil 1996 max - Oct Sun>=1 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] # *************** *** 434,442 **** Rule Para 1992 only - Mar 1 0:00 0 - Rule Para 1992 only - Oct 5 0:00 1:00 S Rule Para 1993 only - Mar 31 0:00 0 - ! Rule Para 1993 max - Oct 1 0:00 1:00 S Rule Para 1994 1995 - Feb lastSun 0:00 0 - Rule Para 1996 max - Mar 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 -3:50:40 - AMT 1931 Oct 10 # Asuncion Mean Time --- 435,445 ---- Rule Para 1992 only - Mar 1 0:00 0 - Rule Para 1992 only - Oct 5 0:00 1:00 S Rule Para 1993 only - Mar 31 0:00 0 - ! Rule Para 1993 1995 - Oct 1 0:00 1:00 S Rule Para 1994 1995 - Feb lastSun 0:00 0 - Rule Para 1996 max - Mar 1 0:00 0 - + Rule Para 1996 only - Oct 6 0:00 1:00 S + Rule Para 1997 max - Oct 1 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 -3:50:40 - AMT 1931 Oct 10 # Asuncion Mean Time

1 0

Timezone changes reported in IATA manual
by gwil＠mindspring.com March 29, 1997

March 29, 1997

I've received the February 1997 edition of the Standard Schedules Information Manual, published by the International Air Transport Association (IATA). This manual has an appendix of international time zone information, which is intended for use by member airlines in generating and interpreting their service schedules. I compared it line by line with the previous (September 1996) edition. This is a report on the differences. In the following table, "edit" is the date of the edition. "zon" is a code for the time zone, consisting of the ISO 3166 country code followed by a digit, where necessary, to distinguish between different zones in the same country. "stdoff" and "dstoff" are the offsets from GMT to standard time and daylight saving time in the zone, respectively. The rest of each line consists of two pairs of consecutive dates for the beginning and end of daylight saving time in the zone, expressed in UTC (without the century, to save space). For time zones that don't observe DST, the last five columns are blank. For countries in the Southern Hemisphere, the four dates represent the same years. For countries in the Northern Hemisphere, the last two dates reported in the 9/96 manual correspond to the first two dates in the 2/97 manual. To help compare the two rows, I've flagged the items in the second row that differ from the first row, or from what you would expect to find in the continuation of the first row. I hope that line wrapping won't make this table too hard to read. edit zon stdoff dstoff 1st dst start 1st dst end 2nd dst start 2nd dst end ---- --- ------ ------ --------------- --------------- --------------- --------------- 9/96 BR1 -3:00 -2:00 Oct 13 96 03:00 Feb 16 97 02:00 Oct 12 97 03:00 Feb 15 98 02:00 2/97 BR1 -3:00 -2:00 Oct 6 96 03:00 Feb 16 97 02:00 Oct 5 97 03:00 Feb 15 98 02:00 ^^ ^^ 9/96 BR2 -4:00 -3:00 Oct 13 96 04:00 Feb 16 97 03:00 Oct 12 97 04:00 Feb 15 98 03:00 2/97 BR2 -4:00 -3:00 Oct 6 96 04:00 Feb 16 97 03:00 Oct 5 97 04:00 Feb 15 98 03:00 ^^ ^^ 9/96 CL1 -4:00 -3:00 Oct 13 96 04:00 Mar 9 97 03:00 Oct 12 97 04:00 Mar 8 98 03:00 2/97 CL1 -4:00 -3:00 Oct 13 96 04:00 Mar 9 97 03:00 Oct 12 97 04:00 Mar 15 98 03:00 ^^ 9/96 CL2 -6:00 -5:00 Oct 13 96 06:00 Mar 9 97 05:00 Oct 12 97 06:00 Mar 8 98 05:00 2/97 CL2 -6:00 -5:00 Oct 13 96 06:00 Mar 9 97 05:00 Oct 12 97 06:00 Mar 15 98 05:00 ^^ 9/96 CU -5:00 -4:00 Apr 7 96 05:00 Oct 6 96 05:00 Apr 6 97 05:00 Oct 5 97 05:00 2/97 CU -5:00 -4:00 Apr 6 97 05:00 Oct 12 97 05:00 Apr 5 98 05:00 Oct 11 98 05:00 ^^ ^^ 9/96 GE 4:00 5:00 Mar 30 96 20:00 Oct 26 96 19:00 Mar 29 97 20:00 Oct 25 97 19:00 2/97 GE 5:00 9/96 IL 2:00 3:00 Mar 14 96 22:00 Sep 15 96 21:00 Mar 13 97 22:00 Sep 14 97 21:00 2/97 IL 2:00 3:00 Mar 13 97 22:00 Oct 18 97 21:00 Mar 19 98 22:00 Oct 17 98 21:00 ^^^^^^ ^^^^^^ 9/96 KI2 -10:00 2/97 KI2 14:00 ^^^^^^ 9/96 KI3 -11:00 2/97 KI3 13:00 ^^^^^^ 9/96 KG 5:00 6:00 Apr 13 96 19:00 Sep 28 96 18:00 Apr 12 97 19:00 Sep 27 97 18:00 2/97 KG 5:00 6:00 Apr 12 97 19:00 Sep 27 97 18:00 Apr 11 98 19:00 Oct 26 98 18:00 ^^^^^^ 9/96 LY 1:00 2:00 Mar 30 96 01:00 Sep 30 96 01:00 Mar 30 97 01:00 Sep 30 97 01:00 2/97 LY 1:00 2:00 Mar 27 97 01:00 Oct 2 97 01:00 Mar 26 98 01:00 Oct 1 98 01:00 ^^^^^^ ^^^^^^ ^^^^^^ ^^^^^^ 9/96 MN 8:00 9:00 Mar 30 96 16:00 Oct 24 96 15:00 Mar 29 97 16:00 Oct 23 97 15:00 2/97 MN 8:00 9:00 Mar 29 97 16:00 Sep 27 97 15:00 Mar 28 98 16:00 Sep 26 98 15:00 ^^^^^^ ^^^^^^ 9/96 NC 11:00 2/97 NC 11:00 12:00 Nov 30 96 15:00 Mar 1 97 15:00 Nov 29 97 15:00 Mar 7 98 15:00 9/96 PY -4:00 -3:00 Oct 1 96 04:00 Mar 1 97 03:00 Oct 1 97 04:00 Mar 1 98 03:00 2/97 PY -4:00 -3:00 Oct 6 96 04:00 Mar 1 97 03:00 Oct 1 97 04:00 Mar 1 98 03:00 ^^ 9/96 LK 6:30 2/97 LK 6:00 9/96 UA1 2:00 3:00 Mar 31 96 01:00 Oct 27 96 01:00 Mar 30 97 01:00 Oct 26 97 01:00 2/97 UA1 2:00 3:00 Mar 30 97 03:00 Oct 26 97 04:00 Mar 29 98 03:00 Oct 25 98 04:00 ^^^^^ ^^^^^ ^^^^^ ^^^^^ Descriptions of the changes shown in these manuals are as follows. I've had to make assumptions in order to state the rules. All I can say for sure is that they're consistent with the data. The rules are expressed in local time, with midnight counting as the following day. Brazil has changed the end of DST from the second to the first Sunday in October, starting in 1996. (Actually, the rule implied by previous manuals was Oct Sun>10 or Sun>11, from 1993 to 1997.) Chile has changed the end of DST from the second to the third Sunday in March, starting in 1998. Cuba has changed the end of DST from Oct Sun>4 to Sun>5 (or more), starting in 1997. Georgia has gone on year-round standard time using its former DST offset, probably by failing to change the clocks back in October, 1996. Israel has changed the end of DST from the third Monday in September to the third Sunday in October, starting in 1997. The parts of Kiribati that were east of the International Date Line have set their calendars ahead one day, so that at most times Kiribati will have a uniform date. There's no evidence in the manuals as to when this took effect, but it's also been reported in the news. Kyrgyzstan has changed the end of DST from the last Sunday in September to the last Tuesday in October, starting in 1998. This may be a typo in the manual. If it said Sep 26 instead of Oct 26, that would be consistent with the old rule. Besides, Tuesday is a rather unusual day for DST to end on. Libya has changed the start and end of DST from fixed dates to the last Thursday in March and the first Thursday in October, respectively, starting in 1997. Mongolia has changed the end of DST from the fourth Friday in October to the fourth Sunday in September, starting in 1997. (The October rule only lasted for one year, 1996.) New Caledonia has adopted DST, beginning December 1, 1996 (local time). Paraguay started DST on October 6 instead of October 1 in 1996 only. Sri Lanka has set its clocks back a half hour. There's no evidence in the manuals as to when this took effect. Ukraine, except for Symferopol, has changed the time at which DST begins to 05:00, and the end time to 07:00 (local time). This is rather unusual, and I suspect an error in the manual. There were three other entries in the manual where I am convinced that IATA made an error. I fixed the errors and didn't list them as changes above. Just for the record, here they are. The manual says that: (1) Gibraltar has moved its winter time an hour earlier, but not its summer time, so that in the winter it matches the United Kingdom and in the Summer it matches mainland Spain, with a two-hour change each time. (2) DST ends one day earlier in Kaliningrad Oblast than in the rest of Russia, although it starts on the same day and hour. This is an error that has occurred in previous editions. When the times are expressed in UTC, Kaliningrad is the only one that changes at or after midnight, so the error is easily explained. Someone copied the date for all the Russian entries without noticing that it should have been the following date in Kaliningrad. (3) In Symferopol, the offset from UTC to standard time is three hours. The manual reports that the offset for DST is four hours in 1997, but three hours in 1998. If that were really true, there would be no point in their reporting the DST start and end dates for 1998, because DST would be the same as standard. Note to Paul Eggert: I'll send you new files with these changes incorporated as soon as I have time (probably not in the next week). -- Gwillim Law Gwillim Law gwil(a)mindspring.com

2 1

Progress on summer time directive for the European Union
by peter＠aldie.co.uk March 28, 1997

March 28, 1997

The Transport Council discussed the proposed Eighth Directive on 11 March and agreed it, so it moves forward to the next stage, from a Commission proposal to a Common Position. Many EU documents are now available on the WWW as the EU have opened the previously subscription only RAPID database to everyone. The report of this transport council took a while to arrive but it is there now. RAPID as available at http://europa.eu.int/en/comm/spp/rapid.html The document reference is PRES/97/70, or you can search for `transport council', or you can try the following long URL for the English text version: http://europa.eu.int/rapid/cgi/rapcgi.ksh?p_action.gettxt=gt&doc=PRES/97/70… It is available in PDF as well, and also in French. The section about Summer Time is quoted below: --------- SUMMER-TIME ARRANGEMENTS The Council reached political agreement by a qualified majority, with France voting against, on a common position prior to adoption of the eighth Directive on summer-time arrangements. Once formally adopted, the common position will be forwarded to the European Parliament for a second reading, in accordance with the co-decision procedure. The aim of the eighth Directive is to harmonize the dates and times for the beginning and end of summer time throughout the Community for the period from 1998 to 2001. In addition, the Council and the Commission approved the following joint declaration: "The Council and the Commission consider that the social and economic implications of the decisions concerning summer-time arrangements justify thorough examination, which will be effected before the eighth Directive elapses. For this purpose, the Commission will forward a detailed report to the Council by 30 June 1999 at the latest, and the Council and the Commission agree to carry out, with the aid of a group comprising representatives of interest groups and Member States' national experts, an in-depth examination of the implications of applying summer-time arrangements, including the institutional aspects of coordination of times between the Member States of the European Union." Furthermore, the United Kingdom made the following unilateral statement: "The United Kingdom states that, while it has no difficulties with the substance of the proposed eighth summer-time Directive, on subsidiarity grounds it considers that Member States' summer-time arrangements would be best addressed in a Recommendation." --------- What this means is: - The eighth directive proposal rules have been accepted. These are the same as the current rules (last Sunday in March and last Sunday in October). The rules will run until 2001. - The French have had their request to abandon summer time turned down. They have been promised some sort of review in 1999 which might change the rules for 2000 and 2001. I personally doubt that anything will happen before a ninth directive as there won't be the time to go though all the necessary steps between 30 June 1999 and March 2000. These people have no sense of deadlines and they will probably all be caught up in Millennium projects by then anyway. - The UK were just stirring things up. Subsidiarity is a Maastricht Treaty buzzword meaning that member states should be free to decide things for themselves unless it is really necessary for things to be done at a European level. A Recommendation rather than a Directive would allow states to ignore it and France could abandon summer time if it felt like it. It is interesting to see the UK using this subsidiarity argument as by doing so they are saying that there is no need to harmonise time arrangements in Europe. This means they will not be able to use the harmonisation argument next time the question of changing the UK's timezone comes up. The next stage is to let the European Parliament have their say, although I don't think they have the power to amend it. Then it is finally confirmed by the Council. This probably won't happen until May. The UK government then has to pass a Staturary Instrument to implement the Directive. My guess is that they won't manage this before Parliament rises for the summer recess so it won't happen until about October. Peter Ilieve peter(a)aldie.co.uk

1 0

Comments on update
by Chris Carrier March 28, 1997

March 28, 1997

Gwillim Law > INTERNET:gwil@mindspring.com wrote on the Subj: Timezone changes reported in IATA manual >I've received the February 1997 edition of the Standard Schedules >Information Manual, published by the International Air Transport >Association (IATA). This manual has an appendix of international time zone >information, which is intended for use by member airlines in generating and >interpreting their service schedules. I compared it line by line with the >previous (September 1996) edition. This is a report on the differences. Thank you for your report. >Brazil has changed the end of DST from the second to the first Sunday in >October, starting in 1996. (Actually, the rule implied by previous manuals >was Oct Sun>10 or Sun>11, from 1993 to 1997.) I presume you mean "beginning of DST" rather than end, because all of Brazil that uses DST is substantially south of the equator, IIRC. >Georgia has gone on year-round standard time using its former DST offset, >probably by failing to change the clocks back in October, 1996. This may have been only a one-year thing, as I remember someone quoting Georgia's President, Schevrednaze (I believe that is the spelling) saying that Georgia would be remaining on DST "this winter" (1996-7) "to save energy." Anyone heard anything about permanent change in Georgia? >Kyrgyzstan has changed the end of DST from the last Sunday in September to >the last Tuesday in October, starting in 1998. This may be a typo in the >manual. If it said Sep 26 instead of Oct 26, that would be consistent with >the old rule. Besides, Tuesday is a rather unusual day for DST to end on. I tend to think typo as well, but they may have changed to the last Sunday in October; as you said, Tuesday is an unusual day for a time change. >Sri Lanka has set its clocks back a half hour. There's no evidence in the >manuals as to when this took effect. Which should make its most famous citizen very happy! (Arthur C. Clarke has been advocating this for >30 years.) >There were three other entries in the manual where I am convinced that IATA >made an error. I fixed the errors and didn't list them as changes above. >Just for the record, here they are. The manual says that: >(1) Gibraltar has moved its winter time an hour earlier, but not its summer >time, so that in the winter it matches the United Kingdom and in the Summer >it matches mainland Spain, with a two-hour change each time. I actually believe this may not be an error. I called up AT&T International Operator twice on two successive nights and they said they have no listing for Gibraltar. I asked for the time in Morocco and was given GMT. Now given that Gibraltar is a British possession and is next to both Morocco and Spain, I can see them staying on GMT in winter and Spanish time in summer. To move in one year from standard time to two hours of DST and back to standard, either in one jump (Newfoundland 1988) or in two one hour jumps (UK 1947) can happen from time to time. BTW, I'm less convinced than I used to be of the infallibility of AT&T, although I still consider it to be the best source available for current time data. This is because they moved the EU back to standard time on 1996 Sep 29, and a couple of weeks later, moved them back ahead, only to then move them back on the actual date of October 27. Would like to ask: is Mexico going to go on DST in 1997 and after? Chris Carrier

1 0

Re: Commentary on time zone policy
by ncm＠cantrip.org March 25, 1997

March 25, 1997

Chris Carrier writes: > Nathan Myers > INTERNET:ncm@cantrip.org wrote: > >... And all such divisions are completely irrelevant, because nobody who > >decides about time zone law reads this list. ... > > I don't see anything wrong with including commentary on various actual and > proposed changes. I apologize for sounding testy. It's frustrating enough keeping up with all the foolishness of law without entertaining suggestions for policy improvements we have no hint of authority to act on. This list is the place changes to the tz database are discussed, and we those of us who follow it must subscribe to keep informed. I meant the suggestion to post in a more appropriate place seriously: your wise analysis is wasted where no reader can act on it. I also meant seriously the suggestion to start a more appropriate list. People who understand politics should be involved, and they are not here. Nathan Myers ncm(a)cantrip.org

1 0

Commentary on time zone policy
by Chris Carrier March 25, 1997

March 25, 1997

I wrote: >>The current list is divided many ways as to what relationship local mean >>time (LMT) should have to local clock time (LCT). ... Nathan Myers > INTERNET:ncm@cantrip.org wrote: >... And all such divisions are completely irrelevant, because nobody who >decides about time zone law reads this list. You do not know that to be a fact, and if some of the more active people on this list have their way, persons in positions to make such decisions will be using this as a resource base. >Please take your opinions about national time zone policies someplace where >they will make a difference. I don't see anything wrong with including commentary on various actual and proposed changes. It is within the scope of this list, or at least not totally irrelevant to time zoning. That I voted for candidate X because I liked his stand on non-time-zone issue Y is irrelevant to this list; opinions on time zoning issues are not, have come from more people than just myself, (you may note that I was replying to another proposal in my post) and are, AFAIK, welcome from the people who run this list. Chris Carrier

1 0

Re: DST switching dates
by ncm＠cantrip.org March 22, 1997

March 22, 1997

> Nathan Myers > INTERNET:ncm@cantrip.org wrote: > > >Clearly the only sensible approach to time would be [something] > > ... However, it's a > >waste of everybody's time and attention to discuss this here. We techies > >are constrained to chase after whatever foolish decisions are made in the > >parliaments and politburos of world. This list is about details of that > >chase. From: Chris Carrier <72157.3334(a)CompuServe.COM> > The current list is divided many ways as to what relationship local mean > time (LMT) should have to local clock time (LCT). ... ... And all such divisions are completely irrelevant, because nobody who decides about time zone law reads this list. Please take your opinions about national time zone policies someplace where they will make a difference. Nathan Myers ncm(a)cantrip.org

1 0

DST switching dates
by Chris Carrier March 22, 1997

March 22, 1997

Nathan Myers > INTERNET:ncm@cantrip.org wrote: >Clearly the only sensible approach to time would be to leave the damn >clocks alone, and change schedules to match reality. However, it's a >waste of everybody's time and attention to discuss this here. We techies >are constrained to chase after whatever foolish decisions are made in the >parliaments and politburos of world. This list is about details of that >chase. >Maybe there should be another list to help discover strategies to influence >idiot politicians. I hope that those of you who are interested in the idea >will create that list, instead of using this one. The current list is divided many ways as to what relationship local mean time (LMT) should have to local clock time (LCT). One the one hand we have persons like yourself who advocate standard time throughout the year (at least I think that is what you are advocating) and alternatively we have advocates for up to three hours of year-round DST such as Peter Hullah, who stated that everyone "should add two hours to their current standard time" all year round. (Since he lives in France, that would be three hours ahead of local mean time.) (A thought: has anyone here in favor of DST in REVERSE?) Garrett Wollman > INTERNET:wollman@LCS.MIT.EDU wrote in reply to me: >On 20 Mar 97 23:41:37 EST, Chris Carrier <72157.3334(a)CompuServe.COM> said: >>Unfortunately things seem to be going in the other direction, given the EU's >>decision to copy the US/UK bad habit of ending DST on the last Sunday in >>OCTOBER, by the end of which the sun is rising later than the large majority >>of day-shift workers get up. >And those of us who live in cities like Boston, which have ``night >life'' rather than ``morning life'' think this is perfectly >reasonable.... DST rules should not be determined by cities such as Boston, but by cities on the western edge of timezones such as Cleveland in the Eastern or Dallas in the Central (and places like Indiana and West Texas should go back an hour into their astronomically correct zone.) Sue Ann Bowling > INTERNET:sbowling@gi.alaska.edu wrote: >The dates of daylight savings shift, and the assymmetry between the spring >shift (when we in Alaska are already pracitically going to bed in daylight) >and October (when it's already dark when we're going home in the evening) >have bothered me for years. The problem in Alaska isn't DST but that ever since October 1983 most of the state, except for Southeast, has been on DST all year with a 2 hour advance during the DST period in the Lower 48. >I wonder if the politicos who first devised the shift thought that solar >symmetry was around the middle of the winter and summer? It seems to have been a thing that evolved. When DST first went US-national in 1918-9, it run from the last Sunday in March to the last Sunday in October. When many states and localities started using it in 1920 in the absence of national legislation, they shortened it by a month on each end, from the last Sunday in April (a ridiculously late date in Lower 48 latitudes) to the (very sensible) last Sunday in September. This went on until 1942-5 when DST was national and year round for the war. It should be noted here that the War Time Act of 1942 called for DST to last until six months after the end of the war, but when the war did end in the summer of 1945 a bill was quickly passed to end War Time on the last Sunday in September, 1945. What I call the "October problem" started in Massachusetts when the legislature there extended DST to the end of October, starting in 1954. (IMHO they should have left September alone and started a month earlier if they wanted an extended DST period.) The next year New York and the rest of New England got on the bandwagon, and by 1962 most places on DST were ending on the last Sunday in October. (A few, however, shortened the end to Labor Day - - Minnesota was one.) Then along came the Uniform Time Act of 1966 which set up the dates of the last Sunday in April to October, nationwide. It should be pointed out that when this bill was originally introduced it did not put the whole country on DST but only stated that anyone using DST had to abide by April Sun=>24 to October Sun =>25 switch dates. Unfortunately the bill was then rewritten to put the whole nation on DST unless states exempted themselves. An amendment to the bill reducing the DST period from Memorial to Labor Day unfortunately failed; this was reintroduced in 1970 and also failed. After the 1974-5 experience with a much earlier start to DST, bills were introduced in each Congress from 1976 on to increase the DST period until in 1987, one passed to move the start date from the last to the first Sunday in April. My position during those years was to support the earlier change if and only if the ending date was moved back to the last Sunday in September. In 1981 I was happy to see the EEC (later known as the EC, now known as the EU) adopt last Sunday March-September for its continental members, hoping this would inspire the UK and US to do likewise and create something like the Livingston worldwide-switch-day proposal (which is what the UTA of 1966 was and should have been). But alas, this was not to be. >Anyway, a popular science article I wrote on the topic 10 >years ago is on the web at ><http://www.gi.alaska.edu/ScienceForum/ASF8/812.html>, pointing out some of >the oddities of time zones here in our 60 degree wide state. I used to write similar articles for the BARROW SUN and the ALEUTIAN EAGLE 1987-92 (when they folded). If you are interested I could send you one I wrote in October 1988 commenting on the fifth anniversary of the consolidation of time zones in Alaska five years earlier. Eric Ulevik > INTERNET:eau@ozemail.com.au wrote: >It is extremely unlikely that time zone rules will be simplified >to make life easier for computers. For example: sunrise and sunset >in Hobart vary sufficiently from Sydney that they are always going >to want to have different summer time start/end dates. Another >example: Adelaide has an offset of <hours>:30m from GMT. Nor should they. Time zone rules should be set by wake-sleep patterns, not the perceived need of the business community to have everyone on the same time: (A fabulous letter to the London Times during the British Standard Time period (1968-71) put it thusly: "We have 3000 telephone links between Britain and the Continent. Why do we need to get 55 million people out of bed in the dark to answer them?") >Having said that, I have an idea for how to simplify time zone rules. >A 'mean local time' can be calculated based upon location on the >earth's surface. This time can be algorithmically biased to >allow for daylight savings, smoothly varying over the year. Clocks >can use GPS and the standard algorithm to calculate this time. >Of course, this was the case before standard time, but transport >and communications go faster these days. Which is why it could never be practically adopted. If I were at the Meridian Convention in Washington, DC, USA, in (I believe) 1881, where they settled on Greenwich as the meridian, (a good decision IMHO) I would have advocated a planetwide version of what the German State Railways were doing. They had time zones based on Berlin, with each zone 10 minutes in time (2.5 degrees of longitude) apart. What I would have wanted would be such a system of 144 time zones, 10 minutes apart, centered on Greenwich. >The problem here is that administrative units - say Sydney - >may wish to adopt a standard time, but then we end not >having algorithmically determined time. Actually the problem is that organizations which deal in a large area such as railways and, in our century, broadcasters, need to have uniform time over a large area. There were many standard 'railway times' before standard time was introduced to reduce confusion in this area. >3) Time near the poles probably needs a special case. Would you believe the South Pole keeps DST? The first commander of the Pole Station wanted to keep GMT, but discovered it was more convenient to keep the time of their supply line; McMurdo Sound, which kept the same time as New Zealand. Since NZ has had a seasonal time change since 1974, McMurdo follows suit, and so does the Pole Station.

1 0

Daylight savings changeover
by Sue Ann Bowling March 21, 1997

March 21, 1997

The dates of daylight savings shift, and the assymmetry between the spring shift (when we in Alaska are already pracitically going to bed in daylight) and October (when it's already dark when we're going home in the evening) have bothered me for years. I wonder if the politicos who first devised the shift thought that solar symmetry was around the middle of the winter and summer? Anyway, a popular science article I wrote on the topic 10 years ago is on the web at <http://www.gi.alaska.edu/ScienceForum/ASF8/812.html>, pointing out some of the oddities of time zones here in our 60 degree wide state. Sue Ann Bowling, Geophysical Institute, University of Alaska Fairbanks Professional URL http://climate.gi.alaska.edu/Bowling/Bowling.html Dog URL http://www.mcf.com/bowlingsite/dogpage.html

1 0

Re: Mass switch at the equinoxes
by ncm＠cantrip.org March 21, 1997

March 21, 1997

Alex Livingston (alex(a)agsm.unsw.edu.au) wrote: >This is an ideal time for anywhere at a high enough latitude in the northern >hemisphere to advance clocks *and* anywhere at a (numerically) high enough >latitude in the southern hemisphere to retard clocks. Imagine if all the >world that did change changed on the same weekend! Chris Carrier: >I totally agree. Clearly the only sensible approach to time would be to leave the damn clocks alone, and change schedules to match reality. However, it's a waste of everybody's time and attention to discuss this here. We techies are constrained to chase after whatever foolish decisions are made in the parliaments and politburos of world. This list is about details of that chase. Maybe there should be another list to help discover strategies to influence idiot politicians. I hope that those of you who are interested in the idea will create that list, instead of using this one. Nathan Myers ncm(a)cantrip.org

2 1

How do you generate POSIX time zone strings?
by Tony Glenning March 21, 1997

March 21, 1997

Hi, I am hoping this is the correct alias for this question (apologies of not). I am trying to find a straight forward way to generate POSIX time zone strings for the current year. For example, if this function were run on machine which has TZ set to US/Pacific in 1997 it would generate: PST8PDT7,97/3:00:00,300/1:00:00 Any suggestions welcome. Currently my best thought is parsing the zoneinfo files and generating them that way, which is quite tedious. Thanks, Tony

3 4

Mass switch at the equinoxes
by Chris Carrier March 21, 1997

March 21, 1997

Alex Livingston (alex(a)agsm.unsw.edu.au) wrote: >This is an ideal time for anywhere at a high enough latitude in the northern >hemisphere to advance clocks *and* anywhere at a (numerically) high enough >latitude in the southern hemisphere to retard clocks. Imagine if all the >world that did change changed on the same weekend! I totally agree. I would like to see a world convention where northern- hemisphere DSTers all agree to start and end on the last Sundays in March and September, as Europe did 1981-95, and southern-hemisphere DSTers end and start on the same weekends. Unfortunately things seem to be going in the other direction, given the EU's decision to copy the US/UK bad habit of ending DST on the last Sunday in OCTOBER, by the end of which the sun is rising later than the large majority of day-shift workers get up. Chris Carrier

2 1

Re: A Timezone Gazetteer (and Map Maybe)
by Dave Skinner March 21, 1997

March 21, 1997

The following is an excerpt from a response I recently sent to Alex Livingston followed by my response to Eric Ulevik. Since both emails to me were also sent to tz(a)elsie.nci.nih.gov, I felt this email to be needed. ------------------------------------------------------------------------------- You are quite right about Australia/Hobart. I took Paul Eggert's input as gospel, so to speak, and he mistakenly treated Australia/Hobart as the same as Australia/Sydney. At the risk of telling you in boring detail what you already told me, here are the appropriate pairs of rules for Australia/Hobart Rule AT 1991 max - Oct Sun>=1 2:00s 1:00 - Rule AT 1991 max - Mar lastSun 2:00s 0 - and Australia/Sydney Rule AN 1987 max - Oct lastSun 2:00s 1:00 - Rule AN 1996 max - Mar lastSun 2:00s 0 - Clearly "Sun>=1" is not the same as "lastSun". You may see an errata about this one to tz(a)elsie.nci.nih.gov in the not too distant future. It would have also have been clearer to append " --> None" to both rules Aus and AQ since I was concentrating on current time zones and into the future, at least for the time being. As for Indian/Cocos, it is separated from the rest of Australia in the "australasia" file, and my lack of geography knowledge means that I did not realize that it was owned by Australia. There needs to be a modification of the "australasia" file if you want it automatically collected as a time zone of Australia in my processing. I do not know who officially to notify of that to effect the change. Do you? I will be happy to make it a time zone of Australia in my personal bookkeeping right now, though. This may be another one for the errata sheet. . . . ------------------------------------------------------------------------------ I just responded to a series of comments from Alex Livingston that included the mistake with respect to Tasmania's time zone without noticing he had subsequently sent a copy of his comments to tz(a)elsie.nci.nih.gov and also without noticing that you made a similar set of comments. A copy of my response to Alex will be sent to tz(a)elsie.nci.nih.gov after I get done responding to the rest of your comments. With regard to my > planning to ignore time zones which are the same currently, but were > different historically being a mistake, it is funny that you should mention that, because Paul Eggert and I were having a similar discussion away from tz(a)elsie.nci.nih.gov (at least I think it was away from tz(a)elsie.nci.nih.gov) with me attempting to take the position you are now advocating. The problem is not in loosing geograpical information, because all that the tz database has currently in terms of lat/lon geographic information are single lat/lon points for each time locale, currently stored in "zone.tab". The problem is, or rather the problems are: (1) We need to be able to automatically process the existing tz database at any point in time in the future to get lists of what might be called "local time zones", i.e. the list of countries that only observe one time, with or without daylight savings time shifts, throughout the year, and the list of multiple time zones by country in countries where, for reasons of either standard time and/or daylight savings time observance variations, observe multiple times at one time or another throughout the year. These "local time zones" can then be combined into "regional time zones" at any point in time, where "regional time zones" are the amalgamated total of all "local time zones" whose clocks are set the same at that point in time. These lists need to be generated and compared to their previous counterparts to see if anything has changed. (2) We need to be able to conveniently respond to changes in "regional time zone" boundaries, especially if we have either previously gathered the lat/lon pairs of the boundary in question or if we have previously gathered, as I am now attempting to do, the lat/lon pairs, i.e. the digital line graph (dlg) data (properly converted to lat/lon polygon data for ease of subsequent handling) for political jurisdictions within the countries in question down to a sufficiently fine granularity that we can simply create lists of the jurisdictions associated with each of the "regional time zones" in question and automatically generate their overall boundary lat/lon polygons. With regard to > Hopefully it will be available on a web page... Any data gathered in (2) above should be made part of the tz database and will be made available in as open a manner as is reasonable/possible. It certainly will not be thrown away. So, as the time zone boundaries change and change back, it will certainly be possible to go back to a previous boundary easily. As for web pages, there currently exist somewhat cumbersome ways to provide this capability in a secure manner (maybe with Java Applets, but totally avoiding Java Applications) on a web page, and certainly if I am able to assemble a sufficiently interesting data set, I will make it a high priority to put the needed effort, around the edges of my other work, into seeing that such a web page gets created and maintained. Furthermore, it should be possible to directly support most Unix boxes with far more efficient versions of the same capability independent of the web page interface. Finally, the automatic assessment of the current situation in (1) above certainly must deal with all of the "Zones" and all of the "Rules" that show up in the tz database. Furthermore, although I am presently focusing only on present and future "regional time zone" boundary data, this is merely to keep my immediate problem as manageable as possible. This should not be construed to mean that I am not interested in historical time zone boundary data. To the contrary, I am very interested in acquiring sufficient historical lat/lon data to make the presentation of historical time zone information by the gazetteer a reality. Unfortunately, unless there is a significant breakthrough in obtaining such historical lat/lon data, present and future time zone information is all that can be reasonably expected in the foreseeable future. Dave Skinner dave(a)kirdu.jpl.nasa.gov

1 0

Happy Equinox
by Alex LIVINGSTON March 20, 1997

March 20, 1997

Happy equinox (1997-03-20 13:55UT) one and all. This is an ideal time for anywhere at a high enough latitude in the northern hemisphere to advance clocks *and* anywhere at a (numerically) high enough latitude in the southern hemisphere to retard clocks. Imagine if all the world that did change changed on the same weekend! _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9931-9349 Telephone: +61 2 9931-9264

1 0

Re-sent: Re: A Timezone Gazetteer (and Map Maybe)
by Alex LIVINGSTON March 20, 1997

March 20, 1997

The project you are embarking on seems fantastic, and looks as though it will eventually make possible the fulfilment of a dream of mine, namely a live time-zone map on the Web showing both current time zones (labeled with UT offset) - in colors reflecting UT offset alone, and not the so-called "Standard" time in that region - and the time in each of those zones. Once such a map is operational, many other possibilities present themselves of course (e.g. zooming in, display for a past or future date). I'm afraid I can't give you any help with boundary-vector information, but I noticed a number of omissions/errors regarding Australia (where I live) in your summary information: (1) >5. australasia:Australia > Indian/Christmas 7:00 None > Australia, Western 8:00 > Australia/Perth 8:00 None > Australia, Central 9:30 > Australia/Adelaide 9:30 AS > Australia/Darwin 9:30 Aus > Australia, Eastern 10:00 > Australia/Brisbane 10:00 AQ > Australia/Sydney 10:00 AN > Australia/Lord_Howe 10:30 LH You have left out the Cocos Islands, which (unfortunately) have a time zone of their own (and not that of neighboring Christmas Island). It might look something like this: Indian/Cocos 6:30 None (2) You have also overlooked Tasmania, which starts keeping daylight-saving time before other parts of the country which observe it do: Australia, Eastern Australia/Hobart 10:00 AT (?) (3) Note also that Australia/Brisbane no longer observes daylight-saving time at all. (Could it have "None" in its DST-Rule column?) > Australia/Hobart, Australia/Melbourne \ > (duplicates of Australia/Sydney) As already intimated, this is not entirely true; Australia/Melbourne is a duplicate of Australia/Sydney, but Australia/Hobart is not. (4) > Australia/Lindeman (duplicate of Australia/Brisbane) This is only true if historical observance is irrelevant. The Australia/Lindeman entry was created for a few Queensland islands for no other reason than that they continued to switch to daylight-saving time for a couple of years after the rest of the state ceased doing so. To the best of my knowledge, however, the two zones are now indistinguishable from each other (UT+10:00 kept year-round). _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9931-9349 Telephone: +61 2 9931-9264

1 0

A Timezone Gazetteer (and Map Maybe)
by Dave Skinner March 20, 1997

March 20, 1997

Any help in obtaining either or both of the following Internal Political Boundary Maps as Digital Line Graphs (DLGs) instead of Bitmaps and Surveyor Type Legal Descriptions of the Internal Timezone Boundaries for the countries that are currently composed of multiple different timezones would be appreciated. Note that in the United States, this resolution has to go down to the county level, not just the state level, and possibly only a surveyor type legal description will do in cases like America/Indiana/Marengo where the current description in the timezone database is "part of Crawford County". I believe that I can easily get the county maps for all 50 states in this form, but I still need a surveyor type legal description of situations like this, and complete lists of counties by timezone in states that have more than one timezone. At the international level, I already located a copy of the 132 MB CIA Digital Line Graph database of the world that was released around 1990 under the Freedom of Information Act. It is composed only of line strokes, and my ultimate goal is polygons. So, the complete set of polygons that describe the current international boundary of each country and any internal regional timezones therein still have to be generated. Nevertheless, it does have international political boundaries as well as the boundaries of the states of the United States and the provinces of Canada. Other internal political boundaries within the various countries are missing, however, and the database also suffers from being out-of-date. It is circa 1989. Back on the good news front, in case it should prove useful, the database does have all significant rivers and other bodies of water down to a fairly fine level of detail. So, unless I find a better source of data, I need to bring this database up-to-date. To that end, I also need the current international political boundaries, probably in surveyor type legal descriptions, that correct all that has happened, especially in Europe and Asia, since the reunification of Germany and the breakup of the Soviet Union. At the internal political boundary level, I analyzed the timezone database and extracted a complete list of all countries (21 in all) that have multiple different current timezones, where "different" is defined as either a different current GMT offset and/or a different current daylight savings time rule. This list is summarized in the table that appears below. Within this table are 6 timezones 9.* australasia/New_Zealand 11.* europe:Norway 12.* europe:Portugal 14.* europe:Spain 20.* southamerica:Chile 21.* southamerica:Ecuador that were edited to have an asterisk ("*") appended to their number to indicate that it seems obvious where to draw a boundary between their constituent timezones. It seems obvious because the two distinct timezones involved in each case are distinguished from each other by one being on the mainland and the other being on an offshore island. This leaves the following 15 countries 1. africa:Zaire 2. asia:Indonesia 3. asia:Japan 4. asia:Kazakhstan 5. australasia:Australia 6. australasia:French_Polynesia 7. australasia:Kiribati 8. australasia:Micronesia 10. europe:Denmark 13. europe:Russia 15. europe:Ukraine 16. northamerica:Canada 17. northamerica:Mexico 18. northamerica:United_States 19. southamerica:Brazil where the exact boundary lines between their internal regional timezones must still be identified. File:Country GMT DST Timezones Offset Rule 1. africa:Zaire Africa/Kinshasa 1:00 None Africa/Lubumbashi 2:00 None 2. asia:Indonesia Asia/Jakarta 7:00 None Asia/Ujung_Pandang 8:00 None Asia/Jayapura 9:00 None 3. asia:Japan Asia/Ishigaki 8:00 None Asia/Tokyo 9:00 None 4. asia:Kazakhstan Asia/Aqtau 4:00 E-Eur Asia/Aqtobe 5:00 E-Eur Asia/Alma-Ata 6:00 E-Eur 5. australasia:Australia Indian/Christmas 7:00 None Australia, Western 8:00 Australia/Perth 8:00 None Australia, Central 9:30 Australia/Adelaide 9:30 AS Australia/Darwin 9:30 Aus Australia, Eastern 10:00 Australia/Brisbane 10:00 AQ Australia/Sydney 10:00 AN Australia/Lord_Howe 10:30 LH 6. australasia:French_Polynesia Pacific/Tahiti -10:00 None Pacific/Marquesas -9:30 None Pacific/Gambier -9:00 None 7. australasia:Kiribati Pacific/Tarawa 12:00 None Pacific/Enderbury 13:00 None Pacific/Kiritimati 14:00 None 8. australasia:Micronesia Pacific/Yap 10:00 None Pacific/Ponape (Pohnpei) 11:00 None Pacific/Kosrae 12:00 None 9.* australasia/New_Zealand Pacific/Auckland 12:00 NZ Pacific/Chatham 12:45 Chatham 10. europe:Denmark America/Thule -4:00 Thule America/Godthab (Nuuk) -3:00 EU America/Scoresbysund (Ittoqqortoormiit) -1:00 EU Atlantic/Faeroe (Faroe Islands) 0:00 EU Europe/Copenhagen 1:00 EU 11.* europe:Norway Atlantic/Jan_Mayen -1:00 None Europe/Oslo 1:00 EU 12.* europe:Portugal Atlantic/Azores -1:00 EU Europe/Lisbon 0:00 EU 13. europe:Russia Europe/Kaliningrad 2:00 Russia Europe/Moscow 3:00 Russia Europe/Samara 4:00 Russia Europe/Yekaterinburg 5:00 Russia Asia/Novosibirsk 6:00 Russia Asia/Krasnoyarsk 7:00 Russia Asia/Irkutsk 8:00 Russia Asia/Yakutsk 9:00 Russia Asia/Vladivostok 10:00 Russia Asia/Magadan 11:00 Russia Asia/Kamchatka 12:00 Russia Asia/Anadyr 13:00 Russia 14.* europe:Spain Atlantic/Canary 0:00 EU Europe/Madrid 1:00 EU 15. europe:Ukraine Europe/Kiev 2:00 EU Europe/Simferopol 3:00 Crimea 16. northamerica:Canada Canada, Pacific -8:00 America/Vancouver -8:00 Vanc Canada, Mountain -7:00 America/Dawson_Creek -7:00 None America/Edmonton -7:00 Edm Canada, Central -6:00 America/Regina -6:00 None America/Winnipeg -6:00 Winn Canada, Eastern -5:00 America/Montreal -5:00 Mont Canada, Atlantic -4:00 America/Halifax -4:00 Halifax Canada, Newfoundland -3:30 America/St_Johns -3:30 StJohns 17. northamerica:Mexico Mexico, Pacific -8:00 America/Tijuana -8:00 Mexico Mexico, Mountain -7:00 America/Mazatlan -7:00 Mexico Mexico, Central -6:00 America/Mexico_City -6:00 Mexico 18. northamerica:United_States United_States, Samoa -11:00 Pacific/Midway -11:00 None United_States, Hawaii-Aleutian -10:00 America/Adak -10:00 US Pacific/Honolulu -10:00 None United_States, Alaska -9:00 America/Anchorage -9:00 US United_States, Pacific -8:00 America/Los_Angeles -8:00 US United_States, Mountain -7:00 America/Denver -7:00 US America/Phoenix -7:00 None United_States, Central -6:00 America/Chicago -6:00 US United_States, Eastern -5:00 America/Indianapolis -5:00 None America/New_York -5:00 US 19. southamerica:Brazil America/Porto_Acre -5:00 None Brazil, Western -4:00 America/Cuiaba -4:00 Brazil America/Manaus -4:00 None Brazil, Eastern -3:00 America/Fortaleza -3:00 None America/Sao_Paulo -3:00 Brazil America/Noronha -2:00 None 20.* southamerica:Chile Pacific/Easter -6:00 Chile America/Santiago -4:00 Chile 21.* southamerica:Ecuador Pacific/Galapagos -6:00 None America/Guayaquil -5:00 None The following list of timezone database entries that are currently operational duplicates of table entries above is provided for completeness. This list was generated by Paul Eggert. Africa/Ceuta (duplicate of Europe/Madrid) America/Boise (duplicate of America/Denver) America/Dawson, America/Whitehorse \ (duplicates of America/Vancouver) America/Detroit, America/Louisville \ (duplicates of America/New_York) America/Glace_Bay, America/Goose_Bay, America/Pangnirtung \ (duplicates of America/Halifax) America/Ensenada (duplicate of America/Tijuana) America/Indiana/Knox, America/Indiana/Marengo, \ America/Indiana/Vevay (duplicates of America/Indianapolis) America/Inuvik, America/Yellowknife \ (duplicates of America/Edmonton) America/Iqaluit, America/Nipigon, America/Thunder_Bay \ (duplicates of America/Montreal) America/Juneau, America/Nome, America/Yakutat \ (duplicates of America/Anchorage) America/Maceio (duplicate of America/Sao_Paulo) America/Menominee (duplicate of America/Chicago) America/Rainy_River, America/Rankin_Inlet \ (duplicates of America/Winnipeg) America/Swift_Current (duplicate of America/Regina) Asia/Omsk (duplicate of Asia/Novosibirsk) Atlantic/Madeira (duplicate of Europe/Lisbon) Australia/Broken_Hill (duplicate of Australia/Adelaide) Australia/Hobart, Australia/Melbourne \ (duplicates of Australia/Sydney) Australia/Lindeman (duplicate of Australia/Brisbane) Pacific/Truk (duplicate of Pacific/Yap) Anyhow, thanks in advance for any help that you end up providing. Dave Skinner dave(a)kirdu.jpl.nasa.gov P.S. I also wanted to thank both Paul Eggert and Eric Ulevik for replying to my original email (to tz(a)elsie.nci.nih.gov) and I especially wanted to thank Paul Eggert for reviewing my original version of this email as well.

2 1

Paul Eggert's IDT patch makes sense
by Chris Carrier March 17, 1997

March 17, 1997

Some thoughts on Paul Eggert's proposed Israel DST rules for =>1999. The proposed rules of the third Friday in March to the third Sunday in September are very reasonable. It seems that the dates of the change are always set to avoid Jewish holy days/periods and the Jewish Sabbath, sunset Friday to sunset Saturday, and Paul's proposed rules do that. Passover, Nisan 15 in the Jewish calendar, is the first full moon after March 27 in the Gregorian calendar in this century. A third-Friday in March beginning prevents the beginning of DST from running into Passover. (Back when the Jewish calendar was determined on the basis of observation, Passover was supposed to be the first full moon after the vernal equinox (which survives in Christian Easter rules). I was informed that a group of rabbis met in Jerusalem to discuss reform of the Jewish calendar, but were unable to come to a conclusion (although the person who told me this suggested the rabbis' real reason for doing nothing was to avoid a schism such as the one that happened in Christendom in 1582 when the Gregorian calendar was implemented and the Catholics adopted it and the Protestants and Greek/Russian Orthodox did not.)) Although the Jewish New Year currently can fall during the date range 15-21 September, it can never be on a Sunday. Neither can Yom Kippur (which can occur prior to September 21) be a Sunday, so a third Sunday in September rule avoids that as well. (Tishri 1 can never fall on Sunday, Wednesday, or Friday because Yom Kippur must avoid Friday or Sunday and Succoth (Tishri 21) must avoid Saturday). However, New Years is celebrated for two days -- Tishri 1 and 2 -- and if Tishri 1 falls on Saturday, the clock change might be moved from Sunday to the preceding Friday. Also, the third Friday in March to third Sunday in September satisfies the current Israeli legal requirement of =>150 days of DST per year. Side note: there are always 154 days between the third Friday in March and the third Sunday in September and they are always the same dates in their respective months (the 15th in 1996, the 21st in 1997). I know that this is a bit of a digression, but I do think that Paul's patch does have some sound reasoning behind it. Chris Carrier

1 0

Chatham Islands time
by Chris Carrier March 17, 1997

March 17, 1997

Some thoughts on the Chatham Islands time of time change. The legal standard time of the Chathams is GMT+12:45, and they observed DST on the same dates as New Zealand, which they are legally tied to. When NZ was making its time changes at 2:00 NZ time, the Chathams changed at 2:45 Chatham time, which was the same time (14:00 GMT of the previous day in both places). Since NZ just changed at 1:00, I would presume the change in the Chathams was at 1:45. Chris Carrier

1 0

proposed tz patch for New Zealand, Israel
by Paul Eggert March 17, 1997

March 17, 1997

Here are proposed patches to the tz database for the recent minor change to the New Zealand rules reported by Jeffrey Connell. I'm also taking the liberty of proposing to regularize the formatting of the recent changes for Israel, along with one substantive change for Israel: a simpler and hopefully more accurate (though still undoubtedly incorrect) prediction for Israeli DST rules from 1999 on. (The existing prediction here seems to be based on the old late-1980s Israeli rules, and it stops after 2009.) =================================================================== RCS file: RCS/australasia,v retrieving revision 1997.1 retrieving revision 1997.1.1.1 diff -c -r1997.1 -r1997.1.1.1 *** australasia 1997/01/21 14:11:10 1997.1 --- australasia 1997/03/16 07:24:58 1997.1.1.1 *************** *** 305,313 **** Rule NZ 1990 max - Oct Sun>=1 2:00s 1:00 D Rule NZ 1975 only - Feb 23 2:00s 0 S Rule NZ 1976 1989 - Mar Sun>=1 2:00s 0 S ! Rule NZ 1990 max - Mar Sun>=15 2:00s 0 S Rule Chatham 1990 max - Oct Sun>=1 2:45s 1:00 D ! Rule Chatham 1991 max - Mar Sun>=15 2:45s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 --- 305,315 ---- Rule NZ 1990 max - Oct Sun>=1 2:00s 1:00 D Rule NZ 1975 only - Feb 23 2:00s 0 S Rule NZ 1976 1989 - Mar Sun>=1 2:00s 0 S ! Rule NZ 1990 1996 - Mar Sun>=15 2:00s 0 S ! Rule NZ 1997 max - Mar Sun>=15 2:00 0 S Rule Chatham 1990 max - Oct Sun>=1 2:45s 1:00 D ! Rule Chatham 1991 1996 - Mar Sun>=15 2:45s 0 S ! Rule Chatham 1997 max - Mar Sun>=15 2:45 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 *************** *** 832,837 **** --- 834,850 ---- # gives the NZ rules but with transitions at 2:45 local standard time. # Guess that they adopted DST in 1990. + # From "J. Sean Connell" <ankh(a)canuck.gen.nz> (1997-03-16): + # As I sit here and change all my other clocks, I would like to let y'all know + # that New Zealand changed its DST rules this year; instead of NZDT 02:59:59 + # becoming NZST 02:00:00, NZDT 01:59:59 now -> NZST 01:00:00. I'm afraid that + # I can't point you to any confirmatory articles, but apparently it was only + # decided a few weeks ago. + # + # From Paul Eggert (1997-03-15): + # We'll assume Chatham followed suit. + + ############################################################################### # Fiji =================================================================== RCS file: RCS/asia,v retrieving revision 1997.3 retrieving revision 1997.3.1.1 diff -c -r1997.3 -r1997.3.1.1 *** asia 1997/03/04 14:58:18 1997.3 --- asia 1997/03/16 07:24:58 1997.3.1.1 *************** *** 508,515 **** # From Ephraim Silverberg (ephraim(a)cs.huji.ac.il) 1997-03-04: - # Zone Information Compiler (ZIC) File for the State of Israel (1989-2009) - # According to the Office of the Secretary General of the Ministry of # Interior, there is NO set rule for Daylight-Savings/Standard time changes. # Each year they decide anew what havoc to wreak on the country. However, --- 508,513 ---- *************** *** 525,551 **** # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0:00 S ! Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0:00 S ! Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0:00 S ! Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0:00 S ! Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0:00 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0:00 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0:00 S # The dates for 1996 were determined by the Minister of Interior of the # time, Haim Ramon. The official announcement regarding 1996-1998 --- 523,549 ---- # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0 S ! Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0 S ! Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0 S ! Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0 S ! Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0 S # The dates for 1996 were determined by the Minister of Interior of the # time, Haim Ramon. The official announcement regarding 1996-1998 *************** *** 560,599 **** # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1996 only - Mar 15 0:00 1:00 D ! Rule Zion 1996 only - Sep 16 0:00 0:00 S ! Rule Zion 1997 only - Mar 21 0:00 1:00 D ! Rule Zion 1997 only - Sep 14 0:00 0:00 S ! Rule Zion 1998 only - Mar 20 0:00 1:00 D ! Rule Zion 1998 only - Oct 18 0:00 0:00 S ! ! # These rules are probably wrong, but they are close approximations (usually ! # within a few weeks): ! ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1999 only - Apr 11 0:00 1:00 D ! Rule Zion 1999 only - Sep 5 0:00 0:00 S ! Rule Zion 2000 only - Apr 30 0:00 1:00 D ! Rule Zion 2000 only - Sep 24 0:00 0:00 S ! Rule Zion 2001 only - Apr 15 0:00 1:00 D ! Rule Zion 2001 only - Sep 9 0:00 0:00 S ! Rule Zion 2002 only - Apr 7 0:00 1:00 D ! Rule Zion 2002 only - Sep 1 0:00 0:00 S ! Rule Zion 2003 only - Apr 27 0:00 1:00 D ! Rule Zion 2003 only - Sep 21 0:00 0:00 S ! Rule Zion 2004 only - Apr 18 0:00 1:00 D ! Rule Zion 2004 only - Sep 12 0:00 0:00 S ! Rule Zion 2005 only - May 1 0:00 1:00 D ! Rule Zion 2005 only - Sep 25 0:00 0:00 S ! Rule Zion 2006 only - Apr 23 0:00 1:00 D ! Rule Zion 2006 only - Sep 17 0:00 0:00 S ! Rule Zion 2007 only - Apr 15 0:00 1:00 D ! Rule Zion 2007 only - Sep 9 0:00 0:00 S ! Rule Zion 2008 only - Apr 27 0:00 1:00 D ! Rule Zion 2008 only - Sep 21 0:00 0:00 S ! Rule Zion 2009 only - Apr 19 0:00 1:00 D ! Rule Zion 2009 only - Sep 13 0:00 0:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 --- 558,577 ---- # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule Zion 1996 only - Mar 15 0:00 1:00 D + Rule Zion 1996 only - Sep 16 0:00 0 S + Rule Zion 1997 only - Mar 21 0:00 1:00 D + Rule Zion 1997 only - Sep 14 0:00 0 S + Rule Zion 1998 only - Mar 20 0:00 1:00 D + Rule Zion 1998 only - Oct 18 0:00 0 S + + # From Paul Eggert (1997-03-15): + # Here are guesses for rules after 1998. + # They are probably wrong, but they are more likely than no DST at all. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1999 max - Mar Fri>=15 0:00 1:00 D ! Rule Zion 1999 max - Sep Sun>=15 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880

2 1

Daylight savings time in New Zealand
by J. Sean Connell March 15, 1997

March 15, 1997

As I sit here and change all my other clocks, I would like to let y'all know that New Zealand changed its DST rules this year; instead of NZDT 02:59:59 becoming NZST 02:00:00, NZDT 01:59:59 now -> NZST 01:00:00. I'm afraid that I can't point you to any confirmatory articles, but apparently it was only decided a few weeks ago... -- Jeffrey Connell | Systems Adminstrator, ICONZ ankh(a)canuck.gen.nz | Any opinions stated above are not my employers', ankh(a)iconz.co.nz | not my boyfriend's, my priest's, my God's, my #include <stddisc.h> | my friends', and probably not even my own. ---------------------------+-------------------------------------------------- Fingerprint: 1024/2B8B116D | Key at http://www.canuck.gen.nz/~ankh/pgpkey.html

1 0

tzcode1997c.tar.gz and tzdata1997d.tar.gz
by ado March 8, 1997

March 8, 1997

The files ftp://elsie.nci.nih.gov/pub/tzcode1997c.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1997d.tar.gz are now available. Included are changes to "zic.c" to correct performance of the "-s" option, and a new file "usno1997". --ado

1 0

Re: Israel Daylight Time
by Dave Skinner March 6, 1997

March 6, 1997

Regarding time settings in the state of Indiana, I do not know about the stories in the email to which I am now responding. Nevertheless, I grew up in Indianapolis, and I do remember that the first week or so of first grade was spent with the schools on one time-of-day and everyone's homes on a time-o-day that differed by an hour. This would have been in approximately September of 1959 (if I have redetermined the year of my 1st grade tour of duty correctly). Dave Skinner dave(a)jpl.nasa.gov

1 0

Israel Daylight Time
by Chris Carrier March 6, 1997

March 6, 1997

Ephraim Silverberg > INTERNET:ephraim@cs.huji.ac.il wrote: >Yesterday, the Knesset (Israeli parliament) passed a law changing the >daylight savings changeover times for 1997 (a mere ten days from when the >old times were to take effect). >An article from the English-language Jerusalem Post of late January explains >the rational for the change and can be found in: > ftp://ftp.huji.ac.il/users/ephraim/tz/timezone97.ps.gz >Please note that the starting time mentioned in the English-language article >is NOT the time that was finally decided upon by the Knesset. Could you please post the article here? Not all of us have Web access, sadly. >According to the Office of the Secretary General of the Ministry of >Interior, there is NO set rule for Daylight-Savings/Standard time changes. >Each year they decide anew what havoc to wreak on the country. However, >there is a "supposed" set of rules which is subject to change depending >on the party the Minister of Interior, the size of the coalition >government, the phase of the moon and the direction of the wind... Sounds like Indiana in the good old days before the Uniform Time Act where each county had its own time, each city within that county could secede from that, and where a 35-mile stretch of road had seven different sets of rules. I heard an apocrphyal story from Indiana at that time that a city council met on a Saturday evening and decided to cancel DST which was to go into effect at 2 a.m. that night (Sunday morning). The police and fire departments went around all over town late that evening and early next morning broadcasting the change on their bullhorns. Although the 1999-2009 dates do bounce around the Gregorian calendar quite a bit, in the Jewish calendar they are quite consistent: DST begins on the fourth Sunday in Nisan and ends on the first Sunday after Elul 20. (Ran the dates through a program of mine that takes Civil dates and translates them into a number of other calendars, including the Jewish).

1 0

tzdata1997c.tar.gz
by ado March 4, 1997

March 4, 1997

The file http://elsie.nci.nih.gov/pub/tzdata1997c.tar.gz is now available; it incorporates the recently circulated changes in Israel. I'm at work on the "zic -s" challenge. The cleanest way to deal with it seems to be to ignore the "-s" flag when running through the rules and zones, then eliminating "early" transition times when writing out the zone file; doing this provides a way of figuring out what time type should be in effect at the earliest instant to be represented in the file. Substantial regression work will be needed, so stay tuned. --ado

1 0

Changes in Israel's 1997 Daylight Savings Rules (CORRECTION!)
by Ephraim Silverberg March 4, 1997

March 4, 1997

> An article from the English-language Jerusalem Post of late January explains > the rational for the change and can be found in: > > ftp://ftp.huji.ac.il/users/ephraim/tz/timezone97.ps.gz > > Please note that the starting time mentioned in the English-language article > is NOT the time that was finally decided upon by the Knesset. The ZIC file I included in my previous message contained the proposed times (and comments) NOT the real times. Attached is the true ZIC file. 10**6 apologies. ___________________________________________________________________________ Ephraim Silverberg, CS System Group, Phone number: 972-2-6585521 Hebrew University, Jerusalem, Israel. Fax number: 972-2-6585439 WWW: http://www.cs.huji.ac.il/~ephraim E-mail: ephraim(a)cs.huji.ac.il --------------------------------------------------------------------------- # Zone Information Compiler (ZIC) File for the State of Israel (1989-2009) # According to the Office of the Secretary General of the Ministry of # Interior, there is NO set rule for Daylight-Savings/Standard time changes. # Each year they decide anew what havoc to wreak on the country. However, # there is a "supposed" set of rules which is subject to change depending # on the party the Minister of Interior, the size of the coalition # government, the phase of the moon and the direction of the wind. Hence, # changes may need to be made on a semi-annual basis. One thing is entrenched # in law, however: that there must be at least 150 days of daylight savings # time annually. Ever since 1993, the change to daylight savings time is # on a Thursday night from midnight IST to 1 a.m IDT. The change back to # standard time is on a Saturday night from midnight daylight savings time # to 11 p.m. standard time. 1996 is an exception to this rule where the # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1989 only - Apr 30 0:00 1:00 D Rule Zion 1989 only - Sep 3 0:00 0:00 S Rule Zion 1990 only - Mar 25 0:00 1:00 D Rule Zion 1990 only - Aug 26 0:00 0:00 S Rule Zion 1991 only - Mar 24 0:00 1:00 D Rule Zion 1991 only - Sep 1 0:00 0:00 S Rule Zion 1992 only - Mar 29 0:00 1:00 D Rule Zion 1992 only - Sep 6 0:00 0:00 S Rule Zion 1993 only - Apr 2 0:00 1:00 D Rule Zion 1993 only - Sep 5 0:00 0:00 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling her office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1994 only - Apr 1 0:00 1:00 D Rule Zion 1994 only - Aug 28 0:00 0:00 S Rule Zion 1995 only - Mar 31 0:00 1:00 D Rule Zion 1995 only - Sep 3 0:00 0:00 S # The dates for 1996 were determined by the Minister of Interior of the # time, Mr. Haim Ramon. The official announcement regarding 1996-1998 # (with the dates for 1997 no longer being relevant) can be viewed at: # # ftp://ftp.huji.ac.il/pub/tz/announcements/1996-1998.ramon.ps.gz # # The dates for 1997 were altered by his successor, Rabbi Eli Suissa. # No changes have been made regarding 1998 as of yet. # # The official announcement for the year 1997 can be viewed at: # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1996 only - Mar 15 0:00 1:00 D Rule Zion 1996 only - Sep 16 0:00 0:00 S Rule Zion 1997 only - Mar 21 0:00 1:00 D Rule Zion 1997 only - Sep 14 0:00 0:00 S Rule Zion 1998 only - Mar 20 0:00 1:00 D Rule Zion 1998 only - Oct 18 0:00 0:00 S # These rules are probably wrong, but they are close approximations (usually # within a few weeks): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1999 only - Apr 11 0:00 1:00 D Rule Zion 1999 only - Sep 5 0:00 0:00 S Rule Zion 2000 only - Apr 30 0:00 1:00 D Rule Zion 2000 only - Sep 24 0:00 0:00 S Rule Zion 2001 only - Apr 15 0:00 1:00 D Rule Zion 2001 only - Sep 9 0:00 0:00 S Rule Zion 2002 only - Apr 7 0:00 1:00 D Rule Zion 2002 only - Sep 1 0:00 0:00 S Rule Zion 2003 only - Apr 27 0:00 1:00 D Rule Zion 2003 only - Sep 21 0:00 0:00 S Rule Zion 2004 only - Apr 18 0:00 1:00 D Rule Zion 2004 only - Sep 12 0:00 0:00 S Rule Zion 2005 only - May 1 0:00 1:00 D Rule Zion 2005 only - Sep 25 0:00 0:00 S Rule Zion 2006 only - Apr 23 0:00 1:00 D Rule Zion 2006 only - Sep 17 0:00 0:00 S Rule Zion 2007 only - Apr 15 0:00 1:00 D Rule Zion 2007 only - Sep 9 0:00 0:00 S Rule Zion 2008 only - Apr 27 0:00 1:00 D Rule Zion 2008 only - Sep 21 0:00 0:00 S Rule Zion 2009 only - Apr 19 0:00 1:00 D Rule Zion 2009 only - Sep 13 0:00 0:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Israel 2:00 Zion I%sT

1 0

Changes in Israel's 1997 Daylight Savings Rules
by Ephraim Silverberg March 4, 1997

March 4, 1997

Yesterday, the Knesset (Israeli parliament) passed a law changing the daylight savings changeover times for 1997 (a mere ten days from when the old times were to take effect). Attached is the new Zic file for Israel with the corrected 1997 times. For now, the times for 1998 remain the same and there are no official times for 1999 and on. Please note that I have altered some of the comments as well. The official announcement (in Hebrew) is in the gzipped postscript file: ftp://ftp.huji.ac.il/pub/tz/announcements/1997.ps.gz An article from the English-language Jerusalem Post of late January explains the rational for the change and can be found in: ftp://ftp.huji.ac.il/users/ephraim/tz/timezone97.ps.gz Please note that the starting time mentioned in the English-language article is NOT the time that was finally decided upon by the Knesset. ___________________________________________________________________________ Ephraim Silverberg, CS System Group, Phone number: 972-2-6585521 Hebrew University, Jerusalem, Israel. Fax number: 972-2-6585439 WWW: http://www.cs.huji.ac.il/~ephraim E-mail: ephraim(a)cs.huji.ac.il --------------------------------------------------------------------------- # Zone Information Compiler (ZIC) File for the State of Israel (1989-2009) # According to the Office of the Secretary General of the Ministry of # Interior, there is NO set rule for Daylight-Savings/Standard time changes. # Each year they decide anew what havoc to wreak on the country. However, # there is a "supposed" set of rules which is subject to change depending # on the party the Minister of Interior, the size of the coalition # government, the phase of the moon and the direction of the wind. Hence, # changes may need to be made on a semi-annual basis. One thing is entrenched # in law, however: that there must be at least 150 days of daylight savings # time annually. The change to daylight savings time is from midnight IST # to 1 a.m IDT (day of week varies in different years). The change back to # standard time is on a Saturday night from midnight daylight savings time # to 11 p.m. standard time. 1996 is an exception to this rule where the # change back to standard time took place on Sunday night instead of Saturday # night to avoid conflicts with the Jewish New Year. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1989 only - Apr 30 0:00 1:00 D Rule Zion 1989 only - Sep 3 0:00 0:00 S Rule Zion 1990 only - Mar 25 0:00 1:00 D Rule Zion 1990 only - Aug 26 0:00 0:00 S Rule Zion 1991 only - Mar 24 0:00 1:00 D Rule Zion 1991 only - Sep 1 0:00 0:00 S Rule Zion 1992 only - Mar 29 0:00 1:00 D Rule Zion 1992 only - Sep 6 0:00 0:00 S Rule Zion 1993 only - Apr 2 0:00 1:00 D Rule Zion 1993 only - Sep 5 0:00 0:00 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling her office directly at 972-2-6701447 or 972-2-6701448. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1994 only - Apr 1 0:00 1:00 D Rule Zion 1994 only - Aug 28 0:00 0:00 S Rule Zion 1995 only - Mar 31 0:00 1:00 D Rule Zion 1995 only - Sep 3 0:00 0:00 S # The dates for 1996 were determined by the Minister of Interior of the # time, Haim Ramon. The dates for 1997 were altered by his successor, # Rabbi Eli Suissa. No changes have been made regarding 1998 as of yet. # # The official announcement for the years 1997 and 1998 can be viewed at: # # ftp://ftp.huji.ac.il/pub/tz/announcements/1997-1998.ps.gz # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1996 only - Mar 15 0:00 1:00 D Rule Zion 1996 only - Sep 16 0:00 0:00 S Rule Zion 1997 only - Mar 23 0:00 1:00 D Rule Zion 1997 only - Sep 14 0:00 0:00 S Rule Zion 1998 only - Mar 20 0:00 1:00 D Rule Zion 1998 only - Oct 18 0:00 0:00 S # These rules are probably wrong, but they are close approximations (usually # within a few weeks): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1999 only - Apr 11 0:00 1:00 D Rule Zion 1999 only - Sep 5 0:00 0:00 S Rule Zion 2000 only - Apr 30 0:00 1:00 D Rule Zion 2000 only - Sep 24 0:00 0:00 S Rule Zion 2001 only - Apr 15 0:00 1:00 D Rule Zion 2001 only - Sep 9 0:00 0:00 S Rule Zion 2002 only - Apr 7 0:00 1:00 D Rule Zion 2002 only - Sep 1 0:00 0:00 S Rule Zion 2003 only - Apr 27 0:00 1:00 D Rule Zion 2003 only - Sep 21 0:00 0:00 S Rule Zion 2004 only - Apr 18 0:00 1:00 D Rule Zion 2004 only - Sep 12 0:00 0:00 S Rule Zion 2005 only - May 1 0:00 1:00 D Rule Zion 2005 only - Sep 25 0:00 0:00 S Rule Zion 2006 only - Apr 23 0:00 1:00 D Rule Zion 2006 only - Sep 17 0:00 0:00 S Rule Zion 2007 only - Apr 15 0:00 1:00 D Rule Zion 2007 only - Sep 9 0:00 0:00 S Rule Zion 2008 only - Apr 27 0:00 1:00 D Rule Zion 2008 only - Sep 21 0:00 0:00 S Rule Zion 2009 only - Apr 19 0:00 1:00 D Rule Zion 2009 only - Sep 13 0:00 0:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Israel 2:00 Zion I%sT

1 0

zic -s bug fixes for year/time extremes (found by code inspection)
by Paul Eggert March 3, 1997

March 3, 1997

I briefly looked for a fix for the problem that Dave Sparks reported today with zic.c, and decided that this will require more zic expertise than I have. However, I did find a couple of related bugs in zic.c by code inspection. First, there are a couple of places in the code that compare for equality to min_year, but values less than min_year are possible if -s is given, so these should be changed to compare for not greater than min_year. (While we're at it, we might as well make max_year symmetric.) Second, the setboundaries function sets min_year and max_year based on GMT, but these values are meant to be bounds for localtime years, so to be safe one must subtract 1 from the GMT min year and add 1 to the GMT max year. This is particularly important with the -s option, since the GMT min year is 1970 but the localtime min year might be 1969. Here is a proposed patch. This patch doesn't fix Sparks's bug, unfortunately. 1997-03-02 Paul Eggert <eggert(a)twinsun.com> * zic.c (setboundaries): Set min_year to be one less than GMT min_year, and max_year to be one greater than GMT max_year, in case local time and GMT disagree about years at time boundaries. (outzone, tadd): Don't assume that min_time and max_time are bounds on time_t values, since -s makes this assumption false. =================================================================== RCS file: RCS/zic.c,v retrieving revision 1997.2.1.1 retrieving revision 1997.2.1.2 diff -c -r1997.2.1.1 -r1997.2.1.2 *** zic.c 1997/02/28 00:22:22 1997.2.1.1 --- zic.c 1997/03/03 03:58:26 1997.2.1.2 *************** *** 647,654 **** max_time <<= TIME_T_BITS_IN_FILE - 1; --max_time; } ! min_year = TM_YEAR_BASE + gmtime(&min_time)->tm_year; ! max_year = TM_YEAR_BASE + gmtime(&max_time)->tm_year; } static int --- 647,654 ---- max_time <<= TIME_T_BITS_IN_FILE - 1; --max_time; } ! min_year = TM_YEAR_BASE + gmtime(&min_time)->tm_year - 1; ! max_year = TM_YEAR_BASE + gmtime(&max_time)->tm_year + 1; } static int *************** *** 1638,1645 **** if (!rp->r_todisstd) offset = oadd(offset, stdoff); jtime = rp->r_temp; ! if (jtime == min_time || ! jtime == max_time) continue; jtime = tadd(jtime, -offset); if (k < 0 || jtime < ktime) { --- 1638,1645 ---- if (!rp->r_todisstd) offset = oadd(offset, stdoff); jtime = rp->r_temp; ! if (jtime <= min_time || ! jtime >= max_time) continue; jtime = tadd(jtime, -offset); if (k < 0 || jtime < ktime) { *************** *** 1978,1986 **** { register time_t t; ! if (t1 == max_time && t2 > 0) return max_time; ! if (t1 == min_time && t2 < 0) return min_time; t = t1 + t2; if ((t2 > 0 && t <= t1) || (t2 < 0 && t >= t1)) { --- 1978,1986 ---- { register time_t t; ! if (t1 >= max_time && t2 > 0) return max_time; ! if (t1 <= min_time && t2 < 0) return min_time; t = t1 + t2; if ((t2 > 0 && t <= t1) || (t2 < 0 && t >= t1)) {

1 0

problem withzic 7.81 (1997a)
by Dave Sparks March 2, 1997

March 2, 1997

I recently downloaded tz{code,data}1997a.tar.gz in order to update our timezone database. Because we will not be using any dates earlier than 1970 I used zic -s to save space. All the timezone information was compiled, but when I tried to install the data into our database four timezones failed the sanity checks. I found that the compiled files for these timezones were each 44 bytes long and contained only zeros. The zones were: Australia/Darwin Africa/Accra Africa/Freetown Africa/Johannesburg (none of which have transitions after 1970). I looked at zic.c and made the following changes: 207% diff zic.c zic.OLD.c 3c3 < static char elsieid[] = "@(#)zic.c 7.81 +DaveS"; --- > static char elsieid[] = "@(#)zic.c 7.81"; 1572a1573 > usestart = i > 0 && (zp - 1)->z_untiltime > min_time; 1576d1576 < usestart = (timecnt == 0 && !useuntil) || (i > 0 && ((zp - 1)->z_untiltime > min_time)); which was partially successful (the Australian timezone was handled, but the African timezones needed modifications which wouldn't have been necessary if the fix had been correct: 208% diff africa africa.OLD 325,326c325 < 0:00 Ghana %s 1942 < 0:00 - WAT --- > 0:00 Ghana %s 561,562c560 < 0:00 SL WA%sT 1962 < 0:00 - WAT --- > 0:00 SL WA%sT 581,582c579 < 2:00 SA SA%sT 1944 < 2:00 - SAT --- > 2:00 SA SA%sT ). After looking more carefully at the timezone data, I realised that what the troublesome timezones had in common wasn't just that there were no transitions after 1970, but also that the last transition was by Rule. Since by then I had compiled data which we could use, I didn't look at zic.c again to try to work out a better fix. Incidentally, the assumption that the first Standard Time offset should be used for times before the first transition doesn't work well for Southern Hemisphere timezones: in many cases Summer Time will be in effect at the earliest time handled. (In case you were wondering why we need to import the timezone data into our own database: the application in question has to handle multiple timezones and is nor written in C or C++.) -- Dave Sparks, Staffordshire, England (posted from my private mailbox to avoid my employer being legally liable, since in English law a disclaimer would be ineffective.)

1 0

Re: ISO 8601 revision
by kuhn＠cs.purdue.edu March 1, 1997

March 1, 1997

Keld J|rn Simonsen wrote on 1997-03-01 22:50 UTC: [How do we get in contact with the ISO 8601 working group?] > I can try to ask the Danish Standards people. Great! > Have you got any suggestions for the "ugly T"? [Anyone interested in this discussion without a copy of ISO 8601, please download and print first <ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/ISO8601.ps.Z> for reference.] I think, a space is the nicest solution as in 1997-03-01 22:50 and it should definitely be explicitely allowed. The current standard gave the author of <http://www.internic.net/internet-drafts/draft-newman-datetime-01.txt> the impression that the "ugly T" is the only comforming way of writing down both date and time, which is the only reason why the new proposed Internet standard date and time format (an ISO 8601 profile) has the "T". Only for applications, where a space is inconvenient (e.g, Unix command line options, where fields are separated by space), the hyphen as used in the corresponding ANSI standard and as shown in the "Chicago Manual of Style" is also quite nice: 1997-02-28-22:50 I do not see, where this overloading of the hyphen would cause problems with the requirement, that a parser must be able to distinguish all formats. If it causes problems with unambiguous parsability, then I wouldn't mind dropping some of the less useful notations from the ensemble. I also find the notation "--MM-DD" awfull for cases where I do not specify the year as it follows from context. It would be much nicer if notations like "-MM-DD" and "-DD" would be part of the collection, as this would allow to use these notations in sentences like "The conference will take place from 1997-08-28 to -31, and the tutorial sessions will run from -08-28 to -09-05." Instead these patterns are currently used for "-YY" and "-YY-MM". I think, using the leading hyphen to indicate the missing century digits was a bad idea. Please note that although ISO 8601 was intended as a standard for data respresentation, it is today quoted in standards for business letter typographical conventions (e.g., DIN 5008-1996). ISO 8601 currently lists numerous incomplete formats which I strongly doubt will ever be used anywhere (e.g., "---DD"). They are in applications like Unix cron, where you want to specify periodic events, much better represented by a more generic extended wildcard notation that allows to specify events like the last Sunday of every month, something ISO 8601 currently does not yet provide. Useful new notations might be 1997-100.5 (noon of the 100th day of 1997) 1997-02-3-7 (the third sunday of February 1997, especially useful with unspecified year or year/month as in *-3-7 or *-02-3-7) These are just a few first ideas for improvement. Once we get in contact with the working group and hear about their plans, we can start working on a detailed proposal. Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

1 0

tzcode1997b.tar.gz and tzdata1997b.tar.gz
by ado Feb. 27, 1997

Feb. 27, 1997

The files ftp://elsie.nci.nih.gov/pub/tzcode1997b.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1997b.tar.gz are now available. The data file incorporates the 1997 leap second; the code file incorporates your correspondent's take on the zic/multiprocessor/directory-creation situation. --ado

1 0

Re: 8th EU Directive, French time
by peter＠memex.co.uk Feb. 27, 1997

Feb. 27, 1997

> Has the 8th EU Summer Time Directive come out? (starting in 1998) Not that I know of. The Transport Council (the group of national transport ministers who decide this) aren't due to meet for the first time this year until 11 March so I can't see it happening before then. I have just checked with my contact at the local EC Information Office and she hasn't heard anything either. They did apparently have an informal meeting on 31 Jan but I can't see anything in the midday press releases (at http://europa.eu.int/en/comm/spp/me/midday.html, with the relevent past ones at me970131.html, me970203.html, etc. (these people have a year 2000 problem looming :-) ). > Also, is France going to move from GMT+1 to GMT+2 this spring, and are they > still discussing remaining on the same time all year? (Perhaps permanent rule > change might be deferred until the end of the 7th Directive in October 1997.) I haven't seen any reports about this for months. I think it very unlikely that they will not follow the existing 7th directive. Any change, if it comes at all, is likely to be in 1998. > Has a date been set for the British General Election? No, but the options are closing in all the time. John Major has all but said it will be 1 May. I think the latest date is 5 May, but elections are always on a Thursday here so that is out. The other hot tip was 20 March but I think it is now too late to dissolve Parliament and meet that date. There is a by-election at Wirral South today, the result of which will no doubt confuse things even more. A bit of bonus news I saw today: there will be a leap second on 30 June 1997. See ftp://hpvlbi.obspm.fr/iers/bul/bulc/bulletinc.13 or http://tycho.usno.navy.mil/leap.html. Peter Ilieve peter(a)aldie.co.uk

2 1

8th EU Directive, French time
by Chris Carrier Feb. 27, 1997

Feb. 27, 1997

Some questions for our UK/European correspondents: Has the 8th EU Summer Time Directive come out? (starting in 1998) Also, is France going to move from GMT+1 to GMT+2 this spring, and are they still discussing remaining on the same time all year? (Perhaps permanent rule change might be deferred until the end of the 7th Directive in October 1997.) Has a date been set for the British General Election? Thank you. Chris Carrier

3 2

Interest in Timezone Information at JPL
by Dave Skinner Feb. 26, 1997

Feb. 26, 1997

I guess I should be added to at least the tz-requests mailing list and possibly the tz mailing list as well if it does NOT include the former email addresses by default. I represent the only person at the Jet Propulsion Laboratory who has both an abiding interest in these matters as well as an immediate and on-going need for this information. For the record, I am coding a web-based capability to look up the latitude and longitude of any any geographic name that is being maintained in the http://www.nima.mil/gns/html/index.html web site, which is the National Imagery and Mapping Agency (NIMA) GEOnet Names Server for non-US geographic names, and at the http://www.census.gov/cgi-bin/gazetteer web site of the US Census Bureau, which is the name server for US geographic names. Once, I have the laititude and longitude I am currently planning to find out which of your timezones is the timezone associated with either the country or territory involved or, if the country in question has multiple timezones, to ascertain which of these timezones is the correct one based on the associated latitude and longitude. Finally, I plan to maintain and use your timezone information to find the best estimate of time-of-day at that location for a specified julian date. I say "best estimate" because many of our lookups will necessarily be for future events, and the timezone boundaries, their associated offsets from GMT, and especially their associated daylight savings time rules are obviously only as good as we know them today. The only problem that remains to be solved is the polygon information that is currently burried in the http://www.odci.gov/cia/publications/95fact/802389h.gif file. To automatically lookup which timezone is associated with a given latitude and longitude requires having those polygons. So, I plan to see if the CIA Publications types would be willing to post such a file. If not, I may be forced to beat on the gif file. Anyway, it is really great to see that such a thorough effort to identify and maintain timezone information is occurring. Dave Skinner dave(a)kirdu.jpl.nasa.gov

1 0

"tzcode.tar.gz" and "tzdata.tar.gz" as links?
by guy＠netapp.com Feb. 11, 1997

Feb. 11, 1997

I sometimes suggest, in postings and mail messages, that people should pick up the Olson code and database; unfortunately, I have to put it as, e.g.: The [Arthur] Olson code, available, to those with FTP access, from "elsie.nci.nih.gov", in "pub/tzcode1997a.tar.gz" (unless, by the time you see this posting, Arthur's put out another version, in which case it'll be "1997b" or something such as that), ... (to quote a recent "comp.unix.solaris" posting). "libpcap" and "tcpdump", for example, handle this by having "libpcap.tar.Z" being a symlink to the current version of the "libpcap" library, and having "tcpdump.tar.Z" being a symlink to the current version of "tcpdump"; should something similar be done for the "tzcode" and "tzdata" "tar.gz" files?

1 0

your timezone program.
by Igor Grobman Feb. 5, 1997

Feb. 5, 1997

-----BEGIN PGP SIGNED MESSAGE----- Hi, I am one of the developers of Debian Linux, a popular free Linux distribution. I was asked to fix bugs in this program that were filed by our users in the bug tracking system. The most serious bug is "the missing timezones". Apparently, your program included some timezones in an earlier version (I would guess around 1994) that were later dropped. The zones that users most ask about is something like US/Eastern, /US/Central, /US/Western, and similar things for other countries. I understand you probably don't want to release an official version with these zones defined, but what would be the best way for me to do it in order to fix it in the distribution? I looked at the source, and saw that you already use "Link" to link some of the obsolete zones. Would it be wise to link those old zones to the corresponding new timezone? Thanks. __ Proudly running Debian Linux! Linux vs. Windows is a no-Win situation.... Igor Grobman igor(a)vaca.net -----BEGIN PGP SIGNATURE----- Version: 2.6.3 Charset: noconv iQBVAwUBMvkDmf6MRr9c8VylAQFtewIAnXYYWwxzoC9erTAgnUJrldkiNQKS//63 cwtOUOY1y1XMAPduspYjmezHMGq47UW1bRgowr+nl9IWzPHqfhU3gA== =iHGm -----END PGP SIGNATURE-----

1 0

Re: zic on multi-processor systems
by Ulrich Drepper Feb. 3, 1997

Feb. 3, 1997

Ken Pizzini <ken(a)halcyon.com> writes: > if (!itsdir(name)) { > /* > ** It doesn't seem to exist, so we try to create it. > + ** Double check the return. Someone may be one > + ** step ahead of us. > */ > if (mkdir(name, 0755) != 0) { > + int sverr = errno; > + if (!itsdir(name)) { > const char *e = strerror(errno); You probably mean `sverr' here --------------------------^^^^^ BTW: I would change the if line to if (errno == EEXIST && !itsdir(name)) I've sent the patch as I got it and thought about it only later. Thanks, -- Uli ---------------. drepper(a)cygnus.com ,-. Rubensstrasse 5 Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany Cygnus Solutions `--' drepper(a)gnu.ai.mit.edu `------------------------

1 0

zic on multi-processor systems
by Ulrich Drepper Feb. 2, 1997

Feb. 2, 1997

Hi, the following patch will improve the usability of zic in environments with multiple processors (or make running several processes). We are in this situation in GNU libc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff -u gnu/glibc/time/zic.c:1.1.1.4 gnu/glibc/time/zic.c:1.2 --- gnu/glibc/time/zic.c:1.1.1.4 Wed Jan 22 06:58:14 1997 +++ gnu/glibc/time/zic.c Sun Feb 2 12:02:29 1997 @@ -2126,8 +2126,11 @@ if (!itsdir(name)) { /* ** It doesn't seem to exist, so we try to create it. + ** Double check the return. Someone may be one + ** step ahead of us. */ - if (mkdir(name, 0755) != 0) { + if (mkdir(name, 0755) != 0 && !itsdir(name)) + { const char *e = strerror(errno); (void) fprintf(stderr, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thanks, -- Uli ---------------. drepper(a)cygnus.com ,-. Rubensstrasse 5 Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany Cygnus Solutions `--' drepper(a)gnu.ai.mit.edu `------------------------

2 1

Re: draft-newman-datetime-01.txt
by Chris Newman Jan. 31, 1997

Jan. 31, 1997

I have a proposal for dealing with the "T" problem: How about at the end of section 5.2, I mention that it may be desirable to substitute a " " for the "T" when displaying times to users (of course the "T" would still be required for Internet protocol interchange). Does this sound like a reasonable compromise?

2 3

I-D ACTION:draft-newman-datetime-01.txt (fwd)
by Chris Newman Jan. 30, 1997

Jan. 30, 1997

Here's a new version of the time format document. The major change is adding a new format to represent future dates by specifying timezone name. Something like this seems to be needed by the IETF calendaring/scheduling working group to deal with future events and recurring events scheduled in local timezones. ---------- Forwarded message ---------- Date: Tue, 28 Jan 1997 09:40:43 -0500 From: Internet-Drafts(a)ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-newman-datetime-01.txt A Revised Internet-Draft is available from the on-line Internet-Drafts directories. Title : Date and Time on the Internet Author(s) : C. Newman Filename : draft-newman-datetime-01.txt Pages : 23 Date : 01/27/1997 Date and time formats cause a lot of confusion and interoperability problems on the Internet. This document will address many of the problems encountered and make recommendations to improve consistancy and interoperability when representing and using date and time in Internet protocols. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-newman-datetime-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-newman-datetime-01.txt Internet-Drafts directories are located at: o Africa: ftp.is.co.za o Europe: ftp.nordu.net ftp.nis.garr.it o Pacific Rim: munnari.oz.au o US East Coast: ds.internic.net o US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ds.internic.net. In the body type: "FILE /internet-drafts/draft-newman-datetime-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e., documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

3 5

Alternative to A/B notation
by Chris Carrier Jan. 30, 1997

Jan. 30, 1997

Paul Eggert > INTERNET:eggert@twinsun.com wrote: >I agree with most of Markus Kuhn's comments and have the following >further comments and suggestions. >* I agree with Markus that ambiguous local times are a problem, but >the proposed A/B notation is not an adequate solution. That notation >works in the European context, where the rules are simple and uniform, >but it won't work well in general and it's painful to implement reliably. (major snip dealing with problems with A/B notation) >Here's a counterproposal that avoids the above problems. Instead of >having a special A/B notation for ambiguous local times, simply >have section 6.7 require the UTC offset. That is, instead of > 1996-10-27T02:30:00A Europe/Paris [+02:00] > 1996-10-27T02:30:00B Europe/Paris [+01:00] >(where the bracketed items are optional), require the UTC offset instead: > 1996-10-27T02:30:00 Europe/Paris +02:00 > 1996-10-27T02:30:00 Europe/Paris +01:00 >This counterproposal simplifies the notation and removes options, >which is a stated goal of the draft. I completely agree with Paul Eggert's suggestion. >* In practice the choice of time zone rule names may be controversial. >To encourage standardization and head off as much controversy as possible, >I'd like to echo Markus's suggestion to add (to the draft's section 6.3) >as much as possible from the advice to submitters of new time zone >rule names, taken from the `africa' file of the ><URL:ftp://elsie.nci.nih.gov/pub/> registry. My advice here would be to avoid using time zone names/acronyms, period. After all EST means either -05:00, +10:00 or +11:00 depending on nationality and time of year. If, however, time zone acronyms and names have to be used, I would urge 'daylight time' instead of 'summer time' as both standard and summer begin with the same letter, creating further confusion; in Australia, EST can be either +10:00 or +11:00 as mentioned above. Chris Carrier

1 0

Indiana time zoning
by Chris Carrier Jan. 30, 1997

Jan. 30, 1997

samrein(a)mainlink.net wrote on the Subj: Indiana Daylight Savings Time >I was just told today that Indiana only has 4 counties that change time >twice a year. Can you tell me which 4 and why? My latest information has 11 counties in Indiana; 6 in the NW part of the state and 5 in the SW; on CST in winter and CDT in summer. The rest of the state keeps EST all year. The reason for the counties in the NW being on CT all year is because they are part of suburban/exurban Chicago and prefer being on Chicago time. The counties in the SW have similar economic ties to Central Time areas in neighboring states and prefer being on Central Time for that reason. The history of Indiana time zoning is more than a little interesting, and I have a fascinating and ahem, rather personal story about it that I will send anyone who is interested. In 1883, when standard time was promulgated by the railroads, Indiana went on CST without much complaint. Indiana observed CDT during the summer-time periods of 1918-19 and all year under the name Central War Time during the American World War II year-round summer-time period of 1942-02-09 to 1945-09-30. It was here that things began to get interesting. At the end of War Time, half of Indiana decided it liked being on CDT or EST all year and the other half didn't. Therefore, from 1946 onwards, you have the phenomenon of counties deciding what time they wished to be on, cities within those counties deciding they didn't like the county decision and adopting their own time, and even some neighborhoods split with one side of town adopting DST and the other not, or a town being on one time and its post office on another, ad nauseum. Shanks has tracked down 255 separate rules for Indiana time zoning on the postwar period, and I'm quite sure even he missed a lot of the little rules. Aggravating this after 1954 is indeterminacy as to whether the summer-time period should end on the last Sunday in September or October (September was near universal 1921-41 and 1946-54, and should still be, IMHO). In the early 1960s there was more confusion as the summer-time period began in most jurisdictions on the last Sunday in April, but in a few was delayed until late May, usually a Sunday preceding or following or the day of US Memorial Day (at that time, May 30 in all years; and in many of these jurisdictions DST ended on either the day of, the day before or the day after US Labor Day; the 1st Monday in September). It remember reading in a magazine printed in the mid-1960s that there was a 35 mile stretch of road in Indiana where the clocks changed 7 times. The Eastern/Central boundary crept west during this period, and was officially moved to cover half of Indiana in 1961, and most of it, excepting the counties that are still on Central, on the last Sunday in April 1970. The Uniform Time Act of 1967 required Indiana to clean its time act up. The Indiana Legislature's response to this was to pass a law requiring one clock in each county courthouse to be set to and be labeled 'official time' and allowed localities to go on as before. The 1972 amendment to the Uniform Time Act allowed states such as Indiana in split time zones to except the zone on the later time from DST. As soon as it was passed the Eastern Zone area of Indiana so exempted itself. As such it remained on EST during the expanded summer time periods of 1974-5. Even today, there is still some un-official time in Indiana, in the counties near the Ohio border, which are officially on EST all year, but some informally use EDT in the summer time period while using EST as the time recorded on official documents such as birth records, timestamping of deeds, etc... Personally they should have stayed in the Central Zone where they astronomically belong. Ohio should have been the scene for this mess (but Ohio has some interesting time tales of its own). Chris Carrier

1 0

Re: Inverse for gmtime() ??
by ncm＠cantrip.org Jan. 22, 1997

Jan. 22, 1997

Chris Newman <Chris.Newman(a)innosoft.com>: > On Mon, 20 Jan 1997, Markus G. Kuhn wrote: > > I just wanted to start writing a ISO 8601 subset -> time_t conversion > > routine, but to my great disappointment I discovered that ISO C does > > not seem to allow portable conversion of a broken-down time into time_t. > > You can do a binary search of the time_t space using the gmtime() > function. This does require the assumption that time_t is an integral > type, but works well. There is no reason to assume that time_t is integral, and good reasons to assume it often is not, and more often in the future than at present. The restricted range of 32-bit time_t values is a problem in common applications, and until 64-bit machines are universal the easiest way to sidestep the problem is "typedef double time_t;". In any case, since time is a continuous quantity a floating-point representation makes perfect sense, and ANSI (aware of this) permits it. Nathan Myers ncm(a)cantrip.org

2 1

Inverse for gmtime() ??
by kuhn＠cs.purdue.edu Jan. 21, 1997

Jan. 21, 1997

I just wanted to start writing a ISO 8601 subset -> time_t conversion routine, but to my great disappointment I discovered that ISO C does not seem to allow portable conversion of a broken-down time into time_t. In other words, while mktime() is the inverse function to localtime(), there exists no mkgmtime() that is the inverse function to gmtime(). I knew that the C standard library time API is a strange design, but I had no idea that it was *that* bad. The only practical way to get from a broken-down UTC time to time_t seems to be to assume that we are on a POSIX system where the time_t representation is exactly specified. Or did I miss something? In case someone of you is in contact with the folks revising ISO C, I have now a whole list of things that should be fixed in time.h: - add inverse function for gmtime() (mkutime() or mkgmtime()) - add to strftime() conversion specifiers for ISO 8601 week-of-year and year-of-week. - remove the second leap second 61 mentioned in the footnote (contradicts to UTC definition) Instead of adding an inverse function for gmtime, one could also extend struct tm by a new field tm_offset, which is in seconds the difference between the time in the struct tm and the corresponding universal time (in my opinion a much cleaner solution than the tm_isdst hack). But I guess, this might break existing code that does not initialize tm_offset ... Having a tm_offset in struct tm would however still be a good idea as this would allow to implement in strftime() conversion specifiers for the time zone offset (much more interesting than the time zone name). Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

3 2

tzcode1997a.tar.gz and tzdata1997a.tar.gz
by ado Jan. 21, 1997

Jan. 21, 1997

The files ftp://elsie.nci.nih.gov/pub/tzcode1997a.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1997a.tar.gz are now available. These include Paul Eggert's Antarctica (and other changes). I've finessed the "getopt" issue by checking against both -1 and EOF (regardless of POSIX, SunOS 4.1.1's manual says -1 is returned while SunOS 5.5's manual says EOF is returned). --ado

1 0

interested in your mailing list
by Wayne Olsen Jan. 21, 1997

Jan. 21, 1997

send me information please wayne olsen

1 0

More about Antartica
by Antoine Leca Jan. 21, 1997

Jan. 21, 1997

Hello, I've dig up some informations about timezones in the French Southern Territories. First, a Web page in English is available at <URL:http://www.icair.iac.org.nz/science/reports/fr/IFRTP.html>. IFRTP (Institut Français pour la Recherche et la Technologie Polaire) is the French organism in charge of the scientific stations there. They don't have a web page of their own presently. When they will have one, it will be linked in the proper place in <http://www.mesr.fr/organism.htm>. I called this organism, and Mrs. Nicole Pailleau which is in charge of the communications with the remote stations gave me the local hours there. She confirms me that no stations use daylight saving time, even Terre Adelie that is connected with Tasmania for support. There is really two different zones: * one is the islands in the Southern Indian Ocean, namely Kerguelen, Crozet, Amsterdam and Saint-Paul. There are 3 meteorologic bases, in the Kerguelen, in Crozet and in Amsterdam. They are constantly at UTC+5: Martin-de-Viviès Base, Amsterdam Island, -374105+0773155, since 1950 30 persons in winter, 50 in summer Port-aux-Français, Kerguelen Islands, -492110+0701303, since 1951 80 persons in winter, 120 in summer Alfred-Faure Base, Crozet Islands, -462551+0515152, since 1964 35 persons in winter, 50 in summer St Paul Island, near Amsterdam, is uninhabited since 1927 The islands were inhabited by whale-hunters (with oil factories) in the 1920's. They are supported from the island of Réunion. Since they are really in the Indian Ocean, I give them the zone name of Indian/Kerguelen, the name of the largest island; Indian/Port_aux_Francais ought to be more appropriate, but too long. * the second is a base in the main continent, in a area called Terre Adélie. It is named Dumont-d'Urville, and it lies at UTC+10 all year round. It holds 35 persons in winter and 100 in summer. Previously, there were another base, named Port-Martin; it was destroyed by fire in 1954. I included it in the statitics about the past. Also, I read in <http://www.antdiv.gov.au/aad/exop/sfo/macca/macca_aws.html> that Macquarie Is is in the same timezone as Tasmania. But I don't know if it is inhabited all-year round. I joined two diff files about the changes. *** antarc~1 Sun Nov 24 02:07:38 1996 --- ant.new Mon Jan 20 19:47:06 1997 *************** *** 58,71 **** # France # # French Southern Territories with year-round inhabitants ! # Amsterdam Island ! # Crozet Islands ! # Kerguelen Islands ! # St Paul Island # ! # year-round base ! # Dumont d'Urville, Adelie Land, since IGY # Germany - year-round base # Georg von Neumayer --- 58,95 ---- # France # + # From Antoine Leca <Antoine.Leca(a)Renault.FR> (1996-01-20): + # Timezones from Nicole Pailleau at IFRTP (French institute). + # She confirms that French Southern Territories and Terre Adelie bases + # doesn't observe daylight saving time, even if Terre Adelie supplies came + # from Tasmania. + # # French Southern Territories with year-round inhabitants ! # ! # Martin-de-Vivies Base, Amsterdam Island, -374105+0773155, since 1950 ! # Alfred-Faure Base, Crozet Islands, -462551+0515152, since 1964 ! # Port-aux-Francais, Kerguelen Islands, -492110+0701303, since 1951 # ! # St Paul Island - near Amsterdam, uninhabited since 1927 ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Kerguelen 0 - ___ 1950 # Port-aux-Francais ! 5:00 - TFT # ISO code TF Time ! # ! # year-round base in the main continent ! # Dumont-d'Urville, Terre Adelie (Adelie Land), -6040 +14001, since 1956-11 ! # ! # Previously, another base at Port-Martin, 50km east, was operated since 1947 ! # It was destroyed by fire on 1952-01-14 ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Antarctica/DumontDUrville 0 - ___ 1947 ! 10:00 - PMT 1952 Jan 14 # Port-Martin Time ! 0 - ___ 1956 Nov ! 10:00 - DDUT # Dumont-d'Urville Time ! # References ! # <URL:http://www.icair.iac.org.nz/science/reports/fr/IFRTP.html> (1996-01-17). ! # Germany - year-round base # Georg von Neumayer *** zone.tab 1996-11-24 02:07:38 tzdata96n --- zone.tab 1997-01-17 18:38:22 tzdata *************** *** 34,39 **** --- 34,40 ---- AQ -6448-06406 Antarctica/Palmer Palmer Station, Anvers Island AQ -6736+06253 Antarctica/Mawson Mawson Station, Holme Bay AQ -6617+11031 Antarctica/Casey Casey Station, Bailey Peninsula + AQ -6040+14001 Antarctica/DumontDUrville Dumont-d'Urville Base, Terre Adelie AR -3436-05827 America/Buenos_Aires E Argentina (BA, DF, SC, TF) AR -3257-06040 America/Rosario NE Argentina (SF, ER, CN, MN, CC, FM, LP, CH) AR -3124-06411 America/Cordoba W Argentina (CB, SA, TM, LR, SJ, SL, NQ, RN) *************** *** 310,315 **** --- 311,317 ---- SZ -2618+03106 Africa/Mbabane TC +2128-07108 America/Grand_Turk TD +1207+01503 Africa/Ndjamena + TF -492110+0701303 Indian/Kerguelen TG +0608+00113 Africa/Lome TH +1345+10031 Asia/Bangkok TJ +3835+06848 Asia/Dushanbe

2 1

Re: minor fixes for tzcode1996o
by ado＠elsie Jan. 20, 1997

Jan. 20, 1997

> This fixes potential buffer overflows, corrects getopt(3) usage > (getopt(3) returns -1, not EOF these days), and adds another > PCTS tweak to pass an arguably bogus test. The diff is reversed, > sorry about that. > ... > --- time/localtime.c Mon Jan 13 20:17:09 1997 > ... > - if ((strlen(p) + strlen(name) + 2) >= sizeof fullname) > + if ((strlen(p) + strlen(name) + 1) >= sizeof fullname) > return -1; > ... There's a problem if the number of characters in a to-be-generated full file name (exclusive of the trailing '\0') equals or exceeds the size of the filename buffer. The number of characters (exclusive of the trailing '\0') is strlen(p) + strlen(name) + 1 (where the "1" is for the slash that separates the directory from the name) and the size of the filename buffer is sizeof fullname It looks to me as if the above test is correct; does anyone see something I've missed? > --- time/zdump.c Mon Jan 13 20:17:17 1997 > ... > (void) strncpy(buf, abbr(&tm), (sizeof buf) - 1); > - buf[(sizeof buf) - 1] = '\0'; > ... > (void) strncpy(buf, abbr(&newtm), > (sizeof buf) - 1); > - buf[(sizeof buf) - 1] = '\0'; > ... > (void) strncpy(loab, abbr(&lotm), (sizeof loab) - 1); > - loab[(sizeof loab) - 1] = '\0'; The strncpy's above all have static arrays as their destinations; since the static array's are initialized to '\0's, and since the strncpy's can't change the last positions in the arrays (given the "- 1"s in the strncpy arguments), the sets of the last elements to '\0' seem unneeded. Does anyone see something I've missed? > --- time/zic.c Wed Jan 15 16:41:36 1997 > ... > - while ((c = getopt(argc, argv, "d:l:p:L:vsy:")) != -1) > + while ((c = getopt(argc, argv, "d:l:p:L:vsy:")) != EOF) If anyone knows a good way of conditionalizing this (to cope with, for example, SunOS 4.1.1), I'd appreciate hearing from you. --ado

2 1

Minute offsets
by Chris Carrier Jan. 17, 1997

Jan. 17, 1997

Markus G. Kuhn wrote: > I do not have very strong feelings about the optionality of the minute > offset, but my arguments for it are: > - only *very* few countries use it today and time zones are so often > redefined that there is some good hope that the 30-min offset zones > will disappear in 2020 or so. Then, we would not carry around > any more the obsolete minute fields in our headers. > - I personally think that the hour only offset is much more readable > and that the additional implementation effort (one single "if" in > my sample code) is so trivial that it is really not worth any > discussion. I would make minute offsets mandatory, because we are discussing not only contemporary but historical time zone data, when minute offsets were more common. Also IMHO minute offsets are not necessarily a Bad Thing; a small country without any of its territory going through an hourly meridian but with territory going through a minute offset might be better served by the minute offset zone; Portugal and Ireland, for example, fit GMT-0:30 closer than GMT or GMT-1. What I would favor is putting a colon in between hours and minutes, for readability; i.e. the time in Darwin, Australia is easier to read as GMT or UT+09:30 than as +0930. My $0.02 worth...

3 2

Re: C Code for draft-newman-datetime-00.txt
by Antoine Leca Jan. 17, 1997

Jan. 17, 1997

Hi Ken, Hi Tom, Tom Peterson wrote: > > Since ISO C doesn't appear to present restrictions here and TOG says they > > don't support negative time_t's, perhaps this is an area where an industry > > precedent should be set. I've yet to see an errno defined for mktime() on > > other systems, but I don't see anything precluding it. Is this something we > > should consider adding to the tz code base? and Ken Pizzini answered: > > The question I have to ask here is: are we working on an ANSI/ISO C > standard compatible interface, or a POSIX/TOG based standard? If > the latter we can work with the understanding that time_t values > represent seconds since some epoch It's my understanding that the current TZ code request it. > and consider following TOG's > lead in saying that negative time_t values are not allowed. OTOH, I don't fell this is requested by the current code base. > But if we are working on something that trancends POSIX compliance > and should work on any standard C system then I don't feel that > we can reasonably rule out negative time_t values -- the C > standard allows far too many possible underlying semanatics > for time_t values. However, we can't aim at full C portability, since the code base made in *many* places the assumption that time_t is an integral type, counting seconds. And the C standard clearly states other implementations are possible. So, as you and Tom point out, we are "between two chairs". > > Is there an existing errno value/macro that > > would fit the description of "time is not representable"? > > The best existing one I see is ERANGE, but the explanitory text > on this system says "Result too large", so it isn't perfect. > (I feel that the description has a bug myself -- a range error > really does encompass more than just "too large" a result.) As the current standard says, this seems correct. ERANGE is used for signaling overflowing of mathematical operations. And the standard explicitly says that it *could* be used for signaling underflows, but doesn't enforce this behavior. If your system don't do it, "Result too large" seems a good description to me. I don't like the idea of re-using ERANGE, because mktime() can fail for others reasons than excessing the available values for time_t (one obvious example is a time in the autumn overloapping period with tm->tm_isdst==-1). I think a new constant is in order (I don't like the idea of a new signaling mechanism); what about EILTIME? Furthermore, since mktime can fail for different reasons (before Epoch, result too large, wrong DST setting, autumn indetermination, spring gap; others?), perhaps can we set up different constants? I also want to bring this discussion to <news:comp.std.c> as well, in part for bringing this to the attention of the members of the comittee in charge of C standardization, in part for asking the C gurus about the choice of an ESOMETHING constant(s). Amicalement, Antoine

1 0

Re: C Code for draft-newman-datetime-00.txt
by Antoine Leca Jan. 17, 1997

Jan. 17, 1997

Tom Peterson (USG) wrote: <from Ken Pizzini> > > A problematical situation on any implementation is distinguishing > > between an error return from mktime() and mktime() returning a > > legitimate -1 value. [...] > > An error code (or errno) would help here I think. If errno were set to a > particular value when mktime() really couldn't represent the value, we'd have > a way to distinguish between a valid -1 and and error -1 return value. I agree with you. > Problem is, we'd have trouble getting the standards like X/Open to accept > this, since they claim they don't support negative time_t's (ie: times before > the Epoch). Strictly speaking, mktime() is not a X/Open standard, but part of the standard C library. So IMHO, the solution lie more in the realm of ISO/JTC2/SC22/WG14 (the comittee in charge of C standardization) than in X/Open. And BTW, ISO C doesn't put any restriction on the range of the value of the time_t (which is only arithmetical, not necessary [un]signed long int); and Epoch does take any sense as long as ISO C is concerned. Best regards, Antoine

1 0

Re: Minute offsets
by ncm＠cantrip.org Jan. 17, 1997

Jan. 17, 1997

The argument that the time format must be obvious by example, so that idiots won't program it wrong, doesn't really apply any more. With the internet, it's easy to find the free code that implements the standard, and given correct free code, people too lazy to read the standard will also be too lazy to rewrite it. Nathan Myers ncm(a)cantrip.org

1 0

My comments on draft-newman-datetime-00.txt
by kuhn＠cs.purdue.edu Jan. 16, 1997

Jan. 16, 1997

Hello! I am the author of the ISO 8601 summary on http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html and I just found your new Internet draft ftp://ds.internic.net/internet-drafts/draft-newman-datetime-00.txt about a standard date and time notation for the Internet. I agree that such a standard would be very useful and hope to be able to assist you in finishing it. Here are some comments that I wrote down while reading your first draft: 1) You wonder, what standard defines UTC and leap seconds. This standard is ITU-R Recommendation TF.460-4. Using your credit card, you can now order very easily an electronic copy from the International Telecommunication Union Web server http://www.itu.int/itudoc/itu-r/rec/tf.html You'll find there also other related standards regarding UTC and time signal transmission. 2) You suggest in section 3 to implement a rule that assumes for the 2-digit years 50-99 that they belong to the 20th century. Considering that Unix systems cannot represent in time_t any point in time before 1970-01-01 00:00:00Z, and that there are not any electronic documents on the Internet with a timestamp predating 1970, I suggest that 70 is a more reasonable border date. Gives us 20 more years and I expect to be almost dead or at least retired by then. 3) In section 4, you recommend the offset -00:00 to indicate UTC. One might consider the much shorter "Z" notation specified by ISO 8601 for this very common case. Saves a few bytes and is consistent with international radio practice (Z = Zulu = UTC). In section 5.4, you do already allow "Z", so here the text is inconsistent. 4) In section 5.4, you allow the hour value 24. Both 00:00:00 and 24:00:00 are allowed by ISO 8601, but the notation 24:00 identifying the midnight at the end of the day is useful only for time interval notations (e.g., 20:00--24:00) and should not be used for unique timestamps. Better restrict the hour range to 00--23. Times like 24:00:01 definitely violate ISO 8601, but are supported by your grammar. 5) You use the ugly "T" separator between date and time. ISO 8601 supports also the notion of separate date and time fields, so I suggest you simply define your format to consist of a date and a time field separated by a space. This is the ISO 8601 notation used by GNU RCS for instance (see option -zLT). I personally feel that separating date and time field by a space increases human readability and is preferable over the ISO 8601 combined dateTtime field format. 6) In section 6, you suggest an IANA registry of time zone names. Forget this. ;-) Time zone rules and names are thanks to the creativity of our politicians MUCH to dynamic and unstable. For very good reasons, ISO 8601 does not use time zone abbreviations at all. An excellent Internet list of current and historic timezone names that is constantly updated is already available in form of the tz database. You definitely should have a look at this first. <URL:ftp://elsie.nci.nih.gov/pub/tz*>. In addition, your proposal does not use any time zone names (which is a good thing!). 7) You could add a reference to the technical corrigendum 1 for ISO 8601, which fixes a few typos in the standard. 8) You could make the minute part of the time zone optional and require that time zones with an integral number of hours offset to UTC (which are almost all!) should only be represented by a 2-digit offset. That is what GNU RCS does already and I think having only a single colon increases human readability. 9) Feel free to copy my arguments against the ancient 12h am/pm time format from <URL:http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html>, in order to help eradicate this silly notation from new software (for instance, sendmail still uses am/pm in Received: header lines, which I consider to be very bad Internet time practice). You should also not use the am/pm notation in section 5.5, as the am/pm notation is really a very US-specific idea. The rest of the world has used the 24h notation for many decades and other languages than English do not even have terms like am/pm. I highly recommend you to join the tz(a)elsie.nci.nih.gov mailing list, where you'll meet a number of very experienced Internet date, time, and especially timezone experts. Send e-mail to tz-request(a)elsie.nci.nih.gov to join the club and check ftp://elsie.nci.nih.gov/pub/tzarchive.gz for previous discussion. These are my suggestions for your draft. Please let me know when you have made any changes or have any questions. Thanks for your effort! Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

2 4

Re: C Code for draft-newman-datetime-00.txt
by kuhn＠cs.purdue.edu Jan. 16, 1997

Jan. 16, 1997

In message <32DD304D.40D(a)Renault.FR>, Antoine Leca wrote: > I didn't change anything, but this raises a point: wouldn't it be better > to pass a « time_t const *t » argument? > This is for consistency with other library functions, and portability > (particularly when time_t is a floating type). This rises an interesting question: Why does the C library functions always access time_t values by constant pointers and not by simply copying the value??? I never understood this part of the C lib API. How is portability increased by not using a call-by-value here? If there is any good reason that this has been done in libc, then I'd of course also add it to my code. I already did it for consistency with the existing library functions, but I'd like to know why this is supposed to be the right thing to do. > ¤ Comparing t with 0 doesn't take any sense (I know one system where > ¤ (time_t)0 is J2000,0, so negative t are allowed before 2000-01-01 12:00:00Z Ok, you are right. I just hope that the system you know does not encode 2000-01-01 11:59:59Z = (time_t) -1 as this value is reserved by the standard for error conditions. > ¤ Basically, you can't trust strftime to output what you want if you > ¤ don't set the locale to "C" before. > ¤ I know this code is overkill in the vast majority of cases. I just checked the standard again and it does not indicate that any of the conversion specifiers "%Y-%m-%d %H:%M:%S" depend on the locale. There ARE many conversion specifiers that depend on the locale, but not the above ones, so I understand that we do not have to switch to the "C" locale. > ****** 8601.c > if (prec > 0) { > sprintf(buf, ".%09ld", nsec); > buf += prec + 1; > ****** 8601wrt.c > if (prec > 0) { > int i=9; > while (i-->prec) nsec /= 10; > sprintf(buf, ".%0*ld", prec, nsec); > buf += prec + 1; > ****** > > ¤ I wrote this modification for avoiding a overflow of the buffer. > ¤ You may consider it as unnecessary (but you then may consider > ¤ issuing a warning in the man page). I checked already that nsec is not out of range previously, so I think this additional check is redundant. Thanks for your good comments and also for those I received from others. I'll post the next revision here soon. Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

4 3

minor fixes for tzcode1996o
by Todd C. Miller Jan. 16, 1997

Jan. 16, 1997

This fixes potential buffer overflows, corrects getopt(3) usage (getopt(3) returns -1, not EOF these days), and adds another PCTS tweak to pass an arguably bogus test. The diff is reversed, sorry about that. - todd --- time/localtime.c Mon Jan 13 20:17:09 1997 +++ /home/millert/tmp/tzcode1996o/localtime.c Tue Nov 5 11:50:08 1996 @@ -291,10 +276,10 @@ if (name[0] == ':') ++name; doaccess = name[0] == '/'; if (!doaccess) { if ((p = TZDIR) == NULL) return -1; - if ((strlen(p) + strlen(name) + 2) >= sizeof fullname) + if ((strlen(p) + strlen(name) + 1) >= sizeof fullname) return -1; (void) strcpy(fullname, p); (void) strcat(fullname, "/"); @@ -1379,14 +1364,7 @@ dir = tmcomp(&mytm, &yourtm); if (dir != 0) { if (bits-- < 0) -#ifdef PCTS - { - t += 2; - break; - } -#else return WRONG; -#endif if (bits < 0) --t; /* may be needed if new t is minimal */ else if (dir > 0) --- time/zdump.c Mon Jan 13 20:17:17 1997 +++ /home/millert/tmp/tzcode1996o/zdump.c Tue Nov 5 12:00:05 1996 @@ -224,7 +223,6 @@ show(argv[i], t, TRUE); tm = *localtime(&t); (void) strncpy(buf, abbr(&tm), (sizeof buf) - 1); - buf[(sizeof buf) - 1] = '\0'; for ( ; ; ) { if (cutoff != NULL && t >= cuttime) break; @@ -241,7 +239,6 @@ newtm = *localtime(&newt); (void) strncpy(buf, abbr(&newtm), (sizeof buf) - 1); - buf[(sizeof buf) - 1] = '\0'; } t = newt; tm = newtm; @@ -283,7 +280,6 @@ lotm = *localtime(&lot); (void) strncpy(loab, abbr(&lotm), (sizeof loab) - 1); - loab[(sizeof loab) - 1] = '\0'; while ((hit - lot) >= 2) { t = lot / 2 + hit / 2; if (t <= lot) --- time/zic.c Wed Jan 15 16:41:36 1997 +++ /home/millert/tmp/tzcode1996o/zic.c Fri Dec 27 19:42:04 1996 @@ -478,7 +476,7 @@ (void) textdomain(TZ_DOMAIN); #endif /* HAVE_GETTEXT - 0 */ progname = argv[0]; - while ((c = getopt(argc, argv, "d:l:p:L:vsy:")) != -1) + while ((c = getopt(argc, argv, "d:l:p:L:vsy:")) != EOF) switch (c) { default: usage();

1 0

Revised C Code for draft-newman-datetime-00.txt
by kuhn＠cs.purdue.edu Jan. 16, 1997

Jan. 16, 1997

Here comes the revised version of my example ISO 8601 output routine. It includes almost all suggestions that I have received plus some more and I have added test calls that should print on all POSIX systems the following: Show time in various forms: Fri Feb 13 18:59:59 2009 2009-02-13 18:59:59-05 2009-02-13 18:59:59.012-05 2009-02-13 23:59:59Z 2009-02-13 23:59:59.012Z 2009-02-13 23:59:60.012Z 2009-02-13 18:59:60-05 2009-02-13 23:59:59+00 2009-02-14 05:14:59+05:15 2009-02-14 05:14:59.012345678+05:15 Show a DST switch (Central Europe, October 1996): 1996-10-26 23:30:00Z = 1996-10-27 01:30:00+02 1996-10-27 00:00:00Z = 1996-10-27 02:00:00+02 1996-10-27 00:30:00Z = 1996-10-27 02:30:00+02 1996-10-27 01:00:00Z = 1996-10-27 02:00:00+01 1996-10-27 01:30:00Z = 1996-10-27 02:30:00+01 1996-10-27 02:00:00Z = 1996-10-27 03:00:00+01 1996-10-27 02:30:00Z = 1996-10-27 03:30:00+01 Thanks for the many valuable suggestions. Since I know now finally, why localtime() uses call-by-reference, I feel very comfortable with breaking the consistency with this legacy interface. Do you see any other portability or elegance problems? Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu /* * Example implementation of the RFC xxxx profile of ISO 8601 * ASCII standard date and time representation in ANSI/ISO C. * * This implementation is only an informal appendix of RFC xxxx and not * part of the standard. This is an early draft version, do not use * this in products yet. * * Please send comments for improvement to * * Markus Kuhn <kuhn(a)cs.purdue.edu> * * Thanks for suggestions to: * * Chris Newman <Chris.Newman(a)innosoft.com> * Ken Pizzini <ken(a)spry.com> * Antoine Leca <Antoine.Leca(a)renault.fr> * * $Id: demo8601.c,v 1.1 1997-01-15 22:02:37-05 kuhn Exp $ */ #include <stdio.h> #include <stdlib.h> #include <time.h> /* * Create an ISO 8601 time string conforming to the RFC xxxx profile * * Input: * * t the time that will be written as returned by time() * utc if true, then UTC instead of local time will be shown * nsec nanoseconds since start of current second or 0 if unknown * prec number of digits (0..9) for decimal fractions of the * second (set to 0 if nsec is unknown) * * Output: * * s time string with strlen(buf) < 36 * * When time_t does not allow to encode leap seconds (like in POSIX), * you can use the value of second 59 in t and add 1000000000 to nsec * in order to represent a leap second. If input or libary errors * are detected, NULL will be returned, otherwise a pointer to the * output string. If buf is NULL, the time string will be written to * a local buffer. This function is not multithreading safe. * * Markus Kuhn <kuhn(a)cs.purdue.edu>, 1997 */ char * create_timestring(char *s, time_t t, int utc, long nsec, unsigned prec) { char *buf, buffer[36]; struct tm ltm, utm, *tmp; long offset; /* safety checks */ s = buf = (s == NULL) ? buffer : s; *buf = '\0'; if (nsec < 0 || nsec > 1999999999L) return NULL; if (prec > 9) prec = 9; /* convert time */ if ((tmp = gmtime(&t)) == NULL) return NULL; utm = ltm = *tmp; if (!utc) ltm = *localtime(&t); /* leap second handling */ if (nsec > 1000000000L) { ltm.tm_sec++; utm.tm_sec++; nsec -= 1000000000L; } /* basic format */ buf += strftime(buf, 20, "%Y-%m-%d %H:%M:%S", utc ? &utm : &ltm); if (prec > 0) { sprintf(buf, ".%09ld", nsec); buf += prec + 1; } /* time zone offset */ if (utc) { *(buf++) = 'Z'; *buf = '\0'; } else { /* we assume without check that the offset is less than 24 hours */ offset = ltm.tm_yday - utm.tm_yday; if (offset > 1) offset = -24; else if (offset < -1) offset = 24; else offset *= 24; offset += ltm.tm_hour - utm.tm_hour; offset *= 60; offset += ltm.tm_min - utm.tm_min; sprintf(buf, "%+03ld", offset / 60); /* hour offset */ buf += 3; if (offset < 0) offset = -offset; offset %= 60; if (offset != 0) sprintf(buf, ":%02ld", offset); /* minute offset */ } return s; } /* Some test code */ int main() { char buf[50]; time_t now; time_t last_dst_hour; int i; puts("Show time in various forms:\n"); now = 1234569599L; /* on POSIX this is 2009-02-13 23:59:59Z */ putenv("TZ=EST5"); puts(ctime(&now)); create_timestring(buf, now, 0, 0, 0); puts(buf); create_timestring(buf, now, 0, 12345678, 3); puts(buf); create_timestring(buf, now, 1, 0, 0); puts(buf); create_timestring(buf, now, 1, 12345678, 3); puts(buf); create_timestring(buf, now, 1, 1012345678, 3); puts(buf); /* leap */ create_timestring(buf, now, 0, 1012345678, 0); puts(buf); /* leap */ putenv("TZ=UTC0"); create_timestring(buf, now, 0, 0, 0); puts(buf); putenv("TZ=TST-5:15"); create_timestring(buf, now, 0, 0, 0); puts(buf); create_timestring(buf, now, 0, 12345678, 9); puts(buf); puts("\nShow a DST switch (Central Europe, October 1996):\n"); last_dst_hour = (((26L * 365) + 6 + 300) * 24) * 3600; putenv("TZ=CET-1CEST,M3.5.0/2,M10.5.0/3"); for (i = -1; i <= 5; i++) { printf("%s = ", create_timestring(NULL, last_dst_hour + i * 1800, 1, 0, 0)); puts(create_timestring(NULL, last_dst_hour + i * 1800, 0, 0, 0)); } return 0; }

1 0

C Code for draft-newman-datetime-00.txt
by kuhn＠cs.purdue.edu Jan. 15, 1997

Jan. 15, 1997

I have done a sample implementation of the draft-newman-datetime-00.txt ISO 8601 profile with the modifications suggested by Paul and myself already included. So far, this is only the write routine, the parser will follow later. Please scrutinize the code below such that it becomes highly portable and reliable ANSI/ISO C. I have some doubts whether this code will handle the local time form correctly during both DST switch hours. Does anyone know a nicer solution for determining the UTC offset of local time with portable library functions reliably? (May be, something like "utm.tm_isdst = ltm.tm_isdst" before mktime() is still necessary?) Well-engineered ISO C example code that can easily be included in new applications will certainly make the ISO 8601 profile RFC more popular and should definitely be added. I would also like to see new format specifiers in GNU date (and POSIX.2 date) that would allow me to easily generate the UTC offset fields. Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu #include <stdio.h> #include <stdlib.h> #include <time.h> /* * Create an ISO 8601 time string conforming to the RFC xxxx profile * * Input: * * t the time that will be written as returned by clock() * utc if true, then UTC instead of local time will be shown * nsec nanoseconds since start of current second or 0 if unknown * prec number of digits (0..9) for decimal fractions of the * second (set to 0 if nsec is unknown) * * Output: * * buf time string with strlen(buf) < 36 * * When time_t does not allow to encode leap seconds (like in POSIX), * you can use the value of second 59 in t and add 1000000000 to nsec * in order to represent a leap second. If input or libary errors * are detected, buf will be set to be an empty string. This function * is not multithreading safe. * * Markus Kuhn <kuhn(a)cs.purdue.edu>, 1997-01-15 01:00:18-05, early draft */ void create_timestring(char *buf, time_t t, int utc, long nsec, int prec) { struct tm ltm, utm, *tmp; double off; long offset; /* safety checks */ if (buf == NULL) return; *buf = 0; if (t < 0 || nsec < 0 || nsec > 1999999999L) return; if (prec > 9) prec = 9; /* convert time */ if ((tmp = localtime(&t)) == NULL) utc = 1; /* fallback when library does not know local time */ else ltm = *tmp; if ((tmp = gmtime(&t)) == NULL) return; utm = *tmp; /* leap second */ if (nsec > 1000000000L) { ltm.tm_sec++; utm.tm_sec++; nsec -= 1000000000L; } /* basic format */ strftime(buf, 20, "%Y-%m-%d %H:%M:%S", utc ? &utm : &ltm); buf += 19; /* fractional seconds */ if (prec > 0) { sprintf(buf, ".%09ld", nsec); buf += prec + 1; } /* time zone offset */ if (utc) { *(buf++) = 'Z'; *buf = 0; } else { off = difftime(t, mktime(&utm)); if (off < -0.01) { *(buf++) = '-'; offset = -off + 0.5; } else { *(buf++) = '+'; offset = off + 0.5; } offset = (offset + 30) / 60; sprintf(buf, "%02ld", offset / 60); /* hour offset */ buf += 2; offset %= 60; if (offset) sprintf(buf, ":%02ld", offset); /* minute offset */ } return; } int main() { char buf[50]; time_t now; now = time(NULL); puts(ctime(&now)); create_timestring(buf, now, 0, 0, 0); puts(buf); create_timestring(buf, now, 0, 12345678, 3); puts(buf); create_timestring(buf, now, 1, 0, 0); puts(buf); create_timestring(buf, now, 1, 12345678, 3); puts(buf); create_timestring(buf, now, 1, 1012345678, 3); puts(buf); create_timestring(buf, now, 0, 12345678, 9); puts(buf); return 0; }

2 1

Re: -00:00 on draft-newman-datetime-00.txt
by David Keegel Jan. 14, 1997

Jan. 14, 1997

To quote some previously private email (with permission): ] On Sun, 12 Jan 1997, David Keegel wrote: ] > Perhaps when ISO-8601 allows different formats (eg: +hh:mm, +hhmm, or +hh) ] > and RFC822 only allows one of these formats, then it would be appropriate ] > to choose the common format (eg: +hhmm). Chris Newman wrote: ] For the "Internet profile", I selected the +hh:mm form. ISO does allow ] the +hhmm form, but one reading of the spec would say only if all ] punctuation is omitted from the rest of the date time format. If all the ] punctuation is omitted, the format becomes basically unreadable. I agree omitting all punctuation would be a Bad Thing. So the question hinges on whether ISO-8601 says you can omit punctuation from the time- zone, without omitting punctuation from everything else. Would anyone on the tz list like to interpret ISO-8601 to answer this? __________________________________________________________________________ David Keegel <djk(a)cyber.com.au> http://www.cyber.com.au/ +61 3 9642-5997 Cybersource P/L: Unix Systems Administration and TCP/IP network management

1 0

[J. Wunsch: hey (fwd)]
by Garrett Wollman Jan. 13, 1997

Jan. 13, 1997

This is something of a security bug report, but the security problem is not necessarily a bug in the timezone code. However, I do think it's a bug that our code (which is not the very latest tzcode) will crash if the TZ variable is set to point to a non-TZ file. I can think of two ways to combat this: 1) Disallow selection of files containing `.' or starting with a leading `/' unless the name is the same as TZDEFAULT. 2) Use some of the tzh_reserved[] bytes for a magic number. (2) is more flexible, but still allows for a malicious user to cause a core dump. I prefer (1) and will probably implement that unless someone can provide a good reason not to. ------- start of forwarded message (RFC 934 encapsulation) ------- From: J Wunsch <j(a)ida.interface-business.de> To: wollman(a)freebsd.org Subject: hey (fwd) Date: Fri, 10 Jan 1997 12:28:15 +0100 (MET) Hi Garrett, can you deal in time with this problem? Otherwise, i'd look into it myself. - ----- Forwarded message from Adam Kubicki ----- Message-Id: <199701092155.WAA12271(a)innocence.interface-business.de> From: Adam Kubicki <mikee(a)solozzo.tele.pw.edu.pl> Subject: hey To: joerg_wunsch(a)interface-business.de Date: Thu, 09 Jan 1997 23:02:44 MET In-Reply-To: <199612171142.MAA11937(a)ida.interface-business.de>; from "J Wunsch" at Dec 17, 96 12:42 (noon) X-Mailer: Elm [revision: 112.2] hi, there is a bug in tzset() function. setting TZ environment variable to some file, you can cause program to dump core - variables read from this file are used as various offsets in settzname() thus you get sigsegv. Because suid programs dont dump core, its not so dangerous, but you can export TZ in telnet and force login to dump core. gettimeoftheday() in login.c is called after loging in, but before setuid(uid) so you will get login.core in you home directory. this core file will follow symlink allowing you to overwrite any file on system. And, setting TZ to /etc/master.passwd you will find whole master.passwd in core file (touch login.core first to fool default umask/owner core flags). I'be be glad to get a smart patch from you, as quick fix i disabled TZ in telnetd. - -adam - ----- End of forwarded message from Adam Kubicki ----- - -- J"org Wunsch Unix support engineer joerg_wunsch(a)interface-business.de http://www.interface-business.de/~j ------- end -------

3 4

comments on draft-newman-datetime-00.txt
by Paul Eggert Jan. 9, 1997

Jan. 9, 1997

I liked Markus Kuhn's comments on your Internet Draft ``Date and Time on the Internet'' <URL:ftp://ds.internic.net/internet-drafts/draft-newman-datetime-00.txt> (December 1996). I have the following further comments and suggestions, some of them echoing Kuhn, some providing more details. Please let me know if you have any questions about these comments, and I'd appreciate hearing about any updates to your draft. Section 2 This section should mention that all dates use the Gregorian calendar. Section 3 Section 3 suggests that 00-49 should map to 2000-2049, and that 50-99 should map to 1950-1999. This contradicts existing practice in one important set of implementations: the XPG4 standard says that 00-68 should map to 2000-2068, and 69-99 should map to 1969-1999. This accommodates nonnegative Posix timestamps which start at 1970-01-01 00:00:00 UTC (equivalent to 1969-12-31 in some time zones). Any suggestion for mapping 2-digit to 4-digit dates is bound to be controversial. Perhaps it would be best to remove this recommendation entirely. If you must suggest a range, the XPG4 range is a bit better than the range in the December draft, as it matches existing practice better (and it will give you another 19 years to upgrade your software...). The recommendation ``Three digit years MUST be interpreted by adding 1900'' seems to be designed only for interfacing to buggy software (e.g. software that uses C's tm_year value without changing it). It is also incompatible with ISO 8601, which uses 3-digit strings for day-of-year. I suggest removing this recommendation. Section 3 mentions ``two digit'' years and ``three digit'' years without making it clear that we are talking about lexical syntax, not numeric value. This should be clarified. For example, the string `0096' should denote the year 96, not 1996; otherwise there would be no way to specify the year 96. Section 4.1 A good reference for local time zone rules is the tz database maintained by Olson et al (<URL:ftp://elsie.nci.nih.gov/pub/>, updated regularly). Section 4.2 When the local offset is unknown, the offset "-00:00" MAY be used to indicate that the time is in UTC and the local offset is unknown. This is worded a little confusingly -- could you please clarify? Is it common to have situations where UTC is known but local time isn't? Without more motivation, it's hard to see why this suggestion is needed. Section 4.3 An alternative would be to show a list of the timezone labels defined in [section XXX]. I'm not sure what is meant here. Surely by ``timezone label'' you do not mean commonly used strings like `EST', since such strings are ambiguous in practice. E.g. `EST' has one meaning in the US, another in Brazil, and yet another in Australia (where the meaning of `EST' also depends on whether it is winter or summer!). Also, there is controversy about what the time zone labels ought to be -- e.g. should Canadian Eastern Standard Time be called `EST' (English) or `HNE' (French)? If by ``timezone label'' you mean some other identifying label, then I suggest using the Posix TZ string as extended by the Olson package (again, see <URL:ftp://elsie.nci.nih.gov/pub/>). This is common practice, is widely used, and there are multiple implementations; e.g. the source code to another implementation of the client library for the Olson TZ extensions can be found in <URL:ftp://prep.ai.mit.edu/pub/gnu/glibc-1.09.1.tar.gz>. For example, the Olson TZ string `America/Los_Angeles' stands for local time in Los Angeles; the Posix TZ string `CST-8' stands for the time zone named `CST' that is always 8 hours ahead of UTC. The advantage of `America/Los_Angeles' is that it can work correctly for all times in the past (the tz database has entries back to 1883, when Los Angeles adopted standard time), and requires no user modification to work correctly in the future, as the tables can be updated automatically by administrators as needed. Section 5.4 time-hour's range should be 00-23, not 00-24. ISO 8601 allows 24 but people are sometimes confused by it, it makes sorting a bit trickier, and it provides no useful functionality in this context. time-second allows leap seconds (value 60), but many systems do not support leap seconds. (E.g. Posix requires that the host not support leap seconds in time_t values.) The RFC should recommend what to do on a system that lacks leap second support when it is given a time stamp containing a leap second. I suggest that such systems treat values >= 60 as 59.999... (the number of 9s after the decimal point being the maximum allowed by the host). time-secfrac should use "." for the decimal point, as this is more commonly used in computer applications. Usurping "," for the decimal point might cause problems in applications that use "," for other punctuation. ISO 8601 allows "." for decimal point. time-numzone should not require specification of minutes (and seconds) as they are normally zero. E.g. change it to: time-numzone = ("+" / "-") time-hour [":" time-minute] date-time should not require a "T" between the date and the time; it should allow a space as well. This is easier to read, is allowed by ISO 8601, and is common practice. ISO 8601 provides no way to represent years before the year 0000, or after the year 9999. This makes it difficult to represent timestamps in some historical applications. To fix this, you might extend the syntax for date-fullyear to: date-fullyear = ["-"] 4*DIGIT where the years are numbered ..., -0002, -0001, 0000, 0001, 0002, .... (Note that unlike the traditional Julian calendar, there is a year 0 in the modern Gregorian calendar.) Section 6 I don't know of any ``IANA Registry of Timezone Names''. But please see my comments on Section 4.3 above for more details about an existing registry that could be used as the basis of an IANA registry. Appendix A Why is this section needed? Appendix B I don't see why this section is needed, since this draft RFC doesn't care about the day of the week. But if you think it's needed, here's the canonical reference for Zeller's congruence (written in German): Chr. Zeller, Kalender-Formeln, Acta Mathematica, Vol. 9, Nov. 1886 And here is code that is derived directly from Zeller's paper and uses Zeller's notation. #include <stdio.h> /* Return day of week, with 0 meaning Saturday and 1 meaning Sunday. See Chr. Zeller, Kalender-Formeln, Acta Mathematica, Vol. 9, Nov. 1886. */ int zeller (int year, int month, int day) { int jan_or_feb = month < 3; int y = year - jan_or_feb; int J = y / 100; /* century number */ int K = y % 100; /* year number within the same */ int m = month + 12 * jan_or_feb; /* month number */ int q = day; /* day number in the month */ int h = (q + ((m + 1) * 26) / 10 + K + K/4 + J/4 - 2*J) % 7; /* weekday number (1 is Sunday) */ return h; } char *dayofweek[] = { "Saturday", "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday" }; int main () { int year, month, day; printf("Enter the year (0001-9999): "); scanf("%d", &year); printf("\nEnter the month (1-12): "); scanf("%d", &month); printf("\nEnter the day of the month (1-31): "); scanf("%d", &day); printf("The day of the week is: %s\n", dayofweek[zeller (year, month, day)]); return 0; }

5 10

Re: Precise date of Millenium
by Jamie Zawinski Jan. 8, 1997

Jan. 8, 1997

Eric Ulevik wrote: > > Otherwise, the argument is that there was no year zero > in the Julian calendar, and we should celebrate after 2000 years. > Thus 1 January 2001. But people forget that the Gregorian calendar > skipped a number of days, so this is wrong! > > So if you wish to be pedantic, please celebrate on 1 January 2001 > on the Julian calendar, which is 14 January 2001 Gregorian. Well that depends on what event you're celebrating! 2000 years since the first second (apex?) of the Julian calendar? 2000 years since the first second of the Gregorian calendar? (As reckoned in the Julian calendar? Weird, but I think that's what you described...) 2000 years since the Julian calendar was introduced? That's still some centuries away. 2000 years since Jesus was born? Nobody really knows, do they? But hey, any excuse for a party... -- Jamie Zawinski jwz(a)netscape.com http://www.netscape.com/people/jwz/

2 2

Re: Newfoundland double summer time
by Rich Wales Jan. 8, 1997

Jan. 8, 1997

Alex Livingston wrote: island of Newfoundland (-03:30/-01:30, if it's true that double summer time is used there), The island of Newfoundland used "double" daylight savings time only in 1988. They switched back to regular DST the following year. Rich Wales <richw(a)yank.kitchener.on.ca> http://yank.kitchener.on.ca/~richw/

1 0

Re: Australian time zoning
by alex＠agsm.unsw.edu.au Jan. 7, 1997

Jan. 7, 1997

>Alex Livingston writes: > >>>I was told recently that the town (district probably) of >>>Kunumurra, in far north east Western Australia has switched its >>>time zone to be the same as that of the Northern Territory >>>instead of using WA time (they're just over the border, and the >>>WA time zone is wildly inappropriate, so it makes sense). > >>To say that the WA time, 08:00 ahead of UT, in Kununurra (I presume that is >>where is meant: there were no matches for Kunumurra on an AltaVista Web >>search but about 200 for Kununurra [and 9 and 7 for Kunnunurra and Kununnurra >>respectively]) is wildly inappropriate is more than an overstatement. The >>WA-NT border runs along the 129 deg. E meridian, so WA time in Kunnunurra is >>less than 36 minutes behind LMT. Is that particularly inappropriate? > >>If Kununurra adopts / has adopted NT time, 09:30 ahead of UT, then its time >>will be / is more than 54 minutes ahead of LMT. Isn't that even more >>"inappropriate"? It is Australia's "Central Time" (09:30 ahead of UT) that is >>inappropriate. The closest it comes to being "appropriate" is on SA's eastern >>border with NSW, where it is still 6 minutes ahead of LMT. I need to confess an oversight here: In fact, the closest Australia's "Central Time" comes to being "appropriate" is at the easternmost point of the shire containing the mining town of Broken Hill (and not much else), namely Yancowinna, NSW, which abuts the SA border. This town is considerably closer to SA's largest capital and largest city (Adelaide) then NSW's (Sydney) and in the shire containing it "Central Time" is kept, along with SA's daylight saving changes. However, unless this shire is particularly huge (and I'm sure it isn't), even at this point "Central Time" is probably still a couple of minutes ahead of LMT. >According to Doane (1972) nt.au and sa.au adopted GMT+9 when they first >adopted standard time 1895-02-01, and then moved to GMT+9:30 on 1899-05-01. >Like many places, they moved from the right time to the wrong time. That concurs with what I have read in a South Australian Yearbook. >I believe that the change was made because Adelaide (138E35), the largest city >in the two states/territories is right on the eastern edge of the time zone >and prefers to be on LMT+0:16 to LMT-0:14. Maybe. Or it didn't want to be so far behind the eastern states (especially Melbourne). >>IMHO Australia's time zoning is a farce. Australia is wholly responsible for >>3 of world's "off the hour" time zones (central zone, Lord Howe Island and >>Norfolk Island) and partially responsible for another 1 (Cocos Islands - same >>time as Burma). > >While I would be opposed to current ACT if I lived there, I do not regard off- >hour zones to be a bad thing, if it is a better fit to LMT. (ACT, of course, >does NOT meet this standard.) If I lived in Portugal or Ireland, I would be >in favor of GMT-0:30 instead of GMT or GMT-1. In the USA the row of states >from North Dakota to Texas would be better off on GMT-6:30 instead of -6, >especially since they all keep DST until late October. Doesn't the practice of observing DST blow any pretended association between legal time and LMT completely out of the water anyway? If a whole-hour intervals between zones are small enough to adequately resolve legal time for all practical purposes in one part of the world, aren't they small enough in every part? I would rather see time zone boundaries moved than off-hour time zones used. I lived most of my life in South Australia, and it irritated me when I had to work out the time almost anywhere else in the world and I had to get that half hour in the right direction (for others it would have been a snap, I'm sure). Another advantage of whole-hour timezone differences is that live broadcasts could give "global" time calls in terms of minutes before or after the hour. Yet another is that it reduces the proliferation of different times kept simultaneously when daylight-saving time is observed (e.g. there are at present five different times in use on the Australian mainland alone, six if the time kept at the roadhouse just west of the WA-SA border [UT+08:45, 0:45 ahead of WA and 1:45 behind SA!] is counted; if whole-hour time zones were in use there would be no more than four). >>There seems to me to be two main options for the central zone: >> >>1: Put the whole zone on UT+10 year-round (no more inappropriate than >>Argentina, not to mention China), with the possible exception of the >>southwest corner of SA (where hardly anyone lives), which could keep on UT+9 ----> ----> shouldn't have been there ^^ >>(whether "officially" or otherwise) along with the southeast corner of WA >>(where even fewer people live) which already keeps UT+8:45 year-round (ugh!). >>2: Put the whole zone on UT+9 during a standardised non-daylight-saving >>period, advancing the southern section to UT+10 during a standardised >>daylight-saving period. A third main option I forgot when I wrote that is: 3: Put the whole zone on UT+10 during a standardised daylight-saving period, retarding the southern section to UT+9 during a standardised non-daylight-saving period (i.e., same as 2, but with northern section on UT+10 year-round instead of UT+9 year-round). In any of these cases consideration could be given to keeping UT+9 in eastern and northern parts of WA. _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9931-9349 Telephone: +61 2 9931-9264

1 0

Re: The year 0 AD
by alex＠agsm.unsw.edu.au Jan. 7, 1997

Jan. 7, 1997

Peter Hullah wrote: >I think that, if you re-read what Chris said, he is of the same opinion >as you - as are, probably, >most clear thinking people and we probably don't need it spelt out in >words of one syllable. I'm sorry to have let off steam in the wrong forum and bored many people (grovel). I don't doubt that Chris is of the same general opinion as me. I'm afraid it triggered me off and I got carried away. But I hope you don't object to the use of words of one syllable in any context ;-) . Happy New Year to you too (no sarcasm intended). Eric Ulevik wrote: >Otherwise, the argument is that there was no year zero >in the Julian calendar I can't resist hammering this point: There is no modern-day obvious inevitability for a "year zero" in any calendar, just as there is no "day 0" at the beginning of a month or "month 0" at the beginning of a year (and I could list any number of other examples from very different contexts). Talk of a "year zero" is a red herring (though not a malicious or deliberate one). It is to my mind condescending and supercilious to belittle ancient calendar designers by claiming they didn't have a "concept of zero" - they probably did in fact, but they didn't need it. Well, that had better be the last I say on this topic here! _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9931-9349 Telephone: +61 2 9931-9264

1 0

Re: Precise date of Millenium
by kuhn＠cs.purdue.edu Jan. 6, 1997

Jan. 6, 1997

In message <32D16CDA.424F(a)ozemail.com.au>, Eric Ulevik wrote: > The obvious time to celebrate is when the calendar rolls over: > January 1 2000. This is when most of the world will celebrate. > (It is also when some computer systems might have some problems). > > Otherwise, the argument is that there was no year zero > in the Julian calendar, and we should celebrate after 2000 years. > Thus 1 January 2001. But people forget that the Gregorian calendar > skipped a number of days, so this is wrong! > > So if you wish to be pedantic, please celebrate on 1 January 2001 > on the Julian calendar, which is 14 January 2001 Gregorian. This is one of the frequently discussed topics on the net these days (and has been over the past 10 years during which I have been watching). You can find dozens of these threads with <URL:http://www.dejanews.com/>. In many senses, the discussion is futile as various definitions of the century and its roll-over have their justification. At least for Germans, Chancelor Kohl (Ph.D. in history) has defined in some interviews that the next millenium will start at 2001-01-01 (in the context that the German Mark will be replaced by the Euro with the beginning of the next millenium, something that causes already MUCH more software engineering work than the year-2000 problem). The real question is not when some counting system rolls over, but when is the right time to party. And the most intelligent answer I have heard on this so far is of course to party on all occations: 2000-01-01, 2001-01-01, 2001-01-14, etc. Therefore, I see the job of time and calendar experts to flood the media with many weired suggestions of when the right time for a new-millenium-party might be, to maximize their number. COBOL reverse engineering experts will certainly party on 00-01-01, Unix system administrators will wait until their epoch overflows 2038-01-19 03:14:08Z (signed 32-bit int) or 2106-02-07 06:28:16Z (unsigned 32-bit int). BTW: Hasn't Arthur C. Clark's HAL its birthdate in a few days? Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

1 0

Re: The year 0 AD
by alex＠agsm.unsw.edu.au Jan. 6, 1997

Jan. 6, 1997

>"Markus G. Kuhn" > INTERNET:kuhn@cs.purdue.edu > >>ISO 8601 provides no way to represent years before the year 0000, or >>after the year 9999. This makes it difficult to represent timestamps >>in some historical applications. To fix this, you might extend the >>syntax for date-fullyear to: > >date-fullyear = ["-"] 4*DIGIT > >>where the years are numbered ..., -0002, -0001, 0000, 0001, 0002, .... >>(Note that unlike the traditional Julian calendar, there is a year 0 >>in the modern Gregorian calendar.) > >WRONG! Negative year numbers are not part of the Gregorian calendar. Still not quite right: *non-positive* numbers are not part of the Gregorian calendar. Which presents me an opportunity too hard to resist to scream something that I have never yet explicitly read anywhere on this discussion group or anywhere else on the Internet. Year numbers are *ordinal* (as opposed to cardinal - correct me if I've got this the wrong way round), i.e., like the day of the month (and the month of the year when written numerically), they indicate the "howmanyeth" year it is (I can't think how better to put it). AD 1 was the *1st* year (of the era). 1997 is the 1997th year. It follows that the *1st decade* comprised the years 1 to 10 *inclusive* (the 1st, 2nd, 3rd, ..., and 10th years); the *1st century* comprised the years 1 to 100 *inclusive*; the *1st millennium* comprised the years 1 to 1000 *inclusive*. And 2000 will be the 2000th year and hence the last year of the 200th decade, the 20th century, and the 2nd millennium. This is one virtually unchallengable way of explaining why the next century (and millennium) begins at the beginning of 2001 (and not 2000) - and pointing that out is the main reason I'm writing this (though I guess I'm preaching to the converted here). Unlike time of day, specifications of year, month, and day of the month (and dates in general) indicate a *period* of time, not an instant. It is 1997 for a whole year; it is 10 o'clock for no time at all. Dates are discrete, time of day is a continuum. Just as the days within a month (and the months within a year) are numbered starting at 1, so are the years of an era. Another illustration (in case it still hasn't sunk in): The second half of a 30-day month starts on the 16th; the second half of the year starts with the 7th month; and the second half of a century starts with the 51st year of that century (ignoring for the moment the fact that months and years are not equal in length etc., making the use of the word "half" here questionable). >There are two ways to number years before 1 AD, astronomical and historical. > >In historical dating, the year 1 AD is preceded by 1 BC, as there was no >concept of 0 in Western civilization when Exigius set up the Anno Domini year >count in AD 532. The BC era is anomalous only in that the years are counted from latest to earliest rather than earliest to latest. Whether or not there was a "concept of 0" back then is entirely irrelevant. (I'm sure that in fact there already was something akin to that - it just might not have been formalized.) With what number do you label the first of something? Go on, say it! Which month of the year is this? On what date did it begin? Which century did Jesus Christ die in? With which year of the era did the era begin? >In astronomical dating, there is no BC: everything is AD, the year 1 AD is >preceded by the year 0 AD, which is preceded by -1 AD, preceded by -2, etc... > >Here's a way to remember it: Julius Caesar was assassinated on 15 March 44 BC, >historical dating, and -43 March 15, astronomical dating. Introducing a year 0 in order to make centuries of the era start when three digits change in the year number sets the cat squarely among the pigeons: If the BC era is to be retained and its centuries are also to change on such occasions, a year 0 BC would also have to be introduced! Then we'd have the years passing thus: ... BC 1, BC 0, AD 0, AD 1, .... A fine improvement! Unless the year AD 0 is called the "1st year" (rather than the "0th"), which I would have thought rather defeats the purpose, calling the years 0 to 99 the "1st century" would be inconsistent anyway: they should be referred to as century 0 (the 0th century?), and the years 0 to 9 as decade 0, and the years 1000 to 1999 as millennium 1 (the 1st millennium?) and the years 1900 to 1999 as century 19 (the 19th century?). If astronomical dating were to become the norm, what sense does a term like "1st century" make? What years did it consist of? Years 0 to 99 or years 1 to 100 (or years -14999999999 to -14999999899)? What was the century before it? The "0th"? What years did it consist of? Years -100 to -1 or years -99 to 0? Facts must be faced (though some would disagree with me there I'm sure): years, months and days are numbered like lines of poem, verses of a song, pages of a book, lots in a subdivision, diskettes in a box, and countless (pardon the pun) other things. That this means that the first 10 of anything includes the 10th, the first 100 the 100th, the first 1000 the 1000th, and the second 1000 and the twentieth 100 the 2000th simply cannot be got around. By all means celebrate the beginning of the 2000th year at the beginning of 2000; but let that be the beginning of a year-long party climaxing at the end when the 2000th year, the 200th decade, the 20th century and the 2nd millennium end and the 3rd millennium, the 21st century, the 201st decade and the 2001st year begin. (On the other hand these are just arbitrary numbers given very tenuous significance only because of the human race's extremely unfortunate choice of base 10 to count in - and Jesus Christ was almost certainly born in BC 7 or 6 anyway, so we're celebrating 2000 years since nothing in particular!) _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9313-7279 Telephone: +61 2 9931-9264

2 1

Re: -00:00 on draft-newman-datetime-00.txt
by alex＠agsm.unsw.edu.au Jan. 6, 1997

Jan. 6, 1997

Robert Elz writes: > Date: Thu, 02 Jan 1997 21:46:47 -0500 > From: kuhn(a)cs.purdue.edu ("Markus G. Kuhn") > Message-ID: <199701030246.VAA09620(a)ector.cs.purdue.edu> [snip] > We go even one step further and remove the redundant minute offset digits. > >The minutes offset is certainly not redundant. I find it hard to >believe that anyone who knows anything about time zones can believe >that. In Australia right now there are two different time zones >that are not even hours. +1030 and +0930. There are two only >because the former (further south) has summer time (it isn't >daylight saving time in Aust, it is Summer Time) and the northern >section (which gets close to the equator, and well into the tropics) >doesn't. Acutally, there are no fewer than *four* off-the-hour time "zones" in effect in Australian territory at the moment. Besides the two mentioned above, there is Cocos Islands time (+06:30) and Norfolk Island time (+11:30). When daylight saving is not in effect, there are still four, as, absurdly, Lord Howe Island (east of NSW) changes from +11:00 to +10:30. >There are also half hour offsets in India, and other places. Besides those already mentioned there is Burma (+06:30), Afganistan (+04:30), Iran (+03:30), Sri Lanka (+06:30, an hour ahead of India, but only since very recently), island of Newfoundland (-03:30/-01:30, if it's true that double summer time is used there), Marquesas Islands (-09:30), Pitcairn and some other islands in the south Pacific (-08:30). There are also two quarter-hour (or should one say "three-quarter-hour") time-zone offsets in effect: Nepal (+05:45) and Chatham Islands (+12:45/+13:45), east of New Zealand. However, over the last half century or so there has, thankfully, been a general reduction in the number of off-hour time zones in use in the world. [snip] >That might not need a lookup table, but it is ambiguous, and >much much worse. You certainly wouldn't have got 19970103 >as that's horrid for humans to parse, and unknown in the US >(and generally here as well, if that matters). 19970103 is only difficult for humans to parse because of the lack of separators. I cannot believe that implementing this obviously superior and consistent ordering of numeric date specifications is harder to understand than the two other orderings in common use. Several countries already use it, e.g. Sweden, Hungary and China (and, I believe, until it was corrupted by the US, Japan). If fact I think it could and should be made a worldwide standard. Just think how much confusion would be avoided, and in how much better an order things labeled with dates would sort into. [snip] _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9931-9349 Telephone: +61 2 9931-9264

1 0

The year 0 AD
by Chris Carrier Jan. 3, 1997

Jan. 3, 1997

"Markus G. Kuhn" > INTERNET:kuhn@cs.purdue.edu >ISO 8601 provides no way to represent years before the year 0000, or >after the year 9999. This makes it difficult to represent timestamps >in some historical applications. To fix this, you might extend the >syntax for date-fullyear to: date-fullyear = ["-"] 4*DIGIT >where the years are numbered ..., -0002, -0001, 0000, 0001, 0002, .... >(Note that unlike the traditional Julian calendar, there is a year 0 >in the modern Gregorian calendar.) WRONG! Negative year numbers are not part of the Gregorian calendar. There are two ways to number years before 1 AD, astronomical and historical. In historical dating, the year 1 AD is preceded by 1 BC, as there was no concept of 0 in Western civilization when Exigius set up the Anno Domini year count in AD 532. In astronomical dating, there is no BC: everything is AD, the year 1 AD is preceded by the year 0 AD, which is preceded by -1 AD, preceded by -2, etc... Here's a way to remember it: Julius Caesar was assassinated on 15 March 44 BC, historical dating, and -43 March 15, astronomical dating.

1 0

time-zone-related comments on draft-ietf-calsch-csct-00.txt
by Paul Eggert Jan. 3, 1997

Jan. 3, 1997

Here are some comments on the time-zone-related parts of your Internet Draft ``MIME Calendaring and Scheduling Content Type'' <URL:ftp://ds.internic.net/internet-drafts/draft-ietf-calsch-csct-00.txt> (November 1996). Please let me know if you have any questions about these comments, and I'd appreciate hearing about any updates to your draft. The comments below are similar to comments I've made about draft-ietf-calsch-sch-00.txt and draft-newman-datetime-00.txt, which I can forward if you're interested. 3.1.3.7 Date and Time The examples do not match the grammar in the use of the character `T' to separate date and time. The grammar specifies date followed by time; the examples use `T'. The grammar is to be preferred here. Common practice (allowed by ISO 8601) is to write the date followed by a space followed by time; this is easier for humans to read. ISO 8601 allows fractions to be preceded by `.' instead of `,'; this should be allowed by the grammar. The grammar allows a utc-offset without a sign; this should be fixed, as utc-offsets always have a sign in ISO 8601. Also, common practice (allowed by ISO 8601) is to omit the `:' and minutes of a UTC offset when minutes are zero. Here is a proposed patch: utc-offset = (_+_ / _-_) hour [[_:_] minute] Following the above suggestions, the examples can be expressed as follows in the extended notation: 1996-04-15 08:30:00-05 1996-04-15 13:30:00Z 3.1.5.2 Daylight Savings Rule 3.1.5.5 Time Zone The underlying model in these sections is too simplistic. It assumes that there is a ``standard time zone'' for the home calendar system, together with a single date and time for entering and exiting daylight saving time. However, locations sometimes alter the UTC offset of standard time (e.g. Portugal and Sri Lanka in 1996). Also, some locales have observed double daylight saving time for part of the summer (e.g. Britain in 1947), and two transitions do not suffice to represent this. The model should be fixed to allow an arbitrary sequence of UTC offset changes. If necessary, each change could be labeled by a daylight saving flag (to say whether the resulting time is considered to be ``daylight saving''), and a string label (e.g. `EST') that can be internationalized (e.g. to `HNE' for French-speakers in Montreal). I suggest that you consult the public domain time zone database maintained by Olson et al (<URL:ftp://elsie.nci.nih.gov/pub/>, updated regularly) for ideas about how time zone and daylight saving information could be represented. For example, you could pass labels that identify time zone and daylight saving rules. In the Olson scheme, the label `America/Los_Angeles' identifies the complete UTC offset history for Los Angeles from to the introduction of standard time in 1883 to the indefinite future. The Olson database is updated as governments change the rules, so the label `America/Los_Angeles' can be used by application programs without worrying about the details. By the way, the proper term is ``daylight saving time'', not ``daylight savings time'' (at least, that is what the OED and the Random House Unabridged Dictionary prefer).

1 0

time-zone-related comments on draft-ietf-calsch-sch-00.txt
by Paul Eggert Jan. 3, 1997

Jan. 3, 1997

Here are some comments on the time-zone-related parts of your Internet Draft ``MIME application/calendar Content Type'' <URL:ftp://ds.internic.net/internet-drafts/draft-ietf-calsch-sch-00.txt> (November 1996). Please let me know if you have any questions about these comments, and I'd appreciate hearing about any updates to your draft. The comments below are similar to comments I've made about draft-ietf-calsch-csct-00.txt and draft-newman-datetime-00.txt, which I can forward if you're interested. 3.2.3.19 TZID This section suggests that it is ``likely that we want an IANA registry of time zone/daylight rule names''. I suggest that you consult the public domain time zone database maintained by Olson et al (<URL:ftp://elsie.nci.nih.gov/pub/>, updated regularly) for ideas about how such a registry should be maintained. The Olson scheme is an upward-compatible extension of the Posix TZ string representation for time zone and daylight saving rules. For example, in the Olson scheme, the label `America/Los_Angeles' identifies the complete UTC offset history for Los Angeles from to the introduction of standard time in 1883 to the indefinite future. The Olson database is updated as governments change the rules, so the label `America/Los_Angeles' can be used by application programs without worrying about the details. It should be easy to convert the Olson database to any proposed IANA registry of time zone and daylight saving info. Perhaps, as a first cut, you could start with the Olson database as the IANA registry. You might contact the mailing list tz(a)elsie.nci.nih.gov if you are interested in using their work. 3.2.3.20 TZBias 3.2.3.21 TZDstBias 3.2.3.22 TZStdBias 3.2.3.23 TZStdTrans 3.2.3.24 TZDstTrans 3.3.1.2 Definitions 3.3.1.4 Recurring Event Date and Time Specification The underlying model in these sections is too simplistic. It assumes that there is a ``standard time zone'' for the home calendar system, together with a single date and time for entering and exiting daylight saving time. However, locations sometimes alter the UTC offset of standard time (e.g. Portugal and Sri Lanka in 1996). Also, some locales have observed double daylight saving time for part of the summer (e.g. Britain in 1947), and TZStdBias does not suffice to represent this. The model should be fixed to allow an arbitrary sequence of UTC offset changes. If necessary, each change could be labeled by a daylight saving flag (to say whether the resulting time is considered to be ``daylight saving''), and a string label (e.g. `EST') that can be internationalized (e.g. to `HNE' for French-speakers in Montreal). This would be simpler and more accurate than the model in draft-ietf-calsch-sch-00.txt. I suggest that you consult the Olson database for ideas about how time zone and daylight saving information could be represented. 3.3.1.2 Definitions The proper term is ``daylight saving time'', not ``daylight savings time'' (at least, that is what the OED and the Random House Unabridged Dictionary prefer). ``Pacific Daylight Savings Time'' should be ``Pacific Daylight Time''. 3.3.1.4 Recurring Event Date and Time Specification This section does not address the problem of ``impossible times'' (e.g. `1996-04-07 02:30:00', which does not denote a valid local time in Los Angeles) or ``ambiguous times'' (e.g. `1996-10-27 01:30:00', which denotes two distinct valid local times in Los Angeles). When a time is converted from some locale to UTC, it may be found to be impossible or ambiguous; in that case, what should a scheduling application do?

1 0

time zone article
by Joe Celko [71062,1056] Jan. 1, 1997

Jan. 1, 1997

I am writing a book on data and databases. I need a short piece on timezones, UTC, leap seconds, etc. for the section on temporal data. If anyone has the time (pun) and would like to contribute, I can pay them a few bucks for their effort. I am more interested in getting the data than in getting a finished ready-to-publish article. Here is my biosketch by way of introduction: BIOSKETCH: Joe Celko is an Atlanta-based consultant with Northern Lights Software Ltd. and has been a member of the ANSI X3H2 Database Standards Committee since 1987 and helped write the ANSI/ISO SQL-89 and SQL-92 standards. Joe Celko has had several regular monthly or biweekly columns in the past eleven years in the computer trade and academic press. His current columns are: "SQL Explorer" in DBMS (Miller-Freeman), "WATCOM SQL Corner" in POWERBUILDER DEVELOPERS' JOURNAL (SysCon). Most recently, Mr. Celko also wrote: "Celko on SQL" in DATABASE PROGRAMMING & DESIGN (Miller-Freeman); "SQL Puzzle" in BOXES & ARROWS (Frank Sweet Publishing); "DBMS/Report" in SYSTEMS INTEGRATION (Cahner-Ziff); "Data Desk" in TECH SPECIALIST (R&D), "Data Points" in PC TECHNIQUES (Coriolis Group), "Celko on Software" in COMPUTING (VNC Publications, UK). and was editor for the "Puzzles & Problems" section of ABACUS (Springer-Verlag). Joe Celko is the author of four books on SQL: SQL FOR SMARTIES (Morgan-Kaufmann, 1995), INSTANT SQL (Wrox Press,1995), SQL PUZZLES & SOLUTIONS (Morgan-Kaufmann, 1997) and SECRETS OF THE SQL MASTER (Sys-Con, 1996). He is currently do a series under his name for Morgan-Kaufmann publishers. Joe Celko is a regular speaker and SQL instructor for Digital Consulting Inc., Norm DiNardi Enterprises, Boston University Corporate Education Center and Miller-Freeman Seminars. --CELKO--

1 0

Internet Profile for ISO 8601
by kuhn＠cs.purdue.edu Dec. 28, 1996

Dec. 28, 1996

You might be interested in reviewing the new Internet draft standard ftp://ds.internic.net/internet-drafts/draft-newman-datetime-00.txt which describes the future recommended Internet date and time notation for new applications. This standard describes a subset of ISO 8601 and recommended usage practice. For more information about ISO 8601, see also http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html The draft-newman-datetime-00.txt is still an early draft and could require some input from the date and time experts here. In addition, I also wanted to mention that all ITU-R TF Recommendations can now be ordered on-line from http://www.itu.int/itudoc/itu-r/rec/tf.html This includes for instance ITU-R TF.460-4, the standard that defines UTC. Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

1 0

tzcode1996o.tar.gz and tzdata1996n.tar.gz
by ado Dec. 28, 1996

Dec. 28, 1996

The files ftp://elsie.nci.nih.gov/pub/tzcode1996o.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1996n.tar.gz are now available; these incorporate Paul Eggert's latest changes. --ado

1 0

Re: Timezone naming
by Janis.Papanagnou＠pc-plus.DE Dec. 27, 1996

Dec. 27, 1996

Markus wrote: > The time zone string CET or MET is never parsed by any software, because in > all applications (e-mail, news, etc.) the time format standards require > that a numeric local time - UTC offset is also provided (e.g., required by > RFC822 except for US names) and the numeric value is then used. Therefore, > MET->CET is no compatibility problem. That seems quite reasonable. A formal scheme is what I expect when handling time zones (myself or by application). > Consequently: Only humans have to recognize the time zone abbreviation > and it definitely does not make sense here to use one that does not > follow common practice (Langenscheid, PTB, SkyTV, CNN, etc.). That's the point, humans should be provided a user-friendly naming scheme. But I cannot second your conclusions. The US time zone "names" are very strange (to me!), but I don't care - it's not my domain, I have not to use them. CNN, etc. is not what I would call common practice; in DE I hear the terms MEZ (or MET). I am not talking with the PTB, nor do I inform myself by US broadcasts. Talking about i18n: are these TZ "names" really considered a matter of international standards ? Concerning computer variable TZ, I doubt it. Concerning the definition of an international standard, I do not think that the current 3-letter TZ "names" serve for i18n-"codes"; they are neither formal nor intuitive. As posted some weeks ago, ambiguities and coincidences happen to exist, too. The Olsen DB as a quasi-standard on computers shall fulfill demands of an IS ? To come back to the user-friendliness: the three letter "names" are easily misinterpreted (from a global view); I would prefer something intuitive. Janis

3 2

Australian time zoning
by Chris Carrier Dec. 24, 1996

Dec. 24, 1996

Alex Livingston writes: >>I was told recently that the town (district probably) of >>Kunumurra, in far north east Western Australia has switched its >>time zone to be the same as that of the Northern Territory >>instead of using WA time (they're just over the border, and the >>WA time zone is wildly inappropriate, so it makes sense). >To say that the WA time, 08:00 ahead of UT, in Kununurra (I presume that is >where is meant: there were no matches for Kunumurra on an AltaVista Web >search but about 200 for Kununurra [and 9 and 7 for Kunnunurra and Kununnurra >respectively]) is wildly inappropriate is more than an overstatement. The >WA-NT border runs along the 129 deg. E meridian, so WA time in Kunnunurra is >less than 36 minutes behind LMT. Is that particularly inappropriate? >If Kununurra adopts / has adopted NT time, 09:30 ahead of UT, then its time >will be / is more than 54 minutes ahead of LMT. Isn't that even more >"inappropriate"? It is Australia's "Central Time" (09:30 ahead of UT) that is >inappropriate. The closest it comes to being "appropriate" is on SA's eastern >border with NSW, where it is still 6 minutes ahead of LMT. According to Doane (1972) nt.au and sa.au adopted GMT+9 when they first adopted standard time 1895-02-01, and then moved to GMT+9:30 on 1899-05-01. Like many places, they moved from the right time to the wrong time. I believe that the change was made because Adelaide (138E35), the largest city in the two states/territories is right on the eastern edge of the time zone and prefers to be on LMT+0:16 to LMT-0:14. >IMHO Australia's time zoning is a farce. Australia is wholly responsible for >3 of world's "off the hour" time zones (central zone, Lord Howe Island and >Norfolk Island) and partially responsible for another 1 (Cocos Islands - same >time as Burma). While I would be opposed to current ACT if I lived there, I do not regard off- hour zones to be a bad thing, if it is a better fit to LMT. (ACT, of course, does NOT meet this standard.) If I lived in Portugal or Ireland, I would be in favor of GMT-0:30 instead of GMT or GMT-1. In the USA the row of states from North Dakota to Texas would be better off on GMT-6:30 instead of -6, especially since they all keep DST until late October. The least justifiable of these is "Central Time", and Lord Howe Island comes a close second, what with its almost entirely pointless daylight-saving practices. (I started a message about the latter several weeks ago but haven't got round to finishing it yet.): There seems to me to be two main options for the central zone: >1: Put the whole zone on UT+10 year-round (no more inappropriate than >Argentina, not to mention China), with the possible exception of the >southwest corner of SA (where hardly anyone lives), which could keep on UT+9 >(whether "officially" or otherwise) along with the southeast corner of WA >(where even fewer people live) which already keeps UT+8:45 year-round (ugh!). Actually if I lived in Kununurra I would want to keep UT+8:45 as opposed to either UT+8 (and certainly +9:30!). Given that LMT is probably about UT+8:35 (since the WA-NT border is +8:36), +8:45 is better than +8, +9, or +9:30. It would also be WA+0:45 and NT-0:45. >2: Put the whole zone on UT+9 during a standardised non-daylight-saving >period, advancing the southern section to UT+10 during a standardised >daylight-saving period. I like this idea better than idea 1.

1 0

No progress on EU eighth summertime directive
by peter＠aldie.co.uk Dec. 20, 1996

Dec. 20, 1996

There still doesn't appear to be much action on getting the next (eighth) EC Directive on summertime arrangements finalised. My contact in the EC Information Office in Edinburgh produced the following response from Brussels in mid November: `Theoretically the proposal should be adopted by the end of the year. Nevertheless European Parliament having not adopted its opinion yet, we do not know if the Council will be able to adopt a common postion by this date. In this case the final adoption might be in early spring.' She also sent me some newspaper clippings from 29 Nov that said the European Parliament had `backed plans to have the European Union change to summertime on the same day to end the disruption caused when some states are out of phase with the rest'. As we are already in this state this can only be a reference to the French proposals to opt out of Summer Time altogether. I didn't think that the European Parliament had much role in adopting directives. I was going to point to the Commission's UK web pages at http://www.cec.org.uk for a page which explained the directive creation process but it seems to have vanished since I last looked. I am pretty sure that this directive is controlled by the EU transport ministers. They had a meeting on 12--13 December. They did not discuss the issue, or at least if they did it wasn't mentioned in the press release after the meeting, and they certainly didn't decide anything. The next (informal) meeting is on 31 Jan 97. The next formal meeting is on 11 Mar 97. Lots of diary publishers are probably getting worried. I hope that the EU isn't organising any sort of Millennium event. I would hope that even they would be embarrassed by missing that deadline. :-) Peter Ilieve peter(a)aldie.co.uk

1 0

Re: Probable change needed to the Aust zone files
by alex＠agsm.unsw.edu.au Dec. 20, 1996

Dec. 20, 1996

>I was told recently that the town (district probably) of >Kunumurra, in far north east Western Australia has switched its >time zone to be the same as that of the Northern Territory >instead of using WA time (they're just over the border, and the >WA time zone is wildly inappropriate, so it makes sense). To say that the WA time, 08:00 ahead of UT, in Kununurra (I presume that is where is meant: there were no matches for Kunumurra on an AltaVista Web search but about 200 for Kununurra [and 9 and 7 for Kunnunurra and Kununnurra respectively]) is wildly inappropriate is more than an overstatement. The WA-NT border runs along the 129 deg. E meridian, so WA time in Kunnunurra is less than 36 minutes behind LMT. Is that particularly inappropriate? If Kununurra adopts / has adopted NT time, 09:30 ahead of UT, then its time will be / is more than 54 minutes ahead of LMT. Isn't that even more "inappropriate"? It is Australia's "Central Time" (09:30 ahead of UT) that is inappropriate. The closest it comes to being "appropriate" is on SA's eastern border with NSW, where it is still 6 minutes ahead of LMT. IMHO Australia's time zoning is a farce. Australia is wholly responsible for 3 of world's "off the hour" time zones (central zone, Lord Howe Island and Norfolk Island) and partially responsible for another 1 (Cocos Islands - same time as Burma). The least justifiable of these is "Central Time", and Lord Howe Island comes a close second, what with its almost entirely pointless daylight-saving practices. (I started a message about the latter several weeks ago but haven't got round to finishing it yet.) There seems to me to be two main options for the central zone: 1: Put the whole zone on UT+10 year-round (no more inappropriate than Argentina, not to mention China), with the possible exception of the southwest corner of SA (where hardly anyone lives), which could keep on UT+9 (whether "officially" or otherwise) along with the southeast corner of WA (where even fewer people live) which already keeps UT+8:45 year-round (ugh!). 2: Put the whole zone on UT+9 during a standardised non-daylight-saving period, advancing the southern section to UT+10 during a standardised daylight-saving period. In either case, a section of northeast WA could consider adopting UT+9 year-round. What chance of this? _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9313-7279 Telephone: +61 2 9931-9264

1 0

Probable change needed to the Aust zone files
by Robert Elz Dec. 18, 1996

Dec. 18, 1996

This is pretty minor, and may not be worth bothering with, but we do try to cover everything, so ... I was told recently that the town (district probably) of Kunumurra, in far north east Western Australia has switched its time zone to be the same as that of the Northern Territory instead of using WA time (they're just over the border, and the WA time zone is wildly inappropriate, so it makes sense). I hope to check this if I can find someone to check it with, and see if I can discover when it happened exactly. I wouldn't be in any great hurry to get this fixed, this is going to be one small town, and I would doubt very much that anyone there is running the tz code in any form... kre

1 0

proposed tz patches for post-1991 Iran, 1930s Soviet week, spelling
by Paul Eggert Dec. 18, 1996

Dec. 18, 1996

Rich Wales suggested that Iran's daylight-saving rules correspond to the Persian calendar and I found another expert source who agrees. This clarifies the daylight saving rules for Iran (and points out what appear to be minor errors in the IATA SSIM). Here's a patch embodying his suggestion, along with a better explanation of the Soviet week from 1929 through 1940 thanks to Chris Carrier, and some miscellaneous spelling fixes (including one fix to a message in `zic'). =================================================================== RCS file: RCS/zic.c,v retrieving revision 1996.14 retrieving revision 1996.14.1.1 diff -c -r1996.14 -r1996.14.1.1 *** zic.c 1996/12/16 14:42:02 1996.14 --- zic.c 1996/12/18 06:42:29 1996.14.1.1 *************** *** 1697,1703 **** (void) strcpy(startbuf, zp->z_format); eat(zp->z_filename, zp->z_linenum); if (*startbuf == '\0') ! error(_("can't determine time zone abbrevation to use just after until time")); else addtt(starttime, addtype(startoff, startbuf, startoff != zp->z_gmtoff, --- 1697,1703 ---- (void) strcpy(startbuf, zp->z_format); eat(zp->z_filename, zp->z_linenum); if (*startbuf == '\0') ! error(_("can't determine time zone abbreviation to use just after until time")); else addtt(starttime, addtype(startoff, startbuf, startoff != zp->z_gmtoff, =================================================================== RCS file: RCS/asia,v retrieving revision 1996.13 retrieving revision 1996.13.1.1 diff -c -r1996.13 -r1996.13.1.1 *** asia 1996/11/24 01:07:37 1996.13 --- asia 1996/12/18 06:42:29 1996.13.1.1 *************** *** 354,359 **** --- 354,379 ---- 9:00 - JAYT # Iran + # From Paul Eggert (1996-12-17), following up a suggestion by Rich Wales: + # Ahmad Alavi <URL:http://tehran.stanford.edu/Iran_Lib/Calendar/taghveem.txt> + # (1993-08-04) writes ``Daylight saving time in Iran starts from the first day + # of Farvardin and ends the first day of Mehr.'' This disagrees with the SSIM: + # + # DST start DST end + # year SSIM Alavi SSIM Alavi + # 1991 05-03!= 03-21 09-20!= 09-23 + # 1992 03-22!= 03-21 09-23 09-23 + # 1993 03-21 03-21 09-23 09-23 + # 1994 03-21 03-21 09-22!= 09-23 + # 1995 03-21 03-21 09-22!= 09-23 + # 1996 03-21!= 03-20 09-21!= 09-22 + # 1997 03-21 03-21 09-21!= 09-23 + # + # Go with Alavi starting with 1992. + # I used Ed Reingold's cal-persia in GNU Emacs 19.34 to compute Persian dates. + # The Persian calendar is based on the sun, and dates after around 2050 + # are approximate; stop after 2037 when 32-bit time_t's overflow. + # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Iran 1978 1980 - Mar 21 0:00 1:00 S Rule Iran 1978 only - Oct 21 0:00 0 - *************** *** 361,371 **** Rule Iran 1980 only - Sep 23 0:00 0 - Rule Iran 1991 only - May 3 0:00s 1:00 S Rule Iran 1991 only - Sep 20 0:00s 0 - ! Rule Iran 1992 only - Mar 22 0:00 1:00 S ! Rule Iran 1992 1993 - Sep 23 0:00 0 - ! Rule Iran 1993 max - Mar 21 0:00 1:00 S ! Rule Iran 1994 1995 - Sep 22 0:00 0 - ! Rule Iran 1996 max - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 3:25:44 - TMT 1946 # Tehran Mean Time --- 381,430 ---- Rule Iran 1980 only - Sep 23 0:00 0 - Rule Iran 1991 only - May 3 0:00s 1:00 S Rule Iran 1991 only - Sep 20 0:00s 0 - ! Rule Iran 1992 1995 - Mar 21 0:00 1:00 S ! Rule Iran 1992 1995 - Sep 23 0:00 0 - ! Rule Iran 1996 only - Mar 20 0:00 1:00 S ! Rule Iran 1996 only - Sep 22 0:00 0 - ! Rule Iran 1997 1999 - Mar 21 0:00 1:00 S ! Rule Iran 1997 1999 - Sep 23 0:00 0 - ! Rule Iran 2000 only - Mar 20 0:00 1:00 S ! Rule Iran 2000 only - Sep 22 0:00 0 - ! Rule Iran 2001 2003 - Mar 21 0:00 1:00 S ! Rule Iran 2001 2003 - Sep 23 0:00 0 - ! Rule Iran 2004 only - Mar 20 0:00 1:00 S ! Rule Iran 2004 only - Sep 22 0:00 0 - ! Rule Iran 2005 2007 - Mar 21 0:00 1:00 S ! Rule Iran 2005 2007 - Sep 23 0:00 0 - ! Rule Iran 2008 only - Mar 20 0:00 1:00 S ! Rule Iran 2008 only - Sep 22 0:00 0 - ! Rule Iran 2009 2011 - Mar 21 0:00 1:00 S ! Rule Iran 2009 2011 - Sep 23 0:00 0 - ! Rule Iran 2012 only - Mar 20 0:00 1:00 S ! Rule Iran 2012 only - Sep 22 0:00 0 - ! Rule Iran 2013 2015 - Mar 21 0:00 1:00 S ! Rule Iran 2013 2015 - Sep 23 0:00 0 - ! Rule Iran 2016 only - Mar 20 0:00 1:00 S ! Rule Iran 2016 only - Sep 22 0:00 0 - ! Rule Iran 2017 2019 - Mar 21 0:00 1:00 S ! Rule Iran 2017 2019 - Sep 23 0:00 0 - ! Rule Iran 2020 only - Mar 20 0:00 1:00 S ! Rule Iran 2020 only - Sep 22 0:00 0 - ! Rule Iran 2021 2023 - Mar 21 0:00 1:00 S ! Rule Iran 2021 2023 - Sep 23 0:00 0 - ! Rule Iran 2024 2025 - Mar 20 0:00 1:00 S ! Rule Iran 2024 2025 - Sep 22 0:00 0 - ! Rule Iran 2026 2027 - Mar 21 0:00 1:00 S ! Rule Iran 2026 2027 - Sep 23 0:00 0 - ! Rule Iran 2028 2029 - Mar 20 0:00 1:00 S ! Rule Iran 2028 2029 - Sep 22 0:00 0 - ! Rule Iran 2030 2031 - Mar 21 0:00 1:00 S ! Rule Iran 2030 2031 - Sep 23 0:00 0 - ! Rule Iran 2032 2033 - Mar 20 0:00 1:00 S ! Rule Iran 2032 2033 - Sep 22 0:00 0 - ! Rule Iran 2034 2035 - Mar 21 0:00 1:00 S ! Rule Iran 2034 2035 - Sep 23 0:00 0 - ! Rule Iran 2036 2037 - Mar 20 0:00 1:00 S ! Rule Iran 2036 2037 - Sep 22 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 3:25:44 - TMT 1946 # Tehran Mean Time *************** *** 492,498 **** # # ftp://ftp.huji.ac.il/pub/misc/timezones/announcements/1996-1998.ps.gz # ! # Emptor Caveat: The dates for the years 1996-1998 were originally announced # on 1995-08-31, by the previous Minister of Interior. The new Minister # of Interior changed the dates on 1996-01-01, to take into account the # desires of certain portions of Israeli society (the next election is in the --- 551,557 ---- # # ftp://ftp.huji.ac.il/pub/misc/timezones/announcements/1996-1998.ps.gz # ! # Caveat emptor: The dates for the years 1996-1998 were originally announced # on 1995-08-31, by the previous Minister of Interior. The new Minister # of Interior changed the dates on 1996-01-01, to take into account the # desires of certain portions of Israeli society (the next election is in the =================================================================== RCS file: RCS/australasia,v retrieving revision 1996.13 retrieving revision 1996.13.1.2 diff -c -r1996.13 -r1996.13.1.2 *** australasia 1996/11/24 01:07:37 1996.13 --- australasia 1996/12/18 06:59:16 1996.13.1.2 *************** *** 48,62 **** # so use Lindeman. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule QL 1989 1991 - Oct lastSun 2:00s 1:00 - ! Rule QL 1990 1992 - Mar Sun>=1 2:00s 0 - Rule Holiday 1989 1993 - Oct lastSun 2:00s 1:00 - Rule Holiday 1990 1994 - Mar Sun>=1 2:00s 0 - Zone Australia/Brisbane 10:12:08 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s 10:00 1:00 EST 1972 Feb lastSun 2:00s ! 10:00 QL EST Zone Australia/Lindeman 9:55:56 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s --- 48,62 ---- # so use Lindeman. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule AQ 1989 1991 - Oct lastSun 2:00s 1:00 - ! Rule AQ 1990 1992 - Mar Sun>=1 2:00s 0 - Rule Holiday 1989 1993 - Oct lastSun 2:00s 1:00 - Rule Holiday 1990 1994 - Mar Sun>=1 2:00s 0 - Zone Australia/Brisbane 10:12:08 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s 10:00 1:00 EST 1972 Feb lastSun 2:00s ! 10:00 AQ EST Zone Australia/Lindeman 9:55:56 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s *************** *** 339,345 **** 9:00 - PWT # Palau Time # Palmyra ! # uninhabited since World War II; was probably like Pacific/Kiritmati # Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 339,345 ---- 9:00 - PWT # Palau Time # Palmyra ! # uninhabited since World War II; was probably like Pacific/Kiritimati # Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/europe,v retrieving revision 1996.13 retrieving revision 1996.13.1.1 diff -c -r1996.13 -r1996.13.1.1 *** europe 1996/11/24 01:07:37 1996.13 --- europe 1996/12/18 06:42:29 1996.13.1.1 *************** *** 78,84 **** # of the text said: # # `An old stone obelisk marking a forgotten terrestrial meridian stands ! # beside the river at Kew. In the 18th century, before time and longditude # was standardised by the Royal Observatory in Greenwich, scholars observed # this stone and the movement of stars from Kew Observatory nearby. They # made their calculations and set the time for the Horse Guards and Parliament, --- 78,84 ---- # of the text said: # # `An old stone obelisk marking a forgotten terrestrial meridian stands ! # beside the river at Kew. In the 18th century, before time and longitude # was standardised by the Royal Observatory in Greenwich, scholars observed # this stone and the movement of stars from Kew Observatory nearby. They # made their calculations and set the time for the Horse Guards and Parliament, *************** *** 86,92 **** # along the towpath within a few yards of it.' # # I have a one inch to one mile map of London and my estimate of the stone's ! # position is 51 deg. 28' 30" N, 0 deg. 18' 45" W. The longditude should # be within about +-2". The Ordnance Survey grid reference is TQ172761. # # [This yields GMTOFF = -0:01:15 for London LMT in the 18th century.] --- 86,92 ---- # along the towpath within a few yards of it.' # # I have a one inch to one mile map of London and my estimate of the stone's ! # position is 51 deg. 28' 30" N, 0 deg. 18' 45" W. The longitude should # be within about +-2". The Ordnance Survey grid reference is TQ172761. # # [This yields GMTOFF = -0:01:15 for London LMT in the 18th century.] *************** *** 167,173 **** # It ends at 02:00 GMT on the morning of the day after the fourth Saturday # in October. (All the redundant `morning of the day ...' is in the Act.) # This is only of passing interest now as it will always be overridden by ! # an Order in Council (a Statutary Instrument, the SI thing mentioned above) # to specify the EC specified dates. # From Peter Ilieve <peter(a)memex.co.uk> (1993-10-18): --- 167,173 ---- # It ends at 02:00 GMT on the morning of the day after the fourth Saturday # in October. (All the redundant `morning of the day ...' is in the Act.) # This is only of passing interest now as it will always be overridden by ! # an Order in Council (a Statutory Instrument, the SI thing mentioned above) # to specify the EC specified dates. # From Peter Ilieve <peter(a)memex.co.uk> (1993-10-18): *************** *** 327,333 **** # so that part of the 1922 Act will still apply. # # - The Defence (Summer Time) Regulations, 1939, SR&O 1939 No. 1379 ! # [SR&O == Statutary Regulation and Order] # # These were made under the Emergency Powers (Defence) Act, 1939. # It changes the end date to be the day after the third Saturday in November. --- 327,333 ---- # so that part of the 1922 Act will still apply. # # - The Defence (Summer Time) Regulations, 1939, SR&O 1939 No. 1379 ! # [SR&O == Statutory Regulation and Order] # # These were made under the Emergency Powers (Defence) Act, 1939. # It changes the end date to be the day after the third Saturday in November. *************** *** 403,409 **** # harmonise with the EC since 1981. The major change is that the time changes # to 01:00 GMT.) # ! # - The Summer Time Order, 1992, SI 1992/1729 [SI == Statutary Instrument] # # This specifies dates of: # Start End --- 403,409 ---- # harmonise with the EC since 1981. The major change is that the time changes # to 01:00 GMT.) # ! # - The Summer Time Order, 1992, SI 1992/1729 [SI == Statutory Instrument] # # This specifies dates of: # Start End *************** *** 1298,1304 **** 1:00 Greece CE%sT 1944 Apr 4 2:00 Greece EE%sT 1981 # Shanks says they switched to C-Eur in 1981; ! # go with EU intead, since Greece joined it on Jan 1. 2:00 EU EE%sT # Hungary --- 1298,1304 ---- 1:00 Greece CE%sT 1944 Apr 4 2:00 Greece EE%sT 1981 # Shanks says they switched to C-Eur in 1981; ! # go with EU instead, since Greece joined it on Jan 1. 2:00 EU EE%sT # Hungary *************** *** 1819,1827 **** 2:00 E-Eur EE%sT # Russia ! # From Shanks (1991): ! # In 1929 the Soviet Union instituted a 5 day week; in 1932 it instituted ! # a 6 day week; on 1940-06-27 it returned to the Gregorian week. # # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # Except for Moscow after 1919-07-01, I invented the time zone abbreviations, --- 1819,1833 ---- 2:00 E-Eur EE%sT # Russia ! ! # From Chris Carrier <72157.3334(a)CompuServe.COM> (1996-12-02): ! # On 1929-10-01 the Soviet Union instituted an ``Eternal Calendar'' ! # with 30-day months plus 5 holidays, with a 5-day week. ! # On 1931-12-01 it changed to a 6-day week; in 1934 it reverted to the ! # Gregorian calendar while retaining the 6-day week; on 1940-06-27 it ! # reverted to the 7-day week. With the 6-day week the usual days ! # off were the 6th, 12th, 18th, 24th and 30th of the month. ! # (Source: Evitiar Zerubavel, _The Seven Day Circle_) # # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # Except for Moscow after 1919-07-01, I invented the time zone abbreviations, *************** *** 1882,1888 **** # as far as I remember it was done exactly during winter->summer switching # so we (Novosibirsk) simply did not switch. Zone Asia/Novosibirsk 5:31:40 - LMT 1924 May 2 ! 6:00 - NOVT 1957 Mar # Novosibirsk TIme 7:00 Russia NOV%sT 1991 Mar 31 2:00s 6:00 1:00 NOVST 1991 Sep 29 2:00s 6:00 - NOVT 1992 Jan 19 2:00s --- 1888,1894 ---- # as far as I remember it was done exactly during winter->summer switching # so we (Novosibirsk) simply did not switch. Zone Asia/Novosibirsk 5:31:40 - LMT 1924 May 2 ! 6:00 - NOVT 1957 Mar # Novosibirsk Time 7:00 Russia NOV%sT 1991 Mar 31 2:00s 6:00 1:00 NOVST 1991 Sep 29 2:00s 6:00 - NOVT 1992 Jan 19 2:00s *************** *** 2134,2140 **** # Ukraine # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Ukraine 1917 only - Jul 1 23:00 1:00 UST # Ukrainian Summer Time ! Rule Ukraine 1917 only - Dec 28 0:00 0 KMT # Kiev Mean TIme Rule Ukraine 1918 only - May 31 22:00 2:00 UDST # Ukrainian Double Summer Time Rule Ukraine 1918 only - Sep 17 0:00 1:00 UST Rule Ukraine 1919 only - May 31 23:00 2:00 UDST --- 2140,2146 ---- # Ukraine # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Ukraine 1917 only - Jul 1 23:00 1:00 UST # Ukrainian Summer Time ! Rule Ukraine 1917 only - Dec 28 0:00 0 KMT # Kiev Mean Time Rule Ukraine 1918 only - May 31 22:00 2:00 UDST # Ukrainian Double Summer Time Rule Ukraine 1918 only - Sep 17 0:00 1:00 UST Rule Ukraine 1919 only - May 31 23:00 2:00 UDST =================================================================== RCS file: RCS/northamerica,v retrieving revision 1996.13 retrieving revision 1996.13.1.1 diff -c -r1996.13 -r1996.13.1.1 *** northamerica 1996/11/24 01:07:37 1996.13 --- northamerica 1996/12/18 06:42:29 1996.13.1.1 *************** *** 920,928 **** # MEXICO BAJA CAL N 7 H BEHIND UTC BAJA CALIFORNIA SUR AND # MEXICO BAJA CAL N N. PACIFIC COAST (STATES # MEXICO BAJA CAL N OF SINALOA AND SONORA) ! # MEXICO BAJA CAL N 8 H BEHIND UTC ABOVE 28TH PARALLAL APR 3 # MEXICO BAJA CAL N - OCT 29 ! # MEXICO BAJA CAL N 7 H BEHIND UTC ABOVE 28TH PARALLAL APR 3 # MEXICO BAJA CAL N - 0CT 29 # MEXICO 6 H BEHIND UTC STATES OF DURANGO, # MEXICO COAHUILA, NUEVO LEON, --- 920,928 ---- # MEXICO BAJA CAL N 7 H BEHIND UTC BAJA CALIFORNIA SUR AND # MEXICO BAJA CAL N N. PACIFIC COAST (STATES # MEXICO BAJA CAL N OF SINALOA AND SONORA) ! # MEXICO BAJA CAL N 8 H BEHIND UTC ABOVE 28TH PARALLEL APR 3 # MEXICO BAJA CAL N - OCT 29 ! # MEXICO BAJA CAL N 7 H BEHIND UTC ABOVE 28TH PARALLEL APR 3 # MEXICO BAJA CAL N - 0CT 29 # MEXICO 6 H BEHIND UTC STATES OF DURANGO, # MEXICO COAHUILA, NUEVO LEON, =================================================================== RCS file: RCS/southamerica,v retrieving revision 1996.13 retrieving revision 1996.13.1.1 diff -c -r1996.13 -r1996.13.1.1 *** southamerica 1996/11/24 01:07:37 1996.13 --- southamerica 1996/12/18 06:42:29 1996.13.1.1 *************** *** 61,67 **** # ARGENTINA 3 H BEHIND UTC # From Hernan G. Otero <hernan(a)isoft.com.ar> (1995-06-26): ! # I am sending modifications to the Argentinian time zone table... # AR was chosen because they are the ISO letters that represent Argentina. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 61,67 ---- # ARGENTINA 3 H BEHIND UTC # From Hernan G. Otero <hernan(a)isoft.com.ar> (1995-06-26): ! # I am sending modifications to the Argentine time zone table... # AR was chosen because they are the ISO letters that represent Argentina. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S *************** *** 99,105 **** # These corrections were contributed by InterSoft Argentina S.A., # obtaining the data from the: # Talleres de Hidrografia Naval Argentina ! # (Argentinian Naval Hydrography Institute) # # Shanks gives 1989 Mar 16 and stops after 1990 Mar 4; go with Otero. Rule Arg 1989 1993 - Mar Sun>=1 0:00 0 - --- 99,105 ---- # These corrections were contributed by InterSoft Argentina S.A., # obtaining the data from the: # Talleres de Hidrografia Naval Argentina ! # (Argentine Naval Hydrography Institute) # # Shanks gives 1989 Mar 16 and stops after 1990 Mar 4; go with Otero. Rule Arg 1989 1993 - Mar Sun>=1 0:00 0 -

1 0

tzcode1996n.tar.gz
by ado Dec. 16, 1996

Dec. 16, 1996

The file ftp://elsie.nci.nih.gov/pub/tzcode1996n.tar.gz is now available; it incorporates the link snapping fix from Bruce Evans (via Garrett Wollman). --ado

1 0

[Bruce Evans: fix for zic following obsolete links]
by Garrett Wollman Dec. 13, 1996

Dec. 13, 1996

Patch from a FreeBSD contributor... -GAWollman ------- start of forwarded message (RFC 934 encapsulation) ------- Message-Id: <199612131138.WAA30698(a)godzilla.zeta.org.au> From: Bruce Evans <bde(a)zeta.org.au> To: wollman(a)freebsd.org Subject: fix for zic following obsolete links Date: Fri, 13 Dec 1996 22:38:49 +1100 zic made a mess of my /usr/share/zoneinfo by not snapping obsolete links (mostly in America/Indiana and Etc). Bruce diff -c2 src/usr.sbin/zic/zic.c~ src/usr.sbin/zic/zic.c *** src/usr.sbin/zic/zic.c~ Fri Jul 19 10:27:13 1996 - --- src/usr.sbin/zic/zic.c Thu Dec 12 21:22:16 1996 *************** *** 1424,1427 **** - --- 1424,1438 ---- (int) (strlen(directory) + 1 + strlen(name) + 1)); (void) sprintf(fullname, "%s/%s", directory, name); + + /* + * Remove old file, if any, to snap links. + */ + if (!itsdir(fullname) && remove(fullname) != 0 && errno != ENOENT) { + const char *e = strerror(errno); + (void) fprintf(stderr, _("%s: Can't remove %s: %s\n"), + progname, fullname, e); + (void) exit(EXIT_FAILURE); + } + if ((fp = fopen(fullname, "wb")) == NULL) { if (mkdirs(fullname) != 0) ------- end -------

1 0

RE: Russian data
by PYMCCART＠ECUVAX.CIS.ECU.EDU Dec. 3, 1996

Dec. 3, 1996

The Eastern Orthodox Churches are evidently individuated by states/nations, being most prominent in eastern Europe and Russia. The autonomy of statehood seems reflected also in some of the practices of state churches, the calendar being a rather divisive issue among them. A schism between Old and New Calendarists developed in this century, when in 1923 several state churches approximated the Gregorian Reform of 1582. The Russian and Greek churches were among those represented at an ecumenical council in which the reform proposal was approved. Technically, they did not fall into step with the Greogrian calendar, even though they skipped the requisite number of days to agree with it. They additionally adopted the new leap-year rule Chris Carrier has mentioned: Leap year every four years except years which leave remainders of 200 or 600 when divided by 900. (http://ecuvax.cis.ecu.edu/~pymccart/orthodox-reform.html) Not all state churches agreed to the reform, and some churches split internally over it. I have read that a subsequent compromise has been attempted, whereby the New Calendarists have readopted the Julian calendar for fixing moveable feasts related to Easter (the principal issue of contention), but observe other feasts, like Christmas, in agreement with the Gregorian calendar. As for the Orthodox church of Finnland, I have seen it mentioned in a few places as a lone exception, having adopted the Gregorian dates for all feasts. The explanation given is usually that the Christian population of Finnland is overwhelmingly Western in orientation, so the Orthodox in Finnland prefer to fit in. As for the FORMULA for computing Orthodox Easter, it would be the same as the Western formula, since both Churches regard the Council of Nicaea in 325 AD as authoritative. But because of the differences in the Julian and Gregorian calendars, the date of the Vernal Equinox (March 21) differs by about two weeks. There's another difference, too: relating to when/WHERE the moon is full. (http://cssa.stanford.ecu/~marcos/ortheast.html) --Rick McCarty

1 0

Russian data
by Chris Carrier Dec. 3, 1996

Dec. 3, 1996

Paul Eggert wrote: Thanks. I edited your message down to the following: is it OK if I include this in a future revision of the `europe' file? # From Chris Carrier <72157.3334(a)CompuServe.COM> (1996-12-02): # On 1929-10-01 the Soviet Union instituted an ``Eternal Calendar'' # with 30-day months plus 5 holidays, with a 5-day week. # On 1931-12-01 it changed to a 6-day week; in 1934 it reverted to the # Gregorian calendar while retaining the 6-day week; on 1940-06-27 it # reverted to the 7-day week. With the 6-day week the usual days # off were the 6th, 12th, 18th, 24th and 30th of the month. # (Source: Evitiar Zerubavel, _The Seven Day Circle_) This is OK; I didn't know how much material to include, because the topic of discussion of the list is the clock, not the calendar, but Gregorian and the 5 and 6 day week experimental calendars were mentioned so I thought I should refine the data. I think the reason that the Russian Orthodox adhere to the Julian calendar, even today, is because Easter is getting steadily later under it. Easter is, after all, a spring festival, and late March in most of Russia is still snowy and very cold. By placing Easter in the date range April 4 - May 8 instead of March 22 - April 25 it's more springlike. Chris Carrier

2 1

Russian calendar data
by Chris Carrier Dec. 2, 1996

Dec. 2, 1996

Some Russian information of interest to the list, and a question. We have Russia adopting a five-day calendar week in 1929 and a six-day week in 1932. The exact date for the adoption of the five day week was 1929-10-01 and for the six day week, 1931-12-01, not 1932. The 1940-06-27 date for the re- adoption of the seven day week is accurate; however they re-adopted their version of the Gregorian Calendar several years earlier (slightly different from ours in how it handles leap centuries; in the Gregorian, leap centuries are in those years divisible by 400; in their system, leap centuries are those in years divisible by either 200 or 600 mod 900, which makes the two calendars even until 2800- 02-28, when we have a leap year and they do not). The six day week was not always six days, but an integral part of the month; the usual days off were the 6th, 12th, 18th, 24th and 30th of the month. (Source: Evitiar Zerubavel, THE SEVEN DAY CIRCLE, a book about the history of the week.) Question: we have Greece on the Gregorian Calendar in 1846. I thought they were the last holdout, not adopting the Gregorian Calendar until 1923, which is when the Eastern Orthodox Churches got together and adopted the mod-900 version of the Gregorian Calendar described above. (The transition was made by making the day after 1923-09-30 Julian 1923-10-14 Gregorian.) Chris Carrier

1 0

Timezone naming
by J Wunsch Nov. 27, 1996

Nov. 27, 1996

You'll say ``Argh!'' now, i know. After a long and heated discussion in the FreeBSD core team, we came to the conclusion that changing the timezone name for Central Europe from MET to CET is a very bad move. The reasoning: the name MET is in widespread use here on almost all Unix systems around. (With AIX being the most noteworthy and most funny exception; they call it ``Norway-France-Time'', NFT. :) However technically correct your choice for CET might be, it breaks tradition, and is in general something people here will consider a ``US-centric'' decision. MET might sound like a half-translated term in German, but people can easily memorize it, and identify their own timezone by this name. Other languages like Danish even use this term as well as their local abbreviation (which is no surprise given that Danish is closer to English than German is). You'll note that we don't mind you US inhabitants naming the New York timezone ``EST'' either, even though the term ``Western Atlantic Timezone'' is far more correct from our point of view, since you are west of us, not east as the name suggests. Needless to say, i'd leave the decision for this name at the people that have to live with the name. But i expect you doing likewise: respect our wish to keep the name `MET' for the Central/Middle European Time. Changing it will gain nothing, but cause support hassles for our userbase. Btw., there's at least one alternate (but not less bogus) translation for this abbreviation: Mediterranean Time. I'm also sending this request on behalf of Poul-Henning Kamp, another FreeBSD core team member. Cc to him for this. -- cheers, J"org joerg_wunsch(a)uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)

5 13

Re: Timezone naming
by Dik.Winter＠cwi.nl Nov. 26, 1996

Nov. 26, 1996

> - I hardly ever have seen MET and METDST used anywhere outside the Unix > world and we can very well assume that MET is today only known because it > somehow found its way into the Olson database some time ago. DST is an > abbreviation exclusively used in the U.S., most other countries > say "summer time". Some historical information from my online archives. The tz database as posted in mod.sources in March 1986 indeed had MET and did not mention CET. Also the variant posted in February 1987 had that. CET crept into the database in March 1987 when it was posted in comp.bug.4-bsd.fixes by Keith Bostic as an official BSD supplement. That version had the remark: # Tom Hoffman says that MET is also known as Central European Time Link MET CET Apparently non-native-English speakers were pretty satisfied with MET for quite a long time (oh, well, at least some 10 years). dik -- dik t. winter, cwi, kruislaan 413, 1098 sj amsterdam, nederland, +31205924131 home: bovenover 215, 1025 jn amsterdam, nederland; http://www.cwi.nl/~dik/

1 0

Two `zones' for Germany?
by Garrett Wollman Nov. 26, 1996

Nov. 26, 1996

A FreeBSD contributor avers that the then-DDR began observing summer time a year [earlier|later] than the BRD, and further claims that the correct BRD start date should be 1979, not 1980 (and this the DDR would be [1978|1980]). (I have since deleted the message so I don't recall which direction the difference was.) According to the existing practice, then, there should be a different rule for locations which were in the DDR. I have no notion of which would be the most populous city in this case, but perhaps <joerg(a)freebsd.org> can provide more detailed information. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman(a)lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick

2 1

ftp://elsie.nci.nih.gov/pub/tzdata1996m.tar.gz
by ado Nov. 24, 1996

Nov. 24, 1996

Paul Eggert's batch of changes are incorporated in ftp://elsie.nci.nih.gov/pub/tzdata1996m.tar.gz --ado

1 0

proposed tz changes for Argentina, Brazil, Russia, etc.
by Paul Eggert Nov. 22, 1996

Nov. 22, 1996

Here is a big batch of proposed changes to the tz database. Most of the changes here were suggested by data taken from the International Air Transport Association's Standard Schedules Information Manual (IATA SSIM), published semiannually. Gwillim Law sent in several very helpful summaries of the IATA's data after 1990, and he deserves a big round of applause for his contributions. All changes below are from the IATA SSIM data unless otherwise noted. * New entries: ** America/Goose_Bay, needed because east Labrador also observed double-DST in 1988 (from Shanks; I misread one of his tables). ** for Argentina, which was in time zone chaos in the early 1990s: America/Catamarca America/Cordoba America/Jujuy America/Mendoza America/Rosario ** for Brazil, since the equatorial part of Brazil does not observe DST and the boundaries have moved recently: America/Cuiaba America/Fortaleza America/Maceio ** Antarctica/Palmer, which used Argentine rules before the Falklands war, Chilean afterwards (from Ethan Dicks) ** Asia/Aqtobe, for central Kazakhstan (which now has 3 time zones). ** Australia/Lindeman, for the Holiday Islands off Queensland, which observed DST for a couple of years after Queensland stopped. ** Europe/Kaliningrad, for Russia's new time zone (as if they didn't have enough time zones already!). * Renamed entries (from yours truly) Asia/Aktau -> Asia/Aqtau (the more usual Kazakh-English transliteration) Europe/Kuybyshev -> Europe/Samara (the city changed names in 1991) * Make the following changes relevant to today's timestamps: ** Data (as opposed to sheer guesswork) are now available for the following countries after 1990: Brazil Cuba Falklands Jordan Lebanon Paraguay Syria ** Albania now uses EU DST rules. ** Azerbaijan is now at +4 with EU rules. It switched to +4 in 1992 but first observed DST this year. ** Belarus now uses Russian DST rules. ** Bulgaria uses E-Eur DST rules, not C-Eur. ** Egypt has changed rules a couple of times in the 1990s; it currently seems to use DST from Apr lastFri 0:00 to Sep lastFri 0:00. ** Georgia is now +5 (from Mathew Englander, quoting AP 1996-10-23 13:05-04). In 1992 it switched to E-Eur rules; in 1994 it switched to +4. ** Greenland uses EU DST rules, except Thule, which adopted USA DST rules in 1993. ** Guyana is at -4; assume a 1991 switch. ** Haiti changes its clocks at 1:00s, not 2:00. ** Iran reinstituted DST since 1991, and currently seems to switch near the equinoxes. ** Iraq changed rules in 1991 to Apr 1 and Oct 1. ** Jamaica stopped observing DST in 1984. ** Kazakhstan uses E-Eur DST rules, not Russian DST rules. ** Kirgizstan uses its own rules since 1991. ** Latvia switched in Sep, not Oct, this year (from Peter Ilieve). ** Libya reinstituted DST this year. ** Mongolia follows Russia since 1991, except it switches at 0:00 local time. ** Namibia adopted DST in 1994. ** New Zealand's Chatham Islands are always 45 minutes ahead of New Zealand, even during DST changes. ** Nicaragua is now at -5. ** Portugal's Azores now use EU DST rules, after dallying with +0 in 1992/1993. ** Romania now uses E-Eur DST rules, after using their own special case in 1991/1994. ** Russians prefer the abbreviations MSK/MSD to MOST/MOSST (from Andrey A. Chernov). ** Tunisia abolished DST in 1991. ** Turkey now uses EU DST rules. ** Turks & Caicos switch at 0:00, not at 2:00. ** Ukraine now uses EU DST rules, except for central Crimea, which changes at 0:00u. ** Vanuatu abolished DST in 1993. ** Etc/UTC, Etc/Universal, and Etc/Zulu now use the abbreviation `UTC' instead of `GMT' (from Markus Kuhn); similarly, Etc/UCT now uses `UCT'. * Make the following changes for older timestamps: ** Newfoundland's UTC offset adjusted by 8 seconds from 1884 to 1935 (from a better reading of Shanks). ** Yukon's time of switch on 1973-10-20 was 0:00, not 2:00 (from Mathew Englander). ** Colombia, Costa Rica and Nicaragua observed DST in 1992. ** Guatemala observed DST in 1991. ** Peru observed DST in 1993. ** Portugal's 1983-1992 rules were W-Eur, not EU. ** Russia's 1992 rules were to switch at 23:00 local time, not 2:00 standard time. ** Uruguay observed DST through 1992/1993. =================================================================== RCS file: RCS/africa,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** africa 1996/11/05 18:50:12 1996.12 --- africa 1996/11/22 19:39:06 1996.12.1.1 *************** *** 4,15 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # Except where otherwise noted, it is the source for the data below. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which --- 4,23 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # ! # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source ! # for recent time zone data is the International Air Transport ! # Association's Standard Schedules Information Manual (IATA SSIM), ! # published semiannually. Law sent in several helpful summaries ! # of the IATA's data after 1990. ! # ! # Except where otherwise noted, Shanks is the source for entries through 1990, ! # and IATA SSIM is the source for entries after 1990. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which *************** *** 255,266 **** Rule Egypt 1958 only - May 1 0:00 1:00 S Rule Egypt 1959 1981 - May 1 1:00 1:00 S Rule Egypt 1959 1965 - Sep 30 3:00 0 - ! Rule Egypt 1966 max - Oct 1 3:00 0 - Rule Egypt 1982 only - Jul 25 1:00 1:00 S Rule Egypt 1983 only - Jul 12 1:00 1:00 S Rule Egypt 1984 1988 - May 1 1:00 1:00 S Rule Egypt 1989 only - May 6 1:00 1:00 S ! Rule Egypt 1990 max - May 1 1:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Cairo 2:05:00 - LMT 1900 Oct 2:00 Egypt EE%sT --- 263,279 ---- Rule Egypt 1958 only - May 1 0:00 1:00 S Rule Egypt 1959 1981 - May 1 1:00 1:00 S Rule Egypt 1959 1965 - Sep 30 3:00 0 - ! Rule Egypt 1966 1990 - Oct 1 3:00 0 - Rule Egypt 1982 only - Jul 25 1:00 1:00 S Rule Egypt 1983 only - Jul 12 1:00 1:00 S Rule Egypt 1984 1988 - May 1 1:00 1:00 S Rule Egypt 1989 only - May 6 1:00 1:00 S ! Rule Egypt 1990 only - May 1 1:00 1:00 S ! Rule Egypt 1991 1994 - May 1 0:00 1:00 S ! Rule Egypt 1991 1994 - Oct 1 0:00 0 - ! Rule Egypt 1995 max - Apr lastFri 0:00 1:00 S ! Rule Egypt 1995 max - Sep lastFri 0:00 0 - ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Cairo 2:05:00 - LMT 1900 Oct 2:00 Egypt EE%sT *************** *** 390,404 **** Rule Libya 1987 1989 - Apr 1 0:00 1:00 S Rule Libya 1987 1990 - Oct 1 0:00 0 - Rule Libya 1990 only - May 4 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 1:00 Libya CE%sT 1959 2:00 - EET 1982 - # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): - # usno1995 (from OAG) says Libya uses 2:00 all year, as they did before 1982. - # We don't know when they switched back. We'll guess 1991. 1:00 Libya CE%sT 1991 ! 2:00 - EET # Madagascar # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 403,417 ---- Rule Libya 1987 1989 - Apr 1 0:00 1:00 S Rule Libya 1987 1990 - Oct 1 0:00 0 - Rule Libya 1990 only - May 4 0:00 1:00 S + Rule Libya 1996 max - Mar 30 2:00s 1:00 S + Rule Libya 1996 max - Sep 30 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 1:00 Libya CE%sT 1959 2:00 - EET 1982 1:00 Libya CE%sT 1991 ! 2:00 - EET 1996 Mar 30 3:00 ! 1:00 Libya CE%sT # Madagascar # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 442,448 **** 3:00 - EAT # Morocco ! # rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Morocco 1939 only - Sep 12 0:00 1:00 S Rule Morocco 1939 only - Nov 19 0:00 0 - Rule Morocco 1940 only - Feb 25 0:00 1:00 S --- 455,461 ---- 3:00 - EAT # Morocco ! # RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Morocco 1939 only - Sep 12 0:00 1:00 S Rule Morocco 1939 only - Nov 19 0:00 0 - Rule Morocco 1940 only - Feb 25 0:00 1:00 S *************** *** 474,485 **** 2:00 - SAT # Namibia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 1:30 - SWAT 1903 Mar # SW Africa Time 2:00 - SAT 1942 Sep 20 2:00 2:00 1:00 SAST 1943 Mar 21 2:00 ! 2:00 - SAT # Niger # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 487,501 ---- 2:00 - SAT # Namibia + # RULE NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule Namibia 1994 max - Sep Sun>=1 2:00 1:00 S + Rule Namibia 1995 max - Apr Sun>=1 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 1:30 - SWAT 1903 Mar # SW Africa Time 2:00 - SAT 1942 Sep 20 2:00 2:00 1:00 SAST 1943 Mar 21 2:00 ! 2:00 Namibia SA%sT # Niger # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 618,627 **** Rule Tunisia 1978 only - May 1 0:00s 1:00 S Rule Tunisia 1978 only - Oct 1 0:00s 0 - Rule Tunisia 1988 only - Jun 1 0:00s 1:00 S ! Rule Tunisia 1988 max - Sep lastSun 0:00s 0 - Rule Tunisia 1989 only - Mar 26 0:00s 1:00 S Rule Tunisia 1990 only - May 1 0:00s 1:00 S - Rule Tunisia 1991 max - Mar lastSun 0:00s 1:00 S # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Shanks says the 1911 switch occurred on Mar 9; go with Howse's Mar 11. # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 634,642 ---- Rule Tunisia 1978 only - May 1 0:00s 1:00 S Rule Tunisia 1978 only - Oct 1 0:00s 0 - Rule Tunisia 1988 only - Jun 1 0:00s 1:00 S ! Rule Tunisia 1988 1990 - Sep lastSun 0:00s 0 - Rule Tunisia 1989 only - Mar 26 0:00s 1:00 S Rule Tunisia 1990 only - May 1 0:00s 1:00 S # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Shanks says the 1911 switch occurred on Mar 9; go with Howse's Mar 11. # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/antarctica,v retrieving revision 1996.11 retrieving revision 1996.11.1.1 diff -c -r1996.11 -r1996.11.1.1 *** antarctica 1996/09/08 20:06:16 1996.11 --- antarctica 1996/11/22 19:39:06 1996.11.1.1 *************** *** 8,13 **** --- 8,27 ---- # I made up all time zone abbreviations mentioned here; corrections welcome! # FORMAT is `___' and GMTOFF is 0 for locations while uninhabited. + # These rules are stolen from the `southamerica' file. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule ArgAQ 1964 1966 - Mar 1 0:00 0 - + Rule ArgAQ 1964 1966 - Oct 15 0:00 1:00 S + Rule ArgAQ 1967 only - Apr 1 0:00 0 - + Rule ArgAQ 1967 1968 - Oct Sun<=7 0:00 1:00 S + Rule ArgAQ 1968 1969 - Apr Sun<=7 0:00 0 - + Rule ArgAQ 1974 only - Jan 23 0:00 1:00 S + Rule ArgAQ 1974 only - May 1 0:00 0 - + Rule ArgAQ 1974 1976 - Oct Sun<=7 0:00 1:00 S + Rule ArgAQ 1975 1977 - Apr Sun<=7 0:00 0 - + Rule ChileAQ 1969 max - Oct Sun>=9 0:00 1:00 S + Rule ChileAQ 1970 max - Mar Sun>=9 0:00 0 - + # Argentina - 6 year-round bases # General Belgrano II *************** *** 118,124 **** # USA - year-round bases # ! # Palmer, Anvers Island # # McMurdo, Ross Island, since 1956 # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 132,152 ---- # USA - year-round bases # ! # Palmer, Anvers Island, since 1965 (moved 2 miles in 1968) ! # ! # From Ethan Dicks <erd(a)mcmsun5.mcmurdo.gov> (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. ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Antarctica/Palmer 0 - ___ 1965 ! -4:00 ArgAQ AR%sT 1969 Oct 5 ! -3:00 ArgAQ AR%sT 1982 May ! -4:00 ChileAQ CL%sT ! # # # McMurdo, Ross Island, since 1956 # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/asia,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** asia 1996/11/05 18:50:13 1996.12 --- asia 1996/11/22 19:39:06 1996.12.1.1 *************** *** 4,16 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1995-07-24): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). # Except where otherwise noted, it is the source for the data below. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which # I found in the UCLA library. --- 4,25 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). # Except where otherwise noted, it is the source for the data below. # + # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source + # for recent time zone data is the International Air Transport + # Association's Standard Schedules Information Manual (IATA SSIM), + # published semiannually. Law sent in several helpful summaries + # of the IATA's data after 1990. + # + # Except where otherwise noted, Shanks is the source for entries through 1990, + # and IATA SSIM is the source for entries after 1990. + # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which # I found in the UCLA library. *************** *** 24,30 **** # Corrections are welcome! # std dst # LMT Local Mean Time - # LST Local Star Time (Russian ``mestnoe zvezdnoe vremya'') # 2:00 EET EEST Eastern European Time # 2:00 IST IDT Israel # 3:00 AST ADT Arabia* --- 33,38 ---- *************** *** 48,59 **** ############################################################################### ! # These rules for Russia are stolen from the `europe' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule RussiaAsia 1981 1984 - Apr 1 0:00 1:00 S ! Rule RussiaAsia 1981 1983 - Oct 1 0:00 0 - ! Rule RussiaAsia 1984 max - Sep lastSun 2:00s 0 - ! Rule RussiaAsia 1985 max - Mar lastSun 2:00s 1:00 S # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 56,77 ---- ############################################################################### ! # These rules are stolen from the `europe' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule EUAsia 1981 max - Mar lastSun 1:00u 1:00 S ! Rule EUAsia 1996 max - Oct lastSun 1:00u 0 - ! Rule E-EurAsia 1981 max - Mar lastSun 0:00 1:00 S ! Rule E-EurAsia 1979 1995 - Sep lastSun 0:00 0 - ! Rule E-EurAsia 1996 max - Oct lastSun 0:00 0 - ! Rule RussiaAsia 1981 1984 - Apr 1 0:00 1:00 S ! Rule RussiaAsia 1981 1983 - Oct 1 0:00 0 - ! Rule RussiaAsia 1984 1991 - Sep lastSun 2:00s 0 - ! Rule RussiaAsia 1985 1991 - Mar lastSun 2:00s 1:00 S ! Rule RussiaAsia 1992 only - Mar lastSat 23:00 1:00 S ! Rule RussiaAsia 1992 only - Sep lastSat 23:00 0 - ! Rule RussiaAsia 1993 max - Mar lastSun 2:00s 1:00 S ! Rule RussiaAsia 1993 1995 - Sep lastSun 2:00s 0 - ! Rule RussiaAsia 1996 max - Oct lastSun 2:00s 0 - # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 85,94 **** 3:00 - BAKT 1957 Mar # Baku Time 4:00 RussiaAsia BAK%sT 1991 Mar 31 2:00s 3:00 1:00 BAKST 1991 Aug 30 # independence ! 3:00 RussiaAsia AZ%sT 1992 # Azerbaijan Time ! 3:00 - AZT ! # Shanks has Baku using Russian DST rules after 1991, ! # but usno1995 has Azerbaijan with no DST. Guess no DST after 1991. # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 103,111 ---- 3:00 - BAKT 1957 Mar # Baku Time 4:00 RussiaAsia BAK%sT 1991 Mar 31 2:00s 3:00 1:00 BAKST 1991 Aug 30 # independence ! 3:00 RussiaAsia AZ%sT 1992 Sep lastSun 2:00s ! 4:00 - AZT 1996 # Azerbaijan time ! 4:00 EUAsia AZ%sT # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 287,304 **** # an MP who went on a hunger strike for 11 days to force discussion about it! # We have no details, but we'll guess they didn't move the clocks back in fall. # ! # From Paul Eggert (1995-11-13): ! # usno1995 has Georgia at 4:00. Guess that Georgia stopped transitions ! # after spring 1994 (thus sticking at 4:00). ! # Most likely we're still missing some rule changes between 1991 and 1994. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tbilisi 2:59:16 - LMT 1880 2:59:16 - TBMT 1924 May 2 # Tbilisi Mean Time 3:00 - TBIT 1957 Mar # Tbilisi Time 4:00 RussiaAsia TBI%sT 1991 Mar 31 2:00s 3:00 1:00 TBIST 1991 Apr 9 # independence ! 3:00 RussiaAsia GE%sT 1994 Sep 25 2:00s # Georgia Time ! 4:00 - GET # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 304,323 ---- # an MP who went on a hunger strike for 11 days to force discussion about it! # We have no details, but we'll guess they didn't move the clocks back in fall. # ! # From Mathew Englander <mathew(a)io.org>, quoting AP (1996-10-23 13:05-04): ! # Instead of putting back clocks at the end of October, Georgia ! # will stay on daylight savings time this winter to save energy, ! # President Eduard Shevardnadze decreed Wednesday. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tbilisi 2:59:16 - LMT 1880 2:59:16 - TBMT 1924 May 2 # Tbilisi Mean Time 3:00 - TBIT 1957 Mar # Tbilisi Time 4:00 RussiaAsia TBI%sT 1991 Mar 31 2:00s 3:00 1:00 TBIST 1991 Apr 9 # independence ! 3:00 RussiaAsia GE%sT 1992 # Georgia Time ! 3:00 E-EurAsia GE%sT 1994 Sep lastSun ! 4:00 E-EurAsia GE%sT 1996 Oct lastSun ! 5:00 - GET # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 340,345 **** --- 359,371 ---- Rule Iran 1978 only - Oct 21 0:00 0 - Rule Iran 1979 only - Sep 19 0:00 0 - Rule Iran 1980 only - Sep 23 0:00 0 - + Rule Iran 1991 only - May 3 0:00s 1:00 S + Rule Iran 1991 only - Sep 20 0:00s 0 - + Rule Iran 1992 only - Mar 22 0:00 1:00 S + Rule Iran 1992 1993 - Sep 23 0:00 0 - + Rule Iran 1993 max - Mar 21 0:00 1:00 S + Rule Iran 1994 1995 - Sep 22 0:00 0 - + Rule Iran 1996 max - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 3:25:44 - TMT 1946 # Tehran Mean Time *************** *** 353,360 **** Rule Iraq 1982 1984 - Oct 1 0:00 0 S Rule Iraq 1983 only - Mar 31 0:00 1:00 D Rule Iraq 1984 1985 - Apr 1 0:00 1:00 D ! Rule Iraq 1985 max - Sep lastSun 1:00s 0 S ! Rule Iraq 1986 max - Mar lastSun 1:00s 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 2:57:36 - BMT 1918 # Baghdad Mean Time? --- 379,389 ---- Rule Iraq 1982 1984 - Oct 1 0:00 0 S Rule Iraq 1983 only - Mar 31 0:00 1:00 D Rule Iraq 1984 1985 - Apr 1 0:00 1:00 D ! Rule Iraq 1985 1990 - Sep lastSun 1:00s 0 S ! Rule Iraq 1986 1990 - Mar lastSun 1:00s 1:00 D ! # IATA SSIM (1991/1996) says Apr 1 12:01am UTC; guess the `:01' is a typo. ! Rule Iraq 1991 max - Apr 1 3:00s 1:00 D ! Rule Iraq 1991 max - Oct 1 3:00s 0 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 2:57:36 - BMT 1918 # Baghdad Mean Time? *************** *** 512,520 **** # Other Japanese possessions are probably like Asia/Tokyo. # Jordan - # From Paul Eggert <eggert(a)twinsun.com> (1993-11-18): - # Most likely Shanks is merely guessing dates from 1992 on. - # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Jordan 1973 only - Jun 6 0:00 1:00 S Rule Jordan 1973 1975 - Oct 1 0:00 0 - --- 541,546 ---- *************** *** 529,568 **** Rule Jordan 1986 1990 - Oct Fri>=1 0:00 0 - Rule Jordan 1989 only - May 8 0:00 1:00 S Rule Jordan 1990 only - Apr 27 0:00 1:00 S ! Rule Jordan 1991 only - Apr 19 0:00 1:00 S Rule Jordan 1991 only - Sep 27 0:00 0 - ! Rule Jordan 1992 max - Apr Fri>=1 0:00 1:00 S ! Rule Jordan 1992 max - Oct Fri>=1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Amman 2:23:44 - LMT 1931 2:00 Jordan EE%sT # Kazakhstan ! # From Paul Eggert (1996-04-19): # Andrew Evtichov <evti(a)chevron.com> (1996-04-13) writes that Kazakhstan ! # stayed in sync with Moscow after 1990, and that Aktau is the biggest city ! # in western Kazakhstan. Follow Shanks before 1991, Evtichov afterwards. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Alma-Ata 5:07:48 - LMT 1924 May 2 # or Almaty 5:00 - ALMT 1957 Mar # Alma-Ata Time 6:00 RussiaAsia ALM%sT 1991 Mar 31 2:00s 5:00 1:00 ALMST 1991 Sep 29 2:00s 5:00 - ALMT 1992 Jan 19 2:00s ! 6:00 RussiaAsia ALM%sT ! Zone Asia/Aktau 3:21:04 - LMT 1924 May 2 # or Aqtau 4:00 - SHET 1957 Mar # Fort Shevchenko Time 5:00 RussiaAsia SHE%sT 1991 Mar 31 2:00s ! 4:00 1:00 AKTST 1991 Sep 29 2:00s ! 4:00 - AKTT 1992 Jan 19 2:00s # Aktau Time ! 5:00 RussiaAsia AKT%sT # Kirgizstan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 5:00 - FRUT 1957 Mar # Frunze Time 6:00 RussiaAsia FRU%sT 1991 Mar 31 2:00s 5:00 1:00 FRUST 1991 Aug 31 # independence ! 5:00 RussiaAsia KG%sT # Kirgizstan Time ############################################################################### --- 555,610 ---- Rule Jordan 1986 1990 - Oct Fri>=1 0:00 0 - Rule Jordan 1989 only - May 8 0:00 1:00 S Rule Jordan 1990 only - Apr 27 0:00 1:00 S ! Rule Jordan 1991 only - Apr 17 0:00 1:00 S Rule Jordan 1991 only - Sep 27 0:00 0 - ! Rule Jordan 1992 only - Apr 10 0:00 1:00 S ! Rule Jordan 1992 1993 - Oct Fri>=1 0:00 0 - ! Rule Jordan 1993 max - Apr Fri>=1 0:00 1:00 S ! Rule Jordan 1994 only - Sep Fri>=15 0:00 0 - ! Rule Jordan 1995 max - Sep Fri>=15 0:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Amman 2:23:44 - LMT 1931 2:00 Jordan EE%sT # Kazakhstan ! # From Paul Eggert (1996-11-22): # Andrew Evtichov <evti(a)chevron.com> (1996-04-13) writes that Kazakhstan ! # stayed in sync with Moscow after 1990, and that Aqtobe (formerly Aktyubinsk) ! # and Aqtau (formerly Shevchenko) are the largest cities in their zones. ! # Guess that Aqtau and Aqtobe diverged in 1995, since that's the first time ! # IATA SSIM mentions a third time zone in Kazakhstan. ! # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Alma-Ata 5:07:48 - LMT 1924 May 2 # or Almaty 5:00 - ALMT 1957 Mar # Alma-Ata Time 6:00 RussiaAsia ALM%sT 1991 Mar 31 2:00s 5:00 1:00 ALMST 1991 Sep 29 2:00s 5:00 - ALMT 1992 Jan 19 2:00s ! 6:00 E-EurAsia ALM%sT ! Zone Asia/Aqtobe 3:48:40 - LMT 1924 May 2 ! 4:00 - AKT 1957 Mar # Aktyubinsk Time ! 5:00 RussiaAsia AK%sT 1991 Mar 31 2:00s ! 4:00 1:00 AKTST 1991 Sep 29 2:00s ! 4:00 - AQTT 1992 Jan 19 2:00s # Aqtobe Time ! 5:00 E-EurAsia AQT%sT ! Zone Asia/Aqtau 3:21:04 - LMT 1924 May 2 # or Aktau 4:00 - SHET 1957 Mar # Fort Shevchenko Time 5:00 RussiaAsia SHE%sT 1991 Mar 31 2:00s ! 4:00 1:00 AQTST 1991 Sep 29 2:00s ! 4:00 - AQTT 1992 Jan 19 2:00s # Aqtau Time ! 5:00 E-EurAsia AQT%sT 1995 Sep lastSun ! 4:00 E-EurAsia AQT%sT # Kirgizstan + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule Kirgiz 1992 max - Apr Sun>=7 0:00 1:00 S + Rule Kirgiz 1991 max - Sep lastSun 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 5:00 - FRUT 1957 Mar # Frunze Time 6:00 RussiaAsia FRU%sT 1991 Mar 31 2:00s 5:00 1:00 FRUST 1991 Aug 31 # independence ! 5:00 Kirgiz KG%sT # Kirgizstan Time ############################################################################### *************** *** 630,639 **** Rule Lebanon 1978 only - Apr 30 0:00 1:00 S Rule Lebanon 1978 only - Sep 30 0:00 0 - Rule Lebanon 1984 1987 - May 1 0:00 1:00 S ! Rule Lebanon 1984 max - Oct 16 0:00 0 - Rule Lebanon 1988 only - Jun 1 0:00 1:00 S Rule Lebanon 1989 only - May 10 0:00 1:00 S ! Rule Lebanon 1990 max - May 1 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Beirut 2:22:00 - LMT 1880 2:00 Lebanon EE%sT --- 672,684 ---- Rule Lebanon 1978 only - Apr 30 0:00 1:00 S Rule Lebanon 1978 only - Sep 30 0:00 0 - Rule Lebanon 1984 1987 - May 1 0:00 1:00 S ! Rule Lebanon 1984 1991 - Oct 16 0:00 0 - Rule Lebanon 1988 only - Jun 1 0:00 1:00 S Rule Lebanon 1989 only - May 10 0:00 1:00 S ! Rule Lebanon 1990 1992 - May 1 0:00 1:00 S ! Rule Lebanon 1992 only - Oct 4 0:00 0 - ! Rule Lebanon 1993 max - Mar lastSun 0:00 1:00 S ! Rule Lebanon 1993 max - Sep lastSun 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Beirut 2:22:00 - LMT 1880 2:00 Lebanon EE%sT *************** *** 673,680 **** # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Mongol 1981 1984 - Apr 1 0:00 1:00 S Rule Mongol 1981 1984 - Oct 1 0:00 0 - ! Rule Mongol 1985 max - Mar lastSun 2:00 1:00 S ! Rule Mongol 1985 max - Sep lastSun 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug # 6:00 - DART 1978 # Dariv Time --- 718,728 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Mongol 1981 1984 - Apr 1 0:00 1:00 S Rule Mongol 1981 1984 - Oct 1 0:00 0 - ! Rule Mongol 1985 1990 - Mar lastSun 2:00 1:00 S ! Rule Mongol 1985 1990 - Sep lastSun 3:00 0 - ! Rule Mongol 1991 max - Mar lastSun 0:00 1:00 S ! Rule Mongol 1991 1995 - Sep lastSun 0:00 0 - ! Rule Mongol 1996 max - Oct Fri>=22 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug # 6:00 - DART 1978 # Dariv Time *************** *** 712,720 **** Rule EgyptAsia 1957 only - May 10 0:00 1:00 S Rule EgyptAsia 1957 1958 - Oct 1 0:00 0 - Rule EgyptAsia 1958 only - May 1 0:00 1:00 S ! Rule EgyptAsia 1959 1981 - May 1 1:00 1:00 S Rule EgyptAsia 1959 1965 - Sep 30 3:00 0 - ! Rule EgyptAsia 1966 max - Oct 1 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 - EET 1957 May 10 --- 760,768 ---- Rule EgyptAsia 1957 only - May 10 0:00 1:00 S Rule EgyptAsia 1957 1958 - Oct 1 0:00 0 - Rule EgyptAsia 1958 only - May 1 0:00 1:00 S ! Rule EgyptAsia 1959 1967 - May 1 1:00 1:00 S Rule EgyptAsia 1959 1965 - Sep 30 3:00 0 - ! Rule EgyptAsia 1966 only - Oct 1 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 - EET 1957 May 10 *************** *** 806,813 **** Rule Syria 1988 only - Mar 15 2:00 1:00 S Rule Syria 1989 only - Mar 31 2:00 1:00 S Rule Syria 1989 only - Oct 1 2:00 0 - ! Rule Syria 1990 max - Apr 1 2:00 1:00 S ! Rule Syria 1990 max - Sep 30 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Damascus 2:25:12 - LMT 1920 2:00 Syria EE%sT --- 854,869 ---- Rule Syria 1988 only - Mar 15 2:00 1:00 S Rule Syria 1989 only - Mar 31 2:00 1:00 S Rule Syria 1989 only - Oct 1 2:00 0 - ! Rule Syria 1990 only - Apr 1 2:00 1:00 S ! Rule Syria 1990 only - Sep 30 2:00 0 - ! Rule Syria 1991 only - Apr 1 0:00 1:00 S ! Rule Syria 1991 1992 - Oct 1 0:00 0 - ! Rule Syria 1992 only - Apr 8 0:00 1:00 S ! Rule Syria 1993 only - Mar 26 0:00 1:00 S ! Rule Syria 1993 only - Sep 25 0:00 0 - ! # IATA SSIM (1996-09) says 1997-03-31; assume that it should be 1997-04-01. ! Rule Syria 1994 max - Apr 1 0:00 1:00 S ! Rule Syria 1994 max - Oct 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Damascus 2:25:12 - LMT 1920 2:00 Syria EE%sT *************** *** 820,829 **** 5:00 1:00 DUSST 1991 Sep 9 # independence 5:00 RussiaAsia TJ%sT 1992 5:00 - TJT # Tajikistan Time - # Shanks has Dushanbe at 5:00 (6:00 summer) after 1991, - # but a cable from the American Embassy at Dushanbe - # <URL:http://www.itaiep.doc.gov/bisnis/cables/960703ti.html> (1996-07-02) - # says that Tajikistan is at 5:00. Guess no DST after 1991. # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 876,881 ---- *************** *** 836,847 **** Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 # or Ashgabat 4:00 - ASHT 1957 Mar # Ashkhabad Time 5:00 RussiaAsia ASH%sT 1991 Mar 31 2:00s ! 4:00 1:00 ASHST 1991 Oct 27 # independence ! 4:00 RussiaAsia TM%sT 1992 # Turkmenistan Time ! 4:00 - TMT ! # Shanks has Ashkhabad at 4:00 (5:00 summer) after 1991, but ! # DHL <URL:http://www.dhl.com/dhlinfo/country/turkmeni.html> (1996-07-26) ! # reports 4:00. Guess no DST after 1991. # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 888,897 ---- Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 # or Ashgabat 4:00 - ASHT 1957 Mar # Ashkhabad Time 5:00 RussiaAsia ASH%sT 1991 Mar 31 2:00s ! 4:00 1:00 ASHST 1991 Sep 29 2:00s ! 4:00 - ASHT 1991 Oct 27 # independence ! 4:00 - TMT 1992 Jan 19 2:00s ! 5:00 - TMT # Turkmenistan Time # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/australasia,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** australasia 1996/11/05 18:50:13 1996.12 --- australasia 1996/11/22 19:39:06 1996.12.1.1 *************** *** 35,51 **** 8:00 1:00 WST 1992 Mar Sun>=1 2:00s 8:00 - WST # Queensland Zone Australia/Brisbane 10:12:08 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s 10:00 1:00 EST 1972 Feb lastSun 2:00s ! 10:00 - EST 1989 Oct lastSun 2:00s ! 10:00 1:00 EST 1990 Mar Sun>=1 2:00s ! 10:00 - EST 1990 Oct lastSun 2:00s ! 10:00 1:00 EST 1991 Mar Sun>=1 2:00s ! 10:00 - EST 1991 Oct lastSun 2:00s ! 10:00 1:00 EST 1992 Mar Sun>=1 2:00s ! 10:00 - EST # South Australia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 35,67 ---- 8:00 1:00 WST 1992 Mar Sun>=1 2:00s 8:00 - WST # Queensland + # + # From Alex Livingston <alex(a)agsm.unsw.edu.au> (1996-11-01): + # I have heard or read more than once that some resort islands off the coast + # of Queensland chose to keep observing daylight-saving time even after + # Queensland ceased to. + # + # From Paul Eggert (1996-11-22): + # IATA SSIM (1993-02/1994-09) say that the Holiday Islands (Hayman, Lindeman, + # Hamilton) observed DST for two years after the rest of Queensland stopped. + # Hamilton is the largest, but there is also a Hamilton in Victoria, + # so use Lindeman. + # + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule QL 1989 1991 - Oct lastSun 2:00s 1:00 - + Rule QL 1990 1992 - Mar Sun>=1 2:00s 0 - + Rule Holiday 1989 1993 - Oct lastSun 2:00s 1:00 - + Rule Holiday 1990 1994 - Mar Sun>=1 2:00s 0 - Zone Australia/Brisbane 10:12:08 - LMT 1895 10:00 - EST 1917 Jan 1 0:01 10:00 Aus EST 1971 Oct lastSun 2:00s 10:00 1:00 EST 1972 Feb lastSun 2:00s ! 10:00 QL EST ! Zone Australia/Lindeman 9:55:56 - LMT 1895 ! 10:00 - EST 1917 Jan 1 0:01 ! 10:00 Aus EST 1971 Oct lastSun 2:00s ! 10:00 1:00 EST 1972 Feb lastSun 2:00s ! 10:00 Holiday EST # South Australia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S *************** *** 289,299 **** Rule NZ 1975 only - Feb 23 2:00s 0 S Rule NZ 1976 1989 - Mar Sun>=1 2:00s 0 S Rule NZ 1990 max - Mar Sun>=15 2:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 12:00 NZ NZ%sT ! Zone Pacific/Chatham 12:45 NZ CHA%sT # Antipodes Is, Kermadec Is --- 305,317 ---- Rule NZ 1975 only - Feb 23 2:00s 0 S Rule NZ 1976 1989 - Mar Sun>=1 2:00s 0 S Rule NZ 1990 max - Mar Sun>=15 2:00s 0 S + Rule Chatham 1990 max - Oct Sun>=1 2:45s 1:00 D + Rule Chatham 1991 max - Mar Sun>=15 2:45s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 12:00 NZ NZ%sT ! Zone Pacific/Chatham 12:45 Chatham CHA%sT # Antipodes Is, Kermadec Is *************** *** 375,383 **** Rule Vanuatu 1983 only - Sep 25 0:00 1:00 S Rule Vanuatu 1984 1991 - Mar Sun>=23 0:00 0 - Rule Vanuatu 1984 only - Oct 23 0:00 1:00 S ! Rule Vanuatu 1985 1990 - Sep Sun>=23 0:00 1:00 S ! Rule Vanuatu 1991 max - Sep lastSun 0:00 1:00 S ! Rule Vanuatu 1992 max - Mar lastSun 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila 11:00 Vanuatu VU%sT # Vanuatu Time --- 393,401 ---- Rule Vanuatu 1983 only - Sep 25 0:00 1:00 S Rule Vanuatu 1984 1991 - Mar Sun>=23 0:00 0 - Rule Vanuatu 1984 only - Oct 23 0:00 1:00 S ! Rule Vanuatu 1985 1991 - Sep Sun>=23 0:00 1:00 S ! Rule Vanuatu 1992 1993 - Jan Sun>=23 0:00 0 - ! Rule Vanuatu 1992 only - Oct Sun>=23 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila 11:00 Vanuatu VU%sT # Vanuatu Time *************** *** 400,410 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-01-22); # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # Except where noted, it is the source for the data above. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which --- 418,436 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # ! # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source ! # for recent time zone data is the International Air Transport ! # Association's Standard Schedules Information Manual (IATA SSIM), ! # published semiannually. Law sent in several helpful summaries ! # of the IATA's data after 1990. ! # ! # Except where otherwise noted, Shanks is the source for entries through 1990, ! # and IATA SSIM is the source for entries after 1990. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which *************** *** 799,806 **** # time on both the first Sunday in October and the third Sunday in March. # As with Australia, we'll assume the tradition is 2:00s, not 2:00. # ! # Shanks gives no data for Chatham, but usno1995 says it's +12:45/+13:45. ! # Guess NZ switchover rules for now. ############################################################################### --- 825,835 ---- # time on both the first Sunday in October and the third Sunday in March. # As with Australia, we'll assume the tradition is 2:00s, not 2:00. # ! # From Paul Eggert (1996-11-22): ! # Shanks gives no data for Chatham; usno1989 says it's +12:45, ! # usno1995 says it's +12:45/+13:45, and IATA SSIM (1991/1996) ! # gives the NZ rules but with transitions at 2:45 local standard time. ! # Guess that they adopted DST in 1990. ############################################################################### =================================================================== RCS file: RCS/etcetera,v retrieving revision 1996.4 retrieving revision 1996.4.1.1 diff -c -r1996.4 -r1996.4.1.1 *** etcetera 1996/03/19 01:49:39 1996.4 --- etcetera 1996/11/22 19:39:06 1996.4.1.1 *************** *** 1,15 **** # @(#)etcetera 7.5 ! # All of these are set up just so people can "zic -l" to a timezone ! # that's right for their area, even if it doesn't have a name or DST rules ! # (half hour zones are too much to bother with -- when someone asks!) Zone Etc/GMT 0 - GMT ! Link Etc/GMT Etc/UTC ! Link Etc/GMT Etc/UCT ! Link Etc/GMT Etc/Universal Link Etc/GMT Etc/Greenwich - Link Etc/GMT Etc/Zulu Link Etc/GMT Etc/GMT-0 Link Etc/GMT Etc/GMT+0 Link Etc/GMT Etc/GMT0 --- 1,19 ---- # @(#)etcetera 7.5 ! # These entries are mostly present for historical reasons, so that ! # people in areas not otherwise covered by the tz files could "zic -l" ! # to a time zone that was right for their area. These days, the ! # tz files cover almost all the inhabited world, so there's little ! # need now for the entries that are not on UTC. Zone Etc/GMT 0 - GMT ! Zone Etc/UTC 0 - UTC ! Zone Etc/UCT 0 - UCT ! ! Link Etc/UTC Etc/Universal ! Link Etc/UTC Etc/Zulu ! Link Etc/GMT Etc/Greenwich Link Etc/GMT Etc/GMT-0 Link Etc/GMT Etc/GMT+0 Link Etc/GMT Etc/GMT0 =================================================================== RCS file: RCS/europe,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** europe 1996/11/05 18:50:14 1996.12 --- europe 1996/11/22 19:39:06 1996.12.1.1 *************** *** 4,14 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # Except where otherwise noted, it is the source for the data below. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which --- 4,22 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # ! # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source ! # for recent time zone data is the International Air Transport ! # Association's Standard Schedules Information Manual (IATA SSIM), ! # published semiannually. Law sent in several helpful summaries ! # of the IATA's data after 1990. ! # ! # Except where otherwise noted, Shanks is the source for entries through 1990, ! # and IATA SSIM is the source for entries after 1990. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which *************** *** 27,32 **** --- 35,41 ---- # 0:00 WET WEST Western Europe # 1:00 CET CEST Central Europe # 2:00 EET EEST Eastern Europe + # 3:00 MSK MSD Moscow # # See the `africa' file for time zone naming and abbreviation conventions. # *************** *** 826,831 **** --- 835,848 ---- Rule C-Eur 1981 max - Mar lastSun 2:00s 1:00 S Rule C-Eur 1996 max - Oct lastSun 2:00s 0 - + # E-Eur differs from EU only in that E-Eur switches at midnight local time. + Rule E-Eur 1977 1980 - Apr Sun>=1 0:00 1:00 S + Rule E-Eur 1977 only - Sep lastSun 0:00 0 - + Rule E-Eur 1978 only - Oct 1 0:00 0 - + Rule E-Eur 1979 1995 - Sep lastSun 0:00 0 - + Rule E-Eur 1981 max - Mar lastSun 0:00 1:00 S + Rule E-Eur 1996 max - Oct lastSun 0:00 0 - + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Russia 1917 only - Jul 1 23:00 1:00 MST # Moscow Summer Time Rule Russia 1917 only - Dec 28 0:00 0 MMT # Moscow Mean Time *************** *** 836,850 **** Rule Russia 1919 only - Aug 16 0:00 0 - Rule Russia 1921 only - Feb 14 23:00 1:00 S # Shanks gives 1921 Mar 21 for the following transition. ! # From Andrew A. Chernov <ache(a)astral.msk.su> (1993-11-12): # My sources says, that it is Mar 20, not 21. Rule Russia 1921 only - Mar 20 23:00 2:00 DS Rule Russia 1921 only - Sep 1 0:00 1:00 S Rule Russia 1921 only - Oct 1 0:00 0 - Rule Russia 1981 1984 - Apr 1 0:00 1:00 S Rule Russia 1981 1983 - Oct 1 0:00 0 - ! Rule Russia 1984 max - Sep lastSun 2:00s 0 - ! Rule Russia 1985 max - Mar lastSun 2:00s 1:00 S # These are for backward compatibility with older versions. --- 853,872 ---- Rule Russia 1919 only - Aug 16 0:00 0 - Rule Russia 1921 only - Feb 14 23:00 1:00 S # Shanks gives 1921 Mar 21 for the following transition. ! # From Andrey A. Chernov <ache(a)astral.msk.su> (1993-11-12): # My sources says, that it is Mar 20, not 21. Rule Russia 1921 only - Mar 20 23:00 2:00 DS Rule Russia 1921 only - Sep 1 0:00 1:00 S Rule Russia 1921 only - Oct 1 0:00 0 - Rule Russia 1981 1984 - Apr 1 0:00 1:00 S Rule Russia 1981 1983 - Oct 1 0:00 0 - ! Rule Russia 1984 1991 - Sep lastSun 2:00s 0 - ! Rule Russia 1985 1991 - Mar lastSun 2:00s 1:00 S ! Rule Russia 1992 only - Mar lastSat 23:00 1:00 S ! Rule Russia 1992 only - Sep lastSat 23:00 0 - ! Rule Russia 1993 max - Mar lastSun 2:00s 1:00 S ! Rule Russia 1993 1995 - Sep lastSun 2:00s 0 - ! Rule Russia 1996 max - Oct lastSun 2:00s 0 - # These are for backward compatibility with older versions. *************** *** 913,919 **** Zone Europe/Tirane 1:19:20 - LMT 1914 1:00 - CET 1940 Jun 16 1:00 Albania CE%sT 1985 Mar 31 1:00 ! 1:00 W-Eur CE%sT # Andorra # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 935,942 ---- Zone Europe/Tirane 1:19:20 - LMT 1914 1:00 - CET 1940 Jun 16 1:00 Albania CE%sT 1985 Mar 31 1:00 ! 1:00 W-Eur CE%sT 1991 ! 1:00 EU CE%sT # Andorra # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 944,954 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MOS%sT 1922 Oct # Moscow Time 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Belgium # Whitman and Shanks disagree; go with Shanks, usually. --- 967,979 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MSK/MSD 1922 Oct 2:00 - EET 1930 Jun 21 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 - EET 1992 Mar 29 0:00 ! 2:00 1:00 EEST 1992 Sep 27 0:00 ! 2:00 Russia EE%sT # Belgium # Whitman and Shanks disagree; go with Shanks, usually. *************** *** 1021,1027 **** 1:00 C-Eur CE%sT 1945 Apr 2 3:00 2:00 - EET 1979 Mar 31 23:00 2:00 Bulg EE%sT 1982 Sep 26 2:00 ! 2:00 C-Eur EE%sT # Croatia # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1046,1053 ---- 1:00 C-Eur CE%sT 1945 Apr 2 3:00 2:00 - EET 1979 Mar 31 23:00 2:00 Bulg EE%sT 1982 Sep 26 2:00 ! 2:00 C-Eur EE%sT 1991 ! 2:00 E-Eur EE%sT # Croatia # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 1077,1106 **** Zone Atlantic/Faeroe -0:27:04 - LMT 1908 Jan 11 # Torshavn 0:00 - WET 1981 0:00 EU WE%sT ! Zone America/Scoresbysund -1:29:00 - LMT 1916 Jul 28 -2:00 - CGT 1980 Apr 6 2:00 -2:00 C-Eur CG%sT 1981 Mar 29 ! -1:00 C-Eur EG%sT ! Zone America/Godthab -3:26:56 - LMT 1916 Jul 28 -3:00 - WGT 1980 Apr 6 2:00 ! -3:00 C-Eur WG%sT ! Zone America/Thule -4:35:08 - LMT 1916 Jul 28 ! -4:00 - AST # Estonia # From Peter Ilieve <peter(a)memex.co.uk> (1994-10-15): # A relative in Tallinn confirms the accuracy of the data for 1989 onwards # [through 1994] and gives the legal authority for it, # a regulation of the Government of Estonia, No. 111 of 1989.... # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tallinn 1:39:00 - LMT 1880 1:39:00 - TMT 1918 Feb # Tallinn Mean Time 1:00 C-Eur CE%sT 1919 Jul 1:39:00 - TMT 1921 May 2:00 - EET 1940 Aug 6 ! 3:00 - MOST 1941 Sep 15 # Moscow Time 1:00 C-Eur CE%sT 1944 Sep 22 ! 3:00 Russia MOS%sT 1989 Mar 26 2:00s 2:00 1:00 EEST 1989 Sep 24 2:00s 2:00 C-Eur EE%sT --- 1103,1156 ---- Zone Atlantic/Faeroe -0:27:04 - LMT 1908 Jan 11 # Torshavn 0:00 - WET 1981 0:00 EU WE%sT ! # ! # From Paul Eggert (1996-11-22): ! # Greenland joined the EU as part of Denmark, obtained home rule on 1979-05-01, ! # and left the EU on 1985-02-01. It therefore should have been using EU ! # rules at least through 1984. Shanks says Scoresbysund and Godthab ! # used C-Eur rules after 1980, but IATA SSIM (1991/1996) says they use EU ! # rules since at least 1991. Assume EU rules since 1980. ! ! # ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Thule 1993 max - Apr Sun>=1 2:00 1:00 D ! Rule Thule 1993 max - Oct lastSun 2:00 0 S ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone America/Scoresbysund -1:29:00 - LMT 1916 Jul 28 # Ittoqqortoormit -2:00 - CGT 1980 Apr 6 2:00 -2:00 C-Eur CG%sT 1981 Mar 29 ! -1:00 EU EG%sT ! Zone America/Godthab -3:26:56 - LMT 1916 Jul 28 # Nuuk -3:00 - WGT 1980 Apr 6 2:00 ! -3:00 EU WG%sT ! Zone America/Thule -4:35:08 - LMT 1916 Jul 28 # Pituffik ! -4:00 Thule A%sT # Estonia # From Peter Ilieve <peter(a)memex.co.uk> (1994-10-15): # A relative in Tallinn confirms the accuracy of the data for 1989 onwards # [through 1994] and gives the legal authority for it, # a regulation of the Government of Estonia, No. 111 of 1989.... + # + # From Peter Ilieve <peter(a)aldie.co.uk> (1996-10-28): + # [IATA SSIM (1992/1996) claims that the Baltic republics switch at 01:00s, + # but a relative confirms that Estonia still switches at 02:00s, writing:] + # ``I do not [know] exactly but there are some little different + # (confusing) rules for International Air and Railway Transport Schedules + # conversion in Sunday connected with end of summer time in Estonia.... + # A discussion is running about the summer time efficiency and effect on + # human physiology. It seems that Estonia maybe will not change to + # summer time next spring.'' # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tallinn 1:39:00 - LMT 1880 1:39:00 - TMT 1918 Feb # Tallinn Mean Time 1:00 C-Eur CE%sT 1919 Jul 1:39:00 - TMT 1921 May 2:00 - EET 1940 Aug 6 ! 3:00 - MSK 1941 Sep 15 1:00 C-Eur CE%sT 1944 Sep 22 ! 3:00 Russia MSK/MSD 1989 Mar 26 2:00s 2:00 1:00 EEST 1989 Sep 24 2:00s 2:00 C-Eur EE%sT *************** *** 1418,1423 **** --- 1468,1481 ---- Link Europe/Rome Europe/San_Marino # Latvia + # From Paul Eggert (1996-11-22): + # Rules after 1991 are by extension from Shanks. They contradict + # IATA SSIM (1992/1996), which claims Latvia uses W-Eur rules, but + # Peter Ilieve's relative writes that Latvia switched in September this year, + # so we'll assume that the old C-Eur-style rules still apply. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule Latvia 1992 max - Mar lastSun 2:00s 1:00 S + Rule Latvia 1992 max - Sep lastSun 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Riga 1:36:24 - LMT 1880 1:36:24 - RMT 1918 Apr 15 2:00 #Riga Mean Time *************** *** 1426,1436 **** 1:36:24 1:00 LST 1919 May 22 3:00 1:36:24 - RMT 1926 May 11 2:00 - EET 1940 Aug 5 ! 3:00 - MOST 1941 Jul # Moscow Time 1:00 C-Eur CE%sT 1944 Aug 8 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1484,1494 ---- 1:36:24 1:00 LST 1919 May 22 3:00 1:36:24 - RMT 1926 May 11 2:00 - EET 1940 Aug 5 ! 3:00 - MSK 1941 Jul 1:00 C-Eur CE%sT 1944 Aug 8 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 Latvia EE%sT # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 1446,1456 **** 1:00 - CET 1920 Jul 12 2:00 - EET 1920 Oct 9 1:00 - CET 1940 Aug 3 ! 3:00 - MOST 1941 Jun 24 # Moscow Time 1:00 C-Eur CE%sT 1944 Aug ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s 2:00 C-Eur EE%sT # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. --- 1504,1517 ---- 1:00 - CET 1920 Jul 12 2:00 - EET 1920 Oct 9 1:00 - CET 1940 Aug 3 ! 3:00 - MSK 1941 Jun 24 1:00 C-Eur CE%sT 1944 Aug ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s 2:00 C-Eur EE%sT + # From Paul Eggert (1996-11-22): + # IATA SSIM (1992/1996) says Lithuania uses W-Eur rules, but since it is + # known to be wrong about Estonia and Latvia, assume it's wrong here too. # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. *************** *** 1517,1525 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s # Moscow Time 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Monaco # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. --- 1578,1586 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 E-Eur EE%sT # Monaco # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. *************** *** 1631,1639 **** --- 1692,1721 ---- 1:00 C-Eur CE%sT 1944 Oct 1:00 Poland CE%sT 1977 Apr 3 1:00 1:00 W-Eur CE%sT + # IATA SSIM (1991/1996) gives EU rules, but the _The Warsaw Voice_ + # <URL:http://www.contact.waw.pl/voice/v361/NewsInBrief.shtml> + # (1995-09-24) says the autumn 1995 switch was at 02:00. + # Stick with W-Eur for now. # Portugal # Gregorian calendar adopted 1582-10-15. + # + # From Rui Pedro Salgueiro <rps(a)inescca.inescc.pt> (1992-11-12): + # Portugal has recently (September, 27) changed timezone + # (from WET to MET or CET) to harmonize with EEC. + # + # Martin Bruckmann <martin(a)ua.pt> (1996-02-29) reports via Peter Ilieve + # that Portugal is reverting to 0:00 by not moving its clocks this spring. + # The new Prime Minister was fed up with getting up in the dark in the winter. + # + # From Paul Eggert (1996-11-12): + # IATA SSIM (1991-09) reports several 1991-09 and 1992-09 transitions + # at 02:00u, not 01:00u. Assume that these are typos. + # IATA SSIM (1991/1992) reports that the Azores were at -1:00. + # IATA SSIM (1993-02) says +0:00; later issues (through 1996-09) say -1:00. + # Guess that the Azores changed to EU rules in 1992 (since that's when Portugal + # harmonized with the EU), and that they stayed +0:00 that winter. + # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Port 1916 only - Jun 17 23:00 1:00 S # Whitman gives 1916 Oct 31; go with Shanks. *************** *** 1701,1723 **** 0:00 Port WE%sT 1966 Apr 3 2:00 1:00 - CET 1976 Sep 26 1:00 0:00 Port WE%sT 1983 Sep 25 1:00s ! # From Rui Pedro Salgueiro <rps(a)inescca.inescc.pt> (1992-11-12): ! # Portugal has recently (September, 27) changed timezone ! # (from WET to MET or CET) to harmonize with EEC. ! 0:00 EU WE%sT 1992 Sep 27 1:00s ! # Martin Bruckmann <martin(a)ua.pt> (1996-02-29) reports via Peter Ilieve ! # that Portugal is reverting to 0:00 by not moving its clocks this spring. ! # The new Prime Minister was fed up with getting up in the dark in the winter. 1:00 EU CE%sT 1996 Mar 31 1:00u 0:00 EU WE%sT - # We don't know what happened to Madeira or the Azores, - # so we'll just use Shanks for now. - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -1:55 - HMT 1911 May 24 # Horta Mean Time -2:00 Port AZO%sT 1966 Apr 3 2:00 # Azores Time -1:00 Port AZO%sT 1983 Sep 25 1:00s ! -1:00 W-Eur AZO%sT Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:08 - FMT 1911 May 24 # Funchal Mean Time -1:00 Port MAD%sT 1966 Apr 3 2:00 # Madeira Time --- 1783,1798 ---- 0:00 Port WE%sT 1966 Apr 3 2:00 1:00 - CET 1976 Sep 26 1:00 0:00 Port WE%sT 1983 Sep 25 1:00s ! 0:00 W-Eur WE%sT 1992 Sep 27 1:00s 1:00 EU CE%sT 1996 Mar 31 1:00u 0:00 EU WE%sT Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -1:55 - HMT 1911 May 24 # Horta Mean Time -2:00 Port AZO%sT 1966 Apr 3 2:00 # Azores Time -1:00 Port AZO%sT 1983 Sep 25 1:00s ! -1:00 W-Eur AZO%sT 1992 Sep 27 1:00s ! 0:00 EU WE%sT 1993 Mar 28 1:00u ! -1:00 EU AZO%sT Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:08 - FMT 1911 May 24 # Funchal Mean Time -1:00 Port MAD%sT 1966 Apr 3 2:00 # Madeira Time *************** *** 1733,1770 **** Rule Romania 1979 only - Sep lastSun 0:00 0 - Rule Romania 1980 only - Apr 5 23:00 1:00 S Rule Romania 1980 only - Sep lastSun 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct 1:44:24 - BMT 1931 Jul 24 # Bucharest MT 2:00 Romania EE%sT 1981 Mar 29 2:00s ! 2:00 C-Eur EE%sT # Russia # From Shanks (1991): # In 1929 the Soviet Union instituted a 5 day week; in 1932 it instituted # a 6 day week; on 1940-06-27 it returned to the Gregorian week. # ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): ! # Moscow rules after 1991 are from Andrew A. Chernov <ache(a)astral.msk.su>. ! # I invented the time zone names, and (unless otherwise specified) ! # guessed what happened after 1991; the clocks were chaotic, and we know little. ! # The rest is from Shanks. ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Moscow 2:30:20 - LMT 1880 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MOS%sT 1922 Oct # Moscow TIme 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MOS%sT ! Zone Europe/Kuybyshev 3:20:36 - LMT 1924 May 2 3:00 - KUYT 1957 Mar # Kuybyshev Time 4:00 Russia KUY%sT 1991 Mar 31 2:00s 3:00 1:00 KUYST 1991 Sep 29 2:00s ! 3:00 - KUYT 1992 Jan 19 2:00s ! 4:00 Russia KUY%sT Zone Asia/Yekaterinburg 4:02:34 - LMT 1924 May 2 4:00 - SVET 1957 Mar # Sverdlovsk Time 5:00 Russia SVE%sT 1991 Mar 31 2:00s --- 1808,1869 ---- Rule Romania 1979 only - Sep lastSun 0:00 0 - Rule Romania 1980 only - Apr 5 23:00 1:00 S Rule Romania 1980 only - Sep lastSun 1:00 0 - + Rule Romania 1991 1993 - Mar lastSun 0:00s 1:00 S + Rule Romania 1991 1993 - Sep lastSun 0:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct 1:44:24 - BMT 1931 Jul 24 # Bucharest MT 2:00 Romania EE%sT 1981 Mar 29 2:00s ! 2:00 C-Eur EE%sT 1991 ! 2:00 Romania EE%sT 1994 ! 2:00 E-Eur EE%sT # Russia # From Shanks (1991): # In 1929 the Soviet Union instituted a 5 day week; in 1932 it instituted # a 6 day week; on 1940-06-27 it returned to the Gregorian week. # ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): ! # Except for Moscow after 1919-07-01, I invented the time zone abbreviations, ! # and (unless otherwise specified) guessed what happened after 1991. ! # Moscow time zone abbreviations after 1919-07-01, and Moscow rules after 1991, ! # are from Andrey A. Chernov. The rest is from Shanks and the IATA. ! # ! # From Andrey A. Chernov <ache(a)nagual.ru> (1996-10-04): ! # `MSK' and `MSD' were born and used initially on Moscow computers with ! # Unix-like OSes by several developer groups (e.g. Demos group, Kiae group).... ! # The next step was the UUCP network, the Relcom predecessor ! # (used mainly for mail), and MSK/MSD was actively used there. ! # ! # From Chris Carrier <72157.3334(a)CompuServe.COM> (1996-10-30): ! # According to a friend of mine who rode the Trans-Siberian Railroad from ! # Moscow to Irkutsk in 1995, public air and rail transport in Russia ... ! # still follows Moscow time, no matter where in Russia it is located. ! # ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Europe/Kaliningrad 1:22:00 - LMT 1893 Apr ! 1:00 C-Eur CE%sT 1945 ! 2:00 Poland CET 1946 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MSK/MSD 1994 ! # IATA SSIM (1994-02) says Kaliningrad is at UTC+2; guess 1994 change. ! 2:00 Russia EE%sT Zone Europe/Moscow 2:30:20 - LMT 1880 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MSK/MSD 1922 Oct 2:00 - EET 1930 Jun 21 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MSK/MSD ! Zone Europe/Samara 3:20:36 - LMT 1924 May 2 3:00 - KUYT 1957 Mar # Kuybyshev Time 4:00 Russia KUY%sT 1991 Mar 31 2:00s 3:00 1:00 KUYST 1991 Sep 29 2:00s ! 3:00 - SAMT 1992 Jan 19 2:00s # Samara Time ! 4:00 Russia SAM%sT Zone Asia/Yekaterinburg 4:02:34 - LMT 1924 May 2 4:00 - SVET 1957 Mar # Sverdlovsk Time 5:00 Russia SVE%sT 1991 Mar 31 2:00s *************** *** 1916,1921 **** --- 2015,2022 ---- 0:00 - WET 1980 Apr 6 0:00s 0:00 1:00 WEST 1980 Sep 28 0:00s 0:00 EU WE%sT + # IATA SSIM (1996-09) says the Canaries switch at 2:00u, not 1:00u. + # Ignore this for now, as the Canaries are part of the EU. # Sweden *************** *** 2026,2032 **** 2:00 Turkey EE%sT 1978 Oct 15 3:00 Turkey TR%sT 1985 Apr 20 # Turkey Time 2:00 Turkey EE%sT 1986 ! 2:00 C-Eur EE%sT Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # Ukraine --- 2127,2134 ---- 2:00 Turkey EE%sT 1978 Oct 15 3:00 Turkey TR%sT 1985 Apr 20 # Turkey Time 2:00 Turkey EE%sT 1986 ! 2:00 C-Eur EE%sT 1991 ! 2:00 EU EE%sT Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # Ukraine *************** *** 2053,2075 **** Rule Crimea 1921 only - Mar 21 23:00 2:00 CDST Rule Crimea 1921 only - Sep 1 0:00 1:00 CST Rule Crimea 1921 only - Oct 1 0:00 0 NMT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Kiev 2:02:04 - LMT 1880 2:02:04 Ukraine %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1990 Jul 17 # Moscow Time ! 2:00 C-Eur EE%sT Zone Europe/Simferopol 2:16:24 - LMT 1880 2:08:00 Crimea %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! # From Paul Eggert <eggert(a)twinsun.com> (1994-05-28): ! # Today's _Economist_ (p 45) reports that Crimea switched ! # from Kiev to Moscow time sometime after the January elections. ! # For now, we'll guess that there was a 2-hour leap forward on March 27. ! 2:00 C-Eur EE%sT 1994 Mar 27 2:00s ! 3:00 Russia MOS%sT # Yugoslavia # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 2155,2182 ---- Rule Crimea 1921 only - Mar 21 23:00 2:00 CDST Rule Crimea 1921 only - Sep 1 0:00 1:00 CST Rule Crimea 1921 only - Oct 1 0:00 0 NMT + Rule Crimea 1996 max - Mar lastSun 0:00u 1:00 - + Rule Crimea 1996 max - Oct lastSun 0:00u 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Kiev 2:02:04 - LMT 1880 2:02:04 Ukraine %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MSK/MSD 1990 Jul 17 ! 2:00 E-Eur EE%sT 1996 ! 2:00 EU EE%sT Zone Europe/Simferopol 2:16:24 - LMT 1880 2:08:00 Crimea %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 2:00 1:00 EEST 1991 Sep 29 2:00s ! # From Paul Eggert <eggert(a)twinsun.com> (1996-10-21): ! # The _Economist_ (1994-05-28, p 45) reports that most of Crimea switched ! # from Kiev to Moscow time sometime after the January 1994 elections. ! # For now, guess it changed Feb 1. ! 2:00 C-Eur EE%sT 1994 Feb ! # From IATA SSIM (1994/1996), which also says that Kerch is still like Kiev. ! 3:00 E-Eur MSK/MSD 1996 ! 3:00 Crimea MSK/MSD # Yugoslavia # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/northamerica,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** northamerica 1996/11/05 18:50:14 1996.12 --- northamerica 1996/11/22 19:39:06 1996.12.1.1 *************** *** 462,472 **** ################################################################################ ! # From Paul Eggert <eggert(a)twinsun.com> (1993-11-18): # A good source for time zone historical data outside the US is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # Except where otherwise noted, it is the source for the data below. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which --- 462,480 ---- ################################################################################ ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # A good source for time zone historical data outside the US is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # ! # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source ! # for recent time zone data is the International Air Transport ! # Association's Standard Schedules Information Manual (IATA SSIM), ! # published semiannually. Law sent in several helpful summaries ! # of the IATA's data after 1990. ! # ! # Except where otherwise noted, Shanks is the source for entries through 1990, ! # and IATA SSIM is the source for entries after 1990. # # Another source occasionally used is Edward W. Whitman, World Time Differences, # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which *************** *** 523,529 **** Rule Canada 1987 max - Apr Sun>=1 2:00 1:00 D ! # Newfoundland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule StJohns 1917 1918 - Apr Sun>=8 2:00 1:00 D --- 531,537 ---- Rule Canada 1987 max - Apr Sun>=1 2:00 1:00 D ! # Newfoundland (except Labrador) # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule StJohns 1917 1918 - Apr Sun>=8 2:00 1:00 D *************** *** 560,570 **** # St John's has an apostrophe, but Posix file names can't have apostrophes. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/St_Johns -3:30:52 - LMT 1884 ! -3:31 StJohns N%sT 1935 Mar 30 -3:30 StJohns N%sT ! # Labrador, New Brunswick, Nova Scotia, Prince Edward I # From Paul Eggert (1996-06-12): # Shanks writes that since 1970 most of this region has been like Halifax. --- 568,590 ---- # St John's has an apostrophe, but Posix file names can't have apostrophes. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/St_Johns -3:30:52 - LMT 1884 ! -3:30:52 StJohns N%sT 1935 Mar 30 -3:30 StJohns N%sT ! # east Labrador ! ! # The name `Happy Valley-Goose Bay' is too long; use `Goose Bay'. ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone America/Goose_Bay -4:01:40 - LMT 1884 # Happy Valley-Goose Bay ! -3:30:52 StJohns NST 1919 ! -3:30:52 - NST 1935 Mar 30 ! -3:30 - NST 1936 ! -3:30 StJohns N%sT 1966 Mar 15 2:00 ! -4:00 StJohns A%sT ! ! ! # west Labrador, New Brunswick, Nova Scotia, Prince Edward I # From Paul Eggert (1996-06-12): # Shanks writes that since 1970 most of this region has been like Halifax. *************** *** 825,833 **** # Northwest Territories, Yukon ! # From Paul Eggert (1996-06-12): # Dawson switched to PST in 1973. Inuvik switched to MST in 1979. # Shanks's table for Watson Lake is corrupted, so we have no data there. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule NT_YK 1918 only - Apr 14 2:00 1:00 D --- 845,861 ---- # Northwest Territories, Yukon ! # From Paul Eggert (1996-10-07): # Dawson switched to PST in 1973. Inuvik switched to MST in 1979. # Shanks's table for Watson Lake is corrupted, so we have no data there. + # Mathew Englander <mathew(a)io.org> (1996-10-07) gives the following refs: + # * 1967. Paragraph 28(34)(g) of the Interpretation Act, S.C. 1967-68, + # c. 7 defines Yukon standard time as UTC-9. This is still valid; + # see Interpretation Act, R.S.C. 1985, c. I-21, s. 35(1). + # * C.O. 1973/214 switched Yukon to PST on 1973-10-28 00:00. + # * O.I.C. 1980/02 established DST. + # * O.I.C. 1987/056 changed DST to Apr firstSun 2:00 to Oct lastSun 2:00. + # Shanks says Yukon's 1973-10-28 switch was at 2:00; go with Englander. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule NT_YK 1918 only - Apr 14 2:00 1:00 D *************** *** 857,863 **** -9:00 NT_YK Y%sT 1966 Jul 1 2:00 -8:00 NT_YK P%sT Zone America/Dawson -9:17:40 - LMT 1900 Aug 20 ! -9:00 NT_YK Y%sT 1973 Oct lastSun 2:00 -8:00 NT_YK P%sT --- 885,891 ---- -9:00 NT_YK Y%sT 1966 Jul 1 2:00 -8:00 NT_YK P%sT Zone America/Dawson -9:17:40 - LMT 1900 Aug 20 ! -9:00 NT_YK Y%sT 1973 Oct 28 0:00 -8:00 NT_YK P%sT *************** *** 1070,1077 **** # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule CR 1979 1980 - Feb lastSun 0:00 1:00 D Rule CR 1979 1980 - Jun Sun>=1 0:00 0 S ! Rule CR 1991 only - Jan 19 0:00 1:00 D ! Rule CR 1991 only - Jul 1 0:00 0 S # There are too many San Joses elsewhere, so we'll use `Costa Rica'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Costa_Rica -5:36:20 - LMT 1890 # San Jose --- 1098,1107 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule CR 1979 1980 - Feb lastSun 0:00 1:00 D Rule CR 1979 1980 - Jun Sun>=1 0:00 0 S ! Rule CR 1991 1992 - Jan Sat>=15 0:00 1:00 D ! # IATA SSIM (1991-09) says the following was at 1:00; go with Shanks. ! Rule CR 1991 only - Jul 1 0:00 0 S ! Rule CR 1992 only - Mar 15 0:00 0 S # There are too many San Joses elsewhere, so we'll use `Costa Rica'. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Costa_Rica -5:36:20 - LMT 1890 # San Jose *************** *** 1114,1123 **** Rule Cuba 1978 1980 - Oct Sun>=8 0:00 0 S Rule Cuba 1979 1980 - Mar Sun>=15 0:00 1:00 D Rule Cuba 1981 1985 - May Sun>=5 0:00 1:00 D ! Rule Cuba 1981 max - Oct Sun>=8 0:00 0 S Rule Cuba 1986 1989 - Mar Sun>=14 0:00 1:00 D ! Rule Cuba 1990 only - Apr 1 0:00 1:00 D ! Rule Cuba 1991 max - Mar Sun>=14 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Havana -5:29:28 - LMT 1890 --- 1144,1154 ---- Rule Cuba 1978 1980 - Oct Sun>=8 0:00 0 S Rule Cuba 1979 1980 - Mar Sun>=15 0:00 1:00 D Rule Cuba 1981 1985 - May Sun>=5 0:00 1:00 D ! Rule Cuba 1981 1990 - Oct Sun>=8 0:00 0 S Rule Cuba 1986 1989 - Mar Sun>=14 0:00 1:00 D ! Rule Cuba 1990 max - Apr Sun>=1 0:00 1:00 D ! Rule Cuba 1991 1995 - Oct Sun>=8 0:00s 0 S ! Rule Cuba 1996 max - Oct Sun>=1 0:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Havana -5:29:28 - LMT 1890 *************** *** 1168,1173 **** --- 1199,1206 ---- Rule Guat 1974 only - Feb 24 0:00 0 S Rule Guat 1983 only - May 21 0:00 1:00 D Rule Guat 1983 only - Sep 22 0:00 0 S + Rule Guat 1991 only - Mar 23 0:00 1:00 D + Rule Guat 1991 only - Sep 7 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guatemala -6:02:04 - LMT 1918 Oct 5 -6:00 Guat C%sT *************** *** 1177,1184 **** Rule Haiti 1983 only - May 8 0:00 1:00 D Rule Haiti 1984 1987 - Apr lastSun 0:00 1:00 D Rule Haiti 1983 1987 - Oct lastSun 0:00 0 S ! Rule Haiti 1988 max - Apr Sun>=1 2:00 1:00 D ! Rule Haiti 1988 max - Oct lastSun 2:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Port-au-Prince -4:49:20 - LMT 1890 -4:49 - PPMT 1917 Jan 24 12:00 # P-a-P MT --- 1210,1218 ---- Rule Haiti 1983 only - May 8 0:00 1:00 D Rule Haiti 1984 1987 - Apr lastSun 0:00 1:00 D Rule Haiti 1983 1987 - Oct lastSun 0:00 0 S ! # Shanks says AT is 2:00, but IATA SSIM (1991/1996) says 1:00s. Go with IATA. ! Rule Haiti 1988 max - Apr Sun>=1 1:00s 1:00 D ! Rule Haiti 1988 max - Oct lastSun 1:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Port-au-Prince -4:49:20 - LMT 1890 -4:49 - PPMT 1917 Jan 24 12:00 # P-a-P MT *************** *** 1203,1209 **** Zone America/Jamaica -5:07:12 - LMT 1890 # Kingston -5:07 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST 1974 Jan 6 2:00 ! -5:00 US E%sT # Martinique # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1237,1244 ---- Zone America/Jamaica -5:07:12 - LMT 1890 # Kingston -5:07 - KMT 1912 Feb # Kingston Mean Time -5:00 - EST 1974 Jan 6 2:00 ! -5:00 US E%sT 1984 ! -5:00 - EST # Martinique # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 1222,1233 **** # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Nic 1979 1980 - Mar Sun>=16 0:00 1:00 D Rule Nic 1979 1980 - Jun Mon>=23 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Managua -5:45:08 - LMT 1890 -5:45 - MMT 1934 Jun 23 # Managua Mean Time -6:00 - CST 1973 May -5:00 - EST 1975 Feb 16 ! -6:00 Nic C%sT # Panama # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1257,1271 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Nic 1979 1980 - Mar Sun>=16 0:00 1:00 D Rule Nic 1979 1980 - Jun Mon>=23 0:00 0 S + Rule Nic 1992 only - Jan 1 4:00 1:00 D + Rule Nic 1992 only - Sep 24 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Managua -5:45:08 - LMT 1890 -5:45 - MMT 1934 Jun 23 # Managua Mean Time -6:00 - CST 1973 May -5:00 - EST 1975 Feb 16 ! -6:00 Nic C%sT 1993 Jan 1 4:00 ! -5:00 - EST # Panama # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 1268,1278 **** -4:00 - AST # Turks and Caicos # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Grand_Turk -4:44:32 - LMT 1890 -5:07 - KMT 1912 Feb # Kingston Mean Time ! -5:00 - EST 1979 Apr 29 2:00 ! -5:00 US E%sT # British Virgin Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1306,1322 ---- -4:00 - AST # Turks and Caicos + # From Paul Eggert (1996-11-22): + # Shanks says they use US DST rules, but IATA SSIM (1991/1996) + # says they switch at midnight. Go with IATA SSIM. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule TC 1979 1986 - Apr lastSun 0:00 1:00 D + Rule TC 1979 max - Oct lastSun 0:00 0 S + Rule TC 1987 max - Apr Sun>=1 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Grand_Turk -4:44:32 - LMT 1890 -5:07 - KMT 1912 Feb # Kingston Mean Time ! -5:00 TC E%sT # British Virgin Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/southamerica,v retrieving revision 1996.12 retrieving revision 1996.12.1.1 diff -c -r1996.12 -r1996.12.1.1 *** southamerica 1996/11/05 18:50:15 1996.12 --- southamerica 1996/11/22 19:39:06 1996.12.1.1 *************** *** 4,14 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # Except where otherwise noted, it is the source for the data below. # # The following abbreviations are used in this file. # Corrections are welcome! --- 4,22 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-11-22): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). ! # ! # Gwillim Law <LAW(a)encmail.encompass.com> writes that a good source ! # for recent time zone data is the International Air Transport ! # Association's Standard Schedules Information Manual (IATA SSIM), ! # published semiannually. Law sent in several helpful summaries ! # of the IATA's data after 1990. ! # ! # Except where otherwise noted, Shanks is the source for entries through 1990, ! # and IATA SSIM is the source for entries after 1990. # # The following abbreviations are used in this file. # Corrections are welcome! *************** *** 103,113 **** --- 111,174 ---- # to the time zones (for daylight saving) are now made. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] + # + # Buenos Aires (BA), Distrito Federal (DF), Santa Cruz (SC), + # Tierra del Fuego (TF) & Antartida e Islas Zone America/Buenos_Aires -3:53:48 - LMT 1894 Nov -4:16:44 - CMT 1920 May # Cordoba Mean Time -4:00 - ART 1930 Dec -4:00 Arg AR%sT 1969 Oct 5 -3:00 Arg AR%sT + # + # Santa Fe (SF), Entre Rios (ER), Corrientes (CN), Misiones (MN), Chaco (CC), + # Formosa (FM), La Pampa (LP), Chubut (CH) + Zone America/Rosario -4:02:40 - LMT 1894 Nov + -4:16:44 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1991 Jul + -3:00 - ART + # + # Cordoba (CB), Santiago del Estero (SE), Salta (SA), Tucuman (TM), La Rioja (LR), San Juan (SJ), San Luis (SL), + # Neuquen (NQ), Rio Negro (RN) + Zone America/Cordoba -4:16:44 - LMT 1894 Nov + -4:16:44 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1990 Jul + -3:00 - ART + # + # Jujuy (JY) + Zone America/Jujuy -4:21:12 - LMT 1894 Nov + -4:16:44 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1991 Mar 3 + -4:00 - WART 1991 Oct 6 + -4:00 1:00 WARST 1992 Mar 15 + -4:00 - WART 1992 Oct 18 + -3:00 - ART + # + # Catamarca (CT) + Zone America/Catamarca -4:23:08 - LMT 1894 Nov + -4:16:44 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1990 Jul + -3:00 - ART 1991 Jul + -3:00 Arg AR%sT 1992 Jul + -3:00 - ART + # + # Mendoza (MZ) + Zone America/Mendoza -4:35:16 - LMT 1894 Nov + -4:16:44 - CMT 1920 May + -4:00 - ART 1930 Dec + -4:00 Arg AR%sT 1969 Oct 5 + -3:00 Arg AR%sT 1991 Mar 3 + -4:00 - WART 1991 Oct 15 + -4:00 1:00 WARST 1992 Mar 1 + -4:00 - WART 1992 Oct 18 + -3:00 - ART # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 132,169 **** # "[America/Porto_Acre]" is for the Territory of Acre; # "[America/Noronha]" is for Fernando De Noronha. - # From Bob Devine (1988-01-28): - # The only information I found is that there was no DST up to 1985. - # But there was some before 1952! - - # From U. S. Naval Observatory (1989-01-16): - # BRAZIL WEST 5 H BEHIND UTC TERRITORY OF ACRE - # BRAZIL WEST 4 H BEHIND UTC ACRE OCT 23, '88-FEB 11, - # BRAZIL '89 (ESTIMATED) - # BRAZIL CENTRAL 4 H BEHIND UTC MANAUS - # BRAZIL CENTRAL 3 H BEHIND UTC MANAUS OCT 23, '88-FEB 11, - # BRAZIL CENTRAL '89 (ESTIMATED) - # BRAZIL EAST 3 H BEHIND UTC COASTAL STATES, RIO, SAO - # BRAZIL EAST PAULO, BRASILIA - # BRAZIL EAST 2 H BEHIND UTC COASTAL STATES, RIO, SAO - # BRAZIL PAULO, BRASILIA OCT 23, - # BRAZIL '88-FEB 11, '89 - # BRAZIL (ESTIMATED) - # BRAZIL 2 H BEHIND UTC ATLANTIC ISLANDS, FERNANDO - # BRAZIL DE NORONHA - # BRAZIL 1 H BEHIND UTC OCT 23, '88-FEB 11, '89 - # BRAZIL (ESTIMATED) - # BRAZIL 3 H BEHIND UTC FOR MOST MAJOR AIRPORTS. - # From Paul Eggert <eggert(a)twinsun.com> (1993-11-18): # The mayor of Rio recently attempted to change the time zone rules # just in his city, in order to leave more summer time for the tourist trade. # The rule change lasted only part of the day; # the federal government refused to follow the city's rules, and business # was in a chaos, so the mayor backed down that afternoon. ! # Shanks claims Acre stopped observing DST after 1988 Feb 7, but it ! # could just be that his table ran out of room. We're extrapolating ! # about time zone changes after 1990 Feb 11. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Brazil 1931 only - Oct 3 11:00 1:00 D --- 193,247 ---- # "[America/Porto_Acre]" is for the Territory of Acre; # "[America/Noronha]" is for Fernando De Noronha. # From Paul Eggert <eggert(a)twinsun.com> (1993-11-18): # The mayor of Rio recently attempted to change the time zone rules # just in his city, in order to leave more summer time for the tourist trade. # The rule change lasted only part of the day; # the federal government refused to follow the city's rules, and business # was in a chaos, so the mayor backed down that afternoon. ! ! # From IATA SSIM (1996-02): ! # _Only_ the following states in BR1 observe DST: Rio Grande do Sul (RS), ! # Santa Catarina (SC), Parana (PR), Sao Paulo (SP), Rio de Janeiro (RJ), ! # Espirito Santo (ES), Minas Gerais (MG), Bahia (BA), Goias (GO), ! # Distrito Federal (DF), Tocantins (TO), Sergipe [SE] and Alagoas [AL]. ! # [The last three states are new to this issue of the IATA SSIM.] ! ! # From Gwillim Law (1996-10-07): ! # Geography, history (Tocantins was part of Goias until 1989), and other ! # sources of time zone information lead me to believe that AL, SE, and TO were ! # always in BR1, and so the only change was whether or not they observed DST.... ! # The earliest issue of the SSIM I have is 2/91. Each issue from then until ! # 9/95 says that DST is observed only in the ten states I quoted from 9/95, ! # along with Mato Grosso (MT) and Mato Grosso do Sul (MS), which are in BR2 ! # (UTC-4).... The other two time zones given for Brazil are BR3, which is ! # UTC-5, no DST, and applies only in the state of Acre (AC); and BR4, which is ! # UTC-2, and applies to Fernando de Noronha (formerly FN, but I believe it's ! # become part of the state of Pernambuco). The boundary between BR1 and BR2 ! # has never been clearly stated. They've simply been called East and West. ! # However, some conclusions can be drawn from another IATA manual: the Airline ! # Coding Directory, which lists close to 400 airports in Brazil. For each ! # airport it gives a time zone which is coded to the SSIM. From that ! # information, I'm led to conclude that the states of Amapa (AP), Ceara (CE), ! # Maranhao (MA), Paraiba (PR), Pernambuco (PE), Piaui (PI), and Rio Grande do ! # Norte (RN), and the eastern part of Para (PA) are all in BR1 without DST. ! ! # From Paul Eggert (1996-11-22): ! # Let's make the following assumptions: ! # ! # * All data in Shanks are correct through 1990. In particular, ! # Shanks was right when he said Acre stopped observing DST in mid-1988. ! # * Areas where Shanks reports DST up to 1990, but the IATA reports no DST ! # in 1995, stopped observing DST in mid-1990. ! # ! # Under these assumptions Brazil needs 7 entries to cover all the distinct ! # time zone histories since 1970: ! # ! # Noronha (UTC-2), Fortaleza (UTC-3), and Manaus (UTC-4) stopped observing DST ! # in mid-1990. ! # Maceio (UTC-3) stopped observing DST in mid-1990, but started again mid-1995. ! # Sao Paulo (UTC-3) and Cuiaba (UTC-4) always observed DST. ! # Porto Acre (UTC-5) stopped observing DST in mid-1988. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Brazil 1931 only - Oct 3 11:00 1:00 D *************** *** 185,205 **** Rule Brazil 1987 only - Feb 14 0:00 0 S Rule Brazil 1988 only - Feb 7 0:00 0 S Rule Brazil 1989 only - Jan 22 0:00 0 S ! Rule Brazil 1988 max - Oct Sun>=15 0:00 1:00 D ! Rule Brazil 1990 max - Feb Sun>=8 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Noronha -2:09:40 - LMT 1914 -2:00 - FST 1963 Dec 9 ! -2:00 Brazil F%sT Zone America/Sao_Paulo -3:06:28 - LMT 1914 -3:00 Brazil E%sT ! Zone America/Manaus -4:00:04 - LMT 1914 -4:00 - WST 1963 Dec 9 -4:00 Brazil W%sT # Rio_Branco is too ambiguous, since there's a Rio Branco in Uruguay too. Zone America/Porto_Acre -4:31:12 - LMT 1914 -5:00 - AST 1963 Dec 9 ! -5:00 Brazil A%sT # # Martin Vaz and Trinidade are like America/Noronha. --- 263,321 ---- Rule Brazil 1987 only - Feb 14 0:00 0 S Rule Brazil 1988 only - Feb 7 0:00 0 S Rule Brazil 1989 only - Jan 22 0:00 0 S ! Rule Brazil 1988 1989 - Oct Sun>=10 0:00 1:00 D ! Rule Brazil 1990 1991 - Feb Sun>=11 0:00 0 S ! Rule Brazil 1990 1992 - Oct Sun>=20 0:00 1:00 D ! Rule Brazil 1992 only - Feb 9 0:00 0 S ! Rule Brazil 1993 max - Oct Sun>=11 0:00 1:00 D ! Rule Brazil 1993 only - Jan 31 0:00 0 S ! Rule Brazil 1994 1995 - Feb Sun>=15 0:00 0 S ! Rule Brazil 1996 max - Feb Sun>=11 0:00 0 S ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] + # + # Fernando de Noronha Zone America/Noronha -2:09:40 - LMT 1914 -2:00 - FST 1963 Dec 9 ! -2:00 Brazil F%sT 1990 Jul ! -2:00 - FST ! # ! # Amapa, east Para, Maranhao, Piaui, Ceara, Rio Grande do Norte, Paraiba, ! # Pernambuco (except Fernando de Noronha) ! Zone America/Fortaleza -2:34:00 - LMT 1914 ! -3:00 - EST 1963 Dec 9 ! -3:00 Brazil E%sT 1990 Jul ! -3:00 - EST ! # ! # Alagoas, Sergipe, Tocantins ! Zone America/Maceio -2:22:52 - LMT 1914 ! -3:00 - EST 1963 Dec 9 ! -3:00 Brazil E%sT 1990 Jul ! -3:00 - EST 1995 Jul ! -3:00 Brazil E%sT ! # ! # Bahia, Goias, Distrito Federal, Minas Gerais, Espirito Santo, Rio de Janeiro, ! # Sao Paulo, Parana, Santa Catarina, Rio Grande do Sul Zone America/Sao_Paulo -3:06:28 - LMT 1914 -3:00 Brazil E%sT ! # ! # Mato Grosso, Mato Grosso do Sul ! Zone America/Cuiaba -3:44:20 - LMT 1914 -4:00 - WST 1963 Dec 9 -4:00 Brazil W%sT + # + # Roraima, west Para, Amazonas, Rondonia + Zone America/Manaus -4:00:04 - LMT 1914 + -4:00 - WST 1963 Dec 9 + -4:00 Brazil W%sT 1990 Jul + -4:00 - WST + # + # Acre # Rio_Branco is too ambiguous, since there's a Rio Branco in Uruguay too. Zone America/Porto_Acre -4:31:12 - LMT 1914 -5:00 - AST 1963 Dec 9 ! -5:00 Brazil A%sT 1988 Jul ! -5:00 - AST # # Martin Vaz and Trinidade are like America/Noronha. *************** *** 217,222 **** --- 333,340 ---- Rule Chile 1928 1932 - Apr 1 0:00 0 - Rule Chile 1969 max - Oct Sun>=9 0:00 1:00 S Rule Chile 1970 max - Mar Sun>=9 0:00 0 - + # IATA SSIM anomalies: (1990-09) says 1990-09-16; (1992-02) says 1992-03-14; + # (1996-09) says 1998-03-08. Ignore these for now. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santiago -4:42:40 - LMT 1890 -4:42:40 - SMT 1910 # Santiago Mean Time *************** *** 233,242 **** # Colombia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:20 - LMT 1884 Mar 13 -4:56:20 - BMT 1914 Nov 23 # Bogota Mean Time ! -5:00 - COT # Colombia Time # Malpelo, Providencia, San Andres # no information; probably like America/Bogota --- 351,363 ---- # Colombia + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule CO 1992 only - May 2 0:00 1:00 S + Rule CO 1992 only - Dec 31 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:20 - LMT 1884 Mar 13 -4:56:20 - BMT 1914 Nov 23 # Bogota Mean Time ! -5:00 CO CO%sT # Colombia Time # Malpelo, Providencia, San Andres # no information; probably like America/Bogota *************** *** 265,272 **** Rule Falk 1983 only - Sep lastSun 0:00 1:00 S Rule Falk 1984 1985 - Apr lastSun 0:00 0 - Rule Falk 1984 only - Sep 16 0:00 1:00 S ! Rule Falk 1985 max - Sep Sun>=9 0:00 1:00 S Rule Falk 1986 max - Apr Sun>=16 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 -3:51:24 - SMT 1912 Mar 12 # Stanley Mean Time --- 386,394 ---- Rule Falk 1983 only - Sep lastSun 0:00 1:00 S Rule Falk 1984 1985 - Apr lastSun 0:00 0 - Rule Falk 1984 only - Sep 16 0:00 1:00 S ! Rule Falk 1985 1995 - Sep Sun>=9 0:00 1:00 S Rule Falk 1986 max - Apr Sun>=16 0:00 0 - + Rule Falk 1996 max - Sep Sun>=8 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 -3:51:24 - SMT 1912 Mar 12 # Stanley Mean Time *************** *** 285,292 **** Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown -3:45 - GBGT 1966 May 26 # Br Guiana Time -3:45 - GYT 1975 Jul 31 # Guyana Time ! -3:00 - GYT ! # Paraguay --- 407,415 ---- Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown -3:45 - GBGT 1966 May 26 # Br Guiana Time -3:45 - GYT 1975 Jul 31 # Guyana Time ! -3:00 - GYT 1991 ! # IATA SSIM (1996-06) says -4:00. Assume a 1991 switch. ! -4:00 - GYT # Paraguay *************** *** 303,312 **** Rule Para 1975 1978 - Oct 1 0:00 1:00 S Rule Para 1975 1978 - Mar 1 0:00 0 - # Shanks says 1979 was all DST. ! Rule Para 1980 max - Apr 1 0:00 0 - Rule Para 1980 1988 - Oct 1 0:00 1:00 S Rule Para 1989 only - Oct 22 0:00 1:00 S ! Rule Para 1990 max - Oct 1 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 -3:50:40 - AMT 1931 Oct 10 # Asuncion Mean Time --- 426,442 ---- Rule Para 1975 1978 - Oct 1 0:00 1:00 S Rule Para 1975 1978 - Mar 1 0:00 0 - # Shanks says 1979 was all DST. ! Rule Para 1980 1991 - Apr 1 0:00 0 - Rule Para 1980 1988 - Oct 1 0:00 1:00 S Rule Para 1989 only - Oct 22 0:00 1:00 S ! Rule Para 1990 only - Oct 1 0:00 1:00 S ! Rule Para 1991 only - Oct 6 0:00 1:00 S ! Rule Para 1992 only - Mar 1 0:00 0 - ! Rule Para 1992 only - Oct 5 0:00 1:00 S ! Rule Para 1993 only - Mar 31 0:00 0 - ! Rule Para 1993 max - Oct 1 0:00 1:00 S ! Rule Para 1994 1995 - Feb lastSun 0:00 0 - ! Rule Para 1996 max - Mar 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 -3:50:40 - AMT 1931 Oct 10 # Asuncion Mean Time *************** *** 324,329 **** --- 454,461 ---- Rule Peru 1987 only - Apr 1 0:00 0 - Rule Peru 1990 only - Jan 1 0:00 1:00 S Rule Peru 1990 only - Apr 1 0:00 0 - + Rule Peru 1993 only - Jan 1 0:00 1:00 S + Rule Peru 1993 only - Apr 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Lima -5:08:12 - LMT 1890 -5:09 - LMT 1908 Jul 28 # Lima Mean Time *************** *** 396,402 **** Rule Uruguay 1988 only - Dec 11 0:00 1:00 S Rule Uruguay 1989 only - Mar 12 0:00 0 - Rule Uruguay 1989 only - Oct 29 0:00 1:00 S ! Rule Uruguay 1990 only - Mar 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 -3:44:44 - MMT 1920 May 1 # Montevideo MT --- 528,537 ---- Rule Uruguay 1988 only - Dec 11 0:00 1:00 S Rule Uruguay 1989 only - Mar 12 0:00 0 - Rule Uruguay 1989 only - Oct 29 0:00 1:00 S ! Rule Uruguay 1990 1992 - Mar Sun>=1 0:00 0 - ! Rule Uruguay 1990 1991 - Oct Sun>=21 0:00 1:00 S ! Rule Uruguay 1992 1993 - Oct Sun>=15 0:00 1:00 S ! Rule Uruguay 1993 only - Feb 28 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 -3:44:44 - MMT 1920 May 1 # Montevideo MT =================================================================== RCS file: RCS/zone.tab,v retrieving revision 1.1 retrieving revision 1.2 diff -c -r1.1 -r1.2 *** zone.tab 1996/09/03 23:48:46 1.1 --- zone.tab 1996/11/22 19:42:05 1.2 *************** *** 31,39 **** AO -0848+01314 Africa/Luanda AQ -7750+16636 Antarctica/McMurdo McMurdo Station, Ross Island AQ -9000+00000 Antarctica/South_Pole Amundsen-Scott Station, South Pole ! AQ -6617+11031 Antarctica/Casey Casey Station, Bailey Peninsula AQ -6736+06253 Antarctica/Mawson Mawson Station, Holme Bay ! AR -3436-05827 America/Buenos_Aires AS -1416-17042 Pacific/Pago_Pago AT +4813+01620 Europe/Vienna AU -3133+15905 Australia/Lord_Howe Lord Howe Island --- 31,45 ---- AO -0848+01314 Africa/Luanda AQ -7750+16636 Antarctica/McMurdo McMurdo Station, Ross Island AQ -9000+00000 Antarctica/South_Pole Amundsen-Scott Station, South Pole ! AQ -6448-06406 Antarctica/Palmer Palmer Station, Anvers Island AQ -6736+06253 Antarctica/Mawson Mawson Station, Holme Bay ! AQ -6617+11031 Antarctica/Casey Casey Station, Bailey Peninsula ! AR -3436-05827 America/Buenos_Aires E Argentina (BA, DF, SC, TF) ! AR -3257-06040 America/Rosario NE Argentina (SF, ER, CN, MN, CC, FM, LP, CH) ! AR -3124-06411 America/Cordoba W Argentina (CB, SA, TM, LR, SJ, SL, NQ, RN) ! AR -2411-06518 America/Jujuy Jujuy (JY) ! AR -2828-06547 America/Catamarca Catamarca (CT) ! AR -3253-06849 America/Mendoza Mendoza (MZ) AS -1416-17042 Pacific/Pago_Pago AT +4813+01620 Europe/Vienna AU -3133+15905 Australia/Lord_Howe Lord Howe Island *************** *** 41,47 **** AU -3749+14458 Australia/Melbourne Victoria AU -3352+15113 Australia/Sydney New South Wales - most locations AU -3157+14127 Australia/Broken_Hill New South Wales - Broken Hill ! AU -2728+15302 Australia/Brisbane Queensland AU -3455+13835 Australia/Adelaide South Australia AU -1228+13050 Australia/Darwin Northern Territory AU -3157+11551 Australia/Perth Western Australia --- 47,54 ---- AU -3749+14458 Australia/Melbourne Victoria AU -3352+15113 Australia/Sydney New South Wales - most locations AU -3157+14127 Australia/Broken_Hill New South Wales - Broken Hill ! AU -2728+15302 Australia/Brisbane Queensland - most locations ! AU -2016+14900 Australia/Lindeman Queensland - Holiday Islands AU -3455+13835 Australia/Adelaide South Australia AU -1228+13050 Australia/Darwin Northern Territory AU -3157+11551 Australia/Perth Western Australia *************** *** 59,67 **** BM +3217-06446 Atlantic/Bermuda BN +0456+11455 Asia/Brunei BO -1630-06809 America/La_Paz ! BR -0351-03225 America/Noronha Atlantic islands ! BR -2332-04637 America/Sao_Paulo east Brazil ! BR -0308-06001 America/Manaus west Brazil BR -0934-06731 America/Porto_Acre Acre BS +2505-07721 America/Nassau BT +2728+08939 Asia/Thimbu --- 66,77 ---- BM +3217-06446 Atlantic/Bermuda BN +0456+11455 Asia/Brunei BO -1630-06809 America/La_Paz ! BR -0351-03225 America/Noronha Fernando de Noronha ! BR -0343-03830 America/Fortaleza NE Brazil (AP, east PA, MA, PI, CE, RN, PR, PE) ! BR -0940-03543 America/Maceio ENE Brazil (AL, SE, TO) ! BR -2332-04637 America/Sao_Paulo S & SE Brazil (BA, GO, DF, MG, ES, RJ, SP, PR, SC, RS) ! BR -1535-05605 America/Cuiaba SW Brazil (MT, MS) ! BR -0308-06001 America/Manaus NW Brazil (RR, west PA, AM, RO) BR -0934-06731 America/Porto_Acre Acre BS +2505-07721 America/Nassau BT +2728+08939 Asia/Thimbu *************** *** 69,76 **** BY +5354+02734 Europe/Minsk BZ +1730-08812 America/Belize CA +4734-05243 America/St_Johns Newfoundland Island ! CA +4439-06336 America/Halifax Atlantic Time - Nova Scotia (most locations), New Brunswick, Labrador & PEI CA +4612-05957 America/Glace_Bay Atlantic Time - Nova Scotia - places that did not observe DST 1966-1971 CA +6608-06544 America/Pangnirtung Atlantic Time - Northwest Territories CA +4531-07334 America/Montreal Eastern Time - Ontario & Quebec - most locations CA +4901-08816 America/Nipigon Eastern Time - Ontario & Quebec - places that did not observe DST 1967-1973 --- 79,87 ---- BY +5354+02734 Europe/Minsk BZ +1730-08812 America/Belize CA +4734-05243 America/St_Johns Newfoundland Island ! CA +4439-06336 America/Halifax Atlantic Time - Nova Scotia (most places), NB, W Labrador, E Quebec & PEI CA +4612-05957 America/Glace_Bay Atlantic Time - Nova Scotia - places that did not observe DST 1966-1971 + CA +5320-06025 America/Goose_Bay Atlantic Time - E Labrador CA +6608-06544 America/Pangnirtung Atlantic Time - Northwest Territories CA +4531-07334 America/Montreal Eastern Time - Ontario & Quebec - most locations CA +4901-08816 America/Nipigon Eastern Time - Ontario & Quebec - places that did not observe DST 1967-1973 *************** *** 189,195 **** KW +2920+04759 Asia/Kuwait KY +1918-08123 America/Cayman KZ +4315+07657 Asia/Alma-Ata east Kazakhstan ! KZ +5016+07302 Asia/Aktau west Kazakhstan LA +1758+10236 Asia/Vientiane LB +3353+03530 Asia/Beirut LC +1401-06100 America/St_Lucia --- 200,207 ---- KW +2920+04759 Asia/Kuwait KY +1918-08123 America/Cayman KZ +4315+07657 Asia/Alma-Ata east Kazakhstan ! KZ +5017+05710 Asia/Aqtobe central Kazakhstan ! KZ +4431+05016 Asia/Aqtau west Kazakhstan LA +1758+10236 Asia/Vientiane LB +3353+03530 Asia/Beirut LC +1401-06100 America/St_Lucia *************** *** 262,276 **** QA +2517+05132 Asia/Qatar RE -2052+05528 Indian/Reunion RO +4426+02606 Europe/Bucharest RU +5545+03735 Europe/Moscow Moscow+00 - west Russia ! RU +5312+05009 Europe/Kuybyshev Moscow+01 - Caspian Sea RU +5651+06036 Asia/Yekaterinburg Moscow+02 - Urals RU +5500+07324 Asia/Omsk Moscow+03 - west Siberia RU +5502+08255 Asia/Novosibirsk Moscow+03 - Novosibirsk RU +5601+09250 Asia/Krasnoyarsk Moscow+04 - Yenisei River ! RU +5216+10420 Asia/Irkutsk Moscow+05 - Irkutsk RU +6200+12940 Asia/Yakutsk Moscow+06 - Lena River ! RU +4310+13156 Asia/Vladivostok Moscow+07 - Vladivostok RU +5934+15048 Asia/Magadan Moscow+08 - Magadan & Sakhalin RU +5301+15839 Asia/Kamchatka Moscow+09 - Kamchatka RU +6445+17729 Asia/Anadyr Moscow+10 - Bering Sea --- 274,289 ---- QA +2517+05132 Asia/Qatar RE -2052+05528 Indian/Reunion RO +4426+02606 Europe/Bucharest + RU +5443+02030 Europe/Kaliningrad Moscow-01 - Kaliningrad RU +5545+03735 Europe/Moscow Moscow+00 - west Russia ! RU +5312+05009 Europe/Samara Moscow+01 - Caspian Sea RU +5651+06036 Asia/Yekaterinburg Moscow+02 - Urals RU +5500+07324 Asia/Omsk Moscow+03 - west Siberia RU +5502+08255 Asia/Novosibirsk Moscow+03 - Novosibirsk RU +5601+09250 Asia/Krasnoyarsk Moscow+04 - Yenisei River ! RU +5216+10420 Asia/Irkutsk Moscow+05 - Lake Baikal RU +6200+12940 Asia/Yakutsk Moscow+06 - Lena River ! RU +4310+13156 Asia/Vladivostok Moscow+07 - Amur River RU +5934+15048 Asia/Magadan Moscow+08 - Magadan & Sakhalin RU +5301+15839 Asia/Kamchatka Moscow+09 - Kamchatka RU +6445+17729 Asia/Anadyr Moscow+10 - Bering Sea

1 0

tzdata1996l - Russian rules and names (both) are very broken
by Андрей Чернов Nov. 20, 1996

Nov. 20, 1996

1) It seems you forget to reflect recent official Moscow timezone rule change (Sep->Oct), I already send you update long time ago and you tell me that it is commited. 2) I still see MOST cruft, instead of commonly used MSK/MSD... I remember you agree to change those names back to MSK/MSD, but nothing happens too. Please fix this two problems and upload new tzdata1996m as soon as possible stop incoming chaos with Russian zone. It already hits: as first example wrong europe file was just commited to FreeBSD distribution. -- Andrey A. Chernov <ache(a)nagual.ru> http://www.nagual.ru/~ache/

2 1

Addition to Microsoft.au time thread
by Chris Carrier Nov. 18, 1996

Nov. 18, 1996

If you think Microsoft's time bug is funny, here is a real-space time zone situation I find even funnier. At the South Pole, day and night each last for six months; sunrise is at the September equinox, sunset at the March equinox, and the time of day in any zone is meaningless. However, the South Pole uses daylight saving time from the first Sunday in October to the third Sunday in March! The reason they do this is because they want to stay on the same time as McMurdo Sound, which uses DST, and the reason McMurdo uses DST is because they want to be on the same time as New Zealand, which uses DST (NZDST=GMT+13:00) on the abovementioned dates. Now that's funny!

1 0

DST and OS software
by Chris Carrier Nov. 17, 1996

Nov. 17, 1996

Which is why daylight saving time rules should NOT be incorporated into OS software -- because they continually change. I am wondering how many computers in the European Union (except UK/Ireland) went back to standard time September 29 when the EU didn't fall back until October 27, the former date being programmed into them when the code was written because the last Sunday in September was the rule then.

1 0

Only Microsoft could come up with this one...
by Monty Solomon Nov. 17, 1996

Nov. 17, 1996

Begin forwarded message: Newsgroups: rec.humor.funny From: GeraghtyR(a)scrha.health.qld.gov.au (Geraghty Rob) Subject: Only Microsoft could come up with this one... Keywords: chuckle, computers Approved: funny-request(a)clari.net Date: Sat, 16 Nov 96 4:30:02 EST Lines: 26 Just the other day, the eastern Australian States of New South Wales and Victoria went over to Daylight Saving time. Queensland did not. Windows 95 regards all three as being in one time zone. Consequently, all our email and schedule appointments have gone haywire, because Exchange is adjusting for a daylight saving difference we don't have. (please note that Queensland has only had daylight saving for one summer - about three years ago) I phoned Microsoft to ask whether they planned to fix the bug, but they told me: "It's not a bug." "Why not?" "Because Queensland had daylight saving when we wrote the code." -- Selected by Jim Griffith. MAIL your joke to funny(a)clari.net. Attribute the joke's source if at all possible. A Daemon will auto-reply. Remember: Always give your jokes a descriptive "Subject:" line. Don't use "joke" or "submission" or "joke submission," please. For the full submission guidelines, see http://comedy.clari.net/rhf/

1 0

tzcode1996m.tar.gz and tzdata1996l.tar.gz
by ado Nov. 5, 1996

Nov. 5, 1996

The files ftp://elsie.nci.nih.gov/pub/tzcode1996m.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata1996l.tar.gz are now available. No functional changes here; the files have simply been changed to make more use of ISO style dates in comments. The names of the above files now include the year in full. --ado

1 0

Re: Clock change orgy of 1996-10-27
by Peter Ilieve Nov. 2, 1996

Nov. 2, 1996

On Nov 2, 4:43am, Chris Carrier wrote: > [I wrote:] > >At least we are making progress here on the cooperation front, > >at least until the French upset things by suggesting they would scrap > >the whole idea. > > What is the status on that? I don't really know at present. There was a report in the Independent (a UK `quality' paper which is unfortunately only available on the Internet via AOL, and possibly only European AOL at that) on 25 October that at least acknowledged that France would have to consult with the rest of the EU about it. It said that `Paris would ask Brussels' meaning ask the EC Commission to be exempted from the Summer Time Directive as soon as possible, either next year or 1998. If it goes into 1998 it will be the eighth Directive which is not yet finalised. I have asked my usual contact at the Commission's Edinburgh office but she can't say much about the state of this new Directive. The Commission has produced a proposal which continues the current rules for 1998--2001. It is now the Council of Ministers' turn to reach a common postion, and then approve that as a Directive. They haven't shown much inclination so far and my contact points out that she can only speak for the Commission, not the Council. The new Directive is supposed to be approved by 1 Jan 97 but I think that is vanishingly unlikely even without this new French move. The Independent report said: `After three months of discussion and two parliamentary reports, it is clear that France intends to rid itself of a device that its experts say no longer saves fuel or manpower, upsets farmers, reduces milk yields by almost one-third and disrupts children's body-clocks.' Polls show 70% of people against changing the clocks, but an even split on the question of which time to use all the year round. Farmers and families with children favour permanent summer time (UTC+2), business and transport organisations favour winter time (UTC+1). The French Senate said winter time would be a good compromise with the rest of the EU, obviously assuming it continues to change its clocks, as France would have the same time as the UK in the Summer and the same as Germany in the winter. Can any French reader of this list give any references to the two official reports, possibly even a quick summary? Don't be too surprised about the importance given to milk yields. Cattle are an important determinant of EU policy, as witnessed by the current BSE row. :-) Peter Ilieve peter(a)aldie.co.uk

1 0

Clock change orgy of 1996-10-27
by Chris Carrier Nov. 2, 1996

Nov. 2, 1996

More thoughts on the clock change orgy of 1996-10-27: >"Rob Jones 4-6597 MR Sys" > INTERNET:jones@mr.med.ge.com wrote: >Anyone willing to venture a guess as to the number of clocks involved ? >(including uwaves, vcrs, etc...) 11 clocks at my home, but only 3 people. In terms of number of people, the 1996-10-27 fall back probably was about equal to 1991-09-15, when China changed its clocks last; however, in terms of clocks changed, the 1996-10-27 event clearly set an all-time record given the higher development level and more consumer goods available in the US and EU; in my household there were five timing devices to be changed per person, and I imagine in China it would probably be closer to one device per five persons. Valery Aronov > INTERNET:valery@ind.tansu.com.au wrote: >My own personal view is that we all should move the start of the workday >and settings of our alarm-clocks if people really want to save energy or >to wake up with sun. No clock adjustment at all. The only inconvinience >I could imagine: two sets of working hours for offices - a summer set and >a winter set. So a DST adjustment will mean switching from one set to >another. Much less problems then now I think. Do you know if this >suggestion was ever considered? I would be very much in favor of this. One interesting thing in our office is that we have flextime and management is trying to get rid of it and to have everyone work 8-17. Most people's day begins around 7:45, and I would say about 15% of the office is on the equivalent of "Daylight Extra" with a workday beginning at 7. We have one woman who works 6-15 and who therefore could be considered on "Double Daylight Extra." I also have an interesting story about my former office, in Sacramento, the capital of California. When I worked there a decade ago, we had people in the office from 7:00 to 20:00. Full time employees were allowed to choose when they could come into work provided they worked an 8 hours within those limits. Sacramento is located in a valley in which summer days are VERY hot (average 35c and it's gone as high as 44c) but nights are quite pleasant, with an overnight low of 15c. I reacted to this by going on what might be called "Darkness Extra"; during the months when DST was in effect I set my work hours for 11:00-19:45, the equivalent of two hours of *reverse* DST to let me enjoy the cooler evenings. Alas, eventually the office went back to normal hours (first people in at 7:00; last out by 17:45) and I had to as well. Peter Hullah > INTERNET:Peter.Hullah@eurocontrol.fr wrote: >Isn't it about time the world came to realise that we don't live by the >sun anymore and that spreading our sunlight more-or-less evenly around >noon no longer has any sense? Strongly disagree; if you work an 8 hour day on a day shift, half of it usually is before noon so the work day starts at 8 which makes the average wakeup time on workdays between 6 and 7, which is when the sun ought to rise. In June, therefore, DST makes sense and in October it does not. >I reckon everyone should add two hours >to their current standard time and stick to it all year round. I've always believed that what can be done an hour before sunrise is much pleasanter to do an hour after sunrise. >In answer to those who say "Just get up and go to bed two hours earlier" >we all live in a community, and one family stepping out of line two >hours is not on. Actually I have heard of a few cases of families with pre-school children where the sole/or both adults work the night shift and the kids follow suit, although this has to change when the kids go to school. Garrett Wollman > INTERNET:wollman@lcs.mit.edu wrote: >...in a city like Boston ...retail sales in the major pedestrian >districts and downtown areas drops off about 25% when the sunset is >moved from 5:45 (after work) to 4:45 (before work lets out). I wonder how much of that activity is transferred to the lunch period, breaks, or before work? Probably most of it. >As far as I'm concerned, we would be better off observing Atlantic time >year-round. Had Boston (and all of New England) not been near the largest city and capital of the US, it might have. Consider there are many cities (Cincinnati, Louisville, Chatannooga, Tallahassee) which astronomically belong in the Central zone observe Eastern time, and large areas are on Central time when they astronomically belong on Mountain (most of the six states in a north- south row between North Dakota and Texas). Alex Livingston >INTERNET:alex@agsm.unsw.edu.au wrote: >Reply to: Re: did the Holiday Is observe DST after the rest of Queensland >stopped? >Australia's vying powers-that-be unfortunately have a very childish, >ingnorant and it seems almost purely politically motivated approach to >daylight saving. I have never tried to get to the bottom of how the dates >for the clock changes were chosen but they are *particularly* bad choices. >The switch made recently by the south-eastern mainland of the country comes >at a time when the sun is rising only about 20 minutes later in the day (in >absolute terms) than the earliest it ever rises, but about 2 hours earlier >than the latest it ever rises. This means that the earliest sunrise of the >year (in clock terms) occurs the day before clocks are advanced. Just like most places in the United States before 1987 when almost nobody sprang forward before the last Sunday in April, wartime and 1974-5 excepted. >On the other hand, when the switch back to so-called standard time occurs at >the end of March, the sun is rising about 1 hour and 20 minutes later (in >absolute terms) than the earliest sunrise of the year and only about an >hour earlier than the latest... I've always thought the logical time to begin and end DST was at some time near the equinox when the sun is at least 1 hour earlier than the latest it does by standard time, and at least 1 hour later than the earliest it does by daylight time. DST should not be used short of an emergency during the time near winter solstice when the sun is rising <1 hour earlier than the latest it ever does by standard time, and if there is <2 hours between the earliest and latest sunrise, you don't have enough daylight to save to warrant DST! Peter Ilieve > INTERNET:peter@aldie.co.uk wrote on the subject: did the Holiday Is observe DST after the rest of Queenslan stopped? >Of my trio of islands, Eigg and Canna are also privately owned (I don't >know about Muck). I fail to see why owning land that is bounded by sea >rather than land bounded by a more normal fence makes the owners any less >subject to the Summer Time Act 1972 than I am. >Don't you have laws in Australia? :-) Setting up private and extra-legal times has a long history in the US. I remember Block Island, RI, went on DST in November 1973 two weeks after they fell back. I know people who were in Indiana in the 1950s-60s who remember the post office being an hour ahead or behind of the rest of town, an unincorporated area of a county being on a different time than a county seat, and so on. When the Uniform Time Act of 1966 was passed, Indiana passed a law requiring one clock in each public building to observe UTAT and marked "Official Time" so localities could go about their merry way. >People seem reluctant to give up summer time, >as shown by popular support in the rest of Europe for changing from >September to October, but don't seem to think of demanding an earlier >start. I wonder if anyone took a poll on the popularity of summer time in the last week in October 1996, when Europe was actually on summer time, as opposed to earlier polls showing majorities in favor. >At least we are making progress here on the cooperation front, >at least until the French upset things by suggesting they would scrap >the whole idea. What is the status on that? Actually the situation in France (and Spain) is that they are already on year round daylight time since their 'standard' is GMT+1 instead of the GMT zone that (nearly all of) France and Spain are astronomically in. When they talk about 'summer time' what they really mean is DOUBLE summer time. It should be noted when the UK was on double DST during WW2 it always ended the second weekend in August or earlier except in 1944, and even then it ran only to mid-September. I can see objections to DDST on October 26th having more than a little merit.

1 0

Re: did the Holiday Is observe DST after the rest of Queensland stopped?
by Nathan Myers Nov. 1, 1996

Nov. 1, 1996

> [Somebodies] unfortunately have a very childish, > ingnorant and it seems almost purely politically motivated approach to > daylight saving. ... But I digress... Daylight saving has always been a purely political phenomenon, an attempt to legislate reality. (Consider observance of summer time in tropical countries!) It is, and always will be, subject to all the foolishness that any purely political abstraction is. Tracking that foolishness in software is as thankless as it is necessary. Nathan Myers ncm@@cantrip.com

1 0

Re: did the Holiday Is observe DST after the rest of Queensland stopped?
by peter＠aldie.co.uk Nov. 1, 1996

Nov. 1, 1996

> >I know I am a long way away from the scene of the action, but from looking > >at the map this looks about as likely as Eigg, Muck or Canna > >having different DST rules from the rest of the UK; ie. not very. :-) > > > >My Times Concise Atlas lists Hayman and Lindeman as being on either > >side of Whitsunday Island. My Britannica Atlas doesn't list either > >but gives 20.17S 148.59E for Whitsunday. Neither has any trace of > >Hamilton. > > I have actually *been* to Hamilton Island, and a close friend of mine > recently had a holiday on Hayman Island. The three islands are probably > owned entirely by holiday (that's "vacation" to you North Americans) > operators and probably made autonomous decisions as to what time to keep on > their properties. I have heard or read more than once that some resort > islands off the coast of Queensland chose to keep observing daylight-saving > time even after Queensland ceased to. It seems that no only does each state > decide independantly if and when to observe daylight saving, but > commercially run holiday resorts can also do it their way. And then there's > Lord Howe Island (what a disaster!). I have reason to doubt, by the way, > that "Holiday Islands" is an officially gazetted name: it's not one I'm > familiar with; as far as I'm aware, all these islands are part of the > Whitsunday Islands group. Of my trio of islands, Eigg and Canna are also privately owned (I don't know about Muck). I fail to see why owning land that is bounded by sea rather than land bounded by a more normal fence makes the owners any less subject to the Summer Time Act 1972 than I am. Don't you have laws in Australia? :-) Seriously, should the tz database document legal time, or should it also document other sorts of `custom and practice' time? If the latter I'm sure I can promulgate an Aldie time to be observed on my patch that would break something in the existing code. :-) Another nearby island, Rum (Rhum if you believe the Ordnance Survey) is also owned by a single organisation and is largely given over to research into Red Deer. Maybe I should suggest to Scottish Natural Heritage that their scientific work justifies keeping UTC all year round. > Australia's vying powers-that-be unfortunately have a very childish, > ingnorant and it seems almost purely politically motivated approach to > daylight saving. ... But I digress... We have the same thing. People seem reluctant to give up summer time, as shown by popular support in the rest of Europe for changing from September to October, but don't seem to think of demanding an earlier start. At least we are making progress here on the cooperation front, at least until the French upset things by suggesting they would scrap the whole idea. Peter Ilieve peter(a)aldie.co.uk

2 1

Moscow DST correction
by Андрей Чернов Nov. 1, 1996

Nov. 1, 1996

Diffs related to europe 7.38 *** europe.orig Thu Jul 18 00:54:30 1996 --- europe Sun Sep 29 19:20:56 1996 *************** *** 852,858 **** Rule Russia 1921 only - Oct 1 0:00 0 K Rule Russia 1981 1984 - Apr 1 0:00 1:00 D Rule Russia 1981 1983 - Oct 1 0:00 0 K ! Rule Russia 1984 max - Sep lastSun 2:00s 0 K Rule Russia 1985 max - Mar lastSun 2:00s 1:00 D # These are for backward compatibility with older versions. --- 852,859 ---- Rule Russia 1921 only - Oct 1 0:00 0 K Rule Russia 1981 1984 - Apr 1 0:00 1:00 D Rule Russia 1981 1983 - Oct 1 0:00 0 K ! Rule Russia 1984 1995 - Sep lastSun 2:00s 0 K ! Rule Russia 1996 max - Oct lastSun 2:00s 0 K Rule Russia 1985 max - Mar lastSun 2:00s 1:00 D # These are for backward compatibility with older versions. -- Andrey A. Chernov <ache(a)nagual.ru> http://www.nagual.ru/~ache/

6 17

Re: did the Holiday Is observe DST after the rest of Queensland stopped?
by alex＠agsm.unsw.edu.au Nov. 1, 1996

Nov. 1, 1996

>> According to the current tz database, Queensland stopped observing DST >> after summer 1991/1992. But the IATA SSIM (which I'm currently >> slogging through, thanks to Gwillim Law) says that the Holiday Islands >> (Hayman, Lindeman, Hamilton) observed DST through 1993/1994. Does >> anyone know the true story here? > >I know I am a long way away from the scene of the action, but from looking >at the map this looks about as likely as Eigg, Muck or Canna >having different DST rules from the rest of the UK; ie. not very. :-) > >My Times Concise Atlas lists Hayman and Lindeman as being on either >side of Whitsunday Island. My Britannica Atlas doesn't list either >but gives 20.17S 148.59E for Whitsunday. Neither has any trace of >Hamilton. I have actually *been* to Hamilton Island, and a close friend of mine recently had a holiday on Hayman Island. The three islands are probably owned entirely by holiday (that's "vacation" to you North Americans) operators and probably made autonomous decisions as to what time to keep on their properties. I have heard or read more than once that some resort islands off the coast of Queensland chose to keep observing daylight-saving time even after Queensland ceased to. It seems that no only does each state decide independantly if and when to observe daylight saving, but commercially run holiday resorts can also do it their way. And then there's Lord Howe Island (what a disaster!). I have reason to doubt, by the way, that "Holiday Islands" is an officially gazetted name: it's not one I'm familiar with; as far as I'm aware, all these islands are part of the Whitsunday Islands group. Australia's vying powers-that-be unfortunately have a very childish, ingnorant and it seems almost purely politically motivated approach to daylight saving. I have never tried to get to the bottom of how the dates for the clock changes were chosen but they are *particularly* bad choices. The switch made recently by the south-eastern mainland of the country comes at a time when the sun is rising only about 20 minutes later in the day (in absolute terms) than the earliest it ever rises, but about 2 hours earlier than the latest it ever rises. This means that the earliest sunrise of the year (in clock terms) occurs the day before clocks are advanced. On the other hand, when the switch back to so-called standard time occurs at the end of March, the sun is rising about 1 hour and 20 minutes later (in absolute terms) than the earliest sunrise of the year and only about an hour earlier than the latest. (The figures quoted apply roughly to the latitude of Adelaide or Sydney but will not differ hugely within the range of latitudes where daylight saving is now observed in Australia.) If the populace can live with the sun rising as late at it does at the end of the daylight-saving period then it should surely be happy to live with it at the beginning as well, in which case it could be started a full 7 weeks earlier (around September 9). And in all of this the possibility of coordinating with other southern-hemisphere countries which also observe daylight saving (even neighbours like New Zealand and Vanuatu) doesn't seem to have flickered into any law-maker's consciousness. (That would involve acknowledging that someone else thought of daylight saving first and rob them of the kudos of coming up with such a great "original" idea.) After all, even the states can't coordinate. But I digress... _______________ Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 9313-7279 Telephone: +61 2 9931-9264

1 0

Re: did the Holiday Is observe DST after the rest of Queensland stopped?
by Peter Ilieve Oct. 31, 1996

Oct. 31, 1996

> According to the current tz database, Queensland stopped observing DST > after summer 1991/1992. But the IATA SSIM (which I'm currently > slogging through, thanks to Gwillim Law) says that the Holiday Islands > (Hayman, Lindeman, Hamilton) observed DST through 1993/1994. Does > anyone know the true story here? I know I am a long way away from the scene of the action, but from looking at the map this looks about as likely as Eigg, Muck or Canna having different DST rules from the rest of the UK; ie. not very. :-) My Times Concise Atlas lists Hayman and Lindeman as being on either side of Whitsunday Island. My Britannica Atlas doesn't list either but gives 20.17S 148.59E for Whitsunday. Neither has any trace of Hamilton. The whole of that coastline is peppered with islands just off the coast. Peter Ilieve peter(a)aldie.co.uk

1 0

did the Holiday Is observe DST after the rest of Queensland stopped?
by Paul Eggert Oct. 31, 1996

Oct. 31, 1996

According to the current tz database, Queensland stopped observing DST after summer 1991/1992. But the IATA SSIM (which I'm currently slogging through, thanks to Gwillim Law) says that the Holiday Islands (Hayman, Lindeman, Hamilton) observed DST through 1993/1994. Does anyone know the true story here? If the IATA is right, we'll need a new entry Australia/Hamilton to handle the anomaly. I know that those islands exist (they're mentioned in <URL:http://www.lonelyplanet.com/dest/aust/gbreef.htm>, which says Hamilton has the most people) but none of them are in my Rand McNally Goode's World Atlas or in Shanks's International Atlas, so I'll need further info to find Hamilton's latitude and longitude.

1 0

Re: Clock change orgy of 1996-10-27
by Rob Jones 4-6597 MR Sys Oct. 30, 1996

Oct. 30, 1996

Anyone willing to venture a guess as to the number of clocks involved ? (including uwaves, vcrs, etc...) 11 clocks at my home, but only 3 people. -- Rob Jones On Oct 30, 12:13am, Chris Carrier wrote: > Subject: Clock change orgy of 1996-10-27 > On 1996-10-28 05:04 GMT I posted: > > more people changed time today, 1996 October 27, than on any other date > in history. > > To which Paul Eggert commented: > > >Could be. 1991-09-15 is another candidate; it's the last time that > >China changed its clocks. > > Good point. The magnitude of the clock changing orgy, in terms of number of > people, would have been about the same. Speaking in very broad general terms, > the population of the US (ex. eastern IN, HI, and AZ) is about 250 million, > Mexico 100 million, EU 350 million, Russia 150 million, totalling 850 million, > plus or minus 100 M. The population of China is somewhere in the range of > 1100-1200 million, so it would take another 300 million people, in non-EU > Europe and the Central Asian republics of the CIS, changing time on 1996 > October 27 to exceed the Chinese 1991 record. Sounds like a close thing. > > I furthermore posted an: > > Editorial comment on the above: it should have been on the last Sunday in > September not October! >

1 0

Clock change orgy of 1996-10-27
by Chris Carrier Oct. 30, 1996

Oct. 30, 1996

On 1996-10-28 05:04 GMT I posted: more people changed time today, 1996 October 27, than on any other date in history. To which Paul Eggert commented: >Could be. 1991-09-15 is another candidate; it's the last time that >China changed its clocks. Good point. The magnitude of the clock changing orgy, in terms of number of people, would have been about the same. Speaking in very broad general terms, the population of the US (ex. eastern IN, HI, and AZ) is about 250 million, Mexico 100 million, EU 350 million, Russia 150 million, totalling 850 million, plus or minus 100 M. The population of China is somewhere in the range of 1100-1200 million, so it would take another 300 million people, in non-EU Europe and the Central Asian republics of the CIS, changing time on 1996 October 27 to exceed the Chinese 1991 record. Sounds like a close thing. I furthermore posted an: Editorial comment on the above: it should have been on the last Sunday in September not October! To which jhuggins(a)comsys-inc.com wanted to know: >I am a rather new subscriber to this newsgroup. Could you explain your >editorial remark about September versus October. I believe DST should end at the end of September because in October (in the North Temperate Zone, where most but not all of the people on this list live) there is simply not enough daylight in the morning when DST is used. The following examples for sunrise on the last day of DST this year (October 26) in certain parts of the United States are used for illustration: Dallas, TX = 7:45 Seattle, WA = 7:45 Oklahoma City = 7:46 Atlanta, GA = 7:51 Salt Lake City = 7:51 Russell, KS = 7:55 Cincinnati = 8:00 Midland, TX = 8:00 N. Platte, NE = 8:06 Louisville, KY = 8:02 Boise, ID = 8:12 Kalispell, MT = 8:13 Marquette, MI = 8:22 Williston, ND = 8:30 And since the Europeans and Russians have adopted our bad habit: Bonn.de = 8:12 Dublin.ie = 8:11 London.uk = 7:42 Madrid.es = 8:37 Moscow.ru = 8:22 Paris.fr = 8:27 St. Pete.ru = 9:04 Seville.es = 8:42 Going back on Standard Time on the last Sunday in September would make each of these sunrises an hour earlier; clearly a much better situation for public convenience and the safety of children on their way to school; in fact a DST ending of Labor Day (the American day, Mon => Sep 1) would serve schoolchildren even better. From: Garrett Wollman > INTERNET:wollman@lcs.mit.edu had a: >Comment on the editorial comment: who cares when the sun rises? Comment on the comment on the comment: Me, and anyone else who is sick and tired of getting up in the dark. Generally more DST is favored when it's not being used; I remember polls in December 1973 in the US in which a 3:1 majority was in favor of year-round DST. Then on 1974-01-06 we actually did go on DST and the 3:1 majority in favor quickly became a 3:1 majority against. The original advocates of DST did not favor DST in October. When Franklin semi-seriously suggested DST in the 18th century, he suggested that DST be used to advance the sunrise to when most people wake up. (He must have been thinking of city people; the majority lived on farms and woke up with the sun during his lifetime, whether sunrise was 3:00 or 9:00). When William Willett proposed it in 1905, he suggested advancing time 80m (20m on each of the first four Sundays) in April and ending it be turning the clock back 20m on each of the first four Sundays in SEPTEMBER, which would have meant reversion to standard time not later than September 28. My own personal view is that I don't really care (most of the time) if sunset is 14:00 or 23:59, I just want it light when I have to get up to go to work! Chris Carrier

2 1

Moscow time & public transit in CIS
by Chris Carrier Oct. 30, 1996

Oct. 30, 1996

According to a friend of mine who rode the Trans-Siberian Railroad from Moscow to Irkutsk in 1995, public air and rail transport in Russia after the USSR breakup still follows Moscow time, no matter where in Russia it is located; he mentioned getting off the train in Irkutsk at 03:00 railway time to see the sun up and people going to work at 08:00 local time, and when flying back having to wait an unexpected 5 hours in the airport for a plane which he thought was leaving on local time when it was really leaving on Moscow time. In those parts of the USSR which were in Europe and outside the Russian Federation, public transport runs on local time (which has a standard of GMT+2, moving back with Moscow in 1991 when they were still Soviet but staying on GMT+2 when Moscow standard time moved back to GMT on 1992-01-18, right after the breakup). Don't know what the Central Asian CIS republics are doing about transport time; anyone know? Chris Carrier

1 0

problem with tzcode96l
by Todd C. Miller Oct. 30, 1996

Oct. 30, 1996

Hi, we're trying to get OpenBSD to pass the NIST POSIX test suite and it tries to do a mktime() with TZ=dst0std,J057,J059 with a time of Tue Feb 26 01:59:59 1991 (which should return 667533600). mktime() from tzcode96l (and earlier versions) returns -1 with that TZ setting. There seems to be a problem with the end of daylight savings time specification. If you comment out the getrule() on line 751 it at least keeps mktime from returning -1 :-) I really don't understand the code in question. Any clues would be greatly appreciated. thanks, todd --- Todd C. Miller Sysadmin--University of Colorado Todd.Miller(a)cs.colorado.edu

2 7

Re: Non-EU Europe, record set today
by peter＠aldie.co.uk Oct. 29, 1996

Oct. 29, 1996

> I would like to ask: given that the European Union has extended summer time > until October 27, and that Russia did the same, can we assume that all > European countries that are *not* in the EU and those former republics of the > ex-Soviet Union that observed DST also delayed their ending date this year > until the end of October? No. Although it won't affect the overall numbers much, it appears that Latvia at least didn't take part in this historic mass orgy of clock changing. I was checking with a relative in Estonia about the IATA manual, which gives a different time of change for Estonia to that which he had told me before, and he said unprompted that he knew Latvia had changed on the last Sunday in September. On the IATA manual and its claim that Estonia changes at 23:00 UTC he said: `I do not [know] exactly but there are some little different (confusing) rules for International Air and Railway Transport Schedules conversion in Sunday connected with end of summer time in Estonia. Anyway Estonia will change 03:00 local time.' This may be a more general problem. Does this IATA manual specifically say that it gives times of change for civil time, or does it describe some special IATA rules? Peter Ilieve peter(a)aldie.co.uk

2 1

Non-EU Europe, record set today
by Chris Carrier Oct. 28, 1996

Oct. 28, 1996

I would like to ask: given that the European Union has extended summer time until October 27, and that Russia did the same, can we assume that all European countries that are *not* in the EU and those former republics of the ex-Soviet Union that observed DST also delayed their ending date this year until the end of October? Another thought. Given that most of the USA, Mexico, the EU and Russia all changed back on the same date, I believe that some sort of record was set today: more people changed time today, 1996 October 27, than on any other date in history. (The combined population of the four nations/unions mentioned above being in the range 800-900 million). Editorial comment on the above: it should have been on the last Sunday in September not October! Chris Carrier

2 1

Re: multithreading and timezones
by Nathan Myers Oct. 22, 1996

Oct. 22, 1996

Valery Aronov <valery(a)ind.tansu.com.au> wrote: > How is it possible to manage current zone information in MT-safe fashion? From: Paul Eggert <eggert(a)twinsun.com> > Write and use a thread-safe version of the tz library. > > This requires changing the interfaces to localtime, gmtime, tzset, etc. > (localtime_r is not enough.) One must also make the locale a > parameter, for strftime at least. And I'm afraid that this will > require going into the guts of the C library, which will make it hard > to do portably. > > On my (long) list of things to do is to make a thread-safe version of > the glibc version of the tz library. Once you know you're dealing > with that particular library, the job becomes tractable. The non-re-entrancy, and the globalness, of the time functions has long bothered me. With the C locale itself global, there's not much to be done about that. The (draft) standard C++ locale is not (necessarily) global, and supports user extensions such as time zone handling. Now would be a good time to start defining a standard time zone facet for the C++ locale, so that it can be made official at the next round, in a few years. The glibc locale functions being worked on by Ulrich Drepper are designed to support a re-entrant (C) interface. We should co-ordinate with him to get the time zone code integrated into his architecture. Please, let's get the interface right this time. Nathan Myers ncm(a)cantrip.org

1 0

Solaris multithreading and timezones
by Valery Aronov Oct. 22, 1996

Oct. 22, 1996

We are moving our software towards multithreading (SunOS 5.5.1). One of the many concerns is the MT-unsafety of tzset() function. It is said to be MT-unsafe in man pages. It is partly due to the keeping references to TZ in the environment variable, I guess. Our software needs to deal with more than one timezone in one process. The only way I know to implement it is to change the value of environment variable TZ and call tzset() every time I want to switch to a new timezone. External variables tzname and others also makes it problematic to maintain access to them: other vendors' software we are using might use their own policy of access. How is it possible to manage current zone information in MT-safe fashion? I would appreciate any help. Valery

3 3

c-common.c
by ado Oct. 18, 1996

Oct. 18, 1996

The file ftp://elsie.nci.nih.gov/pub/c-common.c is now available; this is a replacement for c-common.c in gcc (either 2.7.2 or 2.7.2.1) that does strftime format checking (with special warning for formats that generate two digits worth of years and thus may be especially subject to year 2000 challenges). If anyone has feedback before I ship it off to the GNU folk, I'd love it! --ado

3 3

[Karst Koymans: bin/1740: Setting TZ to unusual values c]
by Garrett Wollman Oct. 9, 1996

Oct. 9, 1996

I don't know whether this is a BSD-specific problem or exists in the current tzcode, but I figured I might forward it here in case it does. -GAWollman ------- start of forwarded message (RFC 934 encapsulation) ------- Message-Id: <199610082133.OAA28831(a)freefall.freebsd.org> X-Send-Pr-Version: www-1.0 X-Loop: FreeBSD.org Precedence: bulk From: Karst.Koymans(a)phil.ruu.nl Sender: owner-bugs(a)freebsd.org To: freebsd-gnats-submit(a)freebsd.org Subject: bin/1740: Setting TZ to unusual values crashes applications using localtime Date: Tue, 8 Oct 1996 14:33:13 -0700 (PDT) >Number: 1740 >Category: bin >Synopsis: Setting TZ to unusual values crashes applications using localtime >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 8 14:40:02 PDT 1996 >Last-Modified: >Originator: Karst Koymans >Organization: Utrecht University >Release: 960501 snapshot >Environment: >Description: Setting TZ to unusual values like "Europe" crashes all applications using the localtime routine. This is because the tzload routine happily opens any file, even directories, as valid timezone files. "Europe" happens to be a directory under /usr/share/zoneinfo. >How-To-Repeat: TZ=Europe date >Fix: >Audit-Trail: >Unformatted: ------- end -------

1 0

patch to zic.8 to document format of UNTIL field
by Paul Eggert Oct. 8, 1996

Oct. 8, 1996

From: "Rob Jones 4-6597 MR Sys" <jones(a)mr.med.ge.com> Date: Tue, 8 Oct 1996 12:23:18 -0500 In the tzdata files when the UNTIL field is just a year (without a month day) specified, does that mean up to and including that year, or just up to ? Somehow that didn't get documented. Here's a draft patch. In practice I use vague dates like `1967' when I don't know exactly when the rules changed, and a more precise time stamp like `1967 Jan 1 00:00' if I know that's the exact time -- even though both inputs mean the same thing to `zic'. =================================================================== RCS file: RCS/zic.8,v retrieving revision 1995.7 retrieving revision 1995.7.1.1 diff -c -r1995.7 -r1995.7.1.1 *** zic.8 1995/10/30 14:58:15 1995.7 --- zic.8 1996/10/08 18:31:38 1995.7.1.1 *************** *** 304,309 **** --- 304,312 ---- If this is specified, the time zone information is generated from the given GMT offset and rule change until the time specified. + The month, day, and time of day have the same format as the IN, ON, and AT + columns of a rule; trailing columns can be omitted, and default to the + earliest possible value for the missing columns. .IP The next line must be a .q continuation

1 0

Antarctic update
by Chris Carrier Oct. 8, 1996

Oct. 8, 1996

Ethan Dicks > INTERNET:erd@mcmsun5.mcmurdo.gov has informed me: >BTW, the data for the British Base Rothera is out of date. Last >year (1995) was the last winter-over season. It's now a summer only station.

1 0

Re: Recent changes to time zones reported by IATA
by Paul Eggert Oct. 6, 1996

Oct. 6, 1996

Date: Fri, 04 Oct 1996 19:34:39 -0500 (EST) From: Gwillim Law 919-852-4294 <LAW(a)encmail.encompass.com> I thought the tz mailing list would want to see these changes, and compare them to those reported by other sources. That is a very helpful contribution; thanks. I compared the IATA changes with the changes reported by other tz contributors, and have the following comments. Later, I'll send out a draft patch reflecting these comments, as well as all the other comments received so far. * Armenia stopped using DST this year, according to Edgar Der-Danieliantz <edd(a)AIC.NET> (1996-05-04). Did the IATA catch this change? * Azerbaijan data from the IATA disagrees with both Shanks and USNO. I guess that the IATA is right, and that we're missing some transitions between 1991 and 1996. Azerbaijan apparently enjoys the distinction of being the first Asian country to use the European Union's DST rules (including switching at 0100 UTC). * Brazil - You wrote: three states (Alagoas, Sergipe, and Tocantins) will begin using DST, probably on October 13, 1996. Could you give more details about this? The entries that you sent made it look like only the DST dates were adjusted. As far as I can tell from other sources, DST is observed uniformly in Brazil, even in the far north where the hemisphere is wrong. Perhaps these states used to be 2 hours behind UTC, and are now 3? This would agree with the map in <URL:http://www.bancobrasil.com.br/bbtur.ing/bbttime.htm>, but so far I've discounted that map, not only because no other sources have UTC-2 Brazilian mainland, but also because its line between UTC-2 and UTC-3 is suspiciously straight. Also, some of the beginning and end dates for DST were adjusted by a week. You gave the change only for BR1; were the dates also changed for other zones in Brazil? It would be odd if the different parts of Brazil had different DST dates. All the Brazilian transitions that we know of since 1989 are consistent with the rules Oct Sun>=10 00:00 and Feb Sun>=10 00:00; I'll propose a change to the tz rules accordingly. * Iran The tz database had Iran not using DST since 1980. For lack of better info I'll assume they readopted DST in 1996. Iran now apparently moves its clocks approximately on the equinoxes -- I think it's the only country to do this. * Kazakhstan - you wrote: Kazakhstan, formerly unified on UTC+6 with DST, will divide into three zones. They will observe UTC+4, 5, and 6, all with DST. The western zone (UTC+4) consists of Aktau, Atyrau, and Uralsk oblasts, and the central zone is Aktyubinsk oblast. Andrew Evtichov <evti(a)chevron.com> (1996-04-13) wrote that Kazakhstan has had multiple time zones for quite some time: at least 2 ``always'' and 3 now. I'd guess that the IATA SSIM is just catching up with this fact. Unfortunately, I misparsed his earlier message and thought that Kazakhstan had just 2 time zones now; he actually wrote that it has 3. I'll add a new zone for Aqtobe (formerly Aktyubinsk) and rename Asia/Aktau to Asia/Aqtau since `Aqtau' name seems to be the usual English rendering of the Kazakh name. * Lebanon. Lebanon returned from DST to Standard Time on September 28, 1996, instead of October 26 as previously announced. Shanks has Lebanon switching on May 1 and Oct 16 every year. Evidently that has changed more than once since 1991. For lack of better info I'll propose a patch so that Lebanon switches on the last Sunday in March and the last Sunday in September, starting 1996. * Libya if I'm right, the first actual time change was on September 30, 1996, when clocks were set back an hour. That sounds right: since 1959, Libya has switched back and forth between straight UTC+2 and UTC+1 with DST. * Mexico - the IATA and tz agree. * Mongolia The IATA says that changes occur at local midnight, whereas Shanks says they occur at 02:00 standard time. Also, the IATA says the fall transition is the 4th Friday (!) in October, whereas tz said it was the last Sunday in September. I'll assume that the IATA is right, and that the rules changed in 1996, but we're undoubtedly missing some other changes between 1985 and 1995. * Paraguay Paraguay will return from DST to Standard Time on March 1, 1997, instead of February 23 as previously announced. Shanks has this transition occuring on April 1. For lack of better info, I'll assume they changed the rules from April 1 to March 1 in 1996. * Portugal Portugal (excluding Azores and Madeira) has switched from UTC+1 to UTC (both using DST). There's no indication of when the change occurred. Martin Bruckmann <martin(a)ua.pt> (1996-02-29) reported that the change occurred this spring, by Portugal not changing its clocks. * Russia Russia's fall transition used to be the last Sunday in September, but it's changed to the last Sunday in October (at 02:00 standard time, as before). Did the IATA catch this change? Presumably this change also applies to Kazakhstan (I just checked the ricc.kz time server in Alma-Ata, and they're still on DST) as well as Kirgizstan. While we're on the subject, in the absence of any better info, the current tz database assumes that Belarus, Estonia, Latvia, Lithuania, and Moldova are moving their clocks on the last Sunday in October at 02:00 standard time, starting this year (in previous years they used September). Since the EU, Russia, and Ukraine are all known to be making a similar switch, it wouldn't be surprising if the other countries are switching too; but we have no info. * Sri Lanka Sri Lanka has changed from UTC+5:30 to UTC+6:30 year-round. There's no indication of when the change occurred. It occurred 1996-05-25 00:00 local time, according to LankaWeb <URL:http://www.virtual-pc.com/lankaweb/news/items/240596-2.html>. * Ukraine Ukraine will begin and end DST at 3:00 am local time, rather than midnight as it used to. (The data make it clear that this is 3:00 local standard time.) For most of Ukraine, this makes sense, since it's the EU rules. However, for Crimea, it doesn't make sense, since it's neither the EU rules (which operate at 4:00 local standard time) nor the Moscow rules (which operate at 2:00 local standard time). Apparently the Ukrainians and the Crimeans are having a little tussle; there was a news story about this by Itar-Tass <URL:http://www.itar-tass.com/tassnews.htm> at 09-18 00:43 entitled ``Crimea ponders over problem of time zone'' but unfortunately I don't have a copy of the story. For now I'll assume Crimea was using Moscow rules until this year, and is as IATA reports afterwards. Shanks says all of Ukraine switches at 2:00 standard time, not midnight. For lack of better info I'll assume that this was true through 1995.

1 0

Spring Forward, Fall Back -- but not just yet
by Monty Solomon Oct. 6, 1996

Oct. 6, 1996

Excerpt from RISKS DIGEST 18.50 ------------------------------ Date: Tue, 1 Oct 1996 12:02:10 +0200 From: minow(a)apple.com Subject: Spring Forward, Fall Back -- but not just yet The biannual daylight savings time confusion began this weekend in Sweden. When Sweden joined the EU (Common Market), it changed the fall changeover from the last weekend in September to the last weekend in October to conform with the rest of Europe. Unfortunately, a few hundred thousand Windows '95 machines were not informed of the changeover and, followed pre-programmed instructions, switched on the old schedule. This is, of course, one small example of a much more difficult problem: there is no obvious way to pre-program daylight savings time changeover in a way that is sufficiently robust to withstand government intervention. (My favorite example is Arizona, where federal land changes, but state land remains on mountain standard time year around.) Martin Minow minow(a)apple.com ------------------------------

1 0

Antarctic Time
by erd＠mcmsun5.mcmurdo.gov Oct. 6, 1996

Oct. 6, 1996

Howdy all, Ethan Dicks here. I'm a computer tech at McMurdo Station who has been sleuthing why my clock on my OpenWin desktop didn't display the correct local time this morning (N.Z. just changed to DST about 20 hours ago), and dug up this mailing list from the docs in the zoneinfo source. It appears as if I've just missed most of the fun of verifying Antarctic time, but I did notice that Palmer Station is not represented in the recently released tables... I am researching the history of Palmer's timezone; for the past few years (I don't know how many yet), 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. Palmer is located at 64.8S by 64.1W, i.e., AQ -6448-6406 Antarctica/Palmer Palmer Station, Anvers Island A footnote on the McMurdo/South Pole timezone issue - our wall clocks and wristwatches are set to N.Z. time (with DST, when appropriate). Our UNIX machines are set to UTC to simplify timestamps on collected data. Desktop machines (Macs and PCs) are set to wall time, however. Please include me on this list for the time being. For the summer season at least, I'm taking care of a bunch of UNIX machines and would like the xclocks to display the correct local time. -ethan -- Ethan Dicks erd(a)infinet.com |"Getting up, that is a problem. I've always had McMurdo Station, Antarctica | a hard time getting up when it's dark outside." erd(a)csec.mcmurdo.gov |"But in space, it's always dark." http://www.infinet.com/~erd/ |"I know...I know" - Sinclair & Ivanova, Babylon 5

1 0

Re: Recent changes to time zones reported by IATA
by kuhn＠cs.purdue.edu Oct. 4, 1996

Oct. 4, 1996

In message <8239341304101996/A31085/GLVC12/11AA23622600*@MHS>, Gwillim Law 919- 852-4294 wrote: > Twice a year, the International Air Transport Association (IATA) issues > a publication containing worldwide time zone data. It's called the > Standard Schedules Information Manual (SSIM). Its main purpose is to > define message formats for airlines to use when communicating their > schedules. The time zone information is apparently submitted by member > airlines, and represents the data those airlines intend to use in their > own schedules. Appendix F of the SSIM contains the time zone data. Sounds very useful. Do you know any contact address where one could subscribe this publication and what the subscription fee is? Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

2 1

FREE registration in over 400 indexes!
by RHill＠TheHost.com Oct. 4, 1996

Oct. 4, 1996

Hi, I saw your site at http://www.ft.uni-erlangen.de/~mskuhn/iso-time.html/, it looks good. Register it FOR FREE in over 400 Internet indexes and directories at http://www.CentralRegistry.com/ (just click the "free" button). I used it for my site and it worked great, traffic soared! Rusty J. Hill RHill(a)TheHost.com

1 0

Russian zone names in use in .ru
by Chris Carrier Oct. 3, 1996

Oct. 3, 1996

(Andrey A. Chernov) >INTERNET:ache@nagual.ru wrote: >Russian time zones never abbreviated in civil live, so don't >even try to search for them. >MSK/MSD abbreviation was born in computers world initially. I would be interested to know, what labels are used in Russia for its time zones? I know Moscow+0 is Moscow time, but what is the name in common use for Moscow+1, Moscow+2, all the way up to Moscow+10. Thank you. >I don't understand why you insist on some meaning of timezone >abbreviation, lets look at them as at abstract ascii labels. >Most of timezone abbreviations already are cryptic enough >for unexperienced user. Only one requirement will be needed: >ascii label must be unique. If timezone abbreviation comes >to you from native background, please don't change it. I completely agree.

2 1

Re: Russia autumn 1996 DST patch
by Michael H. Auria Oct. 2, 1996

Oct. 2, 1996

These messages (your entire thread) are being routed to sco.com. Would you please contact you email administrator (postmaster) to resolve this ... mha(a)sco.com > From netadm Wed Oct 2 13:31:08 1996 > Message-Id: <199610022006.PAA18054(a)ector.cs.purdue.edu> > Cc: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A.\ > Chernov) <ache(a)nagual.ru> > To: tz(a)elsie.nci.nih.gov > Subject: Re: Russia autumn 1996 DST patch > In-Reply-To: Your message of "Wed, 02 Oct 1996 14:23:10 +0400." > <199610021023.OAA00834(a)nagual.ru> > Date: Wed, 02 Oct 1996 15:06:06 -0500 > From: "Markus G. Kuhn" <kuhn(a)cs.purdue.edu> > In message <199610021023.OAA00834(a)nagual.ru>, Andrey A. Chernov wrote: > > Why you not try to change GMT to something else? > > Assume that this idea becomes reality and you understand my > > complaints. MSK/MSD sounds here like GMT for you. > Actually, I *do* suggest to change all occurances of the string GMT in > tzdata to UTC, the correct modern term. Reasonable exceptions are > only comment text references to historic time zones before 1972 (when > UTC replaced GMT as the reference time and GMT was redefined and > replaced by the term UT1) and where the term GMT is necessary for > backwards compatibility. > UTC is the official term even in the U.S. now (according to USNO folks > since 1986). If you listen with your shortwave radio to WWV (2.5, 5, > 10, or 15 MHz), the U.S. NIST time announcement broadcast says: "At > the tone ... twenty-three hours ... fifty-nine minutes ... coordinated > universal time ... beep". > Markus > -- > Markus G. Kuhn, Computer Science grad student, Purdue > University, Indiana, USA -- email: kuhn(a)cs.purdue.edu ================================================================================ Michael H. Auria mha(a)sco.com Santa Cruz Operation Information Services Communications Group Account/Alias/Remote Access Administrator Smith & Wesson: the original point & click interface ... (408) 429-4501

1 0

Europe/Norway (Europe/Oslo?)
by Tore Andre Klock Sept. 30, 1996

Sept. 30, 1996

[From the timedata file 'Europe'] # Plus, from 1 Jan 95: Austria, Finland, Sweden. (Norway negotiated terms for # entry but in a referendum on 28 Nov 94 the people voted No by 52.2% to 47.8% # on a turnout of 88.6%. This was almost the same result as Norway's previous # referendum in 1972, they are the only country to have said No twice. # Referendums in the other three countries voted Yes.) Very well, but.. Norway also uses the new European (EU) standard from _1996_. (The effects are pretty evident this morning, when all computers say "WINTER" and everybody else cling to their sunbath-lotion and scream "SUMMER"! This can be an interesting month.) Political statement/Historical Note: We voted "NO", but that was merely a matter of disposing ourselves of our right to vote. We still follow most of their rules. (Go figure) Hope you can include the correct data in the next version. Tore Andre Klock <tkl(a)www.moredata.no> PS: I got the file from a mirror, so it could be outdated. My apologies if so is the case.

1 0

tzcode and autoconf ?
by phdemuyt＠ulb.ac.be Sept. 25, 1996

Sept. 25, 1996

I have just downloaded tzcode96l.tar.gz, and tried to compile it on sysv68 R3V7.1 (Motorola MVME167 board with 68040 processor), and it failed with the following : cc -DTZDIR=\"/usr/local/etc/zoneinfo\" -c zic.c **Error: ./private.h: 72: Can't find include file stdlib.h **Error: zic.c: 9: Can't find include file locale.h *** Error code 1 Stop. I can solve that myself, but, looking in the sources, I have seen many autoconf-like HAVE_<something> symbols. I like the ability provided by autoconf to automatically deduce system characteristics, and to compile in a separate directory. Is there an autoconf'ed version of tzcode somewhere ? On a related point : the copyright for this code is public-domain. Would it not be better protected by the GPL ? Regards Philippe De Muyter

1 0

Re: how to install new tz data on BSD/OS ?
by Gildas Perrot Sept. 20, 1996

Sept. 20, 1996

Hi, BSD/OS 2.1 uses the new zoneinfo but not BSD/OS 1.1. I have one last BSD/OS 1.1 system and I have problems to change its zoneinfo. I got the sources of code and data of tz in ftp://elsie.nci.nih.gov/pub/. 1) zic europe gives : "europe", line ...: input line of unknown type It seems that zic which comes with 1.1 is not compatible with new source format. 2) I got zoneinfo sources and I compiled zic with 'make zic'. First, I had to remove yearistype in zip entry in Makefile since yearistype.sh doesn't appear in sources. I got a new zip which could compile the tz data. I did "zip europe" and "zip -l Europe/Paris" but /etc/localtime stays the same. I copy Europe/Paris to /etc/localtime and this time, the perl script "http://wsspinfo.cern.ch/file/find_dst.pl" says : Today is Fri Sep 20 13:12:31 1996, DST is off The current value of TZ is <not set> No DST change in the next 20 weeks instead of : Today is Fri Sep 20 15:12:7 1996, DST is on The current value of TZ is <not set> The next DST change will be Sun Sep 29 2:59:59 1996 one second later it will be Sun Sep 29 2:0:0 1996 as before the installation of the new /etc/localtime. Any idea about the problem ? Thanks in advance for your help. Gildas. -- Gildas PERROT, perrot(a)francenet.fr __o FranceNet, 28 rue Desaix, 75015 Paris ---_ \<,_ ---- (_)/ (_)

2 1

how to install new tz data on BSD/OS ?
by Gildas Perrot Sept. 19, 1996

Sept. 19, 1996

Hi, I am using BSD/OS systems which use tz data as BSDI support seems to say. I would like to know how to install tz data to incorporate new european summertimes (I am in MET-1METDST) as HP said : All countries member of the European Community should implement the new summertime guidelines for 1996/1997. From now on in all these countries the switch from wintertime to summertime will be done on the same day (switching back also). The changes are : # Mitteleuropaeische Zeit, Mitteleuropaeische Sommerzeit MEZ-1MESZ 0 3 25-31 3 1983-2038 0 MESZ-2 0 2 24-30 9 1983-1995 0 MEZ-1 0 2 25-31 10 1996-2038 0 MEZ-1 # Middle European Time, Middle European Time Daylight Savings Time MET-1METDST 0 3 25-31 3 1983-2038 0 METDST-2 0 2 24-30 9 1983-1995 0 MET-1 0 2 25-31 10 1996-2038 0 MET-1 # Greenwich Mean Time, British Summer Time GMT0BST 0 3 25-31 3 1983-1984 0 BST-1 0 3 23-29 3 1985-1990 0 BST-1 0 3 25-31 3 1991-1995 0 BST-1 0 2 25-31 3 1996-2038 0 BST-1 0 1 25-31 10 1983-1985 0 GMT0 0 1 23-29 10 1986-1994 0 GMT0 0 1 18-24 10 1995 0 GMT0 0 1 25-31 10 1996-2038 0 GMT0 # Western European Time, Western European Time Daylight Savings Time WET0WETDST 0 3 25-31 3 1983-1984 0 WETDST-1 0 3 23-29 3 1985-1995 0 WETDST-1 0 2 25-31 3 1996-2038 0 WETDST-1 0 1 25-31 10 1983-1985 0 WET0 0 1 23-29 10 1986-1995 0 WET0 0 1 25-31 10 1996-2038 0 WET0 I found that on my systems, I have a crypted /etc/localtime and /usr/share/zoneinfo/ directory with subdir containing TZ info for towns in crypted text. Thanks in advance for your help. Gildas. -- Gildas PERROT, perrot(a)francenet.fr __o FranceNet, 28 rue Desaix, 75015 Paris ---_ \<,_ ---- (_)/ (_)

2 1

About timezone
by yangsf＠cntdns Sept. 15, 1996

Sept. 15, 1996

Hi, The Summer time of P.R.CHINA has been canceled. What shall I do to change my timezone information data on my computer.

1 0

tzcode96l.tar.gz
by ado Sept. 8, 1996

Sept. 8, 1996

My apologies...tzcode96k.tar.gz was missing a couple of pieces. Now available is ftp://elsie.nci.nih.gov/pub/tzcode96l.tar.gz --ado

1 0

tzcode96k.tar.gz and tzdata96k.tar.gz
by ado Sept. 8, 1996

Sept. 8, 1996

The files ftp://elsie.nci.nih.gov/pub/tzcode96k.tar.gz and ftp://elsie.nci.nih.gov/pub/tzdata96k.tar.gz are now available. They incorporate the latest round of changes from Paul Eggert as well as the recent Year 200 material. --ado

1 0

Re: Some thoughts ...
by Peter Ilieve Sept. 7, 1996

Sept. 7, 1996

On Sep 7, 4:31am, Chris Carrier wrote: > > What the EU might consider would be the adoption of something similar to the > Uniform Time Act in the United States; set the dates for summer time but allow > member states to opt out of the summer time provision if they so choose. But that would destroy the whole purpose of the Commission's work to synchronise the change dates, so as to keep a fixed, mostly zero, offset between the times in the member states. > Has anyone heard anything about the release date of the 8th Directive? Well, the official schedule is still to have a Directive agreed by the Council of Ministers by 1 Jan 97. I doubt that this will happen as all previous ones I know of have been late. I reported the Commissions proposals here in May. They were another 4 years of the current rules: year start end 1998 29 Mar 25 Oct 1999 28 Mar 31 Oct 2000 26 Mar 29 Oct 2001 25 Mar 28 Oct If the French are now going to take a few months or so to decide what they want it virtually guarantees that the 8th directive will be late. Peter Ilieve peter(a)aldie.co.uk

1 0

Some thoughts ...
by Chris Carrier Sept. 7, 1996

Sept. 7, 1996

Some thoughts ... Markus G. Kuhn <kuhn(a)cs.purdue.edu> suggested that we get more formal, call ourselves the "Timezone Information Center" and let ourselves become more well known. I don't want to requote his entire post but I do favor all his suggestions. Peter Ilieve reported in a message received here on 1996-Sep-05 08:00 GMT: >The BBC Radio 4 news reported this morning that the French prime >minister Alain Juppe has issued some sort of letter indicating that >France will abandon summer time and keep the clocks the same for >the whole year... >The report said a parliamentary commission would now be set up to >decide if France should use GMT+1 or GMT+2 as its standard time. A thought; this October will be the first October that France will be voluntarily on GMT+2. It was involuntarily on GMT+2 during a couple of Octobers during the Nazi occupation. On the last day of GMT+2 this year, sunrise in Paris will be at 8:27, and at Cherbourg, 8:44. If GMT+2 were to become used all year sunrise in Paris would be delayed until 9:44, and in Cherbourg, 10:04! >I didn't catch what it said about the start date for any of this. To which Antoine Leca commented (1996-09-05) :Addition reflexion from myself: this is only a mission; given the prior :art and the time needed for the mission to investigate, I don't expect :this to change the DST rules in France for 1997, and I understand the :goal is the 8th directive. [starting 1998] :BTW, there will be elections in March 1998 in France. >So much for EC Directives. Actually the EC seems to give member states quite a bit of latitude in summer time dates; prior to 1995, the Directives specifically allowed the UK and Ireland authority to end summer time in late October, and that there was once a proposal to synchronize the end of summer time in 1984-6 at the second Sunday in October throughout the EC, but this fell through (source: some errors in the Nautical Almanac). What the EU might consider would be the adoption of something similar to the Uniform Time Act in the United States; set the dates for summer time but allow member states to opt out of the summer time provision if they so choose. Has anyone heard anything about the release date of the 8th Directive?

1 0

Suggestion: Timezone Information Center
by kuhn＠cs.purdue.edu Sept. 5, 1996

Sept. 5, 1996

As far as I know, this mailing list represents the best collection of people knowledgeable about time zones and summer time regulations all over the world. There would be many advantages if we could present ourself as a more formal entity to the governments of this world. We could establish something called for instance a "International Timezone Information Center". We could send letters directly or over UN channels to the governments. In these letters, we could invite the government employees responsible for the various national time zones to join our mailing list and we could ask the governments to inform us about any future time zone changes as early as possible. We could also provide for governments information material about the summer time switching algorithms that are currently in use. Such a periodic mailing could be easily created automatically from the most recent tz database. Such a publication would have several effects: - Governments have a chance to check the Olson database contents periodicly (both algorithms and terminology) - Governments are reminded periodicly to inform us whenever they plan to change their time zones - We would get in better contact with other organizations that collect timezone information (CIA, phone companies, etc.) - Governments are made a little bit more aware about the headaches that frequent arbitrary time zone changes and incompatible summer time switching rules can cause in the technical world - We would not have to rely completely on unprecise media reports about planned timezone changes but would get access to more official reports - Governments would get well-engineered examples of how a summer time switching rule should be specified correctly - Governments could perhaps be persuaded to accept a unique ID for their national time zones (I have already seen some good proposals here) All we need is someone who would be willing to operate such a "International Timezone Information Center (ITIC?)", preferably someone working for a big organization or company that is very interested in keeping information about time zones up to date. Perhaps several such organizations (AT&T, Sun, Microsoft, etc.) would be willing to support a time zone information center. The Information Center should under no circumstances be financed by selling the resulting publications. The data should be freely usable, in order to avoid the silly situation that we have with ISO standards (not online and so expensive that almost nobody ever sees a copy them). May be, we could later give this operation a more official touch by writing an ISO standard or an ITU-R TF-series recommendation <URL:http://www.itu.ch/itudoc/itu-r/rec/tf.html> that describes the role of the ITIC (ugly acronym, better suggestions?). We could also establish some more or less formal relations with the UN and the BIH/IERS (Bureau International d'Heure/International Earth Rotation Service, the folks that define UTC as defined by ITU-R). What do you think? Markus -- Markus G. Kuhn, Computer Science grad student, Purdue University, Indiana, USA -- email: kuhn(a)cs.purdue.edu

1 0

Re: Comments on download/Asia
by eubank＠itl.atr.co.jp Sept. 5, 1996

Sept. 5, 1996

Chris Carrier says: > It was postulated that Japan would go on DST in 1996, probably using the > American rules of 1st Sunday in April to last Sunday in October. I just > called AT&T and got back a time of GMT+9; therefore they are not on DST. > (This does not, however, preclude their going on DST this April 7 and then > deciding to end DST earlier than planned.) I have been living in Japan for a year and can confirm that there was no DST this year. Also, although I can't read Japanese newspapers, it's worth pointing out that there was absolutely no mention of the possibility of implementing DST in any English-language periodicals here, as far as I know. The only place I've heard anything about the possibility is on this mailing list. (Of course, this being Japan, perhaps such things are not discussed before they are announced :-)) Stephen Eubank eubank(a)itl.atr.co.jp

1 0

Possible future changes in France
by peter＠memex.co.uk Sept. 5, 1996

Sept. 5, 1996

The BBC Radio 4 news reported this morning that the French prime minister Alain Juppe has issued some sort of letter indicating that France will abandon summer time and keep the clocks the same for the whole year. It was reported as though this was almost a personal decision of his. He apparently doesn't see the point of it, says that many people don't understand why it is done, it has no economic benefit and it disturbs the sleep patterns of the young and elderly. The report said a parliamentary commission would now be set up to decide if France should use GMT+1 or GMT+2 as its standard time. I didn't catch what it said about the start date for any of this. So much for EC Directives. Peter Ilieve peter(a)aldie.co.uk

2 1

Comments on download/Asia
by Chris Carrier Sept. 5, 1996

Sept. 5, 1996

Some comments (there will be a lot more) on the time zone download of yesterday. These comments are confined to Asia (will make more comments as I digest the long posting). It was postulated that Japan would go on DST in 1996, probably using the American rules of 1st Sunday in April to last Sunday in October. I just called AT&T and got back a time of GMT+9; therefore they are not on DST. (This does not, however, preclude their going on DST this April 7 and then deciding to end DST earlier than planned.) Sri Lanka is listed as advancing from GMT+5:30 to +6:30 on 1996 May 25. I thought this happened on July 20???? Earlier during this year's Russian summer time period I called AT&T to get the time in Mongolia. I was quoted GMT+9 (GMT+8 with DST) for the entire country, and was told they were on 1 time zone not 3. Chris Carrier

2 1

proposed patch for selecting TZ, MET->CST, Sri Lanka, Antarctica,...
by Paul Eggert Sept. 4, 1996

Sept. 4, 1996

A while ago I composed several proposed changes to the tz tables in response to recent messages to this list, but I never got around to sending them off. Over Labor Day weekend I wrote up a description of the changes (see below). The proposed patch itself is at the end of this message. Sorry about the length and complexity of this change. * Improve support for selecting timezones. ** Add new tables zone.tab and iso3166.tab to make it easier to write scripts for administrators selecting a TZ value when configuring an installation. ** A new program `tzselect' uses these tables to interact with the user and output the resulting TZ value; it should be easy to write a GUI-based program as well. ** `make check_tables' checks these new tables for consistency. * Adopt the following rules for time zone abbreviations. (These rules are documented in the `africa' file.) Use abbreviations that consist of 3 or more upper-case Ascii letters, except use "___" for locations while uninhabited. Posix.1 requires at least 3 characters, and the restriction to upper-case Ascii letters follows most traditions. Previous editions of this database also used characters like ' ' and '?', but these characters have a special meaning to the shell and cause commands like set `date` to have unexpected effects. In theory, the character set could be !%./@A-Z^_a-z{}, but these tables use only upper-case Ascii letters (and "___"). Use abbreviations that are in common use among English-speakers, e.g. `EST' for Eastern Standard Time in North America. We assume that applications translate them to other languages as part of the normal localization process; for example, a French application might translate `EST' to `HNE'. For zones whose times are taken from a city's longitude, use the traditional xMT notation, e.g. `PMT' for Paris Mean Time. The only name like this in current use is `GMT'. If there is no common English abbreviation, abbreviate the English translation of the usual phrase used by native speakers. If this is not available or is a phrase mentioning the country (e.g. ``Cape Verde Time''), then: When a country has a single or principal time zone region, append `T' to the country's ISO code, e.g. `CVT' for Cape Verde Time. For summer time append `ST'; for double summer time append `DST'; etc. When a country has multiple time zones, take the first three letters of an English place name identifying each zone and then append `T', `ST', etc. as before; e.g. `MOSST' for MOScow Summer Time. * Add the following changes planned for the future: ** time zone abbreviation change due to planned political change Asia/Hong_Kong 1997 HKT -> CST Asia/Macao 1999 MOT -> CST * Add the following changes relevant to today's timestamps: ** Asia/Colombo adopted UTC+0630 on May 25; use `LKT' for new abbreviation. ** Asia/Ashkhabad is at UTC+4, not UTC+5. ** Asia/Dushanbe is at UTC+5, not UTC+6. ** Pacifc/Efate observes DST (the previous tables omitted this due to a typo). ** New zones: Africa/El_Aaiun - Western Sahara switched from AAT to WET in 1976. Africa/Ceuta - Spanish Morocco switched from Moroccan to Spanish rules in 1984. Antarctica/Casey - Antarctic research station Antarctica/Mawson - " Antarctica/McMurdo - " Antarctica/South_Pole - " Arctic/Longyearbyen - has a different country code from Europe/Oslo Asia/Ishigaki - uncomment it, since it seems to be right Asia/Kuching - Kuala Lumpur changed UTC offset in 1982, but Kuching didn't ** Zone name change: Africa/Lumumbashi -> Africa/Lubumbashi (fixes an embarrassing misspelling) ** Time zone abbrevation changes Many (but not all) of these changes are a result of the more consistent time zone abbreviation policy described above. *** MET -> CET correction The following changes fix the tz database to reflect actual practice. This change affects many locations in Europe, North Africa, and the Near East. MET -> CET (Central European Time) MET DST -> CEST (Central European Summer Time) MET DDST -> MEDST Similarly for EET DST, WET DST *** South America says ``summer'', not ``daylight'' America/Buenos_Aires: ARST/ARDT -> ART/ARST *** Ad hoc timezone abbreviation -> different ad hoc abbreviation America/Godthab: WGT/WGT DST -> WGT/WGST America/Scoresbysund: EGT/EGT DST -> EGT/EGST *** Ad hoc names to ISO-3166-oriented names America/Asuncion: AST/ADT -> PYT/PYST America/Bogota: EST -> COT America/Cayenne: EST -> GFT America/Caracas: AST -> VET America/Guayaquil: EST -> ECT America/Guyana: EST -> GYT America/La_Paz: AST -> BOT America/Lima: EST -> PET America/Miquelon: SPST/SPDT -> PMST/PMDT America/Montevideo: EST/EDT -> UYT/UYST America/Paramaribo: EST -> SRT America/Santiago: CST/CDT -> CLT/CLST Asia/Ashkhabad: ASK -> TMT Asia/Baku: BSK -> AZT Asia/Bishkek: BSK/BSD -> KGT/KGST Asia/Dacca: BGT -> BDT Asia/Dushanbe: DSK -> TJT Asia/Kuala_Lumpur: SGT -> MYT Asia/Macao: CST -> MOT Asia/Manila: PST/PDT -> PHT/PHST Asia/Rangoon: BMT -> MMT Asia/Tashkent: TSK -> UZT Asia/Tbilisi: TBSK -> GET Asia/Tehran: IST -> IRT Asia/Thimbu: BGT -> BTT Asia/Yerevan: AMST -> AMT Atlantic/Cape_Verde: AAT -> CVT Atlantic/South_Georgia: FST -> GST Atlantic/Stanley: AST/ADT -> FKT/FKST Indian/Chagos: PKT -> IOT Indian/Christmas: JVT -> CXT Indian/Mahe: SMT -> SCT Indian/Maldives: PKT -> MVT Indian/Mauritius: SMT -> MUT Indian/Reunion: SMT -> RET Pacific/Apia: SST -> WST Pacific/Efate: NCST/NCDT -> VUT/VUST Pacific/Fakaofo: THT -> TKT Pacific/Fiji: NZST -> FJT Pacific/Funafuti: NZST -> TVT Pacific/Guadalcanal: NCST -> SBT Pacific/Kwajalein, Pacific/Majuro: NZST -> MHT Pacific/Nauru: NZST -> NRT Pacific/Niue: SST -> NUT Pacific/Norfolk: NRFT -> NFT Pacific/Palau: PLT -> PWT Pacific/Pitcairn: PIT -> PNT Pacific/Port_Moresby: EST -> PGT Pacific/Rarotonga: THT/THDT -> CKT/CKHST Pacific/Saipan: GST -> MPT Pacific/Tongatapu: TGT -> TOT Pacific/Wallis: NZST -> WFT *** Ad hoc names to first-3-letters-of-place names Asia/Aktau: ASK/ASD -> AKTT/AKTST Asia/Alma-Ata: AASK/AASD -> ALMT/ALMST Asia/Anadyr: ASK/ASD -> ANAT/ANAST Asia/Irkutsk: ISK/ISD -> IRKT/IRKST Asia/Jakarta: JVT -> JAVT Asia/Jayapura: MLT -> JAYT Asia/Kamchatka: PSK/PSD -> PETT/PETST Asia/Krasnoyarsk: KRSK/KRSD -> KRAT/KRAST Asia/Magadan: MSK/MSD -> MAGT/MAGST Asia/Novosibirsk: NSK/NSD -> NOVT/NOVST Asia/Omsk: OSK/OSD -> OMST/OMSST Asia/Ujung_Pandang: BNT -> BORT Asia/Ulan_Bator: UST/UTT -> ULAT/ULAST Asia/Vladivostok: VSK/VSD -> VLAT/VLAST Asia/Yakutsk: YSK/YSD -> YAKT/YAKST Europe/Kuybyshev: KSK/KSD -> KUYT/KUYST Europe/Moscow and several other locations: MSK/MSD -> MOST/MOSST Europe/Yekaterinburg: ESK/ESD -> YEKT/YEKST Pacific/Chatham: CHST/CHDT -> CHAST/CHADT Pacific/Easter: CST/CDT -> EAST/EASST Pacific/Enderbury: TGT -> PHOT Pacific/Galapagos: CST -> GALT Pacific/Gambier: GBT -> GAMT Pacific/Kiritimati: KRT -> LINT Pacific/Kosrae: NZST -> KOST Pacific/Marquesas: MQT -> MART Pacific/Ponape: NCST -> PONT Pacific/Tahiti: THT -> TAHT Pacific/Tarawa: NZST -> GILT Pacific/Truk: GST -> TRUT Pacific/Wake: NZST -> WAKT Pacific/Yap: GST -> YAPT * There are many other changes relevant only for historical timestamps. Below, only the changes for times since 1970 are listed. ** Atlantic/Azores 1977-1983: observed DST ** time zone name change at independence for: America/Paramaribo 1975 Asia/Ashkhabad 1991 Asia/Yerevan 1991 Asia/Baku 1991 Asia/Bishkek 1991 Asia/Dacca 1971 Asia/Dushanbe 1991 Asia/Karachi 1971 Asia/Tashkent 1991 Asia/Tbilisi 1991 ** time zone abbreviation changes: Africa/Monrovia 1919-1972: LST -> LRT America/Asuncion 1972-1974: EST -> PYT America/Paramaribo 1945-1975: DGST -> NEGT America/Scoresbysund 1916-1981: MGT/MGT DST -> CGT/CGST Asia/Aktau 1924-1991: SHSK/SHSD -> SHET/SHEST Asia/Ashkhabad 1924-1991: ASK/ASD -> ASHT/ASHST Asia/Baku 1924-1991: BSD/BSK -> BAKT/BAKST Asia/Bishkek 1924-1991: FSK/FSD -> FRUT/FRUST Asia/Chungking 1928-1980: ICT -> CHUT Asia/Dacca 1951-1971: BGT -> DACT Asia/Dushanbe 1924-1991: DSK/DSD -> DUST/DUSST Asia/Harbin 1928-1932, 1940-1980: MAT -> HART, KST -> HART Asia/Karachi 1951-1971: PKT -> KART Asia/Kashgar 1928-1980: ETT -> KAST Asia/Kuala_Lumpur 1905-1942, 1945-1982: SGT -> MALT Asia/Tashkent 1924-1991: TSK/TSD -> TAST/TASST Asia/Tbilisi 1924-1991: TBSK/TBSD -> TBIT/TBIST Asia/Tehran 1977-1979: GST/GDT -> IRT/IRST Asia/Urumqi 1928-1980: URT -> URUT Asia/Yerevan 1924-1991: YSK/YSD -> YERT/YERST Atlantic/Azores ACT/ACT DST/ACT DDST -> AZOT/AZOST/AZODST Atlantic/Canary ACT/ACT DST -> CANT/CANST Atlantic/Madeira ACT/ACT DST/ACT DDST -> MAT/MADST/MADDST Atlantic/Stanley 1983-1985: EST/EDT -> FKT/FKST Europe/Istanbul 1978-1985: TUR/TUR DST -> TRT/TRST Europe/Yekaterinburg 1924-1991: SSK/SSD -> SVET/SVEST Pacific/Easter 1932-1982: MST/MDT -> EAST/EASST Pacific/Enderbury 1901-1979: KJT -> PHOT Pacific/Enderbury 1979-1995: SST -> PHOT Pacific/Kiritimati 1901-1979: LIT -> LINT Pacific/Kiritimati 1979-1995: THT -> LINT Pacific/Kwajalein 1969-1993: KJT -> KWAT Pacific/Nauru 1944-1979: NST -> NRT Pacific/Niue 1951-1978: NIT -> NUT Pacific/Rarotonga 1901-1978: CIST -> CKT =================================================================== RCS file: RCS/Makefile,v retrieving revision 1996.5 retrieving revision 1996.5.1.1 diff -c -r1996.5 -r1996.5.1.1 *** Makefile 1996/02/29 15:33:38 1996.5 --- Makefile 1996/09/03 23:48:46 1996.5.1.1 *************** *** 197,202 **** --- 197,205 ---- CFLAGS= + # The name of a Posix-compliant `awk' on your system. + AWK= awk + ############################################################################### cc= cc *************** *** 215,225 **** NEWUCBSRCS= date.c logwtmp.c strftime.c SOURCES= $(HEADERS) $(LIBSRCS) $(NONLIBSRCS) $(NEWUCBSRCS) MANS= newctime.3 newstrftime.3 newtzset.3 time2posix.3 \ ! tzfile.5 zic.8 zdump.8 DOCS= README Theory $(MANS) date.1 Makefile ! YDATA= africa antarctica asia australasia \ ! europe northamerica southamerica pacificnew etcetera factory \ ! backward NDATA= systemv SDATA= solar87 solar88 solar89 TDATA= $(YDATA) $(NDATA) $(SDATA) --- 218,228 ---- NEWUCBSRCS= date.c logwtmp.c strftime.c SOURCES= $(HEADERS) $(LIBSRCS) $(NONLIBSRCS) $(NEWUCBSRCS) MANS= newctime.3 newstrftime.3 newtzset.3 time2posix.3 \ ! tzfile.5 tzselect.8 zic.8 zdump.8 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) *************** *** 234,244 **** all: zic zdump $(LIBOBJS) ! ALL: all date install: all $(DATA) $(REDO) $(TZLIB) $(MANS) ./zic -y $(YEARISTYPE) \ -d $(TZDIR) -l $(LOCALTIME) -p $(POSIXRULES) -mkdir $(TOPDIR) $(ETCDIR) cp zic zdump $(ETCDIR)/. -mkdir $(TOPDIR) $(MANDIR) \ --- 237,249 ---- all: zic zdump $(LIBOBJS) ! ALL: all date tzselect install: all $(DATA) $(REDO) $(TZLIB) $(MANS) ./zic -y $(YEARISTYPE) \ -d $(TZDIR) -l $(LOCALTIME) -p $(POSIXRULES) + -rm -f $(TZDIR)/iso3166.tab $(TZDIR)/zone.tab + cp iso3166.tab zone.tab $(TZDIR)/. -mkdir $(TOPDIR) $(ETCDIR) cp zic zdump $(ETCDIR)/. -mkdir $(TOPDIR) $(MANDIR) \ *************** *** 246,256 **** -rm -f $(MANDIR)/man3/newctime.3 \ $(MANDIR)/man3/newtzset.3 \ $(MANDIR)/man5/tzfile.5 \ $(MANDIR)/man8/zdump.8 \ $(MANDIR)/man8/zic.8 cp newctime.3 newtzset.3 $(MANDIR)/man3/. cp tzfile.5 $(MANDIR)/man5/. ! cp zdump.8 zic.8 $(MANDIR)/man8/. INSTALL: ALL install date.1 -mkdir $(TOPDIR) $(BINDIR) --- 251,262 ---- -rm -f $(MANDIR)/man3/newctime.3 \ $(MANDIR)/man3/newtzset.3 \ $(MANDIR)/man5/tzfile.5 \ + $(MANDIR)/man8/tzselect.8 \ $(MANDIR)/man8/zdump.8 \ $(MANDIR)/man8/zic.8 cp newctime.3 newtzset.3 $(MANDIR)/man3/. cp tzfile.5 $(MANDIR)/man5/. ! cp tzselect.8 zdump.8 zic.8 $(MANDIR)/man8/. INSTALL: ALL install date.1 -mkdir $(TOPDIR) $(BINDIR) *************** *** 300,307 **** $(LDLIBS) -lc ,lib.a -o $@ rm -f ,lib.a clean: ! rm -f core *.o *.out zdump zic yearistype date ,* *.tar.gz names: @echo $(ENCHILADA) --- 306,324 ---- $(LDLIBS) -lc ,lib.a -o $@ rm -f ,lib.a + tzselect: tzselect.ksh + sed \ + -e 's|AWK=[^}]*|AWK=$(AWK)|g' \ + -e 's|TZDIR=[^}]*|TZDIR=$(TZDIR)|' \ + <$? >$@ + chmod +x $@ + + check_tables: checktab.awk $(PRIMARY_YDATA) + $(AWK) -f checktab.awk $(PRIMARY_YDATA) + clean: ! rm -f core *.o *.out tzselect zdump zic yearistype date \ ! ,* *.tar.gz names: @echo $(ENCHILADA) =================================================================== RCS file: RCS/africa,v retrieving revision 1996.7 retrieving revision 1996.7.1.1 diff -c -r1996.7 -r1996.7.1.1 *** africa 1996/05/03 02:49:55 1996.7 --- africa 1996/09/03 23:48:46 1996.7.1.1 *************** *** 4,10 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), --- 4,10 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), *************** *** 61,124 **** # Omit `.' from abbreviations in names, e.g. prefer `St_Helena' # to `St._Helena'. # ! # We typically use traditional English time zone abbreviations, ! # and assume that applications translate them to other languages ! # as part of the normal localization process. # ! # I made up the following time zone abbreviations; corrections are welcome! # LMT Local Mean Time ! # -2:00 CVT Cape Verde Time (no longer used) ! # -1:00 AAT Atlantic Africa Time # 0:00 WAT West Africa Time # 1:00 CAT Central Africa Time # 2:00 SAT South Africa Time # 3:00 EAT East Africa Time - # 4:00 SMT Seychelles and Mascarene Time # The final `T' is replaced by `ST' for summer time, e.g. `SAST'. # BEAT is British East Africa Time, which was 2:30 before 1948 and 2:45 after. # Algeria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Algeria 1916 only - Jun 14 23:00s 1:00 " DST" Rule Algeria 1916 1919 - Oct Sun<=7 23:00s 0 - ! Rule Algeria 1917 only - Mar 24 23:00s 1:00 " DST" ! Rule Algeria 1918 only - Mar 9 23:00s 1:00 " DST" ! Rule Algeria 1919 only - Mar 1 23:00s 1:00 " DST" ! Rule Algeria 1920 only - Feb 14 23:00s 1:00 " DST" Rule Algeria 1920 only - Oct 23 23:00s 0 - ! Rule Algeria 1921 only - Mar 14 23:00s 1:00 " DST" Rule Algeria 1921 only - Jun 21 23:00s 0 - ! Rule Algeria 1939 only - Sep 11 23:00s 1:00 " DST" Rule Algeria 1939 only - Nov 19 1:00 0 - ! Rule Algeria 1944 1945 - Apr Mon<=7 2:00 1:00 " DST" Rule Algeria 1944 only - Oct 8 2:00 0 - Rule Algeria 1945 only - Sep 16 1:00 0 - ! Rule Algeria 1971 only - Apr 25 23:00s 1:00 " DST" Rule Algeria 1971 only - Sep 26 23:00s 0 - ! Rule Algeria 1977 only - May 6 0:00 1:00 " DST" Rule Algeria 1977 only - Oct 21 0:00 0 - ! Rule Algeria 1978 only - Mar 24 1:00 1:00 " DST" Rule Algeria 1978 only - Sep 22 3:00 0 - ! Rule Algeria 1980 only - Apr 25 0:00 1:00 " DST" Rule Algeria 1980 only - Oct 31 2:00 0 - # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Algiers 0:12:12 - LMT 1891 Mar 15 0:01 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 Algeria WET%s 1940 Feb 25 2:00 ! 1:00 Algeria MET%s 1946 Oct 7 0:00 - WET 1956 Jan 29 ! 1:00 - MET 1963 Apr 14 ! 0:00 Algeria WET%s 1977 Oct 21 ! 1:00 Algeria MET%s 1979 Oct 26 ! 0:00 Algeria WET%s 1981 May ! 1:00 - MET # Angola # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Luanda 0:52:56 - LMT 1892 ! 0:52 - LMT 1911 May 26 # Luanda Mean Time 1:00 - CAT # Bassas da India --- 61,155 ---- # Omit `.' from abbreviations in names, e.g. prefer `St_Helena' # to `St._Helena'. # ! # For time zone abbreviations like `EST' I used the following rules, ! # in decreasing order of importance: ! # ! # Use abbreviations that consist of 3 or more upper-case Ascii letters, ! # except use "___" for locations while uninhabited. ! # Posix.1 requires at least 3 characters, and the restriction to ! # upper-case Ascii letters follows most traditions. ! # Previous editions of this database also used characters like ! # ' ' and '?', but these characters have a special meaning to ! # the shell and cause commands like ! # set `date` ! # to have unexpected effects. In theory, the character set could ! # be !%./@A-Z^_a-z{}, but these tables use only upper-case ! # Ascii letters (and "___"). ! # Use abbreviations that are in common use among English-speakers, ! # e.g. `EST' for Eastern Standard Time in North America. ! # We assume that applications translate them to other languages ! # as part of the normal localization process; for example, ! # a French application might translate `EST' to `HNE'. ! # For zones whose times are taken from a city's longitude, use the ! # traditional xMT notation, e.g. `PMT' for Paris Mean Time. ! # The only name like this in current use is `GMT'. ! # If there is no common English abbreviation, abbreviate the English ! # translation of the usual phrase used by native speakers. ! # If this is not available or is a phrase mentioning the country ! # (e.g. ``Cape Verde Time''), then: ! # ! # When a country has a single or principal time zone region, ! # append `T' to the country's ISO code, e.g. `CVT' for ! # Cape Verde Time. For summer time append `ST'; ! # for double summer time append `DST'; etc. ! # When a country has multiple time zones, take the first three ! # letters of an English place name identifying each zone ! # and then append `T', `ST', etc. as before; ! # e.g. `MOSST' for MOScow Summer Time. # ! # ! # For Africa I invented the following time zone abbreviations. # LMT Local Mean Time ! # -1:00 AAT Atlantic Africa Time (no longer used) # 0:00 WAT West Africa Time # 1:00 CAT Central Africa Time # 2:00 SAT South Africa Time # 3:00 EAT East Africa Time # The final `T' is replaced by `ST' for summer time, e.g. `SAST'. # BEAT is British East Africa Time, which was 2:30 before 1948 and 2:45 after. # Algeria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Algeria 1916 only - Jun 14 23:00s 1:00 S Rule Algeria 1916 1919 - Oct Sun<=7 23:00s 0 - ! Rule Algeria 1917 only - Mar 24 23:00s 1:00 S ! Rule Algeria 1918 only - Mar 9 23:00s 1:00 S ! Rule Algeria 1919 only - Mar 1 23:00s 1:00 S ! Rule Algeria 1920 only - Feb 14 23:00s 1:00 S Rule Algeria 1920 only - Oct 23 23:00s 0 - ! Rule Algeria 1921 only - Mar 14 23:00s 1:00 S Rule Algeria 1921 only - Jun 21 23:00s 0 - ! Rule Algeria 1939 only - Sep 11 23:00s 1:00 S Rule Algeria 1939 only - Nov 19 1:00 0 - ! Rule Algeria 1944 1945 - Apr Mon<=7 2:00 1:00 S Rule Algeria 1944 only - Oct 8 2:00 0 - Rule Algeria 1945 only - Sep 16 1:00 0 - ! Rule Algeria 1971 only - Apr 25 23:00s 1:00 S Rule Algeria 1971 only - Sep 26 23:00s 0 - ! Rule Algeria 1977 only - May 6 0:00 1:00 S Rule Algeria 1977 only - Oct 21 0:00 0 - ! Rule Algeria 1978 only - Mar 24 1:00 1:00 S Rule Algeria 1978 only - Sep 22 3:00 0 - ! Rule Algeria 1980 only - Apr 25 0:00 1:00 S Rule Algeria 1980 only - Oct 31 2:00 0 - # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Algiers 0:12:12 - LMT 1891 Mar 15 0:01 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 Algeria WE%sT 1940 Feb 25 2:00 ! 1:00 Algeria CE%sT 1946 Oct 7 0:00 - WET 1956 Jan 29 ! 1:00 - CET 1963 Apr 14 ! 0:00 Algeria WE%sT 1977 Oct 21 ! 1:00 Algeria CE%sT 1979 Oct 26 ! 0:00 Algeria WE%sT 1981 May ! 1:00 - CET # Angola # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Luanda 0:52:56 - LMT 1892 ! 0:52:04 - LMT 1911 May 26 # Luanda Mean Time? 1:00 - CAT # Bassas da India *************** *** 160,166 **** -2:00 - CVT 1942 Sep -2:00 1:00 CVST 1945 Oct 15 -2:00 - CVT 1975 Nov 25 2:00 ! -1:00 - AAT # Central African Republic # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 191,197 ---- -2:00 - CVT 1942 Sep -2:00 1:00 CVST 1945 Oct 15 -2:00 - CVT 1975 Nov 25 2:00 ! -1:00 - CVT # Central African Republic # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 211,238 **** # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Egypt 1940 only - Jul 15 0:00 1:00 " DST" Rule Egypt 1940 only - Oct 1 0:00 0 - ! Rule Egypt 1941 only - Apr 15 0:00 1:00 " DST" Rule Egypt 1941 only - Sep 16 0:00 0 - ! Rule Egypt 1942 1944 - Apr 1 0:00 1:00 " DST" Rule Egypt 1942 only - Oct 27 0:00 0 - Rule Egypt 1943 1945 - Nov 1 0:00 0 - ! Rule Egypt 1945 only - Apr 16 0:00 1:00 " DST" ! Rule Egypt 1957 only - May 10 0:00 1:00 " DST" Rule Egypt 1957 1958 - Oct 1 0:00 0 - ! Rule Egypt 1958 only - May 1 0:00 1:00 " DST" ! Rule Egypt 1959 1981 - May 1 1:00 1:00 " DST" Rule Egypt 1959 1965 - Sep 30 3:00 0 - Rule Egypt 1966 max - Oct 1 3:00 0 - ! Rule Egypt 1982 only - Jul 25 1:00 1:00 " DST" ! Rule Egypt 1983 only - Jul 12 1:00 1:00 " DST" ! Rule Egypt 1984 1988 - May 1 1:00 1:00 " DST" ! Rule Egypt 1989 only - May 6 1:00 1:00 " DST" ! Rule Egypt 1990 max - May 1 1:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Cairo 2:05:00 - LMT 1900 Oct ! 2:00 Egypt EET%s # Equatorial Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 242,269 ---- # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Egypt 1940 only - Jul 15 0:00 1:00 S Rule Egypt 1940 only - Oct 1 0:00 0 - ! Rule Egypt 1941 only - Apr 15 0:00 1:00 S Rule Egypt 1941 only - Sep 16 0:00 0 - ! Rule Egypt 1942 1944 - Apr 1 0:00 1:00 S Rule Egypt 1942 only - Oct 27 0:00 0 - Rule Egypt 1943 1945 - Nov 1 0:00 0 - ! Rule Egypt 1945 only - Apr 16 0:00 1:00 S ! Rule Egypt 1957 only - May 10 0:00 1:00 S Rule Egypt 1957 1958 - Oct 1 0:00 0 - ! Rule Egypt 1958 only - May 1 0:00 1:00 S ! Rule Egypt 1959 1981 - May 1 1:00 1:00 S Rule Egypt 1959 1965 - Sep 30 3:00 0 - Rule Egypt 1966 max - Oct 1 3:00 0 - ! Rule Egypt 1982 only - Jul 25 1:00 1:00 S ! Rule Egypt 1983 only - Jul 12 1:00 1:00 S ! Rule Egypt 1984 1988 - May 1 1:00 1:00 S ! Rule Egypt 1989 only - May 6 1:00 1:00 S ! Rule Egypt 1990 max - May 1 1:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Cairo 2:05:00 - LMT 1900 Oct ! 2:00 Egypt EE%sT # Equatorial Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 243,256 **** # Eritrea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Asmera 2:35:32 - LMT 1870 ! 2:36 - AMT 1890 # Asmera Mean Time ! 2:35 - AAMT 1936 May 5 # Addis Ababa MT 3:00 - EAT # Ethiopia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Addis_Ababa 2:34:48 - LMT 1870 ! 2:35 - AAMT 1936 May 5 # Addis Ababa MT 3:00 - EAT # Europa Island --- 274,287 ---- # Eritrea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Asmera 2:35:32 - LMT 1870 ! 2:35:32 - AMT 1890 # Asmera Mean Time ! 2:35:20 - AAMT 1936 May 5 # Addis Ababa MT? 3:00 - EAT # Ethiopia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Addis_Ababa 2:34:48 - LMT 1870 ! 2:35:20 - AAMT 1936 May 5 # Addis Ababa MT? 3:00 - EAT # Europa Island *************** *** 264,280 **** # Gambia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Banjul -1:06:36 - LMT 1912 ! -1:07 - BMT 1935 # Banjul Mean Time -1:00 - AAT 1964 0:00 - WAT # Ghana ! # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): ! # WATDT is my invention for ``West Africa one-Third Daylight Time''. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman says DST was observed from 1931 to ``the present''; go with Shanks. ! Rule Ghana 1936 1942 - Sep 1 0:00 0:20 WATDT Rule Ghana 1936 1942 - Dec 31 0:00 0 WAT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Accra -0:00:52 - LMT 1918 --- 295,311 ---- # Gambia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Banjul -1:06:36 - LMT 1912 ! -1:06:36 - BMT 1935 # Banjul Mean Time -1:00 - AAT 1964 0:00 - WAT # Ghana ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): ! # WATST is my invention for ``West Africa one-Third Summer Time''. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman says DST was observed from 1931 to ``the present''; go with Shanks. ! Rule Ghana 1936 1942 - Sep 1 0:00 0:20 WATST Rule Ghana 1936 1942 - Dec 31 0:00 0 WAT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Accra -0:00:52 - LMT 1918 *************** *** 329,335 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Monrovia -0:43:08 - LMT 1882 -0:43:08 - MMT 1919 Mar # Monrovia Mean Time ! -0:44:30 - LST 1972 May # Liberia Standard Time 0:00 - WAT ############################################################################### --- 360,366 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Monrovia -0:43:08 - LMT 1882 -0:43:08 - MMT 1919 Mar # Monrovia Mean Time ! -0:44:30 - LRT 1972 May # Liberia Time 0:00 - WAT ############################################################################### *************** *** 345,372 **** # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Libya 1951 only - Oct 14 2:00 1:00 " DST" Rule Libya 1952 only - Jan 1 0:00 0 - ! Rule Libya 1953 only - Oct 9 2:00 1:00 " DST" Rule Libya 1954 only - Jan 1 0:00 0 - ! Rule Libya 1955 only - Sep 30 0:00 1:00 " DST" Rule Libya 1956 only - Jan 1 0:00 0 - ! Rule Libya 1982 1984 - Apr 1 0:00 1:00 " DST" Rule Libya 1982 1985 - Oct 1 0:00 0 - ! Rule Libya 1985 only - Apr 6 0:00 1:00 " DST" ! Rule Libya 1986 only - Apr 4 0:00 1:00 " DST" Rule Libya 1986 only - Oct 3 0:00 0 - ! Rule Libya 1987 1989 - Apr 1 0:00 1:00 " DST" Rule Libya 1987 1990 - Oct 1 0:00 0 - ! Rule Libya 1990 only - May 4 0:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 ! 1:00 Libya MET%s 1959 2:00 - EET 1982 # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): # usno1995 (from OAG) says Libya uses 2:00 all year, as they did before 1982. # We don't know when they switched back. We'll guess 1991. ! 1:00 Libya MET%s 1991 2:00 - EET # Madagascar --- 376,403 ---- # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Libya 1951 only - Oct 14 2:00 1:00 S Rule Libya 1952 only - Jan 1 0:00 0 - ! Rule Libya 1953 only - Oct 9 2:00 1:00 S Rule Libya 1954 only - Jan 1 0:00 0 - ! Rule Libya 1955 only - Sep 30 0:00 1:00 S Rule Libya 1956 only - Jan 1 0:00 0 - ! Rule Libya 1982 1984 - Apr 1 0:00 1:00 S Rule Libya 1982 1985 - Oct 1 0:00 0 - ! Rule Libya 1985 only - Apr 6 0:00 1:00 S ! Rule Libya 1986 only - Apr 4 0:00 1:00 S Rule Libya 1986 only - Oct 3 0:00 0 - ! Rule Libya 1987 1989 - Apr 1 0:00 1:00 S Rule Libya 1987 1990 - Oct 1 0:00 0 - ! Rule Libya 1990 only - May 4 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tripoli 0:52:44 - LMT 1920 ! 1:00 Libya CE%sT 1959 2:00 - EET 1982 # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): # usno1995 (from OAG) says Libya uses 2:00 all year, as they did before 1982. # We don't know when they switched back. We'll guess 1991. ! 1:00 Libya CE%sT 1991 2:00 - EET # Madagascar *************** *** 401,407 **** # Mauritius # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis ! 4:00 - SMT # Agalega Is, Rodriguez # no information; probably like Indian/Mauritius --- 432,438 ---- # Mauritius # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mauritius 3:50:00 - LMT 1907 # Port Louis ! 4:00 - MUT # Mauritius Time # Agalega Is, Rodriguez # no information; probably like Indian/Mauritius *************** *** 411,439 **** 3:00 - EAT # Morocco ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Morocco 1939 only - Sep 12 0:00 1:00 " DST" Rule Morocco 1939 only - Nov 19 0:00 0 - ! Rule Morocco 1940 only - Feb 25 0:00 1:00 " DST" Rule Morocco 1945 only - Nov 18 0:00 0 - ! Rule Morocco 1950 only - Jun 11 0:00 1:00 " DST" Rule Morocco 1950 only - Oct 29 0:00 0 - ! Rule Morocco 1967 only - Jun 3 12:00 1:00 " DST" Rule Morocco 1967 only - Oct 1 0:00 0 - ! Rule Morocco 1974 only - Jun 24 0:00 1:00 " DST" Rule Morocco 1974 only - Sep 1 0:00 0 - ! Rule Morocco 1976 1977 - May 1 0:00 1:00 " DST" Rule Morocco 1976 only - Aug 1 0:00 0 - Rule Morocco 1977 only - Sep 28 0:00 0 - ! Rule Morocco 1978 only - Jun 1 0:00 1:00 " DST" Rule Morocco 1978 only - Aug 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 ! 0:00 Morocco WET%s 1984 Mar 16 ! 1:00 - MET 1986 0:00 - WET - # The following are controlled by Spain, and are like Europe/Madrid: - # Alboran, Alhucemas Is, Ceuta, Chafarinas Is, Melilla. # Mozambique # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 442,472 ---- 3:00 - EAT # Morocco ! # rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Morocco 1939 only - Sep 12 0:00 1:00 S Rule Morocco 1939 only - Nov 19 0:00 0 - ! Rule Morocco 1940 only - Feb 25 0:00 1:00 S Rule Morocco 1945 only - Nov 18 0:00 0 - ! Rule Morocco 1950 only - Jun 11 0:00 1:00 S Rule Morocco 1950 only - Oct 29 0:00 0 - ! Rule Morocco 1967 only - Jun 3 12:00 1:00 S Rule Morocco 1967 only - Oct 1 0:00 0 - ! Rule Morocco 1974 only - Jun 24 0:00 1:00 S Rule Morocco 1974 only - Sep 1 0:00 0 - ! Rule Morocco 1976 1977 - May 1 0:00 1:00 S Rule Morocco 1976 only - Aug 1 0:00 0 - Rule Morocco 1977 only - Sep 28 0:00 0 - ! Rule Morocco 1978 only - Jun 1 0:00 1:00 S Rule Morocco 1978 only - Aug 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Casablanca -0:30:20 - LMT 1913 Oct 26 ! 0:00 Morocco WE%sT 1984 Mar 16 ! 1:00 - CET 1986 ! 0:00 - WET ! # Western Sahara ! Zone Africa/El_Aaiun -0:52:48 - LMT 1934 Jan ! -1:00 - AAT 1976 Apr 14 0:00 - WET # Mozambique # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 463,469 **** # Reunion # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Reunion 3:41:52 - LMT 1911 Jun # Saint-Denis ! 4:00 - SMT # Rwanda # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 496,502 ---- # Reunion # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Reunion 3:41:52 - LMT 1911 Jun # Saint-Denis ! 4:00 - RET # Reunion Time # Rwanda # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 473,479 **** # St Helena # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/St_Helena -0:22:48 - LMT 1890 # Jamestown ! -0:06 - ?MT 1951 # a typo in Shanks? 0:00 - GMT # The other parts of the St Helena territory are similar: # Tristan da Cunha: on GMT, says Whitman --- 506,512 ---- # St Helena # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/St_Helena -0:22:48 - LMT 1890 # Jamestown ! -0:06 - SHT 1951 # St Helena Time (?) 0:00 - GMT # The other parts of the St Helena territory are similar: # Tristan da Cunha: on GMT, says Whitman *************** *** 483,489 **** # Sao Tome and Principe # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Sao_Tome 0:26:56 - LMT 1884 ! -0:37 - ?MT 1912 # a typo in Shanks? 0:00 - WAT # Senegal --- 516,522 ---- # Sao Tome and Principe # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Sao_Tome 0:26:56 - LMT 1884 ! -0:36:32 - LMT 1912 # Lisbon Mean Time 0:00 - WAT # Senegal *************** *** 495,501 **** # Seychelles # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mahe 3:41:48 - LMT 1906 Jun # Victoria ! 4:00 - SMT # Sierra Leone # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 528,534 ---- # Seychelles # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Mahe 3:41:48 - LMT 1906 Jun # Victoria ! 4:00 - SCT # Seychelles Time # Sierra Leone # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S *************** *** 506,512 **** Rule SL 1957 1962 - Sep 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Freetown -0:53:00 - LMT 1882 ! -0:53 - FMT 1913 Jun -1:00 SL AA%sT 1957 0:00 SL WA%sT --- 539,545 ---- Rule SL 1957 1962 - Sep 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Freetown -0:53:00 - LMT 1882 ! -0:53:00 - FMT 1913 Jun # Freetown Mean Time -1:00 SL AA%sT 1957 0:00 SL WA%sT *************** *** 537,549 **** # I verified this today by telephone with the Sudan Mission to the # United Nations: 212-573-6033 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Sudan 1970 only - May 1 0:00 1:00 " DST" Rule Sudan 1970 1985 - Oct 15 0:00 0 - ! Rule Sudan 1971 only - Apr 30 0:00 1:00 " DST" ! Rule Sudan 1972 1985 - Apr lastSun 0:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Khartoum 2:10:08 - LMT 1931 ! 2:00 Sudan EET%s # Swaziland # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 570,582 ---- # I verified this today by telephone with the Sudan Mission to the # United Nations: 212-573-6033 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Sudan 1970 only - May 1 0:00 1:00 S Rule Sudan 1970 1985 - Oct 15 0:00 0 - ! Rule Sudan 1971 only - Apr 30 0:00 1:00 S ! Rule Sudan 1972 1985 - Apr lastSun 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Khartoum 2:10:08 - LMT 1931 ! 2:00 Sudan EE%sT # Swaziland # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 567,600 **** # Tunisia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Tunisia 1939 only - Apr 15 23:00s 1:00 " DST" Rule Tunisia 1939 only - Nov 18 23:00s 0 - ! Rule Tunisia 1940 only - Feb 25 23:00s 1:00 " DST" Rule Tunisia 1941 only - Oct 6 0:00 0 - ! Rule Tunisia 1942 only - Mar 9 0:00 1:00 " DST" Rule Tunisia 1942 only - Nov 2 3:00 0 - ! Rule Tunisia 1943 only - Mar 29 2:00 1:00 " DST" Rule Tunisia 1943 only - Apr 17 2:00 0 - ! Rule Tunisia 1943 only - Apr 25 2:00 1:00 " DST" Rule Tunisia 1943 only - Oct 4 2:00 0 - ! Rule Tunisia 1944 1945 - Apr Mon>=1 2:00 1:00 " DST" Rule Tunisia 1944 only - Oct 8 0:00 0 - Rule Tunisia 1945 only - Sep 16 0:00 0 - ! Rule Tunisia 1977 only - Apr 30 0:00s 1:00 " DST" Rule Tunisia 1977 only - Sep 24 0:00s 0 - ! Rule Tunisia 1978 only - May 1 0:00s 1:00 " DST" Rule Tunisia 1978 only - Oct 1 0:00s 0 - ! Rule Tunisia 1988 only - Jun 1 0:00s 1:00 " DST" Rule Tunisia 1988 max - Sep lastSun 0:00s 0 - ! Rule Tunisia 1989 only - Mar 26 0:00s 1:00 " DST" ! Rule Tunisia 1990 only - May 1 0:00s 1:00 " DST" ! Rule Tunisia 1991 max - Mar lastSun 0:00s 1:00 " DST" # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Shanks says the 1911 switch occurred on Mar 9; go with Howse's Mar 11. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tunis 0:40:44 - LMT 1881 May 12 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 1:00 Tunisia MET%s # Uganda # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 600,633 ---- # Tunisia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Tunisia 1939 only - Apr 15 23:00s 1:00 S Rule Tunisia 1939 only - Nov 18 23:00s 0 - ! Rule Tunisia 1940 only - Feb 25 23:00s 1:00 S Rule Tunisia 1941 only - Oct 6 0:00 0 - ! Rule Tunisia 1942 only - Mar 9 0:00 1:00 S Rule Tunisia 1942 only - Nov 2 3:00 0 - ! Rule Tunisia 1943 only - Mar 29 2:00 1:00 S Rule Tunisia 1943 only - Apr 17 2:00 0 - ! Rule Tunisia 1943 only - Apr 25 2:00 1:00 S Rule Tunisia 1943 only - Oct 4 2:00 0 - ! Rule Tunisia 1944 1945 - Apr Mon>=1 2:00 1:00 S Rule Tunisia 1944 only - Oct 8 0:00 0 - Rule Tunisia 1945 only - Sep 16 0:00 0 - ! Rule Tunisia 1977 only - Apr 30 0:00s 1:00 S Rule Tunisia 1977 only - Sep 24 0:00s 0 - ! Rule Tunisia 1978 only - May 1 0:00s 1:00 S Rule Tunisia 1978 only - Oct 1 0:00s 0 - ! Rule Tunisia 1988 only - Jun 1 0:00s 1:00 S Rule Tunisia 1988 max - Sep lastSun 0:00s 0 - ! Rule Tunisia 1989 only - Mar 26 0:00s 1:00 S ! Rule Tunisia 1990 only - May 1 0:00s 1:00 S ! Rule Tunisia 1991 max - Mar lastSun 0:00s 1:00 S # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Shanks says the 1911 switch occurred on Mar 9; go with Howse's Mar 11. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Tunis 0:40:44 - LMT 1881 May 12 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 1:00 Tunisia CE%sT # Uganda # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 608,614 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Kinshasa 1:01:12 - LMT 1897 Nov 9 1:00 - CAT ! Zone Africa/Lumumbashi 1:49:52 - LMT 1897 Nov 9 2:00 - SAT # Zambia --- 641,647 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Africa/Kinshasa 1:01:12 - LMT 1897 Nov 9 1:00 - CAT ! Zone Africa/Lubumbashi 1:49:52 - LMT 1897 Nov 9 2:00 - SAT # Zambia =================================================================== RCS file: RCS/antarctica,v retrieving revision 1995.10 retrieving revision 1995.10.1.1 diff -c -r1995.10 -r1995.10.1.1 *** antarctica 1995/10/28 16:08:56 1995.10 --- antarctica 1996/09/03 23:48:46 1995.10.1.1 *************** *** 1,25 **** # @(#)antarctica 7.3 ! # From Arthur David Olson (February 13, 1988): ! # No data available. ! # Balleny Is ! # British Antarctic Territories include ! # South Orkney Is ! # South Shetland Is ! ! # Bouvet ! # uninhabited ! ! # French Southern and Antarctic Lands (no indigenous inhabitants) include ! # Amsterdam Island ! # Crozet Is ! # Kerguelen Is ! # St Paul Island ! ! # Heard Island, McDonald Is ! # uninhabited ! ! # Peter I Island # Scott Island --- 1,151 ---- # @(#)antarctica 7.3 ! # From Paul Eggert (1996-09-03): ! # To keep things manageable, we list only locations occupied year-round; ! # see <URL:http://earth.agu.org/amen/nations.html> (1996-05-24). ! # Unless otherwise specified, we have no time zone information. ! # ! # I made up all time zone abbreviations mentioned here; corrections welcome! ! # FORMAT is `___' and GMTOFF is 0 for locations while uninhabited. ! ! ! # Argentina - 6 year-round bases ! # General Belgrano II ! # 5 others ! ! # Australia - territories ! # Heard Island, McDonald Islands ! # ! # year-round bases ! # Casey, Bailey Peninsula, since 1969 ! # Davis, Vestfold Hills, since 1957-01-13 (except 1965-01 - 1969-02) ! # Mawson, Holme Bay, since 1954-02-13 ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Antarctica/Casey 0 - ___ 1969 ! 8:00 - WST # Western (Aus) Standard Time ! #Zone Antartica/Davis unknown ! Zone Antarctica/Mawson 0 - ___ 1954 Feb 13 ! 6:00 - MAWT # Mawson Time ! # References: ! # <URL:http://www.antdiv.gov.au/aad/exop/sfo/casey/casey_aws.html> (1996-07-15) ! # <URL:http://www.antdiv.gov.au/aad/exop/sfo/mawson/video.html> (1996-04-19) ! ! # Brazil - year-round base ! # Ferraz, King George Island, since 1983/4 ! ! # Chile - 4 year-round bases ! ! # China - year-round bases ! # Great Wall, King George Island, since 1985-02-20 ! # Zhongshan, Larsemann Hills, Prydz Bay, since 1989-02-26 ! ! # Finland - year-round base ! # Aboa, Queen Maud Land, since 1988 ! ! # France ! # ! # French Southern Territories with year-round inhabitants ! # Amsterdam Island ! # Crozet Islands ! # Kerguelen Islands ! # St Paul Island ! # ! # year-round base ! # Dumont d'Urville, Adelie Land, since IGY ! ! # Germany - year-round base ! # Georg von Neumayer ! ! # India - year-round base ! # Dakshin Gangotri ! ! # Japan - year-round bases ! # Dome Fuji ! # Syowa ! # S Korea - year-round base ! # King Sejong, King George Island, since 1988 ! # New Zealand - claims ! # Balleny Islands # Scott Island + # + # year-round base + # Scott, Ross Island, since 1957-01, is like Antarctica/McMurdo. + # + # These rules for New Zealand are stolen from the `australasia' file. + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule NZAQ 1974 only - Nov 3 2:00s 1:00 D + Rule NZAQ 1975 1988 - Oct lastSun 2:00s 1:00 D + Rule NZAQ 1989 only - Oct 8 2:00s 1:00 D + Rule NZAQ 1990 max - Oct Sun>=1 2:00s 1:00 D + Rule NZAQ 1975 only - Feb 23 2:00s 0 S + Rule NZAQ 1976 1989 - Mar Sun>=1 2:00s 0 S + Rule NZAQ 1990 max - Mar Sun>=15 2:00s 0 S + + # Norway - territories + # Bouvet (uninhabited) + # + # claims + # Peter I Island (uninhabited) + + # Poland - year-round base + # Arctowski, King George Island, since 1977 + + # Russia - year-round bases + # Bellingshausen, King George Island + # Mirny + # Molodezhnaya + # Novolazarevskaya + # Vostok + + # S Africa - year-round bases + # Marion Island + # Sanae + + # UK + # + # British Antarctic Territories (BAT) claims + # South Orkney Islands + # South Shetland Islands + # + # year-round bases + # Halley, Coates Land, -7535-2619, since 1956-01-06 + # Rothera, Adelaide Island, -6734-6808, since 1976-12-01 + + # Uruguay - year round base + # Artigas, King George Island + + # USA - year-round bases + # + # Palmer, Anvers Island + # + # McMurdo, Ross Island, since 1956 + # Zone NAME GMTOFF RULES FORMAT [UNTIL] + Zone Antarctica/McMurdo 0 - ___ 1956 + 12:00 NZAQ NZ%sT + # + # Amundsen-Scott, South Pole, since 1957-01-23 + # From Paul Eggert (1996-09-03): + # Normally it wouldn't have a separate entry, since it's like the + # larger Antarctica/McMurdo since 1970, but it's too famous to omit. + # + # From Chris Carrier <72157.3334(a)CompuServe.COM> (1996-06-27): + # Siple, the first commander of the South Pole station, + # stated that he would have liked to have kept GMT at the station, + # but that he found it more convenient to keep GMT+12 + # as supplies for the station were coming from McMurdo Sound, + # which was on GMT+12 because New Zealand was on GMT+12 all year + # at that time (1957). (Source: Siple's book 90 degrees SOUTH.) + # + # From Susan Smith <URL:http://www.cybertours.com/whs/pole10.html> + # (1995-11-13 16:24:56 +1300): We use the same time as McMurdo does. + # And they use the same time as Christchurch, NZ does.... + # One last quirk about South Pole time. + # All the electric clocks are usually wrong. + # Something about the generators running at 60.1hertz or something + # makes all of the clocks run fast. So every couple of days, + # we have to go around and set them back 5 minutes or so. + # Maybe if we let them run fast all of the time, we'd get to leave here sooner!! + # + Link Antarctica/McMurdo Antarctica/South_Pole =================================================================== RCS file: RCS/asia,v retrieving revision 1996.8 retrieving revision 1996.8.1.1 diff -c -r1996.8 -r1996.8.1.1 *** asia 1996/05/09 21:40:44 1996.8 --- asia 1996/09/03 23:48:46 1996.8.1.1 *************** *** 4,10 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), --- 4,10 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1995-07-24): # # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), *************** *** 25,66 **** # std dst # LMT Local Mean Time # LST Local Star Time (Russian ``mestnoe zvezdnoe vremya'') ! # 2:00 EET EET DST Eastern European Time # 2:00 IST IDT Israel # 3:00 AST ADT Arabia* ! # 3:00 BSK BSD Baku (was 4:00)* ! # 3:30 IST IDT Iran ! # 4:00 AMST AMDT Armenia (was 3:00) (was YSK, YSD)* ! # 4:00 TBSK TBSD Tbilisi (was 3:00)* ! # 4:00 GST GDT Gulf* ! # 4:30 AFT Afghanistan* ! # 5:00 ASK ASD Aktau (was SHSK, SHSD)* ! # 5:00 ASK ASD Ashkhabad (was 4:00)* ! # 5:00 BSK BSD Bishkek (was 6:00) (was FSK, FSD)* ! # 5:00 PKT Pakistan* ! # 5:00 TSK TSD Tashkent (was 6:00)* ! # 5:30 IST IST India ! # 5:45 NPT Nepal* ! # 6:00 AASK AASD Alma-Ata (was 5:00)* ! # 6:00 BGT Bengal, Bangladesh* ! # 6:00 DSK DSD Dushanbe (was 5:00)* ! # 6:30 BMT Burma* # 7:00 ICT Indochina* ! # 7:00 JVT Java* ! # 8:00 BNT Borneo, Brunei* ! # 8:00 CST CDT China ! # 8:00 HKT HKST Hong Kong ! # 8:00 PST PDT Philippines* ! # 8:00 SGT Singapore ! # 8:00 UST UDT Ulan Bator* ! # 9:00 JST JDT Japan ! # 9:00 KST KDT Korea ! # 9:00 MLT Moluccas* ! # 9:30 CST Australian Central Standard Time # # See the `europe' file for Russia and Turkey in Asia. # ! # See the `africa' file for Zone naming conventions. # From Guy Harris: # Incorporates data for Singapore from Robert Elz' asia 1.1, as well as --- 25,44 ---- # std dst # LMT Local Mean Time # LST Local Star Time (Russian ``mestnoe zvezdnoe vremya'') ! # 2:00 EET EEST Eastern European Time # 2:00 IST IDT Israel # 3:00 AST ADT Arabia* ! # 4:00 GST Gulf* ! # 5:30 IST India # 7:00 ICT Indochina* ! # 8:00 CST China ! # 9:00 JST Japan ! # 9:00 KST Korea ! # 9:30 CST (Australian) Central Standard Time # # See the `europe' file for Russia and Turkey in Asia. # ! # See the `africa' file for time zone naming and abbreviation conventions. # From Guy Harris: # Incorporates data for Singapore from Robert Elz' asia 1.1, as well as *************** *** 72,86 **** # These rules for Russia are stolen from the `europe' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule RussiaAsia 1981 1984 - Apr 1 0:00 1:00 D ! Rule RussiaAsia 1981 1983 - Oct 1 0:00 0 K ! Rule RussiaAsia 1984 max - Sep lastSun 2:00s 0 K ! Rule RussiaAsia 1985 max - Mar lastSun 2:00s 1:00 D # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kabul 4:36:48 - LMT 1890 ! 4:00 - GST 1945 4:30 - AFT # Armenia --- 50,64 ---- # These rules for Russia are stolen from the `europe' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule RussiaAsia 1981 1984 - Apr 1 0:00 1:00 S ! Rule RussiaAsia 1981 1983 - Oct 1 0:00 0 - ! Rule RussiaAsia 1984 max - Sep lastSun 2:00s 0 - ! Rule RussiaAsia 1985 max - Mar lastSun 2:00s 1:00 S # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kabul 4:36:48 - LMT 1890 ! 4:00 - AFT 1945 4:30 - AFT # Armenia *************** *** 90,119 **** # <edd(a)AIC.NET> reported today that Yerevan probably won't use DST this year, # though it did use DST in 1995. We guess Yerevan stayed in sync with Moscow # between 1990 and 1995, but stopped using DST in 1996. - # Der-Danieliantz also asked for a better abbreviation than `YSK' - # after independence. Apparently no abbreviation is in common use; - # use `AMST/AMDT' since `AM' is the ISO country code for Armenia. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Armenia 1992 1995 - Sep lastSun 2:00s 0 S ! Rule Armenia 1992 1995 - Mar lastSun 2:00s 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 ! 3:00 - YSK 1957 Mar ! 4:00 RussiaAsia YS%s 1991 Mar 31 2:00s ! 3:00 1:00 YSD 1991 Sep 29 2:00s ! 3:00 - AMST 1992 Jan 19 2:00s ! 4:00 Armenia AM%sT 1996 ! 4:00 - AMST # Azerbaijan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 ! 3:00 - BSK 1957 Mar ! 4:00 RussiaAsia BS%s 1991 Mar 31 2:00s ! 3:00 1:00 BSD 1991 Sep 29 2:00s ! 3:00 - BSK # Shanks has Baku using Russian DST rules after 1991, ! # but usno1995 has Azerbaijan with no DST. Go with usno1995. # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 68,94 ---- # <edd(a)AIC.NET> reported today that Yerevan probably won't use DST this year, # though it did use DST in 1995. We guess Yerevan stayed in sync with Moscow # between 1990 and 1995, but stopped using DST in 1996. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Armenia 1991 1995 - Mar lastSun 2:00s 1:00 S ! Rule Armenia 1991 1995 - Sep lastSun 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 ! 3:00 - YERT 1957 Mar # Yerevan Time ! 4:00 RussiaAsia YER%sT 1991 Mar 31 2:00s ! 3:00 1:00 YERST 1991 Sep 23 # independence ! 3:00 Armenia AM%sT 1992 Jan 19 2:00s # Armenia Time ! 4:00 Armenia AM%sT # Azerbaijan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 ! 3:00 - BAKT 1957 Mar # Baku Time ! 4:00 RussiaAsia BAK%sT 1991 Mar 31 2:00s ! 3:00 1:00 BAKST 1991 Aug 30 # independence ! 3:00 RussiaAsia AZ%sT 1992 # Azerbaijan Time ! 3:00 - AZT # Shanks has Baku using Russian DST rules after 1991, ! # but usno1995 has Azerbaijan with no DST. Guess no DST after 1991. # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 124,145 **** # Bangladesh # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dacca 6:01:40 - LMT 1890 ! 5:53 - CMT 1941 Oct # Calcutta Mean Time ! 6:30 - BMT 1942 May 15 5:30 - IST 1942 Sep ! 6:30 - BMT 1951 Sep 30 ! 6:00 - BGT # Bhutan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Thimbu 5:58:36 - LMT 1947 Aug 15 5:30 - IST 1987 Oct ! 6:00 - BGT # British Indian Ocean Territory # From Whitman: # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Chagos 5:00 - PKT # Brunei # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 99,121 ---- # Bangladesh # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dacca 6:01:40 - LMT 1890 ! 5:53:20 - HMT 1941 Oct # Howrah Mean Time? ! 6:30 - BURT 1942 May 15 # Burma Time 5:30 - IST 1942 Sep ! 6:30 - BURT 1951 Sep 30 ! 6:00 - DACT 1971 Mar 26 # Dacca Time ! 6:00 - BDT # Bangladesh Time # Bhutan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Thimbu 5:58:36 - LMT 1947 Aug 15 5:30 - IST 1987 Oct ! 6:00 - BTT # Bhutan Time # British Indian Ocean Territory # From Whitman: # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Chagos 5:00 - IOT # BIOT Time # Brunei # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 150,164 **** # Burma / Myanmar # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Rangoon 6:24:40 - LMT 1880 # or Yangon ! 6:25 - RMT 1920 ! 6:30 - BMT 1942 May 9:00 - JST 1945 May 3 ! 6:30 - BMT # Cambodia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Phnom_Penh 6:59:40 - LMT 1906 Jun 9 ! 7:06 - SMT 1911 Mar 11 0:01 # Saigon MT 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT --- 126,140 ---- # Burma / Myanmar # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Rangoon 6:24:40 - LMT 1880 # or Yangon ! 6:24:36 - RMT 1920 # Rangoon Mean Time? ! 6:30 - BURT 1942 May # Burma Time 9:00 - JST 1945 May 3 ! 6:30 - MMT # Myanmar Time # Cambodia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Phnom_Penh 6:59:40 - LMT 1906 Jun 9 ! 7:06:20 - SMT 1911 Mar 11 0:01 # Saigon MT? 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT *************** *** 187,194 **** # CHINA 9 H AHEAD OF UTC APR 17 - SEP 10 # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): ! # Shanks writes that China switched from the Chinese calendar on 1912 Feb 12. ! # He also writes that China has had a single time zone since 1980 May 1, # observing summer DST from 1986 through 1991; this contradicts Devine's # note about Time magazine, though apparently _something_ happened in 1986. # Go with Shanks for now. I made up names for the other pre-1980 time zones. --- 163,169 ---- # CHINA 9 H AHEAD OF UTC APR 17 - SEP 10 # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): ! # Shanks writes that China has had a single time zone since 1980 May 1, # observing summer DST from 1986 through 1991; this contradicts Devine's # note about Time magazine, though apparently _something_ happened in 1986. # Go with Shanks for now. I made up names for the other pre-1980 time zones. *************** *** 204,226 **** Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Harbin 8:26:44 - LMT 1928 ! 8:30 - MAT 1932 Mar # Manchuria 8:00 - CST 1940 ! 9:00 - KST 1966 May ! 8:30 - MAT 1980 May 8:00 PRC C%sT Zone Asia/Shanghai 8:05:52 - LMT 1928 8:00 Shang C%sT 1949 8:00 PRC C%sT Zone Asia/Chungking 7:06:20 - LMT 1928 ! 7:00 - ICT 1980 May 8:00 PRC C%sT Zone Asia/Urumqi 5:50:20 - LMT 1928 ! 6:00 - URT 1980 May # Urumqi 8:00 PRC C%sT Zone Asia/Kashgar 5:03:56 - LMT 1928 ! 5:30 - ETT 1940 # Eastern Turkestan ! 5:00 - ETT 1980 May 8:00 PRC C%sT ############################################################################### --- 179,201 ---- Rule PRC 1987 1991 - Apr Sun>=10 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Harbin 8:26:44 - LMT 1928 ! 8:30 - HART 1932 Mar # Harbin Time 8:00 - CST 1940 ! 9:00 - HART 1966 May ! 8:30 - HART 1980 May 8:00 PRC C%sT Zone Asia/Shanghai 8:05:52 - LMT 1928 8:00 Shang C%sT 1949 8:00 PRC C%sT Zone Asia/Chungking 7:06:20 - LMT 1928 ! 7:00 - CHUT 1980 May # Chungking Time 8:00 PRC C%sT Zone Asia/Urumqi 5:50:20 - LMT 1928 ! 6:00 - URUT 1980 May # Urumqi Time 8:00 PRC C%sT Zone Asia/Kashgar 5:03:56 - LMT 1928 ! 5:30 - KAST 1940 # Kashgar Time ! 5:00 - KAST 1980 May 8:00 PRC C%sT ############################################################################### *************** *** 263,307 **** Rule HK 1979 1980 - Oct Sun>=16 3:30 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Hong_Kong 7:36:36 - LMT 1904 Oct 30 ! 8:00 HK HK%sT # Macao # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Macao 1961 1962 - Mar Sun>=16 3:30 1:00 D ! Rule Macao 1961 1964 - Nov Sun>=1 3:30 0 S ! Rule Macao 1963 only - Mar Sun>=16 0:00 1:00 D ! Rule Macao 1964 only - Mar Sun>=16 3:30 1:00 D ! Rule Macao 1965 only - Mar Sun>=16 0:00 1:00 D ! Rule Macao 1965 only - Oct 31 0:00 0 S ! Rule Macao 1966 1971 - Apr Sun>=16 3:30 1:00 D ! Rule Macao 1966 1971 - Oct Sun>=16 3:30 0 S ! Rule Macao 1972 1974 - Apr Sun>=15 0:00 1:00 D ! Rule Macao 1972 1973 - Oct Sun>=15 0:00 0 S ! Rule Macao 1974 1977 - Oct Sun>=15 3:30 0 S ! Rule Macao 1975 1977 - Apr Sun>=15 3:30 1:00 D ! Rule Macao 1978 1980 - Apr Sun>=15 0:00 1:00 D ! Rule Macao 1978 1980 - Oct Sun>=15 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Macao 7:34:20 - LMT 1912 ! 8:00 Macao C%sT ############################################################################### # Cyprus # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Cyprus 1975 only - Apr 13 0:00 1:00 " DST" Rule Cyprus 1975 only - Oct 12 0:00 0 - ! Rule Cyprus 1976 only - May 15 0:00 1:00 " DST" Rule Cyprus 1976 only - Oct 11 0:00 0 - ! Rule Cyprus 1977 1980 - Apr Sun>=1 0:00 1:00 " DST" Rule Cyprus 1977 only - Sep 25 0:00 0 - Rule Cyprus 1978 only - Oct 2 0:00 0 - Rule Cyprus 1979 max - Sep lastSun 0:00 0 - ! Rule Cyprus 1981 max - Mar lastSun 0:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Nicosia 2:13:28 - LMT 1921 Nov 14 ! 2:00 Cyprus EET%s # Georgia # From Paul Eggert <eggert(a)twinsun.com> (1994-11-19): --- 238,284 ---- Rule HK 1979 1980 - Oct Sun>=16 3:30 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Hong_Kong 7:36:36 - LMT 1904 Oct 30 ! 8:00 HK HK%sT 1997 Jul 1 # return to China ! 8:00 PRC C%sT # Macao # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Macao 1961 1962 - Mar Sun>=16 3:30 1:00 S ! Rule Macao 1961 1964 - Nov Sun>=1 3:30 0 - ! Rule Macao 1963 only - Mar Sun>=16 0:00 1:00 S ! Rule Macao 1964 only - Mar Sun>=16 3:30 1:00 S ! Rule Macao 1965 only - Mar Sun>=16 0:00 1:00 S ! Rule Macao 1965 only - Oct 31 0:00 0 - ! Rule Macao 1966 1971 - Apr Sun>=16 3:30 1:00 S ! Rule Macao 1966 1971 - Oct Sun>=16 3:30 0 - ! Rule Macao 1972 1974 - Apr Sun>=15 0:00 1:00 S ! Rule Macao 1972 1973 - Oct Sun>=15 0:00 0 - ! Rule Macao 1974 1977 - Oct Sun>=15 3:30 0 - ! Rule Macao 1975 1977 - Apr Sun>=15 3:30 1:00 S ! Rule Macao 1978 1980 - Apr Sun>=15 0:00 1:00 S ! Rule Macao 1978 1980 - Oct Sun>=15 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Macao 7:34:20 - LMT 1912 ! 8:00 Macao MO%sT 1999 Dec 20 # return to China ! 8:00 PRC C%sT ############################################################################### # Cyprus # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Cyprus 1975 only - Apr 13 0:00 1:00 S Rule Cyprus 1975 only - Oct 12 0:00 0 - ! Rule Cyprus 1976 only - May 15 0:00 1:00 S Rule Cyprus 1976 only - Oct 11 0:00 0 - ! Rule Cyprus 1977 1980 - Apr Sun>=1 0:00 1:00 S Rule Cyprus 1977 only - Sep 25 0:00 0 - Rule Cyprus 1978 only - Oct 2 0:00 0 - Rule Cyprus 1979 max - Sep lastSun 0:00 0 - ! Rule Cyprus 1981 max - Mar lastSun 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Nicosia 2:13:28 - LMT 1921 Nov 14 ! 2:00 Cyprus EE%sT # Georgia # From Paul Eggert <eggert(a)twinsun.com> (1994-11-19): *************** *** 316,333 **** # Most likely we're still missing some rule changes between 1991 and 1994. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tbilisi 2:59:16 - LMT 1880 ! 2:59 - LST 1924 May 2 ! 3:00 - TBSK 1957 Mar ! 4:00 RussiaAsia TBS%s 1991 Mar 31 2:00s ! 3:00 1:00 TBSD 1991 Sep 29 2:00s ! 3:00 RussiaAsia TBS%s 1994 Sep 25 2:00s ! 4:00 - TBSK # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Calcutta 5:53:28 - LMT 1880 ! 5:53 - CMT 1941 Oct # Calcutta Mean Time ! 6:30 - BMT 1942 May 15 5:30 - IST 1942 Sep 5:30 1:00 IST 1945 Oct 15 5:30 - IST --- 293,310 ---- # Most likely we're still missing some rule changes between 1991 and 1994. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tbilisi 2:59:16 - LMT 1880 ! 2:59:16 - TBMT 1924 May 2 # Tbilisi Mean Time ! 3:00 - TBIT 1957 Mar # Tbilisi Time ! 4:00 RussiaAsia TBI%sT 1991 Mar 31 2:00s ! 3:00 1:00 TBIST 1991 Apr 9 # independence ! 3:00 RussiaAsia GE%sT 1994 Sep 25 2:00s # Georgia Time ! 4:00 - GET # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Calcutta 5:53:28 - LMT 1880 ! 5:53:20 - HMT 1941 Oct # Howrah Mean Time? ! 6:30 - BURT 1942 May 15 # Burma Time 5:30 - IST 1942 Sep 5:30 1:00 IST 1945 Oct 15 5:30 - IST *************** *** 339,374 **** # Indonesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jakarta 7:07:12 - LMT 1867 Aug 10 ! 7:07 - JMT 1924 Jan 1 0:13 ! 7:20 - JVT 1932 Nov ! 7:30 - JVT 1942 Mar 23 9:00 - JST 1945 Aug ! 7:30 - JVT 1948 May ! 8:00 - JVT 1950 May ! 7:30 - JVT 1964 ! 7:00 - JVT Zone Asia/Ujung_Pandang 7:57:36 - LMT 1920 ! 7:58 - MMT 1932 Nov # Macassar Mean Time ! 8:00 - BNT 1942 Feb 9 9:00 - JST 1945 Aug ! 8:00 - BNT Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov ! 9:00 - MLT 1944 9:30 - CST 1964 ! 9:00 - MLT # Iran # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Iran 1978 1980 - Mar 21 0:00 1:00 D ! Rule Iran 1978 only - Oct 21 0:00 0 S ! Rule Iran 1979 only - Sep 19 0:00 0 S ! Rule Iran 1980 only - Sep 23 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 ! 3:26 - TMT 1946 ! 3:30 - IST 1977 Nov ! 4:00 Iran G%sT 1979 ! 3:30 Iran I%sT # Iraq # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 316,351 ---- # Indonesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jakarta 7:07:12 - LMT 1867 Aug 10 ! 7:07:12 - JMT 1924 Jan 1 0:13 # Jakarta MT ! 7:20 - JAVT 1932 Nov # Java Time ! 7:30 - JAVT 1942 Mar 23 9:00 - JST 1945 Aug ! 7:30 - JAVT 1948 May ! 8:00 - JAVT 1950 May ! 7:30 - JAVT 1964 ! 7:00 - JAVT Zone Asia/Ujung_Pandang 7:57:36 - LMT 1920 ! 7:57:36 - MMT 1932 Nov # Macassar MT ! 8:00 - BORT 1942 Feb 9 # Borneo Time 9:00 - JST 1945 Aug ! 8:00 - BORT Zone Asia/Jayapura 9:22:48 - LMT 1932 Nov ! 9:00 - JAYT 1944 # Jayapura Time 9:30 - CST 1964 ! 9:00 - JAYT # Iran # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Iran 1978 1980 - Mar 21 0:00 1:00 S ! Rule Iran 1978 only - Oct 21 0:00 0 - ! Rule Iran 1979 only - Sep 19 0:00 0 - ! Rule Iran 1980 only - Sep 23 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tehran 3:25:44 - LMT 1916 ! 3:25:44 - TMT 1946 # Tehran Mean Time ! 3:30 - IRT 1977 Nov ! 4:00 Iran IR%sT 1979 ! 3:30 Iran IR%sT # Iraq # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S *************** *** 380,386 **** Rule Iraq 1986 max - Mar lastSun 1:00s 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 ! 2:58 - BMT 1918 # Baghdad Mean Time 3:00 - AST 1982 May 3:00 Iraq A%sT --- 357,363 ---- Rule Iraq 1986 max - Mar lastSun 1:00s 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baghdad 2:57:40 - LMT 1890 ! 2:57:36 - BMT 1918 # Baghdad Mean Time? 3:00 - AST 1982 May 3:00 Iraq A%sT *************** *** 440,451 **** Rule Zion 1987 only - Sep 13 0:00 0 S Rule Zion 1988 only - Apr 9 0:00 1:00 D Rule Zion 1988 only - Sep 3 0:00 0 S - #Rule Zion 1989 only - Apr 29 0:00 1:00 D - #Rule Zion 1989 only - Sep 2 0:00 0 S - #Rule Zion 1990 only - Mar 25 0:00 1:00 D - #Rule Zion 1990 only - Aug 26 0:00 0 S - #Rule Zion 1991 only - Mar 10 0:00 1:00 D - #Rule Zion 1991 only - Sep 1 0:00 0 S # From Ephraim Silverberg (1996-01-02): # --- 417,422 ---- *************** *** 466,490 **** # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0:00 S Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0:00 S Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0:00 S Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0:00 S Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0:00 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the switchboard at 972-2-701411 and asking for the spokeswoman. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0:00 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0:00 S # The dates for 1996-1998 were also obtained from Office of the Spokeswoman # for the Ministry of Interior, Jerusalem, Israel. The official announcement --- 437,461 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1989 only - Apr 30 0:00 1:00 D ! Rule Zion 1989 only - Sep 3 0:00 0 S Rule Zion 1990 only - Mar 25 0:00 1:00 D ! Rule Zion 1990 only - Aug 26 0:00 0 S Rule Zion 1991 only - Mar 24 0:00 1:00 D ! Rule Zion 1991 only - Sep 1 0:00 0 S Rule Zion 1992 only - Mar 29 0:00 1:00 D ! Rule Zion 1992 only - Sep 6 0:00 0 S Rule Zion 1993 only - Apr 2 0:00 1:00 D ! Rule Zion 1993 only - Sep 5 0:00 0 S # The dates for 1994-1995 were obtained from Office of the Spokeswoman for the # Ministry of Interior, Jerusalem, Israel. The spokeswoman can be reached by # calling the switchboard at 972-2-701411 and asking for the spokeswoman. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Zion 1994 only - Apr 1 0:00 1:00 D ! Rule Zion 1994 only - Aug 28 0:00 0 S ! Rule Zion 1995 only - Mar 31 0:00 1:00 D ! Rule Zion 1995 only - Sep 3 0:00 0 S # The dates for 1996-1998 were also obtained from Office of the Spokeswoman # for the Ministry of Interior, Jerusalem, Israel. The official announcement *************** *** 504,515 **** # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1996 1998 - Mar Fri>=14 0:00 1:00 D ! Rule Zion 1996 only - Sep 16 0:00 0:00 S ! Rule Zion 1997 1998 - Oct Sun>=14 0:00 0:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 ! 2:21 - JMT 1918 2:00 Zion I%sT --- 475,486 ---- # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1996 1998 - Mar Fri>=14 0:00 1:00 D ! Rule Zion 1996 only - Sep 16 0:00 0 S ! Rule Zion 1997 1998 - Oct Sun>=14 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 ! 2:20:40 - JMT 1918 # Jerusalem Mean Time? 2:00 Zion I%sT *************** *** 531,559 **** #Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # but the only locations using it were US military bases. # We go with Shanks and omit daylight saving in those years for Asia/Tokyo. - # - # The same news article also reports that Japan is likely to go on DST in 1996 - # as follows, where I've guessed the AT and LETTER/S columns: - # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S - #Rule Japan 1996 max - Apr Sun>=1 2:00 1:00 D - #Rule Japan 1996 max - Oct lastSun 2:00 0 S - # From Shanks (1991): - # Japan switched from the Japanese calendar on 1893 Jan 1. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tokyo 9:19:04 - LMT 1896 9:00 - JST ! # If Japan adopts DST in 1996, replace the above line with the following lines: ! # 9:00 - JST 1996 ! # 9:00 Japan J%sT ! # and uncomment the two `Rule' lines commented out above. ! ! # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): ! # Shanks says that the far southern Ryukyu Is (Nansei-Shoto) are 8:00, ! # but we haven't confirmed this. ! # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! #Zone Asia/Ishigaki 8:16:36 - LMT 1896 ! # 8:00 - CST # There is no information for Marcus. # Other Japanese possessions are probably like Asia/Tokyo. --- 502,513 ---- #Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D # but the only locations using it were US military bases. # We go with Shanks and omit daylight saving in those years for Asia/Tokyo. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tokyo 9:19:04 - LMT 1896 9:00 - JST ! Zone Asia/Ishigaki 8:16:36 - LMT 1896 ! 8:00 - CST # There is no information for Marcus. # Other Japanese possessions are probably like Asia/Tokyo. *************** *** 562,587 **** # Most likely Shanks is merely guessing dates from 1992 on. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Jordan 1973 only - Jun 6 0:00 1:00 " DST" Rule Jordan 1973 1975 - Oct 1 0:00 0 - ! Rule Jordan 1974 1977 - May 1 0:00 1:00 " DST" Rule Jordan 1976 only - Nov 1 0:00 0 - Rule Jordan 1977 only - Oct 1 0:00 0 - ! Rule Jordan 1978 only - Apr 30 0:00 1:00 " DST" Rule Jordan 1978 only - Sep 30 0:00 0 - ! Rule Jordan 1985 only - Apr 1 0:00 1:00 " DST" Rule Jordan 1985 only - Oct 1 0:00 0 - ! Rule Jordan 1986 1988 - Apr Fri>=1 0:00 1:00 " DST" Rule Jordan 1986 1990 - Oct Fri>=1 0:00 0 - ! Rule Jordan 1989 only - May 8 0:00 1:00 " DST" ! Rule Jordan 1990 only - Apr 27 0:00 1:00 " DST" ! Rule Jordan 1991 only - Apr 19 0:00 1:00 " DST" Rule Jordan 1991 only - Sep 27 0:00 0 - ! Rule Jordan 1992 max - Apr Fri>=1 0:00 1:00 " DST" Rule Jordan 1992 max - Oct Fri>=1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Amman 2:23:44 - LMT 1931 ! 2:00 Jordan EET%s # Kazakhstan # From Paul Eggert (1996-04-19): --- 516,541 ---- # Most likely Shanks is merely guessing dates from 1992 on. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Jordan 1973 only - Jun 6 0:00 1:00 S Rule Jordan 1973 1975 - Oct 1 0:00 0 - ! Rule Jordan 1974 1977 - May 1 0:00 1:00 S Rule Jordan 1976 only - Nov 1 0:00 0 - Rule Jordan 1977 only - Oct 1 0:00 0 - ! Rule Jordan 1978 only - Apr 30 0:00 1:00 S Rule Jordan 1978 only - Sep 30 0:00 0 - ! Rule Jordan 1985 only - Apr 1 0:00 1:00 S Rule Jordan 1985 only - Oct 1 0:00 0 - ! Rule Jordan 1986 1988 - Apr Fri>=1 0:00 1:00 S Rule Jordan 1986 1990 - Oct Fri>=1 0:00 0 - ! Rule Jordan 1989 only - May 8 0:00 1:00 S ! Rule Jordan 1990 only - Apr 27 0:00 1:00 S ! Rule Jordan 1991 only - Apr 19 0:00 1:00 S Rule Jordan 1991 only - Sep 27 0:00 0 - ! Rule Jordan 1992 max - Apr Fri>=1 0:00 1:00 S Rule Jordan 1992 max - Oct Fri>=1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Amman 2:23:44 - LMT 1931 ! 2:00 Jordan EE%sT # Kazakhstan # From Paul Eggert (1996-04-19): *************** *** 590,614 **** # in western Kazakhstan. Follow Shanks before 1991, Evtichov afterwards. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Alma-Ata 5:07:48 - LMT 1924 May 2 # or Almaty ! 5:00 - AASK 1957 Mar ! 6:00 RussiaAsia AAS%s 1991 Mar 31 2:00s ! 5:00 1:00 AASD 1991 Sep 29 2:00s ! 5:00 - AASK 1992 Jan 19 2:00s ! 6:00 RussiaAsia AAS%s Zone Asia/Aktau 3:21:04 - LMT 1924 May 2 # or Aqtau ! 4:00 - SHSK 1957 Mar # Fort Shevchenko ! 5:00 RussiaAsia SHS%s 1991 Mar 31 2:00s ! 4:00 1:00 ASD 1991 Sep 29 2:00s ! 4:00 - ASK 1992 Jan 19 2:00s ! 5:00 RussiaAsia AS%s # Kirgizstan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 ! 5:00 - FSK 1957 Mar # Frunze ! 6:00 RussiaAsia FS%s 1991 Mar 31 2:00s ! 5:00 1:00 FSD 1991 Sep 29 2:00s ! 5:00 RussiaAsia BS%s ############################################################################### --- 544,568 ---- # in western Kazakhstan. Follow Shanks before 1991, Evtichov afterwards. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Alma-Ata 5:07:48 - LMT 1924 May 2 # or Almaty ! 5:00 - ALMT 1957 Mar # Alma-Ata Time ! 6:00 RussiaAsia ALM%sT 1991 Mar 31 2:00s ! 5:00 1:00 ALMST 1991 Sep 29 2:00s ! 5:00 - ALMT 1992 Jan 19 2:00s ! 6:00 RussiaAsia ALM%sT Zone Asia/Aktau 3:21:04 - LMT 1924 May 2 # or Aqtau ! 4:00 - SHET 1957 Mar # Fort Shevchenko Time ! 5:00 RussiaAsia SHE%sT 1991 Mar 31 2:00s ! 4:00 1:00 AKTST 1991 Sep 29 2:00s ! 4:00 - AKTT 1992 Jan 19 2:00s # Aktau Time ! 5:00 RussiaAsia AKT%sT # Kirgizstan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bishkek 4:58:24 - LMT 1924 May 2 ! 5:00 - FRUT 1957 Mar # Frunze Time ! 6:00 RussiaAsia FRU%sT 1991 Mar 31 2:00s ! 5:00 1:00 FRUST 1991 Aug 31 # independence ! 5:00 RussiaAsia KG%sT # Kirgizstan Time ############################################################################### *************** *** 653,733 **** # Laos # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Vientiane 6:50:24 - LMT 1906 Jun 9 ! 7:06 - SMT 1911 Mar 11 0:01 # Saigon MT 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT # Lebanon # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Lebanon 1920 only - Mar 28 0:00 1:00 " DST" Rule Lebanon 1920 only - Oct 25 0:00 0 - ! Rule Lebanon 1921 only - Apr 3 0:00 1:00 " DST" Rule Lebanon 1921 only - Oct 3 0:00 0 - ! Rule Lebanon 1922 only - Mar 26 0:00 1:00 " DST" Rule Lebanon 1922 only - Oct 8 0:00 0 - ! Rule Lebanon 1923 only - Apr 22 0:00 1:00 " DST" Rule Lebanon 1923 only - Sep 16 0:00 0 - ! Rule Lebanon 1957 1961 - May 1 0:00 1:00 " DST" Rule Lebanon 1957 1961 - Oct 1 0:00 0 - ! Rule Lebanon 1972 only - Jun 22 0:00 1:00 " DST" Rule Lebanon 1972 1977 - Oct 1 0:00 0 - ! Rule Lebanon 1973 1977 - May 1 0:00 1:00 " DST" ! Rule Lebanon 1978 only - Apr 30 0:00 1:00 " DST" Rule Lebanon 1978 only - Sep 30 0:00 0 - ! Rule Lebanon 1984 1987 - May 1 0:00 1:00 " DST" Rule Lebanon 1984 max - Oct 16 0:00 0 - ! Rule Lebanon 1988 only - Jun 1 0:00 1:00 " DST" ! Rule Lebanon 1989 only - May 10 0:00 1:00 " DST" ! Rule Lebanon 1990 max - May 1 0:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Beirut 2:22:00 - LMT 1880 ! 2:00 Lebanon EET%s # Malaysia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kuala_Lumpur 6:46:48 - LMT 1880 ! 6:55 - SMT 1905 Jun ! 7:00 - SGT 1933 ! 7:20 - SGT 1942 Feb 15 9:00 - JST 1945 Sep 2 ! 7:20 - SGT 1950 ! 7:30 - SGT 1982 May ! 8:00 - SGT # Maldives # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Maldives 4:54:00 - LMT 1880 # Male ! 4:54 - MMT 1960 ! 5:00 - PKT # Mongolia ! # Shanks says that Mongolia has three time zones, ! # but usno1995 and http://www.odci.gov/cia/publications/95fact/802389h.gif # both say that it has just one. # Let's comment out the western and eastern Mongolian time zones # till we know what their principal towns are. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Mongol 1981 1984 - Apr 1 0:00 1:00 T ! Rule Mongol 1981 1984 - Oct 1 0:00 0 S ! Rule Mongol 1985 max - Mar lastSun 2:00 1:00 T ! Rule Mongol 1985 max - Sep lastSun 3:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug ! # 6:00 - DST 1978 ! # 7:00 Mongol D%sT Zone Asia/Ulan_Bator 7:07:32 - LMT 1905 Aug ! 7:00 - UST 1978 ! 8:00 Mongol U%sT #Zone Asia/Baruun-Urt 7:33:00 - LMT 1905 Aug ! # 8:00 - BST 1978 ! # 9:00 Mongol B%sT # Nepal # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Katmandu 5:41:16 - LMT 1920 5:30 - IST 1986 ! 5:45 - NPT # Oman # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 607,696 ---- # Laos # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Vientiane 6:50:24 - LMT 1906 Jun 9 ! 7:06:20 - SMT 1911 Mar 11 0:01 # Saigon MT? 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT # Lebanon # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Lebanon 1920 only - Mar 28 0:00 1:00 S Rule Lebanon 1920 only - Oct 25 0:00 0 - ! Rule Lebanon 1921 only - Apr 3 0:00 1:00 S Rule Lebanon 1921 only - Oct 3 0:00 0 - ! Rule Lebanon 1922 only - Mar 26 0:00 1:00 S Rule Lebanon 1922 only - Oct 8 0:00 0 - ! Rule Lebanon 1923 only - Apr 22 0:00 1:00 S Rule Lebanon 1923 only - Sep 16 0:00 0 - ! Rule Lebanon 1957 1961 - May 1 0:00 1:00 S Rule Lebanon 1957 1961 - Oct 1 0:00 0 - ! Rule Lebanon 1972 only - Jun 22 0:00 1:00 S Rule Lebanon 1972 1977 - Oct 1 0:00 0 - ! Rule Lebanon 1973 1977 - May 1 0:00 1:00 S ! Rule Lebanon 1978 only - Apr 30 0:00 1:00 S Rule Lebanon 1978 only - Sep 30 0:00 0 - ! Rule Lebanon 1984 1987 - May 1 0:00 1:00 S Rule Lebanon 1984 max - Oct 16 0:00 0 - ! Rule Lebanon 1988 only - Jun 1 0:00 1:00 S ! Rule Lebanon 1989 only - May 10 0:00 1:00 S ! Rule Lebanon 1990 max - May 1 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Beirut 2:22:00 - LMT 1880 ! 2:00 Lebanon EE%sT # Malaysia + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S + Rule NBorneo 1935 1941 - Sep 14 0:00 0:20 TS + Rule NBorneo 1935 1941 - Dec 14 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Kuala_Lumpur 6:46:48 - LMT 1880 ! 6:55:24 - SMT 1905 Jun # Singapore Mean Time ! 7:00 - MALT 1933 # Malaya Time ! 7:20 - MALT 1942 Feb 15 9:00 - JST 1945 Sep 2 ! 7:20 - MALT 1950 ! 7:30 - MALT 1982 May ! 8:00 - MYT # Malaysia Time ! Zone Asia/Kuching 7:21:20 - LMT 1926 Mar ! 7:30 - BORT 1933 # Borneo Time ! 8:00 NBorneo BOR%sT 1942 ! 9:00 - JST 1945 Sep 2 ! 8:00 - BORT 1982 May ! 8:00 - MYT # Maldives # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Maldives 4:54:00 - LMT 1880 # Male ! 4:54:00 - MMT 1960 # Male Mean Time ! 5:00 - MVT # Maldives Time # Mongolia ! # Shanks says that Mongolia has three time zones, but usno1995 and ! # <URL:http://www.odci.gov/cia/publications/95fact/802389h.gif> (1995) # both say that it has just one. # Let's comment out the western and eastern Mongolian time zones # till we know what their principal towns are. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Mongol 1981 1984 - Apr 1 0:00 1:00 S ! Rule Mongol 1981 1984 - Oct 1 0:00 0 - ! Rule Mongol 1985 max - Mar lastSun 2:00 1:00 S ! Rule Mongol 1985 max - Sep lastSun 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] #Zone Asia/Dariv 6:14:32 - LMT 1905 Aug ! # 6:00 - DART 1978 # Dariv Time ! # 7:00 Mongol DAR%sT Zone Asia/Ulan_Bator 7:07:32 - LMT 1905 Aug ! 7:00 - ULAT 1978 # Ulan Bator Time ! 8:00 Mongol ULA%sT #Zone Asia/Baruun-Urt 7:33:00 - LMT 1905 Aug ! # 8:00 - BART 1978 # Baruun-Urt Time ! # 9:00 Mongol BAR%sT # Nepal # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Katmandu 5:41:16 - LMT 1920 5:30 - IST 1986 ! 5:45 - NPT # Nepal Time # Oman # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 740,762 **** 5:30 - IST 1942 Sep 5:30 1:00 IST 1945 Oct 15 5:30 - IST 1951 Sep 30 ! 5:00 - PKT # Palestine # These rules for Egypt are stolen from the `africa' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule EgyptAsia 1957 only - May 10 0:00 1:00 " DST" Rule EgyptAsia 1957 1958 - Oct 1 0:00 0 - ! Rule EgyptAsia 1958 only - May 1 0:00 1:00 " DST" ! Rule EgyptAsia 1959 1981 - May 1 1:00 1:00 " DST" Rule EgyptAsia 1959 1965 - Sep 30 3:00 0 - Rule EgyptAsia 1966 max - Oct 1 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 - EET 1957 May 10 ! 2:00 EgyptAsia EET%s 1967 Jun 30 2:00 Zion I%sT - # This will undoubtedly change soon. # Paracel Is # no information --- 703,725 ---- 5:30 - IST 1942 Sep 5:30 1:00 IST 1945 Oct 15 5:30 - IST 1951 Sep 30 ! 5:00 - KART 1971 Mar 26 # Karachi Time ! 5:00 - PKT # Pakistan Time # Palestine # These rules for Egypt are stolen from the `africa' file. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule EgyptAsia 1957 only - May 10 0:00 1:00 S Rule EgyptAsia 1957 1958 - Oct 1 0:00 0 - ! Rule EgyptAsia 1958 only - May 1 0:00 1:00 S ! Rule EgyptAsia 1959 1981 - May 1 1:00 1:00 S Rule EgyptAsia 1959 1965 - Sep 30 3:00 0 - Rule EgyptAsia 1966 max - Oct 1 3:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Gaza 2:17:52 - LMT 1900 Oct 2:00 - EET 1957 May 10 ! 2:00 EgyptAsia EE%sT 1967 Jun 30 2:00 Zion I%sT # Paracel Is # no information *************** *** 765,782 **** # Howse writes (p 162) that until 1844 the Philippines kept American date. # The rest of this data is from Shanks. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Phil 1936 only - Nov 1 0:00 1:00 D ! Rule Phil 1937 only - Feb 1 0:00 0 S ! Rule Phil 1954 only - Apr 12 0:00 1:00 D ! Rule Phil 1954 only - Jul 1 0:00 0 S ! Rule Phil 1978 only - Mar 22 0:00 1:00 D ! Rule Phil 1978 only - Sep 21 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Manila -15:56:00 - LMT 1844 8:04:00 - LMT 1899 May 11 ! 8:00 Phil P%sT 1942 May 9:00 - JST 1944 Nov ! 8:00 Phil P%sT # Qatar # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 728,745 ---- # Howse writes (p 162) that until 1844 the Philippines kept American date. # The rest of this data is from Shanks. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Phil 1936 only - Nov 1 0:00 1:00 S ! Rule Phil 1937 only - Feb 1 0:00 0 - ! Rule Phil 1954 only - Apr 12 0:00 1:00 S ! Rule Phil 1954 only - Jul 1 0:00 0 - ! Rule Phil 1978 only - Mar 22 0:00 1:00 S ! Rule Phil 1978 only - Sep 21 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Manila -15:56:00 - LMT 1844 8:04:00 - LMT 1899 May 11 ! 8:00 Phil PH%sT 1942 May 9:00 - JST 1944 Nov ! 8:00 Phil PH%sT # Qatar # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 792,869 **** # Singapore # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Singapore 6:55:24 - LMT 1880 ! 6:55 - SMT 1905 Jun ! 7:00 - SGT 1933 ! 7:20 - SGT 1942 Feb 15 9:00 - JST 1945 Sep 2 ! 7:20 - SGT 1950 ! 7:30 - SGT 1982 May 8:00 - SGT # Spratly Is # no information # Sri Lanka # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Colombo 5:19:24 - LMT 1880 ! 5:20 - JMT 1906 5:30 - IST 1942 Jan 5 5:30 0:30 IHST 1942 Sep 5:30 1:00 IST 1945 Oct 16 2:00 ! 5:30 - IST # Syria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Syria 1920 1923 - Apr Sun>=15 2:00 1:00 " DST" Rule Syria 1920 1923 - Oct Sun>=1 2:00 0 - ! Rule Syria 1962 only - Apr 29 2:00 1:00 " DST" Rule Syria 1962 only - Oct 1 2:00 0 - ! Rule Syria 1963 1965 - May 1 2:00 1:00 " DST" Rule Syria 1963 only - Sep 30 2:00 0 - Rule Syria 1964 only - Oct 1 2:00 0 - Rule Syria 1965 only - Sep 30 2:00 0 - ! Rule Syria 1966 only - Apr 24 2:00 1:00 " DST" Rule Syria 1966 1976 - Oct 1 2:00 0 - ! Rule Syria 1967 1978 - May 1 2:00 1:00 " DST" Rule Syria 1977 1978 - Sep 1 2:00 0 - ! Rule Syria 1983 1984 - Apr 9 2:00 1:00 " DST" Rule Syria 1983 1984 - Oct 1 2:00 0 - ! Rule Syria 1986 only - Feb 16 2:00 1:00 " DST" Rule Syria 1986 only - Oct 9 2:00 0 - ! Rule Syria 1987 only - Mar 1 2:00 1:00 " DST" Rule Syria 1987 1988 - Oct 31 2:00 0 - ! Rule Syria 1988 only - Mar 15 2:00 1:00 " DST" ! Rule Syria 1989 only - Mar 31 2:00 1:00 " DST" Rule Syria 1989 only - Oct 1 2:00 0 - ! Rule Syria 1990 max - Apr 1 2:00 1:00 " DST" Rule Syria 1990 max - Sep 30 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Damascus 2:25:12 - LMT 1920 ! 2:00 Syria EET%s # Tajikistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 ! 5:00 - DSK 1957 Mar ! 6:00 RussiaAsia DS%s 1991 ! 6:00 - DSK ! # Shanks has Dushanbe at 5:00 (6:00 summer) after 1991 Sep 29 3:00, ! # but usno1995 has it at 6:00. Go with usno1995. # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bangkok 6:42:04 - LMT 1880 ! 6:42 - BMT 1920 Apr 7:00 - ICT # Turkmenistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 ! 4:00 - ASK 1957 Mar ! 5:00 RussiaAsia AS%s 1991 ! 5:00 - ASK ! # Shanks has Ashkhabad at 4:00 (5:00 summer) after 1991 Sep 20 3:00, ! # but usno has it at 5:00. Go with usno1995. # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 755,847 ---- # Singapore # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Singapore 6:55:24 - LMT 1880 ! 6:55:24 - SMT 1905 Jun # Singapore Mean Time ! 7:00 - MALT 1933 # Malaya Time ! 7:20 - MALT 1942 Feb 15 9:00 - JST 1945 Sep 2 ! 7:20 - MALT 1950 ! 7:30 - MALT 1965 Aug 9 # independence ! 7:30 - SGT 1982 May # Singapore Time 8:00 - SGT # Spratly Is # no information # Sri Lanka + # From Paul Eggert (1996-09-03): + # <URL:http://www.virtual-pc.com/lankaweb/news/items/240596-2.html> (1996-05-24) + # reported ``the country's standard time will be put forward by one hour at + # midnight Friday (1830 GMT) `in the light of the present power crisis'.'' + # Transitions before 1996 are from Shanks (1991). + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Colombo 5:19:24 - LMT 1880 ! 5:20 - CEYT 1906 # Ceylon Time 5:30 - IST 1942 Jan 5 5:30 0:30 IHST 1942 Sep 5:30 1:00 IST 1945 Oct 16 2:00 ! 5:30 - IST 1996 May 25 0:00 ! 6:30 - LKT # Sri Lanka Time # Syria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Syria 1920 1923 - Apr Sun>=15 2:00 1:00 S Rule Syria 1920 1923 - Oct Sun>=1 2:00 0 - ! Rule Syria 1962 only - Apr 29 2:00 1:00 S Rule Syria 1962 only - Oct 1 2:00 0 - ! Rule Syria 1963 1965 - May 1 2:00 1:00 S Rule Syria 1963 only - Sep 30 2:00 0 - Rule Syria 1964 only - Oct 1 2:00 0 - Rule Syria 1965 only - Sep 30 2:00 0 - ! Rule Syria 1966 only - Apr 24 2:00 1:00 S Rule Syria 1966 1976 - Oct 1 2:00 0 - ! Rule Syria 1967 1978 - May 1 2:00 1:00 S Rule Syria 1977 1978 - Sep 1 2:00 0 - ! Rule Syria 1983 1984 - Apr 9 2:00 1:00 S Rule Syria 1983 1984 - Oct 1 2:00 0 - ! Rule Syria 1986 only - Feb 16 2:00 1:00 S Rule Syria 1986 only - Oct 9 2:00 0 - ! Rule Syria 1987 only - Mar 1 2:00 1:00 S Rule Syria 1987 1988 - Oct 31 2:00 0 - ! Rule Syria 1988 only - Mar 15 2:00 1:00 S ! Rule Syria 1989 only - Mar 31 2:00 1:00 S Rule Syria 1989 only - Oct 1 2:00 0 - ! Rule Syria 1990 max - Apr 1 2:00 1:00 S Rule Syria 1990 max - Sep 30 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Damascus 2:25:12 - LMT 1920 ! 2:00 Syria EE%sT # Tajikistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 ! 5:00 - DUST 1957 Mar # Dushanbe Time ! 6:00 RussiaAsia DUS%sT 1991 Mar 31 2:00s ! 5:00 1:00 DUSST 1991 Sep 9 # independence ! 5:00 RussiaAsia TJ%sT 1992 ! 5:00 - TJT # Tajikistan Time ! # Shanks has Dushanbe at 5:00 (6:00 summer) after 1991, ! # but a cable from the American Embassy at Dushanbe ! # <URL:http://www.itaiep.doc.gov/bisnis/cables/960703ti.html> (1996-07-02) ! # says that Tajikistan is at 5:00. Guess no DST after 1991. # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Bangkok 6:42:04 - LMT 1880 ! 6:42:04 - BMT 1920 Apr # Bangkok Mean Time 7:00 - ICT # Turkmenistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 # or Ashgabat ! 4:00 - ASHT 1957 Mar # Ashkhabad Time ! 5:00 RussiaAsia ASH%sT 1991 Mar 31 2:00s ! 4:00 1:00 ASHST 1991 Oct 27 # independence ! 4:00 RussiaAsia TM%sT 1992 # Turkmenistan Time ! 4:00 - TMT ! # Shanks has Ashkhabad at 4:00 (5:00 summer) after 1991, but ! # DHL <URL:http://www.dhl.com/dhlinfo/country/turkmeni.html> (1996-07-26) ! # reports 4:00. Guess no DST after 1991. # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 873,886 **** # Uzbekistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tashkent 4:37:12 - LMT 1924 May 2 ! 5:00 - TSK 1957 Mar ! 6:00 RussiaAsia TS%s 1991 Mar 31 2:00s ! 5:00 1:00 TSD 1991 Sep 29 2:00s ! 5:00 - TSK # Shanks has Tashkent using DST after 1991, but usno1995 says they don't. ! # Go with usno1995. ! # http://www.odci.gov/cia/publications/95fact/802389h.gif claims that ! # Uzbekistan has two time zones, but we lack data about this. # Vietnam # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): --- 851,866 ---- # Uzbekistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tashkent 4:37:12 - LMT 1924 May 2 ! 5:00 - TAST 1957 Mar # Tashkent Time ! 6:00 RussiaAsia TAS%sT 1991 Mar 31 2:00s ! 5:00 1:00 TASST 1991 Sep 29 2:00s ! 5:00 - UZT # Uzbekistan Time # Shanks has Tashkent using DST after 1991, but usno1995 says they don't. ! # Guess no DST after 1991. ! # <URL:http://www.odci.gov/cia/publications/95fact/802389h.gif> (1995) ! # says that Uzbekistan has two time zones, but a cable ! # <URL:http://www.itaiep.doc.gov/bisnis/cables/960510uz.html> (1996-05-10) ! # from the American Embassy in Tashkent implies that they have just one. # Vietnam # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): *************** *** 889,895 **** # From Shanks (1991): # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Saigon 7:06:40 - LMT 1906 Jun 9 ! 7:06 - SMT 1911 Mar 11 0:01 # Saigon MT 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT --- 869,875 ---- # From Shanks (1991): # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Saigon 7:06:40 - LMT 1906 Jun 9 ! 7:06:20 - SMT 1911 Mar 11 0:01 # Saigon MT? 7:00 - ICT 1912 May 8:00 - ICT 1931 May 7:00 - ICT =================================================================== RCS file: RCS/australasia,v retrieving revision 1996.7 retrieving revision 1996.7.1.1 diff -c -r1996.7 -r1996.7.1.1 *** australasia 1996/05/03 02:49:56 1996.7 --- australasia 1996/09/03 23:48:46 1996.7.1.1 *************** *** 143,149 **** # Australian miscellany # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Christmas 7:02:52 - LMT 1895 Feb ! 7:00 - JVT # # Ashmore Is, Cartier # no indigenous inhabitants; only seasonal caretakers --- 143,149 ---- # Australian miscellany # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Indian/Christmas 7:02:52 - LMT 1895 Feb ! 7:00 - CXT # Christmas Island Time # # Ashmore Is, Cartier # no indigenous inhabitants; only seasonal caretakers *************** *** 159,190 **** # Cook Is # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Cook 1978 only - Nov 12 0:00 0:30 HD ! Rule Cook 1979 max - Mar Sun>=1 0:00 0 H ! Rule Cook 1979 max - Oct lastSun 0:00 0:30 HD # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Rarotonga -10:39:04 - LMT 1901 # Avarua ! -10:30 - CIST 1978 Nov 12 # Cook Is ST ! -10:00 Cook T%sT # Cocos # From USNO (1989): # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Cocos 6:30 - CCT # Fiji # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fiji 11:53:40 - LMT 1915 Oct 26 # Suva ! 12:00 - NZST # French Polynesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Gambier -8:59:48 - LMT 1912 Oct # Rikitea ! -9:00 - GBT Zone Pacific/Marquesas -9:18:00 - LMT 1912 Oct ! -9:30 - MQT Zone Pacific/Tahiti -9:58:16 - LMT 1912 Oct # Papeete ! -10:00 - THT # Guam # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 159,190 ---- # Cook Is # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Cook 1978 only - Nov 12 0:00 0:30 HS ! Rule Cook 1979 max - Mar Sun>=1 0:00 0 - ! Rule Cook 1979 max - Oct lastSun 0:00 0:30 HS # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Rarotonga -10:39:04 - LMT 1901 # Avarua ! -10:30 - CKT 1978 Nov 12 # Cook Is Time ! -10:00 Cook CK%sT # Cocos # From USNO (1989): # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone Indian/Cocos 6:30 - CCT # Cocos Islands Time # Fiji # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fiji 11:53:40 - LMT 1915 Oct 26 # Suva ! 12:00 - FJT # Fiji Time # French Polynesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Gambier -8:59:48 - LMT 1912 Oct # Rikitea ! -9:00 - GAMT # Gambier Time Zone Pacific/Marquesas -9:18:00 - LMT 1912 Oct ! -9:30 - MART # Marquesas Time Zone Pacific/Tahiti -9:58:16 - LMT 1912 Oct # Papeete ! -10:00 - TAHT # Tahiti Time # Guam # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 209,265 **** # Kiribati # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tarawa 11:32:04 - LMT 1901 # Bairiki ! 12:00 - NZST Zone Pacific/Enderbury -11:24:20 - LMT 1901 ! -12:00 - KJT 1979 Oct ! -11:00 - SST 1995 ! 13:00 - TGT Zone Pacific/Kiritimati -10:29:20 - LMT 1901 ! -10:40 - LIT 1979 Oct # Line Is Time ! -10:00 - THT 1995 ! 14:00 - KRT # N Mariana Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Saipan 9:43:00 - LMT 1901 ! 9:00 - PLT 1969 Oct ! 10:00 - GST # Marshall Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Majuro 11:24:48 - LMT 1901 ! 11:00 - NCST 1969 Oct ! 12:00 - NZST Zone Pacific/Kwajalein 11:09:20 - LMT 1901 ! 11:00 - NCST 1969 Oct ! -12:00 - KJT 1993 Aug 20 ! 12:00 - NZST # Micronesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Yap 9:12:32 - LMT 1901 # Colonia ! 9:00 - PLT 1969 Oct ! 10:00 - GST Zone Pacific/Truk 10:07:08 - LMT 1901 ! 10:00 - GST Zone Pacific/Ponape 10:32:52 - LMT 1901 # Kolonia ! 11:00 - NCST Zone Pacific/Kosrae 10:51:56 - LMT 1901 ! 11:00 - NCST 1969 Oct ! 12:00 - NZST # Nauru # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Nauru 11:07:40 - LMT 1921 Jan 15 # Uaobe ! 11:30 - NST 1942 Mar 15 9:00 - JST 1944 Aug 15 ! 11:30 - NST 1979 May ! 12:00 - NZST # New Caledonia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule NC 1977 1978 - Dec Sun>=1 0:00 1:00 D ! Rule NC 1978 1979 - Feb 27 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Noumea 11:05:48 - LMT 1912 Jan 13 11:00 NC NC%sT --- 209,265 ---- # Kiribati # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tarawa 11:32:04 - LMT 1901 # Bairiki ! 12:00 - GILT # Gilbert Is Time Zone Pacific/Enderbury -11:24:20 - LMT 1901 ! -12:00 - PHOT 1979 Oct # Phoenix Is Time ! -11:00 - PHOT 1995 ! 13:00 - PHOT Zone Pacific/Kiritimati -10:29:20 - LMT 1901 ! -10:40 - LINT 1979 Oct # Line Is Time ! -10:00 - LINT 1995 ! 14:00 - LINT # N Mariana Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Saipan 9:43:00 - LMT 1901 ! 9:00 - MPT 1969 Oct # N Mariana Is Time ! 10:00 - MPT # Marshall Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Majuro 11:24:48 - LMT 1901 ! 11:00 - MHT 1969 Oct # Marshall Islands Time ! 12:00 - MHT Zone Pacific/Kwajalein 11:09:20 - LMT 1901 ! 11:00 - MHT 1969 Oct ! -12:00 - KWAT 1993 Aug 20 # Kwajalein Time ! 12:00 - MHT # Micronesia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Yap 9:12:32 - LMT 1901 # Colonia ! 9:00 - YAPT 1969 Oct # Yap Time ! 10:00 - YAPT Zone Pacific/Truk 10:07:08 - LMT 1901 ! 10:00 - TRUT # Truk Time Zone Pacific/Ponape 10:32:52 - LMT 1901 # Kolonia ! 11:00 - PONT # Ponape Time Zone Pacific/Kosrae 10:51:56 - LMT 1901 ! 11:00 - PONT 1969 Oct ! 12:00 - KOST # Kosrae Time # Nauru # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Nauru 11:07:40 - LMT 1921 Jan 15 # Uaobe ! 11:30 - NRT 1942 Mar 15 # Nauru Time 9:00 - JST 1944 Aug 15 ! 11:30 - NRT 1979 May ! 12:00 - NRT # New Caledonia # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule NC 1977 1978 - Dec Sun>=1 0:00 1:00 S ! Rule NC 1978 1979 - Feb 27 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Noumea 11:05:48 - LMT 1912 Jan 13 11:00 NC NC%sT *************** *** 293,303 **** Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 12:00 NZ NZ%sT ! Zone Pacific/Chatham 12:45 NZ CH%sT # Antipodes Is, Kermadec Is ! # no information; probably like Pacific/Auckland ############################################################################### --- 293,303 ---- Zone Pacific/Auckland 11:39:04 - LMT 1868 11:30 NZ NZ%sT 1940 Sep 29 2:00 12:00 NZ NZ%sT ! Zone Pacific/Chatham 12:45 NZ CHA%sT # Antipodes Is, Kermadec Is ! # uninhabited except by research personnel; probably like Pacific/Auckland ############################################################################### *************** *** 305,324 **** # Niue # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Niue -11:19:40 - LMT 1901 # Alofi ! -11:20 - NIT 1951 # Niue I Time ! -11:30 - NIT 1978 Oct 1 ! -11:00 - SST # Norfolk # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Norfolk 11:11:52 - LMT 1901 # Kingston ! 11:12 - NMT 1951 ! 11:30 - NRFT # Palau # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Palau 8:57:56 - LMT 1901 # Koror ! 9:00 - PLT # Palmyra # uninhabited since World War II; was probably like Pacific/Kiritmati --- 305,324 ---- # Niue # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Niue -11:19:40 - LMT 1901 # Alofi ! -11:20 - NUT 1951 # Niue Time ! -11:30 - NUT 1978 Oct 1 ! -11:00 - NUT # 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 # Norfolk Time # Palau # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Palau 8:57:56 - LMT 1901 # Koror ! 9:00 - PWT # Palau Time # Palmyra # uninhabited since World War II; was probably like Pacific/Kiritmati *************** *** 326,343 **** # Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 ! 9:49 - PMMT 1895 ! 10:00 - EST # Pitcairn # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Pitcairn -8:40:20 - LMT 1901 # Adamstown ! -8:30 - PIT # American Samoa Zone Pacific/Pago_Pago 12:37:12 - LMT 1879 Jul 5 -11:22:48 - LMT 1911 ! -11:30 - SST 1950 -11:00 - NST 1967 Apr # N=Nome -11:00 - BST 1983 Nov 30 # B=Bering -11:00 - SST # S=Samoa --- 326,343 ---- # Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Port_Moresby 9:48:40 - LMT 1880 ! 9:48:40 - PMMT 1895 # Port Moresby Mean Time ! 10:00 - PGT # Papua New Guinea Time # Pitcairn # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Pitcairn -8:40:20 - LMT 1901 # Adamstown ! -8:30 - PNT # Pitcairn Time # American Samoa Zone Pacific/Pago_Pago 12:37:12 - LMT 1879 Jul 5 -11:22:48 - LMT 1911 ! -11:30 - SAMT 1950 # Samoa Time -11:00 - NST 1967 Apr # N=Nome -11:00 - BST 1983 Nov 30 # B=Bering -11:00 - SST # S=Samoa *************** *** 345,396 **** # W Samoa Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 ! -11:30 - SST 1950 ! -11:00 - SST # Solomon Is # excludes Bougainville, for which see Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara ! 11:00 - NCST # Tokelau Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fakaofo -11:24:56 - LMT 1901 ! -10:00 - THT # Tonga # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tongatapu 12:19:20 - LMT 1901 ! 12:20 - TMT 1968 Oct ! 13:00 - TGT # Tuvalu # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Funafuti 11:56:52 - LMT 1901 ! 12:00 - NZST # Vanuatu # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Vanuatu 1983 only - Sep 25 0:00 1:00 D ! Rule Vanuatu 1984 1991 - Mar Sun>=23 0:00 0 S ! Rule Vanuatu 1984 only - Oct 23 0:00 1:00 D ! Rule Vanuatu 1985 1990 - Sep Sun>=23 0:00 1:00 D ! Rule Vanuatu 1991 max - Sep lastSun 0:00 1:00 D ! Rule Vanuatu 1992 max - Mar lastSun 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila ! 11:00 - NCST # Wake # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wake 11:06:28 - LMT 1901 ! 12:00 - NZST # Wallis and Futuna # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wallis 12:15:20 - LMT 1901 ! 12:00 - NZST ############################################################################### --- 345,396 ---- # W Samoa Zone Pacific/Apia 12:33:04 - LMT 1879 Jul 5 -11:26:56 - LMT 1911 ! -11:30 - SAMT 1950 # Samoa Time ! -11:00 - WST # W Samoa Time # Solomon Is # excludes Bougainville, for which see Papua New Guinea # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Guadalcanal 10:39:48 - LMT 1912 Oct # Honiara ! 11:00 - SBT # Solomon Is Time # Tokelau Is # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fakaofo -11:24:56 - LMT 1901 ! -10:00 - TKT # Tokelau Time # Tonga # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Tongatapu 12:19:20 - LMT 1901 ! 12:20 - TOT 1968 Oct # Tonga Time ! 13:00 - TOT # Tuvalu # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Funafuti 11:56:52 - LMT 1901 ! 12:00 - TVT # Tuvalu Time # Vanuatu # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Vanuatu 1983 only - Sep 25 0:00 1:00 S ! Rule Vanuatu 1984 1991 - Mar Sun>=23 0:00 0 - ! Rule Vanuatu 1984 only - Oct 23 0:00 1:00 S ! Rule Vanuatu 1985 1990 - Sep Sun>=23 0:00 1:00 S ! Rule Vanuatu 1991 max - Sep lastSun 0:00 1:00 S ! Rule Vanuatu 1992 max - Mar lastSun 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila ! 11:00 Vanuatu VU%sT # Vanuatu Time # Wake # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wake 11:06:28 - LMT 1901 ! 12:00 - WAKT # Wake Time # Wallis and Futuna # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Wallis 12:15:20 - LMT 1901 ! 12:00 - WFT # Wallis & Futuna Time ############################################################################### *************** *** 419,452 **** # Corrections are welcome! # std dst # LMT Local Mean Time - # 6:30 CCT Cocos* - # 7:00 JVT Java* # 8:00 WST WST Western Australia # 9:00 JST Japan - # 9:00 PLT Palau* # 9:30 CST CST Central Australia # 10:00 EST EST Eastern Australia ! # 10:00 GST Guam* # 10:30 LHST LHST Lord Howe* - # 11:00 NCST NCDT New Caledonia* - # 11:30 NRFT Norfolk* # 12:00 NZST NZDT New Zealand ! # 12:45 CHST CHDT Chatham* ! # 13:00 TGT Tongatapu* ! # 14:00 KRT Kiritimati* ! # -12:00 KJT Kwajalein (no longer used)* # -11:00 SST Samoa - # -10:40 LIT Line Is (no longer used)* - # -10:00 THT Tahiti* # -10:00 HST Hawaii - # - 9:30 MQT Marquesas* - # - 9:00 GBT Gambier* - # - 8:30 PIT Pitcairn* # # See the `northamerica' file for Hawaii. # See the `southamerica' file for Easter I and the Galapagos Is. # ! # See the `africa' file for Zone naming conventions. ############################################################################### --- 419,439 ---- # Corrections are welcome! # std dst # LMT Local Mean Time # 8:00 WST WST Western Australia # 9:00 JST Japan # 9:30 CST CST Central Australia # 10:00 EST EST Eastern Australia ! # 10:00 GST Guam # 10:30 LHST LHST Lord Howe* # 12:00 NZST NZDT New Zealand ! # 12:45 CHAST CHADT Chatham* # -11:00 SST Samoa # -10:00 HST Hawaii # # See the `northamerica' file for Hawaii. # See the `southamerica' file for Easter I and the Galapagos Is. # ! # See the `africa' file for time zone naming and abbreviation conventions. ############################################################################### =================================================================== RCS file: RCS/europe,v retrieving revision 1996.9 retrieving revision 1996.9.1.1 diff -c -r1996.9 -r1996.9.1.1 *** europe 1996/07/01 22:12:45 1996.9 --- europe 1996/09/03 23:48:46 1996.9.1.1 *************** *** 4,10 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1995-12-19): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). --- 4,10 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). *************** *** 16,58 **** # # I invented the abbreviations marked `*' in the following table; # the rest are from earlier versions of this file, or from other sources. ! # The starred Russian names are dubious. Corrections are welcome! # std dst # LMT Local Mean Time - # LST Local Star Time (Russian ``mestnoe zvezdnoe vremya'') # -4:00 AST Atlantic ! # -3:00 WGT+DST Western Greenland* ! # -2:00 MGT+DST Middle Greenland* ! # -1:00 EGT+DST Eastern Greenland* ! # -1:00 ACT+DST Azores and Canaries* ! # -1:00 IST IDT Iceland (no longer used)* # 0:00 GMT BST Greenwich, British Summer ! # 0:00 WET+DST Western Europe ! # 1:00 MET+DST Middle Europe ! # 2:00 EET+DST Eastern Europe ! # 3:00 MSK MSD Moscow ! # 3:00 TUR+DST Turkey (no longer used)* ! # 4:00 KSK KSD Kuybyshev (was 3:00)* ! # 5:00 ESK ESD Yekaterinburg (was 4:00) (was SSK, SSD)* ! # 6:00 OSK OSD Omsk (was 5:00)* ! # 6:00 NSK NSD Novosibirsk (was 7:00) ! # 7:00 KRSK KRSD Krasnoyarsk (was 6:00) ! # 8:00 ISK ISD Irkutsk (was 7:00)* ! # 9:00 YSK YSD Yakutsk (was 8:00)* ! # 10:00 VSK VSD Vladivostok (was 9:00)* ! # 11:00 MSK MSD Magadan (was 10:00)* ! # 12:00 PSK PSD Petropavlovsk-Kamchatski (was 11:00)* ! # 13:00 ASK ASD Anadyr (was 12:00)* # ! # See the `africa' file for Zone naming conventions. # # A reliable and entertaining source about time zones, especially in Britain, # is Derek Howse, Greenwich time and the discovery of the longitude, # Oxford University Press (1980). - # From Andrew A. Chernov <ache(a)astral.msk.su> (November 12, 1993): - # LST is Local Star Time (``mestnoe zvezdnoe vremya''). - # From Peter Ilieve <peter(a)memex.co.uk> (December 4, 1994), # The original six [EU members]: Belgium, France, (West) Germany, Italy, # Luxembourg, the Netherlands. --- 16,39 ---- # # I invented the abbreviations marked `*' in the following table; # the rest are from earlier versions of this file, or from other sources. ! # Corrections are welcome! # std dst # LMT Local Mean Time # -4:00 AST Atlantic ! # -3:00 WGT WGST Western Greenland* ! # -1:00 EGT EGST Eastern Greenland* # 0:00 GMT BST Greenwich, British Summer ! # 0:00 GMT IST Greenwich, Irish Summer ! # 0:00 WET WEST Western Europe ! # 1:00 CET CEST Central Europe ! # 2:00 EET EEST Eastern Europe # ! # See the `africa' file for time zone naming and abbreviation conventions. # # A reliable and entertaining source about time zones, especially in Britain, # is Derek Howse, Greenwich time and the discovery of the longitude, # Oxford University Press (1980). # From Peter Ilieve <peter(a)memex.co.uk> (December 4, 1994), # The original six [EU members]: Belgium, France, (West) Germany, Italy, # Luxembourg, the Netherlands. *************** *** 74,82 **** --- 55,65 ---- # different end date for the UK and Ireland, and this was always allowed # in the Directive. + ############################################################################### # United Kingdom + # The UK and its colonies adopted the Gregorian calendar on 1752-09-14. # From Peter Ilieve <peter(a)memex.co.uk> (July 6, 1994): # *************** *** 134,139 **** --- 117,128 ---- # but it met with ridicule and opposition, especially from farming interests. # One-hour Summer Time was eventually adopted as a wartime measure in 1916. + # From Paul Eggert (1996-09-03): + # The OED Supplement says that the English originally said ``Daylight Saving'' + # when they were debating the adoption of DST in 1908; but by 1916 this + # term appears only in quotes taken from DST's opponents, whereas the + # proponents (who eventually won the argument) are quoted as using ``Summer''. + # From Arthur David Olson (January 19, 1989): # # A source at the British Information Office in New York avers that it's *************** *** 194,199 **** --- 183,194 ---- # Sunday, but in the night of Sunday- Monday so that it will operate from # Monday, 2nd April.' + # From Chris Carrier <72157.3334(a)CompuServe.COM> (1996-06-14): + # I remember reading in various wartime issues of the London Times the + # acronym BDST for British Double Summer Time. Look for the published + # time of sunrise and sunset in The Times, when BDST was in effect, and + # if you find a zone reference it will say, "All times B.D.S.T." + # From Peter Ilieve <peter(a)memex.co.uk> (September 3, 1993): # # > # Current rules *************** *** 719,736 **** # 1939 end to 1947--irregular, and with double summer time Rule GB-Eire 1939 only - Nov 19 2:00s 0 GMT Rule GB-Eire 1940 only - Feb 25 2:00s 1:00 BST ! Rule GB-Eire 1941 only - May Sun>=2 1:00s 2:00 DST Rule GB-Eire 1941 1943 - Aug Sun>=9 1:00s 1:00 BST ! Rule GB-Eire 1942 1944 - Apr Sun>=2 1:00s 2:00 DST Rule GB-Eire 1944 only - Sep Sun>=16 1:00s 1:00 BST # Double daylight starts on a Monday in 1945--see above. ! Rule GB-Eire 1945 only - Apr 2 1:00s 2:00 DST Rule GB-Eire 1945 only - Jul 15 1:00s 1:00 BST Rule GB-Eire 1945 only - Oct 7 2:00s 0 GMT Rule GB-Eire 1946 only - Apr 14 2:00s 1:00 BST Rule GB-Eire 1946 only - Oct 6 2:00s 0 GMT Rule GB-Eire 1947 only - Mar 16 2:00s 1:00 BST ! Rule GB-Eire 1947 only - Apr 13 1:00s 2:00 DST Rule GB-Eire 1947 only - Aug 10 1:00s 1:00 BST Rule GB-Eire 1947 only - Nov 2 2:00s 0 GMT # So much for double saving time. 1948 and 1949, irregular. --- 714,731 ---- # 1939 end to 1947--irregular, and with double summer time Rule GB-Eire 1939 only - Nov 19 2:00s 0 GMT Rule GB-Eire 1940 only - Feb 25 2:00s 1:00 BST ! Rule GB-Eire 1941 only - May Sun>=2 1:00s 2:00 BDST Rule GB-Eire 1941 1943 - Aug Sun>=9 1:00s 1:00 BST ! Rule GB-Eire 1942 1944 - Apr Sun>=2 1:00s 2:00 BDST Rule GB-Eire 1944 only - Sep Sun>=16 1:00s 1:00 BST # Double daylight starts on a Monday in 1945--see above. ! Rule GB-Eire 1945 only - Apr 2 1:00s 2:00 BDST Rule GB-Eire 1945 only - Jul 15 1:00s 1:00 BST Rule GB-Eire 1945 only - Oct 7 2:00s 0 GMT Rule GB-Eire 1946 only - Apr 14 2:00s 1:00 BST Rule GB-Eire 1946 only - Oct 6 2:00s 0 GMT Rule GB-Eire 1947 only - Mar 16 2:00s 1:00 BST ! Rule GB-Eire 1947 only - Apr 13 1:00s 2:00 BDST Rule GB-Eire 1947 only - Aug 10 1:00s 1:00 BST Rule GB-Eire 1947 only - Nov 2 2:00s 0 GMT # So much for double saving time. 1948 and 1949, irregular. *************** *** 768,782 **** 0:00 EU GMT/BST Zone Europe/Belfast -0:23:40 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00 # Dublin MT ! -0:25:21 1:00 DST 1916 Oct 1 3:00 0:00 GB-Eire %s 1968 Oct 27 1:00 - BST 1971 Oct 31 2:00u 0:00 GB-Eire %s 1996 0:00 EU GMT/BST Zone Europe/Dublin -0:25:21 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00 # Dublin MT ! -0:25:21 1:00 DST 1916 Oct 1 3:00 ! 0:00 GB-Eire %s 1921 Dec 6 0:00 GB-Eire GMT/IST 1940 Feb 25 2:00 0:00 1:00 IST 1946 Oct 6 2:00 0:00 - GMT 1947 Mar 16 2:00 --- 763,777 ---- 0:00 EU GMT/BST Zone Europe/Belfast -0:23:40 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00 # Dublin MT ! -0:25:21 1:00 IST 1916 Oct 1 3:00 # Irish Summer Time 0:00 GB-Eire %s 1968 Oct 27 1:00 - BST 1971 Oct 31 2:00u 0:00 GB-Eire %s 1996 0:00 EU GMT/BST Zone Europe/Dublin -0:25:21 - LMT 1880 Aug 2 -0:25:21 - DMT 1916 May 21 2:00 # Dublin MT ! -0:25:21 1:00 IST 1916 Oct 1 3:00 ! 0:00 GB-Eire %s 1921 Dec 6 # independence 0:00 GB-Eire GMT/IST 1940 Feb 25 2:00 0:00 1:00 IST 1946 Oct 6 2:00 0:00 - GMT 1947 Mar 16 2:00 *************** *** 795,1053 **** # Common Market, etc. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule EU 1977 1980 - Apr Sun>=1 1:00u 1:00 " DST" Rule EU 1977 only - Sep lastSun 1:00u 0 - Rule EU 1978 only - Oct 1 1:00u 0 - Rule EU 1979 1995 - Sep lastSun 1:00u 0 - ! Rule EU 1981 max - Mar lastSun 1:00u 1:00 " DST" Rule EU 1996 max - Oct lastSun 1:00u 0 - # W-Eur differs from EU only in that W-Eur uses standard time. ! Rule W-Eur 1977 1980 - Apr Sun>=1 1:00s 1:00 " DST" Rule W-Eur 1977 only - Sep lastSun 1:00s 0 - Rule W-Eur 1978 only - Oct 1 1:00s 0 - Rule W-Eur 1979 1995 - Sep lastSun 1:00s 0 - ! Rule W-Eur 1981 max - Mar lastSun 1:00s 1:00 " DST" Rule W-Eur 1996 max - Oct lastSun 1:00s 0 - ! # Older M-Eur rules are for convenience in the tables. ! # From 1977 on, M-Eur differs from EU only in that M-Eur uses standard time. ! Rule M-Eur 1916 only - Apr 30 23:00 1:00 " DST" ! Rule M-Eur 1916 only - Oct 1 1:00 0 - ! Rule M-Eur 1917 1918 - Apr Mon>=15 2:00s 1:00 " DST" ! Rule M-Eur 1917 1918 - Sep Mon>=15 2:00s 0 - ! Rule M-Eur 1940 only - Apr 1 2:00s 1:00 " DST" # Whitman says 1941 DST was only from Feb 25 to Oct 5; go with Shanks. ! Rule M-Eur 1942 only - Nov 2 2:00s 0 - ! Rule M-Eur 1943 only - Mar 29 2:00s 1:00 " DST" ! Rule M-Eur 1943 only - Oct 4 2:00s 0 - ! Rule M-Eur 1944 only - Apr 3 2:00s 1:00 " DST" # Whitman gives 1944 Oct 7; go with Shanks. ! Rule M-Eur 1944 only - Oct 2 2:00s 0 - ! Rule M-Eur 1977 1980 - Apr Sun>=1 2:00s 1:00 " DST" ! Rule M-Eur 1977 only - Sep lastSun 2:00s 0 - ! Rule M-Eur 1978 only - Oct 1 2:00s 0 - ! Rule M-Eur 1979 1995 - Sep lastSun 2:00s 0 - ! Rule M-Eur 1981 max - Mar lastSun 2:00s 1:00 " DST" ! Rule M-Eur 1996 max - Oct lastSun 2:00s 0 - ! ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Russia 1917 only - Jul 1 23:00 1:00 " DST" ! Rule Russia 1917 only - Dec 28 0:00 0 - ! Rule Russia 1918 only - May 31 22:00 2:00 " DDST" ! Rule Russia 1918 only - Sep 17 0:00 1:00 " DST" ! Rule Russia 1919 only - May 31 23:00 2:00 " DDST" ! Rule Russia 1919 only - Jul 1 2:00 1:00 D ! Rule Russia 1919 only - Aug 16 0:00 0 K ! Rule Russia 1921 only - Feb 14 23:00 1:00 D # Shanks gives 1921 Mar 21 for the following transition. # From Andrew A. Chernov <ache(a)astral.msk.su> (November 12, 1993): # My sources says, that it is Mar 20, not 21. ! Rule Russia 1921 only - Mar 20 23:00 2:00 DD ! Rule Russia 1921 only - Sep 1 0:00 1:00 D ! Rule Russia 1921 only - Oct 1 0:00 0 K ! Rule Russia 1981 1984 - Apr 1 0:00 1:00 D ! Rule Russia 1981 1983 - Oct 1 0:00 0 K ! Rule Russia 1984 max - Sep lastSun 2:00s 0 K ! Rule Russia 1985 max - Mar lastSun 2:00s 1:00 D # These are for backward compatibility with older versions. # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone WET 0:00 EU WET%s ! Zone MET 1:00 M-Eur MET%s ! Zone EET 2:00 EU EET%s ! ! # Tom Hoffman says that MET is also known as Central European Time - Link MET CET # Albania # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Albania 1940 only - Jun 16 0:00 1:00 " DST" Rule Albania 1942 only - Nov 2 3:00 0 - ! Rule Albania 1943 only - Mar 29 2:00 1:00 " DST" Rule Albania 1943 only - Apr 10 3:00 0 - ! Rule Albania 1974 only - May 4 0:00 1:00 " DST" Rule Albania 1974 only - Oct 2 0:00 0 - ! Rule Albania 1975 only - May 1 0:00 1:00 " DST" Rule Albania 1975 only - Oct 2 0:00 0 - ! Rule Albania 1976 only - May 2 0:00 1:00 " DST" Rule Albania 1976 only - Oct 3 0:00 0 - ! Rule Albania 1977 only - May 8 0:00 1:00 " DST" Rule Albania 1977 only - Oct 2 0:00 0 - ! Rule Albania 1978 only - May 6 0:00 1:00 " DST" Rule Albania 1978 only - Oct 1 0:00 0 - ! Rule Albania 1979 only - May 5 0:00 1:00 " DST" Rule Albania 1979 only - Sep 30 0:00 0 - ! Rule Albania 1980 only - May 3 0:00 1:00 " DST" Rule Albania 1980 only - Oct 4 0:00 0 - ! Rule Albania 1981 only - Apr 26 0:00 1:00 " DST" Rule Albania 1981 only - Sep 27 0:00 0 - ! Rule Albania 1982 only - May 2 0:00 1:00 " DST" Rule Albania 1982 only - Oct 3 0:00 0 - ! Rule Albania 1983 only - Apr 18 0:00 1:00 " DST" Rule Albania 1983 only - Oct 1 0:00 0 - ! Rule Albania 1984 only - Apr 1 0:00 1:00 " DST" Rule Albania 1984 only - Oct 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tirane 1:19:20 - LMT 1914 ! 1:00 - MET 1940 Jun 16 ! 1:00 Albania MET%s 1985 Mar 31 1:00 ! 1:00 W-Eur MET%s ! # This may change to `EU' soon. # Andorra # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Andorra 0:06:04 - LMT 1901 0:00 - WET 1946 Sep 30 ! 1:00 - MET 1985 Mar 31 2:00 ! 1:00 EU MET%s # Austria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Austria 1920 only - Apr 5 2:00s 1:00 " DST" Rule Austria 1920 only - Sep 13 2:00s 0 - ! Rule Austria 1945 only - Apr 2 2:00s 1:00 " DST" Rule Austria 1945 only - Nov 18 2:00s 0 - ! Rule Austria 1946 only - Apr 14 2:00s 1:00 " DST" Rule Austria 1946 1948 - Oct Sun>=1 2:00s 0 - ! Rule Austria 1947 only - Apr 6 2:00s 1:00 " DST" ! Rule Austria 1948 only - Apr 18 2:00s 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vienna 1:05:20 - LMT 1893 Apr ! 1:00 M-Eur MET%s 1918 Jun 16 3:00 ! 1:00 Austria MET%s 1940 Apr 1 2:00 ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Austria MET%s 1981 ! 1:00 EU MET%s # Belarus # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 ! 2:31 Russia LST%s 1919 Jul 1 2:00 ! 3:00 Russia MS%s 1922 Oct 2:00 - EET 1930 Jun 21 ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Belgium # Whitman and Shanks disagree; go with Shanks, usually. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # From Whitman: ! Rule Belgium 1919 only - Mar 1 23:00s 1:00 " DST" Rule Belgium 1919 only - Oct 4 23:00s 0 - # Shanks gives 1920 Feb 14 23:00s; go with Whitman. ! Rule Belgium 1920 1921 - Mar 14 23:00s 1:00 " DST" Rule Belgium 1920 only - Oct 23 23:00s 0 - Rule Belgium 1921 only - Oct 25 23:00s 0 - ! Rule Belgium 1922 only - Mar 25 23:00s 1:00 " DST" # Whitman gives 1927 Oct 1 2:00s and 1928 Oct 7 2:00s; go with Shanks. Rule Belgium 1922 1928 - Oct Sat>=1 23:00s 0 - ! Rule Belgium 1923 only - Apr 21 23:00s 1:00 " DST" ! Rule Belgium 1924 only - Mar 29 23:00s 1:00 " DST" ! Rule Belgium 1925 only - Apr 4 23:00s 1:00 " DST" ! Rule Belgium 1926 only - Apr 17 23:00s 1:00 " DST" ! Rule Belgium 1927 only - Apr 9 23:00s 1:00 " DST" ! Rule Belgium 1928 only - Apr 14 23:00s 1:00 " DST" ! Rule Belgium 1929 only - Apr 21 2:00s 1:00 " DST" Rule Belgium 1929 1938 - Oct Sun>=2 2:00s 0 - ! Rule Belgium 1930 only - Apr 13 2:00s 1:00 " DST" ! Rule Belgium 1931 only - Apr 19 2:00s 1:00 " DST" ! Rule Belgium 1932 only - Apr 17 2:00s 1:00 " DST" ! Rule Belgium 1933 only - Mar 26 2:00s 1:00 " DST" ! Rule Belgium 1934 only - Apr 8 2:00s 1:00 " DST" ! Rule Belgium 1935 only - Mar 31 2:00s 1:00 " DST" ! Rule Belgium 1936 only - Apr 19 2:00s 1:00 " DST" # Whitman says 1937 Apr 18 2:00s; go with Shanks. ! Rule Belgium 1937 only - Apr 4 2:00s 1:00 " DST" # Whitman says 1938 Apr 10 2:00s; go with Shanks. ! Rule Belgium 1938 only - Mar 27 2:00s 1:00 " DST" ! Rule Belgium 1939 only - Apr 16 2:00s 1:00 " DST" Rule Belgium 1939 only - Nov 19 2:00s 0 - ! Rule Belgium 1945 only - Apr 2 2:00s 1:00 " DST" Rule Belgium 1945 only - Sep 16 2:00s 0 - ! Rule Belgium 1946 only - May 19 2:00s 1:00 " DST" Rule Belgium 1946 only - Oct 7 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Brussels 0:17:20 - LMT 1880 ! 0:17 - BST 1892 May 1 12:00 0:00 - WET 1914 Aug 4 ! 1:00 M-Eur MET%s 1919 Mar 1 23:00 ! 0:00 Belgium WET%s 1940 Feb 24 23:00 ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Belgium MET%s 1977 ! 1:00 EU MET%s # Bosnia and Herzegovina - # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Sarajevo 1:13:40 - LMT 1884 ! 1:00 - MET 1941 Apr 18 23:00 ! 1:00 M-Eur MET%s 1945 May 8 2:00s ! 1:00 1:00 "MET DST" 1945 Sep 16 2:00s ! 1:00 - MET 1983 ! 1:00 EU MET%s # Bulgaria - # Part switched from the Julian to the Gregorian calendar on 1915 Nov 14; - # the rest switched on 1920 Sep 17. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Bulg 1979 only - Mar 31 23:00 1:00 " DST" Rule Bulg 1979 only - Oct 1 1:00 0 - ! Rule Bulg 1980 1982 - Apr Sat<=7 23:00 1:00 " DST" Rule Bulg 1980 only - Sep 29 1:00 0 - Rule Bulg 1981 only - Sep 27 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Sofia 1:33:16 - LMT 1880 ! 1:57 - TST 1894 Nov 30 2:00 - EET 1942 Nov 2 3:00 ! 1:00 M-Eur MET%s 1945 Apr 2 3:00 2:00 - EET 1979 Mar 31 23:00 ! 2:00 Bulg EET%s 1982 Sep 26 2:00 ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Croatia - # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Zagreb 1:03:52 - LMT 1884 ! 1:00 - MET 1941 Apr 18 23:00 ! 1:00 M-Eur MET%s 1945 May 8 2:00s ! 1:00 1:00 "MET DST" 1945 Sep 16 2:00s ! 1:00 - MET 1983 ! 1:00 EU MET%s # Czech Republic # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Czech 1945 only - Apr 8 2:00s 1:00 " DST" Rule Czech 1945 only - Nov 18 2:00s 0 - ! Rule Czech 1946 only - May 6 2:00s 1:00 " DST" Rule Czech 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Czech 1947 only - Apr 20 2:00s 1:00 " DST" ! Rule Czech 1948 only - Apr 18 2:00s 1:00 " DST" ! Rule Czech 1949 only - Apr 9 2:00s 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Prague 0:57:44 - LMT 1850 ! 0:58 - PMT 1891 Oct # Prague Mean Time ! 1:00 M-Eur MET%s 1944 Sep 17 2:00s ! 1:00 Czech MET%s 1979 ! 1:00 EU MET%s # Denmark # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Denmark 1916 only - May 14 23:00 1:00 " DST" Rule Denmark 1916 only - Sep 30 23:00 0 - ! Rule Denmark 1940 only - May 15 0:00 1:00 " DST" ! Rule Denmark 1945 only - Apr 2 2:00s 1:00 " DST" Rule Denmark 1945 only - Aug 15 2:00s 0 - ! Rule Denmark 1946 only - May 1 2:00s 1:00 " DST" Rule Denmark 1946 only - Sep 1 2:00s 0 - ! Rule Denmark 1947 only - May 4 2:00s 1:00 " DST" Rule Denmark 1947 only - Aug 10 2:00s 0 - ! Rule Denmark 1948 only - May 9 2:00s 1:00 " DST" Rule Denmark 1948 only - Aug 8 2:00s 0 - # Whitman also gives 1949 Apr 9 to 1949 Oct 1, and disagrees in minor ways # about many of the above dates; go with Shanks. --- 790,1067 ---- # Common Market, etc. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule EU 1977 1980 - Apr Sun>=1 1:00u 1:00 S Rule EU 1977 only - Sep lastSun 1:00u 0 - Rule EU 1978 only - Oct 1 1:00u 0 - Rule EU 1979 1995 - Sep lastSun 1:00u 0 - ! Rule EU 1981 max - Mar lastSun 1:00u 1:00 S Rule EU 1996 max - Oct lastSun 1:00u 0 - # W-Eur differs from EU only in that W-Eur uses standard time. ! Rule W-Eur 1977 1980 - Apr Sun>=1 1:00s 1:00 S Rule W-Eur 1977 only - Sep lastSun 1:00s 0 - Rule W-Eur 1978 only - Oct 1 1:00s 0 - Rule W-Eur 1979 1995 - Sep lastSun 1:00s 0 - ! Rule W-Eur 1981 max - Mar lastSun 1:00s 1:00 S Rule W-Eur 1996 max - Oct lastSun 1:00s 0 - ! # Older C-Eur rules are for convenience in the tables. ! # From 1977 on, C-Eur differs from EU only in that C-Eur uses standard time. ! Rule C-Eur 1916 only - Apr 30 23:00 1:00 S ! Rule C-Eur 1916 only - Oct 1 1:00 0 - ! Rule C-Eur 1917 1918 - Apr Mon>=15 2:00s 1:00 S ! Rule C-Eur 1917 1918 - Sep Mon>=15 2:00s 0 - ! Rule C-Eur 1940 only - Apr 1 2:00s 1:00 S # Whitman says 1941 DST was only from Feb 25 to Oct 5; go with Shanks. ! Rule C-Eur 1942 only - Nov 2 2:00s 0 - ! Rule C-Eur 1943 only - Mar 29 2:00s 1:00 S ! Rule C-Eur 1943 only - Oct 4 2:00s 0 - ! Rule C-Eur 1944 only - Apr 3 2:00s 1:00 S # Whitman gives 1944 Oct 7; go with Shanks. ! Rule C-Eur 1944 only - Oct 2 2:00s 0 - ! Rule C-Eur 1977 1980 - Apr Sun>=1 2:00s 1:00 S ! Rule C-Eur 1977 only - Sep lastSun 2:00s 0 - ! Rule C-Eur 1978 only - Oct 1 2:00s 0 - ! Rule C-Eur 1979 1995 - Sep lastSun 2:00s 0 - ! Rule C-Eur 1981 max - Mar lastSun 2:00s 1:00 S ! Rule C-Eur 1996 max - Oct lastSun 2:00s 0 - ! ! # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Russia 1917 only - Jul 1 23:00 1:00 MST # Moscow Summer Time ! Rule Russia 1917 only - Dec 28 0:00 0 MMT # Moscow Mean Time ! Rule Russia 1918 only - May 31 22:00 2:00 MDST # Moscow Double Summer Time ! Rule Russia 1918 only - Sep 17 0:00 1:00 MST ! Rule Russia 1919 only - May 31 23:00 2:00 MDST ! Rule Russia 1919 only - Jul 1 2:00 1:00 S ! Rule Russia 1919 only - Aug 16 0:00 0 - ! Rule Russia 1921 only - Feb 14 23:00 1:00 S # Shanks gives 1921 Mar 21 for the following transition. # From Andrew A. Chernov <ache(a)astral.msk.su> (November 12, 1993): # My sources says, that it is Mar 20, not 21. ! Rule Russia 1921 only - Mar 20 23:00 2:00 DS ! Rule Russia 1921 only - Sep 1 0:00 1:00 S ! Rule Russia 1921 only - Oct 1 0:00 0 - ! Rule Russia 1981 1984 - Apr 1 0:00 1:00 S ! Rule Russia 1981 1983 - Oct 1 0:00 0 - ! Rule Russia 1984 max - Sep lastSun 2:00s 0 - ! Rule Russia 1985 max - Mar lastSun 2:00s 1:00 S # These are for backward compatibility with older versions. # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone WET 0:00 EU WE%sT ! Zone CET 1:00 C-Eur CE%sT ! Zone MET 1:00 C-Eur ME%sT ! Zone EET 2:00 EU EE%sT ! ! # Previous editions of this database used abbreviations like MET DST ! # for Central European Summer Time, but this didn't agree with common usage. ! ! # From Markus Kuhn <mskuhn(a)unrza3.dialin.rrze.uni-erlangen.de> (1996-07-12): ! # The official German names ... are ! # ! # Mitteleuropaeische Zeit (MEZ) = UTC+01:00 ! # Mitteleuropaeische Sommerzeit (MESZ) = UTC+02:00 ! # ! # as defined in the German Time Act (Gesetz ueber die Zeitbestimmung (ZeitG), ! # 1978-07-25, Bundesgesetzblatt, Jahrgang 1978, Teil I, S. 1110-1111).... ! # I wrote ... to the German Federal Physical-Technical Institution ! # ! # Physikalisch-Technische Bundesanstalt (PTB) ! # Laboratorium 4.41 "Zeiteinheit" ! # Postfach 3345 ! # D-38023 Braunschweig ! # phone: +49 531 592-0 ! # ! # ... I received today an answer letter from Dr. Peter Hetzel, head of the PTB ! # department for time and frequency transmission. He explained that the ! # PTB translates MEZ and MESZ into English as ! # ! # Central European Time (CET) = UTC+01:00 ! # Central European Summer Time (CEST) = UTC+02:00 # Albania # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Albania 1940 only - Jun 16 0:00 1:00 S Rule Albania 1942 only - Nov 2 3:00 0 - ! Rule Albania 1943 only - Mar 29 2:00 1:00 S Rule Albania 1943 only - Apr 10 3:00 0 - ! Rule Albania 1974 only - May 4 0:00 1:00 S Rule Albania 1974 only - Oct 2 0:00 0 - ! Rule Albania 1975 only - May 1 0:00 1:00 S Rule Albania 1975 only - Oct 2 0:00 0 - ! Rule Albania 1976 only - May 2 0:00 1:00 S Rule Albania 1976 only - Oct 3 0:00 0 - ! Rule Albania 1977 only - May 8 0:00 1:00 S Rule Albania 1977 only - Oct 2 0:00 0 - ! Rule Albania 1978 only - May 6 0:00 1:00 S Rule Albania 1978 only - Oct 1 0:00 0 - ! Rule Albania 1979 only - May 5 0:00 1:00 S Rule Albania 1979 only - Sep 30 0:00 0 - ! Rule Albania 1980 only - May 3 0:00 1:00 S Rule Albania 1980 only - Oct 4 0:00 0 - ! Rule Albania 1981 only - Apr 26 0:00 1:00 S Rule Albania 1981 only - Sep 27 0:00 0 - ! Rule Albania 1982 only - May 2 0:00 1:00 S Rule Albania 1982 only - Oct 3 0:00 0 - ! Rule Albania 1983 only - Apr 18 0:00 1:00 S Rule Albania 1983 only - Oct 1 0:00 0 - ! Rule Albania 1984 only - Apr 1 0:00 1:00 S Rule Albania 1984 only - Oct 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tirane 1:19:20 - LMT 1914 ! 1:00 - CET 1940 Jun 16 ! 1:00 Albania CE%sT 1985 Mar 31 1:00 ! 1:00 W-Eur CE%sT # Andorra # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Andorra 0:06:04 - LMT 1901 0:00 - WET 1946 Sep 30 ! 1:00 - CET 1985 Mar 31 2:00 ! 1:00 EU CE%sT # Austria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Austria 1920 only - Apr 5 2:00s 1:00 S Rule Austria 1920 only - Sep 13 2:00s 0 - ! Rule Austria 1945 only - Apr 2 2:00s 1:00 S Rule Austria 1945 only - Nov 18 2:00s 0 - ! Rule Austria 1946 only - Apr 14 2:00s 1:00 S Rule Austria 1946 1948 - Oct Sun>=1 2:00s 0 - ! Rule Austria 1947 only - Apr 6 2:00s 1:00 S ! Rule Austria 1948 only - Apr 18 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vienna 1:05:20 - LMT 1893 Apr ! 1:00 C-Eur CE%sT 1918 Jun 16 3:00 ! 1:00 Austria CE%sT 1940 Apr 1 2:00 ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Austria CE%sT 1981 ! 1:00 EU CE%sT # Belarus # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Minsk 1:50:16 - LMT 1880 ! 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MOS%sT 1922 Oct # Moscow Time 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Belgium # Whitman and Shanks disagree; go with Shanks, usually. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # From Whitman: ! Rule Belgium 1919 only - Mar 1 23:00s 1:00 S Rule Belgium 1919 only - Oct 4 23:00s 0 - # Shanks gives 1920 Feb 14 23:00s; go with Whitman. ! Rule Belgium 1920 1921 - Mar 14 23:00s 1:00 S Rule Belgium 1920 only - Oct 23 23:00s 0 - Rule Belgium 1921 only - Oct 25 23:00s 0 - ! Rule Belgium 1922 only - Mar 25 23:00s 1:00 S # Whitman gives 1927 Oct 1 2:00s and 1928 Oct 7 2:00s; go with Shanks. Rule Belgium 1922 1928 - Oct Sat>=1 23:00s 0 - ! Rule Belgium 1923 only - Apr 21 23:00s 1:00 S ! Rule Belgium 1924 only - Mar 29 23:00s 1:00 S ! Rule Belgium 1925 only - Apr 4 23:00s 1:00 S ! Rule Belgium 1926 only - Apr 17 23:00s 1:00 S ! Rule Belgium 1927 only - Apr 9 23:00s 1:00 S ! Rule Belgium 1928 only - Apr 14 23:00s 1:00 S ! Rule Belgium 1929 only - Apr 21 2:00s 1:00 S Rule Belgium 1929 1938 - Oct Sun>=2 2:00s 0 - ! Rule Belgium 1930 only - Apr 13 2:00s 1:00 S ! Rule Belgium 1931 only - Apr 19 2:00s 1:00 S ! Rule Belgium 1932 only - Apr 17 2:00s 1:00 S ! Rule Belgium 1933 only - Mar 26 2:00s 1:00 S ! Rule Belgium 1934 only - Apr 8 2:00s 1:00 S ! Rule Belgium 1935 only - Mar 31 2:00s 1:00 S ! Rule Belgium 1936 only - Apr 19 2:00s 1:00 S # Whitman says 1937 Apr 18 2:00s; go with Shanks. ! Rule Belgium 1937 only - Apr 4 2:00s 1:00 S # Whitman says 1938 Apr 10 2:00s; go with Shanks. ! Rule Belgium 1938 only - Mar 27 2:00s 1:00 S ! Rule Belgium 1939 only - Apr 16 2:00s 1:00 S Rule Belgium 1939 only - Nov 19 2:00s 0 - ! Rule Belgium 1945 only - Apr 2 2:00s 1:00 S Rule Belgium 1945 only - Sep 16 2:00s 0 - ! Rule Belgium 1946 only - May 19 2:00s 1:00 S Rule Belgium 1946 only - Oct 7 2:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Brussels 0:17:20 - LMT 1880 ! 0:17:20 - BMT 1892 May 1 12:00 # Brussels MT 0:00 - WET 1914 Aug 4 ! 1:00 C-Eur CE%sT 1919 Mar 1 23:00 ! 0:00 Belgium WE%sT 1940 Feb 24 23:00 ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Belgium CE%sT 1977 ! 1:00 EU CE%sT # Bosnia and Herzegovina # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Sarajevo 1:13:40 - LMT 1884 ! 1:00 - CET 1941 Apr 18 23:00 ! 1:00 C-Eur CE%sT 1945 May 8 2:00s ! 1:00 1:00 CEST 1945 Sep 16 2:00s ! 1:00 - CET 1983 ! 1:00 EU CE%sT # Bulgaria # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Bulg 1979 only - Mar 31 23:00 1:00 S Rule Bulg 1979 only - Oct 1 1:00 0 - ! Rule Bulg 1980 1982 - Apr Sat<=7 23:00 1:00 S Rule Bulg 1980 only - Sep 29 1:00 0 - Rule Bulg 1981 only - Sep 27 2:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Sofia 1:33:16 - LMT 1880 ! 1:56:56 - IMT 1894 Nov 30 # Istanbul MT? 2:00 - EET 1942 Nov 2 3:00 ! 1:00 C-Eur CE%sT 1945 Apr 2 3:00 2:00 - EET 1979 Mar 31 23:00 ! 2:00 Bulg EE%sT 1982 Sep 26 2:00 ! 2:00 C-Eur EE%sT # Croatia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Zagreb 1:03:52 - LMT 1884 ! 1:00 - CET 1941 Apr 18 23:00 ! 1:00 C-Eur CE%sT 1945 May 8 2:00s ! 1:00 1:00 CEST 1945 Sep 16 2:00s ! 1:00 - CET 1983 ! 1:00 EU CE%sT # Czech Republic + # Gregorian calendar adopted 1584-01-17. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Czech 1945 only - Apr 8 2:00s 1:00 S Rule Czech 1945 only - Nov 18 2:00s 0 - ! Rule Czech 1946 only - May 6 2:00s 1:00 S Rule Czech 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Czech 1947 only - Apr 20 2:00s 1:00 S ! Rule Czech 1948 only - Apr 18 2:00s 1:00 S ! Rule Czech 1949 only - Apr 9 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Prague 0:57:44 - LMT 1850 ! 0:57:44 - PMT 1891 Oct # Prague Mean Time ! 1:00 C-Eur CE%sT 1944 Sep 17 2:00s ! 1:00 Czech CE%sT 1979 ! 1:00 EU CE%sT # Denmark + # Gregorian calendar adopted 1700-03-01. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Denmark 1916 only - May 14 23:00 1:00 S Rule Denmark 1916 only - Sep 30 23:00 0 - ! Rule Denmark 1940 only - May 15 0:00 1:00 S ! Rule Denmark 1945 only - Apr 2 2:00s 1:00 S Rule Denmark 1945 only - Aug 15 2:00s 0 - ! Rule Denmark 1946 only - May 1 2:00s 1:00 S Rule Denmark 1946 only - Sep 1 2:00s 0 - ! Rule Denmark 1947 only - May 4 2:00s 1:00 S Rule Denmark 1947 only - Aug 10 2:00s 0 - ! Rule Denmark 1948 only - May 9 2:00s 1:00 S Rule Denmark 1948 only - Aug 8 2:00s 0 - # Whitman also gives 1949 Apr 9 to 1949 Oct 1, and disagrees in minor ways # about many of the above dates; go with Shanks. *************** *** 1055,1099 **** # For 1894, Shanks says Jan, Whitman Apr; go with Whitman. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Copenhagen 0:50:20 - LMT 1890 ! 0:50 - CMT 1894 Apr # Copenhagen Mean Time ! 1:00 Denmark MET%s 1942 Nov 2 2:00s ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Denmark MET%s 1980 ! 1:00 EU MET%s Zone Atlantic/Faeroe -0:27:04 - LMT 1908 Jan 11 # Torshavn 0:00 - WET 1981 ! 0:00 EU WET%s Zone America/Scoresbysund -1:29:00 - LMT 1916 Jul 28 ! -2:00 - MGT 1980 Apr 6 2:00 ! -2:00 M-Eur MGT%s 1981 Mar 29 ! -1:00 M-Eur EGT%s Zone America/Godthab -3:26:56 - LMT 1916 Jul 28 -3:00 - WGT 1980 Apr 6 2:00 ! -3:00 M-Eur WGT%s Zone America/Thule -4:35:08 - LMT 1916 Jul 28 -4:00 - AST # Estonia - # They switched from the Julian to the Gregorian calendar on 1918 Feb 15. - # # From Peter Ilieve <peter(a)memex.co.uk> (1994-10-15): # A relative in Tallinn confirms the accuracy of the data for 1989 onwards # [through 1994] and gives the legal authority for it, # a regulation of the Government of Estonia, No. 111 of 1989.... # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tallinn 1:39:00 - LMT 1880 ! 1:39 - LST 1918 Feb ! 1:00 M-Eur MET%s 1919 Jul ! 1:39 - LST 1921 May 2:00 - EET 1940 Aug 6 ! 3:00 - MSK 1941 Sep 15 ! 1:00 M-Eur MET%s 1944 Sep 22 ! 3:00 Russia MS%s 1989 Mar 26 2:00s ! 2:00 1:00 "EET DST" 1989 Sep 24 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Finland # # From Hannu Strang <chs(a)apu.fi> (25 Sep 1994 06:03:37 UTC): # Well, here in Helsinki we're just changing from summer time to regular one, --- 1069,1111 ---- # For 1894, Shanks says Jan, Whitman Apr; go with Whitman. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Copenhagen 0:50:20 - LMT 1890 ! 0:50:20 - CMT 1894 Apr # Copenhagen Mean Time ! 1:00 Denmark CE%sT 1942 Nov 2 2:00s ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Denmark CE%sT 1980 ! 1:00 EU CE%sT Zone Atlantic/Faeroe -0:27:04 - LMT 1908 Jan 11 # Torshavn 0:00 - WET 1981 ! 0:00 EU WE%sT Zone America/Scoresbysund -1:29:00 - LMT 1916 Jul 28 ! -2:00 - CGT 1980 Apr 6 2:00 ! -2:00 C-Eur CG%sT 1981 Mar 29 ! -1:00 C-Eur EG%sT Zone America/Godthab -3:26:56 - LMT 1916 Jul 28 -3:00 - WGT 1980 Apr 6 2:00 ! -3:00 C-Eur WG%sT Zone America/Thule -4:35:08 - LMT 1916 Jul 28 -4:00 - AST # Estonia # From Peter Ilieve <peter(a)memex.co.uk> (1994-10-15): # A relative in Tallinn confirms the accuracy of the data for 1989 onwards # [through 1994] and gives the legal authority for it, # a regulation of the Government of Estonia, No. 111 of 1989.... # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tallinn 1:39:00 - LMT 1880 ! 1:39:00 - TMT 1918 Feb # Tallinn Mean Time ! 1:00 C-Eur CE%sT 1919 Jul ! 1:39:00 - TMT 1921 May 2:00 - EET 1940 Aug 6 ! 3:00 - MOST 1941 Sep 15 # Moscow Time ! 1:00 C-Eur CE%sT 1944 Sep 22 ! 3:00 Russia MOS%sT 1989 Mar 26 2:00s ! 2:00 1:00 EEST 1989 Sep 24 2:00s ! 2:00 C-Eur EE%sT # Finland + # See Sweden for when the Gregorian calendar was adopted. # # From Hannu Strang <chs(a)apu.fi> (25 Sep 1994 06:03:37 UTC): # Well, here in Helsinki we're just changing from summer time to regular one, *************** *** 1104,1164 **** # Go with Strang instead. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Finland 1942 only - Apr 3 0:00 1:00 " DST" Rule Finland 1942 only - Oct 3 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Helsinki 1:39:52 - LMT 1878 May 31 ! 1:40 - HMT 1921 May # Helsinki Mean Time ! 2:00 Finland EET%s 1981 Mar 29 2:00 ! 2:00 EU EET%s # France # Shanks seems to use `24:00' ambiguously; we resolve it with Whitman. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule France 1916 only - Jun 14 23:00s 1:00 " DST" Rule France 1916 1919 - Oct Sun>=1 0:00 0 - ! Rule France 1917 only - Mar 24 23:00s 1:00 " DST" ! Rule France 1918 only - Mar 9 23:00s 1:00 " DST" ! Rule France 1919 only - Mar 1 23:00s 1:00 " DST" ! Rule France 1920 only - Feb 14 23:00s 1:00 " DST" Rule France 1920 only - Oct 23 23:00s 0 - ! Rule France 1921 only - Mar 14 23:00s 1:00 " DST" Rule France 1921 only - Oct 25 23:00s 0 - ! Rule France 1922 only - Mar 25 23:00s 1:00 " DST" Rule France 1922 1938 - Oct Sat>=1 23:00s 0 - ! Rule France 1923 only - May 26 23:00s 1:00 " DST" ! Rule France 1924 only - Mar 29 23:00s 1:00 " DST" ! Rule France 1925 only - Apr 4 23:00s 1:00 " DST" ! Rule France 1926 only - Apr 17 23:00s 1:00 " DST" ! Rule France 1927 only - Apr 9 23:00s 1:00 " DST" ! Rule France 1928 only - Apr 14 23:00s 1:00 " DST" ! Rule France 1929 only - Apr 20 23:00s 1:00 " DST" ! Rule France 1930 only - Apr 12 23:00s 1:00 " DST" ! Rule France 1931 only - Apr 18 23:00s 1:00 " DST" ! Rule France 1932 only - Apr 2 23:00s 1:00 " DST" ! Rule France 1933 only - Mar 25 23:00s 1:00 " DST" ! Rule France 1934 only - Apr 7 23:00s 1:00 " DST" ! Rule France 1935 only - Mar 30 23:00s 1:00 " DST" ! Rule France 1936 only - Apr 18 23:00s 1:00 " DST" ! Rule France 1937 only - Apr 3 23:00s 1:00 " DST" ! Rule France 1938 only - Mar 26 23:00s 1:00 " DST" ! Rule France 1939 only - Apr 15 23:00s 1:00 " DST" Rule France 1939 only - Nov 18 23:00s 0 - ! Rule France 1940 only - Feb 25 2:00 1:00 " DST" # The French rules for 1941-1944 were not used in Paris, # but were used in other places (e.g. Monaco). ! Rule France 1941 only - May 5 0:00 2:00 " DDST" ! Rule France 1941 only - Oct 6 1:00 1:00 " DST" ! Rule France 1942 only - Mar 8 0:00 2:00 " DDST" ! Rule France 1942 only - Nov 2 3:00 1:00 " DST" ! Rule France 1943 only - Mar 29 2:00 2:00 " DDST" ! Rule France 1943 only - Nov 4 3:00 1:00 " DST" ! Rule France 1944 only - Apr 3 2:00 2:00 " DDST" ! Rule France 1944 only - Oct 8 1:00 1:00 " DST" ! Rule France 1945 only - Apr 2 2:00 2:00 " DDST" Rule France 1945 only - Sep 16 3:00 0 - ! Rule France 1976 only - Mar 28 2:00s 1:00 " DST" Rule France 1976 only - Sep lastSun 2:00s 0 - # Shanks gives 0:09 for Paris Mean Time, and Whitman gives 0:09:05, # but Howse quotes the actual French legislation as saying 0:09:21. --- 1116,1179 ---- # Go with Strang instead. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Finland 1942 only - Apr 3 0:00 1:00 S Rule Finland 1942 only - Oct 3 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Helsinki 1:39:52 - LMT 1878 May 31 ! 1:39:52 - HMT 1921 May # Helsinki Mean Time ! 2:00 Finland EE%sT 1981 Mar 29 2:00 ! 2:00 EU EE%sT # France + # Gregorian calendar adopted 1582-12-20. + # French Revolutionary calendar used 1792-09-22 - 1805-12-31. + # # Shanks seems to use `24:00' ambiguously; we resolve it with Whitman. # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule France 1916 only - Jun 14 23:00s 1:00 S Rule France 1916 1919 - Oct Sun>=1 0:00 0 - ! Rule France 1917 only - Mar 24 23:00s 1:00 S ! Rule France 1918 only - Mar 9 23:00s 1:00 S ! Rule France 1919 only - Mar 1 23:00s 1:00 S ! Rule France 1920 only - Feb 14 23:00s 1:00 S Rule France 1920 only - Oct 23 23:00s 0 - ! Rule France 1921 only - Mar 14 23:00s 1:00 S Rule France 1921 only - Oct 25 23:00s 0 - ! Rule France 1922 only - Mar 25 23:00s 1:00 S Rule France 1922 1938 - Oct Sat>=1 23:00s 0 - ! Rule France 1923 only - May 26 23:00s 1:00 S ! Rule France 1924 only - Mar 29 23:00s 1:00 S ! Rule France 1925 only - Apr 4 23:00s 1:00 S ! Rule France 1926 only - Apr 17 23:00s 1:00 S ! Rule France 1927 only - Apr 9 23:00s 1:00 S ! Rule France 1928 only - Apr 14 23:00s 1:00 S ! Rule France 1929 only - Apr 20 23:00s 1:00 S ! Rule France 1930 only - Apr 12 23:00s 1:00 S ! Rule France 1931 only - Apr 18 23:00s 1:00 S ! Rule France 1932 only - Apr 2 23:00s 1:00 S ! Rule France 1933 only - Mar 25 23:00s 1:00 S ! Rule France 1934 only - Apr 7 23:00s 1:00 S ! Rule France 1935 only - Mar 30 23:00s 1:00 S ! Rule France 1936 only - Apr 18 23:00s 1:00 S ! Rule France 1937 only - Apr 3 23:00s 1:00 S ! Rule France 1938 only - Mar 26 23:00s 1:00 S ! Rule France 1939 only - Apr 15 23:00s 1:00 S Rule France 1939 only - Nov 18 23:00s 0 - ! Rule France 1940 only - Feb 25 2:00 1:00 S # The French rules for 1941-1944 were not used in Paris, # but were used in other places (e.g. Monaco). ! Rule France 1941 only - May 5 0:00 2:00 DS ! Rule France 1941 only - Oct 6 1:00 1:00 S ! Rule France 1942 only - Mar 8 0:00 2:00 DS ! Rule France 1942 only - Nov 2 3:00 1:00 S ! Rule France 1943 only - Mar 29 2:00 2:00 DS ! Rule France 1943 only - Nov 4 3:00 1:00 S ! Rule France 1944 only - Apr 3 2:00 2:00 DS ! Rule France 1944 only - Oct 8 1:00 1:00 S ! Rule France 1945 only - Apr 2 2:00 2:00 DS Rule France 1945 only - Sep 16 3:00 0 - ! Rule France 1976 only - Mar 28 2:00s 1:00 S Rule France 1976 only - Sep lastSun 2:00s 0 - # Shanks gives 0:09 for Paris Mean Time, and Whitman gives 0:09:05, # but Howse quotes the actual French legislation as saying 0:09:21. *************** *** 1167,1272 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Paris 0:09:21 - LMT 1891 Mar 15 0:01 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 France WET%s 1940 Jun 14 ! 1:00 M-Eur MET%s 1944 Aug 25 ! 0:00 France WET%s 1945 Sep 16 3:00 ! 1:00 France MET%s 1977 ! 1:00 EU MET%s # Germany # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Germany 1945 only - Apr 2 2:00s 1:00 " DST" ! Rule Germany 1945 only - May 24 2:00 2:00 " DDST" ! Rule Germany 1945 only - Sep 24 3:00 1:00 " DST" Rule Germany 1945 only - Nov 18 2:00s 0 - ! Rule Germany 1946 only - Apr 14 2:00s 1:00 " DST" # Whitman gives 1948 Oct 31; go with Shanks. Rule Germany 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Germany 1947 only - Apr 6 2:00s 1:00 " DST" ! Rule Germany 1947 only - May 11 2:00s 2:00 " DDST" ! Rule Germany 1947 only - Jun 29 3:00 1:00 " DST" ! Rule Germany 1948 only - Apr 18 2:00s 1:00 " DST" ! Rule Germany 1949 only - Apr 10 2:00s 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Berlin 0:53:28 - LMT 1893 Apr ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Germany MET%s 1980 ! 1:00 EU MET%s # Gibraltar # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Gibraltar -0:21:24 - LMT 1880 Aug 2 0:00 GB-Eire %s 1957 Apr 14 2:00 ! 1:00 - MET 1982 ! 1:00 EU MET%s # Greece - # They adopted the Julian calendar in 1846. - # Part switched to the Gregorian calendar on 1916 Jul 28. - # The rest switched on 1920 Mar 18. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1932 Jul 5 - Nov 1; go with Shanks. ! Rule Greece 1932 only - Jul 7 0:00 1:00 " DST" Rule Greece 1932 only - Sep 1 0:00 0 - # Whitman gives 1941 Apr 25 - ?; go with Shanks. ! Rule Greece 1941 only - Apr 7 0:00 1:00 " DST" # Whitman gives 1942 Feb 2 - ?; go with Shanks. Rule Greece 1942 only - Nov 2 3:00 0 - ! Rule Greece 1943 only - Mar 30 0:00 1:00 " DST" Rule Greece 1943 only - Oct 4 0:00 0 - # Whitman gives 1944 Oct 3 - Oct 31; go with Shanks. ! Rule Greece 1952 only - Jul 1 0:00 1:00 " DST" Rule Greece 1952 only - Nov 2 0:00 0 - ! Rule Greece 1975 only - Apr 12 0:00s 1:00 " DST" Rule Greece 1975 only - Nov 26 0:00s 0 - ! Rule Greece 1976 only - Apr 11 2:00s 1:00 " DST" Rule Greece 1976 only - Oct 10 2:00s 0 - ! Rule Greece 1977 1978 - Apr Sun>=1 2:00s 1:00 " DST" Rule Greece 1977 only - Sep 26 2:00s 0 - Rule Greece 1978 only - Sep 24 4:00 0 - ! Rule Greece 1979 only - Apr 1 9:00 1:00 " DST" Rule Greece 1979 only - Sep 29 2:00 0 - ! Rule Greece 1980 only - Apr 1 0:00 1:00 " DST" Rule Greece 1980 only - Sep 28 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Athens 1:34:52 - LMT 1895 Sep 14 ! 1:35 - AMT 1916 Jul 28 0:01 # Athens MT ! 2:00 Greece EET%s 1941 Apr 30 ! 1:00 Greece MET%s 1944 Apr 4 ! 2:00 Greece EET%s 1981 ! # Shanks says they switched to M-Eur in 1981; # go with EU intead, since Greece joined it on Jan 1. ! 2:00 EU EET%s # Hungary # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Hungary 1918 only - Apr 1 3:00 1:00 " DST" Rule Hungary 1918 only - Sep 29 3:00 0 - ! Rule Hungary 1919 only - Apr 15 3:00 1:00 " DST" Rule Hungary 1919 only - Sep 15 3:00 0 - ! Rule Hungary 1920 only - Apr 5 3:00 1:00 " DST" Rule Hungary 1920 only - Sep 30 3:00 0 - ! Rule Hungary 1945 only - May 1 23:00 1:00 " DST" Rule Hungary 1945 only - Nov 3 0:00 0 - ! Rule Hungary 1946 only - Mar 31 2:00s 1:00 " DST" Rule Hungary 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Hungary 1947 1949 - Apr Sun>=4 2:00s 1:00 " DST" ! Rule Hungary 1950 only - Apr 17 2:00s 1:00 " DST" Rule Hungary 1950 only - Oct 23 2:00s 0 - ! Rule Hungary 1954 1955 - May 23 0:00 1:00 " DST" Rule Hungary 1954 1955 - Oct 3 0:00 0 - ! Rule Hungary 1956 only - Jun Sun>=1 0:00 1:00 " DST" Rule Hungary 1956 only - Sep lastSun 0:00 0 - ! Rule Hungary 1957 only - Jun Sun>=1 1:00 1:00 " DST" Rule Hungary 1957 only - Sep lastSun 3:00 0 - ! Rule Hungary 1980 only - Apr 6 1:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Budapest 1:16:20 - LMT 1890 Oct ! 1:00 M-Eur MET%s 1918 ! 1:00 Hungary MET%s 1941 Apr 6 2:00 ! 1:00 M-Eur MET%s 1945 May 1 23:00 ! 1:00 Hungary MET%s 1980 Sep 28 2:00s ! 1:00 EU MET%s # Iceland # --- 1182,1286 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Paris 0:09:21 - LMT 1891 Mar 15 0:01 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 France WE%sT 1940 Jun 14 ! 1:00 C-Eur CE%sT 1944 Aug 25 ! 0:00 France WE%sT 1945 Sep 16 3:00 ! 1:00 France CE%sT 1977 ! 1:00 EU CE%sT # Germany + # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Germany 1945 only - Apr 2 2:00s 1:00 S ! Rule Germany 1945 only - May 24 2:00 2:00 DS ! Rule Germany 1945 only - Sep 24 3:00 1:00 S Rule Germany 1945 only - Nov 18 2:00s 0 - ! Rule Germany 1946 only - Apr 14 2:00s 1:00 S # Whitman gives 1948 Oct 31; go with Shanks. Rule Germany 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Germany 1947 only - Apr 6 2:00s 1:00 S ! Rule Germany 1947 only - May 11 2:00s 2:00 DS ! Rule Germany 1947 only - Jun 29 3:00 1:00 S ! Rule Germany 1948 only - Apr 18 2:00s 1:00 S ! Rule Germany 1949 only - Apr 10 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Berlin 0:53:28 - LMT 1893 Apr ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Germany CE%sT 1980 ! 1:00 EU CE%sT # Gibraltar # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Gibraltar -0:21:24 - LMT 1880 Aug 2 0:00 GB-Eire %s 1957 Apr 14 2:00 ! 1:00 - CET 1982 ! 1:00 EU CE%sT # Greece # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1932 Jul 5 - Nov 1; go with Shanks. ! Rule Greece 1932 only - Jul 7 0:00 1:00 S Rule Greece 1932 only - Sep 1 0:00 0 - # Whitman gives 1941 Apr 25 - ?; go with Shanks. ! Rule Greece 1941 only - Apr 7 0:00 1:00 S # Whitman gives 1942 Feb 2 - ?; go with Shanks. Rule Greece 1942 only - Nov 2 3:00 0 - ! Rule Greece 1943 only - Mar 30 0:00 1:00 S Rule Greece 1943 only - Oct 4 0:00 0 - # Whitman gives 1944 Oct 3 - Oct 31; go with Shanks. ! Rule Greece 1952 only - Jul 1 0:00 1:00 S Rule Greece 1952 only - Nov 2 0:00 0 - ! Rule Greece 1975 only - Apr 12 0:00s 1:00 S Rule Greece 1975 only - Nov 26 0:00s 0 - ! Rule Greece 1976 only - Apr 11 2:00s 1:00 S Rule Greece 1976 only - Oct 10 2:00s 0 - ! Rule Greece 1977 1978 - Apr Sun>=1 2:00s 1:00 S Rule Greece 1977 only - Sep 26 2:00s 0 - Rule Greece 1978 only - Sep 24 4:00 0 - ! Rule Greece 1979 only - Apr 1 9:00 1:00 S Rule Greece 1979 only - Sep 29 2:00 0 - ! Rule Greece 1980 only - Apr 1 0:00 1:00 S Rule Greece 1980 only - Sep 28 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Athens 1:34:52 - LMT 1895 Sep 14 ! 1:34:52 - AMT 1916 Jul 28 0:01 # Athens MT ! 2:00 Greece EE%sT 1941 Apr 30 ! 1:00 Greece CE%sT 1944 Apr 4 ! 2:00 Greece EE%sT 1981 ! # Shanks says they switched to C-Eur in 1981; # go with EU intead, since Greece joined it on Jan 1. ! 2:00 EU EE%sT # Hungary + # Gregorian calendar adopted 1587-11-01. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Hungary 1918 only - Apr 1 3:00 1:00 S Rule Hungary 1918 only - Sep 29 3:00 0 - ! Rule Hungary 1919 only - Apr 15 3:00 1:00 S Rule Hungary 1919 only - Sep 15 3:00 0 - ! Rule Hungary 1920 only - Apr 5 3:00 1:00 S Rule Hungary 1920 only - Sep 30 3:00 0 - ! Rule Hungary 1945 only - May 1 23:00 1:00 S Rule Hungary 1945 only - Nov 3 0:00 0 - ! Rule Hungary 1946 only - Mar 31 2:00s 1:00 S Rule Hungary 1946 1949 - Oct Sun>=1 2:00s 0 - ! Rule Hungary 1947 1949 - Apr Sun>=4 2:00s 1:00 S ! Rule Hungary 1950 only - Apr 17 2:00s 1:00 S Rule Hungary 1950 only - Oct 23 2:00s 0 - ! Rule Hungary 1954 1955 - May 23 0:00 1:00 S Rule Hungary 1954 1955 - Oct 3 0:00 0 - ! Rule Hungary 1956 only - Jun Sun>=1 0:00 1:00 S Rule Hungary 1956 only - Sep lastSun 0:00 0 - ! Rule Hungary 1957 only - Jun Sun>=1 1:00 1:00 S Rule Hungary 1957 only - Sep lastSun 3:00 0 - ! Rule Hungary 1980 only - Apr 6 1:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Budapest 1:16:20 - LMT 1890 Oct ! 1:00 C-Eur CE%sT 1918 ! 1:00 Hungary CE%sT 1941 Apr 6 2:00 ! 1:00 C-Eur CE%sT 1945 May 1 23:00 ! 1:00 Hungary CE%sT 1980 Sep 28 2:00s ! 1:00 EU CE%sT # Iceland # *************** *** 1295,1302 **** # (old style), or on St. Luke's day, if a Saturday. # St. Luke's day ought to be traceable from ecclesiastical sources. "old style" # might be a reference to the Julian calendar as opposed to Gregorian, or it ! # might mean something else (???). The Gregorian calendar was not introduced ! # in Iceland until 1700. # # From Paul Eggert <eggert(a)twinsun.com> (December 9, 1993): # The Iceland Almanak, Shanks and Whitman disagree on many points. --- 1309,1315 ---- # (old style), or on St. Luke's day, if a Saturday. # St. Luke's day ought to be traceable from ecclesiastical sources. "old style" # might be a reference to the Julian calendar as opposed to Gregorian, or it ! # might mean something else (???). # # From Paul Eggert <eggert(a)twinsun.com> (December 9, 1993): # The Iceland Almanak, Shanks and Whitman disagree on many points. *************** *** 1304,1340 **** # Reykavik was -1:28 from 1837 to 1908, local mean time before that. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Iceland 1917 1918 - Feb 19 23:00 1:00 D ! Rule Iceland 1917 only - Oct 21 1:00 0 S ! Rule Iceland 1918 only - Nov 16 1:00 0 S ! Rule Iceland 1939 only - Apr 29 23:00 1:00 D ! Rule Iceland 1939 only - Nov 29 2:00 0 S ! Rule Iceland 1940 only - Feb 25 2:00 1:00 D ! Rule Iceland 1940 only - Nov 3 2:00 0 S ! Rule Iceland 1941 only - Mar 2 1:00s 1:00 D ! Rule Iceland 1941 only - Nov 2 1:00s 0 S ! Rule Iceland 1942 only - Mar 8 1:00s 1:00 D ! Rule Iceland 1942 only - Oct 25 1:00s 0 S # 1943-1946 - first Sunday in March until first Sunday in winter ! Rule Iceland 1943 1946 - Mar Sun>=1 1:00s 1:00 D ! Rule Iceland 1943 1948 - Oct Sun>=22 1:00s 0 S # 1947-1967 - first Sunday in April until first Sunday in winter ! Rule Iceland 1947 1967 - Apr Sun>=1 1:00s 1:00 D # 1949 Oct transition delayed by 1 week ! Rule Iceland 1949 only - Oct 30 1:00s 0 S ! Rule Iceland 1950 1966 - Oct Sun>=22 1:00s 0 S ! Rule Iceland 1967 only - Oct 29 1:00s 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Reykjavik -1:27:24 - LMT 1837 ! -1:28 - RMT 1908 # Reykjavik Mean Time ! -1:00 Iceland I%sT 1968 Apr 7 1:00s 0:00 - GMT # Italy # From Paul Eggert (1996-05-06): # For Italian DST we have three sources: Shanks, Whitman, and F. Pollastri ! # <URL:http://pisolo.cstv.to.cnr.it/toi/uk/ienitlt.html> (see `FP' below), ! # taken from a publication of the Italian National Electrotechnical Institute. # When the three sources disagree, guess who's right, as follows: # # year FP Shanks (S) Whitman (W) Go with: --- 1317,1355 ---- # Reykavik was -1:28 from 1837 to 1908, local mean time before that. # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Iceland 1917 1918 - Feb 19 23:00 1:00 S ! Rule Iceland 1917 only - Oct 21 1:00 0 - ! Rule Iceland 1918 only - Nov 16 1:00 0 - ! Rule Iceland 1939 only - Apr 29 23:00 1:00 S ! Rule Iceland 1939 only - Nov 29 2:00 0 - ! Rule Iceland 1940 only - Feb 25 2:00 1:00 S ! Rule Iceland 1940 only - Nov 3 2:00 0 - ! Rule Iceland 1941 only - Mar 2 1:00s 1:00 S ! Rule Iceland 1941 only - Nov 2 1:00s 0 - ! Rule Iceland 1942 only - Mar 8 1:00s 1:00 S ! Rule Iceland 1942 only - Oct 25 1:00s 0 - # 1943-1946 - first Sunday in March until first Sunday in winter ! Rule Iceland 1943 1946 - Mar Sun>=1 1:00s 1:00 S ! Rule Iceland 1943 1948 - Oct Sun>=22 1:00s 0 - # 1947-1967 - first Sunday in April until first Sunday in winter ! Rule Iceland 1947 1967 - Apr Sun>=1 1:00s 1:00 S # 1949 Oct transition delayed by 1 week ! Rule Iceland 1949 only - Oct 30 1:00s 0 - ! Rule Iceland 1950 1966 - Oct Sun>=22 1:00s 0 - ! Rule Iceland 1967 only - Oct 29 1:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Reykjavik -1:27:24 - LMT 1837 ! -1:27:48 - RMT 1908 # Reykjavik Mean Time? ! -1:00 Iceland IS%sT 1968 Apr 7 1:00s 0:00 - GMT # Italy + # Gregorian calendar adopted 1582-10-15. + # # From Paul Eggert (1996-05-06): # For Italian DST we have three sources: Shanks, Whitman, and F. Pollastri ! # <URL:http://pisolo.cstv.to.cnr.it/toi/uk/ienitlt.html> (1996-03-14) (`FP' ! # below), taken from an Italian National Electrotechnical Institute publication. # When the three sources disagree, guess who's right, as follows: # # year FP Shanks (S) Whitman (W) Go with: *************** *** 1348,1533 **** # 10-04 10-04 24:00 10-04 01:00 FP; guess 24:00s # 1920 03-20 03-20 24:00 03-20 00:00 FP & S # 09-18 09-18 24:00 10-01 01:00 FP; guess 24:00s ! # 1944 04-02 04-03 02:00 S (see M-Eur) # 09-16 10-02 03:00 FP; guess 24:00s # 1945 09-14 09-16 24:00 FP; guess 24:00s # 1970 05-21 05-31 00:00 S # 09-20 09-27 00:00 S # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Italy 1916 only - Jun 3 0:00s 1:00 " DST" Rule Italy 1916 only - Oct 1 0:00s 0 - ! Rule Italy 1917 only - Apr 1 0:00s 1:00 " DST" Rule Italy 1917 only - Sep 30 0:00s 0 - ! Rule Italy 1918 only - Mar 10 0:00s 1:00 " DST" Rule Italy 1918 1919 - Oct Sun>=1 0:00s 0 - ! Rule Italy 1919 only - Mar 2 0:00s 1:00 " DST" ! Rule Italy 1920 only - Mar 21 0:00s 1:00 " DST" Rule Italy 1920 only - Sep 19 0:00s 0 - ! Rule Italy 1940 only - Jun 15 0:00s 1:00 " DST" Rule Italy 1944 only - Sep 17 0:00s 0 - ! Rule Italy 1945 only - Apr 2 2:00 1:00 " DST" Rule Italy 1945 only - Sep 15 0:00s 0 - ! Rule Italy 1946 only - Mar 17 2:00s 1:00 " DST" Rule Italy 1946 only - Oct 6 2:00s 0 - ! Rule Italy 1947 only - Mar 16 0:00s 1:00 " DST" Rule Italy 1947 only - Oct 5 0:00s 0 - ! Rule Italy 1948 only - Feb 29 2:00s 1:00 " DST" Rule Italy 1948 only - Oct 3 2:00s 0 - ! Rule Italy 1966 1968 - May Sun>=22 0:00 1:00 " DST" Rule Italy 1966 1969 - Sep Sun>=22 0:00 0 - ! Rule Italy 1969 only - Jun 1 0:00 1:00 " DST" ! Rule Italy 1970 only - May 31 0:00 1:00 " DST" Rule Italy 1970 only - Sep lastSun 0:00 0 - ! Rule Italy 1971 1972 - May Sun>=22 0:00 1:00 " DST" Rule Italy 1971 only - Sep lastSun 1:00 0 - Rule Italy 1972 only - Oct 1 0:00 0 - ! Rule Italy 1973 only - Jun 3 0:00 1:00 " DST" Rule Italy 1973 1974 - Sep lastSun 0:00 0 - ! Rule Italy 1974 only - May 26 0:00 1:00 " DST" ! Rule Italy 1975 only - Jun 1 0:00s 1:00 " DST" Rule Italy 1975 1977 - Sep lastSun 0:00s 0 - ! Rule Italy 1976 only - May 30 0:00s 1:00 " DST" ! Rule Italy 1977 1979 - May Sun>=22 0:00s 1:00 " DST" Rule Italy 1978 only - Oct 1 0:00s 0 - Rule Italy 1979 only - Sep 30 0:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Rome 0:49:56 - LMT 1866 Sep 22 ! 0:50 - RMT 1893 Nov # Rome Mean Time ! 1:00 Italy MET%s 1942 Nov 2 2:00s ! 1:00 M-Eur MET%s 1944 Jul ! 1:00 Italy MET%s 1980 ! 1:00 EU MET%s Link Europe/Rome Europe/Vatican Link Europe/Rome Europe/San_Marino # Latvia - # They switched from the Julian to the Gregorian calendar on 1918 Feb 15. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Riga 1:36:24 - LMT 1880 ! 1:36 - LST 1918 Apr 15 2:00 ! 1:36 M-Eur LST%s 1919 Apr 1 2:00 ! 1:36 1:00 "LST DST" 1919 May 22 3:00 ! 1:36 - LST 1926 May 11 2:00 - EET 1940 Aug 5 ! 3:00 - MSK 1941 Jul ! 1:00 M-Eur MET%s 1944 Aug 8 ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vaduz 0:38:04 - LMT 1894 Jun ! 1:00 - MET 1981 ! 1:00 EU MET%s # Lithuania - # They switched from the Julian to the Gregorian calendar on 1918 Feb 15. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vilnius 1:41:16 - LMT 1880 ! 1:24 - LST 1917 # Kaunas ! 1:36 - LST 1919 Oct 10 ! 1:00 - MET 1920 Jul 12 2:00 - EET 1920 Oct 9 ! 1:00 - MET 1940 Aug 3 ! 3:00 - MSK 1941 Jun 24 ! 1:00 M-Eur MET%s 1944 Aug ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Lux 1916 only - May 14 23:00 1:00 " DST" Rule Lux 1916 only - Oct 1 1:00 0 - ! Rule Lux 1917 only - Apr 28 23:00 1:00 " DST" Rule Lux 1917 only - Sep 17 1:00 0 - ! Rule Lux 1918 only - Apr Mon>=15 2:00s 1:00 " DST" Rule Lux 1918 only - Sep Mon>=15 2:00s 0 - ! Rule Lux 1919 only - Mar 1 23:00 1:00 " DST" Rule Lux 1919 only - Oct 5 3:00 0 - ! Rule Lux 1920 only - Feb 14 23:00 1:00 " DST" Rule Lux 1920 only - Oct 24 2:00 0 - ! Rule Lux 1921 only - Mar 14 23:00 1:00 " DST" Rule Lux 1921 only - Oct 26 2:00 0 - ! Rule Lux 1922 only - Mar 25 23:00 1:00 " DST" Rule Lux 1922 only - Oct Sun>=2 1:00 0 - ! Rule Lux 1923 only - Apr 21 23:00 1:00 " DST" Rule Lux 1923 only - Oct Sun>=2 2:00 0 - ! Rule Lux 1924 only - Mar 29 23:00 1:00 " DST" Rule Lux 1924 1928 - Oct Sun>=2 1:00 0 - ! Rule Lux 1925 only - Apr 5 23:00 1:00 " DST" ! Rule Lux 1926 only - Apr 17 23:00 1:00 " DST" ! Rule Lux 1927 only - Apr 9 23:00 1:00 " DST" ! Rule Lux 1928 only - Apr 14 23:00 1:00 " DST" ! Rule Lux 1929 only - Apr 20 23:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Luxembourg 0:24:36 - LMT 1904 Jun ! 1:00 Lux MET%s 1918 Nov 25 ! 0:00 Lux WET%s 1929 Oct 6 2:00s ! 0:00 Belgium WET%s 1940 May 14 3:00 ! 1:00 M-Eur WET%s 1944 Sep 18 3:00 ! 1:00 Belgium MET%s 1977 ! 1:00 EU MET%s # Macedonia - # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Skopje 1:25:44 - LMT 1884 ! 1:00 - MET 1941 Apr 18 23:00 ! 1:00 M-Eur MET%s 1945 May 8 2:00s ! 1:00 1:00 "MET DST" 1945 Sep 16 2:00s ! 1:00 - MET 1983 ! 1:00 EU MET%s # Malta # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Malta 1973 only - Mar 31 0:00s 1:00 " DST" Rule Malta 1973 only - Sep 29 0:00s 0 - ! Rule Malta 1974 only - Apr 21 0:00s 1:00 " DST" Rule Malta 1974 only - Sep 16 0:00s 0 - ! Rule Malta 1975 1979 - Apr Sun>=15 2:00 1:00 " DST" Rule Malta 1975 1980 - Sep Sun>=15 2:00 0 - ! Rule Malta 1980 only - Mar 31 2:00 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Malta 0:58:04 - LMT 1893 Nov 2 # Valletta ! 1:00 Italy MET%s 1942 Nov 2 2:00s ! 1:00 M-Eur MET%s 1945 Apr 2 2:00s ! 1:00 Italy MET%s 1973 Mar 31 ! 1:00 Malta MET%s 1981 ! 1:00 EU MET%s # Moldova - # They switched from the Julian to the Gregorian calendar on 1919 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Monaco # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Monaco 0:29:32 - LMT 1891 Mar 15 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 France WET%s 1945 Sep 16 3:00 ! 1:00 France MET%s 1977 ! 1:00 EU MET%s # Netherlands # Howse writes that the Netherlands' railways used GMT between 1892 and 1940, # but for other purposes the Netherlands used Amsterdam mean time. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Shanks gives 1916 May 1 0:00 and 1916 Oct 1 0:00; go with Whitman. ! Rule Neth 1916 only - May 1 2:00s 1:00 NST ! Rule Neth 1916 only - Oct 2 2:00s 0 AMT Rule Neth 1917 only - Apr 16 2:00s 1:00 NST Rule Neth 1917 only - Sep 17 2:00s 0 AMT # Whitman gives 1918 Apr 14, 1918 Oct 31, and 1921 Sep 28; go with Shanks. --- 1363,1542 ---- # 10-04 10-04 24:00 10-04 01:00 FP; guess 24:00s # 1920 03-20 03-20 24:00 03-20 00:00 FP & S # 09-18 09-18 24:00 10-01 01:00 FP; guess 24:00s ! # 1944 04-02 04-03 02:00 S (see C-Eur) # 09-16 10-02 03:00 FP; guess 24:00s # 1945 09-14 09-16 24:00 FP; guess 24:00s # 1970 05-21 05-31 00:00 S # 09-20 09-27 00:00 S # # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Italy 1916 only - Jun 3 0:00s 1:00 S Rule Italy 1916 only - Oct 1 0:00s 0 - ! Rule Italy 1917 only - Apr 1 0:00s 1:00 S Rule Italy 1917 only - Sep 30 0:00s 0 - ! Rule Italy 1918 only - Mar 10 0:00s 1:00 S Rule Italy 1918 1919 - Oct Sun>=1 0:00s 0 - ! Rule Italy 1919 only - Mar 2 0:00s 1:00 S ! Rule Italy 1920 only - Mar 21 0:00s 1:00 S Rule Italy 1920 only - Sep 19 0:00s 0 - ! Rule Italy 1940 only - Jun 15 0:00s 1:00 S Rule Italy 1944 only - Sep 17 0:00s 0 - ! Rule Italy 1945 only - Apr 2 2:00 1:00 S Rule Italy 1945 only - Sep 15 0:00s 0 - ! Rule Italy 1946 only - Mar 17 2:00s 1:00 S Rule Italy 1946 only - Oct 6 2:00s 0 - ! Rule Italy 1947 only - Mar 16 0:00s 1:00 S Rule Italy 1947 only - Oct 5 0:00s 0 - ! Rule Italy 1948 only - Feb 29 2:00s 1:00 S Rule Italy 1948 only - Oct 3 2:00s 0 - ! Rule Italy 1966 1968 - May Sun>=22 0:00 1:00 S Rule Italy 1966 1969 - Sep Sun>=22 0:00 0 - ! Rule Italy 1969 only - Jun 1 0:00 1:00 S ! Rule Italy 1970 only - May 31 0:00 1:00 S Rule Italy 1970 only - Sep lastSun 0:00 0 - ! Rule Italy 1971 1972 - May Sun>=22 0:00 1:00 S Rule Italy 1971 only - Sep lastSun 1:00 0 - Rule Italy 1972 only - Oct 1 0:00 0 - ! Rule Italy 1973 only - Jun 3 0:00 1:00 S Rule Italy 1973 1974 - Sep lastSun 0:00 0 - ! Rule Italy 1974 only - May 26 0:00 1:00 S ! Rule Italy 1975 only - Jun 1 0:00s 1:00 S Rule Italy 1975 1977 - Sep lastSun 0:00s 0 - ! Rule Italy 1976 only - May 30 0:00s 1:00 S ! Rule Italy 1977 1979 - May Sun>=22 0:00s 1:00 S Rule Italy 1978 only - Oct 1 0:00s 0 - Rule Italy 1979 only - Sep 30 0:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Rome 0:49:56 - LMT 1866 Sep 22 ! 0:49:56 - RMT 1893 Nov # Rome Mean Time ! 1:00 Italy CE%sT 1942 Nov 2 2:00s ! 1:00 C-Eur CE%sT 1944 Jul ! 1:00 Italy CE%sT 1980 ! 1:00 EU CE%sT Link Europe/Rome Europe/Vatican Link Europe/Rome Europe/San_Marino # Latvia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Riga 1:36:24 - LMT 1880 ! 1:36:24 - RMT 1918 Apr 15 2:00 #Riga Mean Time ! 1:36:24 1:00 LST 1918 Sep 16 3:00 #Latvian Summer ! 1:36:24 - RMT 1919 Apr 1 2:00 ! 1:36:24 1:00 LST 1919 May 22 3:00 ! 1:36:24 - RMT 1926 May 11 2:00 - EET 1940 Aug 5 ! 3:00 - MOST 1941 Jul # Moscow Time ! 1:00 C-Eur CE%sT 1944 Aug 8 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vaduz 0:38:04 - LMT 1894 Jun ! 1:00 - CET 1981 ! 1:00 EU CE%sT # Lithuania # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Vilnius 1:41:16 - LMT 1880 ! 1:24:00 - WMT 1917 # Warsaw Mean Time ! 1:35:36 - KMT 1919 Oct 10 # Kaunas Mean Time ! 1:00 - CET 1920 Jul 12 2:00 - EET 1920 Oct 9 ! 1:00 - CET 1940 Aug 3 ! 3:00 - MOST 1941 Jun 24 # Moscow Time ! 1:00 C-Eur CE%sT 1944 Aug ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Lux 1916 only - May 14 23:00 1:00 S Rule Lux 1916 only - Oct 1 1:00 0 - ! Rule Lux 1917 only - Apr 28 23:00 1:00 S Rule Lux 1917 only - Sep 17 1:00 0 - ! Rule Lux 1918 only - Apr Mon>=15 2:00s 1:00 S Rule Lux 1918 only - Sep Mon>=15 2:00s 0 - ! Rule Lux 1919 only - Mar 1 23:00 1:00 S Rule Lux 1919 only - Oct 5 3:00 0 - ! Rule Lux 1920 only - Feb 14 23:00 1:00 S Rule Lux 1920 only - Oct 24 2:00 0 - ! Rule Lux 1921 only - Mar 14 23:00 1:00 S Rule Lux 1921 only - Oct 26 2:00 0 - ! Rule Lux 1922 only - Mar 25 23:00 1:00 S Rule Lux 1922 only - Oct Sun>=2 1:00 0 - ! Rule Lux 1923 only - Apr 21 23:00 1:00 S Rule Lux 1923 only - Oct Sun>=2 2:00 0 - ! Rule Lux 1924 only - Mar 29 23:00 1:00 S Rule Lux 1924 1928 - Oct Sun>=2 1:00 0 - ! Rule Lux 1925 only - Apr 5 23:00 1:00 S ! Rule Lux 1926 only - Apr 17 23:00 1:00 S ! Rule Lux 1927 only - Apr 9 23:00 1:00 S ! Rule Lux 1928 only - Apr 14 23:00 1:00 S ! Rule Lux 1929 only - Apr 20 23:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Luxembourg 0:24:36 - LMT 1904 Jun ! 1:00 Lux CE%sT 1918 Nov 25 ! 0:00 Lux WE%sT 1929 Oct 6 2:00s ! 0:00 Belgium WE%sT 1940 May 14 3:00 ! 1:00 C-Eur WE%sT 1944 Sep 18 3:00 ! 1:00 Belgium CE%sT 1977 ! 1:00 EU CE%sT # Macedonia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Skopje 1:25:44 - LMT 1884 ! 1:00 - CET 1941 Apr 18 23:00 ! 1:00 C-Eur CE%sT 1945 May 8 2:00s ! 1:00 1:00 CEST 1945 Sep 16 2:00s ! 1:00 - CET 1983 ! 1:00 EU CE%sT # Malta # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Malta 1973 only - Mar 31 0:00s 1:00 S Rule Malta 1973 only - Sep 29 0:00s 0 - ! Rule Malta 1974 only - Apr 21 0:00s 1:00 S Rule Malta 1974 only - Sep 16 0:00s 0 - ! Rule Malta 1975 1979 - Apr Sun>=15 2:00 1:00 S Rule Malta 1975 1980 - Sep Sun>=15 2:00 0 - ! Rule Malta 1980 only - Mar 31 2:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Malta 0:58:04 - LMT 1893 Nov 2 # Valletta ! 1:00 Italy CE%sT 1942 Nov 2 2:00s ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00s ! 1:00 Italy CE%sT 1973 Mar 31 ! 1:00 Malta CE%sT 1981 ! 1:00 EU CE%sT # Moldova # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s # Moscow Time ! 2:00 1:00 EEST 1991 Sep 29 2:00s ! 2:00 C-Eur EE%sT # Monaco # Shanks gives 0:09 for Paris Mean Time; go with Howse's more precise 0:09:21. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Monaco 0:29:32 - LMT 1891 Mar 15 0:09:21 - PMT 1911 Mar 11 # Paris Mean Time ! 0:00 France WE%sT 1945 Sep 16 3:00 ! 1:00 France CE%sT 1977 ! 1:00 EU CE%sT # Netherlands # Howse writes that the Netherlands' railways used GMT between 1892 and 1940, # but for other purposes the Netherlands used Amsterdam mean time. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Shanks gives 1916 May 1 0:00 and 1916 Oct 1 0:00; go with Whitman. ! Rule Neth 1916 only - May 1 2:00s 1:00 NST # Netherlands Summer Time ! Rule Neth 1916 only - Oct 2 2:00s 0 AMT # Amsterdam Mean Time Rule Neth 1917 only - Apr 16 2:00s 1:00 NST Rule Neth 1917 only - Sep 17 2:00s 0 AMT # Whitman gives 1918 Apr 14, 1918 Oct 31, and 1921 Sep 28; go with Shanks. *************** *** 1535,1541 **** Rule Neth 1918 1921 - Sep Mon>=24 2:00s 0 AMT Rule Neth 1922 only - Mar 26 2:00s 1:00 NST # Whitman gives 1939 Oct 1; go with Shanks. ! Rule Neth 1922 1939 - Oct Sun>=2 2:00s 0 AMT Rule Neth 1923 only - Jun 1 2:00s 1:00 NST Rule Neth 1924 only - Mar 30 2:00s 1:00 NST # Whitman gives 1925 Apr 5; go with Shanks. --- 1544,1550 ---- Rule Neth 1918 1921 - Sep Mon>=24 2:00s 0 AMT Rule Neth 1922 only - Mar 26 2:00s 1:00 NST # Whitman gives 1939 Oct 1; go with Shanks. ! Rule Neth 1922 1936 - Oct Sun>=2 2:00s 0 AMT Rule Neth 1923 only - Jun 1 2:00s 1:00 NST Rule Neth 1924 only - Mar 30 2:00s 1:00 NST # Whitman gives 1925 Apr 5; go with Shanks. *************** *** 1545,1907 **** Rule Neth 1932 only - May 22 2:00s 1:00 NST Rule Neth 1933 1936 - May 15 2:00s 1:00 NST Rule Neth 1937 only - May 22 2:00s 1:00 NST # Whitman gives 1939 Apr 15 and 1940 Apr 19; go with Shanks. ! Rule Neth 1938 1939 - May 15 2:00s 1:00 NST ! Rule Neth 1945 only - Apr 2 2:00s 1:00 " DST" Rule Neth 1945 only - May 20 2:00s 0 - # Before 1937, Shanks says just `0:20'; we use Whitman's more precise figure. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Amsterdam 0:19:28 - LMT 1892 May 0:19:28 Neth %s 1937 Jul ! 0:20 Neth %s 1940 May 16 0:40 ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Neth MET%s 1977 ! 1:00 EU MET%s # Norway # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1916 May 21 - 1916 Oct 21; go with Shanks. ! Rule Norway 1916 only - May 22 1:00 1:00 " DST" Rule Norway 1916 only - Sep 30 0:00 0 - # Shanks omits the following transition; go with Whitman. ! Rule Norway 1935 only - Aug 11 0:00 1:00 " DST" # Whitman says DST observed until 1942 Nov 1, then 1943 Mar 29 - Oct 4, # 1944 Apr 3 - Oct 2, and 1945 Apr 1 - Oct 1; go with Shanks after 1940. ! Rule Norway 1945 only - Apr 2 2:00s 1:00 " DST" Rule Norway 1945 only - Oct 1 2:00s 0 - ! Rule Norway 1959 1964 - Mar Sun>=15 2:00s 1:00 " DST" Rule Norway 1959 1965 - Sep Sun>=15 2:00s 0 - ! Rule Norway 1965 only - Apr 25 2:00s 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Oslo 0:43:00 - LMT 1895 ! 1:00 Norway MET%s 1940 Aug 10 23:00 ! 1:00 M-Eur MET%s 1945 Apr 2 2:00 ! 1:00 Norway MET%s 1980 ! 1:00 EU MET%s ! # Svalbard is like Europe/Oslo. # # From Whitman: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Jan_Mayen -1:00 - EGT # Poland - # Austrian and German Poland switched from the Julian to the Gregorian calendar - # on 1582 Oct 15. Russian Poland switched on 1918 Jan 14. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Poland 1918 1919 - Sep 16 2:00s 0 - ! Rule Poland 1919 only - Apr 15 2:00s 1:00 " DST" # Whitman gives 1944 Nov 30; go with Shanks. Rule Poland 1944 only - Oct 4 2:00 0 - # For 1944-1948 Whitman gives the previous day; go with Shanks. ! Rule Poland 1945 only - Apr 29 0:00 1:00 " DST" Rule Poland 1945 only - Nov 1 0:00 0 - ! Rule Poland 1946 only - Apr 14 0:00 1:00 " DST" Rule Poland 1946 only - Sep 7 0:00 0 - ! Rule Poland 1947 only - May 4 0:00 1:00 " DST" Rule Poland 1947 1948 - Oct Sun>=1 0:00 0 - ! Rule Poland 1948 only - Apr 18 0:00 1:00 " DST" # Whitman also gives 1949 Apr 9 - 1949 Oct 1; go with Shanks. ! Rule Poland 1957 only - Jun 2 1:00s 1:00 " DST" Rule Poland 1957 1958 - Sep lastSun 1:00s 0 - ! Rule Poland 1958 only - Mar 30 1:00s 1:00 " DST" ! Rule Poland 1959 only - May 31 1:00s 1:00 " DST" Rule Poland 1959 1961 - Oct Sun>=1 1:00s 0 - ! Rule Poland 1960 only - Apr 3 1:00s 1:00 " DST" ! Rule Poland 1961 1964 - May Sun>=25 1:00s 1:00 " DST" Rule Poland 1962 1964 - Sep lastSun 1:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Warsaw 1:24:00 - LMT 1880 ! 1:24 - WMT 1915 Aug 5 # Warsaw Mean Time ! 1:00 M-Eur MET%s 1918 Sep 16 3:00 ! 2:00 Poland EET%s 1922 Jun ! 1:00 Poland MET%s 1940 Jun 23 2:00 ! 1:00 M-Eur MET%s 1944 Oct ! 1:00 Poland MET%s 1977 Apr 3 1:00 ! 1:00 W-Eur MET%s ! # This may change to `EU' soon. # Portugal # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Port 1916 only - Jun 17 23:00 1:00 " DST" # Whitman gives 1916 Oct 31; go with Shanks. Rule Port 1916 only - Nov 1 1:00 0 - ! Rule Port 1917 only - Feb 28 23:00s 1:00 " DST" Rule Port 1917 1921 - Oct 14 23:00s 0 - ! Rule Port 1918 only - Mar 1 23:00s 1:00 " DST" ! Rule Port 1919 only - Feb 28 23:00s 1:00 " DST" ! Rule Port 1920 only - Feb 29 23:00s 1:00 " DST" ! Rule Port 1921 only - Feb 28 23:00s 1:00 " DST" ! Rule Port 1924 only - Apr 16 23:00s 1:00 " DST" Rule Port 1924 only - Oct 14 23:00s 0 - ! Rule Port 1926 only - Apr 17 23:00s 1:00 " DST" Rule Port 1926 1929 - Oct Sat>=1 23:00s 0 - ! Rule Port 1927 only - Apr 9 23:00s 1:00 " DST" ! Rule Port 1928 only - Apr 14 23:00s 1:00 " DST" ! Rule Port 1929 only - Apr 20 23:00s 1:00 " DST" ! Rule Port 1931 only - Apr 18 23:00s 1:00 " DST" # Whitman gives 1931 Oct 8; go with Shanks. Rule Port 1931 1932 - Oct Sat>=1 23:00s 0 - ! Rule Port 1932 only - Apr 2 23:00s 1:00 " DST" # Shanks gives 1934 Apr 4; go with Whitman. ! Rule Port 1934 only - Apr 7 23:00s 1:00 " DST" # Whitman gives 1934 Oct 5; go with Shanks. Rule Port 1934 1938 - Oct Sat>=1 23:00s 0 - # Shanks gives 1935 Apr 30; go with Whitman. ! Rule Port 1935 only - Mar 30 23:00s 1:00 " DST" ! Rule Port 1936 only - Apr 18 23:00s 1:00 " DST" # Whitman gives 1937 Apr 2; go with Shanks. ! Rule Port 1937 only - Apr 3 23:00s 1:00 " DST" ! Rule Port 1938 only - Mar 26 23:00s 1:00 " DST" ! Rule Port 1939 only - Apr 15 23:00s 1:00 " DST" # Whitman gives 1939 Oct 7; go with Shanks. Rule Port 1939 only - Nov 18 23:00s 0 - ! Rule Port 1940 only - Feb 24 23:00s 1:00 " DST" # Shanks gives 1940 Oct 7; go with Whitman. Rule Port 1940 1941 - Oct 5 23:00s 0 - ! Rule Port 1941 only - Apr 5 23:00s 1:00 " DST" ! Rule Port 1942 1945 - Mar Sat>=8 23:00s 1:00 " DST" ! Rule Port 1942 only - Apr 25 22:00s 2:00 " DDST" ! Rule Port 1942 only - Aug 15 22:00s 1:00 " DST" Rule Port 1942 1945 - Oct Sat>=24 23:00s 0 - ! Rule Port 1943 only - Apr 17 22:00s 2:00 " DDST" ! Rule Port 1943 1945 - Aug Sat>=25 22:00s 1:00 " DST" ! Rule Port 1944 1945 - Apr Sat>=21 22:00s 2:00 " DDST" ! Rule Port 1946 only - Apr Sat>=1 23:00s 1:00 " DST" Rule Port 1946 only - Oct Sat>=1 23:00s 0 - ! Rule Port 1947 1949 - Apr Sun>=1 2:00s 1:00 " DST" Rule Port 1947 1949 - Oct Sun>=1 2:00s 0 - # Shanks says DST was observed in 1950; go with Whitman. # Whitman gives Oct lastSun for 1952 on; go with Shanks. ! Rule Port 1951 1965 - Apr Sun>=1 2:00s 1:00 " DST" Rule Port 1951 1965 - Oct Sun>=1 2:00s 0 - ! Rule Port 1977 only - Mar 27 0:00s 1:00 " DST" Rule Port 1977 only - Sep 25 0:00s 0 - ! Rule Port 1978 1979 - Apr Sun>=1 0:00s 1:00 " DST" Rule Port 1978 only - Oct 1 0:00s 0 - Rule Port 1979 1982 - Sep lastSun 1:00s 0 - ! Rule Port 1980 only - Mar lastSun 0:00s 1:00 " DST" ! Rule Port 1981 1982 - Mar lastSun 1:00s 1:00 " DST" ! Rule Port 1983 only - Mar lastSun 2:00s 1:00 " DST" # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Lisbon -0:36:32 - LMT 1884 ! -0:37 - LMT 1911 May 24 # Lisbon Mean Time ! 0:00 Port WET%s 1966 Apr 3 2:00 ! 1:00 - MET 1976 Sep 26 1:00 ! 0:00 Port WET%s 1983 Sep 25 1:00s ! 0:00 EU WET%s 1992 Sep 27 1:00s # From Rui Pedro Salgueiro <rps(a)inescca.inescc.pt> (November 12, 1992): # Portugal has recently (September, 27) changed timezone # (from WET to MET or CET) to harmonize with EEC. ! 1:00 EU MET%s 1996 Mar 31 1:00u # Martin Bruckmann <martin(a)ua.pt> (1996-02-29) reports via Peter Ilieve # that Portugal is reverting to 0:00 by not moving its clocks this spring. # The new Prime Minister was fed up with getting up in the dark in the winter. ! 0:00 1:00 "WET DST" 1996 Oct 27 1:00u ! 0:00 EU WET%s # We don't know what happened to Madeira or the Azores, # so we'll just use Shanks for now. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -1:55 - HMT 1911 May 24 # Horta Mean Time ! -2:00 Port ACT%s 1966 Apr 3 2:00 ! -1:00 - ACT 1977 Mar 27 ! -1:00 - ACT 1983 Sep 25 1:00s ! -1:00 W-Eur ACT%s Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:08 - FMT 1911 May 24 # Funchal Mean Time ! -1:00 Port ACT%s 1966 Apr 3 2:00 ! 0:00 - WET 1977 Mar 27 ! 0:00 Port WET%s 1983 Sep 25 1:00s ! 0:00 EU WET%s # Romania - # Catholic Romania switched from the Julian to the Gregorian calendar on - # on 1919 Mar 18. Greek Orthodox Romania switched on 1920 Mar 18. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Romania 1932 only - May 21 0:00s 1:00 " DST" Rule Romania 1932 1939 - Oct Sun>=1 0:00s 0 - ! Rule Romania 1933 1939 - Apr Sun>=2 0:00s 1:00 " DST" ! Rule Romania 1979 only - May 27 0:00 1:00 " DST" Rule Romania 1979 only - Sep lastSun 0:00 0 - ! Rule Romania 1980 only - Apr 5 23:00 1:00 " DST" Rule Romania 1980 only - Sep lastSun 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct ! 1:44 - BMT 1931 Jul 24 # Bucharest MT ! 2:00 Romania EET%s 1981 Mar 29 2:00s ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. # Russia ! # From Paul Eggert <eggert(a)twinsun.com> (May 28, 1994): ! # Moscow and Novosibirsk time zone names, and Moscow rules after 1991, ! # are from Andrew A. Chernov <ache(a)astral.msk.su>. ! # I invented the other time zone names, and (unless otherwise specified) # guessed what happened after 1991; the clocks were chaotic, and we know little. # The rest is from Shanks. # - # From Shanks (1991): - # Western Russia switched from the Julian to the Gregorian calendar - # on 1918 Jan 14. Eastern Russia switched on 1920 Mar 18. - # In 1929 the Soviet Union instituted a 5 day week; in 1932 it instituted - # a 6 day week; on 1940 Jun 27 it returned to the Gregorian week. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Moscow 2:30:20 - LMT 1880 ! 2:31 Russia LST%s 1919 Jul 1 2:00 ! 3:00 Russia MS%s 1922 Oct 2:00 - EET 1930 Jun 21 ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MS%s Zone Europe/Kuybyshev 3:20:36 - LMT 1924 May 2 ! 3:00 - KSK 1957 Mar ! 4:00 Russia KS%s 1991 Mar 31 2:00s ! 3:00 1:00 KSD 1991 Sep 29 2:00s ! 3:00 - KSK 1992 Jan 19 2:00s ! 4:00 Russia KS%s Zone Asia/Yekaterinburg 4:02:34 - LMT 1924 May 2 ! 4:00 - SSK 1957 Mar ! 5:00 Russia SS%s 1991 Mar 31 2:00s ! 4:00 1:00 SSD 1991 Sep 29 2:00s ! 4:00 - SSK 1992 Jan 19 2:00s ! 5:00 Russia ES%s # name change from Sverdlovsk Zone Asia/Omsk 4:53:36 - LMT 1924 May 2 ! 5:00 - OSK 1957 Mar ! 6:00 Russia OS%s 1991 Mar 31 2:00s ! 5:00 1:00 OSD 1991 Sep 29 2:00s ! 5:00 - OSK 1992 Jan 19 2:00s ! 6:00 Russia OS%s # From Stanislaw A. Kuzikowski <S.A.Kuz(a)iae.nsk.su> (June 29, 1994): # But now it is some months since Novosibirsk is 3 hours ahead of Moscow! # I do not know why they have decided to make this change; # as far as I remember it was done exactly during winter->summer switching # so we (Novosibirsk) simply did not switch. Zone Asia/Novosibirsk 5:31:40 - LMT 1924 May 2 ! 6:00 - NSK 1957 Mar ! 7:00 Russia NS%s 1991 Mar 31 2:00s ! 6:00 1:00 NSD 1991 Sep 29 2:00s ! 6:00 - NSK 1992 Jan 19 2:00s ! 7:00 Russia NS%s 1994 Mar 27 2:00s ! 6:00 1:00 NSD 1994 Sep 25 2:00s ! 6:00 Russia NS%s Zone Asia/Krasnoyarsk 6:11:20 - LMT 1924 May 2 ! 6:00 - KRSK 1957 Mar ! 7:00 Russia KRS%s 1991 Mar 31 2:00s ! 6:00 1:00 KRSD 1991 Sep 29 2:00s ! 6:00 - KRSK 1992 Jan 19 2:00s ! 7:00 Russia KRS%s Zone Asia/Irkutsk 6:57:20 - LMT 1880 ! 6:57 - LST 1924 May 2 ! 7:00 - ISK 1957 Mar ! 8:00 Russia IS%s 1991 Mar 31 2:00s ! 7:00 1:00 ISD 1991 Sep 29 2:00s ! 7:00 - ISK 1992 Jan 19 2:00s ! 8:00 Russia IS%s Zone Asia/Yakutsk 8:38:40 - LMT 1924 May 2 ! 8:00 - YSK 1957 Mar ! 9:00 Russia YS%s 1991 Mar 31 2:00s ! 8:00 1:00 YSD 1991 Sep 29 2:00s ! 8:00 - YSK 1992 Jan 19 2:00s ! 9:00 Russia YS%s Zone Asia/Vladivostok 8:47:44 - LMT 1880 ! 8:48 - LST 1924 May 2 ! 9:00 - VSK 1957 Mar ! 10:00 Russia VS%s 1991 Mar 31 2:00s ! 9:00 1:00 VSD 1991 Sep 29 2:00s ! 9:00 - VSK 1992 Jan 19 2:00s ! 10:00 Russia VS%s Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 ! 10:00 - MSK 1957 Mar ! 11:00 Russia MS%s 1991 Mar 31 2:00s ! 10:00 1:00 MSD 1991 Sep 29 2:00s ! 10:00 - MSK 1992 Jan 19 2:00s ! 11:00 Russia MS%s # This name should be Asia/Petropavlovsk-Kamchatski, but that's too long. Zone Asia/Kamchatka 10:34:36 - LMT 1924 May 2 ! 11:00 - PSK 1957 Mar ! 12:00 Russia PS%s 1991 Mar 31 2:00s ! 11:00 1:00 PSD 1991 Sep 29 2:00s ! 11:00 - PSK 1992 Jan 19 2:00s ! 12:00 Russia PS%s Zone Asia/Anadyr 11:49:56 - LMT 1924 May 2 ! 12:00 - ASK 1957 Mar ! 13:00 Russia AS%s 1991 Mar 31 2:00s ! 12:00 1:00 ASD 1991 Sep 29 2:00s ! 12:00 - ASK 1992 Jan 19 2:00s ! 13:00 Russia AS%s # Slovakia Link Europe/Prague Europe/Bratislava # Slovenia - # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Ljubljana 0:58:04 - LMT 1884 ! 1:00 - MET 1941 Apr 18 23:00 ! 1:00 M-Eur MET%s 1945 May 8 2:00s ! 1:00 1:00 "MET DST" 1945 Sep 16 2:00s ! 1:00 - MET 1983 ! 1:00 EU MET%s # Spain # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # For 1917-1919 Whitman gives Apr Sat>=1 - Oct Sat>=1; go with Shanks. ! Rule Spain 1917 only - May 5 23:00s 1:00 " DST" Rule Spain 1917 1919 - Oct 6 23:00s 0 - ! Rule Spain 1918 only - Apr 15 23:00s 1:00 " DST" ! Rule Spain 1919 only - Apr 5 23:00s 1:00 " DST" # Whitman gives 1921 Feb 28 - Oct 14; go with Shanks. ! Rule Spain 1924 only - Apr 16 23:00s 1:00 " DST" # Whitman gives 1924 Oct 14; go with Shanks. Rule Spain 1924 only - Oct 4 23:00s 0 - ! Rule Spain 1926 only - Apr 17 23:00s 1:00 " DST" # Whitman says no DST in 1929; go with Shanks. Rule Spain 1926 1929 - Oct Sat>=1 23:00s 0 - ! Rule Spain 1927 only - Apr 9 23:00s 1:00 " DST" ! Rule Spain 1928 only - Apr 14 23:00s 1:00 " DST" ! Rule Spain 1929 only - Apr 20 23:00s 1:00 " DST" # Whitman gives 1937 Jun 16, 1938 Apr 16, 1940 Apr 13; go with Shanks. ! Rule Spain 1937 only - May 22 23:00s 1:00 " DST" Rule Spain 1937 1939 - Oct Sat>=1 23:00s 0 - ! Rule Spain 1938 only - Mar 22 23:00s 1:00 " DST" ! Rule Spain 1939 only - Apr 15 23:00s 1:00 " DST" ! Rule Spain 1940 only - Mar 16 23:00s 1:00 " DST" # Whitman says no DST 1942-1945; go with Shanks. ! Rule Spain 1942 only - May 2 22:00s 2:00 " DDST" ! Rule Spain 1942 only - Sep 1 22:00s 1:00 " DST" ! Rule Spain 1943 1946 - Apr Sat>=13 22:00s 2:00 " DDST" ! Rule Spain 1943 only - Oct 3 22:00s 1:00 " DST" ! Rule Spain 1944 only - Oct 10 22:00s 1:00 " DST" ! Rule Spain 1945 only - Sep 30 1:00 1:00 " DST" Rule Spain 1946 only - Sep 30 0:00 0 - ! Rule Spain 1949 only - Apr 30 23:00 1:00 " DST" Rule Spain 1949 only - Sep 30 1:00 0 - ! Rule Spain 1974 1975 - Apr Sat>=13 23:00 1:00 " DST" Rule Spain 1974 1975 - Oct Sun>=1 1:00 0 - ! Rule Spain 1976 only - Mar 27 23:00 1:00 " DST" Rule Spain 1976 1977 - Sep lastSun 1:00 0 - ! Rule Spain 1977 1978 - Apr 2 23:00 1:00 " DST" Rule Spain 1978 only - Oct 1 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Madrid -0:14:44 - LMT 1901 ! 0:00 Spain WET%s 1946 Sep 30 ! 1:00 Spain MET%s 1979 ! 1:00 EU MET%s Zone Atlantic/Canary -1:01:36 - LMT 1922 Mar # Las Palmas de Gran C. ! -1:00 - ACT 1946 Sep 30 1:00 0:00 - WET 1980 Apr 6 0:00s ! 0:00 1:00 "WET DST" 1980 Sep 28 0:00s ! 0:00 EU WET%s # Sweden # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Stockholm 1:12:12 - LMT 1878 May 31 ! 1:12 - SMT 1900 Jan 1 1:00 # Stockholm MT ! 1:00 - MET 1916 Apr 14 23:00s ! 1:00 1:00 "MET DST" 1916 Sep 30 23:00s ! 1:00 - MET 1980 ! 1:00 EU MET%s # Switzerland # From Howse (1988), p 82: --- 1554,1952 ---- Rule Neth 1932 only - May 22 2:00s 1:00 NST Rule Neth 1933 1936 - May 15 2:00s 1:00 NST Rule Neth 1937 only - May 22 2:00s 1:00 NST + Rule Neth 1937 only - Jul 1 0:00 1:00 S + Rule Neth 1937 1939 - Oct Sun>=2 2:00s 0 - # Whitman gives 1939 Apr 15 and 1940 Apr 19; go with Shanks. ! Rule Neth 1938 1939 - May 15 2:00s 1:00 S ! Rule Neth 1945 only - Apr 2 2:00s 1:00 S Rule Neth 1945 only - May 20 2:00s 0 - # Before 1937, Shanks says just `0:20'; we use Whitman's more precise figure. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Amsterdam 0:19:28 - LMT 1892 May 0:19:28 Neth %s 1937 Jul ! 0:20 Neth NE%sT 1940 May 16 0:40 ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Neth CE%sT 1977 ! 1:00 EU CE%sT # Norway + # Gregorian calendar adopted 1700-03-01. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1916 May 21 - 1916 Oct 21; go with Shanks. ! Rule Norway 1916 only - May 22 1:00 1:00 S Rule Norway 1916 only - Sep 30 0:00 0 - # Shanks omits the following transition; go with Whitman. ! Rule Norway 1935 only - Aug 11 0:00 1:00 S # Whitman says DST observed until 1942 Nov 1, then 1943 Mar 29 - Oct 4, # 1944 Apr 3 - Oct 2, and 1945 Apr 1 - Oct 1; go with Shanks after 1940. ! Rule Norway 1945 only - Apr 2 2:00s 1:00 S Rule Norway 1945 only - Oct 1 2:00s 0 - ! Rule Norway 1959 1964 - Mar Sun>=15 2:00s 1:00 S Rule Norway 1959 1965 - Sep Sun>=15 2:00s 0 - ! Rule Norway 1965 only - Apr 25 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Oslo 0:43:00 - LMT 1895 ! 1:00 Norway CE%sT 1940 Aug 10 23:00 ! 1:00 C-Eur CE%sT 1945 Apr 2 2:00 ! 1:00 Norway CE%sT 1980 ! 1:00 EU CE%sT # + # Svalbard + Link Europe/Oslo Arctic/Longyearbyen + # + # Jan Mayen # From Whitman: # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Jan_Mayen -1:00 - EGT # Poland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Poland 1918 1919 - Sep 16 2:00s 0 - ! Rule Poland 1919 only - Apr 15 2:00s 1:00 S # Whitman gives 1944 Nov 30; go with Shanks. Rule Poland 1944 only - Oct 4 2:00 0 - # For 1944-1948 Whitman gives the previous day; go with Shanks. ! Rule Poland 1945 only - Apr 29 0:00 1:00 S Rule Poland 1945 only - Nov 1 0:00 0 - ! Rule Poland 1946 only - Apr 14 0:00 1:00 S Rule Poland 1946 only - Sep 7 0:00 0 - ! Rule Poland 1947 only - May 4 0:00 1:00 S Rule Poland 1947 1948 - Oct Sun>=1 0:00 0 - ! Rule Poland 1948 only - Apr 18 0:00 1:00 S # Whitman also gives 1949 Apr 9 - 1949 Oct 1; go with Shanks. ! Rule Poland 1957 only - Jun 2 1:00s 1:00 S Rule Poland 1957 1958 - Sep lastSun 1:00s 0 - ! Rule Poland 1958 only - Mar 30 1:00s 1:00 S ! Rule Poland 1959 only - May 31 1:00s 1:00 S Rule Poland 1959 1961 - Oct Sun>=1 1:00s 0 - ! Rule Poland 1960 only - Apr 3 1:00s 1:00 S ! Rule Poland 1961 1964 - May Sun>=25 1:00s 1:00 S Rule Poland 1962 1964 - Sep lastSun 1:00s 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Warsaw 1:24:00 - LMT 1880 ! 1:24:00 - WMT 1915 Aug 5 # Warsaw Mean Time ! 1:00 C-Eur CE%sT 1918 Sep 16 3:00 ! 2:00 Poland EE%sT 1922 Jun ! 1:00 Poland CE%sT 1940 Jun 23 2:00 ! 1:00 C-Eur CE%sT 1944 Oct ! 1:00 Poland CE%sT 1977 Apr 3 1:00 ! 1:00 W-Eur CE%sT # Portugal + # Gregorian calendar adopted 1582-10-15. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Port 1916 only - Jun 17 23:00 1:00 S # Whitman gives 1916 Oct 31; go with Shanks. Rule Port 1916 only - Nov 1 1:00 0 - ! Rule Port 1917 only - Feb 28 23:00s 1:00 S Rule Port 1917 1921 - Oct 14 23:00s 0 - ! Rule Port 1918 only - Mar 1 23:00s 1:00 S ! Rule Port 1919 only - Feb 28 23:00s 1:00 S ! Rule Port 1920 only - Feb 29 23:00s 1:00 S ! Rule Port 1921 only - Feb 28 23:00s 1:00 S ! Rule Port 1924 only - Apr 16 23:00s 1:00 S Rule Port 1924 only - Oct 14 23:00s 0 - ! Rule Port 1926 only - Apr 17 23:00s 1:00 S Rule Port 1926 1929 - Oct Sat>=1 23:00s 0 - ! Rule Port 1927 only - Apr 9 23:00s 1:00 S ! Rule Port 1928 only - Apr 14 23:00s 1:00 S ! Rule Port 1929 only - Apr 20 23:00s 1:00 S ! Rule Port 1931 only - Apr 18 23:00s 1:00 S # Whitman gives 1931 Oct 8; go with Shanks. Rule Port 1931 1932 - Oct Sat>=1 23:00s 0 - ! Rule Port 1932 only - Apr 2 23:00s 1:00 S # Shanks gives 1934 Apr 4; go with Whitman. ! Rule Port 1934 only - Apr 7 23:00s 1:00 S # Whitman gives 1934 Oct 5; go with Shanks. Rule Port 1934 1938 - Oct Sat>=1 23:00s 0 - # Shanks gives 1935 Apr 30; go with Whitman. ! Rule Port 1935 only - Mar 30 23:00s 1:00 S ! Rule Port 1936 only - Apr 18 23:00s 1:00 S # Whitman gives 1937 Apr 2; go with Shanks. ! Rule Port 1937 only - Apr 3 23:00s 1:00 S ! Rule Port 1938 only - Mar 26 23:00s 1:00 S ! Rule Port 1939 only - Apr 15 23:00s 1:00 S # Whitman gives 1939 Oct 7; go with Shanks. Rule Port 1939 only - Nov 18 23:00s 0 - ! Rule Port 1940 only - Feb 24 23:00s 1:00 S # Shanks gives 1940 Oct 7; go with Whitman. Rule Port 1940 1941 - Oct 5 23:00s 0 - ! Rule Port 1941 only - Apr 5 23:00s 1:00 S ! Rule Port 1942 1945 - Mar Sat>=8 23:00s 1:00 S ! Rule Port 1942 only - Apr 25 22:00s 2:00 DS ! Rule Port 1942 only - Aug 15 22:00s 1:00 S Rule Port 1942 1945 - Oct Sat>=24 23:00s 0 - ! Rule Port 1943 only - Apr 17 22:00s 2:00 DS ! Rule Port 1943 1945 - Aug Sat>=25 22:00s 1:00 S ! Rule Port 1944 1945 - Apr Sat>=21 22:00s 2:00 DS ! Rule Port 1946 only - Apr Sat>=1 23:00s 1:00 S Rule Port 1946 only - Oct Sat>=1 23:00s 0 - ! Rule Port 1947 1949 - Apr Sun>=1 2:00s 1:00 S Rule Port 1947 1949 - Oct Sun>=1 2:00s 0 - # Shanks says DST was observed in 1950; go with Whitman. # Whitman gives Oct lastSun for 1952 on; go with Shanks. ! Rule Port 1951 1965 - Apr Sun>=1 2:00s 1:00 S Rule Port 1951 1965 - Oct Sun>=1 2:00s 0 - ! Rule Port 1977 only - Mar 27 0:00s 1:00 S Rule Port 1977 only - Sep 25 0:00s 0 - ! Rule Port 1978 1979 - Apr Sun>=1 0:00s 1:00 S Rule Port 1978 only - Oct 1 0:00s 0 - Rule Port 1979 1982 - Sep lastSun 1:00s 0 - ! Rule Port 1980 only - Mar lastSun 0:00s 1:00 S ! Rule Port 1981 1982 - Mar lastSun 1:00s 1:00 S ! Rule Port 1983 only - Mar lastSun 2:00s 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Lisbon -0:36:32 - LMT 1884 ! -0:36:32 - LMT 1911 May 24 # Lisbon Mean Time ! 0:00 Port WE%sT 1966 Apr 3 2:00 ! 1:00 - CET 1976 Sep 26 1:00 ! 0:00 Port WE%sT 1983 Sep 25 1:00s # From Rui Pedro Salgueiro <rps(a)inescca.inescc.pt> (November 12, 1992): # Portugal has recently (September, 27) changed timezone # (from WET to MET or CET) to harmonize with EEC. ! 0:00 EU WE%sT 1992 Sep 27 1:00s # Martin Bruckmann <martin(a)ua.pt> (1996-02-29) reports via Peter Ilieve # that Portugal is reverting to 0:00 by not moving its clocks this spring. # The new Prime Minister was fed up with getting up in the dark in the winter. ! 1:00 EU CE%sT 1996 Mar 31 1:00u ! 0:00 EU WE%sT # We don't know what happened to Madeira or the Azores, # so we'll just use Shanks for now. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Azores -1:42:40 - LMT 1884 # Ponta Delgada -1:55 - HMT 1911 May 24 # Horta Mean Time ! -2:00 Port AZO%sT 1966 Apr 3 2:00 # Azores Time ! -1:00 Port AZO%sT 1983 Sep 25 1:00s ! -1:00 W-Eur AZO%sT Zone Atlantic/Madeira -1:07:36 - LMT 1884 # Funchal -1:08 - FMT 1911 May 24 # Funchal Mean Time ! -1:00 Port MAD%sT 1966 Apr 3 2:00 # Madeira Time ! 0:00 Port WE%sT 1983 Sep 25 1:00s ! 0:00 EU WE%sT # Romania # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Romania 1932 only - May 21 0:00s 1:00 S Rule Romania 1932 1939 - Oct Sun>=1 0:00s 0 - ! Rule Romania 1933 1939 - Apr Sun>=2 0:00s 1:00 S ! Rule Romania 1979 only - May 27 0:00 1:00 S Rule Romania 1979 only - Sep lastSun 0:00 0 - ! Rule Romania 1980 only - Apr 5 23:00 1:00 S Rule Romania 1980 only - Sep lastSun 1:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Bucharest 1:44:24 - LMT 1891 Oct ! 1:44:24 - BMT 1931 Jul 24 # Bucharest MT ! 2:00 Romania EE%sT 1981 Mar 29 2:00s ! 2:00 C-Eur EE%sT # Russia ! # From Shanks (1991): ! # In 1929 the Soviet Union instituted a 5 day week; in 1932 it instituted ! # a 6 day week; on 1940-06-27 it returned to the Gregorian week. ! # ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): ! # Moscow rules after 1991 are from Andrew A. Chernov <ache(a)astral.msk.su>. ! # I invented the time zone names, and (unless otherwise specified) # guessed what happened after 1991; the clocks were chaotic, and we know little. # The rest is from Shanks. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Moscow 2:30:20 - LMT 1880 ! 2:30:20 Russia %s 1919 Jul 1 2:00 ! 3:00 Russia MOS%sT 1922 Oct # Moscow TIme 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MOS%sT Zone Europe/Kuybyshev 3:20:36 - LMT 1924 May 2 ! 3:00 - KUYT 1957 Mar # Kuybyshev Time ! 4:00 Russia KUY%sT 1991 Mar 31 2:00s ! 3:00 1:00 KUYST 1991 Sep 29 2:00s ! 3:00 - KUYT 1992 Jan 19 2:00s ! 4:00 Russia KUY%sT Zone Asia/Yekaterinburg 4:02:34 - LMT 1924 May 2 ! 4:00 - SVET 1957 Mar # Sverdlovsk Time ! 5:00 Russia SVE%sT 1991 Mar 31 2:00s ! 4:00 1:00 SVEST 1991 Sep 29 2:00s ! 4:00 - SVET 1992 Jan 19 2:00s ! 5:00 Russia YEK%sT # Yekaterinburg Time Zone Asia/Omsk 4:53:36 - LMT 1924 May 2 ! 5:00 - OMST 1957 Mar # Omsk Time ! 6:00 Russia OMS%sT 1991 Mar 31 2:00s ! 5:00 1:00 OMSST 1991 Sep 29 2:00s ! 5:00 - OMST 1992 Jan 19 2:00s ! 6:00 Russia OMS%sT # From Stanislaw A. Kuzikowski <S.A.Kuz(a)iae.nsk.su> (June 29, 1994): # But now it is some months since Novosibirsk is 3 hours ahead of Moscow! # I do not know why they have decided to make this change; # as far as I remember it was done exactly during winter->summer switching # so we (Novosibirsk) simply did not switch. Zone Asia/Novosibirsk 5:31:40 - LMT 1924 May 2 ! 6:00 - NOVT 1957 Mar # Novosibirsk TIme ! 7:00 Russia NOV%sT 1991 Mar 31 2:00s ! 6:00 1:00 NOVST 1991 Sep 29 2:00s ! 6:00 - NOVT 1992 Jan 19 2:00s ! 7:00 Russia NOV%sT 1994 Mar 27 2:00s ! 6:00 1:00 NOVST 1994 Sep 25 2:00s ! 6:00 Russia NOV%sT Zone Asia/Krasnoyarsk 6:11:20 - LMT 1924 May 2 ! 6:00 - KRAT 1957 Mar # Krasnoyarsk Time ! 7:00 Russia KRA%sT 1991 Mar 31 2:00s ! 6:00 1:00 KRAST 1991 Sep 29 2:00s ! 6:00 - KRAT 1992 Jan 19 2:00s ! 7:00 Russia KRA%sT Zone Asia/Irkutsk 6:57:20 - LMT 1880 ! 6:57:20 - IMT 1924 May 2 # Irkutsk Mean Time ! 7:00 - IRKT 1957 Mar # Irkutsk Time ! 8:00 Russia IRK%sT 1991 Mar 31 2:00s ! 7:00 1:00 IRKST 1991 Sep 29 2:00s ! 7:00 - IRKT 1992 Jan 19 2:00s ! 8:00 Russia IRK%sT Zone Asia/Yakutsk 8:38:40 - LMT 1924 May 2 ! 8:00 - YAKT 1957 Mar # Yakutsk Time ! 9:00 Russia YAK%sT 1991 Mar 31 2:00s ! 8:00 1:00 YAKST 1991 Sep 29 2:00s ! 8:00 - YAKT 1992 Jan 19 2:00s ! 9:00 Russia YAK%sT Zone Asia/Vladivostok 8:47:44 - LMT 1880 ! 8:47:44 - VMT 1924 May 2 # Vladivostok MT ! 9:00 - VLAT 1957 Mar # Vladivostok Time ! 10:00 Russia VLA%sT 1991 Mar 31 2:00s ! 9:00 1:00 VLAST 1991 Sep 29 2:00s ! 9:00 - VLAT 1992 Jan 19 2:00s ! 10:00 Russia VLA%sT Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 ! 10:00 - MAGT 1957 Mar # Magadan Time ! 11:00 Russia MAG%sT 1991 Mar 31 2:00s ! 10:00 1:00 MAGST 1991 Sep 29 2:00s ! 10:00 - MAGT 1992 Jan 19 2:00s ! 11:00 Russia MAG%sT # This name should be Asia/Petropavlovsk-Kamchatski, but that's too long. Zone Asia/Kamchatka 10:34:36 - LMT 1924 May 2 ! 11:00 - PETT 1957 Mar # P-K Time ! 12:00 Russia PET%sT 1991 Mar 31 2:00s ! 11:00 1:00 PETST 1991 Sep 29 2:00s ! 11:00 - PETT 1992 Jan 19 2:00s ! 12:00 Russia PET%sT Zone Asia/Anadyr 11:49:56 - LMT 1924 May 2 ! 12:00 - ANAT 1957 Mar # Anadyr Time ! 13:00 Russia ANA%sT 1991 Mar 31 2:00s ! 12:00 1:00 ANAST 1991 Sep 29 2:00s ! 12:00 - ANAT 1992 Jan 19 2:00s ! 13:00 Russia ANA%sT # Slovakia Link Europe/Prague Europe/Bratislava # Slovenia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Ljubljana 0:58:04 - LMT 1884 ! 1:00 - CET 1941 Apr 18 23:00 ! 1:00 C-Eur CE%sT 1945 May 8 2:00s ! 1:00 1:00 CEST 1945 Sep 16 2:00s ! 1:00 - CET 1983 ! 1:00 EU CE%sT # Spain + # Gregorian calendar adopted 1582-10-15. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # For 1917-1919 Whitman gives Apr Sat>=1 - Oct Sat>=1; go with Shanks. ! Rule Spain 1917 only - May 5 23:00s 1:00 S Rule Spain 1917 1919 - Oct 6 23:00s 0 - ! Rule Spain 1918 only - Apr 15 23:00s 1:00 S ! Rule Spain 1919 only - Apr 5 23:00s 1:00 S # Whitman gives 1921 Feb 28 - Oct 14; go with Shanks. ! Rule Spain 1924 only - Apr 16 23:00s 1:00 S # Whitman gives 1924 Oct 14; go with Shanks. Rule Spain 1924 only - Oct 4 23:00s 0 - ! Rule Spain 1926 only - Apr 17 23:00s 1:00 S # Whitman says no DST in 1929; go with Shanks. Rule Spain 1926 1929 - Oct Sat>=1 23:00s 0 - ! Rule Spain 1927 only - Apr 9 23:00s 1:00 S ! Rule Spain 1928 only - Apr 14 23:00s 1:00 S ! Rule Spain 1929 only - Apr 20 23:00s 1:00 S # Whitman gives 1937 Jun 16, 1938 Apr 16, 1940 Apr 13; go with Shanks. ! Rule Spain 1937 only - May 22 23:00s 1:00 S Rule Spain 1937 1939 - Oct Sat>=1 23:00s 0 - ! Rule Spain 1938 only - Mar 22 23:00s 1:00 S ! Rule Spain 1939 only - Apr 15 23:00s 1:00 S ! Rule Spain 1940 only - Mar 16 23:00s 1:00 S # Whitman says no DST 1942-1945; go with Shanks. ! Rule Spain 1942 only - May 2 22:00s 2:00 DS ! Rule Spain 1942 only - Sep 1 22:00s 1:00 S ! Rule Spain 1943 1946 - Apr Sat>=13 22:00s 2:00 DS ! Rule Spain 1943 only - Oct 3 22:00s 1:00 S ! Rule Spain 1944 only - Oct 10 22:00s 1:00 S ! Rule Spain 1945 only - Sep 30 1:00 1:00 S Rule Spain 1946 only - Sep 30 0:00 0 - ! Rule Spain 1949 only - Apr 30 23:00 1:00 S Rule Spain 1949 only - Sep 30 1:00 0 - ! Rule Spain 1974 1975 - Apr Sat>=13 23:00 1:00 S Rule Spain 1974 1975 - Oct Sun>=1 1:00 0 - ! Rule Spain 1976 only - Mar 27 23:00 1:00 S Rule Spain 1976 1977 - Sep lastSun 1:00 0 - ! Rule Spain 1977 1978 - Apr 2 23:00 1:00 S Rule Spain 1978 only - Oct 1 1:00 0 - + # The following rules are copied from Morocco from 1967 through 1978. + Rule SpainAfrica 1967 only - Jun 3 12:00 1:00 S + Rule SpainAfrica 1967 only - Oct 1 0:00 0 - + Rule SpainAfrica 1974 only - Jun 24 0:00 1:00 S + Rule SpainAfrica 1974 only - Sep 1 0:00 0 - + Rule SpainAfrica 1976 1977 - May 1 0:00 1:00 S + Rule SpainAfrica 1976 only - Aug 1 0:00 0 - + Rule SpainAfrica 1977 only - Sep 28 0:00 0 - + Rule SpainAfrica 1978 only - Jun 1 0:00 1:00 S + Rule SpainAfrica 1978 only - Aug 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Madrid -0:14:44 - LMT 1901 ! 0:00 Spain WE%sT 1946 Sep 30 ! 1:00 Spain CE%sT 1979 ! 1:00 EU CE%sT ! Zone Africa/Ceuta -0:21:16 - LMT 1901 ! 0:00 - WET 1918 May 6 23:00 ! 0:00 1:00 WEST 1918 Oct 7 23:00 ! 0:00 - WET 1924 ! 0:00 Spain WE%sT 1929 ! 0:00 SpainAfrica WE%sT 1984 Mar 16 ! 1:00 - CET 1986 ! 1:00 EU CE%sT Zone Atlantic/Canary -1:01:36 - LMT 1922 Mar # Las Palmas de Gran C. ! -1:00 - CANT 1946 Sep 30 1:00 # Canaries Time 0:00 - WET 1980 Apr 6 0:00s ! 0:00 1:00 WEST 1980 Sep 28 0:00s ! 0:00 EU WE%sT # Sweden + + # From: msb(a)sq.com (Mark Brader) <URL:news:1996Jul6.012937.29190@sq.com>: + # + # In 1700, Denmark made the transition from Julian to Gregorian. Sweden + # decided to *start* a transition in 1700 as well, but rather than have one of + # those unsightly calendar gaps :-), they simply decreed that the next leap + # year after 1696 would be in 1744 -- putting the whole country on a calendar + # different from both Julian and Gregorian for a period of 40 years. + # + # However, in 1704 something went wrong and the plan was not carried through; + # they did, after all, have a leap year that year. And one in 1708. In 1712 + # they gave it up and went back to Julian, putting 30 days in February that + # year!... + # + # Then in 1753, Sweden made the transition to Gregorian in the usual manner, + # getting there only 13 years behind the original schedule. + # + # (A previous posting of this story was challenged, and Swedish readers + # produced the following references to support it: "Tiderakning och historia" + # by Natanael Beckman (1924) and "Tid, en bok om tiderakning och + # kalendervasen" by Lars-Olof Lode'n (no date was given).) + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Stockholm 1:12:12 - LMT 1878 May 31 ! 1:12:12 - SMT 1900 Jan 1 1:00 # Stockholm MT ! 1:00 - CET 1916 Apr 14 23:00s ! 1:00 1:00 CEST 1916 Sep 30 23:00s ! 1:00 - CET 1980 ! 1:00 EU CE%sT # Switzerland # From Howse (1988), p 82: *************** *** 1910,2030 **** # mean time in preference to apparent time -- Geneva from 1780 .... # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # From Whitman (who writes ``Midnight?''): ! Rule Swiss 1940 only - Nov 2 0:00 1:00 " DST" Rule Swiss 1940 only - Dec 31 0:00 0 - # From Shanks (1991): ! Rule Swiss 1941 1942 - May Sun>=1 2:00 1:00 " DST" Rule Swiss 1941 1942 - Oct Sun>=1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Zurich 0:34:08 - LMT 1848 Sep 12 ! 0:30 - SST 1894 Jun # Swiss Standard Time ! 1:00 Swiss MET%s 1981 ! 1:00 EU MET%s # Turkey - # European Turkey switched to the Gregorian calendar in 1908. - # Asian Turkey switched in 1914. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Turkey 1916 only - May 1 0:00 1:00 " DST" Rule Turkey 1916 only - Oct 1 0:00 0 - ! Rule Turkey 1920 only - Mar 28 0:00 1:00 " DST" Rule Turkey 1920 only - Oct 25 0:00 0 - ! Rule Turkey 1921 only - Apr 3 0:00 1:00 " DST" Rule Turkey 1921 only - Oct 3 0:00 0 - ! Rule Turkey 1922 only - Mar 26 0:00 1:00 " DST" Rule Turkey 1922 only - Oct 8 0:00 0 - # Whitman gives 1923 Apr 28 - Sep 16 and no DST in 1924-1925; go with Shanks. ! Rule Turkey 1924 only - May 13 0:00 1:00 " DST" Rule Turkey 1924 1925 - Oct 1 0:00 0 - ! Rule Turkey 1925 only - May 1 0:00 1:00 " DST" # Shanks omits the first two transitions in 1940; go with Whitman. ! Rule Turkey 1940 only - Jun 30 0:00 1:00 " DST" Rule Turkey 1940 only - Oct 5 0:00 0 - ! Rule Turkey 1940 only - Dec 1 0:00 1:00 " DST" Rule Turkey 1941 only - Sep 21 0:00 0 - ! Rule Turkey 1942 only - Apr 1 0:00 1:00 " DST" # Whitman omits the next two transition and gives 1945 Oct 1; go with Shanks. Rule Turkey 1942 only - Nov 1 0:00 0 - ! Rule Turkey 1945 only - Apr 2 0:00 1:00 " DST" Rule Turkey 1945 only - Oct 8 0:00 0 - ! Rule Turkey 1946 only - Jun 1 0:00 1:00 " DST" Rule Turkey 1946 only - Oct 1 0:00 0 - ! Rule Turkey 1947 1948 - Apr Sun>=16 0:00 1:00 " DST" Rule Turkey 1947 1950 - Oct Sun>=2 0:00 0 - ! Rule Turkey 1949 only - Apr 10 0:00 1:00 " DST" ! Rule Turkey 1950 only - Apr 19 0:00 1:00 " DST" ! Rule Turkey 1951 only - Apr 22 0:00 1:00 " DST" Rule Turkey 1951 only - Oct 8 0:00 0 - ! Rule Turkey 1962 only - Jul 15 0:00 1:00 " DST" Rule Turkey 1962 only - Oct 8 0:00 0 - ! Rule Turkey 1964 only - May 15 0:00 1:00 " DST" Rule Turkey 1964 only - Oct 1 0:00 0 - ! Rule Turkey 1970 1972 - May Sun>=2 0:00 1:00 " DST" Rule Turkey 1970 1972 - Oct Sun>=2 0:00 0 - ! Rule Turkey 1973 only - Jun 3 1:00 1:00 " DST" Rule Turkey 1973 only - Nov 4 3:00 0 - ! Rule Turkey 1974 only - Mar 31 2:00 1:00 " DST" Rule Turkey 1974 only - Nov 3 5:00 0 - ! Rule Turkey 1975 only - Mar 30 0:00 1:00 " DST" Rule Turkey 1975 1976 - Oct lastSun 0:00 0 - ! Rule Turkey 1976 only - Jun 1 0:00 1:00 " DST" ! Rule Turkey 1977 1978 - Apr Sun>=1 0:00 1:00 " DST" Rule Turkey 1977 only - Oct 16 0:00 0 - ! Rule Turkey 1979 1980 - Apr Sun>=1 3:00 1:00 " DST" Rule Turkey 1979 1982 - Oct Mon>=11 0:00 0 - ! Rule Turkey 1981 1982 - Mar lastSun 3:00 1:00 " DST" ! Rule Turkey 1983 only - Jul 31 0:00 1:00 " DST" Rule Turkey 1983 only - Oct 2 0:00 0 - ! Rule Turkey 1985 only - Apr 20 0:00 1:00 " DST" Rule Turkey 1985 only - Sep 28 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Istanbul 1:55:52 - LMT 1880 ! 1:57 - OMT 1910 Oct # Ottoman Mean Time ! 2:00 Turkey EET%s 1978 Oct 15 ! 3:00 Turkey TUR%s 1985 Apr 20 ! 2:00 Turkey EET%s 1986 ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # Ukraine # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Ukraine 1919 only - Jul 1 2:00 1:00 " DST" ! Rule Ukraine 1919 only - Aug 16 0:00 0 - ! Rule Ukraine 1921 only - Feb 14 23:00 1:00 " DST" ! Rule Ukraine 1921 only - Mar 21 23:00 2:00 " DDST" ! Rule Ukraine 1921 only - Sep 1 0:00 1:00 " DST" ! Rule Ukraine 1921 only - Oct 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Kiev 2:02:04 - LMT 1880 ! 2:02 Russia LST%s 1919 Jul 1 2:00 ! 2:02 Ukraine LST%s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MS%s 1990 Jul 17 ! 2:00 M-Eur EET%s ! # This may change to `EU' soon. Zone Europe/Simferopol 2:16:24 - LMT 1880 ! 2:08 Russia LST%s 1919 Jul 1 2:00 ! 2:08 Ukraine LST%s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MS%s 1991 Mar 31 2:00s ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s # From Paul Eggert <eggert(a)twinsun.com> (May 28, 1994): # Today's _Economist_ (p 45) reports that Crimea switched # from Kiev to Moscow time sometime after the January elections. # For now, we'll guess that there was a 2-hour leap forward on March 27. ! 2:00 M-Eur EET%s 1994 Mar 27 2:00s ! 3:00 Russia MS%s # Yugoslavia - # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Belgrade 1:22:00 - LMT 1884 ! 1:00 - MET 1941 Apr 18 23:00 ! 1:00 M-Eur MET%s 1945 May 8 2:00s ! 1:00 1:00 "MET DST" 1945 Sep 16 2:00s ! 1:00 - MET 1983 ! 1:00 EU MET%s ############################################################################### --- 1955,2084 ---- # mean time in preference to apparent time -- Geneva from 1780 .... # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # From Whitman (who writes ``Midnight?''): ! Rule Swiss 1940 only - Nov 2 0:00 1:00 S Rule Swiss 1940 only - Dec 31 0:00 0 - # From Shanks (1991): ! Rule Swiss 1941 1942 - May Sun>=1 2:00 1:00 S Rule Swiss 1941 1942 - Oct Sun>=1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Zurich 0:34:08 - LMT 1848 Sep 12 ! 0:29:44 - BMT 1894 Jun # Bern Mean Time ! 1:00 Swiss CE%sT 1981 ! 1:00 EU CE%sT # Turkey # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Turkey 1916 only - May 1 0:00 1:00 S Rule Turkey 1916 only - Oct 1 0:00 0 - ! Rule Turkey 1920 only - Mar 28 0:00 1:00 S Rule Turkey 1920 only - Oct 25 0:00 0 - ! Rule Turkey 1921 only - Apr 3 0:00 1:00 S Rule Turkey 1921 only - Oct 3 0:00 0 - ! Rule Turkey 1922 only - Mar 26 0:00 1:00 S Rule Turkey 1922 only - Oct 8 0:00 0 - # Whitman gives 1923 Apr 28 - Sep 16 and no DST in 1924-1925; go with Shanks. ! Rule Turkey 1924 only - May 13 0:00 1:00 S Rule Turkey 1924 1925 - Oct 1 0:00 0 - ! Rule Turkey 1925 only - May 1 0:00 1:00 S # Shanks omits the first two transitions in 1940; go with Whitman. ! Rule Turkey 1940 only - Jun 30 0:00 1:00 S Rule Turkey 1940 only - Oct 5 0:00 0 - ! Rule Turkey 1940 only - Dec 1 0:00 1:00 S Rule Turkey 1941 only - Sep 21 0:00 0 - ! Rule Turkey 1942 only - Apr 1 0:00 1:00 S # Whitman omits the next two transition and gives 1945 Oct 1; go with Shanks. Rule Turkey 1942 only - Nov 1 0:00 0 - ! Rule Turkey 1945 only - Apr 2 0:00 1:00 S Rule Turkey 1945 only - Oct 8 0:00 0 - ! Rule Turkey 1946 only - Jun 1 0:00 1:00 S Rule Turkey 1946 only - Oct 1 0:00 0 - ! Rule Turkey 1947 1948 - Apr Sun>=16 0:00 1:00 S Rule Turkey 1947 1950 - Oct Sun>=2 0:00 0 - ! Rule Turkey 1949 only - Apr 10 0:00 1:00 S ! Rule Turkey 1950 only - Apr 19 0:00 1:00 S ! Rule Turkey 1951 only - Apr 22 0:00 1:00 S Rule Turkey 1951 only - Oct 8 0:00 0 - ! Rule Turkey 1962 only - Jul 15 0:00 1:00 S Rule Turkey 1962 only - Oct 8 0:00 0 - ! Rule Turkey 1964 only - May 15 0:00 1:00 S Rule Turkey 1964 only - Oct 1 0:00 0 - ! Rule Turkey 1970 1972 - May Sun>=2 0:00 1:00 S Rule Turkey 1970 1972 - Oct Sun>=2 0:00 0 - ! Rule Turkey 1973 only - Jun 3 1:00 1:00 S Rule Turkey 1973 only - Nov 4 3:00 0 - ! Rule Turkey 1974 only - Mar 31 2:00 1:00 S Rule Turkey 1974 only - Nov 3 5:00 0 - ! Rule Turkey 1975 only - Mar 30 0:00 1:00 S Rule Turkey 1975 1976 - Oct lastSun 0:00 0 - ! Rule Turkey 1976 only - Jun 1 0:00 1:00 S ! Rule Turkey 1977 1978 - Apr Sun>=1 0:00 1:00 S Rule Turkey 1977 only - Oct 16 0:00 0 - ! Rule Turkey 1979 1980 - Apr Sun>=1 3:00 1:00 S Rule Turkey 1979 1982 - Oct Mon>=11 0:00 0 - ! Rule Turkey 1981 1982 - Mar lastSun 3:00 1:00 S ! Rule Turkey 1983 only - Jul 31 0:00 1:00 S Rule Turkey 1983 only - Oct 2 0:00 0 - ! Rule Turkey 1985 only - Apr 20 0:00 1:00 S Rule Turkey 1985 only - Sep 28 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Istanbul 1:55:52 - LMT 1880 ! 1:56:56 - IMT 1910 Oct # Istanbul Mean Time? ! 2:00 Turkey EE%sT 1978 Oct 15 ! 3:00 Turkey TR%sT 1985 Apr 20 # Turkey Time ! 2:00 Turkey EE%sT 1986 ! 2:00 C-Eur EE%sT Link Europe/Istanbul Asia/Istanbul # Istanbul is in both continents. # Ukraine # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Ukraine 1917 only - Jul 1 23:00 1:00 UST # Ukrainian Summer Time ! Rule Ukraine 1917 only - Dec 28 0:00 0 KMT # Kiev Mean TIme ! Rule Ukraine 1918 only - May 31 22:00 2:00 UDST # Ukrainian Double Summer Time ! Rule Ukraine 1918 only - Sep 17 0:00 1:00 UST ! Rule Ukraine 1919 only - May 31 23:00 2:00 UDST ! Rule Ukraine 1919 only - Jul 1 2:00 1:00 UST ! Rule Ukraine 1919 only - Aug 16 0:00 0 KMT ! Rule Ukraine 1921 only - Feb 14 23:00 1:00 UST ! Rule Ukraine 1921 only - Mar 21 23:00 2:00 UDST ! Rule Ukraine 1921 only - Sep 1 0:00 1:00 UST ! Rule Ukraine 1921 only - Oct 1 0:00 0 KMT ! Rule Crimea 1917 only - Jul 1 23:00 1:00 CST # Crimean Summer Time ! Rule Crimea 1917 only - Dec 28 0:00 0 NMT # Nikolayev Mean Time ! Rule Crimea 1918 only - May 31 22:00 2:00 CDST # Crimean Double Summer Time ! Rule Crimea 1918 only - Sep 17 0:00 1:00 CST ! Rule Crimea 1919 only - May 31 23:00 2:00 CDST ! Rule Crimea 1919 only - Jul 1 2:00 1:00 CST ! Rule Crimea 1919 only - Aug 16 0:00 0 NMT ! Rule Crimea 1921 only - Feb 14 23:00 1:00 CST ! Rule Crimea 1921 only - Mar 21 23:00 2:00 CDST ! Rule Crimea 1921 only - Sep 1 0:00 1:00 CST ! Rule Crimea 1921 only - Oct 1 0:00 0 NMT # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Kiev 2:02:04 - LMT 1880 ! 2:02:04 Ukraine %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1990 Jul 17 # Moscow Time ! 2:00 C-Eur EE%sT Zone Europe/Simferopol 2:16:24 - LMT 1880 ! 2:08:00 Crimea %s 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 Russia MOS%sT 1991 Mar 31 2:00s ! 2:00 1:00 EEST 1991 Sep 29 2:00s # From Paul Eggert <eggert(a)twinsun.com> (May 28, 1994): # Today's _Economist_ (p 45) reports that Crimea switched # from Kiev to Moscow time sometime after the January elections. # For now, we'll guess that there was a 2-hour leap forward on March 27. ! 2:00 C-Eur EE%sT 1994 Mar 27 2:00s ! 3:00 Russia MOS%sT # Yugoslavia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Belgrade 1:22:00 - LMT 1884 ! 1:00 - CET 1941 Apr 18 23:00 ! 1:00 C-Eur CE%sT 1945 May 8 2:00s ! 1:00 1:00 CEST 1945 Sep 16 2:00s ! 1:00 - CET 1983 ! 1:00 EU CE%sT ############################################################################### =================================================================== RCS file: RCS/northamerica,v retrieving revision 1996.9 retrieving revision 1996.9.1.1 diff -c -r1996.9 -r1996.9.1.1 *** northamerica 1996/07/01 22:13:01 1996.9 --- northamerica 1996/09/03 23:48:46 1996.9.1.1 *************** *** 202,210 **** # # From Paul Eggert (1995-12-19): # Howse writes that Alaska switched from the Julian to the Gregorian calendar, ! # and from east-of-GMT to west-of-GMT days, in 1867 when the US purchased it ! # from Russia. We omit this transition, since we can't represent changes ! # from Julian to Gregorian. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Juneau -8:57:41 - LMT 1900 Aug 20 12:00 --- 202,210 ---- # # From Paul Eggert (1995-12-19): # Howse writes that Alaska switched from the Julian to the Gregorian calendar, ! # and from east-of-GMT to west-of-GMT days, when the US bought it from Russia. ! # This was on 1867-10-18. We omit this transition, since we can't represent ! # changes from Julian to Gregorian. # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Juneau -8:57:41 - LMT 1900 Aug 20 12:00 *************** *** 472,483 **** # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which # I found in the UCLA library. # - # I invented the abbreviation SPST for St Pierre Standard Time; SPDT likewise. - # Corrections are welcome! - # # See the `europe' file for Greenland. # ! # See the `africa' file for Zone naming conventions. # Canada --- 472,480 ---- # Whitman Publishing Co, 2 Niagara Av, Ealing, London (undated), which # I found in the UCLA library. # # See the `europe' file for Greenland. # ! # See the `africa' file for time zone naming and abbreviation conventions. # Canada *************** *** 839,845 **** Rule NT_YK 1919 only - Nov 1 0:00 0 S Rule NT_YK 1942 only - Feb 9 2:00 1:00 D Rule NT_YK 1945 only - Sep 30 2:00 0 S - # 0:00 ?? Rule NT_YK 1965 only - Apr lastSun 0:00 2:00 DD Rule NT_YK 1965 only - Oct lastSun 2:00 0 S Rule NT_YK 1980 1986 - Apr lastSun 2:00 1:00 D --- 836,841 ---- *************** *** 1158,1164 **** # Grenada # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone America/Grenada -4:07:00 - LMT 1911 Jul -4:00 - AST # Guadeloupe --- 1154,1160 ---- # Grenada # Zone NAME GMTOFF RULES FORMAT [UNTIL] ! Zone America/Grenada -4:07:00 - LMT 1911 Jul # St George's -4:00 - AST # Guadeloupe *************** *** 1263,1269 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre -4:00 - AST 1980 May ! -3:00 Mont SP%sT # St Vincent and the Grenadines # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1259,1265 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Miquelon -3:44:40 - LMT 1911 May 15 # St Pierre -4:00 - AST 1980 May ! -3:00 Mont PM%sT # Pierre & Miquelon Time # St Vincent and the Grenadines # Zone NAME GMTOFF RULES FORMAT [UNTIL] =================================================================== RCS file: RCS/southamerica,v retrieving revision 1996.7 retrieving revision 1996.7.1.1 diff -c -r1996.7 -r1996.7.1.1 *** southamerica 1996/05/03 02:49:59 1996.7 --- southamerica 1996/09/03 23:48:46 1996.7.1.1 *************** *** 4,33 **** # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). # Except where otherwise noted, it is the source for the data below. # ! # I invented the abbreviations marked `*' in the following table; ! # the rest are from earlier versions of this file, or from other sources. ! # Some of these are just plausible excuses for common English abbreviations. # Corrections are welcome! # std dst # LMT Local Mean Time # -2:00 FST FDT Fernando de Noronha ! # -3:00 EST EDT Eastern South America (conflicts with -5:00) ! # -3:00 ARST ARDT Argentina ! # -4:00 AST ADT Andes*, Antilles*, Asuncion*, Atlantic ! # -4:00 CST CDT Chile (conflicts with -6:00) # -4:00 WST WDT Western Brazil ! # -5:00 AST ADT Acre (conflicts with -4:00) ! # -5:00 EST EDT Eastern, Ecuador* ! # -6:00 CST CDT Archipelago of Columbus*, Central ! # -7:00 MST MDT Mataveri*, Mountain # ! # See the `africa' file for Zone naming conventions. # From Guy Harris: # From Official Airline Guide - Worldwide Edition (1987). Countries not --- 4,35 ---- # go ahead and edit the file (and please send any changes to # tz(a)elsie.nci.nih.gov for general use in the future). ! # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): # A good source for time zone historical data outside the U.S. is # Thomas G. Shanks, The International Atlas (3rd edition), # San Diego: ACS Publications, Inc. (1991). # Except where otherwise noted, it is the source for the data below. # ! # The following abbreviations are used in this file. # Corrections are welcome! # std dst # LMT Local Mean Time # -2:00 FST FDT Fernando de Noronha ! # -3:00 EST EDT Eastern Brazil # -4:00 WST WDT Western Brazil ! # -4:00 AST ADT Atlantic ! # -5:00 AST ADT Acre # ! # See the `africa' file for time zone naming and abbreviation conventions. ! # Earlier editions of these tables used the North American style (e.g. ARST and ! # ARDT for Argentine Standard and Daylight Time), but the following quote ! # suggests that it's better to use European style (e.g. ART and ARST). ! # 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 ! # H L Mencken, _The American Language: Supplement I_ (1960), p 466 ! # From Guy Harris: # From Official Airline Guide - Worldwide Edition (1987). Countries not *************** *** 55,89 **** # AR was chosen because they are the ISO letters that represent Argentina. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Arg 1930 only - Dec 1 0:00 1:00 D ! Rule Arg 1931 only - Apr 1 0:00 0 S ! Rule Arg 1931 only - Oct 15 0:00 1:00 D ! Rule Arg 1932 1940 - Mar 1 0:00 0 S ! Rule Arg 1932 1939 - Nov 1 0:00 1:00 D ! Rule Arg 1940 only - Jul 1 0:00 1:00 D ! Rule Arg 1941 only - Jun 15 0:00 0 S ! Rule Arg 1941 only - Oct 15 0:00 1:00 D ! Rule Arg 1943 only - Aug 1 0:00 0 S ! Rule Arg 1943 only - Oct 15 0:00 1:00 D ! Rule Arg 1946 only - Mar 1 0:00 0 S ! Rule Arg 1946 only - Oct 1 0:00 1:00 D ! Rule Arg 1963 only - Oct 1 0:00 0 S ! Rule Arg 1963 only - Dec 15 0:00 1:00 D ! Rule Arg 1964 1966 - Mar 1 0:00 0 S ! Rule Arg 1964 1966 - Oct 15 0:00 1:00 D ! Rule Arg 1967 only - Apr 1 0:00 0 S ! Rule Arg 1967 1968 - Oct Sun<=7 0:00 1:00 D ! Rule Arg 1968 1969 - Apr Sun<=7 0:00 0 S ! Rule Arg 1974 only - Jan 23 0:00 1:00 D ! Rule Arg 1974 only - May 1 0:00 0 S ! Rule Arg 1974 1976 - Oct Sun<=7 0:00 1:00 D ! Rule Arg 1975 1977 - Apr Sun<=7 0:00 0 S ! Rule Arg 1985 only - Nov 2 0:00 1:00 D ! Rule Arg 1986 only - Mar 14 0:00 0 S ! Rule Arg 1986 1987 - Oct 25 0:00 1:00 D ! Rule Arg 1987 only - Feb 13 0:00 0 S ! Rule Arg 1988 only - Feb 7 0:00 0 S ! Rule Arg 1988 only - Dec 1 0:00 1:00 D # # From Hernan G. Otero <hernan(a)isoft.com.ar> (June 26, 1995): # These corrections were contributed by InterSoft Argentina S.A., --- 57,91 ---- # AR was chosen because they are the ISO letters that represent Argentina. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Arg 1930 only - Dec 1 0:00 1:00 S ! Rule Arg 1931 only - Apr 1 0:00 0 - ! Rule Arg 1931 only - Oct 15 0:00 1:00 S ! Rule Arg 1932 1940 - Mar 1 0:00 0 - ! Rule Arg 1932 1939 - Nov 1 0:00 1:00 S ! Rule Arg 1940 only - Jul 1 0:00 1:00 S ! Rule Arg 1941 only - Jun 15 0:00 0 - ! Rule Arg 1941 only - Oct 15 0:00 1:00 S ! Rule Arg 1943 only - Aug 1 0:00 0 - ! Rule Arg 1943 only - Oct 15 0:00 1:00 S ! Rule Arg 1946 only - Mar 1 0:00 0 - ! Rule Arg 1946 only - Oct 1 0:00 1:00 S ! Rule Arg 1963 only - Oct 1 0:00 0 - ! Rule Arg 1963 only - Dec 15 0:00 1:00 S ! Rule Arg 1964 1966 - Mar 1 0:00 0 - ! Rule Arg 1964 1966 - Oct 15 0:00 1:00 S ! Rule Arg 1967 only - Apr 1 0:00 0 - ! Rule Arg 1967 1968 - Oct Sun<=7 0:00 1:00 S ! Rule Arg 1968 1969 - Apr Sun<=7 0:00 0 - ! Rule Arg 1974 only - Jan 23 0:00 1:00 S ! Rule Arg 1974 only - May 1 0:00 0 - ! Rule Arg 1974 1976 - Oct Sun<=7 0:00 1:00 S ! Rule Arg 1975 1977 - Apr Sun<=7 0:00 0 - ! Rule Arg 1985 only - Nov 2 0:00 1:00 S ! Rule Arg 1986 only - Mar 14 0:00 0 - ! Rule Arg 1986 1987 - Oct 25 0:00 1:00 S ! Rule Arg 1987 only - Feb 13 0:00 0 - ! Rule Arg 1988 only - Feb 7 0:00 0 - ! Rule Arg 1988 only - Dec 1 0:00 1:00 S # # From Hernan G. Otero <hernan(a)isoft.com.ar> (June 26, 1995): # These corrections were contributed by InterSoft Argentina S.A., *************** *** 92,99 **** # (Argentinian Naval Hydrography Institute) # # Shanks gives 1989 Mar 16 and stops after 1990 Mar 4; go with Otero. ! Rule Arg 1989 1993 - Mar Sun>=1 0:00 0 S ! Rule Arg 1989 1992 - Oct Sun>=15 0:00 1:00 D # # From Hernan G. Otero <hernan(a)isoft.com.ar> (June 26, 1995): # From this moment on, the law that mandated the daylight saving --- 94,101 ---- # (Argentinian Naval Hydrography Institute) # # Shanks gives 1989 Mar 16 and stops after 1990 Mar 4; go with Otero. ! Rule Arg 1989 1993 - Mar Sun>=1 0:00 0 - ! Rule Arg 1989 1992 - Oct Sun>=15 0:00 1:00 S # # From Hernan G. Otero <hernan(a)isoft.com.ar> (June 26, 1995): # From this moment on, the law that mandated the daylight saving *************** *** 102,124 **** # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Buenos_Aires -3:53:48 - LMT 1894 Nov ! -4:17 - CMT 1920 May # Cordoba Mean Time ! -4:00 - AST 1930 Dec ! -4:00 Arg A%sT 1969 Oct 5 -3:00 Arg AR%sT # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Aruba -4:40:24 - LMT 1912 Feb 12 # Oranjestad ! -4:30 - NAST 1965 # Netherlands Antilles -4:00 - AST # Bolivia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/La_Paz -4:32:36 - LMT 1890 ! -4:33 - LPMT 1931 Oct 15 # La Paz Mean Time ! -4:33 1:00 LPDT 1932 Mar 21 ! -4:00 - AST # Brazil --- 104,126 ---- # # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Buenos_Aires -3:53:48 - LMT 1894 Nov ! -4:16:44 - CMT 1920 May # Cordoba Mean Time ! -4:00 - ART 1930 Dec ! -4:00 Arg AR%sT 1969 Oct 5 -3:00 Arg AR%sT # Aruba # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Aruba -4:40:24 - LMT 1912 Feb 12 # Oranjestad ! -4:30 - ANT 1965 # Netherlands Antilles Time -4:00 - AST # Bolivia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/La_Paz -4:32:36 - LMT 1890 ! -4:32:36 - LPMT 1931 Oct 15 # La Paz Mean Time ! -4:32:36 1:00 BOST 1932 Mar 21 # Bolivia ST ! -4:00 - BOT # Bolivia Time # Brazil *************** *** 164,189 **** # about time zone changes after 1990 Feb 11. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Brazil 1931 only - Oct 3 11:00 1 D Rule Brazil 1932 1933 - Apr 1 0:00 0 S ! Rule Brazil 1932 only - Oct 3 0:00 1 D ! Rule Brazil 1949 1952 - Dec 1 0:00 1 D Rule Brazil 1950 only - Apr 16 0:00 0 S Rule Brazil 1951 1953 - Apr 1 0:00 0 S ! Rule Brazil 1963 only - Dec 9 0:00 1 D Rule Brazil 1964 only - Mar 1 0:00 0 S ! Rule Brazil 1965 only - Jan 31 0:00 1 D Rule Brazil 1965 only - Apr 1 0:00 0 S ! Rule Brazil 1965 only - Dec 1 0:00 1 D Rule Brazil 1966 1968 - Mar 1 0:00 0 S ! Rule Brazil 1966 1967 - Nov 1 0:00 1 D ! Rule Brazil 1985 only - Nov 2 0:00 1 D Rule Brazil 1986 only - Mar 15 0:00 0 S ! Rule Brazil 1986 1987 - Oct Sat<=28 0:00 1 D Rule Brazil 1987 only - Feb 14 0:00 0 S Rule Brazil 1988 only - Feb 7 0:00 0 S Rule Brazil 1989 only - Jan 22 0:00 0 S ! Rule Brazil 1988 max - Oct Sun>=15 0:00 1 D Rule Brazil 1990 max - Feb Sun>=8 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Noronha -2:09:40 - LMT 1914 --- 166,191 ---- # about time zone changes after 1990 Feb 11. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Brazil 1931 only - Oct 3 11:00 1:00 D Rule Brazil 1932 1933 - Apr 1 0:00 0 S ! Rule Brazil 1932 only - Oct 3 0:00 1:00 D ! Rule Brazil 1949 1952 - Dec 1 0:00 1:00 D Rule Brazil 1950 only - Apr 16 0:00 0 S Rule Brazil 1951 1953 - Apr 1 0:00 0 S ! Rule Brazil 1963 only - Dec 9 0:00 1:00 D Rule Brazil 1964 only - Mar 1 0:00 0 S ! Rule Brazil 1965 only - Jan 31 0:00 1:00 D Rule Brazil 1965 only - Apr 1 0:00 0 S ! Rule Brazil 1965 only - Dec 1 0:00 1:00 D Rule Brazil 1966 1968 - Mar 1 0:00 0 S ! Rule Brazil 1966 1967 - Nov 1 0:00 1:00 D ! Rule Brazil 1985 only - Nov 2 0:00 1:00 D Rule Brazil 1986 only - Mar 15 0:00 0 S ! Rule Brazil 1986 1987 - Oct Sat<=28 0:00 1:00 D Rule Brazil 1987 only - Feb 14 0:00 0 S Rule Brazil 1988 only - Feb 7 0:00 0 S Rule Brazil 1989 only - Jan 22 0:00 0 S ! Rule Brazil 1988 max - Oct Sun>=15 0:00 1:00 D Rule Brazil 1990 max - Feb Sun>=8 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Noronha -2:09:40 - LMT 1914 *************** *** 209,229 **** # of October.... The law is the same for March and October. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Chile 1918 only - Sep 1 0:00 1:00 D ! Rule Chile 1919 only - Jul 2 0:00 0 S ! Rule Chile 1927 1931 - Sep 1 0:00 1:00 D ! Rule Chile 1928 1932 - Apr 1 0:00 0 S ! Rule Chile 1969 max - Oct Sun>=9 0:00 1:00 D ! Rule Chile 1970 max - Mar Sun>=9 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santiago -4:42:40 - LMT 1890 ! -4:43 - SMT 1910 # Santiago Mean Time ! -5:00 Chile C%sT 1932 Sep ! -4:00 Chile C%sT Zone Pacific/Easter -7:17:28 - LMT 1890 # Mataveri ! -7:17 - MMT 1932 Sep # Mataveri Mean Time ! -7:00 Chile M%sT 1982 Mar 14 ! -6:00 Chile C%sT # # Whitman says Juan Fernandez Is are like America/Santiago. # San Ambrosio, San Felix --- 211,231 ---- # of October.... The law is the same for March and October. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Chile 1918 only - Sep 1 0:00 1:00 S ! Rule Chile 1919 only - Jul 2 0:00 0 - ! Rule Chile 1927 1931 - Sep 1 0:00 1:00 S ! Rule Chile 1928 1932 - Apr 1 0:00 0 - ! Rule Chile 1969 max - Oct Sun>=9 0:00 1:00 S ! Rule Chile 1970 max - Mar Sun>=9 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Santiago -4:42:40 - LMT 1890 ! -4:42:40 - SMT 1910 # Santiago Mean Time ! -5:00 Chile CL%sT 1932 Sep # Chile Time ! -4:00 Chile CL%sT Zone Pacific/Easter -7:17:28 - LMT 1890 # Mataveri ! -7:17:28 - MMT 1932 Sep # Mataveri Mean Time ! -7:00 Chile EAS%sT 1982 Mar 14 # Easter I Time ! -6:00 Chile EAS%sT # # Whitman says Juan Fernandez Is are like America/Santiago. # San Ambrosio, San Felix *************** *** 233,288 **** # Colombia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:20 - LMT 1884 Mar 13 ! -4:56 - BMT 1914 Nov 23 # Bogota Mean Time ! -5:00 - EST # Malpelo, Providencia, San Andres # no information; probably like America/Bogota # Curacao # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Curacao -4:35:44 - LMT 1912 Feb 12 # Willemstad ! -4:30 - NAST 1965 # Netherlands Antilles -4:00 - AST # Ecuador # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guayaquil -5:19:20 - LMT 1890 ! -5:14 - QMT 1931 # Quito Mean Time ! -5:00 - EST Zone Pacific/Galapagos -5:58:24 - LMT 1931 # Puerto Baquerizo Moreno ! -5:00 - EST 1986 ! -6:00 - CST # Falklands # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Falk 1937 1938 - Sep lastSun 0:00 1:00 D ! Rule Falk 1938 1942 - Mar Sun>=19 0:00 0 S ! Rule Falk 1939 only - Oct 1 0:00 1:00 D ! Rule Falk 1940 1942 - Sep lastSun 0:00 1:00 D ! Rule Falk 1943 only - Jan 1 0:00 0 S ! Rule Falk 1983 only - Sep lastSun 0:00 1:00 D ! Rule Falk 1984 1985 - Apr lastSun 0:00 0 S ! Rule Falk 1984 only - Sep 16 0:00 1:00 D ! Rule Falk 1985 max - Sep Sun>=9 0:00 1:00 D ! Rule Falk 1986 max - Apr Sun>=16 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 ! -3:51 - SMT 1912 Mar 12 # Stanley Mean Time ! -4:00 Falk A%sT 1983 May ! -3:00 Falk E%sT 1985 Sep 15 ! -4:00 Falk A%sT # French Guiana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Cayenne -3:29:20 - LMT 1911 Jul ! -4:00 - AST 1967 Oct ! -3:00 - EST # Guyana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown ! -3:45 - BGST 1975 Jul 31 # British Guiana ST ! -3:00 - EST # Paraguay --- 235,291 ---- # Colombia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Bogota -4:56:20 - LMT 1884 Mar 13 ! -4:56:20 - BMT 1914 Nov 23 # Bogota Mean Time ! -5:00 - COT # Colombia Time # Malpelo, Providencia, San Andres # no information; probably like America/Bogota # Curacao # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Curacao -4:35:44 - LMT 1912 Feb 12 # Willemstad ! -4:30 - ANT 1965 # Netherlands Antilles Time -4:00 - AST # Ecuador # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guayaquil -5:19:20 - LMT 1890 ! -5:14:00 - QMT 1931 # Quito Mean Time ! -5:00 - ECT # Ecuador Time Zone Pacific/Galapagos -5:58:24 - LMT 1931 # Puerto Baquerizo Moreno ! -5:00 - ECT 1986 ! -6:00 - GALT # Galapagos Time # Falklands # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Falk 1937 1938 - Sep lastSun 0:00 1:00 S ! Rule Falk 1938 1942 - Mar Sun>=19 0:00 0 - ! Rule Falk 1939 only - Oct 1 0:00 1:00 S ! Rule Falk 1940 1942 - Sep lastSun 0:00 1:00 S ! Rule Falk 1943 only - Jan 1 0:00 0 - ! Rule Falk 1983 only - Sep lastSun 0:00 1:00 S ! Rule Falk 1984 1985 - Apr lastSun 0:00 0 - ! Rule Falk 1984 only - Sep 16 0:00 1:00 S ! Rule Falk 1985 max - Sep Sun>=9 0:00 1:00 S ! Rule Falk 1986 max - Apr Sun>=16 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/Stanley -3:51:24 - LMT 1890 ! -3:51:24 - SMT 1912 Mar 12 # Stanley Mean Time ! -4:00 Falk FK%sT 1983 May # Falkland Is Time ! -3:00 Falk FK%sT 1985 Sep 15 ! -4:00 Falk FK%sT # French Guiana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Cayenne -3:29:20 - LMT 1911 Jul ! -4:00 - GFT 1967 Oct # French Guiana Time ! -3:00 - GFT # Guyana # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Guyana -3:52:40 - LMT 1915 Mar # Georgetown ! -3:45 - GBGT 1966 May 26 # Br Guiana Time ! -3:45 - GYT 1975 Jul 31 # Guyana Time ! -3:00 - GYT # Paraguay *************** *** 297,335 **** # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Para 1975 1978 - Oct 1 0:00 1:00 D ! Rule Para 1975 1978 - Mar 1 0:00 0 S # Shanks says 1979 was all DST. ! Rule Para 1980 max - Apr 1 0:00 0 S ! Rule Para 1980 1988 - Oct 1 0:00 1:00 D ! Rule Para 1989 only - Oct 22 0:00 1:00 D ! Rule Para 1990 max - Oct 1 0:00 1:00 D # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 ! -3:51 - AMT 1931 Oct 10 # Asuncion Mean Time ! -4:00 - AST 1972 Oct ! -3:00 - EST 1974 Apr ! -4:00 Para A%sT # Peru # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Peru 1938 only - Jan 1 0:00 1:00 D ! Rule Peru 1938 only - Apr 1 0:00 0 S ! Rule Peru 1938 1939 - Sep lastSun 0:00 1:00 D ! Rule Peru 1939 1940 - Mar Sun>=24 0:00 0 S ! Rule Peru 1987 only - Jan 1 0:00 1:00 D ! Rule Peru 1987 only - Apr 1 0:00 0 S ! Rule Peru 1990 only - Jan 1 0:00 1:00 D ! Rule Peru 1990 only - Apr 1 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Lima -5:08:12 - LMT 1890 ! -5:09 - LMT 1908 Jul 28 ! -5:00 Peru E%sT # South Georgia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/South_Georgia -2:26:08 - LMT 1890 # Grytviken ! -2:00 - FST # South Sandwich Is # uninhabited --- 300,338 ---- # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Para 1975 1978 - Oct 1 0:00 1:00 S ! Rule Para 1975 1978 - Mar 1 0:00 0 - # Shanks says 1979 was all DST. ! Rule Para 1980 max - Apr 1 0:00 0 - ! Rule Para 1980 1988 - Oct 1 0:00 1:00 S ! Rule Para 1989 only - Oct 22 0:00 1:00 S ! Rule Para 1990 max - Oct 1 0:00 1:00 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Asuncion -3:50:40 - LMT 1890 ! -3:50:40 - AMT 1931 Oct 10 # Asuncion Mean Time ! -4:00 - PYT 1972 Oct # Paraguay Time ! -3:00 - PYT 1974 Apr ! -4:00 Para PY%sT # Peru # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Peru 1938 only - Jan 1 0:00 1:00 S ! Rule Peru 1938 only - Apr 1 0:00 0 - ! Rule Peru 1938 1939 - Sep lastSun 0:00 1:00 S ! Rule Peru 1939 1940 - Mar Sun>=24 0:00 0 - ! Rule Peru 1987 only - Jan 1 0:00 1:00 S ! Rule Peru 1987 only - Apr 1 0:00 0 - ! Rule Peru 1990 only - Jan 1 0:00 1:00 S ! Rule Peru 1990 only - Apr 1 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Lima -5:08:12 - LMT 1890 ! -5:09 - LMT 1908 Jul 28 # Lima Mean Time ! -5:00 Peru PE%sT # Peru Time # South Georgia # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Atlantic/South_Georgia -2:26:08 - LMT 1890 # Grytviken ! -2:00 - GST # South Georgia Time # South Sandwich Is # uninhabited *************** *** 339,346 **** Zone America/Paramaribo -3:40:40 - LMT 1911 -3:40:52 - PMT 1935 # Paramaribo Mean Time -3:40:36 - PMT 1945 Oct # The capital moved? ! -3:30 - DGST 1984 Oct # Dutch Guiana Std Time ! -3:00 - EST # Trinidad and Tobago # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 342,350 ---- Zone America/Paramaribo -3:40:40 - LMT 1911 -3:40:52 - PMT 1935 # Paramaribo Mean Time -3:40:36 - PMT 1945 Oct # The capital moved? ! -3:30 - NEGT 1975 Nov 20 # Dutch Guiana Time ! -3:30 - SRT 1984 Oct # Suriname Time ! -3:00 - SRT # Trinidad and Tobago # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 353,407 **** # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1923 Oct 1; go with Shanks. ! Rule Uruguay 1923 only - Oct 2 0:00 0:30 HD ! Rule Uruguay 1924 1926 - Apr 1 0:00 0 S ! Rule Uruguay 1924 1925 - Oct 1 0:00 0:30 HD ! Rule Uruguay 1933 1935 - Oct lastSun 0:00 0:30 HD # Shanks gives 1935 Apr 1 0:00 and 1936 Mar 30 0:00; go with Whitman. ! Rule Uruguay 1934 1936 - Mar Sat>=25 23:30s 0 S ! Rule Uruguay 1936 only - Nov 1 0:00 0:30 HD ! Rule Uruguay 1937 1941 - Mar lastSun 0:00 0 S # Whitman gives 1937 Oct 3; go with Shanks. ! Rule Uruguay 1937 1940 - Oct lastSun 0:00 0:30 HD # Whitman gives 1941 Oct 24 - 1942 Mar 27, 1942 Dec 14 - 1943 Apr 13, # and 1943 Apr 13 ``to present time''; go with Shanks. ! Rule Uruguay 1941 only - Aug 1 0:00 0 S ! Rule Uruguay 1942 only - Jan 1 0:00 0:30 HD ! Rule Uruguay 1942 only - Dec 14 0:00 1:00 D ! Rule Uruguay 1943 only - Mar 14 0:00 0 S ! Rule Uruguay 1959 only - May 24 0:00 1:00 D ! Rule Uruguay 1959 only - Nov 15 0:00 0 S ! Rule Uruguay 1960 only - Jan 17 0:00 1:00 D ! Rule Uruguay 1960 only - Mar 6 0:00 0 S ! Rule Uruguay 1965 1967 - Apr Sun>=1 0:00 1:00 D ! Rule Uruguay 1965 only - Sep 26 0:00 0 S ! Rule Uruguay 1966 1967 - Oct 31 0:00 0 S ! Rule Uruguay 1968 1970 - May 27 0:00 0:30 HD ! Rule Uruguay 1968 1970 - Dec 2 0:00 0 S ! Rule Uruguay 1972 only - Apr 24 0:00 1:00 D ! Rule Uruguay 1972 only - Aug 15 0:00 0 S ! Rule Uruguay 1974 only - Mar 10 0:00 0:30 HD ! Rule Uruguay 1974 only - Dec 22 0:00 1:00 D ! Rule Uruguay 1976 only - Oct 1 0:00 0 S ! Rule Uruguay 1977 only - Dec 4 0:00 1:00 D ! Rule Uruguay 1978 only - Apr 1 0:00 0 S ! Rule Uruguay 1979 only - Oct 1 0:00 1:00 D ! Rule Uruguay 1980 only - May 1 0:00 0 S ! Rule Uruguay 1987 only - Dec 14 0:00 1:00 D ! Rule Uruguay 1988 only - Mar 14 0:00 0 S ! Rule Uruguay 1988 only - Dec 11 0:00 1:00 D ! Rule Uruguay 1989 only - Mar 12 0:00 0 S ! Rule Uruguay 1989 only - Oct 29 0:00 1:00 D ! Rule Uruguay 1990 only - Mar 4 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 ! -3:45 - MMT 1920 May 1 # Montevideo MT ! -3:30 Uruguay U%sT 1942 Dec 14 # Uruguay ST ! -3:00 Uruguay E%sT # Venezuela # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Caracas -4:27:44 - LMT 1890 ! -4:28 - CMT 1912 Feb 12 # Caracas Mean Time ! -4:30 - VZT 1965 # Venezuela Time ! -4:00 - AST --- 357,411 ---- # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S # Whitman gives 1923 Oct 1; go with Shanks. ! Rule Uruguay 1923 only - Oct 2 0:00 0:30 HS ! Rule Uruguay 1924 1926 - Apr 1 0:00 0 - ! Rule Uruguay 1924 1925 - Oct 1 0:00 0:30 HS ! Rule Uruguay 1933 1935 - Oct lastSun 0:00 0:30 HS # Shanks gives 1935 Apr 1 0:00 and 1936 Mar 30 0:00; go with Whitman. ! Rule Uruguay 1934 1936 - Mar Sat>=25 23:30s 0 - ! Rule Uruguay 1936 only - Nov 1 0:00 0:30 HS ! Rule Uruguay 1937 1941 - Mar lastSun 0:00 0 - # Whitman gives 1937 Oct 3; go with Shanks. ! Rule Uruguay 1937 1940 - Oct lastSun 0:00 0:30 HS # Whitman gives 1941 Oct 24 - 1942 Mar 27, 1942 Dec 14 - 1943 Apr 13, # and 1943 Apr 13 ``to present time''; go with Shanks. ! Rule Uruguay 1941 only - Aug 1 0:00 0 - ! Rule Uruguay 1942 only - Jan 1 0:00 0:30 HS ! Rule Uruguay 1942 only - Dec 14 0:00 1:00 S ! Rule Uruguay 1943 only - Mar 14 0:00 0 - ! Rule Uruguay 1959 only - May 24 0:00 1:00 S ! Rule Uruguay 1959 only - Nov 15 0:00 0 - ! Rule Uruguay 1960 only - Jan 17 0:00 1:00 S ! Rule Uruguay 1960 only - Mar 6 0:00 0 - ! Rule Uruguay 1965 1967 - Apr Sun>=1 0:00 1:00 S ! Rule Uruguay 1965 only - Sep 26 0:00 0 - ! Rule Uruguay 1966 1967 - Oct 31 0:00 0 - ! Rule Uruguay 1968 1970 - May 27 0:00 0:30 HS ! Rule Uruguay 1968 1970 - Dec 2 0:00 0 - ! Rule Uruguay 1972 only - Apr 24 0:00 1:00 S ! Rule Uruguay 1972 only - Aug 15 0:00 0 - ! Rule Uruguay 1974 only - Mar 10 0:00 0:30 HS ! Rule Uruguay 1974 only - Dec 22 0:00 1:00 S ! Rule Uruguay 1976 only - Oct 1 0:00 0 - ! Rule Uruguay 1977 only - Dec 4 0:00 1:00 S ! Rule Uruguay 1978 only - Apr 1 0:00 0 - ! Rule Uruguay 1979 only - Oct 1 0:00 1:00 S ! Rule Uruguay 1980 only - May 1 0:00 0 - ! Rule Uruguay 1987 only - Dec 14 0:00 1:00 S ! Rule Uruguay 1988 only - Mar 14 0:00 0 - ! Rule Uruguay 1988 only - Dec 11 0:00 1:00 S ! Rule Uruguay 1989 only - Mar 12 0:00 0 - ! Rule Uruguay 1989 only - Oct 29 0:00 1:00 S ! Rule Uruguay 1990 only - Mar 4 0:00 0 - # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Montevideo -3:44:44 - LMT 1898 Jun 28 ! -3:44:44 - MMT 1920 May 1 # Montevideo MT ! -3:30 Uruguay UY%sT 1942 Dec 14 # Uruguay Time ! -3:00 Uruguay UY%sT # Venezuela # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone America/Caracas -4:27:44 - LMT 1890 ! -4:27:44 - CMT 1912 Feb 12 # Caracas Mean Time ! -4:30 - VET 1965 # Venezuela Time ! -4:00 - VET *** /dev/null Tue Sep 3 16:57:02 1996 --- checktab.awk Tue Sep 3 16:48:46 1996 *************** *** 0 **** --- 1,152 ---- + # Check tz tables for consistency. + + # Contributed by Paul Eggert <eggert(a)twinsun.com>. + + BEGIN { + FS = "\t" + + if (!iso_table) iso_table = "iso3166.tab" + if (!zone_table) zone_table = "zone.tab" + if (!want_warnings) want_warnings = -1 + + while (getline <iso_table) { + iso_NR++ + if ($0 ~ /^#/) continue + if (NF != 2) { + printf "%s:%d: wrong number of columns\n", + iso_table, iso_NR >>"/dev/stderr" + status = 1 + } + cc = $1 + name = $2 + if (cc !~ /^[A-Z][A-Z]$/) { + printf "%s:%d: invalid country code `%s'\n", \ + iso_table, iso_NR, cc >>"/dev/stderr" + status = 1 + } + if (cc <= cc0) { + printf "%s:%d: country code `%s' is %s\n", \ + iso_table, iso_NR, cc, \ + cc==cc0 ? "duplicate" : "out of order" \ + >>"/dev/stderr" + status = 1 + } + cc0 = cc + if (name2cc[name]) { + printf "%s:%d: `%s' and `%s' have the sname name\n", \ + iso_table, iso_NR, name2cc[name], cc \ + >>"/dev/stderr" + status = 1 + } + name2cc[name] = cc + cc2name[cc] = name + cc2NR[cc] = iso_NR + } + + zone_table = "zone.tab" + cc0 = "" + + while (getline <zone_table) { + zone_NR++ + if ($0 ~ /^#/) continue + if (NF != 3 && NF != 4) { + printf "%s:%d: wrong number of columns\n", + zone_table, zone_NR >>"/dev/stderr" + status = 1 + } + cc = $1 + coordinates = $2 + tz = $3 + comments = $4 + if (cc < cc0) { + printf "%s:%d: country code `%s' is out of order\n", \ + zone_table, zone_NR, cc >>"/dev/stderr" + status = 1 + } + cc0 = cc + if (tz2cc[tz]) { + printf "%s:%d: %s: duplicate TZ column\n", \ + zone_table, zone_NR, tz >>"/dev/stderr" + status = 1 + } + tz2cc[tz] = cc + tz2comments[tz] = comments + tz2NR[tz] = zone_NR + if (cc2name[cc]) { + cc_used[cc]++ + } else { + printf "%s:%d: %s: unknown country code\n", \ + zone_table, zone_NR, cc >>"/dev/stderr" + status = 1 + } + if (coordinates !~ /^[-+][0-9][0-9][0-5][0-9][-+][01][0-9][0-9][0-5][0-9]$/ \ + && coordinates !~ /^[-+][0-9][0-9][0-5][0-9][0-5][0-9][-+][01][0-9][0-9][0-5][0-9][0-5][0-9]$/) { + printf "%s:%d: %s: invalid coordinates\n", \ + zone_table, zone_NR, coordinates >>"/dev/stderr" + status = 1 + } + } + + for (tz in tz2cc) { + if (cc_used[tz2cc[tz]] == 1) { + if (tz2comments[tz]) { + printf "%s:%d: unnecessary comment `%s'\n", \ + zone_table, tz2NR[tz], tz2comments[tz] \ + >>"/dev/stderr" + status = 1 + } + } else { + if (!tz2comments[tz]) { + printf "%s:%d: missing comment\n", \ + zone_table, tz2NR[tz] >>"/dev/stderr" + status = 1 + } + } + } + + FS = " " + } + + { + tz = "" + if ($1 == "Zone") tz = $2 + if ($1 == "Link") { + # Ignore Link commands if source and destination basenames + # are identical, e.g. Europe/Istanbul versus Asia/Istanbul. + src = $2 + dst = $3 + while ((i = index(src, "/"))) src = substr(src, i+1) + while ((i = index(dst, "/"))) dst = substr(dst, i+1) + if (src != dst) tz = $3 + } + if (tz && tz ~ /\//) { + if (!tz2cc[tz]) { + printf "%s: no data for `%s'\n", zone_table, tz \ + >>"/dev/stderr" + status = 1 + } + zoneSeen[tz] = 1 + } + } + + END { + for (tz in tz2cc) { + if (!zoneSeen[tz]) { + printf "%s:%d: no Zone table for `%s'\n", \ + zone_table, tz2NR[tz], tz >>"/dev/stderr" + status = 1 + } + } + + if (0 < want_warnings) { + for (cc in cc2name) { + if (!cc_used[cc]) { + printf "%s:%d: warning:" \ + "no Zone entries for %s (%s)\n", + iso_table, cc2NR[cc], cc, cc2name[cc] + } + } + } + + exit status + } *** /dev/null Tue Sep 3 16:57:02 1996 --- iso3166.tab Tue Sep 3 16:48:46 1996 *************** *** 0 **** --- 1,254 ---- + # ISO 3166 2-letter country codes + # + # From Paul Eggert <eggert(a)twinsun.com> (1996-09-03): + # + # This file contains a table with the following columns: + # 1. ISO 3166 2-character country code. + # 2. The usual English name for the country, + # chosen so that alphabetic sorting of subsets produces helpful lists. + # + # Columns are separated by a single tab. + # The table is sorted by country code. + # + # Lines beginning with `#' are comments. + # + #country- + #code country name + AD Andorra + AE United Arab Emirates + AF Afghanistan + AG Antigua & Barbuda + AI Anguilla + AL Albania + AM Armenia + AN Netherlands Antilles + AO Angola + AQ Antarctica + AR Argentina + AS Samoa (American) + AT Austria + AU Australia + AW Aruba + AZ Azerbaijan + BA Bosnia & Herzegovina + BB Barbados + BD Bangladesh + BE Belgium + BF Burkina Faso + BG Bulgaria + BH Bahrain + BI Burundi + BJ Benin + BM Bermuda + BN Brunei + BO Bolivia + BR Brazil + BS Bahamas + BT Bhutan + BV Bouvet Island + BW Botswana + BY Belarus + BZ Belize + CA Canada + CC Cocos (Keeling) Islands + CF Central African Rep. + CG Congo + CH Switzerland + CI Cote d'Ivoire + CK Cook Islands + CL Chile + CM Cameroon + CN China + CO Colombia + CR Costa Rica + CU Cuba + CV Cape Verde + CX Christmas Island + CY Cyprus + CZ Czech Republic + DE Germany + DJ Djibouti + DK Denmark + DM Dominica + DO Dominican Republic + DZ Algeria + EC Ecuador + EE Estonia + EG Egypt + EH Western Sahara + ER Eritrea + ES Spain + ET Ethiopia + FI Finland + FJ Fiji + FK Falkland Islands + FM Micronesia + FO Faeroe Islands + FR France + GA Gabon + GB Britain (UK) + GD Grenada + GE Georgia + GF French Guiana + GH Ghana + GI Gibraltar + GL Greenland + GM Gambia + GN Guinea + GP Guadeloupe + GQ Equatorial Guinea + GR Greece + GS South Georgia & the South Sandwich Islands + GT Guatemala + GU Guam + GW Guinea-Bissau + GY Guyana + HK Hong Kong + HM Heard Island & McDonald Islands + HN Honduras + HR Croatia + HT Haiti + HU Hungary + ID Indonesia + IE Ireland + IL Israel + IN India + IO British Indian Ocean Territory + IQ Iraq + IR Iran + IS Iceland + IT Italy + JM Jamaica + JO Jordan + JP Japan + KE Kenya + KG Kirgizstan + KH Cambodia + KI Kiribati + KM Comoros + KN St Kitts & Nevis + KP Korea (North) + KR Korea (South) + KW Kuwait + KY Cayman Islands + KZ Kazakhstan + LA Laos + LB Lebanon + LC St Lucia + LI Liechtenstein + LK Sri Lanka + LR Liberia + LS Lesotho + LT Lithuania + LU Luxembourg + LV Latvia + LY Libya + MA Morocco + MC Monaco + MD Moldova + MG Madagascar + MH Marshall Islands + MK Macedonia + ML Mali + MM Myanmar (Burma) + MN Mongolia + MO Macao + MP Northern Mariana Islands + MQ Martinique + MR Mauritania + MS Montserrat + MT Malta + MU Mauritius + MV Maldives + MW Malawi + MX Mexico + MY Malaysia + MZ Mozambique + NA Namibia + NC New Caledonia + NE Niger + NF Norfolk Island + NG Nigeria + NI Nicaragua + NL Netherlands + NO Norway + NP Nepal + NR Nauru + NU Niue + NZ New Zealand + OM Oman + PA Panama + PE Peru + PF French Polynesia + PG Papua New Guinea + PH Philippines + PK Pakistan + PL Poland + PM St Pierre & Miquelon + PN Pitcairn + PR Puerto Rico + PT Portugal + PW Palau + PY Paraguay + QA Qatar + RE Reunion + RO Romania + RU Russia + RW Rwanda + SA Saudi Arabia + SB Solomon Islands + SC Seychelles + SD Sudan + SE Sweden + SG Singapore + SH St Helena + SI Slovenia + SJ Svalbard & Jan Mayen + SK Slovakia + SL Sierra Leone + SM San Marino + SN Senegal + SO Somalia + SR Suriname + ST Sao Tome & Principe + SV El Salvador + SY Syria + SZ Swaziland + TC Turks & Caicos Is + TD Chad + TF French Southern & Antarctic Lands + TG Togo + TH Thailand + TJ Tajikistan + TK Tokelau + TM Turkmenistan + TN Tunisia + TO Tonga + TP East Timor + TR Turkey + TT Trinidad & Tobago + TV Tuvalu + TW Taiwan + TZ Tanzania + UA Ukraine + UG Uganda + UM US minor outlying islands + US United States + UY Uruguay + UZ Uzbekistan + VA Vatican City + VC St Vincent + VE Venezuela + VG Virgin Islands (UK) + VI Virgin Islands (US) + VN Vietnam + VU Vanuatu + WF Wallis & Futuna + WS Samoa (Western) + YE Yemen + YT Mayotte + YU Yugoslavia + ZA South Africa + ZM Zambia + ZR Zaire + ZW Zimbabwe *** /dev/null Tue Sep 3 16:57:02 1996 --- tzselect.8 Tue Sep 3 17:10:03 1996 *************** *** 0 **** --- 1,40 ---- + .TH TZSELECT 8 + .SH NAME + tzselect \- select a time zone + .SH SYNOPSIS + .B tzselect + .SH DESCRIPTION + The + .B tzselect + program asks the user for information about the current location, + and outputs the resulting time zone description to standard output. + The output is suitable as a value for the TZ environment variable. + .PP + All interaction with the user is done via standard input and standard error. + .SH "ENVIRONMENT VARIABLES" + .TP + \f3AWK\fP + Name of a Posix-compliant + .I awk + program (default: + .BR awk ). + .TP + \f3TZDIR\fP + Name of the directory containing time zone data files (default: + .BR /usr/local/etc/zoneinfo ). + .SH FILES + .TP + \f2TZDIR\fP\f3/iso3166.tab\fP + Table of ISO 3166 2-letter country codes and country names. + .TP + \f2TZDIR\fP\f3/zone.tab\fP + Table of country codes, latitude and longitude, TZ values, and + descriptive comments. + .TP + \f2TZDIR\fP\f3/\fP\f2TZ\fP + Time zone data file for time zone \f2TZ\fP. + .SH "EXIT STATUS" + The exit status is zero if a time zone was successfully obtained from the user, + nonzero otherwise. + .SH "SEE ALSO" + newctime(3), tzfile(5), zdump(8), zic(8) *** /dev/null Tue Sep 3 16:57:02 1996 --- tzselect.ksh Tue Sep 3 16:48:46 1996 *************** *** 0 **** --- 1,292 ---- + #! /bin/ksh + # Ask the user about the time zone, and output the resulting TZ value to stdout. + # Interact with the user via stderr and stdin. + + # Contributed by Paul Eggert <eggert(a)twinsun.com>. + + # Porting notes: + # + # This script requires several features of the Korn shell. + # If your host lacks the Korn shell, + # you can use either of the following free programs instead: + # + # Bourne-Again shell (bash) + # <URL:ftp://prep.ai.mit.edu:/pub/gnu/bash-1.14.7.tar.gz> + # (or any later version) + # + # Public domain ksh + # <URL:ftp://ftp.cs.mun.ca:/pub/pdksh/pdksh.tar.gz> + # + # This script also uses several features of modern awk programs. + # If your host lacks awk, or has an old awk that does not conform to Posix.2, + # you can use either of the following free programs instead: + # + # GNU awk (gawk) + # <URL:ftp://prep.ai.mit.edu:/pub/gnu/gawk-3.0.0.tar.gz> + # (or any later version) + # + # mawk + # <URL:ftp://oxy.edu/public/mawk1.2.2.tar.gz> + # (or any later version) + + + # Specify default values for environment variables if they are unset. + : ${AWK=awk} + : ${TZDIR=$(pwd)} + + # Check for awk Posix compliance. + ($AWK -v x=y 'BEGIN { exit 123 }') </dev/null >/dev/null 2>&1 + [ $? = 123 ] || { + echo >&2 "$0: Sorry, your \`$AWK' program is not Posix compatible." + exit 1 + } + + # Make sure the tables are readable. + TZ_COUNTRY_TABLE=$TZDIR/iso3166.tab + TZ_ZONE_TABLE=$TZDIR/zone.tab + for f in $TZ_COUNTRY_TABLE $TZ_ZONE_TABLE + do + <$f || { + echo >&2 "$0: time zone files are not set up correctly" + exit 1 + } + done + + newline=' + ' + IFS=$newline + + + # Work around a bash bug, where $PS3 is sent to stdout. + case $(echo 1 | (select x in x; do break; done) 2>/dev/null) in + ?*) PS3= + esac + + + # Begin the main loop. We come back here if the user wants to retry. + while + + echo >&2 'Please identify a location' \ + 'so that time zone rules can be set correctly.' + + continent= + country= + region= + + + # Ask the user for continent or ocean. + + echo >&2 'Please select a continent or ocean.' + + select continent in \ + Africa \ + Americas \ + Antarctica \ + 'Arctic Ocean' \ + Asia \ + 'Atlantic Ocean' \ + Australia \ + Europe \ + 'Indian Ocean' \ + 'Pacific Ocean' \ + 'none - I want to specify the time zone using the Posix TZ format.' + do + case $continent in + '') + echo >&2 'Please enter a number in range.';; + ?*) + case $continent in + Americas) continent=America;; + *' '*) continent=$(expr "$continent" : '$[^ ]*$') + esac + break + esac + done + case $continent in + '') + exit 1;; + none) + # Ask the user for a Posix TZ string. Check that it conforms. + while + echo >&2 'Please enter the desired value' \ + 'of the TZ environment variable.' + echo >&2 'For example, GST-10 is a zone named GST' \ + 'that is 10 hours ahead (east) of UTC.' + read TZ + $AWK -v TZ="$TZ" 'BEGIN { + tzname = "[^-+,0-9][^-+,0-9][^-+,0-9]+" + time = "[0-2]?[0-9](:[0-5][0-9](:[0-5][0-9])?)?" + offset = "[-+]?" time + date = "(J?[0-9]+|M[0-9]+\.[0-9]+\.[0-9]+)" + datetime = "," date "(/" time ")?" + tzpattern = "^(:.*|" tzname offset "(" tzname \ + "(" offset ")?(" datetime datetime ")?)?)$" + if (TZ ~ tzpattern) exit 1 + exit 0 + }' + do + echo >&2 "\`$TZ' is not a conforming" \ + 'Posix time zone string.' + done + TZ_for_date=$TZ;; + *) + # Get list of names of countries in the continent or ocean. + countries=$($AWK -F'\t' \ + -v continent="$continent" \ + -v TZ_COUNTRY_TABLE="$TZ_COUNTRY_TABLE" \ + ' + /^#/ { next } + $3 ~ ("^" continent "/") { + if (!cc_seen[$1]++) cc_list[++ccs] = $1 + } + END { + while (getline <TZ_COUNTRY_TABLE) { + if ($0 !~ /^#/) cc_name[$1] = $2 + } + for (i = 1; i <= ccs; i++) { + country = cc_list[i] + if (cc_name[country]) { + country = cc_name[country] + } + print country + } + } + ' <$TZ_ZONE_TABLE | sort -f) + + + # If there's more than one country, ask the user which one. + case $countries in + *"$newline"*) + echo >&2 'Please select a country.' + select country in $countries + do + case $country in + '') echo >&2 'Please enter a number in range.';; + ?*) break + esac + done + + case $country in + '') exit 1 + esac;; + *) + country=$countries + esac + + + # Get list of names of time zone rule regions in the country. + regions=$($AWK -F'\t' \ + -v country="$country" \ + -v TZ_COUNTRY_TABLE="$TZ_COUNTRY_TABLE" \ + ' + BEGIN { + cc = country + while (getline <TZ_COUNTRY_TABLE) { + if ($0 !~ /^#/ && country == $2) { + cc = $1 + break + } + } + } + $1 == cc { print $4 } + ' <$TZ_ZONE_TABLE) + + + # If there's more than one region, ask the user which one. + case $regions in + *"$newline"*) + echo >&2 'Please select one of the following' \ + 'time zone regions.' + select region in $regions + do + case $region in + '') echo >&2 'Please enter a number in range.';; + ?*) break + esac + done + case $region in + '') exit 1 + esac;; + *) + region=$regions + esac + + # Determine TZ from country and region. + TZ=$($AWK -F'\t' \ + -v country="$country" \ + -v region="$region" \ + -v TZ_COUNTRY_TABLE="$TZ_COUNTRY_TABLE" \ + ' + BEGIN { + cc = country + while (getline <TZ_COUNTRY_TABLE) { + if ($0 !~ /^#/ && country == $2) { + cc = $1 + break + } + } + } + $1 == cc && $4 == region { print $3 } + ' <$TZ_ZONE_TABLE) + + # Make sure the corresponding zoneinfo file exists. + TZ_for_date=$TZDIR/$TZ + <$TZ_for_date || { + echo >&2 "$0: time zone files are not set up correctly" + exit 1 + } + esac + + + # Use the proposed TZ to output the current date relative to UTC. + # Loop until they agree in seconds. + # Give up after 8 unsuccessful tries. + + extra_info= + for i in 1 2 3 4 5 6 7 8 + do + TZdate=$(LANG=C TZ="$TZ_for_date" date) + UTdate=$(LANG=C TZ=UTC0 date) + TZsec=$(expr "$TZdate" : '.*:$[0-5][0-9]$') + UTsec=$(expr "$UTdate" : '.*:$[0-5][0-9]$') + case $TZsec in + $UTsec) + extra_info=" + Local time is now: $TZdate. + Universal Time is now: $UTdate." + break + esac + done + + + # Output TZ info and ask the user to confirm. + + echo >&2 "" + echo >&2 "The following information has been given:" + echo >&2 "" + case $country+$region in + ?*+?*) echo >&2 " $country$newline $region";; + ?*+) echo >&2 " $country";; + +) echo >&2 " TZ='$TZ'" + esac + echo >&2 "" + echo >&2 "Therefore TZ='$TZ' will be used.$extra_info" + echo >&2 "Is the above information OK?" + + ok= + select ok in Yes No + do + case $ok in + '') echo >&2 'Please enter 1 for Yes, or 2 for No.';; + ?*) break + esac + done + case $ok in + '') exit 1;; + Yes) break + esac + do : + done + + # Output the answer. + echo "$TZ" *** /dev/null Tue Sep 3 16:57:02 1996 --- zone.tab Tue Sep 3 16:48:46 1996 *************** *** 0 **** --- 1,356 ---- + # TZ zone descriptions + # + # From Paul Eggert <eggert(a)twinsun.com> (1996-08-05): + # + # This file contains a table with the following columns: + # 1. ISO 3166 2-character country code. See the file `iso3166.tab'. + # 2. Latitude and longitude of the zone's principal location + # in ISO 6709 sign-degrees-minutes-seconds format, + # either +-DDMM+-DDDMM or +-DDMMSS+-DDDMMSS, + # first latitude (+ is north), then longitude (+ is east). + # 3. Zone name used in value of TZ environment variable. + # 4. Comments; present if and only if the country has multiple rows. + # + # Columns are separated by a single tab. + # The table is sorted first by country, then an order within the country that + # (1) makes some geographical sense, and + # (2) puts the most populous zones first, where that does not contradict (1). + # + # Lines beginning with `#' are comments. + # + #country- + #code coordinates TZ comments + AD +4230+00131 Europe/Andorra + AE +2518+05518 Asia/Dubai + AF +3431+06912 Asia/Kabul + AG +1703-06148 America/Antigua + AI +1812-06304 America/Anguilla + AL +4120+01950 Europe/Tirane + AM +4011+04430 Asia/Yerevan + AN +1211-06900 America/Curacao + AO -0848+01314 Africa/Luanda + AQ -7750+16636 Antarctica/McMurdo McMurdo Station, Ross Island + AQ -9000+00000 Antarctica/South_Pole Amundsen-Scott Station, South Pole + AQ -6617+11031 Antarctica/Casey Casey Station, Bailey Peninsula + AQ -6736+06253 Antarctica/Mawson Mawson Station, Holme Bay + AR -3436-05827 America/Buenos_Aires + AS -1416-17042 Pacific/Pago_Pago + AT +4813+01620 Europe/Vienna + AU -3133+15905 Australia/Lord_Howe Lord Howe Island + AU -4253+14719 Australia/Hobart Tasmania + AU -3749+14458 Australia/Melbourne Victoria + AU -3352+15113 Australia/Sydney New South Wales - most locations + AU -3157+14127 Australia/Broken_Hill New South Wales - Broken Hill + AU -2728+15302 Australia/Brisbane Queensland + AU -3455+13835 Australia/Adelaide South Australia + AU -1228+13050 Australia/Darwin Northern Territory + AU -3157+11551 Australia/Perth Western Australia + AW +1230-06858 America/Aruba + AZ +4023+04951 Asia/Baku + BA +4352+01825 Europe/Sarajevo + BB +1306-05937 America/Barbados + BD +2343+09025 Asia/Dacca + BE +5050+00420 Europe/Brussels + BF +1222-00131 Africa/Ouagadougou + BG +4241+02319 Europe/Sofia + BH +2623+05035 Asia/Bahrain + BI -0323+02922 Africa/Bujumbura + BJ +0629+00237 Africa/Porto-Novo + BM +3217-06446 Atlantic/Bermuda + BN +0456+11455 Asia/Brunei + BO -1630-06809 America/La_Paz + BR -0351-03225 America/Noronha Atlantic islands + BR -2332-04637 America/Sao_Paulo east Brazil + BR -0308-06001 America/Manaus west Brazil + BR -0934-06731 America/Porto_Acre Acre + BS +2505-07721 America/Nassau + BT +2728+08939 Asia/Thimbu + BW -2545+02555 Africa/Gaborone + BY +5354+02734 Europe/Minsk + BZ +1730-08812 America/Belize + CA +4734-05243 America/St_Johns Newfoundland Island + CA +4439-06336 America/Halifax Atlantic Time - Nova Scotia (most locations), New Brunswick, Labrador & PEI + CA +4612-05957 America/Glace_Bay Atlantic Time - Nova Scotia - places that did not observe DST 1966-1971 + CA +6608-06544 America/Pangnirtung Atlantic Time - Northwest Territories + CA +4531-07334 America/Montreal Eastern Time - Ontario & Quebec - most locations + CA +4901-08816 America/Nipigon Eastern Time - Ontario & Quebec - places that did not observe DST 1967-1973 + CA +4823-08915 America/Thunder_Bay Eastern Time - Thunder Bay, Ontario + CA +6344-06828 America/Iqaluit Eastern Time - Northwest Territories + CA +4953-09709 America/Winnipeg Central Time - Manitoba & west Ontario + CA +4843-09429 America/Rainy_River Central Time - Rainy River & Fort Frances, Ontario + CA +6245-09210 America/Rankin_Inlet Central Time - Northwest Territories + CA +5024-10439 America/Regina Central Standard Time - Saskatchewan - most locations + CA +5017-10750 America/Swift_Current Central Standard Time - Saskatchewan - midwest + CA +5333-11328 America/Edmonton Mountain Time - Alberta, east British Columbia & west Saskatchewan + CA +6227-11421 America/Yellowknife Mountain Time - central Northwest Territories + CA +6825-11330 America/Inuvik Mountain Time - west Northwest Territories + CA +5946-12014 America/Dawson_Creek Mountain Standard Time - Dawson Creek & Fort Saint John, British Columbia + CA +4916-12307 America/Vancouver Pacific Time - west British Columbia + CA +6043-13503 America/Whitehorse Pacific Time - south Yukon + CA +6404-13925 America/Dawson Pacific Time - north Yukon + CC -1210+09655 Indian/Cocos + CF +0422+01835 Africa/Bangui + CG -0416+01517 Africa/Brazzaville + CH +4723+00832 Europe/Zurich + CI +0519-00402 Africa/Abidjan + CK -2114-15946 Pacific/Rarotonga + CL -3327-07040 America/Santiago mainland + CL -2710-10927 Pacific/Easter Easter Island + CM +0403+00942 Africa/Douala + CN +4545+12641 Asia/Harbin north Manchuria + CN +3114+12128 Asia/Shanghai China coast + CN +2934+10635 Asia/Chungking China mountains + CN +4348+08735 Asia/Urumqi Tibet & Xinjiang + CN +3929+07559 Asia/Kashgar Eastern Turkestan + CO +0436-07405 America/Bogota + CR +0956-08405 America/Costa_Rica + CU +2308-08222 America/Havana + CV +1455-02331 Atlantic/Cape_Verde + CX -1025+10543 Indian/Christmas + CY +3510+03322 Asia/Nicosia + CZ +5005+01426 Europe/Prague + DE +5230+01322 Europe/Berlin + DJ +1136+04309 Africa/Djibouti + DK +5540+01235 Europe/Copenhagen + DM +1518-06124 America/Dominica + DO +1828-06954 America/Santo_Domingo + DZ +3647+00303 Africa/Algiers + EC -0210-07950 America/Guayaquil mainland + EC -0054-08936 Pacific/Galapagos Galapagos Islands + EE +5925+02445 Europe/Tallinn + EG +3003+03115 Africa/Cairo + EH +2709-01312 Africa/El_Aaiun + ER +1520+03853 Africa/Asmera + ES +4024-00341 Europe/Madrid mainland + ES +3553-00519 Africa/Ceuta Ceuta & Melilla + ES +2806-01524 Atlantic/Canary Canary Islands + ET +0902+03842 Africa/Addis_Ababa + FI +6010+02458 Europe/Helsinki + FJ -1808+17825 Pacific/Fiji + FK -5142-05751 Atlantic/Stanley + FM +0931+13808 Pacific/Yap Yap + FM +0725+15147 Pacific/Truk Truk (Chuuk) + FM +0658+15813 Pacific/Ponape Ponape (Pohnpei) + FM +0519+16259 Pacific/Kosrae Kosrae + FO +6201-00646 Atlantic/Faeroe + FR +4852+00220 Europe/Paris + GA +0023+00927 Africa/Libreville + GB +512830-0001845 Europe/London Great Britain + GB +5435-00555 Europe/Belfast Northern Ireland + GD +1203-06145 America/Grenada + GE +4143+04449 Asia/Tbilisi + GF +0456-05220 America/Cayenne + GH +0533-00013 Africa/Accra + GI +3608-00521 Europe/Gibraltar + GL +7030-02215 America/Scoresbysund east Greenland + GL +6411-05144 America/Godthab southwest Greenland + GL +7634-06847 America/Thule northwest Greenland + GM +1328-01639 Africa/Banjul + GN +0931-01343 Africa/Conakry + GP +1614-06132 America/Guadeloupe + GQ +0345+00847 Africa/Malabo + GR +3758+02343 Europe/Athens + GS -5416-03632 Atlantic/South_Georgia + GT +1438-09031 America/Guatemala + GU +1328+14445 Pacific/Guam + GW +1151-01535 Africa/Bissau + GY +0648-05810 America/Guyana + HK +2217+11409 Asia/Hong_Kong + HN +1406-08713 America/Tegucigalpa + HR +4548+01558 Europe/Zagreb + HT +1832-07220 America/Port-au-Prince + HU +4730+01905 Europe/Budapest + ID -0610+10648 Asia/Jakarta Java & Sumatra + ID -0507+11924 Asia/Ujung_Pandang Borneo & Celebes + ID -0232+14042 Asia/Jayapura Irian Jaya & the Moluccas + IE +5320-00615 Europe/Dublin + IL +3146+03514 Asia/Jerusalem most locations + IL +3130+03428 Asia/Gaza Gaza Strip + IN +2232+08822 Asia/Calcutta + IO -0720+07225 Indian/Chagos + IQ +3321+04425 Asia/Baghdad + IR +3540+05126 Asia/Tehran + IS +6409-02151 Atlantic/Reykjavik + IT +4154+01229 Europe/Rome + JM +1800-07648 America/Jamaica + JO +3157+03556 Asia/Amman + JP +3542+13946 Asia/Tokyo most locations + JP +2420+12409 Asia/Ishigaki south Ryukyu Islands + KE -0117+03649 Africa/Nairobi + KG +4254+07436 Asia/Bishkek + KH +1133+10455 Asia/Phnom_Penh + KI +0125+17300 Pacific/Tarawa Gilbert Islands + KI -0308-17105 Pacific/Enderbury Phoenix Islands + KI +0152-15720 Pacific/Kiritimati Line Islands + KM -1141+04316 Indian/Comoro + KN +1718-06243 America/St_Kitts + KP +3901+12545 Asia/Pyongyang + KR +3733+12658 Asia/Seoul + KW +2920+04759 Asia/Kuwait + KY +1918-08123 America/Cayman + KZ +4315+07657 Asia/Alma-Ata east Kazakhstan + KZ +5016+07302 Asia/Aktau west Kazakhstan + LA +1758+10236 Asia/Vientiane + LB +3353+03530 Asia/Beirut + LC +1401-06100 America/St_Lucia + LI +4709+00931 Europe/Vaduz + LK +0656+07951 Asia/Colombo + LR +0618-01047 Africa/Monrovia + LS -2928+02730 Africa/Maseru + LT +5441+02519 Europe/Vilnius + LU +4936+00609 Europe/Luxembourg + LV +5657+02406 Europe/Riga + LY +3254+01311 Africa/Tripoli + MA +3339-00735 Africa/Casablanca + MC +4342+00723 Europe/Monaco + MD +4700+02850 Europe/Chisinau + MG -1855+04731 Indian/Antananarivo + MH +0709+17112 Pacific/Majuro most locations + MH +0905+16720 Pacific/Kwajalein Kwajalein + MK +4159+02126 Europe/Skopje + ML +1239-00800 Africa/Bamako southwest Mali + ML +1446-00301 Africa/Timbuktu northeast Mali + MM +1647+09610 Asia/Rangoon + MN +4755+10653 Asia/Ulan_Bator + MO +2214+11335 Asia/Macao + MP +1512+14545 Pacific/Saipan + MQ +1436-06105 America/Martinique + MR +1806-01557 Africa/Nouakchott + MS +1642-06213 America/Montserrat + MT +3554+01431 Europe/Malta + MU -2010+05730 Indian/Mauritius + MV +0410+07330 Indian/Maldives + MW -1547+03500 Africa/Blantyre + MX +1924-09909 America/Mexico_City Central Time + MX +2313-10625 America/Mazatlan Mountain Time + MX +3152-11637 America/Ensenada Pacific Time - most locations + MX +3232-11701 America/Tijuana Pacific Time - north Baja California + MY +0310+10142 Asia/Kuala_Lumpur peninsular Malaysia + MY +0133+11020 Asia/Kuching Sabah & Sarawak + MZ -2558+03235 Africa/Maputo + NA -2234+01706 Africa/Windhoek + NC -2216+16530 Pacific/Noumea + NE +1331+00207 Africa/Niamey + NF -2903+16758 Pacific/Norfolk + NG +0627+00324 Africa/Lagos + NI +1209-08617 America/Managua + NL +5222+00454 Europe/Amsterdam + NO +5955+01045 Europe/Oslo + NP +2743+08519 Asia/Katmandu + NR -0031+16655 Pacific/Nauru + NU -1901+16955 Pacific/Niue + NZ -3652+17446 Pacific/Auckland most locations + NZ -4355+17630 Pacific/Chatham Chatham Island + OM +2336+05835 Asia/Muscat + PA +0858-07932 America/Panama + PE -1203-07703 America/Lima + PF -1732-14934 Pacific/Tahiti Society Islands + PF -0900-13930 Pacific/Marquesas Marquesas Islands + PF -2308-13457 Pacific/Gambier Gambier Islands + PG -0930+14710 Pacific/Port_Moresby + PH +1435+12100 Asia/Manila + PK +2452+06703 Asia/Karachi + PL +5215+02100 Europe/Warsaw + PM +4703-05620 America/Miquelon + PN -2504-13005 Pacific/Pitcairn + PR +182806-0660622 America/Puerto_Rico + PT +3843-00908 Europe/Lisbon mainland + PT +3238-01654 Atlantic/Madeira Madeira Islands + PT +3744-02540 Atlantic/Azores Azores + PW +0720+13429 Pacific/Palau + PY -2516-05740 America/Asuncion + QA +2517+05132 Asia/Qatar + RE -2052+05528 Indian/Reunion + RO +4426+02606 Europe/Bucharest + RU +5545+03735 Europe/Moscow Moscow+00 - west Russia + RU +5312+05009 Europe/Kuybyshev Moscow+01 - Caspian Sea + RU +5651+06036 Asia/Yekaterinburg Moscow+02 - Urals + RU +5500+07324 Asia/Omsk Moscow+03 - west Siberia + RU +5502+08255 Asia/Novosibirsk Moscow+03 - Novosibirsk + RU +5601+09250 Asia/Krasnoyarsk Moscow+04 - Yenisei River + RU +5216+10420 Asia/Irkutsk Moscow+05 - Irkutsk + RU +6200+12940 Asia/Yakutsk Moscow+06 - Lena River + RU +4310+13156 Asia/Vladivostok Moscow+07 - Vladivostok + RU +5934+15048 Asia/Magadan Moscow+08 - Magadan & Sakhalin + RU +5301+15839 Asia/Kamchatka Moscow+09 - Kamchatka + RU +6445+17729 Asia/Anadyr Moscow+10 - Bering Sea + RW -0157+03004 Africa/Kigali + SA +2438+04643 Asia/Riyadh + SB -0932+16012 Pacific/Guadalcanal + SC -0440+05528 Indian/Mahe + SD +1536+03232 Africa/Khartoum + SE +5920+01803 Europe/Stockholm + SG +0117+10351 Asia/Singapore + SH -1555-00542 Atlantic/St_Helena + SI +4603+01431 Europe/Ljubljana + SJ +7800+01600 Arctic/Longyearbyen Svalbard + SJ +7059-00805 Atlantic/Jan_Mayen Jan Mayen + SK +4809+01707 Europe/Bratislava + SL +0830-01315 Africa/Freetown + SM +4355+01228 Europe/San_Marino + SN +1440-01726 Africa/Dakar + SO +0204+04522 Africa/Mogadishu + SR +0550-05510 America/Paramaribo + ST +0020+00644 Africa/Sao_Tome + SV +1342-08912 America/El_Salvador + SY +3330+03618 Asia/Damascus + SZ -2618+03106 Africa/Mbabane + TC +2128-07108 America/Grand_Turk + TD +1207+01503 Africa/Ndjamena + TG +0608+00113 Africa/Lome + TH +1345+10031 Asia/Bangkok + TJ +3835+06848 Asia/Dushanbe + TK -0922-17114 Pacific/Fakaofo + TM +3757+05823 Asia/Ashkhabad + TN +3648+01011 Africa/Tunis + TO -2110+17510 Pacific/Tongatapu + TR +4101+02858 Europe/Istanbul + TT +1039-06131 America/Port_of_Spain + TV -0831+17913 Pacific/Funafuti + TW +2503+12130 Asia/Taipei + TZ -0648+03917 Africa/Dar_es_Salaam + UA +5026+03031 Europe/Kiev most locations + UA +4457+03406 Europe/Simferopol Crimea + UG +0019+03225 Africa/Kampala + UM +1700-16830 Pacific/Johnston Johnston Atoll + UM +2813-17722 Pacific/Midway Midway Islands + UM +1917+16637 Pacific/Wake Wake Island + US +404251-0740023 America/New_York Eastern Time + US +421953-0830245 America/Detroit Eastern Time - Michigan - most locations + US +381515-0854534 America/Louisville Eastern Time - Louisville, Kentucky + US +394606-0860929 America/Indianapolis Eastern Standard Time - Indiana - most locations + US +382232-0862041 America/Indiana/Marengo Eastern Standard Time - Indiana - Crawford County + US +411745-0863730 America/Indiana/Knox Eastern Standard Time - Indiana - Starke County + US +384452-0850402 America/Indiana/Vevay Eastern Standard Time - Indiana - Switzerland County + US +415100-0873900 America/Chicago Central Time + US +450628-0873651 America/Menominee Central Time - Michigan - Wisconsin border + US +394421-1045903 America/Denver Mountain Time + US +433649-1161209 America/Boise Mountain Time - south Idaho & east Oregon + US +364708-1084111 America/Shiprock Mountain Time - Navajo + US +332654-1120424 America/Phoenix Mountain Standard Time - Arizona + US +340308-1181434 America/Los_Angeles Pacific Time + US +611305-1495401 America/Anchorage Alaska Time + US +581807-1342511 America/Juneau Alaska Time - Alaska panhandle + US +593249-1394338 America/Yakutat Alaska Time - Alaska panhandle neck + US +643004-1652423 America/Nome Alaska Time - west Alaska + US +515248-1763929 America/Adak Aleutian Islands + US +211825-1575130 Pacific/Honolulu Hawaii + UY -3453-05611 America/Montevideo + UZ +4120+06918 Asia/Tashkent + VA +4154+01227 Europe/Vatican + VC +1309-06114 America/St_Vincent + VE +1030-06656 America/Caracas + VG +1827-06437 America/Tortola + VI +1821-06456 America/St_Thomas + VN +1045+10640 Asia/Saigon + VU -1740+16825 Pacific/Efate + WF -1318-17610 Pacific/Wallis + WS -1350-17144 Pacific/Apia + YE +1245+04512 Asia/Aden + YT -1247+04514 Indian/Mayotte + YU +4450+02030 Europe/Belgrade + ZA -2615+02800 Africa/Johannesburg + ZM -1525+02817 Africa/Lusaka + ZR -0418+01518 Africa/Kinshasa west Zaire + ZR -1140+02728 Africa/Lubumbashi east Zaire + ZW -1750+03103 Africa/Harare

1 0

Re: c-common.c; strftime.c; question
by Alan.Perry＠Eng.Sun.COM Aug. 23, 1996

Aug. 23, 1996

> From guy(a)netapp.com Thu Aug 22 19:45:31 1996 > > > If you are going to follow the standards, then strftime() should replace > > %x with the "locale's appropriate date representation". That means that > > the date representation should vary based on the locale that the caller > > is running under. The default locale is the C locale. > > > > I am at home and I do not keep the standards here, so I cannot look up > > what that should be, but I can do it later tonight or tomorrow. > > My copy of ANSI X3.159-1989 doesn't appear to specify the C locale's > "appropriate date representation". My copy of IEEE 1003.1b-1993 doesn't > appear to specify it either. There must be something wrong with my real job that I am spending so much time on this :-) I found the XPG4 definition of the C/POSIX locale (for those reading along, I am in the XPG4 System Interfaces Definitions Issue 4, Version 2). The LC_TIME locale category is discussed starting at Section 5.3.5, p. 69. The C/POSIX locale value for d_fmt (the thing associated with %x) is "%m/%d/%y". This can be found on p. 75. Normally, XPG4 is not very creative here, so I doubt they made this up, but I cannot find where they could have taken it from. I will ask the big league standards guys around here tomorrow. alan

2 1

Re: c-common.c; strftime.c; question
by Alan.Perry＠Eng.Sun.COM Aug. 23, 1996

Aug. 23, 1996

>And a year-2000 related question: might it be best to change strftime so >that "%x" yields, for example, > 1996-08-22 >rather than > 08/22/96 >as is currently true? If you are going to follow the standards, then strftime() should replace %x with the "locale's appropriate date representation". That means that the date representation should vary based on the locale that the caller is running under. The default locale is the C locale. I am at home and I do not keep the standards here, so I cannot look up what that should be, but I can do it later tonight or tomorrow. alan perry former standards and libc guy current zoneinfo and device driver interfaces guy

2 1

Re: c-common.c; strftime.c; question
by alex＠agsm.unsw.edu.au Aug. 23, 1996

Aug. 23, 1996

>Jim Van Zandt writes: >Alex Livingston writes: >>>might it be best to change strftime so >>>that "%x" yields, for example, >>> 1996-08-22 >... >> >>Absolutely! It infuriates me that such a result should ever be returned. >>Any concession to the US-only >>we'll-do-it-our-way-and-never-change-and-claim-to-be-best-no-matter-how-bad- >>it-is all-numerical way of writing dates should be eliminated. > >Not all of us claim that 12/1/96 is the best way. I would support use >of the ISO 8601 format. Sorry, I generalized unfairly. I guess I went over the top (is that an expression understood in the US?). I applaud your support for ISO 8601 format. - Alex LIVINGSTON

1 0

Re: c-common.c; strftime.c; question
by alex＠agsm.unsw.edu.au Aug. 23, 1996

Aug. 23, 1996

>And a year-2000 related question: might it be best to change strftime so >that "%x" yields, for example, > 1996-08-22 >rather than > 08/22/96 >as is currently true? Absolutely! It infuriates me that such a result should ever be returned. Any concession to the US-only we'll-do-it-our-way-and-never-change-and-claim-to-be-best-no-matter-how-bad- it-is all-numerical way of writing dates should be eliminated. Alex LIVINGSTON Macintosh Support Computing & IT (C&IT) Australian Graduate School of Management (AGSM) The University of New South Wales (UNSW) Sydney NSW 2052 AUSTRALIA E-mail : alex(a)agsm.unsw.edu.au; cit(a)agsm.unsw.edu.au (C&IT) Facsimile: +61 2 93137279 Telephone: +61 2 99319264

2 1

c-common.c; strftime.c; question
by ado Aug. 22, 1996

Aug. 22, 1996

A new version of the GNU C compiler's file c-common.c is available: ftp://elsie.nci.nih.gov/pub/c-common.c This version does strftime format checking against the formats recognized by an impending release of GNU's strftime.c; as suggested by Paul Eggert, it's also been retooled to minimize the differences between it and the stock c-common.c (at the cost of a bit of obscureness). Also available is ftp://elsie.nci.nih.gov/pub/strftime.c which is a first attempt at run-time strftime format checking. If the environment variable CHECK_STRFTIME_FORMATS_FOR_TWO_DIGIT_YEARS is defined, strftime formats are checked at run time and diagnostics are written to stderr about formats that produce two-digit years in all locales, in the current locale, or in some locales. And a year-2000 related question: might it be best to change strftime so that "%x" yields, for example, 1996-08-22 rather than 08/22/96 as is currently true? Feedback on the new files and the question most welcome! --ado

1 0

Re: c-common.c
by Ulrich Drepper Aug. 20, 1996

Aug. 20, 1996

From: Paul Eggert <eggert(a)twinsun.com> Subject: Re: c-common.c Date: Mon, 19 Aug 1996 19:42:12 -0700 > Does c-common.c and/or the strftime in version 2.0 of glibc address > these points [about ISO 8601 week notation]? > > glibc 2.0 strftime doesn't. I am preparing a fix along the lines of > the tz strftime. The fix will also make GNU strftime comply with > Posix.2 section 4.15.4, and fix a few other bugs that I've discovered > by code inspection (e.g. sometimes it returns 0 when it shouldn't, and > it assumes 32-bit time_t's in a place or two). Paul, you will correct me, but a few weeks ago you tested the "week" code in strftime and you hopefully saw that I have no %U, %V, and %W implemented (all three kinds of week representation from XPG4 and therefore ISO 8601). If think %W is the representation Jim van Zandt asked for. -- Uli --------------. drepper(a)cygnus.com ,-. Rubensstrasse 5 Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany Cygnus Support `--' drepper(a)gnu.ai.mit.edu `------------------------

2 1

Re: c-common.c
by Ulrich Drepper Aug. 20, 1996

Aug. 20, 1996

From: ado(a)elsie.nci.nih.gov (Arthur David Olson) Subject: c-common.c Date: Mon, 19 Aug 96 17:25:58 EDT Hi, I took a fast look at the source and it seems to be really fine. Only one thing is not the best we could get: ** Only format characters recognized by glibc 1.09.1's strftime appear below; 1.09.1 is the last official release, but we have version 2.0 near to a date of release and the strftime function was changed. I would happily send you the last version so that you could add the other formats (mostly GNU extensions). Thanks, -- Uli --------------. drepper(a)cygnus.com ,-. Rubensstrasse 5 Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany Cygnus Support `--' drepper(a)gnu.ai.mit.edu `------------------------

1 0

UNIX System Administration Handbook CDROM
by Evi Nemeth Aug. 19, 1996

Aug. 19, 1996

August, 1996 Dear Arthur: A CD-ROM of useful software, tools, and facts for system administrators has replaced the appendices as part of the second edition of UNIX System Administration Handbook (Prentice Hall, 1995). We are about to do a new printing of the book and CD and would like to include your software package "tzcode, tzdata" on the CD. Please excuse the form-letter-ness of this message, it's due to the number of software packages in question and a lack of sophistication in my PERL programming skills. My purpose in writing covers three issues: availability, correctness of our index entry, and continuing permission to include your software. 1) We would like to confirm that "tzcode, tzdata" is in fact freely redistributable and that you have no objection to its inclusion on our CD. The CD is included with the book at no cost; the current version is available as an update for a modest distribution cost. The image of the CD can also be accessed by anonymous ftp from cs.colorado.edu. 2) We want to make sure that our page-length "index entry" from the CD for your software is accurate and complete. Both the index entry and the tentative table of contents of the CD are included below. 3) In order to expedite future updates of the CD we'd like you to choose a permission model from those listed below (or suggest your own): a) OK to include the software forever; don't bother me again b) OK to include the software, but ask each time you revise the CD c) Please DO NOT distribute my software We intend to upgrade as software evolves, but new releases of the CD will track printings of the book and so the timing is not under our control. If you agree to a "don't ask me again" model, it would help us keep our index pages current and correct if you would make the README associated with your software include any changes in the maintainer or primary ftp site. Please use email to respond; if we don't hear from you we will assume that it is OK to include your software and that our index entry is correct (permission model b), but we would prefer an explicit answer. Thank you, -evi Evi Nemeth, Assoc Prof Computer Science Dept University of Colorado Boulder, CO 80309-0430 303-492-5385

1 0

Sri Lanka situation
by Chris Carrier Aug. 17, 1996

Aug. 17, 1996

Paul Eggert > INTERNET:eggert@twinsun.com wrote: >despite the phrases used in the news articles, the Sri Lanka time switch >isn't daylight time in the usual sense -- it's a permanent change Are you sure of this? Is it 'for the duration of the emergency' or is it meant to permanent and for all time, or is it year-round until a definite date in the future? (As an aside, YRDST in the United States, when implemented in 1942, was to last until six months after the end of the war, but was modified by another bill in the summer of 1945, after the war was won, to end on the last Sunday in September, the ending date for most jurisdictions observing seasonal DST in the twenty years before the war. A lot of war-related legislation had a 'duration plus six months' clause in it.) I had imagined that the change would be year-round and not seasonal, because of SL being so near the equator; I ran some sunrise/sunset data for Colombo and noted there was only a 36 minute difference between the latest (February 2, 6:29 GMT+5:30) and earliest (May 26, 5:53 GMT+5:30) sunrises of the year.

1 0

Sri Lanka, Arthur C. Clarke
by Chris Carrier Aug. 16, 1996

Aug. 16, 1996

Did anyone get a response from anyone in Sri Lanka concerning the daylight- time situation? I've been subscribing to soc.culture.sri-lanka and haven't seen anything there other than Paul's posting, as the ng seems to be mostly about Sinhalese and Tamils living outside Sri Lanka cheering on their respective home teams and accusing each other of war crimes. Also, I wonder if Arthur C. Clarke, who lives in Sri Lanka and has made comments on time zoning, has had anything to say about it. The future of time zoning is of interest to me, especially since I live in California, and Clarke in the novel IMPERIAL EARTH (1976) projected that in 2276 we would have only four time zones. Although not explicitly stated, I believe that the times he used were GMT-5 for both American continents, GMT+1 for Europe and Africa, GMT+7 for Asia, and either GMT+13 or -11 for Australia/NZ/Pacific Ocean. Chris Carrier

2 1

Year 2000
by ado Aug. 12, 1996

Aug. 12, 1996

One thought is to provide the GNU folks with code to support a compilie-time option that checks strftime arguments and warns about warn about two-digit-year format specifications (along the lines of the checking now done of printf and scanf formats). Another thought is to set up strftime to warn about two-digit-year format specifications if a sufficiently obscurely named environment variable is present. Does anyone know of prior art in these (or other) areas? --ado

1 0

Re: Supplying names for timezones in the data files
by ado Aug. 5, 1996

Aug. 5, 1996

> # ZONE-DESCR America New_York United_States Eastern time > > Good idea, but how about a format like this instead? > > America/New_York +404251-0740023 US US Eastern time > > where the columns are: > > * zone name in tz database > * latitude and longitude (in ISO 6709 format) of the zone's main location > * country code (in ISO 3166 2-letter format) > * an (English) comment describing the zone One approach would be to, for example, Link America/New_York Coords/+404251-0740023 Link America/New_York Descrips/US_Eastern_time --ado

3 2

S.u.S.E. Linux 4.2 for Developers
by Burchard Steinbild Aug. 5, 1996

Aug. 5, 1996

To: tz(a)elsie.nci.nih.gov Date: Mon, 5 Aug 1996 18:06:23 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 2242 Hello, first of all: Sorry, if this mail seems to be a little bit unpersonal. It will be sent to a lot of people - so I don't have the time to write so many emails. It is also possible, that you get this message more than once on different email addresses, just delete the following ones ;-) Maybe you know that we produce Linux-CDROMs (some prefer: Linux based GNU System CDROMs) - maybe you've already gotten one :-) . In any case, our new triple-CD (the first one with a complete own distribution, the former releases always based on Slackware, Thanx to Pat for his great work) has been derived from your work and we would like to say "Thank You" by sending you a FREE DEVELOPER'S COPY of our CDROMs. So if you care to get hold of one, please send me your snail mail address. Don't worry about shipping costs - we'll try to find someone in every edge of this planet to carry the parcels to a local post office :-) We will allow 2-3 weeks for your response to reach us before we start shipping outside of Germany. So please be patient if it takes a little while until the packet reaches you. So, if you're interested, just reply to this mail ;-) - if you're not interested and don't want this offer anymore, drop me a line as well. Thanx again & cu ...bs PS: I think I've taken great care with the email addresses, but never- theless it is possible, that I catched an address of a mailing list. If this has happened, please be fair - this offer is only meant for developers, not for the plain user. PPS: If you answered the previous developer's mailing, and didn't get your copy until now, please do not despair! Probably the address was faulty or incomplete. Try again, so we can sort out what went wrong. PPPS: Take a look at http://www.suse.de, if you're interested in more information or simply ask me by email ;-) PPPPS: If you're interested in a list who got this offer (1000+), drop me a line. Maybe you'd like to check, if I've forgotten someone ;) -- My tip for this evening: Zappa: In New York --- Burchard Steinbild, S.u.S.E. GmbH, Gebhardtstr. 2, 90762 Fuerth, Germany Tel: +49-911-74053-0, Fax: +49-911-7417755, Email: bs(a)suse.de

1 0

Mailing list
by Ulrich Drepper Aug. 2, 1996

Aug. 2, 1996

Hi, could you please add drepper(a)gnu.ai.mit.edu to your mailing list about the time zone code. I'm now maintaining GNU libc and the time code is part of this. Thanks, -- Uli --------------. drepper(a)cygnus.com ,-. Rubensstrasse 5 Ulrich Drepper \ ,--------------------' \ 76149 Karlsruhe/Germany Cygnus Support `--' drepper(a)gnu.ai.mit.edu `------------------------

1 0

Re: daylight-saving time in Sri Lanka
by peter＠memex.co.uk July 31, 1996

July 31, 1996

> In hindsight there was some warning that Sri Lanka might adopt > daylight-saving time. In March the Sri Lanka _Sunday Observer_ > reported that the government was considering it; see > <URL:http://www.lanka.net/lakehouse/anclweb/observr/week5/hotnews/31hot01.ht…> > (1996-03-31). The motivation: Sri Lanka's hydro reservoirs, the > source of much of its electrical power, are quite low this year. This shows the amazing power of the Internet. Who amongst us would have known of the existence of this paper, let alone being able to reach out and read it. > If we > don't hear more details about the change, I propose that we assume > that Sri Lanka changed clocks at 1996-07-21 02:00 and that they'll > continue to use daylight-saving time until further notice (I'll > include this in a proposed patch that I'm preparing). I didn't check with a calendar when I just counted back ten days from the Times issue date to guess at 21 July. Note that the Sunday Observer story says it would have to be done on a Saturday at 2 am. Maybe they consider 2 am Sunday morning to be still part of Saturday night, but maybe they do mean 2 am on Saturday. Peter Ilieve peter(a)aldie.co.uk

1 0

daylight-saving time in Sri Lanka
by Paul Eggert July 31, 1996

July 31, 1996

In hindsight there was some warning that Sri Lanka might adopt daylight-saving time. In March the Sri Lanka _Sunday Observer_ reported that the government was considering it; see <URL:http://www.lanka.net/lakehouse/anclweb/observr/week5/hotnews/31hot01.ht…> (1996-03-31). The motivation: Sri Lanka's hydro reservoirs, the source of much of its electrical power, are quite low this year. And last month roshan(a)lankacom.net asked in <URL:news:31C7D974.41C6@lankacom.net> (1996-06-19) how to change an AIX host's time zone to GMT+0630. LankaCom is a new ISP, a joint venture between Singapore Telecom International and the Capital Development and Investment Co Ltd of Sri Lanka. I asked roshan ``why +0630?'', but got no response. I've emailed questions for more details about the change to the Sri Lankan embassy in Washington DC, and to Sri Lanka Telecom; I've also posted a query in soc.culture.sri-lanka and comp.std.misc. If we don't hear more details about the change, I propose that we assume that Sri Lanka changed clocks at 1996-07-21 02:00 and that they'll continue to use daylight-saving time until further notice (I'll include this in a proposed patch that I'm preparing). This assumption could well be incorrect, but it should be less incorrect than the current tz database.

1 0

Sri Lanka
by Chris Carrier July 31, 1996

July 31, 1996

Some comments/questions about the Sri Lankan situation: Does Sri Lanka plan to remain on daylight time permanently, do they intend to end it on a given date, or are they going to adopt it in the summer only? (A rather silly idea at their latitude, but it's happened before in other tropical places.) Actually my information disagrees with the Times about this change being the first in Sri Lankan history. My data states that Sri Lanka adopted daylight time in 1942 and ended it in 1945. But the phrase "the first time in the country's history" could refer to history only since its independence in the late 1940s. Called AT&T International Operator to get the time in SL and they quoted me the new time, GMT+6:30. AT&T is usually the place to go for current data. Sunrise and sunset in Sri Lanka generally occurs between 6 and 6:30 standard (7 to 7:30 daylight) time all year long. Also noted in the Times article: >Sri Lanka is a nation of clock towers, erected by a zealous government to >ensure punctuality. Sounds like they've been getting foreign aid from Singapore! :) Chris Carrier

1 0

bug report - timezone incorrectly set [forwarded with permission]
by ado July 30, 1996

July 30, 1996

I'm forwarding the attached bug report with permisison from Timothy Patrick Murphy; an updated version of the time zone code-- ftp://elsie.nci.nih.gov/pub/tzcode96j.tar.gz --is now available which sets sp->typecnt as suggested. --ado > ... > Date: Mon, 29 Jul 1996 10:24:18 -0400 > ... > To: ado(a)elsie.nci.nih.gov > Subject: bug report - timezone incorrectly set > ... > > I believe I have discovered a bug in the tzparse() function and would > like you to review this. When the value of the TZ environment > variable is of the form JKL3:10PNM4:40 the section of code between > lines 947 and 1031 in localtime.c are executed. It seems that at the > end of this block the value of sp->typecnt should be set to 2. If > this is not done and there are at least 2 entries in the ttis array > such that tt_isdst is false then the value of the global timezone > variable is corrupted on line 234 in the settzname() function. > > tpm > > Timothy Patrick Murphy tpm(a)hi.com Voice: (617) 890-0444 > Hitachi Computer Products Fax: (617) 890-4998 > 1601 Trapelo Rd., Waltham, MA 02154, USA

1 0