- tz - lists.iana.org

Partially translated output in timezones utils
by Vladimir Michl Jan. 18, 1999

Jan. 18, 1999

>Submitter-Id: net >Originator: Vladimir Michl >Organization: >Confidential: no >Synopsis: Partially translated output >Severity: >Priority: >Category: libc >Class: >Release: libc-2.0.109 >Environment: Host type: i586-pc-linux-gnu System: Linux trpajzlik 2.0.36 #3 Út pec 8 19:21:57 CET 1998 i586 unknown Architecture: i586 Addons: crypt linuxthreads localedata Build CFLAGS: -g -O2 Build CC: gcc Build shared: yes Build profile: yes Build omitfp: no Stdio: libio >Description: In file timezone/zdump.c on line 266 is code: (void) fprintf(stderr, _("%s: Error writing standard output "), argv[0]); (void) perror(_("standard output")); (void) exit(EXIT_FAILURE); The result of this code will be: "xxxx: Error writing standard output standard output: xxxxx" I suggest this change: (void) fprintf(stderr, _("%s: Error writing "), argv[0]); (void) perror(_("standard output")); (void) exit(EXIT_FAILURE); On line 768 of timezone/zic.c is code: return (errnum > 0 && errnum <= sys_nerr) ? sys_errlist[errnum] : "Unknown system error"; Message "Unknown system error" is not marked for translation. Please mark it. In file timezone/zic.c on line 433 in function warning(string) is: cp = ecpyalloc("warning: "); If this function is called output may be: warning: tento soubor neexistuje It is translated partially. Please, mark this message for translation. Thank you Vladimir Michl -- ********************************************************************** * Name: Vladimir Michl Student of Palacky University * * E-mail: Vladimir.Michl(a)upol.cz, MichlV(a)risc.upol.cz * * Web: http://www.inf.upol.cz/~michlv * * Address: U nove skoly 292 * * Velky Tynec * * 783 72 * * Czech Republic * **********************************************************************

1 0

changes for Nicaragua and Fiji
by Steffen Thorsen Dec. 29, 1998

Dec. 29, 1998

