- tz - lists.iana.org

Blather 2000 Conference
by Monty Solomon March 15, 1996

March 15, 1996

FYI. Excerpt from mini-AIR Mar 96. ----------------------------------------------------------- 1996-03-14 Blather 2000 Conference Enough hot air has already been released to make it obvious that Humankind must anticipate accelerating amounts of endless palaver about how New Year's Eve December 31st 1999 isn't REALLY the End of the 20th Century and how January 1st, 2000 isn't REALLY going to be the First Day of the 21st Century. AIR will sponsor a conference on "Blather 2000 -- Strategies to Avoid the Pedantry." We will bring together the World's Leading Thinkers to debate and make one big announcement about what the deal is, put their statement into a widely-publicized Web Page, and then ask the second-rate usage pundits, congenital columnists, and other emitters of Sound 'n' Fury (TM) to just Shut Up About It. If you have anything to say on the matter -- anything that hasn't already been said -- please direct it to the Blather 2000 Conference chairman, Dr. Y. Foo <blather2k(a)mit.edu>

1 0

proposed tz changes for Portugal, Etc/GMT-14, and Mideast/Riyadh89
by Paul Eggert March 12, 1996

March 12, 1996

Here are proposed changes to the tz database: * Portugal is apparently not moving its clocks this spring. * Since Kiritimati is now 14 hours ahead of GMT, there should be an Etc/GMT-14 zone. (I suppose if Cuba goes ahead with its threat to move its clocks ahead by 24 hours, we'll need an Etc/GMT-19 zone...) * Fix a typo in solar89. =================================================================== RCS file: RCS/europe,v retrieving revision 1995.13 retrieving revision 1995.13.1.1 diff -c -r1995.13 -r1995.13.1.1 *** europe 1995/12/21 17:18:29 1995.13 --- europe 1996/03/12 03:16:42 1995.13.1.1 *************** *** 1644,1650 **** # 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 EC MET%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] --- 1644,1655 ---- # 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 EC 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 - "WET DST" 1996 Oct 27 1:00u ! 0:00 EC 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] =================================================================== RCS file: RCS/etcetera,v retrieving revision 1994.4 retrieving revision 1994.4.1.1 diff -c -r1994.4 -r1994.4.1.1 *** etcetera 1994/02/24 20:42:21 1994.4 --- etcetera 1996/03/12 03:16:42 1994.4.1.1 *************** *** 27,33 **** # zic -l GMT-12 # so we moved the names into the Etc subdirectory. ! Zone Etc/GMT-13 13 - GMT-13 # 12 hours ahead of GMT, plus DST Zone Etc/GMT-12 12 - GMT-12 Zone Etc/GMT-11 11 - GMT-11 Zone Etc/GMT-10 10 - GMT-10 --- 27,34 ---- # zic -l GMT-12 # so we moved the names into the Etc subdirectory. ! Zone Etc/GMT-14 14 - GMT-14 # 14 hours ahead of GMT ! Zone Etc/GMT-13 13 - GMT-13 Zone Etc/GMT-12 12 - GMT-12 Zone Etc/GMT-11 11 - GMT-11 Zone Etc/GMT-10 10 - GMT-10 =================================================================== RCS file: RCS/solar89,v retrieving revision 1996.2 retrieving revision 1996.2.1.1 diff -c -r1996.2 -r1996.2.1.1 *** solar89 1995/10/30 15:07:12 1996.2 --- solar89 1996/03/12 03:16:42 1996.2.1.1 *************** *** 390,393 **** 3:07:04 sol89 ?? 1990 3:07:04 - ?? # For backward compatibility... ! Link Asia/Riyadh88 Mideast/Riyadh88 --- 390,393 ---- 3:07:04 sol89 ?? 1990 3:07:04 - ?? # For backward compatibility... ! Link Asia/Riyadh89 Mideast/Riyadh89

1 0

Time Bomb Still Ticking For Year 2000
by Monty Solomon March 1, 1996

March 1, 1996

Excerpt from Edupage, 15 February 1996 TIME BOMB STILL TICKING FOR YEAR 2000 The Gartner Group predicts that half of all companies affected by the year 2000 date field problem will still be unprepared when the fateful day arrives. "A lot of companies are like deer frozen in the headlights of a big truck coming right at them," says a Gartner analyst. Some industry experts estimate the cost of fixing the problem at $40 million per large corporation, with the global price tag pegged at $400 billion to $600 billion. Many corporations are wondering if their old systems are worth all the trouble: "Do we just fix the millennium bug, or should we take this as an opportunity to put in some new systems?" asks one CIO. (Information Week 5 Feb 96 p30)

1 0

Portugal to change timezone again (??)
by peter＠aldie.co.uk Feb. 29, 1996

Feb. 29, 1996

The following article appeared in uk.misc and a few other groups as part of a discussion of time matters. (It is surprising how much confusion there still is about the EU start/end dates.) >From: martin(a)ci.ua.pt (Martin Bruckmann) >Newsgroups: uk.misc,soc.culture.french,rec.travel.air,rec.travel.misc, > rec.travel.europe >Subject: Re: Time difference between Paris & London after clocks change >Date: 27 Feb 1996 15:35:53 GMT >Organization: Universidade de Aveiro, Portugal >Message-ID: <4gv8cp$atu(a)titan.ci.ua.pt> > >... >And, a novelty (or back to how it was before E.U.) : Portugal is >re-adopting its more natural time, i.e. the same as in the U.K. It is >still 1h delay compared to its solar time, but it's already better than >the E.U. imposed Central European Time, which forced little kids to >wake up very early to go to school in the total darkness in Winter... > >-- >All about Portuguese Internet Sites & People on http://sapo.ua.pt I asked for some more info by email and this was the result, quoted with permission: >From: Martin Bruckmann <martin(a)ua.pt> >To: peter(a)aldie.co.uk (Peter Ilieve) >Date: Thu, 29 Feb 1996 10:09:31 +0000 (PWT) > >> [my query] >> Is this true? It was only a few years ago that you changed from GMT to CET. >> I would like to pass this information along to Arthur Olson's timezone >> mailing list. Do you have a reference to the law or whatever it is that >> says you will change back? When will you change? > >Yes, it is true. Actually, we just stayed with "Winter time" instead of >changing to Summer time this year. This has been decided by the new Prime >Minister and his government a month ago or so. Exact legal references ? I >don't have any, nor would I know where to look for them. >What is this "Arthur Olson's timezone mailing list" ? After a bit more clarification it seems that the new Portugese Prime Minister has got fed up with getting up in the dark in the Winter and has decided they won't put the clocks forward this March. I assume they will then put them back in October, reverting to GMT as they were before 1992. I am not an expert on Portugal and although Martin will undoubtedly know more than me I don't think he would consider himself a timezone expert, so best treat this as a warning for now. Does anyone know more? Peter Ilieve peter(a)aldie.co.uk

1 0

tzcode96e.tar.gz
by ado Feb. 29, 1996

Feb. 29, 1996

The file tzcode96e.tar.gz is now available for anonymous ftp from elsie.nci.nih.gov (165.112.73.1) in the ~ftp/pub directory: -rw-r--r-- 1 ado 74253 Feb 29 10:41 tzcode96e.tar.gz This include internationalization changes and the fix to the documentation for strftime. --ado

1 0

newstrftime.3 patch
by J.T. Conklin Feb. 29, 1996

Feb. 29, 1996

A NetBSD user discovered that the descriptions of the %x and %X format specifiers are swapped. --jtc Index: newstrftime.3 =================================================================== RCS file: /home/cvsroot/tz/tzcode/newstrftime.3,v retrieving revision 1.1.1.1 diff -c -r1.1.1.1 newstrftime.3 *** newstrftime.3 1996/01/15 21:48:02 1.1.1.1 --- newstrftime.3 1996/02/29 15:04:55 *************** *** 192,201 **** as a decimal number (0-6). .TP %X ! is replaced by the locale's appropriate date representation. .TP %x ! is replaced by the locale's appropriate time representation. .TP %Y is replaced by the year with century as a decimal number. --- 192,201 ---- as a decimal number (0-6). .TP %X ! is replaced by the locale's appropriate time representation. .TP %x ! is replaced by the locale's appropriate date representation. .TP %Y is replaced by the year with century as a decimal number.

1 0

Timezone names for Greenland
by ohnielse＠fysik.dtu.dk Feb. 27, 1996

Feb. 27, 1996

Dear Sir, In your timezone data file for Europe you define: # -3:00 WGT+DST Western Greenland* # -2:00 MGT+DST Middle Greenland* # -1:00 EGT+DST Eastern Greenland* 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 The naming "America" is politically incorrect. Greenland is a part of Denmark, but has had home rule for 10 or 11 years. If anything, you would have to define the zone names as "Denmark/...." or perhaps "Greenland/....". Furthermore, the town names that you give are Danish names. Greenlanders would undoubtedly insist that the Greenland names be used, so perhaps better namings would be: America/Scoresbysund -> Greenland/Ittoqqortoormiit America/Godthab -> Greenland/Nuuk America/Thule -> Greenland/Dundas I don't know if the timezone names have been fixed by international convention, but the naming would appear controversial :-) With best regards, Dr. Ole H. Nielsen Technical University of Denmark % Ole Holm Nielsen % UNI-C, Building 304 % Technical University of Denmark, DK-2800 Lyngby, Denmark % E-mail: Ole.H.Nielsen(a)uni-c.dk or Ole.H.Nielsen(a)fysik.dtu.dk % WWW URL: http://www.fysik.dtu.dk/persons/ohnielse.html % Telephone: (+45) 35 87 89 65

2 1

Bug in localtime.c
by Gibson_Roger/HEMEL_ENGINEERING_SERVERS＠uniplex.co.uk Feb. 23, 1996

Feb. 23, 1996

From: Roger Gibson (rxg(a)uniplex.co.uk) I have found a bug in 'localtime.c' for which I am sending a proposed fix. The problem occurs when 'mktime' is called with tm_mday <= 0, tm_mon > 1 and tm_year is a leap year or the year after a leap year. For such a case, the normalization is performed incorrectly, and yields a date which is one day out. The following example program demonstrates this: -------------------------------- #include <stdio.h> #include <time.h> int main() { struct tm tm; char buf[256]; memset(&tm, 0, sizeof tm); tm.tm_year = 96; /* 1996 */ tm.tm_mon = 2; /* March */ tm.tm_mday = 0; tm.tm_hour = 12; mktime(&tm); /* Should give Feb 29 */ strftime(buf, sizeof buf, "%C", &tm); printf("%s\n", buf); return 0; } -------------------------------- To deal with cases like this, the 'time2' function decrements the year, and adds the corresponding number of days to 'tm_mday'. The problem is that the number of days is taken to be that in the year after it has been decremented, whereas it is actually that in the year which contains the end of February which is spanned by the interval. It is necessary to take 'tm_mon' into account in determining this. The same problem occurs in the part of the code which deals with values of 'tm_mday' which exceed the number of days in a year. The version of 'time2' below contains my attempt to fix these problems. It seems to work, but I'd like to know if you concur. -------------------------------- Version information: static char elsieid[] = "@(#)localtime.c 7.44"; (Still present in version 7.55.) -------------------------------- static time_t time2(tmp, funcp, offset, okayp) struct tm * const tmp; void (* const funcp) P((const time_t*, long, struct tm*)); const long offset; int * const okayp; { register const struct state * sp; register int dir; register int bits; register int i, j ; register int saved_seconds; time_t newt; time_t t; struct tm yourtm, mytm; *okayp = FALSE; yourtm = *tmp; if (normalize_overflow(&yourtm.tm_hour, &yourtm.tm_min, MINSPERHOUR)) return WRONG; if (normalize_overflow(&yourtm.tm_mday, &yourtm.tm_hour, HOURSPERDAY)) return WRONG; if (normalize_overflow(&yourtm.tm_year, &yourtm.tm_mon, MONSPERYEAR)) return WRONG; /* ** Turn yourtm.tm_year into an actual year number for now. ** It is converted back to an offset from TM_YEAR_BASE later. */ if (increment_overflow(&yourtm.tm_year, TM_YEAR_BASE)) return WRONG; while (yourtm.tm_mday <= 0) { if (increment_overflow(&yourtm.tm_year, -1)) return WRONG; if (yourtm.tm_mon >= 2) yourtm.tm_mday += year_lengths[isleap(yourtm.tm_year + 1)]; else yourtm.tm_mday += year_lengths[isleap(yourtm.tm_year)]; } while (yourtm.tm_mday > DAYSPERLYEAR) { if (yourtm.tm_mon >= 2) yourtm.tm_mday -= year_lengths[isleap(yourtm.tm_year + 1)]; else yourtm.tm_mday -= year_lengths[isleap(yourtm.tm_year)]; if (increment_overflow(&yourtm.tm_year, 1)) return WRONG; } for ( ; ; ) { i = mon_lengths[isleap(yourtm.tm_year)][yourtm.tm_mon]; if (yourtm.tm_mday <= i) break; yourtm.tm_mday -= i; if (++yourtm.tm_mon >= MONSPERYEAR) { yourtm.tm_mon = 0; if (increment_overflow(&yourtm.tm_year, 1)) return WRONG; } } if (increment_overflow(&yourtm.tm_year, -TM_YEAR_BASE)) return WRONG; if (yourtm.tm_year + TM_YEAR_BASE < EPOCH_YEAR) { /* ** We can't set tm_sec to 0, because that might push the ** time below the minimum representable time. ** Set tm_sec to 59 instead. ** This assumes that the minimum representable time is ** not in the same minute that a leap second was deleted from, ** which is a safer assumption than using 58 would be. */ if (increment_overflow(&yourtm.tm_sec, 1 - SECSPERMIN)) return WRONG; saved_seconds = yourtm.tm_sec; yourtm.tm_sec = SECSPERMIN - 1; } else { saved_seconds = yourtm.tm_sec; yourtm.tm_sec = 0; } /* ** Calculate the number of magnitude bits in a time_t ** (this works regardless of whether time_t is ** signed or unsigned, though lint complains if unsigned). */ for (bits = 0, t = 1; t > 0; ++bits, t <<= 1) continue; /* ** If time_t is signed, then 0 is the median value, ** if time_t is unsigned, then 1 << bits is median. */ t = (t < 0) ? 0 : ((time_t) 1 << bits); for ( ; ; ) { (*funcp)(&t, offset, &mytm); dir = tmcomp(&mytm, &yourtm); if (dir != 0) { if (bits-- < 0) return WRONG; if (bits < 0) --t; else if (dir > 0) t -= (time_t) 1 << bits; else t += (time_t) 1 << bits; continue; } if (yourtm.tm_isdst < 0 || mytm.tm_isdst == yourtm.tm_isdst) break; /* ** Right time, wrong type. ** Hunt for right time, right type. ** It's okay to guess wrong since the guess ** gets checked. */ /* ** The (void *) casts are the benefit of SunOS 3.3 on Sun 2's. */ sp = (const struct state *) (((void *) funcp == (void *) localsub) ? lclptr : gmtptr); #ifdef ALL_STATE if (sp == NULL) return WRONG; #endif /* defined ALL_STATE */ for (i = 0; i < sp->typecnt; ++i) { if (sp->ttis[i].tt_isdst != yourtm.tm_isdst) continue; for (j = 0; j < sp->typecnt; ++j) { if (sp->ttis[j].tt_isdst == yourtm.tm_isdst) continue; newt = t + sp->ttis[j].tt_gmtoff - sp->ttis[i].tt_gmtoff; (*funcp)(&newt, offset, &mytm); if (tmcomp(&mytm, &yourtm) != 0) continue; if (mytm.tm_isdst != yourtm.tm_isdst) continue; /* ** We have a match. */ t = newt; goto label; } } return WRONG; } label: newt = t + saved_seconds; if ((newt < t) != (saved_seconds < 0)) return WRONG; t = newt; (*funcp)(&t, offset, tmp); *okayp = TRUE; return t; }

1 0

Timezones
by Ravi Narine Feb. 21, 1996

Feb. 21, 1996

Hi there, My name is Ravi Narine, and I am a software developer for Bell Sygma Inc. We are using the Timezone library that you have created. I am wondering is there a program that can take information (ex. city,country,province,state,area code or anything on that means) and return me the timezone that is in. Greatly appreciated Ravi Narine

1 0

None
by Roland McGrath Feb. 19, 1996

Feb. 19, 1996

In the GNU C library I use zic.c and zdump.c verbatim from tzcode96d, except for marking all the strings for user messages so they can be translated through message catalogs. Could these changes perhaps be merged so I don't have to re-modify each new version? It is quite simple and unobtrusive: put in private.h or someplace: #ifndef _ #define _(x) x #endif (in my system, _ will be defined as a macro that invokes the translation lookup). Here are the patches to zic.c and zdump.c to make their "messages" use _("messages"). Can I hope to get this merged into the tzcode distribution? Thanks, Roland --- /home/fsf/roland/libc/time/=ado/96d/zic.c Mon Feb 12 11:01:33 1996 +++ /src/libc/time/zic.c Mon Feb 19 18:31:47 1996 @@ -396,10 +396,10 @@ const char * const string; ** zic ... 2>&1 | error -t "*" -v ** on BSD systems. */ - (void) fprintf(stderr, "\"%s\", line %d: %s", + (void) fprintf(stderr, _("\"%s\", line %d: %s"), filename, linenum, string); if (rfilename != NULL) - (void) fprintf(stderr, " (rule from \"%s\", line %d)", + (void) fprintf(stderr, _(" (rule from \"%s\", line %d)"), rfilename, rlinenum); (void) fprintf(stderr, "\n"); ++errors; @@ -408,9 +408,9 @@ const char * const string; static void usage P((void)) { - (void) fprintf(stderr, "%s: usage is %s \ + (void) fprintf(stderr, _("%s: usage is %s \ [ -s ] [ -v ] [ -l localtime ] [ -p posixrules ] [ -d directory ]\n\ -\t[ -L leapseconds ] [ -y yearistype ] [ filename ... ]\n", +\t[ -L leapseconds ] [ -y yearistype ] [ filename ... ]\n"), progname, progname); (void) exit(EXIT_FAILURE); } @@ -444,7 +444,7 @@ char * argv[]; directory = optarg; else { (void) fprintf(stderr, -"%s: More than one -d option specified\n", +_("%s: More than one -d option specified\n"), progname); (void) exit(EXIT_FAILURE); } @@ -454,7 +454,7 @@ char * argv[]; lcltime = optarg; else { (void) fprintf(stderr, -"%s: More than one -l option specified\n", +_("%s: More than one -l option specified\n"), progname); (void) exit(EXIT_FAILURE); } @@ -464,7 +464,7 @@ char * argv[]; psxrules = optarg; else { (void) fprintf(stderr, -"%s: More than one -p option specified\n", +_("%s: More than one -p option specified\n"), progname); (void) exit(EXIT_FAILURE); } @@ -474,7 +474,7 @@ char * argv[]; yitcommand = optarg; else { (void) fprintf(stderr, -"%s: More than one -y option specified\n", +_("%s: More than one -y option specified\n"), progname); (void) exit(EXIT_FAILURE); } @@ -484,7 +484,7 @@ char * argv[]; leapsec = optarg; else { (void) fprintf(stderr, -"%s: More than one -L option specified\n", +_("%s: More than one -L option specified\n"), progname); (void) exit(EXIT_FAILURE); } @@ -567,7 +567,7 @@ const char * const tofile; if (mkdirs(toname) != 0) (void) exit(EXIT_FAILURE); if (link(fromname, toname) != 0) { - (void) fprintf(stderr, "%s: Can't link from %s to ", + (void) fprintf(stderr, _("%s: Can't link from %s to "), progname, fromname); (void) perror(toname); (void) exit(EXIT_FAILURE); @@ -688,7 +688,7 @@ associate P((void)) ** a '%s' in the format is a bad thing. */ if (strchr(zp->z_format, '%') != 0) - error("%s in ruleless zone"); + error(_("%s in ruleless zone")); } } if (errors) @@ -709,10 +709,10 @@ const char * name; char buf[BUFSIZ]; if (strcmp(name, "-") == 0) { - name = "standard input"; + name = _("standard input"); fp = stdin; } else if ((fp = fopen(name, "r")) == NULL) { - (void) fprintf(stderr, "%s: Can't open ", progname); + (void) fprintf(stderr, _("%s: Can't open "), progname); (void) perror(name); (void) exit(EXIT_FAILURE); } @@ -723,7 +723,7 @@ const char * name; break; cp = strchr(buf, '\n'); if (cp == NULL) { - error("line too long"); + error(_("line too long")); (void) exit(EXIT_FAILURE); } *cp = '\0'; @@ -743,7 +743,7 @@ const char * name; } else { lp = byword(fields[0], line_codes); if (lp == NULL) - error("input line of unknown type"); + error(_("input line of unknown type")); else switch ((int) (lp->l_value)) { case LC_RULE: inrule(fields, nfields); @@ -759,14 +759,14 @@ const char * name; case LC_LEAP: if (name != leapsec) (void) fprintf(stderr, -"%s: Leap line in non leap seconds file %s\n", +_("%s: Leap line in non leap seconds file %s\n"), progname, name); else inleap(fields, nfields); wantcont = FALSE; break; default: /* "cannot happen" */ (void) fprintf(stderr, -"%s: panic: Invalid l_value %d\n", +_("%s: panic: Invalid l_value %d\n"), progname, lp->l_value); (void) exit(EXIT_FAILURE); } @@ -774,17 +774,17 @@ const char * name; ifree((char *) fields); } if (ferror(fp)) { - (void) fprintf(stderr, "%s: Error reading ", progname); + (void) fprintf(stderr, _("%s: Error reading "), progname); (void) perror(filename); (void) exit(EXIT_FAILURE); } if (fp != stdin && fclose(fp)) { - (void) fprintf(stderr, "%s: Error closing ", progname); + (void) fprintf(stderr, _("%s: Error closing "), progname); (void) perror(filename); (void) exit(EXIT_FAILURE); } if (wantcont) - error("expected continuation line not found"); + error(_("expected continuation line not found")); } /* @@ -839,16 +839,16 @@ const int nfields; static struct rule r; if (nfields != RULE_FIELDS) { - error("wrong number of fields on Rule line"); + error(_("wrong number of fields on Rule line")); return; } if (*fields[RF_NAME] == '\0') { - error("nameless rule"); + error(_("nameless rule")); return; } r.r_filename = filename; r.r_linenum = linenum; - r.r_stdoff = gethms(fields[RF_STDOFF], "invalid saved time", TRUE); + r.r_stdoff = gethms(fields[RF_STDOFF], _("invalid saved time"), TRUE); rulesub(&r, fields[RF_LOYEAR], fields[RF_HIYEAR], fields[RF_COMMAND], fields[RF_MONTH], fields[RF_DAY], fields[RF_TOD]); r.r_name = ecpyalloc(fields[RF_NAME]); @@ -867,13 +867,13 @@ const int nfields; static char * buf; if (nfields < ZONE_MINFIELDS || nfields > ZONE_MAXFIELDS) { - error("wrong number of fields on Zone line"); + error(_("wrong number of fields on Zone line")); return FALSE; } if (strcmp(fields[ZF_NAME], TZDEFAULT) == 0 && lcltime != NULL) { buf = erealloc(buf, (int) (132 + strlen(TZDEFAULT))); (void) sprintf(buf, -"\"Zone %s\" line and -l option are mutually exclusive", +_("\"Zone %s\" line and -l option are mutually exclusive"), TZDEFAULT); error(buf); return FALSE; @@ -881,7 +881,7 @@ const int nfields; if (strcmp(fields[ZF_NAME], TZDEFRULES) == 0 && psxrules != NULL) { buf = erealloc(buf, (int) (132 + strlen(TZDEFRULES))); (void) sprintf(buf, -"\"Zone %s\" line and -p option are mutually exclusive", +_("\"Zone %s\" line and -p option are mutually exclusive"), TZDEFRULES); error(buf); return FALSE; @@ -893,7 +893,7 @@ const int nfields; strlen(fields[ZF_NAME]) + strlen(zones[i].z_filename))); (void) sprintf(buf, -"duplicate zone name %s (file \"%s\", line %d)", +_("duplicate zone name %s (file \"%s\", line %d)"), fields[ZF_NAME], zones[i].z_filename, zones[i].z_linenum); @@ -909,7 +909,7 @@ register char ** const fields; const int nfields; { if (nfields < ZONEC_MINFIELDS || nfields > ZONEC_MAXFIELDS) { - error("wrong number of fields on Zone continuation line"); + error(_("wrong number of fields on Zone continuation line")); return FALSE; } return inzsub(fields, nfields, TRUE); @@ -949,10 +949,10 @@ const int iscont; } z.z_filename = filename; z.z_linenum = linenum; - z.z_gmtoff = gethms(fields[i_gmtoff], "invalid GMT offset", TRUE); + z.z_gmtoff = gethms(fields[i_gmtoff], _("invalid GMT offset"), TRUE); if ((cp = strchr(fields[i_format], '%')) != 0) { if (*++cp != 's' || strchr(cp, '%') != 0) { - error("invalid abbreviation format"); + error(_("invalid abbreviation format")); return FALSE; } } @@ -978,8 +978,8 @@ const int iscont; zones[nzones - 1].z_untiltime > min_time && zones[nzones - 1].z_untiltime < max_time && zones[nzones - 1].z_untiltime >= z.z_untiltime) { - error("Zone continuation line end time is not \ -after end time of previous line"); + error(_("Zone continuation line end time is \ +not after end time of previous line")); return FALSE; } } @@ -1006,7 +1006,7 @@ const int nfields; time_t t; if (nfields != LEAP_FIELDS) { - error("wrong number of fields on Leap line"); + error(_("wrong number of fields on Leap line")); return; } dayoff = 0; @@ -1015,7 +1015,7 @@ const int nfields; /* * Leapin' Lizards! */ - error("invalid leaping year"); + error(_("invalid leaping year")); return; } j = EPOCH_YEAR; @@ -1030,7 +1030,7 @@ const int nfields; dayoff = oadd(dayoff, eitol(i)); } if ((lp = byword(fields[LP_MONTH], mon_names)) == NULL) { - error("invalid month name"); + error(_("invalid month name")); return; } month = lp->l_value; @@ -1043,7 +1043,7 @@ const int nfields; cp = fields[LP_DAY]; if (sscanf(cp, scheck(cp, "%d"), &day) != 1 || day <= 0 || day > len_months[isleap(year)][month]) { - error("invalid day of month"); + error(_("invalid day of month")); return; } dayoff = oadd(dayoff, eitol(day - 1)); @@ -1056,7 +1056,7 @@ const int nfields; ** Cheap overflow check. */ if (t / SECSPERDAY != dayoff) { - error("time overflow"); + error(_("time overflow")); return; } tod = gethms(fields[LP_TIME], "invalid time of day", FALSE); @@ -1078,11 +1078,11 @@ const int nfields; positive = TRUE; count = 2; } else { - error("illegal CORRECTION field on Leap line"); + error(_("illegal CORRECTION field on Leap line")); return; } if ((lp = byword(fields[LP_ROLL], leap_types)) == NULL) { - error("illegal Rolling/Stationary field on Leap line"); + error(_("illegal Rolling/Stationary field on Leap line")); return; } leapadd(tadd(t, tod), positive, lp->l_value, count); @@ -1097,15 +1097,15 @@ const int nfields; struct link l; if (nfields != LINK_FIELDS) { - error("wrong number of fields on Link line"); + error(_("wrong number of fields on Link line")); return; } if (*fields[LF_FROM] == '\0') { - error("blank FROM field on Link line"); + error(_("blank FROM field on Link line")); return; } if (*fields[LF_TO] == '\0') { - error("blank TO field on Link line"); + error(_("blank TO field on Link line")); return; } l.l_filename = filename; @@ -1133,7 +1133,7 @@ const char * const timep; register char * ep; if ((lp = byword(monthp, mon_names)) == NULL) { - error("invalid month name"); + error(_("invalid month name")); return; } rp->r_month = lp->l_value; @@ -1177,11 +1177,11 @@ const char * const timep; break; default: /* "cannot happen" */ (void) fprintf(stderr, - "%s: panic: Invalid l_value %d\n", + _("%s: panic: Invalid l_value %d\n"), progname, lp->l_value); (void) exit(EXIT_FAILURE); } else if (sscanf(cp, scheck(cp, "%d"), &rp->r_loyear) != 1) { - error("invalid starting year"); + error(_("invalid starting year")); return; } cp = hiyearp; @@ -1197,22 +1197,22 @@ const char * const timep; break; default: /* "cannot happen" */ (void) fprintf(stderr, - "%s: panic: Invalid l_value %d\n", + _("%s: panic: Invalid l_value %d\n"), progname, lp->l_value); (void) exit(EXIT_FAILURE); } else if (sscanf(cp, scheck(cp, "%d"), &rp->r_hiyear) != 1) { - error("invalid ending year"); + error(_("invalid ending year")); return; } if (rp->r_loyear > rp->r_hiyear) { - error("starting year greater than ending year"); + error(_("starting year greater than ending year")); return; } if (*typep == '\0') rp->r_yrtype = NULL; else { if (rp->r_loyear == rp->r_hiyear) { - error("typed single year"); + error(_("typed single year")); return; } rp->r_yrtype = ecpyalloc(typep); @@ -1242,12 +1242,12 @@ const char * const timep; if (rp->r_dycode != DC_DOM) { *ep++ = 0; if (*ep++ != '=') { - error("invalid day of month"); + error(_("invalid day of month")); ifree(dp); return; } if ((lp = byword(dp, wday_names)) == NULL) { - error("invalid weekday name"); + error(_("invalid weekday name")); ifree(dp); return; } @@ -1256,7 +1256,7 @@ const char * const timep; if (sscanf(ep, scheck(ep, "%d"), &rp->r_dayofmonth) != 1 || rp->r_dayofmonth <= 0 || (rp->r_dayofmonth > len_months[1][rp->r_month])) { - error("invalid day of month"); + error(_("invalid day of month")); ifree(dp); return; } @@ -1303,7 +1303,8 @@ const char * const name; if (mkdirs(fullname) != 0) (void) exit(EXIT_FAILURE); if ((fp = fopen(fullname, "wb")) == NULL) { - (void) fprintf(stderr, "%s: Can't create ", progname); + (void) fprintf(stderr, _("%s: Can't create "), + progname); (void) perror(fullname); (void) exit(EXIT_FAILURE); } @@ -1368,7 +1369,7 @@ const char * const name; for (i = 0; i < typecnt; ++i) (void) putc(ttisgmts[i], fp); if (ferror(fp) || fclose(fp)) { - (void) fprintf(stderr, "%s: Write error on ", progname); + (void) fprintf(stderr, _("%s: Write error on "), progname); (void) perror(fullname); (void) exit(EXIT_FAILURE); } @@ -1586,7 +1587,7 @@ const int type; if (timecnt == 0 && type == 0 && isdsts[0] == 0) return; /* handled by default rule */ if (timecnt >= TZ_MAX_TIMES) { - error("too many transitions?!"); + error(_("too many transitions?!")); (void) exit(EXIT_FAILURE); } ats[timecnt] = starttime; @@ -1620,7 +1621,7 @@ const int ttisgmt; ** many. */ if (typecnt >= TZ_MAX_TYPES) { - error("too many local time types"); + error(_("too many local time types")); (void) exit(EXIT_FAILURE); } gmtoffs[i] = gmtoff; @@ -1648,13 +1649,13 @@ int count; register int i, j; if (leapcnt + (positive ? count : 1) > TZ_MAX_LEAPS) { - error("too many leap seconds"); + error(_("too many leap seconds")); (void) exit(EXIT_FAILURE); } for (i = 0; i < leapcnt; ++i) if (t <= trans[i]) { if (t == trans[i]) { - error("repeated leap second moment"); + error(_("repeated leap second moment")); (void) exit(EXIT_FAILURE); } break; @@ -1704,8 +1705,8 @@ const char * const type; return TRUE; if (result == (1 << 8)) return FALSE; - error("Wild result from command execution"); - (void) fprintf(stderr, "%s: command was '%s', result was %d\n", + error(_("Wild result from command execution")); + (void) fprintf(stderr, _("%s: command was '%s', result was %d\n"), progname, buf, result); for ( ; ; ) (void) exit(EXIT_FAILURE); @@ -1799,7 +1800,7 @@ register char * cp; else while ((*dp = *cp++) != '"') if (*dp != '\0') ++dp; - else error("Odd number of quotation marks"); + else error(_("Odd number of quotation marks")); } while (*cp != '\0' && *cp != '#' && (!isascii(*cp) || !isspace((unsigned char) *cp))); if (isascii(*cp) && isspace((unsigned char) *cp)) @@ -1819,7 +1820,7 @@ const long t2; t = t1 + t2; if ((t2 > 0 && t <= t1) || (t2 < 0 && t >= t1)) { - error("time overflow"); + error(_("time overflow")); (void) exit(EXIT_FAILURE); } return t; @@ -1838,7 +1839,7 @@ const long t2; return min_time; t = t1 + t2; if ((t2 > 0 && t <= t1) || (t2 < 0 && t >= t1)) { - error("time overflow"); + error(_("time overflow")); (void) exit(EXIT_FAILURE); } return t; @@ -1885,7 +1886,7 @@ register const int wantedy; if (rp->r_dycode == DC_DOWLEQ) --i; else { - error("use of 2/29 in non leap-year"); + error(_("use of 2/29 in non leap-year")); (void) exit(EXIT_FAILURE); } } @@ -1919,7 +1920,7 @@ register const int wantedy; --i; } if (i < 0 || i >= len_months[isleap(y)][m]) { - error("no day in month matches rule"); + error(_("no day in month matches rule")); (void) exit(EXIT_FAILURE); } } @@ -1942,7 +1943,7 @@ const char * const string; i = strlen(string) + 1; if (charcnt + i > TZ_MAX_CHARS) { - error("too many, or too long, time zone abbreviations"); + error(_("too many, or too long, time zone abbreviations")); (void) exit(EXIT_FAILURE); } (void) strcpy(&chars[charcnt], string); @@ -1977,7 +1978,7 @@ char * const argname; */ if (mkdir(name, 0755) != 0) { (void) fprintf(stderr, - "%s: Can't create directory ", + _("%s: Can't create directory "), progname); (void) perror(name); ifree(name); @@ -1999,7 +2000,7 @@ const int i; 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", + _("%s: %d did not sign extend correctly\n"), progname, i); (void) exit(EXIT_FAILURE); } --- /home/fsf/roland/libc/time/=ado/96d/zdump.c Mon Feb 12 11:01:55 1996 +++ /src/libc/time/zdump.c Tue Feb 13 02:45:50 1996 @@ -132,7 +132,7 @@ char * argv[]; if (c != EOF || (optind == argc - 1 && strcmp(argv[optind], "=") == 0)) { (void) fprintf(stderr, -"%s: usage is %s [ -v ] [ -c cutoff ] zonename ...\n", +_("%s: usage is %s [ -v ] [ -c cutoff ] zonename ...\n"), argv[0], argv[0]); (void) exit(EXIT_FAILURE); } @@ -224,9 +224,9 @@ char * argv[]; show(argv[i], t, TRUE);

1 0

Re: mktime() failure vs 31-DEC-1969 23:59:59 GMT
by tomp＠zk3.dec.com Feb. 19, 1996

Feb. 19, 1996

Hi Valery, > My man page on mktime() (Solaris2) clearly says that 'tm_year > of the tm structure must be for year 1970 or later.' This would seem to limit the usefulness of timezone rules prior to 1970 with respect to mktime(). Perhaps they did this for standards compliance? thanks, - Tom

2 3

Re: mktime() failure vs 31-DEC-1969 23:59:59 GMT
by Bradley White Feb. 16, 1996

Feb. 16, 1996

>> Call localtime() on the seemingly-in-error mktime() result, and compare >> the relevant portions of the structs tm. A match implies a non-error. > This doesn't sound very stable, but perhaps there is no other alternative. I'm not sure of what you mean by stable. This is, after all, exactly what mktime() does to determine is has the matching time_t. > Of course, we only need to check this > when the return of mktime() is -1 Exactly what I meant by "Call localtime() on the seemingly-in-error mktime() result."

2 1

Re: mktime() failure vs 31-DEC-1969 23:59:59 GMT
by ado Feb. 16, 1996

Feb. 16, 1996

> > Another possibility is to save away the original tm structure; if mktime > > returns -1, bump the tm_sec value by 1, call mktime again, and see if it > > returns zero. > > This still doesn't tell me whether the -1 return from mktime() meant > that the time was not representable. It does tell me whether it is > representable one second later. If a particular implementation of > mktime() doesn't support times before the Epoch (and that seems okay > as far as the standards go), then a return of 0 resulting from bumping > the tm_sec up by 1 would lead me to the wrong conclusion concerning my > original call. Oops...point well taken! Would subtracting one from tm_sec (and looking for a return of -2) work? --ado

1 0

Timezone change for Mexico: the Presidential Decree
by Alan.Perry＠Eng.Sun.COM Feb. 15, 1996

Feb. 15, 1996

A guy from our Mexico subsidiary finally found the Presidential Decree outlining the timezone changes in Mexico. ------------- Begin Forwarded Message ------------- I finally got my hands on the Official Presidential Decree that sets up the rules for the DST changes. The rules are: 1. The country is divided in 3 timezones: - Baja California Norte (the Mexico/BajaNorte TZ) - Baja California Sur, Nayarit, Sinaloa and Sonora (the Mexico/BajaSur TZ) - The rest of the country (the Mexico/General TZ) 2. From the first Sunday in April at 2:00 AM to the last Sunday in October at 2:00 AM, the times in each zone are as follows: BajaNorte: GMT+7 BajaSur: GMT+6 General: GMT+5 3. The rest of the year, the times are as follows: BajaNorte: GMT+8 BajaSur: GMT+7 General: GMT+6 The Decree was published in Mexico's Official Newspaper on January 4th. -------------- End Forwarded Message --------------

1 0

Re: mktime() failure vs 31-DEC-1969 23:59:59 GMT
by ado Feb. 14, 1996

Feb. 14, 1996

> > The standards for mktime() define a return value of > > (time_t)-1 as indicating that the time specified cannot be > > represented. However, a return value of -1 is also a valid time_t > > corresponding to 31-DEC-1969 23:59:59 GMT. How do we distinguish > > between the two? > > Call localtime() on the seemingly-in-error mktime() result, and compare > the relevant portions of the structs tm. A match implies a non-error. Since there's normalization going on in mktime, the tm that comes back from localtime may not match the one that went in to mktime even if -1 is being returned as a legitimate time_t rather than an error indication. Another possibility is to save away the original tm structure; if mktime returns -1, bump the tm_sec value by 1, call mktime again, and see if it returns zero. --ado

2 1

Re: mktime() failure vs 31-DEC-1969 23:59:59 GMT
by Bradley White Feb. 14, 1996

Feb. 14, 1996

> The standards for mktime() define a return value of > (time_t)-1 as indicating that the time specified cannot be > represented. However, a return value of -1 is also a valid time_t > corresponding to 31-DEC-1969 23:59:59 GMT. How do we distinguish > between the two? Call localtime() on the seemingly-in-error mktime() result, and compare the relevant portions of the structs tm. A match implies a non-error.

2 1

mktime() failure vs 31-DEC-1969 23:59:59 GMT
by tomp＠zk3.dec.com Feb. 14, 1996

Feb. 14, 1996

This has probably been discussed before, but perhaps someone can bring me up to speed. The standards for mktime() define a return value of (time_t)-1 as indicating that the time specified cannot be represented. However, a return value of -1 is also a valid time_t corresponding to 31-DEC-1969 23:59:59 GMT. How do we distinguish between the two? Here's a sample program: #include <time.h> #include <strings.h> #include <string.h> #include <stdio.h> main() { struct tm stm; time_t timet; memset(&stm, 0, sizeof(stm)); putenv("TZ=GMT0"); stm.tm_sec = 59; stm.tm_min = 59; stm.tm_hour = 23; stm.tm_mday = 31; stm.tm_mon = 11; stm.tm_year = 69; stm.tm_isdst = -1; timet = mktime(&stm); printf("timet = %ld\n",timet); } thanks, - Tom

4 4

Re: tztab changes for HPUX
by ado Feb. 12, 1996

Feb. 12, 1996

Current versions of the public-domain time zone package do the right thing for October, 1995: Script started on Mon Feb 12 10:53:47 1996 elsie$ ./zdump -v Europe/London | grep 1995 Europe/London Sun Mar 26 00:59:59 1995 GMT = Sun Mar 26 00:59:59 1995 GMT isdst=0 Europe/London Sun Mar 26 01:00:00 1995 GMT = Sun Mar 26 02:00:00 1995 BST isdst=1 Europe/London Sun Oct 22 00:59:59 1995 GMT = Sun Oct 22 01:59:59 1995 BST isdst=1 Europe/London Sun Oct 22 01:00:00 1995 GMT = Sun Oct 22 01:00:00 1995 GMT isdst=0 elsie$ exit script done on Mon Feb 12 10:54:36 1996 Howmsoever...the references to and excerpts from "tztab" files in the articles about HPUX indicate the existence of an alternate and (presumably better) way of handling time zone stuff. If anyone has tztab insights to share with folks on the list, I'd love it. --ado

2 1

tzcode96d.tar.gz and tzdata96c.tar.gz
by ado Feb. 12, 1996

Feb. 12, 1996

Updated time zone files are available using anonymous ftp from elsie.nci.nih.gov (165.112.73.1) in the ~ftp/pub directory: -rw-r--r-- 1 ado 73315 Feb 12 11:05 tzcode96d.tar.gz -rw-r--r-- 1 ado 73301 Feb 12 11:05 tzdata96c.tar.gz The "code" file simply updates Bob Kridle's electronic address; the "data" file updates rules for Mexico. --ado

1 0

Re: Fault in tztab on HP-UX
by Monty Solomon Feb. 10, 1996

Feb. 10, 1996

FYI Begin forwarded message: Newsgroups: comp.sys.hp.hpux From: hmc(a)cee.hw.ac.uk (Hugh Conner) Subject: Re: Fault in tztab on HP-UX Message-Id: <DGwHBL.DI9(a)cee.hw.ac.uk> Sender: news(a)cee.hw.ac.uk (News Administrator) Organization: Dept of Computing & Electrical Engineering, Heriot-Watt University, Scotland References: <308A28E6.186D(a)ug.eds.com> Date: Mon, 23 Oct 1995 11:59:45 GMT In article <308A28E6.186D(a)ug.eds.com>, Daniel Dignam <daniel(a)ug.eds.com> writes: > There's a fault in the tztab entry for GMT0BST in 9.05, the clocks went > back today (the 22nd), but date under HP-UX is still stuck at BST :-(. > The relevant entry from tztab is as follows > > > # 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-2038 0 BST-1 > 0 1 25-31 10 1983-1985 0 GMT0 > 0 1 23-29 10 1986-2038 0 GMT0 > > As I understand this table it should read > > 0 1 22-29 10 1986-2038 0 GMT0 > > Anways, I guess the technology will sort itself out tomorrow, I wonder > how much breaks because of this ? The problem is that they decided to change the clocks back a week earlier than normal this year, thus screwing up all Unix systems time tables, not just HPs. I believe that next year it will be changed again so that Britain changes over at the same time as the rest of Europe, so you'll have to edit the tztab all over again. -- Hugh M. Conner hmc(a)cee.hw.ac.uk "Wot? No signature!"

1 0

tztab changes for HPUX
by Monty Solomon Feb. 10, 1996

Feb. 10, 1996

FYI Begin forwarded message: From: ajm(a)hpwin064.uksr.hp.com (Andy Monks) Newsgroups: comp.sys.hp.hpux Subject: tztab changes for HPUX Date: 23 Oct 1995 11:03:18 GMT Organization: Hewlett-Packard Message-Id: <46fspm$bhk(a)hpwin055.uksr.hp.com> -----BEGIN PGP SIGNED MESSAGE----- Dear Customer, Recent legislation has redefined the date at which we change between British Summer Time and Greenwich Mean Time. In 1995 we will return to GMT on 22nd October at 02:00 BST. The timezone adjustment table supplied with HP-UX does not take these legislative changes into account, and therefore modifications must be made if the time change is to take place correctly. The file to be modified is /usr/lib/tztab; it can be modified using vi. The section for British time is headed with the line "# Greenwich Mean Time, British Summer Time", and the table beneath it must be modified to resemble the table below: # 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-1994 0 BST-1 0 2 25-31 3 1995-2038 0 BST-1 0 1 25-31 10 1983-1985 0 GMT0 0 1 23-29 10 1986-1994 0 GMT0 0 1 21-27 10 1995 0 GMT0 0 1 25-31 10 1996-2038 0 GMT0 Note: The character 0 is the number zero in all cases include the GMT0BST line. IF THESE MODIFICATIONS ARE NOT MADE, YOUR SYSTEM WILL NOT CHANGE TO GMT ON 22ND OCTOBER THIS YEAR. It is also important to restart the cron daemon. If you need any further information, please contact the Hewlett-Packard Response Centre on 01344-366366. Yours faithfully, The Response Centre -----BEGIN PGP SIGNATURE----- Version: 2.6.2i iQCVAwUBMIt1+zjIE3zxzhaxAQHcoQQA1JEkjfFdwIDdKnCO1yAX1y9b/dJtU6aB uUAeBbZuONFAWJLlbkVO0FwU2RvXAGfbiApTQapxwlL2RBkU4u23Yynu+D6c4/Zy sK3LcHy2acBY3CTV1tr9py+Ya3v5ZdkiYnM726JGJhDJ3QefKMKkpQRnev3zlkUz QRK8WlbPbWU= =OJEn -----END PGP SIGNATURE-----

1 0

proposed patch for Mexico
by Paul Eggert Feb. 10, 1996

Feb. 10, 1996

I asked on the net about Mexico's DST rule change this year; the most authoritative-sounding response I got was from Kevin Pitts, so I've included his version in the patch proposed below. Further corrections may be needed, since there seems to be some confusion about the changes; e.g. in http://mexico-travel.com/mex_eng.html, Mexico's Ministry of Tourism claims that Mexico switched to US style DST rules way back in spring 1994. =================================================================== RCS file: RCS/northamerica,v retrieving revision 1995.13 retrieving revision 1995.13.1.1 diff -c -r1995.13 -r1995.13.1.1 *** northamerica 1995/12/21 17:18:31 1995.13 --- northamerica 1996/02/10 04:40:26 1995.13.1.1 *************** *** 852,857 **** --- 852,866 ---- # Shanks also says there are four zones, but disagrees about the fourth. # Instead of GMT-6 with DST, he says there's GMT-8 without DST. + # From Paul Eggert (1996-02-07): + # Today in news:4f90v4$g6g@news.internet.com.mx, Kevin Pitts + # <bravo2(a)internet.com.mx> wrote that Mexico will use Horario de Verano (DST) + # starting this year with the same rules as the US, and gave FIDE as a source. + # (FIDE is a private organization that promotes efficient electrical use.) + # On 1996-02-02 Mario Camou wrote that the transition times are Apr Sun>=1 + # 0:00 and Nov 1 0:00 but also wrote ``The DST-out date looks a bit fishy''. + # Go with Pitts after 1996, and with Shanks before that. + # From Shanks (1991): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Mexico 1922 only - Jan 1 0:00 0 S *************** *** 863,868 **** --- 872,880 ---- Rule Mexico 1944 only - May 1 0:00 0 S Rule Mexico 1950 only - Feb 12 0:00 1:00 D Rule Mexico 1950 only - Jul 30 0:00 0 S + Rule Mexico 1996 max - Apr Sun>=1 2:00 1:00 D + Rule Mexico 1996 max - Oct lastSun 2:00 0 S + # Rule BajaN 1950 1966 - Apr lastSun 2:00 1:00 D Rule BajaN 1950 1961 - Sep lastSun 2:00 0 S Rule BajaN 1961 1966 - Oct lastSun 2:00 0 S *************** *** 883,902 **** -6:00 - CST 1942 Apr -7:00 - MST 1949 Jan 14 -8:00 - PST 1970 ! -7:00 - MST Zone America/Tijuana -7:48:04 - LMT 1922 Jan 1 0:11:56 -8:00 - PST 1927 Jun 10 23:00 -7:00 - MST 1930 Nov 16 -8:00 - PST 1942 Apr -7:00 - MST 1949 Jan 14 -8:00 BajaN P%sT 1967 Apr lastSun 2:00 ! -8:00 US P%sT Zone America/Ensenada -7:46:28 - LMT 1922 Jan 1 0:13:32 -8:00 - PST 1927 Jun 10 23:00 -7:00 - MST 1930 Nov 16 -8:00 - PST 1942 Apr -7:00 - MST 1949 Jan 14 ! -8:00 - PST # # Revillagigedo Is # no information --- 895,916 ---- -6:00 - CST 1942 Apr -7:00 - MST 1949 Jan 14 -8:00 - PST 1970 ! -7:00 Mexico M%sT Zone America/Tijuana -7:48:04 - LMT 1922 Jan 1 0:11:56 -8:00 - PST 1927 Jun 10 23:00 -7:00 - MST 1930 Nov 16 -8:00 - PST 1942 Apr -7:00 - MST 1949 Jan 14 -8:00 BajaN P%sT 1967 Apr lastSun 2:00 ! -8:00 US P%sT 1996 ! -8:00 Mexico P%sT Zone America/Ensenada -7:46:28 - LMT 1922 Jan 1 0:13:32 -8:00 - PST 1927 Jun 10 23:00 -7:00 - MST 1930 Nov 16 -8:00 - PST 1942 Apr -7:00 - MST 1949 Jan 14 ! -8:00 - PST 1996 ! -8:00 Mexico P%sT # # Revillagigedo Is # no information

1 0

DST in Mexico
by Alan.Perry＠Eng.Sun.COM Feb. 3, 1996

Feb. 3, 1996

This is what I got from our Mexico subsidiary. ------------- Begin Forwarded Message ------------- Date: Fri, 02 Feb 1996 19:38:38 -0600 From: Mario Camou - Sun Mexico Hi Alan, I finally got the info: DST-in date: 1st Sunday in April @ midnight (0:00) (bump clock 1 hour forward) DST-out date: October 31st @ midnight (24:00) (bump clock 1 hour back) TZ's affected: All of Mexico (Mexico/General, Mexico/BajaNorte and Mexico/BajaSur) The DST-out date looks a bit fishy, I'd think it more logical to put it @ the last sunday in October or something like that. However, this is the info I was able to get, and since I'm travelling to Los Angeles next week I thought it better to forward it to you now. -------------- End Forwarded Message --------------

1 0

Is Mexico starting DST back up?
by Alan.Perry＠Eng.Sun.COM Jan. 31, 1996

Jan. 31, 1996

I just got a query from our Mexico subsidiary stating that Mexico is resuming DST in April (after many years of not doing DST). This is not reflected in the current tzdata from elsie. Does anyone have any details about this? alan

1 0

Bangalore not in the same time zone as Calcutta?
by guy＠netapp.com Jan. 30, 1996

Jan. 30, 1996

This is a message that showed up in "info.sun-managers"; the only time zone I could find for India in the "tzdata96b" file was # 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 which is 5 1/2 hours from GMT, not 5 hours from GMT.... From: jerome(a)india.ti.com (Jerome Alphonse) Newsgroups: info.sun-managers Subject: date problems between Solaris and SunOS Date: 27 Jan 1996 20:06:01 -0600 Organization: UTexas Mail-to-News Gateway Message-ID: <199601270204.HAA02126(a)supernova.india.ti.com> Hello Gurus Our timezone is GMT+5. We have setup our machines in this timezone So in SunOS machines , if I give date command ,the output is Sat Jan 27 06:45:57 GMT+0500 1996 Which seems to be okay. In Solaris machines, if I give date command, the output is (though we have set it up as GMT+5,during installation) Sat Jan 27 06:45:01 GMT 1996 Becoz' of which we are not able to run certain Solaris applications which look into SUNOS or HP-UX machines for licensing as license gives error saying that time gap is more than it could handle (probably those wretched 5 hours). Becoz of this time stamp of the files created across NFS( between SUNOS and Solaris), is also crazy In Solaris machines -rw-rw-r-- 1 aravind 0 Jan 26 20:47 123 -rw-rw-r-- 1 aravind 0 Jan 26 20:47 234 In Solaris machines ,same files(across NFS) -rw-rw-r-- 1 aravind 0 Jan 27 06:47 123 -rw-rw-r-- 1 aravind 0 Jan 27 06:47 234 And also due to this time zone problem , I suspect there are some NFS mount problems which I posted in this forum a day or two before. Regards Jerome \\|// \\|// @@@@ ($$) (@@) (!!) ----o00--()--00o------o00--()--o00--------o00-()-00o------ Jerome Alphonse Email: jerome(a)india.ti.com Systems Engineer Phone: 011-91-80-2264235/9 Texas Instruments Fax : 011-91-80-2267024 Bangalore 560052 India URL : http://www.india.ti.com/~jerome/ ===========================================================

1 0