Dear Sirs, Nicaragua seems to be back at -6:00 but I have not been able to find when they changed from -5:00, so I have not included any patch for this change. (I got this information from a citizen in Managua. I've also tried telnet ibw.com.ni 13 which is located there, and it shows -6:00 to UTC) It seems like Fiji has started using DST now, but they provide information only for the change this year. I have tried to make a diff for australasia and had to make a new rule for "Fiji" because of the DST. Patch for Fiji is included at the end. Leo Brandewie <lbrand(a)earthlink.net> got this information from the Fiji Government: Forwarded: Here's what I got back from the Fijian Government. Note that it fails to provide general rules, and due to a nasty coincidence we cannot infer them without risk. Since Nov. 1 and Feb 28 are both Sundays, we can assume but not prove that it starts on the first Sun. in Nov. and ends on the last Sun. in Feb. Hope this helps, Leo [ Part 2: "Included Message" ] Date: Tue, 29 Dec 1998 14:20:20 +0000 From: Fiji Government <info(a)fiji.gov.fj> To: Leo Brandewie <lbrand(a)earthlink.net> Subject: Re: Daylight Savings Leo Below is a Government press release on the 5th of October on Daylight Savings. "The Minister for Labour and Industrial Relations, Mr Vincent Lobendahn declared Daylight Saving to commence on November 1st, 1998. This means that at 2am on Sunday 1 November, clocks will be put forward to 3am and at 3am on Sunday 28 February 1999, clocks will be put back to 2am. The concept of daylight saving means that extra daylight will be available at the end of each day during the daylight saving period. The advantages of of daylight saving include: more time for sport, family recreation, gardening and other outdoor activities, savings in respect of electricity, reduction in nightime road accidents, increase in economic activity, with longer daylight hours for productive work activities, benefits to tourism by making best use of available daylight. According to a spokesman from the Ministry of Labour and Industrial Relations, Sunday morning has been chosen to ensure the least disruption to work activities as only shift workers employed at that time will be affected. The spokesman said the people will have to put their clocks forward by one hour before they go to bed on Saturday 31 October, which will ensure their time is correct when they wake up on Sunday morning. The same will apply on Saturday, 27 February next year, except that people will need to put their clocks back by one hour before they go to bed. However, shift workers employed at the time that clocks are officially changed will be affected. This means that a shift worker working an eight hour night shift starting at 10pm on Saturday 31 October and finishing at 6am on Sunday, 1 November 1998 will start and finish at those times but will work only seven hours due to the change in time. However, the person will still be entitled to eight hours pay. And a person who works the same shift from 10pm on Saturday 27 February until 6am on Sunday 28 February 1999 will work nine hours due to the change in time. The person must be paid for the extra hour and if the contract of service provides for overtime to be paid after eight hours, he or she would be entitled to the overtime rate of pay for the ninth hour of work." -END- diff -u australasia.old australasia --- australasia.old Thu Sep 24 16:46:09 1998 +++ australasia Tue Dec 29 11:31:06 1998 @@ -197,9 +197,15 @@ Zone Indian/Cocos 6:30 - CCT # Cocos Islands Time # Fiji + +# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S +Rule Fiji 1998 only - Nov 1 2:00 1:00 - +Rule Fiji 1999 only - Feb 28 3:00 0:00 - + # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Pacific/Fiji 11:53:40 - LMT 1915 Oct 26 # Suva - 12:00 - FJT # Fiji Time + 12:00 - FJT 1998 Nov 1 + 12:00 Fiji FJT # Fiji Time # French Polynesia # Zone NAME GMTOFF RULES FORMAT [UNTIL]

1 0

New labels in EOP IERS/CB solutions
by IERS/CB Dec. 28, 1998

Dec. 28, 1998

Subject : Change in the labelling of the IERS/BC EOP solutions on January 1 >From D. Gambis Dear Colleagues, Please note the following labelling changes in the EOP solutions of the IERS Central Bureau: In order to avoid confusion, starting from 1 JANUARY 1999, the LABELS of IERS/BC solutions EOP(IERS) 97 C 01, 02, 03, 04 will be changed to: EOP(IERS) C 01 EOP(IERS) C 02 EOP(IERS) C 03 EOP(IERS) C 04 I hope that this will not introduce any problem in your data handling. Best Wishes to all for 1999. D. Gambis

1 0

Israel Timezone -- Dates for 1999
by Ephraim Silverberg Dec. 28, 1998

Dec. 28, 1998

Here are the dates for Israel for 1999. The main changes are starting in 1999, the Friday morning changeover to DST will take place at 2 a.m. instead of midnight and the change back will also be on a Friday morning at 2 a.m. instead of Saturday night at midnight. The following are context diffs for the file 'asia' extracted from ftp://elsie.nci.nih.gov/pub/tzdata1998i.tar.gz -----------------------------Begin Context Diff------------------------------ *** asia Thu Sep 24 16:46:09 1998 --- asia.new Mon Dec 28 12:26:31 1998 *************** *** 509,530 **** Rule Zion 1988 only - Sep 3 0:00 0 S # From Ephraim Silverberg <ephraim(a)cs.huji.ac.il> ! # (1997-03-04 and 1998-03-16): # 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 --- 509,529 ---- Rule Zion 1988 only - Sep 3 0:00 0 S # From Ephraim Silverberg <ephraim(a)cs.huji.ac.il> ! # (1997-03-04, 1998-03-16 and 1998-12-28): # According to the Office of the Secretary General of the Ministry of # Interior, there is NO set rule for Daylight-Savings/Standard time changes. ! # One thing is entrenched in law, however: that there must be at least 150 ! # days of daylight savings time annually. From 1993-1998, the change to ! # daylight savings time was on a Friday morning from midnight IST to ! # 1 a.m IDT; up until 1998, the change back to standard time was 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. Starting in 1999, the change to ! # daylight savings time will still be on a Friday morning but from ! # 2 a.m. IST to 3 a.m. IDT; furthermore, the change back to standard time ! # will now also be on a Friday morning from 2 a.m. IDT to 1 a.m. IST. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Zion 1989 only - Apr 30 0:00 1:00 D *************** *** 570,588 **** 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 - Sep 6 0:00 0 S ! # From Member of Knesset Avraham Poraz, as quoted in Ha'aretz (1998-09-02): ! # [The 1998-09-06 transition is to] serve the interests of a small minority ! # of ultra-Orthodox Sephardic Jews who, during the [Hebrew] month of Elul, ! # recite Slihot penitential prayers in the early morning hours ! # and thus find daylight time inconvenient. # From Paul Eggert (1998-01-12): ! # 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>=1 0:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 --- 569,589 ---- 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 - Sep 6 0:00 0 S + Rule Zion 1999 only - Apr 2 2:00 1:00 D + Rule Zion 1999 only - Sep 3 2:00 0 S ! # Due to imminent elections in 1999, there are no dates for the year 2000 ! # and beyond. There was a move to legislate the DST rules in Israel, but ! # due to the government's fall, it most likely won't be brought to the Knesset ! # for first reading before the elections and will probably be altered by the ! # newly elected government. # From Paul Eggert (1998-01-12): ! # Here are guesses for rules after 1999. # 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 2000 max - Mar Fri>=15 2:00 1:00 D ! Rule Zion 2000 max - Sep Fri>=1 2:00 0 S # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Jerusalem 2:20:56 - LMT 1880 ------------------------------End Context Diff------------------------------- ___________________________________________________________________________ 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

1 0

RE: Solaris mktime with multiple timezones
by Olson, Arthur David (NCI) Nov. 23, 1998

Nov. 23, 1998

I compiled the small program (bugtest.c) mentioned in the letter below using the latest elsie.nci.nih.gov source; the program ran okay. As Scott mentions, folks on the mailing list probably do need to be aware of the bug. --ado From: Scott Harrington [SMTP:seh4@ix.netcom.com] Sent: Friday, November 06, 1998 1:16 PM Subject: BUG: Solaris mktime with multiple timezones I have posted the attached message to comp.unix.solaris, so replies should probably be posted there. I wanted to notify this mailing list since the bug affects those who use multiple time zones in their programs... I have uncovered a bug in the mktime() routine found in libc.so.1 and libc.a on my SunOS 5.5.1 Generic_103640-12 sun4u sparc SUNW,Ultra-2 machine: -rw-r--r-- 1 bin bin 1155756 Jun 23 1997 /usr/lib/libc.a -rwxr-xr-x 1 bin bin 664760 Jun 23 1997 /usr/lib/libc.so.1 I have attached a small program which should determine if your system has the bug or not.

1 0

FW: symlinks in zic
by Olson, Arthur David (NCI) Nov. 17, 1998

Nov. 17, 1998

-----Original Message----- From: Mani Varadarajan [SMTP:mani@be.com] Sent: Monday, November 16, 1998 9:04 PM To: eggert(a)twinsun.com; tz(a)elsie.nci.nih.gov Subject: symlinks in zic Dear Time Zone experts, I incorporated your timezone database into the BeOS last year. The BeOS file system does not support hard links, so I had to implement symbolic link support myself. Judging from the latest version of tzcode, which I just stumbled upon today, I notice that you have done the same. I suggest a few changes to your implementation, detailed in the attached diff. The problem with how it is right now is that if zic is invoked as follows: zic -d foodir <rules files> where foodir is a relative and not an absolute path, the symbolic links in the timezone database point to bogus places. (We use relative paths in our build environment at Be during our daily builds of the BeOS.) My proposed changes fix this problem. We have used my modified version of zic for over a year now in production without any problems. Please let me know what you think of the changes. I am not on this list so please keep me on the CC list. Thanks, Mani *** zic.c.old Mon Nov 16 17:48:18 1998 --- zic.c Mon Nov 16 16:47:55 1998 *************** *** 605,616 **** if (mkdirs(toname) != 0) (void) exit(EXIT_FAILURE); result = link(fromname, toname); #if (HAVE_SYMLINK - 0) if (result != 0) { ! result = symlink(fromname, toname); if (result == 0) warning(_("hard link failed, symbolic link used")); } #endif if (result != 0) { --- 605,624 ---- if (mkdirs(toname) != 0) (void) exit(EXIT_FAILURE); + result = link(fromname, toname); #if (HAVE_SYMLINK - 0) if (result != 0) { ! char *s = (char *) tofile; ! register char * symlinkcontents = NULL; ! while ((s = strchr(s+1, '/')) != NULL) ! symlinkcontents = ecatalloc(symlinkcontents, "../"); ! symlinkcontents = ecatalloc(symlinkcontents, fromfile); ! ! result = symlink(symlinkcontents, toname); if (result == 0) warning(_("hard link failed, symbolic link used")); + ifree(symlinkcontents); } #endif if (result != 0) {

1 0

symlinks in zic
by Mani Varadarajan Nov. 17, 1998

Nov. 17, 1998

Dear Time Zone experts, I incorporated your timezone database into the BeOS last year. The BeOS file system does not support hard links, so I had to implement symbolic link support myself. Judging from the latest version of tzcode, which I just stumbled upon today, I notice that you have done the same. I suggest a few changes to your implementation, detailed in the attached diff. The problem with how it is right now is that if zic is invoked as follows: zic -d foodir <rules files> where foodir is a relative and not an absolute path, the symbolic links in the timezone database point to bogus places. (We use relative paths in our build environment at Be during our daily builds of the BeOS.) My proposed changes fix this problem. We have used my modified version of zic for over a year now in production without any problems. Please let me know what you think of the changes. I am not on this list so please keep me on the CC list. Thanks, Mani *** zic.c.old Mon Nov 16 17:48:18 1998 --- zic.c Mon Nov 16 16:47:55 1998 *************** *** 605,616 **** if (mkdirs(toname) != 0) (void) exit(EXIT_FAILURE); result = link(fromname, toname); #if (HAVE_SYMLINK - 0) if (result != 0) { ! result = symlink(fromname, toname); if (result == 0) warning(_("hard link failed, symbolic link used")); } #endif if (result != 0) { --- 605,624 ---- if (mkdirs(toname) != 0) (void) exit(EXIT_FAILURE); + result = link(fromname, toname); #if (HAVE_SYMLINK - 0) if (result != 0) { ! char *s = (char *) tofile; ! register char * symlinkcontents = NULL; ! while ((s = strchr(s+1, '/')) != NULL) ! symlinkcontents = ecatalloc(symlinkcontents, "../"); ! symlinkcontents = ecatalloc(symlinkcontents, fromfile); ! ! result = symlink(symlinkcontents, toname); if (result == 0) warning(_("hard link failed, symbolic link used")); + ifree(symlinkcontents); } #endif if (result != 0) {

1 0

FW: Asia/Ishigaki?
by Olson, Arthur David (NCI) Nov. 16, 1998

Nov. 16, 1998

-----Original Message----- From: Hideyuki Suzuki [SMTP:hideyuki@sat.t.u-tokyo.ac.jp] Sent: Monday, November 09, 1998 6:50 AM To: tz(a)elsie.nci.nih.gov Subject: Re: Asia/Ishigaki? I also examined other data concerning Japan in tzdata1998i. The patch at the bottom of this mail fixes the following points. - Only one timezone JST is used everywhere in Japan. - In tzdata1998i, the location of 'Tokyo' (+3542+13946) seems to be around the University of Tokyo. However, 'Tokyo' usually stands for the former location of Tokyo Astronomical Observatory: E 139 44' 40".90 (9h 18m 58s.727), N 35 39' 16".0. This data is from 'Rika Nenpyou (Chronological Scientific Tables) 1996' edited by National Astronomical Observatory of Japan. - JST (Japan Standard Time) has been used since Jan. 1, 1888 0:00AM (JST). The law is enacted on July 7, 1886. I couldn't understand the comment 'There is no information for Marcus.' Does anyone know what 'Marcus' is? -- hideyuki diff -u tzdata1998i/asia tzdata/asia --- tzdata1998i/asia Thu Sep 24 23:46:09 1998 +++ tzdata/asia Mon Nov 9 20:12:24 1998 @@ -610,12 +610,9 @@ # 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 +Zone Asia/Tokyo 9:18:59 - LMT 1887 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. # Jordan # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S diff -u tzdata1998i/zone.tab tzdata/zone.tab --- tzdata1998i/zone.tab Thu Sep 24 23:46:11 1998 +++ tzdata/zone.tab Mon Nov 9 19:25:10 1998 @@ -188,8 +188,7 @@ 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 +JP +3539+13944 Asia/Tokyo KE -0117+03649 Africa/Nairobi KG +4254+07436 Asia/Bishkek KH +1133+10455 Asia/Phnom_Penh

3 3

FW: Asia/Ishigaki?
by gwil＠mindspring.com Nov. 10, 1998

Nov. 10, 1998

>From: Hideyuki Suzuki [SMTP:hideyuki@sat.t.u-tokyo.ac.jp] > [...] >I couldn't understand the comment 'There is no information for Marcus.' >Does anyone know what 'Marcus' is? Marcus Island is the name used by Americans for Minami-Tori-shima. It's located at about 24 deg. 18 min. N., 153 deg. 58 min. E., which I think makes it the easternmost, as well as one of the southernmost, of the Japanese islands. It was administered by the U.S. military from the end of World War II to 1968. This background should help to explain why it's referred to by its American name, and why it might be expected to lie in a different time zone. -- Gwillim Law

1 0

FW: Asia/Ishigaki?
by Olson, Arthur David (NCI) Nov. 9, 1998

Nov. 9, 1998

-----Original Message----- From: Hideyuki Suzuki [SMTP:hideyuki@sat.t.u-tokyo.ac.jp] Sent: Saturday, November 07, 1998 11:54 AM To: tz(a)elsie.nci.nih.gov Subject: Asia/Ishigaki? In tzdata1998i.tar.gz, I found that two timezones are defined for Japan. This is somewhat strange to me, because only JST (+0900) is used everywhere in Japan including Ishigaki island. I want to suggest that Asia/Ishigaki (CST, +0800) zone should be removed. However, you may wonder why it was added to the database, and in tzarchive I found the following comment: Date: Tue, 3 Sep 1996 17:14:22 -0700 From: Paul Eggert <eggert(a)twinsun.com> Subject: proposed patch for selecting TZ, MET->CST, Sri Lanka, Antarctica,... > Asia/Ishigaki - uncomment it, since it seems to be right I don't know whether the zone was added at this time, but I suspect that it was added because of an ambiguous reason. So, I believe that it should be removed. I'm not on the tz list, so please leave my address in Cc: line when you reply. Thanks. -- hideyuki

1 0