- tz - lists.iana.org

proposed corrections for Russia, Ukraine, Bahamas
by eggert＠twinsun.com June 3, 1994

June 3, 1994

The letter from "Andy J. Chichak" <chch(a)gateway.tiasur.tomsk.su> about Tomsk prompted me to check the Russian time zone data more carefully. Unfortunately it's a mess, as Shanks was published in 1991, a year that saw chaos in Russian time zones. Though it's hard to know what the correct rules are, it _is_ clear that the rules I submitted last year to the tz database are incorrect, since I got lost with the +1hour -1hour business and ended up omitting a timezone just west of the Urals. Given Chichak's comments about being N hours away from Moscow, I decided that the most likely possibility is that Russia kept in synch with Moscow (for which we already have a detailed post-1991 update from "Andrew A. Chernov" <ache(a)astral.msk.su>). I'd guess also that Belarus followed suit, but (as described below) we know that Ukraine did not, so I'd guess the other western bits of the ex-Soviet Union stuck with EET instead of Moscow time. We have no data on Central Asia and the Caucausus, so I'd guess we should stick with the pre-1991 rules for it until we have more data. The following proposed corrections insert that missing timezone (its biggest city is Kuybyshev) and bump the remaining Russian timezones by one; this gives the proper value for Tomsk and Novosibirsk as reported by Chichak. The latest _Economist_ reports that the Crimea, as part of its attempt to break away from Ukraine, has switched from Kiev time to Moscow time, so I've proposed another timezone entry Europe/Simferopol to take this into account. Also, more people seem to be calling Macedonia ``Macedonia'' instead of the odd ``The Former Yugoslav Republic of Macedonia'' moniker that was first pasted on it, so I think we should call it by its common name. Finally, there is a minor typo in the Bahamas entry. =================================================================== RCS file: RCS/northamerica,v retrieving revision 1994.4 retrieving revision 1994.4.1.1 diff -c -r1994.4 -r1994.4.1.1 *** northamerica 1994/02/07 14:57:50 1994.4 --- northamerica 1994/05/29 04:38:57 1994.4.1.1 *************** *** 629,635 **** # Bahamas # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Bahamas 1912 max - Mar 2 0:00 0 S Rule Bahamas 1964 max - Oct lastSun 2:00 0 S Rule Bahamas 1964 1986 - Apr lastSun 2:00 1:00 D Rule Bahamas 1987 max - Apr Sun>=1 2:00 1:00 D --- 629,635 ---- # Bahamas # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S ! Rule Bahamas 1912 only - Mar 2 0:00 0 S Rule Bahamas 1964 max - Oct lastSun 2:00 0 S Rule Bahamas 1964 1986 - Apr lastSun 2:00 1:00 D Rule Bahamas 1987 max - Apr Sun>=1 2:00 1:00 D =================================================================== RCS file: RCS/asia,v retrieving revision 1994.4 retrieving revision 1994.4.1.1 diff -c -r1994.4 -r1994.4.1.1 *** asia 1994/02/07 14:57:49 1994.4 --- asia 1994/05/29 04:38:57 1994.4.1.1 *************** *** 29,39 **** # 4:00 BSK BSD Baku* # 4:00 GST GDT Gulf* # 4:30 AFT Afghanistan* ! # 5:00 TSK TSD Tashkent* # 5:00 PKT Pakistan* # 5:30 IST IST India # 5:45 NPT Nepal* # 6:00 BGT Bengal, Bangladesh* # 6:30 BMT Burma* # 7:00 ICT Indochina* # 7:00 JVT Java* --- 29,40 ---- # 4:00 BSK BSD Baku* # 4:00 GST GDT Gulf* # 4:30 AFT Afghanistan* ! # 5:00 ASK ASD Ashkhabad* # 5:00 PKT Pakistan* # 5:30 IST IST India # 5:45 NPT Nepal* # 6:00 BGT Bengal, Bangladesh* + # 6:00 TSK TSD Tashkent* # 6:30 BMT Burma* # 7:00 ICT Indochina* # 7:00 JVT Java* *************** *** 60,72 **** ############################################################################### # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule Russia 1981 1984 - Apr 1 0:00 1:00 D Rule Russia 1981 1983 - Oct 1 0:00 0 K ! Rule Russia 1984 1990 - Sep lastSun 3:00 0 K ! Rule Russia 1985 1990 - Mar lastSun 2:00 1:00 D ! Rule Russia 1992 max - Sep lastSun 2:00s 0 K ! Rule Russia 1992 max - Mar lastSun 2:00s 1:00 D # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 61,74 ---- ############################################################################### + # From Paul Eggert <eggert(a)twinsun.com> (May 28, 1994): + # We don't know what happened to the clocks in the Caucausus and the ex-Soviet + # Central Asia after 1990. Until we get more info, stick with the pre-1991 rules. # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S 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 3:00 0 K ! Rule Russia 1985 max - Mar lastSun 2:00 1:00 D # Afghanistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 78,92 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s 1991 Sep 29 3:00 ! 3:00 Russia MS%s # Azerbaijan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s 1991 Sep 29 3:00 ! 3:00 Russia MS%s # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 80,92 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Yerevan 2:58:00 - LMT 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s # Azerbaijan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Baku 3:19:24 - LMT 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s # Bahrain # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 277,284 **** Zone Asia/Tbilisi 2:59:16 - LMT 1880 2:59 - LST 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s 1991 Sep 29 3:00 ! 3:00 Russia MS%s # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 277,283 ---- Zone Asia/Tbilisi 2:59:16 - LMT 1880 2:59 - LST 1924 May 2 3:00 - MSK 1957 Mar ! 4:00 Russia BS%s # India # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 516,523 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Almaty 5:07:48 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s 1991 Sep 29 3:00 ! 5:00 Russia TS%s ############################################################################### --- 515,521 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Almaty 5:07:48 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s ############################################################################### *************** *** 565,572 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Frunze 4:58:24 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s 1991 Sep 29 3:00 ! 5:00 Russia TS%s # Laos # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 563,569 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Frunze 4:58:24 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s # Laos # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 755,762 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s 1991 Sep 29 3:00 ! 5:00 Russia TS%s # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 752,758 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Dushanbe 4:35:12 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s # Thailand # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 767,775 **** # Turkmenistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 ! 4:00 - BSK 1957 Mar ! 5:00 Russia SS%s 1991 Sep 29 3:00 ! 4:00 Russia BS%s # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 763,770 ---- # Turkmenistan # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Ashkhabad 3:53:32 - LMT 1924 May 2 ! 4:00 - ASK 1957 Mar ! 5:00 Russia AS%s # United Arab Emirates # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 780,787 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tashkent 4:37:12 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s 1991 Sep 29 3:00 ! 5:00 Russia TS%s # Vietnam # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): --- 775,781 ---- # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Asia/Tashkent 4:37:12 - LMT 1924 May 2 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s # Vietnam # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): =================================================================== RCS file: RCS/europe,v retrieving revision 1994.4 retrieving revision 1994.4.1.1 diff -c -r1994.4 -r1994.4.1.1 *** europe 1994/02/07 14:57:50 1994.4 --- europe 1994/05/29 04:38:57 1994.4.1.1 *************** *** 32,46 **** # 2:00 EET+DST Eastern Europe # 3:00 MSK MSD Moscow # 3:00 TUR+DST Turkey (no longer used)* ! # 4:00 ESK ESD Yekaterinburg* ! # 5:00 OSK OSD Omsk* ! # 6:00 NSK NSD Novosibirsk ! # 7:00 ISK ISD Irkutsk* ! # 8:00 YSK YSD Yakutsk* ! # 9:00 VSK VSD Vladivostok* ! # 10:00 GSK GSD Magadan* ! # 11:00 PSK PSD Petropavlovsk-Kamchatski* ! # 12:00 ASK ASD Anadyr* # # See the `africa' file for Zone naming conventions. # --- 32,47 ---- # 2:00 EET+DST Eastern Europe # 3:00 MSK MSD Moscow # 3:00 TUR+DST Turkey (no longer used)* ! # 4:00 KSK KSD Kuybyshev* ! # 5:00 ESK ESD Yekaterinburg* ! # 6:00 OSK OSD Omsk* ! # 7:00 NSK NSD Novosibirsk ! # 8:00 ISK ISD Irkutsk* ! # 9:00 YSK YSD Yakutsk* ! # 10:00 VSK VSD Vladivostok* ! # 11:00 GSK GSD Magadan* ! # 12:00 PSK PSD Petropavlovsk-Kamchatski* ! # 13:00 ASK ASD Anadyr* # # See the `africa' file for Zone naming conventions. # *************** *** 421,427 **** # ## <years> is either a single year or a hyphen separated range, with -- # ## also accepted as I use this in TeX a lot. # ## <start date> and <end date> are a digit followed bu a month name. ! # ## It is either an nth Saturday or an explcit date, depending on <flags>. # ## 0 and/or none are used when there is no date, as during 1968--71. # ## <flags> can contain `fixed' to indicate explicit dates and `double' # ## to indicate double summer time dates are present. --- 422,428 ---- # ## <years> is either a single year or a hyphen separated range, with -- # ## also accepted as I use this in TeX a lot. # ## <start date> and <end date> are a digit followed bu a month name. ! # ## It is either an nth Saturday or an explicit date, depending on <flags>. # ## 0 and/or none are used when there is no date, as during 1968--71. # ## <flags> can contain `fixed' to indicate explicit dates and `double' # ## to indicate double summer time dates are present. *************** *** 730,739 **** 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 1990 - Sep lastSun 2:00s 0 K ! Rule Russia 1985 1990 - Mar lastSun 2:00s 1:00 D ! Rule Russia 1992 max - Sep lastSun 2:00s 0 K ! Rule Russia 1992 max - Mar lastSun 2:00s 1:00 D # These are for backward compatibility with older versions. --- 731,738 ---- 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. *************** *** 813,820 **** 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 Sep 29 3:00 ! 2:00 Russia MS%s # Belgium # Whitman and Shanks disagree; go with Shanks, usually. --- 812,822 ---- 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 ! # From Paul Eggert <eggert(a)twinsun.com> (May 28, 1994): A guess at recent dates: ! 2:00 1:00 "EET DST" 1991 Sep 29 2:00s ! 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MS%s # Belgium # Whitman and Shanks disagree; go with Shanks, usually. *************** *** 966,973 **** 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:00 ! 2:00 M-Eur MET%s # Finland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S --- 968,976 ---- 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 # Finland # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S *************** *** 1162,1168 **** # to the julian/gregorian calendar) over the period in question. # the winter begins on the Saturday next before St. Luke's day # (old style), or on St. Luke's day, if a Saturday. ! # St. Luke's day ought to be traceable from ecclesiatical 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. --- 1165,1171 ---- # to the julian/gregorian calendar) over the period in question. # the winter begins on the Saturday next before St. Luke's day # (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. *************** *** 1260,1267 **** 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 Sep 29 3:00 ! 2:00 M-Eur MET%s # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] --- 1263,1271 ---- 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 # Liechtenstein # Zone NAME GMTOFF RULES FORMAT [UNTIL] *************** *** 1280,1287 **** 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 Sep 29 3:00 ! 2:00 M-Eur MET%s # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. --- 1284,1292 ---- 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 # Luxembourg # Whitman disagrees with most of these dates in minor ways; go with Shanks. *************** *** 1319,1325 **** 1:00 Belgium MET%s 1979 Apr 1 2:00 1:00 M-Eur MET%s ! # The Former Yugoslav Republic of 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 --- 1324,1330 ---- 1:00 Belgium MET%s 1979 Apr 1 2:00 1:00 M-Eur 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 *************** *** 1351,1358 **** # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Chisinau 1:55:20 - LMT 1924 May 2 2:00 - EET 1930 Jun 21 ! 3:00 - MSK 1981 Apr ! 3:00 Russia MS%s 1991 Sep 29 2:00s 2:00 M-Eur EET%s # Monaco --- 1356,1363 ---- # 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 # Monaco *************** *** 1435,1441 **** 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" --- 1440,1446 ---- 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" *************** *** 1574,1647 **** 2:00 M-Eur EET%s # Russia ! # From Paul Eggert <eggert(a)twinsun.com> (November 18, 1993): # 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. ! # The rest is from Shanks; it's probably wrong after 1991. ! # We're not sure whether St Petersburg switched in step with Moscow after 1991; ! # it might be a useless name, so we'll comment it out for now. # # From Shanks (1991): # Western Russia switched from the Julian to the Gregorian calendar ! # on 1918 Jan 14. Eatern 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/St_Petersburg 2:30:20 - LMT 1880 ! # 2:01 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 Sep 29 3:00 ! # 2:00 Russia SPS%s ! 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 lastSun 2:00s ! 2:00 1:00 "EET DST" 1991 Sep lastSun 2:00s ! 2:00 - EET 1992 Jan 19 2:00s ! 3:00 Russia MS%s ! Zone Asia/Yekaterinburg 4:02:34 - LMT 1924 May 2 ! 4:00 - ESK 1957 Mar ! 5:00 Russia ES%s 1991 Sep 29 3:00 ! 4:00 Russia ES%s ! Zone Asia/Omsk 4:53:36 - LMT 1924 May 2 ! 5:00 - TSK 1957 Mar ! 6:00 Russia TS%s 1991 Sep 29 3:00 ! 5:00 Russia OS%s ! Zone Asia/Novosibirsk 5:31:40 - LMT 1924 May 2 ! 6:00 - NSK 1957 Mar ! 7:00 Russia NS%s 1991 Sep 29 3:00 ! 6:00 Russia NS%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 Sep 29 3:00 ! 7: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 Sep 29 3:00 ! 8: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 Sep 29 3:00 ! 9:00 Russia VS%s # MSK is taken; settle for GSK. Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 10:00 - GSK 1957 Mar ! 11:00 Russia GS%s 1991 Sep 29 3:00 ! 10:00 Russia GS%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 Sep 29 3:00 ! 11: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 Sep 29 3:00 ! 12:00 Russia AS%s # Serbia # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. --- 1579,1669 ---- 2:00 M-Eur EET%s # 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 ! 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 ! 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 # MSK is taken; settle for GSK. Zone Asia/Magadan 10:03:12 - LMT 1924 May 2 10:00 - GSK 1957 Mar ! 11:00 Russia GS%s 1991 Mar 31 2:00s ! 10:00 1:00 GSD 1991 Sep 29 2:00s ! 10:00 - GSK 1992 Jan 19 2:00s ! 11:00 Russia GS%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 # Serbia # They switched from the Julian to the Gregorian calendar on 1918 Mar 18. *************** *** 1816,1827 **** 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 ############################################################################### --- 1838,1861 ---- 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 + 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 ###############################################################################

1 0

v28i034: strftime - strftime(3) and date(1) implementation, V6.1, Part01/01
by Monty Solomon May 12, 1994

May 12, 1994

FYI Begin forwarded message: Path: decwrl!vixie!vixie!not-for-mail From: arnold(a)skeeve.atl.ga.us (Arnold Robbins) Newsgroups: comp.sources.unix Subject: v28i034: strftime - strftime(3) and date(1) implementation, V6.1, Part01/01 Date: 11 May 1994 22:11:06 -0700 Organization: Vixie Enterprises Lines: 1303 Sender: vixie(a)vix.com Approved: vixie(a)gw.home.vix.com Nntp-Posting-Host: gw.home.vix.com To: unix-sources(a)pa.dec.com Submitted-By: arnold(a)skeeve.atl.ga.us (Arnold Robbins) Posting-Number: Volume 28, Issue 34 Archive-Name: strftime-6.1/part01 In Volume 27, Issue 207 our moderator writes: >[ this recurring package is the cleanest, nicest date(1) and strftime(3) > i have ever seen, including all free or vendor systems. --vix ] To which I can only say, "gosh, thanks!". I had written: > It seems to be an annual event, something in the circling of the stars > overhead, that requires me to post this, at least once a year. (:-) > > I sincerely hope this will be it (at least 'til next year! :-) Alas, it seems to be an annual event that shortly after posting my package, I also post bug fixes. :-) There are three main fixes here. 1) An update to the date.1 man page to reflect that POSIX.2 is not in draft any more, 2) Yet another fix to the %V code, and 3) Portability enhancements if there is no tm_zone field in the struct tm. Thanks to all who sent mail and helped me track down the ISO 8601 issues. This is strftime 6.1. The package is small enough I'm just reposting the whole thing. Arnold Robbins -- The Basement Computer | Laundry increases Internet: arnold(a)skeeve.ATL.GA.US | exponentially in the UUCP: emory!skeeve!arnold | number of children. Bitnet: Forget it. Get on a real network. | -- Miriam Robbins ------------------------- cut here ------------------------------------ #! /bin/sh echo - 'README' cat << 'EOF' > 'README' Tue May 10 21:43:29 EDT 1994 This package implements the Posix 1003.2 date command, as a wrapper around an extended version of the ANSI strftime(3) library routine. Everything in it is public domain. Arnold Robbins -- The Basement Computer | Laundry increases Internet: arnold(a)skeeve.ATL.GA.US | exponentially in the UUCP: { gatech, emory }!skeeve!arnold | number of children. Bitnet: Forget it. Get on a real network. | -- Miriam Robbins EOF echo - 'Makefile' cat << 'EOF' > 'Makefile' # Makefile for PD date and strftime SRCS= date.c strftime.c OBJS= date.o strftime.o DOCS= date.1 strftime.3 # Uncomment the define of HAVE_TZNAME if your system has the tzname[] array. # Uncomment the define of TM_IN_SYS_TIME if struct tm is in <sys/time.h>. # Uncomment the define of TM_ZONE if your struct tm has the tm_zone field. CFLAGS= -O #-DHAVE_TZNAME #-DTM_IN_SYS_TIME #-DHAVE_TM_ZONE date: $(OBJS) $(CC) $(CFLAGS) $(OBJS) -o $@ date.o: date.c strftime.o: strftime.c EOF echo - 'date.c' cat << 'EOF' > 'date.c' /* * date.c * * Public domain implementation of Posix 1003.2 * date command. Lets strftime() do the dirty work. * * Arnold Robbins * arnold(a)skeeve.atl.ga.us * April, 1991 * * Bug fix courtesy of Chris Ritson (C.R.Ritson(a)newcastle.ac.uk) * February, 1994. */ #include <stdio.h> #include <sys/types.h> #include <time.h> extern char *malloc(); extern size_t strftime(); extern int getopt(); extern int optind; int main(argc, argv) int argc; char **argv; { time_t clock; struct tm *now; int c, size, ret; char *defhow = "%a %b %e %H:%M:%S %Z %Y"; char *howto = defhow; char *buf; while ((c = getopt(argc, argv, "u")) != -1) switch (c) { case 'u': putenv("TZ=GMT0"); break; default: fprintf(stderr, "usage: %s [-u] [+format_str]\n", argv[0]); exit(1); } time(& clock); now = localtime(& clock); if (optind < argc && argv[optind][0] == '+') howto = & argv[optind][1]; size = strlen(howto) * 10; if (size < 26) size = 26; if ((buf = malloc(size)) == NULL) { perror("not enough memory"); exit(1); } ret = strftime(buf, size, howto, now); if (ret != 0) printf("%s\n", buf); else { fprintf(stderr, "conversion failed\n"); exit(1); } exit(0); } EOF echo - 'strftime.c' cat << 'EOF' > 'strftime.c' /* * strftime.c * * Public-domain implementation of ANSI C library routine. * * It's written in old-style C for maximal portability. * However, since I'm used to prototypes, I've included them too. * * If you want stuff in the System V ascftime routine, add the SYSV_EXT define. * For extensions from SunOS, add SUNOS_EXT. * For stuff needed to implement the P1003.2 date command, add POSIX2_DATE. * For VMS dates, add VMS_EXT. * For complete POSIX semantics, add POSIX_SEMANTICS. * * The code for %c, %x, and %X is my best guess as to what's "appropriate". * This version ignores LOCALE information. * It also doesn't worry about multi-byte characters. * So there. * * This file is also shipped with GAWK (GNU Awk), gawk specific bits of * code are included if GAWK is defined. * * Arnold Robbins * January, February, March, 1991 * Updated March, April 1992 * Updated April, 1993 * Updated February, 1994 * Updated May, 1994 * * Fixes from ado(a)elsie.nci.nih.gov * February 1991, May 1992 * Fixes from Tor Lillqvist tml(a)tik.vtt.fi * May, 1993 * Further fixes from ado(a)elsie.nci.nih.gov * February 1994 */ #ifndef GAWK #include <stdio.h> #include <ctype.h> #include <string.h> #include <time.h> #endif #if defined(TM_IN_SYS_TIME) || ! defined(GAWK) #include <sys/types.h> #include <sys/time.h> #endif /* defaults: season to taste */ #define SYSV_EXT 1 /* stuff in System V ascftime routine */ #define SUNOS_EXT 1 /* stuff in SunOS strftime routine */ #define POSIX2_DATE 1 /* stuff in Posix 1003.2 date command */ #define VMS_EXT 1 /* include %v for VMS date format */ #ifndef GAWK #define POSIX_SEMANTICS 1 /* call tzset() if TZ changes */ #endif #if defined(POSIX2_DATE) #if ! defined(SYSV_EXT) #define SYSV_EXT 1 #endif #if ! defined(SUNOS_EXT) #define SUNOS_EXT 1 #endif #endif #if defined(POSIX2_DATE) #define adddecl(stuff) stuff #else #define adddecl(stuff) #endif #undef strchr /* avoid AIX weirdness */ #ifndef __STDC__ #define const /**/ extern void *malloc(); extern void *realloc(); extern void tzset(); extern char *strchr(); extern char *getenv(); static int weeknumber(); adddecl(static int iso8601wknum();) #else extern void *malloc(unsigned count); extern void *realloc(void *ptr, unsigned count); extern void tzset(void); extern char *strchr(const char *str, int ch); extern char *getenv(const char *v); static int weeknumber(const struct tm *timeptr, int firstweekday); adddecl(static int iso8601wknum(const struct tm *timeptr);) #endif #ifdef __GNUC__ #define inline __inline__ #else #define inline /**/ #endif #define range(low, item, hi) max(low, min(item, hi)) #if !defined(OS2) && !defined(MSDOS) && defined(HAVE_TZNAME) extern char *tzname[2]; extern int daylight; #endif /* min --- return minimum of two numbers */ #ifndef __STDC__ static inline int min(a, b) int a, b; #else static inline int min(int a, int b) #endif { return (a < b ? a : b); } /* max --- return maximum of two numbers */ #ifndef __STDC__ static inline int max(a, b) int a, b; #else static inline int max(int a, int b) #endif { return (a > b ? a : b); } /* strftime --- produce formatted time */ #ifndef __STDC__ size_t strftime(s, maxsize, format, timeptr) char *s; size_t maxsize; const char *format; const struct tm *timeptr; #else size_t strftime(char *s, size_t maxsize, const char *format, const struct tm *timeptr) #endif { char *endp = s + maxsize; char *start = s; auto char tbuf[100]; int i; static short first = 1; #ifdef POSIX_SEMANTICS static char *savetz = NULL; static int savetzlen = 0; char *tz; #endif /* POSIX_SEMANTICS */ #ifndef HAVE_TM_ZONE extern char *timezone(); struct timeval tv; struct timezone zone; #endif /* HAVE_TM_ZONE */ /* various tables, useful in North America */ static const char *days_a[] = { "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", }; static const char *days_l[] = { "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", }; static const char *months_a[] = { "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec", }; static const char *months_l[] = { "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December", }; static const char *ampm[] = { "AM", "PM", }; if (s == NULL || format == NULL || timeptr == NULL || maxsize == 0) return 0; /* quick check if we even need to bother */ if (strchr(format, '%') == NULL && strlen(format) + 1 >= maxsize) return 0; #ifndef POSIX_SEMANTICS if (first) { tzset(); first = 0; } #else /* POSIX_SEMANTICS */ tz = getenv("TZ"); if (first) { if (tz != NULL) { int tzlen = strlen(tz); savetz = (char *) malloc(tzlen + 1); if (savetz != NULL) { savetzlen = tzlen + 1; strcpy(savetz, tz); } } tzset(); first = 0; } /* if we have a saved TZ, and it is different, recapture and reset */ if (tz && savetz && (tz[0] != savetz[0] || strcmp(tz, savetz) != 0)) { i = strlen(tz) + 1; if (i > savetzlen) { savetz = (char *) realloc(savetz, i); if (savetz) { savetzlen = i; strcpy(savetz, tz); } } else strcpy(savetz, tz); tzset(); } #endif /* POSIX_SEMANTICS */ for (; *format && s < endp - 1; format++) { tbuf[0] = '\0'; if (*format != '%') { *s++ = *format; continue; } again: switch (*++format) { case '\0': *s++ = '%'; goto out; case '%': *s++ = '%'; continue; case 'a': /* abbreviated weekday name */ if (timeptr->tm_wday < 0 || timeptr->tm_wday > 6) strcpy(tbuf, "?"); else strcpy(tbuf, days_a[timeptr->tm_wday]); break; case 'A': /* full weekday name */ if (timeptr->tm_wday < 0 || timeptr->tm_wday > 6) strcpy(tbuf, "?"); else strcpy(tbuf, days_l[timeptr->tm_wday]); break; #ifdef SYSV_EXT case 'h': /* abbreviated month name */ #endif case 'b': /* abbreviated month name */ if (timeptr->tm_mon < 0 || timeptr->tm_mon > 11) strcpy(tbuf, "?"); else strcpy(tbuf, months_a[timeptr->tm_mon]); break; case 'B': /* full month name */ if (timeptr->tm_mon < 0 || timeptr->tm_mon > 11) strcpy(tbuf, "?"); else strcpy(tbuf, months_l[timeptr->tm_mon]); break; case 'c': /* appropriate date and time representation */ sprintf(tbuf, "%s %s %2d %02d:%02d:%02d %d", days_a[range(0, timeptr->tm_wday, 6)], months_a[range(0, timeptr->tm_mon, 11)], range(1, timeptr->tm_mday, 31), range(0, timeptr->tm_hour, 23), range(0, timeptr->tm_min, 59), range(0, timeptr->tm_sec, 61), timeptr->tm_year + 1900); break; case 'd': /* day of the month, 01 - 31 */ i = range(1, timeptr->tm_mday, 31); sprintf(tbuf, "%02d", i); break; case 'H': /* hour, 24-hour clock, 00 - 23 */ i = range(0, timeptr->tm_hour, 23); sprintf(tbuf, "%02d", i); break; case 'I': /* hour, 12-hour clock, 01 - 12 */ i = range(0, timeptr->tm_hour, 23); if (i == 0) i = 12; else if (i > 12) i -= 12; sprintf(tbuf, "%02d", i); break; case 'j': /* day of the year, 001 - 366 */ sprintf(tbuf, "%03d", timeptr->tm_yday + 1); break; case 'm': /* month, 01 - 12 */ i = range(0, timeptr->tm_mon, 11); sprintf(tbuf, "%02d", i + 1); break; case 'M': /* minute, 00 - 59 */ i = range(0, timeptr->tm_min, 59); sprintf(tbuf, "%02d", i); break; case 'p': /* am or pm based on 12-hour clock */ i = range(0, timeptr->tm_hour, 23); if (i < 12) strcpy(tbuf, ampm[0]); else strcpy(tbuf, ampm[1]); break; case 'S': /* second, 00 - 61 */ i = range(0, timeptr->tm_sec, 61); sprintf(tbuf, "%02d", i); break; case 'U': /* week of year, Sunday is first day of week */ sprintf(tbuf, "%02d", weeknumber(timeptr, 0)); break; case 'w': /* weekday, Sunday == 0, 0 - 6 */ i = range(0, timeptr->tm_wday, 6); sprintf(tbuf, "%d", i); break; case 'W': /* week of year, Monday is first day of week */ sprintf(tbuf, "%02d", weeknumber(timeptr, 1)); break; case 'x': /* appropriate date representation */ sprintf(tbuf, "%s %s %2d %d", days_a[range(0, timeptr->tm_wday, 6)], months_a[range(0, timeptr->tm_mon, 11)], range(1, timeptr->tm_mday, 31), timeptr->tm_year + 1900); break; case 'X': /* appropriate time representation */ sprintf(tbuf, "%02d:%02d:%02d", range(0, timeptr->tm_hour, 23), range(0, timeptr->tm_min, 59), range(0, timeptr->tm_sec, 61)); break; case 'y': /* year without a century, 00 - 99 */ i = timeptr->tm_year % 100; sprintf(tbuf, "%02d", i); break; case 'Y': /* year with century */ sprintf(tbuf, "%d", 1900 + timeptr->tm_year); break; case 'Z': /* time zone name or abbrevation */ #ifdef HAVE_TZNAME i = (daylight && timeptr->tm_isdst); /* 0 or 1 */ strcpy(tbuf, tzname[i]); #else #ifdef HAVE_TM_ZONE strcpy(tbuf, timeptr->tm_zone); #else gettimeofday(& tv, & zone); strcpy(tbuf, timezone(zone.tz_minuteswest, timeptr->tm_isdst)); #endif #endif break; #ifdef SYSV_EXT case 'n': /* same as \n */ tbuf[0] = '\n'; tbuf[1] = '\0'; break; case 't': /* same as \t */ tbuf[0] = '\t'; tbuf[1] = '\0'; break; case 'D': /* date as %m/%d/%y */ strftime(tbuf, sizeof tbuf, "%m/%d/%y", timeptr); break; case 'e': /* day of month, blank padded */ sprintf(tbuf, "%2d", range(1, timeptr->tm_mday, 31)); break; case 'r': /* time as %I:%M:%S %p */ strftime(tbuf, sizeof tbuf, "%I:%M:%S %p", timeptr); break; case 'R': /* time as %H:%M */ strftime(tbuf, sizeof tbuf, "%H:%M", timeptr); break; case 'T': /* time as %H:%M:%S */ strftime(tbuf, sizeof tbuf, "%H:%M:%S", timeptr); break; #endif #ifdef SUNOS_EXT case 'k': /* hour, 24-hour clock, blank pad */ sprintf(tbuf, "%2d", range(0, timeptr->tm_hour, 23)); break; case 'l': /* hour, 12-hour clock, 1 - 12, blank pad */ i = range(0, timeptr->tm_hour, 23); if (i == 0) i = 12; else if (i > 12) i -= 12; sprintf(tbuf, "%2d", i); break; #endif #ifdef VMS_EXT case 'v': /* date as dd-bbb-YYYY */ sprintf(tbuf, "%02d-%3.3s-%4d", range(1, timeptr->tm_mday, 31), months_a[range(0, timeptr->tm_mon, 11)], timeptr->tm_year + 1900); for (i = 3; i < 6; i++) if (islower(tbuf[i])) tbuf[i] = toupper(tbuf[i]); break; #endif #ifdef POSIX2_DATE case 'C': sprintf(tbuf, "%02d", (timeptr->tm_year + 1900) / 100); break; case 'E': case 'O': /* POSIX locale extensions, ignored for now */ goto again; case 'V': /* week of year according ISO 8601 */ #if defined(GAWK) && defined(VMS_EXT) { extern int do_lint; extern void warning(); static int warned = 0; if (! warned && do_lint) { warned = 1; warning( "conversion %%V added in P1003.2; for VMS style date, use %%v"); } } #endif sprintf(tbuf, "%02d", iso8601wknum(timeptr)); break; case 'u': /* ISO 8601: Weekday as a decimal number [1 (Monday) - 7] */ sprintf(tbuf, "%d", timeptr->tm_wday == 0 ? 7 : timeptr->tm_wday); break; #endif /* POSIX2_DATE */ default: tbuf[0] = '%'; tbuf[1] = *format; tbuf[2] = '\0'; break; } i = strlen(tbuf); if (i) { if (s + i < endp - 1) { strcpy(s, tbuf); s += i; } else return 0; } } out: if (s < endp && *format == '\0') { *s = '\0'; return (s - start); } else return 0; } /* isleap --- is a year a leap year? */ #ifndef __STDC__ static int isleap(year) int year; #else static int isleap(int year) #endif { return ((year % 4 == 0 && year % 100 != 0) || year % 400 == 0); } #ifdef POSIX2_DATE /* iso8601wknum --- compute week number according to ISO 8601 */ #ifndef __STDC__ static int iso8601wknum(timeptr) const struct tm *timeptr; #else static int iso8601wknum(const struct tm *timeptr) #endif { /* * From 1003.2: * If the week (Monday to Sunday) containing January 1 * has four or more days in the new year, then it is week 1; * otherwise it is the highest numbered week of the previous * (52 or 53) year, and the next week is week 1. * * ADR: This means if Jan 1 was Monday through Thursday, * it was week 1, otherwise week 52 or 53. * * XPG4 erroneously included POSIX.2 rationale text in the * main body of the standard. Thus it requires week 53. */ int weeknum, jan1day, diff; /* get week number, Monday as first day of the week */ weeknum = weeknumber(timeptr, 1); /* * With thanks and tip of the hatlo to tml(a)tik.vtt.fi * * What day of the week does January 1 fall on? * We know that * (timeptr->tm_yday - jan1.tm_yday) MOD 7 == * (timeptr->tm_wday - jan1.tm_wday) MOD 7 * and that * jan1.tm_yday == 0 * and that * timeptr->tm_wday MOD 7 == timeptr->tm_wday * from which it follows that. . . */ jan1day = timeptr->tm_wday - (timeptr->tm_yday % 7); if (jan1day < 0) jan1day += 7; /* * If Jan 1 was a Monday through Thursday, it was in * week 1. Otherwise it was last year's highest week, which is * this year's week 0. * * What does that mean? * If Jan 1 was Monday, the week number is exactly right, it can * never be 0. * If it was Tuesday through Thursday, the weeknumber is one * less than it should be, so we add one. * Otherwise, Friday, Saturday or Sunday, the week number is * OK, but if it is 0, it needs to be 52 or 53. */ switch (jan1day) { case 1: /* Monday */ break; case 2: /* Tuesday */ case 3: /* Wednedsday */ case 4: /* Thursday */ weeknum++; break; case 5: /* Friday */ case 6: /* Saturday */ case 0: /* Sunday */ if (weeknum == 0) { #ifdef USE_BROKEN_XPG4 /* XPG4 (as of March 1994) says 53 unconditionally */ weeknum = 53; #else /* get week number of last week of last year */ struct tm dec31ly; /* 12/31 last year */ dec31ly = *timeptr; dec31ly.tm_year--; dec31ly.tm_mon = 11; dec31ly.tm_mday = 31; dec31ly.tm_wday = (jan1day == 0) ? 6 : jan1day - 1; dec31ly.tm_yday = 364 + isleap(dec31ly.tm_year + 1900); weeknum = iso8601wknum(& dec31ly); #endif } break; } return weeknum; } #endif /* weeknumber --- figure how many weeks into the year */ /* With thanks and tip of the hatlo to ado(a)elsie.nci.nih.gov */ #ifndef __STDC__ static int weeknumber(timeptr, firstweekday) const struct tm *timeptr; int firstweekday; #else static int weeknumber(const struct tm *timeptr, int firstweekday) #endif { int wday = timeptr->tm_wday; int ret; if (firstweekday == 1) { if (wday == 0) /* sunday */ wday = 6; else wday--; } ret = ((timeptr->tm_yday + 7 - wday) / 7); if (ret < 0) ret = 0; return ret; } #if 0 /* ADR --- I'm loathe to mess with ado's code ... */ Date: Wed, 24 Apr 91 20:54:08 MDT From: Michal Jaegermann <audfax!emory!vm.ucs.UAlberta.CA!NTOMCZAK> To: arnold(a)audiofax.com Hi Arnold, in a process of fixing of strftime() in libraries on Atari ST I grabbed some pieces of code from your own strftime. When doing that it came to mind that your weeknumber() function compiles a little bit nicer in the following form: /* * firstweekday is 0 if starting in Sunday, non-zero if in Monday */ { return (timeptr->tm_yday - timeptr->tm_wday + (firstweekday ? (timeptr->tm_wday ? 8 : 1) : 7)) / 7; } How nicer it depends on a compiler, of course, but always a tiny bit. Cheers, Michal ntomczak(a)vm.ucs.ualberta.ca #endif #ifdef TEST_STRFTIME /* * NAME: * tst * * SYNOPSIS: * tst * * DESCRIPTION: * "tst" is a test driver for the function "strftime". * * OPTIONS: * None. * * AUTHOR: * Karl Vogel * Control Data Systems, Inc. * vogelke(a)c-17igp.wpafb.af.mil * * BUGS: * None noticed yet. * * COMPILE: * cc -o tst -DTEST_STRFTIME strftime.c */ /* ADR: I reformatted this to my liking, and deleted some unneeded code. */ #ifndef NULL #include <stdio.h> #endif #include <sys/time.h> #include <string.h> #define MAXTIME 132 /* * Array of time formats. */ static char *array[] = { "(%%A) full weekday name, var length (Sunday..Saturday) %A", "(%%B) full month name, var length (January..December) %B", "(%%C) Century %C", "(%%D) date (%%m/%%d/%%y) %D", "(%%E) Locale extensions (ignored) %E", "(%%H) hour (24-hour clock, 00..23) %H", "(%%I) hour (12-hour clock, 01..12) %I", "(%%M) minute (00..59) %M", "(%%O) Locale extensions (ignored) %O", "(%%R) time, 24-hour (%%H:%%M) %R", "(%%S) second (00..61) %S", "(%%T) time, 24-hour (%%H:%%M:%%S) %T", "(%%U) week of year, Sunday as first day of week (00..53) %U", "(%%V) week of year according to ISO 8601 %V", "(%%W) week of year, Monday as first day of week (00..53) %W", "(%%X) appropriate locale time representation (%H:%M:%S) %X", "(%%Y) year with century (1970...) %Y", "(%%Z) timezone (EDT), or blank if timezone not determinable %Z", "(%%a) locale's abbreviated weekday name (Sun..Sat) %a", "(%%b) locale's abbreviated month name (Jan..Dec) %b", "(%%c) full date (Sat Nov 4 12:02:33 1989)%n%t%t%t %c", "(%%d) day of the month (01..31) %d", "(%%e) day of the month, blank-padded ( 1..31) %e", "(%%h) should be same as (%%b) %h", "(%%j) day of the year (001..366) %j", "(%%k) hour, 24-hour clock, blank pad ( 0..23) %k", "(%%l) hour, 12-hour clock, blank pad ( 0..12) %l", "(%%m) month (01..12) %m", "(%%p) locale's AM or PM based on 12-hour clock %p", "(%%r) time, 12-hour (same as %%I:%%M:%%S %%p) %r", "(%%u) ISO 8601: Weekday as decimal number [1 (Monday) - 7] %u", "(%%v) VAX date (dd-bbb-YYYY) %v", "(%%w) day of week (0..6, Sunday == 0) %w", "(%%x) appropriate locale date representation %x", "(%%y) last two digits of year (00..99) %y", (char *) NULL }; /* main routine. */ int main(argc, argv) int argc; char **argv; { long time(); char *next; char string[MAXTIME]; int k; int length; struct tm *tm; long clock; /* Call the function. */ clock = time((long *) 0); tm = localtime(&clock); for (k = 0; next = array[k]; k++) { length = strftime(string, MAXTIME, next, tm); printf("%s\n", string); } exit(0); } #endif /* TEST_STRFTIME */ EOF echo - 'date.1' cat << 'EOF' > 'date.1' .TH DATE 1 .SH NAME date \- write the date and time .SH SYNOPSIS .B date [ .B \-u ] [ .RI + format ] .SH DESCRIPTION .I Date writes the current date and time to the standard output. It is intended to be compliant with the Posix 1003.2 Command Language and Utilities standard. Therefore, it is purposely .I not usable by the super-user for setting the system time. .LP .I Date accepts one option: .TP .B \-u Perform operations as if the .B TZ environment variable was set to .BR GMT0 . .LP If an argument to .I date is given that begins with a ``+'', then the output is controlled by the contents of the rest of the string. Normal text is output unmodified, while field descriptors in the format string are substituted for. .LP The .I date program is essentially a wrapper around .IR strftime (3); see there for a description of the available formatting options. .LP If no format string is given, or if it does not begin with a ``+'', then the default format of \fB"%a %b %e %H:%M:%S %Z %Y"\fR will be used. This produces the traditional style of output, such as ``Sun Mar 17 10:32:47 EST 1991''. .SH SEE ALSO time(2), strftime(3), localtime(3) .SH BUGS This version only works for the POSIX locale. .SH AUTHOR .nf Arnold Robbins .sp INTERNET: arnold(a)skeeve.atl.ga.us UUCP: emory!skeeve!arnold Phone: +1 404 248 9324 .fi EOF echo - 'strftime.3' cat << 'EOF' > 'strftime.3' .TH STRFTIME 3 .SH NAME strftime \- generate formatted time information .SH SYNOPSIS .ft B .nf #include <sys/types.h> #include <time.h> .sp size_t strftime(char *s, size_t maxsize, const char *format, const struct tm *timeptr); .SH DESCRIPTION The following description is transcribed verbatim from the December 7, 1988 draft standard for ANSI C. This draft is essentially identical in technical content to the final version of the standard. .LP The .B strftime function places characters into the array pointed to by .B s as controlled by the string pointed to by .BR format . The format shall be a multibyte character sequence, beginning and ending in its initial shift state. The .B format string consists of zero or more conversion specifiers and ordinary multibyte characters. A conversion specifier consists of a .B % character followed by a character that determines the behavior of the conversion specifier. All ordinary multibyte characters (including the terminating null character) are copied unchanged into the array. If copying takes place between objects that overlap the behavior is undefined. No more than .B maxsize characters are placed into the array. Each conversion specifier is replaced by appropriate characters as described in the following list. The appropriate characters are determined by the .B LC_TIME category of the current locale and by the values contained in the structure pointed to by .BR timeptr . .TP .B %a is replaced by the locale's abbreviated weekday name. .TP .B %A is replaced by the locale's full weekday name. .TP .B %b is replaced by the locale's abbreviated month name. .TP .B %B is replaced by the locale's full month name. .TP .B %c is replaced by the locale's appropriate date and time representation. .TP .B %d is replaced by the day of the month as a decimal number .RB ( 01 - 31 ). .TP .B %H is replaced by the hour (24-hour clock) as a decimal number .RB ( 00 - 23 ). .TP .B %I is replaced by the hour (12-hour clock) as a decimal number .RB ( 01 - 12 ). .TP .B %j is replaced by the day of the year as a decimal number .RB ( 001 - 366 ). .TP .B %m is replaced by the month as a decimal number .RB ( 01 - 12 ). .TP .B %M is replaced by the minute as a decimal number .RB ( 00 - 59 ). .TP .B %p is replaced by the locale's equivalent of the AM/PM designations associated with a 12-hour clock. .TP .B %S is replaced by the second as a decimal number .RB ( 00 - 61 ). .TP .B %U is replaced by the week number of the year (the first Sunday as the first day of week 1) as a decimal number .RB ( 00 - 53 ). .TP .B %w is replaced by the weekday as a decimal number .RB [ "0 " (Sunday)- 6 ]. .TP .B %W is replaced by the week number of the year (the first Monday as the first day of week 1) as a decimal number .RB ( 00 - 53 ). .TP .B %x is replaced by the locale's appropriate date representation. .TP .B %X is replaced by the locale's appropriate time representation. .TP .B %y is replaced by the year without century as a decimal number .RB ( 00 - 99 ). .TP .B %Y is replaced by the year with century as a decimal number. .TP .B %Z is replaced by the time zone name or abbreviation, or by no characters if no time zone is determinable. .TP .B %% is replaced by .BR % . .LP If a conversion specifier is not one of the above, the behavior is undefined. .SH RETURNS If the total number of resulting characters including the terminating null character is not more than .BR maxsize , the .B strftime function returns the number of characters placed into the array pointed to by .B s not including the terminating null character. Otherwise, zero is returned and the contents of the array are indeterminate. .SH NON-ANSI EXTENSIONS If .B SYSV_EXT is defined when the routine is compiled, then the following additional conversions will be available. These are borrowed from the System V .IR cftime (3) and .IR ascftime (3) routines. .TP .B %D is equivalent to specifying .BR %m/%d/%y . .TP .B %e is replaced by the day of the month, padded with a blank if it is only one digit. .TP .B %h is equivalent to .BR %b , above. .TP .B %n is replaced with a newline character (\s-1ASCII LF\s+1). .TP .B %r is equivalent to specifying .BR "%I:%M:%S %p" . .TP .B %R is equivalent to specifying .BR %H:%M . .TP .B %T is equivalent to specifying .BR %H:%M:%S . .TP .B %t is replaced with a \s-1TAB\s+1 character. .PP If .B SUNOS_EXT is defined when the routine is compiled, then the following additional conversions will be available. These are borrowed from the SunOS version of .IR strftime . .TP .B %k is replaced by the hour (24-hour clock) as a decimal number .RB ( 0 - 23 ). Single digit numbers are padded with a blank. .TP .B %l is replaced by the hour (12-hour clock) as a decimal number .RB ( 1 - 12 ). Single digit numbers are padded with a blank. .SH POSIX 1003.2 EXTENSIONS If .B POSIX2_DATE is defined, then all of the conversions available with .B SYSV_EXT and .B SUNOS_EXT are available, as well as the following additional conversions: .TP .B %C The century, as a number between 00 and 99. .TP .B %u is replaced by the weekday as a decimal number .RB [ "1 " (Monday)- 7 ]. .TP .B %V is replaced by the week number of the year (the first Monday as the first day of week 1) as a decimal number .RB ( 01 - 53 ). The method for determining the week number is as specified by ISO 8601 (to wit: if the week containing January 1 has four or more days in the new year, then it is week 1, otherwise it is the highest numbered week of the previous year (52 or 53) and the next week is week 1). .LP The text of the POSIX standard for the .I date utility describes .B %U and .B %W this way: .TP .B %U is replaced by the week number of the year (the first Sunday as the first day of week 1) as a decimal number .RB ( 00 - 53 ). All days in a new year preceding the first Sunday are considered to be in week 0. .TP .B %W is replaced by the week number of the year (the first Monday as the first day of week 1) as a decimal number .RB ( 00 - 53 ). All days in a new year preceding the first Monday are considered to be in week 0. .LP In addition, the alternate representations .BR %Ec , .BR %EC , .BR %Ex , .BR %Ey , .BR %EY , .BR %Od , .BR %Oe , .BR %OH , .BR %OI , .BR %Om , .BR %OM , .BR %OS , .BR %Ou , .BR %OU , .BR %OV , .BR %Ow , .BR %OW , and .B %Oy are recognized, but their normal representations are used. .SH VMS EXTENSIONS If .B VMS_EXT is defined, then the following additional conversion is available: .TP .B %v The date in VMS format (e.g. 20-JUN-1991). .SH SEE ALSO .IR time (2), .IR ctime (3), .IR localtime (3), .IR tzset (3) .SH BUGS This version does not handle multibyte characters or pay attention to the setting of the .B LC_TIME environment variable. .LP It is not clear what is ``appropriate'' for the C locale; the values returned are a best guess on the author's part. .SH CAVEATS The pre-processor symbol .B POSIX_SEMANTICS is automatically defined, which forces the code to call .IR tzset (3) whenever the .B TZ environment variable has changed. If this routine will be used in an application that will not be changing .BR TZ , then there may be some performance improvements by not defining .BR POSIX_SEMANTICS . .SH AUTHOR .nf Arnold Robbins .sp INTERNET: arnold(a)skeeve.atl.ga.us UUCP: emory!skeeve!arnold Phone: +1 404 248 9324 .fi .SH ACKNOWLEDGEMENTS Thanks to Geoff Clare <gwc(a)root.co.uk> for helping debug earlier versions of this routine, and for advice about POSIX semantics. Additional thanks to Arthur David Olsen <ado(a)elsie.nci.nih.gov> for some code improvements. Thanks also to Tor Lillqvist <tml(a)tik.vtt.fi> for code fixes to the ISO 8601 code. EOF

1 0

Re: workaround for common programming error involving ctime and localtime
by ado May 11, 1994

May 11, 1994

> ! /* > ! ** The following is equivalent to `return asctime(localtime(timep));', > ! ** except it does not modify localtime's static storage, > ! ** and thus it works around all-too-common bugs like > ! ** `struct tm *p = localtime(&t1); puts(ctime(&t2)); return p->tm_year'. > ! */ Hmmm...given the X3J11 description of ctime in section 4.12.3.2... The ctime funciton converts the calendar time pointed to by timer to local time in the form of a string. It is equivalent to asctime(localtime(timer)) ...do we open ourselves up to standard conformance challenges if ctime is anything except "asctime(localtime(timer))"? --ado

2 1

support for ICL extension to Posix TZ string parsing
by yata!eggert＠twinsun.com May 8, 1994

May 8, 1994

The following Usenet article describes a extension to Posix TZ strings that allows the strings to express the daylight savings time rules currently used in Britain. At the end of this message is a patch to the tz package that adds support for this extension. This patch also fixes a theoretical leap second problem with Posix TZ strings. But looking at the code, I suspect that leap seconds don't work at all with Posix TZ strings; perhaps this is intentional? Newsgroups: comp.unix.unixware From: jjf(a)dsbc.icl.co.uk (J J Farrell) Subject: Re: Daylight saving time in UW1.1 Message-ID: <CpCvnG.7Dy(a)dsbc.icl.co.uk> Organization: International Computers Limited References: <767043120.AA04204(a)cswamp.apana.org.au> <Cp9x6n.7uB(a)novell.co.uk> Date: Fri, 6 May 1994 00:50:03 GMT In article <Cp9x6n.7uB(a)novell.co.uk> msohnius(a)novell.co.uk (Martin Sohnius) writes: > UnixWare supports two different styles of timezone handling. > > One is what I may call "System V" style, with the TZ environment > variable as described in environ(5). It might be better described as "Standard" style - it's been specified by X/Open for many years, and I think Posix is the same. > Note also that the October rule for many parts of Australia > ("next-to-last Sunday in October") cannot be implemented with the > "System V" style TZ. (NB nor can the British rule, > "day after 4th Saturday in October"). I'm not sure about the Australian ones, but the British rule can be done in "System V" style TZ. The following works on SVR4 systems and has been issued by ICL for several years: GMT0BST,M3.5.0/1,M10.4.6/26 I've not looked up the wording in the SVR4 documentation, but this does break the wording in XPG3; they may have loosened the wording in XPG4, but I haven't checked. It is probably a bug that this works, but bugs can sometimes be useful! My opinions; I do not speak for my employer. =================================================================== RCS file: RCS/localtime.c,v retrieving revision 1994.6.1.2 retrieving revision 1994.6.1.3 diff -c -r1994.6.1.2 -r1994.6.1.3 *** localtime.c 1994/05/09 10:16:11 1994.6.1.2 --- localtime.c 1994/05/09 10:22:51 1994.6.1.3 *************** *** 414,423 **** { int num; ! strp = getnum(strp, &num, 0, HOURSPERDAY); if (strp == NULL) return NULL; ! *secsp = num * SECSPERHOUR; if (*strp == ':') { ++strp; strp = getnum(strp, &num, 0, MINSPERHOUR - 1); --- 414,429 ---- { int num; ! /* ! ** `HOURSPERDAY * DAYSPERWEEK - 1' allows quasi-Posix rules like ! ** "M10.4.6/26", which does not conform to Posix, ! ** but which specifies the equivalent of ! ** ``02:00 on the first Sunday on or after 23 Oct''. ! */ ! strp = getnum(strp, &num, 0, HOURSPERDAY * DAYSPERWEEK - 1); if (strp == NULL) return NULL; ! *secsp = num * (long) SECSPERHOUR; if (*strp == ':') { ++strp; strp = getnum(strp, &num, 0, MINSPERHOUR - 1); *************** *** 426,432 **** *secsp += num * SECSPERMIN; if (*strp == ':') { ++strp; ! strp = getnum(strp, &num, 0, SECSPERMIN - 1); if (strp == NULL) return NULL; *secsp += num; --- 432,439 ---- *secsp += num * SECSPERMIN; if (*strp == ':') { ++strp; ! /* `SECSPERMIN' allows for leap seconds. */ ! strp = getnum(strp, &num, 0, SECSPERMIN); if (strp == NULL) return NULL; *secsp += num;

1 0

workaround for common programming error involving ctime and localtime
by yata!eggert＠twinsun.com May 8, 1994

May 8, 1994

The following patch lets the tz package work around a common programming error when using ctime and localtime. =================================================================== RCS file: RCS/localtime.c,v retrieving revision 1994.6.1.1 retrieving revision 1994.6.1.2 diff -c -r1994.6.1.1 -r1994.6.1.2 *** localtime.c 1994/05/05 16:24:49 1994.6.1.1 --- localtime.c 1994/05/09 10:16:11 1994.6.1.2 *************** *** 1136,1142 **** ctime(timep) const time_t * const timep; { ! return asctime(localtime(timep)); } /* --- 1136,1151 ---- ctime(timep) const time_t * const timep; { ! struct tm tm; ! ! /* ! ** The following is equivalent to `return asctime(localtime(timep));', ! ** except it does not modify localtime's static storage, ! ** and thus it works around all-too-common bugs like ! ** `struct tm *p = localtime(&t1); puts(ctime(&t2)); return p->tm_year'. ! */ ! localsub(timep, 0L, &tm); ! return asctime(&tm); } /*

1 0

support for locales
by yata!eggert＠twinsun.com May 8, 1994

May 8, 1994

Here is a patch that adds support for locales to the tz package's strftime function and date command. For example, if the LC_TIME environment variable is set to "de", `date' will output something like `Montag, 9. Mai 1994, 02:59:54 Uhr PDT' instead of the usual `Mon May 9 02:59:54 PDT 1994'. The locale files are in /usr/lib/locale, using the same format as in Solaris 2.3 (which I assume is fairly standard, at least among SVR4-ish hosts). If locale files are absent or are not of the proper form, traditional behavior is assumed. I invented a strftime format `%+', which expands to the default format used by `date'; this makes it easier to put all the locale-relevant stuff in strftime.c, and also lets the user type fun commands like `date "+|%+|"'. This patch also extends strftime to use the format "%c" if its format argument is (char*)0; this is the documented behavior in Solaris 2.3. This patch assumes the Posix/GCC cleanup patch I sent a while back. =================================================================== RCS file: RCS/Makefile,v retrieving revision 1994.7.1.1 retrieving revision 1994.7.1.2 diff -c -r1994.7.1.1 -r1994.7.1.2 *** Makefile 1994/05/05 19:10:21 1994.7.1.1 --- Makefile 1994/05/09 09:47:26 1994.7.1.2 *************** *** 82,87 **** --- 82,88 ---- # -DHAVE_ADJTIME=0 if `adjtime' does not exist (SVR0?) # -DHAVE_LONG_DOUBLE if your compiler supports the `long double' type # -DHAVE_MKDIR=0 if the mkdir system call does not work (SVR0?) + # -DHAVE_SETLOCALE=0 if the setlocale function does not work (SVR3) # -DHAVE_SETTIMEOFDAY=0 if settimeofday does not exist (SVR0?) # -DHAVE_SETTIMEOFDAY=1 if settimeofday has just 1 arg (SVR4) # -DHAVE_SETTIMEOFDAY=2 if settimeofday uses 2nd arg (4.3BSD) *************** *** 89,94 **** --- 90,96 ---- # -DHAVE_STDLIB_H=0 if `#include <stdlib.h>' does not work # -DHAVE_UMASK=0 if `umask(0)' does not work # -DHAVE_UNISTD=0 if `#include <unistd.h>' does not work + # -DLOCALE_HOME=\"path\" if locales are in "path", not "/usr/lib/locale" # -DNEED_STRCHR_DECL=1 if <string.h> does not declare strchr fully # -DNEED_TIME_DECL=1 if <time.h> does not declare `time' fully # -Dalloc_size_t=T if the malloc size argument is of type T, not size_t =================================================================== RCS file: RCS/date.1,v retrieving revision 1994.7 retrieving revision 1994.7.1.1 diff -c -r1994.7 -r1994.7.1.1 *** date.1 1992/11/04 18:08:06 1994.7 --- date.1 1994/05/09 09:47:50 1994.7.1.1 *************** *** 37,42 **** --- 37,43 ---- (or by the abbreviation for the time zone specified in the .B TZ environment variable if set). + The exact output format depends on the locale. .PP If a command-line argument starts with a plus sign .RB (` + '), *************** *** 51,70 **** to be output in a particular way (or identify a special character to output): .nf .if t .in +.5i .if n .in +2 ! .ta \w'%M\0\0'u +\w'Wed Mar 8 14:54:40 1989\0\0'u Sample output Explanation ! %a Wed Abbreviated weekday name ! %A Wednesday Full weekday name ! %b Mar Abbreviated month name ! %B March Full month name ! %c 03/08/89 14:54:40 Month/day/year Hour:minute:second ! %C Wed Mar 8 14:54:40 1989 a la \fIasctime\^\fP(3) %d 08 Day of month (always two digits) %D 03/08/89 Month/day/year (eight characters) %e 8 Day of month (leading zero blanked) ! %h Mar Abbreviated month name %H 14 24-hour-clock hour (two digits) %I 02 12-hour-clock hour (two digits) %j 067 Julian day number (three digits) --- 52,72 ---- to be output in a particular way (or identify a special character to output): .nf + .sp .if t .in +.5i .if n .in +2 ! .ta \w'%M\0\0'u +\w'Wed Mar 8 14:54:40 EST 1989\0\0'u Sample output Explanation ! %a Wed Abbreviated weekday name* ! %A Wednesday Full weekday name* ! %b Mar Abbreviated month name* ! %B March Full month name* ! %c Wed Mar 08 14:54:40 1989 Date and time* ! %C 19 Century %d 08 Day of month (always two digits) %D 03/08/89 Month/day/year (eight characters) %e 8 Day of month (leading zero blanked) ! %h Mar Abbreviated month name* %H 14 24-hour-clock hour (two digits) %I 02 12-hour-clock hour (two digits) %j 067 Julian day number (three digits) *************** *** 82,94 **** %U 10 Sunday-based week number (two digits) %w 3 Day number (one digit, Sunday is 0) %W 10 Monday-based week number (two digits) ! %x 03/08/89 Month/day/year (eight characters) ! %X 14:54:40 Hour:minute:second %y 89 Last two digits of year %Y 1989 Year in full %Z EST Time zone abbreviation .if t .in -.5i .if n .in -2 .fi If a character other than one of those shown above appears after a percent sign in the format, --- 84,99 ---- %U 10 Sunday-based week number (two digits) %w 3 Day number (one digit, Sunday is 0) %W 10 Monday-based week number (two digits) ! %x 03/08/89 Date* ! %X 14:54:40 Time* %y 89 Last two digits of year %Y 1989 Year in full %Z EST Time zone abbreviation + %+ Wed Mar 8 14:54:40 EST 1989 Default output format* .if t .in -.5i .if n .in -2 + * The exact output depends on the locale. + .sp .fi If a character other than one of those shown above appears after a percent sign in the format, *************** *** 150,153 **** --- 155,175 ---- On BSD-based systems, the adjustment is made by changing the rate at which time advances; on System-V-based systems, the adjustment is made by changing the time. + .SH FILES + .ta \w'/usr/local/etc/zoneinfo/posixrules\0\0'u + /usr/lib/locale/\f2L\fP/LC_TIME description of time locale \f2L\fP + .br + /usr/local/etc/zoneinfo time zone information directory + .br + /usr/local/etc/zoneinfo/localtime local time zone file + .br + /usr/local/etc/zoneinfo/posixrules used with POSIX-style TZ's + .br + /usr/local/etc/zoneinfo/GMT for UTC leap seconds + .sp + If + .B /usr/local/etc/zoneinfo/GMT + is absent, + UTC leap seconds are loaded from + .BR /usr/local/etc/zoneinfo/posixrules . .\" @(#)date.1 7.2 =================================================================== RCS file: RCS/date.c,v retrieving revision 1994.6.1.1 retrieving revision 1994.6.1.2 diff -c -r1994.6.1.1 -r1994.6.1.2 *** date.c 1994/05/05 16:24:49 1994.6.1.1 --- date.c 1994/05/09 09:47:28 1994.6.1.2 *************** *** 40,45 **** --- 40,49 ---- #endif #include "utmp.h" /* for OLD_TIME (or its absence) */ + #if HAVE_SETLOCALE + # include "locale.h" + #endif + /* ** The two things date knows about time are. . . */ *************** *** 485,495 **** (void) time(&now); tm = *localtime(&now); ! if (format == NULL) { ! timeout(stdout, "%a %b ", &tm); ! (void) printf("%2d ", tm.tm_mday); ! timeout(stdout, "%X %Z %Y", &tm); ! } else timeout(stdout, format, &tm); (void) putchar('\n'); (void) fflush(stdout); (void) fflush(stderr); --- 489,498 ---- (void) time(&now); tm = *localtime(&now); ! #if HAVE_SETLOCALE ! setlocale(LC_TIME, ""); ! #endif ! timeout(stdout, format ? format : "%+", &tm); (void) putchar('\n'); (void) fflush(stdout); (void) fflush(stderr); =================================================================== RCS file: RCS/private.h,v retrieving revision 1994.5.1.1 retrieving revision 1994.5.1.2 diff -c -r1994.5.1.1 -r1994.5.1.2 *** private.h 1994/04/03 02:54:41 1994.5.1.1 --- private.h 1994/05/09 09:47:28 1994.5.1.2 *************** *** 30,35 **** --- 30,38 ---- #ifndef HAVE_MKDIR #define HAVE_MKDIR 1 #endif + #ifndef HAVE_SETLOCALE + #define HAVE_SETLOCALE 1 + #endif #ifndef HAVE_SETTIMEOFDAY #define HAVE_SETTIMEOFDAY 3 #endif *************** *** 48,53 **** --- 51,60 ---- #endif #ifndef NEED_TIME_DECL #define NEED_TIME_DECL 0 + #endif + + #ifndef LOCALE_HOME + #define LOCALE_HOME "/usr/lib/locale" #endif /* =================================================================== RCS file: RCS/strftime.c,v retrieving revision 1994.6 retrieving revision 1994.6.1.1 diff -c -r1994.6 -r1994.6.1.1 *** strftime.c 1994/05/05 15:47:58 1994.6 --- strftime.c 1994/05/09 09:48:02 1994.6.1.1 *************** *** 3,10 **** static char elsieid[] = "@(#)strftime.c 7.19"; /* ** Based on the UCB version with the ID appearing below. ! ** This is ANSIish only when time is treated identically in all locales and ! ** when "multibyte character == plain character". */ #endif /* !defined NOID */ #endif /* !defined lint */ --- 3,9 ---- static char elsieid[] = "@(#)strftime.c 7.19"; /* ** Based on the UCB version with the ID appearing below. ! ** This is ANSIish only when "multibyte character == plain character". */ #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 35,60 **** #endif /* !defined LIBC_SCCS */ #include "tzfile.h" ! static const char afmt[][4] = { ! "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat" }; ! static const char Afmt[][10] = { ! "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", ! "Saturday" ! }; ! static const char bfmt[][4] = { ! "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", ! "Oct", "Nov", "Dec" ! }; ! static const char Bfmt[][10] = { ! "January", "February", "March", "April", "May", "June", "July", ! "August", "September", "October", "November", "December" }; static char *_add P((const char *, char *, const char *)); static char *_conv P((int, const char *, char *, const char *)); ! static char *_fmt P((const char *, const struct tm *, char *, const char *)); size_t strftime P((char *, size_t, const char *, const struct tm *)); --- 34,98 ---- #endif /* !defined LIBC_SCCS */ #include "tzfile.h" + #include "fcntl.h" ! struct lc_time { ! const char *mon[12]; ! const char *month[12]; ! const char *wday[7]; ! const char *weekday[7]; ! const char *X_fmt; ! const char *x_fmt; ! const char *c_fmt; ! const char *am; ! const char *pm; ! const char *date_fmt; }; ! ! static const struct lc_time C_time_locale = { ! { ! "Jan", "Feb", "Mar", "Apr", "May", "Jun", ! "Jul", "Aug", "Sep", "Oct", "Nov", "Dec" ! }, { ! "January", "February", "March", "April", "May", "June", ! "July", "August", "September", "October", "November", "December" ! }, { ! "Sun", "Mon", "Tue", "Wed", ! "Thu", "Fri", "Sat" ! }, { ! "Sunday", "Monday", "Tuesday", "Wednesday", ! "Thursday", "Friday", "Saturday" ! }, ! ! /* X_fmt */ ! "%H:%M:%S", ! ! /* ! ** x_fmt ! ** Since the C language standard calls for ! ** "date, using locale's date format," anything goes. ! ** Using just numbers (as here) makes Quakers happier; ! ** it's also compatible with SVR4. ! */ ! "%m/%d/%y", ! ! /* c_fmt */ ! "%a %b %d %H:%M:%S %Y", ! ! "AM", "PM", ! ! /* date_fmt */ ! "%a %b %e %H:%M:%S %Z %Y" }; + #if HAVE_SETLOCALE + # include <locale.h> + #endif + static char *_add P((const char *, char *, const char *)); static char *_conv P((int, const char *, char *, const char *)); ! static char *_fmt P((const char *, const struct tm *, char *, const char *, struct lc_time *)); ! static const struct lc_time *_loc P((struct lc_time *)); size_t strftime P((char *, size_t, const char *, const struct tm *)); *************** *** 68,75 **** const struct tm *t; { char *p; ! p = _fmt(format, t, s, s + maxsize); if (p == s + maxsize) return 0; *p = '\0'; --- 106,117 ---- const struct tm *t; { char *p; + struct lc_time localebuf; ! if (!format) ! format = "%c"; ! localebuf.mon[0] = 0; ! p = _fmt(format, t, s, s + maxsize, &localebuf); if (p == s + maxsize) return 0; *p = '\0'; *************** *** 77,87 **** } static char * ! _fmt(format, t, pt, ptlim) const char *format; const struct tm *t; char *pt; const char *ptlim; { for (; *format; ++format) { if (*format == '%') { --- 119,130 ---- } static char * ! _fmt(format, t, pt, ptlim, locale) const char *format; const struct tm *t; char *pt; const char *ptlim; + struct lc_time *locale; { for (; *format; ++format) { if (*format == '%') { *************** *** 90,114 **** case '\0': --format; break; case 'A': pt = _add((t->tm_wday < 0 || t->tm_wday > 6) ? ! "?" : Afmt[t->tm_wday], pt, ptlim); continue; case 'a': pt = _add((t->tm_wday < 0 || t->tm_wday > 6) ? ! "?" : afmt[t->tm_wday], pt, ptlim); continue; case 'B': pt = _add((t->tm_mon < 0 || t->tm_mon > 11) ? ! "?" : Bfmt[t->tm_mon], pt, ptlim); continue; case 'b': case 'h': pt = _add((t->tm_mon < 0 || t->tm_mon > 11) ? ! "?" : bfmt[t->tm_mon], pt, ptlim); continue; case 'c': ! pt = _fmt("%D %X", t, pt, ptlim); continue; case 'C': /* --- 133,166 ---- case '\0': --format; break; + case '+': + pt = _fmt(_loc(locale)->date_fmt, t, + pt, ptlim, locale); + continue; case 'A': pt = _add((t->tm_wday < 0 || t->tm_wday > 6) ? ! "?" : _loc(locale)->weekday[t->tm_wday], ! pt, ptlim); continue; case 'a': pt = _add((t->tm_wday < 0 || t->tm_wday > 6) ? ! "?" : _loc(locale)->wday[t->tm_wday], ! pt, ptlim); continue; case 'B': pt = _add((t->tm_mon < 0 || t->tm_mon > 11) ? ! "?" : _loc(locale)->month[t->tm_mon], ! pt, ptlim); continue; case 'b': case 'h': pt = _add((t->tm_mon < 0 || t->tm_mon > 11) ? ! "?" : _loc(locale)->mon[t->tm_mon], ! pt, ptlim); continue; case 'c': ! pt = _fmt(_loc(locale)->c_fmt, t, ! pt, ptlim, locale); continue; case 'C': /* *************** *** 122,148 **** "%02d", pt, ptlim); continue; case 'D': ! pt = _fmt("%m/%d/%y", t, pt, ptlim); ! continue; ! case 'x': ! /* ! ** Version 3.0 of strftime from Arnold Robbins ! ** (arnold(a)skeeve.atl.ga.us) does the ! ** equivalent of... ! ** _fmt("%a %b %e %Y"); ! ** ...for %x; since the X3J11 C language ! ** standard calls for "date, using locale's ! ** date format," anything goes. Using just ! ** numbers (as here) makes Quakers happier. ! ** Word from Paul Eggert (eggert(a)twinsun.com) ! ** is that %Y-%m-%d is the ISO standard date ! ** format, specified in ISO 2014 and later ! ** ISO 8601:1988, with a summary available in ! ** pub/doc/ISO/english/ISO8601.ps.Z on ! ** ftp.uni-erlangen.de. ! ** (ado, 5/30/93) ! */ ! pt = _fmt("%m/%d/%y", t, pt, ptlim); continue; case 'd': pt = _conv(t->tm_mday, "%02d", pt, ptlim); --- 174,180 ---- "%02d", pt, ptlim); continue; case 'D': ! pt = _fmt("%m/%d/%y", t, pt, ptlim, locale); continue; case 'd': pt = _conv(t->tm_mday, "%02d", pt, ptlim); *************** *** 224,240 **** pt, ptlim); continue; case 'R': ! pt = _fmt("%H:%M", t, pt, ptlim); continue; case 'r': ! pt = _fmt("%I:%M:%S %p", t, pt, ptlim); continue; case 'S': pt = _conv(t->tm_sec, "%02d", pt, ptlim); continue; case 'T': ! case 'X': ! pt = _fmt("%H:%M:%S", t, pt, ptlim); continue; case 't': pt = _add("\t", pt, ptlim); --- 256,271 ---- pt, ptlim); continue; case 'R': ! pt = _fmt("%H:%M", t, pt, ptlim, locale); continue; case 'r': ! pt = _fmt("%I:%M:%S %p", t, pt, ptlim, locale); continue; case 'S': pt = _conv(t->tm_sec, "%02d", pt, ptlim); continue; case 'T': ! pt = _fmt("%H:%M:%S", t, pt, ptlim, locale); continue; case 't': pt = _add("\t", pt, ptlim); *************** *** 321,327 **** ** "date as dd-bbb-YYYY" ** (ado, 5/24/93) */ ! pt = _fmt("%e-%b-%Y", t, pt, ptlim); continue; case 'W': pt = _conv((t->tm_yday + 7 - --- 352,358 ---- ** "date as dd-bbb-YYYY" ** (ado, 5/24/93) */ ! pt = _fmt("%e-%b-%Y", t, pt, ptlim, locale); continue; case 'W': pt = _conv((t->tm_yday + 7 - *************** *** 332,337 **** --- 363,376 ---- case 'w': pt = _conv(t->tm_wday, "%d", pt, ptlim); continue; + case 'X': + pt = _fmt(_loc(locale)->X_fmt, t, + pt, ptlim, locale); + continue; + case 'x': + pt = _fmt(_loc(locale)->x_fmt, t, + pt, ptlim, locale); + continue; case 'y': pt = _conv((t->tm_year + TM_YEAR_BASE) % 100, "%02d", pt, ptlim); *************** *** 390,393 **** --- 429,526 ---- while (pt < ptlim && (*pt = *str++) != '\0') ++pt; return pt; + } + + static const struct lc_time * + _loc(locale) + struct lc_time *locale; + { + static const char locale_home[] = LOCALE_HOME; + static const char lc_time[] = "LC_TIME"; + static char *locale_buf; + static char locale_buf_C[] = "C"; + + int fd; + char *lbuf, *name, *p; + const char **ap, *plim; + char filename[FILENAME_MAX]; + struct stat st; + size_t namesize, bufsize; + + /* Use locale->mon[0] to signal whether locale is already set up. */ + if (locale->mon[0]) + return locale; + + #if HAVE_SETLOCALE + name = setlocale(LC_TIME, (char *)0); + #else + if (!(name = getenv("LC_ALL")) || !*name) + if (!(name = getenv(lc_time)) || !*name) + name = getenv("LANG"); + #endif + if (!name || !*name) + goto no_locale; + + /* If the locale name is the same as our cache, use the cache. */ + lbuf = locale_buf; + if (lbuf && strcmp(name, lbuf) == 0) { + p = lbuf; + for (ap=(const char **)locale; ap<(const char **)(locale + 1); ap++) + *ap = p += strlen(p) + 1; + return locale; + } + + /* Slurp the locale file into the cache. */ + namesize = strlen(name) + 1; + if (sizeof(filename) < sizeof(locale_home) + namesize + sizeof(lc_time)) + goto no_locale; + sprintf(filename, "%s/%s/%s", locale_home, name, lc_time); + fd = open(filename, O_RDONLY, 0); + if (fd < 0) + goto no_locale; + if (fstat(fd, &st) != 0) + goto bad_locale; + if (st.st_size <= 0) + goto bad_locale; + bufsize = namesize + st.st_size; + locale_buf = 0; + lbuf = + !lbuf || lbuf==locale_buf_C + ? malloc(bufsize) + : realloc(lbuf, bufsize); + if (!lbuf) + goto bad_locale; + strcpy(lbuf, name); + p = lbuf + namesize; + plim = p + st.st_size; + if (read(fd, p, (size_t)st.st_size) != st.st_size) + goto bad_lbuf; + if (close(fd) != 0) + goto bad_lbuf; + + /* Parse the locale file into *locale. */ + if (plim[-1] != '\n') + goto bad_lbuf; + for (ap=(const char **)locale; ap<(const char **)(locale + 1); ap++) { + if (p == plim) + goto bad_lbuf; + *ap = p; + while (*p != '\n') + p++; + *p++ = 0; + } + + /* Record the successful parse in the cache. */ + locale_buf = lbuf; + + return locale; + + bad_lbuf: + free(lbuf); + bad_locale: + (void) close(fd); + no_locale: + *locale = C_time_locale; + locale_buf = locale_buf_C; + return locale; }

1 0

timezones compatible with POSIX? [forwarded with permisison]
by ado May 8, 1994

May 8, 1994

> From peggyd(a)sco.COM Fri May 6 14:03:24 1994 > Return-Path: <peggyd(a)sco.COM> > Received: from relay1.UU.NET by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA01798; Fri, 6 May 94 14:03:23 EDT > Received: from sco.sco.COM by relay1.UU.NET with SMTP > (5.61/UUNET-internet-primary) id AAwotc03064; Fri, 6 May 94 14:03:19 -0400 > Received: from tehama.sco.COM by sco.sco.COM > id aa08718; Wed, 6 May 70 11:08:32 PDT > Received: from ping.sco.COM by tehama.sco.com id aa00201; 6 May 94 11:00 PDT > From: mommy <peggyd(a)sco.COM> > X-Mailer: SCO System V Mail (version 3.2) > To: ado(a)elsie.nci.nih.gov > Subject: timezones compatible with POSIX? > Cc: peggyd(a)sco.COM > Date: Fri, 6 May 94 10:59:55 PDT > Message-Id: <9405061059.aa21366(a)ping.sco.com> > Status: RO > > > Hello, > > I work at the Santa Cruz Operation, a company that makes > UNIX. I am designing and implementing the part of our > installation that sets time zones. A search for complete, > thorough timezone information led me to your anonymous ftp > site, and I would like to use the information that you make > available, if possible. > > However I am having some trouble reconciling the Rule > format with the format we use, which is also the POSIX standard > for timezone strings (as far as I can tell, looking at my > POSIX doc). The problem is in the area of shifting to and from > Daylight Savings Time. Our format is to use a Julian day, > a month/week/day, or a week/day format. It's different enough from > your Rule format that timezones defined in your format (such as Sun >= 11) > do not work in our format for more than a few years at best (is > that the 2nd week of the month? The 3rd week? It shifts.) > > I am wondering if anyone else has had this problem, and if you > have seen any solutions? Are there alternate ways of expressing > timezones? If you'd like more information I'd be happy to supply > it. > > Thanks very much for your help, > > --peggyd(a)sco.com

4 3

oops--tzcode94g.tar.gz
by ado May 5, 1994

May 5, 1994

The file tzcode94f.tar.gz was missing "optind.c" and a reference to it in the Makefile; tzcode94g.tar.gz remedies the problem. --ado

1 0

tzcode94f.tar.gz
by ado May 5, 1994

May 5, 1994

The file tzcode94f.tar.gz is now available for anonymous ftp from the "~ftp/pub" directory on elsie.nci.nih.gov (128.231.16.1). It includes changes to avoid overflow in difftime, as well as changes to cope with the 52/53 challenge in strftime. --ado

1 0

difftime overflows when it shouldn't
by eggert＠twinsun.com May 3, 1994

May 3, 1994

Let's take the common case where time_t ranges from -2147483648 through 2147483647, and `double' is IEEE 754 double precision. Then, under tz-1994e, the program #include <time.h> #include <stdio.h> #define MAX_TIME 2147483647 #define MIN_TIME (-1 - MAX_TIME) int main() { printf("difftime(%ld, %ld) = %.17g\n", (long) MAX_TIME, (long) MIN_TIME, difftime(MAX_TIME, MIN_TIME)); return 0; } outputs difftime(2147483647, -2147483648) = -1 There's no reason for difftime to report the wrong answer, since the result is exactly representable. Here is a patch. =================================================================== RCS file: difftime.c,v retrieving revision 1994.5 retrieving revision 1994.5.1.1 diff -c -r1994.5 -r1994.5.1.1 *** difftime.c 1992/04/23 17:34:30 1994.5 --- difftime.c 1994/05/03 04:30:43 1994.5.1.1 *************** *** 13,17 **** const time_t time1; const time_t time0; { ! return time1 - time0; } --- 13,28 ---- const time_t time1; const time_t time0; { ! if (sizeof(time_t) < sizeof(double)) ! return (double) time1 - (double) time0; ! else { ! time_t delta = time1 - time0; ! if ((~time1 & time0 & delta) < 0) { ! time_t hibit; ! for (hibit = 1; (hibit <<= 1) > 0; ) ! ; ! return delta - 2.0 * hibit; ! } else ! return delta; ! } }

1 0

forwarded message from Andy J. Chichak
by Garrett Wollman April 28, 1994

April 28, 1994

------- start of forwarded message (RFC 934) ------- Message-Id: <199404280314.LAA01792(a)gateway.tiasur.tomsk.su> X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 805 Precedence: bulk From: "Andy J. Chichak" <chch(a)gateway.tiasur.tomsk.su> Sender: freebsd-tz-owner(a)freefall.cdrom.com To: freebsd-tz(a)freefall.cdrom.com (FreeBSD time zone) Subject: some questions about src/share/zoneinfo/datfiles/europe Date: Thu, 28 Apr 1994 11:14:24 +0800 (TSD) Hello ! I`ve tried to setup my time & found some interest things : Always our timezone was TSK (TSD), TSK is in Tashkent ... We have 4 hours difference in time with Moscow & 1 hour with Irkutsk => time in Irkutsk - time in Moscow = 5 , but in 'europe' it is so : # 3:00 MSK MSD Moscow # 3:00 TUR+DST Turkey (no longer used)* # 4:00 SSK SSD Sverdlovsk* # 5:00 OSK OSD Omsk* # 6:00 NSK NSD Novosibirsk # 7:00 ISK ISD Irkutsk* >? 7:00 TSK TSD Tomsk >? 8:00 ISK ISD Irkutsk And one more problem : Zone Asia/Omsk 4:53:36 - LMT 1924 May 2 5:00 - TSK 1957 Mar 6:00 Russia TS%s 1991 Sep 29 3:00 > ^^^^ ??????? 5:00 Russia OS%s I`ll try to know all about time zones in Russia. Who is 'europe' coordinator ? /Andy ------- end -------

1 0

Re: Australian daylight savings time [forwarded with permission]
by Bradley White April 11, 1994

April 11, 1994

John Connolly <connolly(a)zk3.dec.com> writes: > I am tracking down a problem reported by a customer. He indicates that the > zoneinfo for South Australia is off by one week. > > I have no idea if he is correct or not but I assume he is if he lives there. > Is there there a way to check this officially and if it is wrong I would > like to see the change made in the right places. The file contains the > following rule: > > Rule AS 1990 max even Mar Sun>=22 3:00 0 - > > He has suggested the rule be changed to: > > Rule AS 1990 max even Mar Sun>=15 3:00 0 - > > Any help on this would be greatly appreciated. ado, Here are five old messages chronicling the Adelaide Festival rule. If Sun, 15 March, 1992 was at +1030 as kre asserts, but yet Sun, 20 March, 1994 was at +0930 as John Connolly's customer seems to assert, then I can only conclude that the actual rule is more complicated than either of those given above. kre's ``2nd last Sunday'' is consistent with those dates, but perhaps his ``the Sunday we pick for this year'' is the real truth. bww ------- Begin Forwarded Message #1 Date: Wed, 11 Mar 92 12:21:42 -0500 (EST) From: Bradley White <bww+(a)CS.CMU.EDU> Subject: Re: australasia To: Arthur David Olson <ado(a)ELSIE.NCI.NIH.GOV> Cc: Zone Watchers <tz(a)ELSIE.NCI.NIH.GOV> I believe ... Rule AS 1991 max - Mar Sun>=1 3:00 0 - ... to be wrong. Recent correspondence with a friend in Adelaide contained the following exchange: Due to the Adelaide Festival, South Australia delays setting back our clocks for a few weeks. ------- End Forwarded Message ------- Begin Forwarded Message #2 Date: Fri, 13 Mar 92 07:49:50 +1000 From: Robert Elz <kre(a)munnari.oz.au> Subject: Re: australasia To: Bradley White <bww+(a)CS.CMU.EDU> Cc: Arthur David Olson <ado(a)ELSIE.nci.nih.gov> I heard that apparently (or at least, it appears that) South Aus will have an extra 3 weeks daylight saving every even numbered year (from 1990). That's when the Adelaide Festival is on... ------- End Forwarded Message ------- Begin Forwarded Message #3 Date: Sat, 14 Mar 92 13:27:30 EST From: ado(a)elsie.nci.nih.gov (Arthur David Olson) Subject: South Australia DST cutoff day To: bww+(a)cs.cmu.edu, kre(a)munnari.oz.au An extra three weeks would make the ending test "Sun>=22" as opposed to the "Sun>=1" used everywhere else, right? Making what we need Rule AS 1986 max adfest Mar Sun>=22 3:00 0 - Rule AS 1986 max nonfest Mar Sun>=1 3:00 0 - plus a "yearistype" script? ------- End Forwarded Message ------- Begin Forwarded Message #4 Date: Sat, 14 Mar 92 20:11:44 -0500 (EST) From: Bradley White <bww+(a)CS.CMU.EDU> Subject: Re: South Australia DST cutoff day To: Arthur David Olson <ado(a)elsie.nci.nih.gov> Cc: Robert Elz <kre(a)MUNNARI.OZ.AU> I don't know the exact rules in this case, but historically things usually happen on the ``third Sunday,'' which would be "Sun>=15" or "Sun<=21". Given that it is "Sun, 15 Mar 92" in South Australia at this very moment, it should be easy to find out if the shift was today, or is next week. [Aside: I actually just received a message from someone in Adelaide and the timezone still read +1030 (daylight time), so perhaps the ">=22" is right.] ------- End Forwarded Message ------- Begin Forwarded Message #5 Date: Mon, 16 Mar 92 00:57:07 +1000 From: Robert Elz <kre(a)munnari.oz.au> Subject: Re: South Australia DST cutoff day To: Bradley White <bww+(a)CS.CMU.EDU> Cc: Arthur David Olson <ado(a)elsie.nci.nih.gov> DST didn't end in Adelaide today (yesterday) (Aside: it did in NZ for a cross check on what the rules for NZ say). That's for sure - there was a world cup cricket match in Adelaide yesterday (Sunday), and it was certainly still daylight saving there. Quite apart from that, the news reports said "an extra 3 weeks in SA" and yesterday was just 2 weeks, so there's certainly one to go. But whether its "4th Sunday" or "2nd last Sunday" I have no idea whatever... (its just as likely to be "the Sunday we pick for this year"...) ------- End Forwarded Message

1 0

Australian daylight savings time [forwarded with permission]
by ado April 11, 1994

April 11, 1994

> From connolly(a)zk3.dec.com Fri Apr 8 14:35:03 1994 > Return-Path: <connolly(a)zk3.dec.com> > Received: from decvax.dec.com (decvax.zk3.dec.com) by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA16343; Fri, 8 Apr 94 14:35:01 EDT > Received: from quarry.zk3.dec.com by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92) > id AA00453; Fri, 8 Apr 1994 14:34:58 -0400 > Received: from localhost by quarry.zk3.dec.com; (5.65/1.1.8.2/07Apr94-0144PM) > id AA06464; Fri, 8 Apr 1994 14:34:56 -0400 > Message-Id: <9404081834.AA06464(a)quarry.zk3.dec.com> > To: ado(a)elsie.nci.nih.gov > Cc: connolly(a)quarry.zk3.dec.com > Subject: Australian daylight savings time > Date: Fri, 08 Apr 94 14:34:56 -0400 > From: connolly(a)zk3.dec.com > X-Mts: smtp > Status: RO > > Arthur, > > I am tracking down a problem reported by a customer. He indicates that the > zoneinfo for South Australia is off by one week. > > I have no idea if he is correct or not but I assume he is if he lives there. Is there there a way to check this officially > and if it is wrong I would like to see the change made in the right places. The > file contains the following rule: > > Rule AS 1990 max even Mar Sun>=22 3:00 0 - > > He has suggested the rule be changed to: > > Rule AS 1990 max even Mar Sun>=15 3:00 0 - > > Any help on this would be greatly appreciated. > > John Connolly

1 0

Re: problems with tz-1994e `date'+mktime and Solaris 2.3 strftime
by eggert＠twinsun.com April 8, 1994

April 8, 1994

I think I've figured out the problem with tz-1994e under Solaris 2.3. Guy Harris's intuition was right -- it was the leading-`_' symbols. The problem is that tz-1994e's `date' command calls Sun's strftime, which invokes mktime to set _tzname (not tzname, since a non-Posix Standard C program might have its own external variable called tzname, so the Sun tzname is a weak reference to _tzname). But the tz package defines its own mktime, which sets tzname (which is qnot _tzname). Sun's mktime never gets invoked and therefore Sun's _tzname never gets initialized. I think that this bug will happen in any SVR4 system, regardless of whether -DUSG_COMPAT and -DTM_GMTOFF. The only fix that I can see for tz is the one I already submitted, namely to use tz's strftime instead of the one supplied with the system, as follows: =================================================================== RCS file: Makefile,v retrieving revision 1994.5.1.1 retrieving revision 1994.5.1.2 diff -c -r1994.5.1.1 -r1994.5.1.2 *** Makefile 1994/04/03 02:54:41 1994.5.1.1 --- Makefile 1994/04/03 19:47:59 1994.5.1.2 *************** *** 280,292 **** if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib $@ ; fi ! # We use the system's logwtmp and strftime in preference to ours if available. date: $(DATEOBJS) ! ar r ,lib.a logwtmp.o strftime.o if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib ,lib.a ; fi ! $(CC) $(CFLAGS) date.o localtime.o asctime.o getopt.o \ -lc ,lib.a -o $@ rm -f ,lib.a --- 280,292 ---- if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib $@ ; fi ! # We use the system's getopt and logwtmp in preference to ours if available. date: $(DATEOBJS) ! ar r ,lib.a getopt.o logwtmp.o if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib ,lib.a ; fi ! $(CC) $(CFLAGS) date.o localtime.o asctime.o strftime.o \ -lc ,lib.a -o $@ rm -f ,lib.a

1 0

Re: linking problems with tz-1994e `date' on Solaris 2.3
by Joel.Tornatore＠Eng.Sun.COM April 7, 1994

April 7, 1994

> > 1. The Solaris 2.3 strftime gets confused about the timezone when > > it's linked together with `date'. I don't have the Solaris 2.3 > > source, so I don't know the details, but my guess is that Solaris 2.3 > > strftime assumes that tzset sets some global variables in the Solaris > > 2.3 library, but since we've substituted our own tzset this assumption > > no longer applies. The symptoms are that `date' prints the correct > > time but with either "GMT" or "" substituted for the time zone name. > > As I remember, in SV-derived systems, "tzset()" will set the "timezone", > "daylight", and "tzname" variables; in systems derived from more recent > SV's (SVR3.1 and later, I think), it also sets "altzone". > > SunOS 5.3 is SVR4-derived, so any time zone code installed on it should > arrange to set "timezone", "altzone", "daylight", and "tzname" when > "tzset()" is called. (It may, I think, reset them if there aren't > single values for them that make sense - e.g., if there are different > time zone abbreviations for standard time at different dates, or > different time zone abbreviations for summer time at different dates, I > think "localtime()" may change the setting of "tzname". That, at least, > was the intent.) > > It may be that "strftime()" is expecting "tzname" to be set; if it's not > being set, that may be the source of the problem. The SunOS 5.3 version of tzset() does set these variables: timezone daylight tzname altzone and it does reset them if TZ is not set properly. localtime() calls tzset(), so it will change the tzname[] values. joel

3 4

linking problems with tz-1994e `date' on Solaris 2.3
by eggert＠lotl.twinsun.com April 4, 1994

April 4, 1994

I had two problems linking tz-1994e `date' under Solaris 2.3. 1. The Solaris 2.3 strftime gets confused about the timezone when it's linked together with `date'. I don't have the Solaris 2.3 source, so I don't know the details, but my guess is that Solaris 2.3 strftime assumes that tzset sets some global variables in the Solaris 2.3 library, but since we've substituted our own tzset this assumption no longer applies. The symptoms are that `date' prints the correct time but with either "GMT" or "" substituted for the time zone name. The workaround is to use tz's strftime instead. 2. The system `getopt' and tz `getopt' clash as follows. In Solaris 2.3, `getopt' is broken into two object modules to make its more efficient in a shared library. One, `opt_data.o', merely contains the modifiable data (optind, optarg, opterr, and optopt). (The other, getopt.o, contains the code.) opt_data.o contains definitions for all four symbols, whereas tz's getopt contains two definitions (opterr and optind) and two common symbols (optopt and optarg). This confuses the Solaris 2.3 linker: it brings in opt_data to resolve the common symbols, but then it complains that opterr and optind are multiply defined. Here are the symptoms: gcc -static -Dlint -g -O -Wall -DTZDIR=\"etc/zoneinfo\" date.o localtime.o asctime.o getopt.o \ -lc ,lib.a -o date ld: fatal: symbol `optind' is multiply defined: (file getopt.o and file /usr/lib/libc.a(opt_data.o)); ld: fatal: symbol `opterr' is multiply defined: (file getopt.o and file /usr/lib/libc.a(opt_data.o)); ld: fatal: File processing errors. No output written to date *** Error code 1 One patch might be to modify tz's getopt.c to statically initialize optopt and optarg to 0 (I haven't tested this). Another patch, which I've taken below, is to use the system getopt if it is available. Here is a patch that embodies the above two suggestions. =================================================================== RCS file: Makefile,v retrieving revision 1994.5.1.1 retrieving revision 1994.5.1.2 diff -c -r1994.5.1.1 -r1994.5.1.2 *** Makefile 1994/04/03 02:54:41 1994.5.1.1 --- Makefile 1994/04/03 19:47:59 1994.5.1.2 *************** *** 280,292 **** if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib $@ ; fi ! # We use the system's logwtmp and strftime in preference to ours if available. date: $(DATEOBJS) ! ar r ,lib.a logwtmp.o strftime.o if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib ,lib.a ; fi ! $(CC) $(CFLAGS) date.o localtime.o asctime.o getopt.o \ -lc ,lib.a -o $@ rm -f ,lib.a --- 280,292 ---- if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib $@ ; fi ! # We use the system's getopt and logwtmp in preference to ours if available. date: $(DATEOBJS) ! ar r ,lib.a getopt.o logwtmp.o if [ -x /usr/ucb/ranlib -o -x /usr/bin/ranlib ] ; \ then ranlib ,lib.a ; fi ! $(CC) $(CFLAGS) date.o localtime.o asctime.o strftime.o \ -lc ,lib.a -o $@ rm -f ,lib.a

2 1

mktime bugs around the edges
by eggert＠lotl.twinsun.com April 3, 1994

April 3, 1994

Here are some mktime bugs in tz-1994e. (Bugs that PCTS should have caught :-) mktime fails on the earliest representable time (Fri Dec 13 20:45:52 1901 GMT). mktime does not fail, as it should, with one plus the last representable time (i.e. with Tue Jan 19 03:14:08 2038 GMT). It wraps around and reports Fri Dec 13 20:45:52 1901 GMT instead. When normalizing times, mktime assumes that every minute contains 60 seconds. This is incorrect if leap seconds are in use. mktime does not detect arithmetic overflow when normalizing nonsensically large inputs. Here is a patch. =================================================================== RCS file: localtime.c,v retrieving revision 1994.5.1.1 retrieving revision 1994.5.1.2 diff -c2 -r1994.5.1.1 -r1994.5.1.2 *** localtime.c 1994/04/03 02:54:41 1994.5.1.1 --- localtime.c 1994/04/03 21:25:32 1994.5.1.2 *************** *** 114,118 **** static void localsub P((const time_t * timep, long offset, struct tm * tmp)); ! static void normalize P((int * tensptr, int * unitsptr, int base)); static void settzname P((void)); static time_t time1 P((struct tm * tmp, --- 114,120 ---- static void localsub P((const time_t * timep, long offset, struct tm * tmp)); ! static int increment_overflow P((int * number, int delta)); ! static int normalize_overflow P((int * tensptr, int * unitsptr, ! int base)); static void settzname P((void)); static time_t time1 P((struct tm * tmp, *************** *** 1155,1160 **** */ ! static void ! normalize(tensptr, unitsptr, base) int * const tensptr; int * const unitsptr; --- 1157,1172 ---- */ ! static int ! increment_overflow(number, delta) ! int * number; ! int delta; ! { ! int number0 = *number; ! *number = number0 + delta; ! return (*number < number0) != (delta < 0); ! } ! ! static int ! normalize_overflow(tensptr, unitsptr, base) int * const tensptr; int * const unitsptr; *************** *** 1166,1171 **** (*unitsptr / base) : (-1 - (-1 - *unitsptr) / base); - *tensptr += tensdelta; *unitsptr -= tensdelta * base; } --- 1178,1183 ---- (*unitsptr / base) : (-1 - (-1 - *unitsptr) / base); *unitsptr -= tensdelta * base; + return increment_overflow(tensptr, tensdelta); } *************** *** 1204,1225 **** *okayp = FALSE; yourtm = *tmp; ! if (yourtm.tm_sec >= SECSPERMIN + 2 || yourtm.tm_sec < 0) ! normalize(&yourtm.tm_min, &yourtm.tm_sec, SECSPERMIN); ! normalize(&yourtm.tm_hour, &yourtm.tm_min, MINSPERHOUR); ! normalize(&yourtm.tm_mday, &yourtm.tm_hour, HOURSPERDAY); ! normalize(&yourtm.tm_year, &yourtm.tm_mon, MONSPERYEAR); while (yourtm.tm_mday <= 0) { ! --yourtm.tm_year; ! yourtm.tm_mday += ! year_lengths[isleap(yourtm.tm_year + TM_YEAR_BASE)]; } while (yourtm.tm_mday > DAYSPERLYEAR) { ! yourtm.tm_mday -= ! year_lengths[isleap(yourtm.tm_year + TM_YEAR_BASE)]; ! ++yourtm.tm_year; } for ( ; ; ) { ! i = mon_lengths[isleap(yourtm.tm_year + ! TM_YEAR_BASE)][yourtm.tm_mon]; if (yourtm.tm_mday <= i) break; --- 1216,1236 ---- *okayp = FALSE; yourtm = *tmp; ! if ( normalize_overflow(&yourtm.tm_hour, &yourtm.tm_min, MINSPERHOUR) ! || normalize_overflow(&yourtm.tm_mday, &yourtm.tm_hour, HOURSPERDAY) ! || normalize_overflow(&yourtm.tm_year, &yourtm.tm_mon, MONSPERYEAR) ! || increment_overflow(&yourtm.tm_year, TM_YEAR_BASE)) ! return WRONG; while (yourtm.tm_mday <= 0) { ! if (increment_overflow(&yourtm.tm_year, -1)) ! return WRONG; ! yourtm.tm_mday += year_lengths[isleap(yourtm.tm_year)]; } while (yourtm.tm_mday > DAYSPERLYEAR) { ! 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; *************** *** 1227,1235 **** if (++yourtm.tm_mon >= MONSPERYEAR) { yourtm.tm_mon = 0; ! ++yourtm.tm_year; } } ! saved_seconds = yourtm.tm_sec; ! yourtm.tm_sec = 0; /* ** Calculate the number of magnitude bits in a time_t --- 1238,1264 ---- 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 < EPOCH_YEAR - TM_YEAR_BASE) { ! /* ! ** 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 *************** *** 1298,1302 **** } label: ! t += saved_seconds; (*funcp)(&t, offset, tmp); *okayp = TRUE; --- 1327,1334 ---- } label: ! newt = t + saved_seconds; ! if ((newt < t) != (saved_seconds < 0)) ! return WRONG; ! t = newt; (*funcp)(&t, offset, tmp); *okayp = TRUE;

1 0

Re: mktime() failures under PCTS testing
by eggert＠twinsun.com April 1, 1994

April 1, 1994

Mark Brader, who I believe is well connected with the C standardization process, wrote a news article about the mktime problem in which he indicated that he thought that mktime could yield -1 in the spring-forward gap (i.e. that this particular PCTS case is incorrect). I'll enclose a copy of the article at the end of this message. (It responds to another article that I don't have a copy of.) This is probably the best we can do until I get an official response to the C Standard defect report that I filed earlier this week. ----- Newsgroups: comp.std.c From: msb(a)sq.sq.com (Mark Brader) Subject: Re: Can mktime return -1 for times in the spring-forward gap? Message-ID: <1994Mar25.173447.2810(a)sq.sq.com> Summary: Yes, it's undefined behavior Organization: SoftQuad Inc., Toronto, Canada References: <Cn4tnp.DvM(a)twinsun.com> <2mr48c$duk(a)usenet.pa.dec.com> Date: Fri, 25 Mar 94 17:34:47 GMT The original question was about mktime() with the tm_isdst member negative, and times in the "spring-forward gap", i.e. the transition to Daylight Saving Time. > I think the standard contradicts itself. The relevant fields are not > restricted to the usual ranges, yet if the calendar time cannot be > represented then mktime returns -1. I think that your example requires > a return of -1, and an example with tm_hour being 27 is a calendar time > that cannot be represented so it requires a return of -1, even though > mktime has to force the fields into the usual ranges. I think that this is a strained interpretation, and that if a ruling was requested, the response would be that the standard is clear enough as it is. The intent of saying that "the original values ... are not restricted to the ranges indicated above" obviously was to allow alternative specifications for a calendar time, so that 27:00 UTC on October 15, 1982, would signify the same as 03:00 UTC on October 16, 1982; and I don't think there is any other reasonable way to read the actual text. > > The Rationale (section 4.12.2.3) clearly allows mktime to yield -1 in the > > ``fall-backward fold'' [i.e. the opposite transition]... > > The rationale conflicts with the standard, and the standard has priority. > If the tm_isdst field is -1, then a time in the "fall-backward fold" is a > calendar time that can be represented in two ways, so it can be represented, > so the return value cannot be -1 ... The Rationale for 4.12.2.3 does not specify what kind of behavior is involved here, but seems to mean that it is unspecified; perhaps that is what was intended. On reading 4.12.2.3/7.12.2.3 in the actual standard, though, I think the behavior is undefined. What it specifies is only that the broken-down time is converted to a calendar time value. For times in the gap and the fold, no well-defined conversion exists. Therefore, as I see it, the general exclusions in 1.6/3.16 and/or 4.1.6/7.1.7 apply, and the behavior is undefined. (And I think that's an unwise choice; I'd rather that it either be unspecified, or implementation-defined, or that -1 be returned.) > Perhaps now is the calendar time for a few more defect reports. Chuckle. I'd say so. > Every technical corrigendum is met by an equally troublesome new defect > report. But then again... -- Mark Brader, msb(a)sq.com | "You keep using that word. I do not think it means SoftQuad Inc., Toronto | what you think it means." -- The Princess Bride This article is in the public domain.

1 0

Re: 18 sec
by Mills＠udel.edu March 31, 1994

March 31, 1994

Garrett, Wrong. See rfc1589 for an explanation. Dave

1 0

tzcode94e.tar.gz
by ado March 31, 1994

March 31, 1994

The file "tzcode94e.tar.gz" is now available for anonymous ftp from the "~ftp/pub" directory of elsie.nci.nih.gov (128.231.16.1); "tzdata94d.tar.gz" remains the latest data file. The new code incorporates a change for the benefit of PCTS; diffs are attached. --ado SCCS/s.Makefile: 7.21 vs. 7.23 *** 7.21/Makefile Wed Mar 30 23:32:14 1994 --- 7.23/Makefile Wed Mar 30 23:32:15 1994 *************** *** 1,4 **** ! # @(#)Makefile 7.21 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). --- 1,4 ---- ! # @(#)Makefile 7.23 # Change the line below for your time zone (after finding the zone you want in # the time zone files, or adding it to a time zone file). *************** *** 168,173 **** --- 168,179 ---- # -DCMUCS # to the end of the "CFLAGS=" line # This function is not described in X3J11's work. + # + # NIST-PCTS:151-2, Version 1.4, (1993-12-03) is a test suite put + # out by the National Institute of Standards and Technology + # which claims to test C and Posix conformance. If you want to pass PCTS, add + # -DPCTS + # to the end of the "CFLAGS=" line. CFLAGS= SCCS/s.localtime.c: 7.17 vs. 7.18 *** 7.17/localtime.c Wed Mar 30 23:32:17 1994 --- 7.18/localtime.c Wed Mar 30 23:32:18 1994 *************** *** 1,6 **** #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.17"; #endif /* !defined NOID */ #endif /* !defined lint */ --- 1,6 ---- #ifndef lint #ifndef NOID ! static char elsieid[] = "@(#)localtime.c 7.18"; #endif /* !defined NOID */ #endif /* !defined lint */ *************** *** 1308,1315 **** --- 1308,1326 ---- if (tmp->tm_isdst > 1) tmp->tm_isdst = 1; t = time2(tmp, funcp, offset, &okay); + #ifdef PCTS + /* + ** PCTS code courtesy Grant Sullivan (grant(a)osf.org) + */ + if (okay) + return t; + if (tmp->tm_isdst < 0) + tmp->tm_isdst = 0; /* reset to std and try again */ + #endif /* defined PCTS */ + #ifndef PCTS if (okay || tmp->tm_isdst < 0) return t; + #endif /* !defined PCTS */ /* ** We're supposed to assume that somebody took a time of one type ** and did some math on it that yielded a "struct tm" that's bad.

1 0

18 sec
by Garrett Wollman March 29, 1994

March 29, 1994

<<On Tue, 29 Mar 1994 10:12:19 +0200 (MESZ), Hinrich Eilts <eilts(a)late.e-technik.uni-erlangen.de> said: > I synchronized FreeBSD-1.1-BETA to a stratum-1 timeserver by ntpdate > and xntpd and compared localtime by "date" with it and two other > machines, which are synchronized by xntpd too. FreeBSD has a > difference of -18 secounds to all other machines (a NeXT-Station > with NeXTStep, a Sun with SunOS 4.x and a HP9000-750 with > HPUX). What you are seeing is the interaction of several different `features' of NTP and FreeBSD. I'll try to explain, and again hope that somebody out there can provide a complete solution. Here are the problems... 1) The timezone database does not reflect the fact that the first time step, in going from GMT (pre-1972) to UTC (1972 to present) was actually 10 seconds, and not just one like all subsequent leap seconds. 2) The timezone database DOES include all subsequent time steps. 3) The NTP code ``handles'' leap seconds by turning the clock back when they happen. By contrast, the timezone code assumes that time_t's are increasing (which they ought to be; I hold that xntpd's behavior is simply wrong). To wit: NTP code wants: Real Time UNIX Time --------------- --------- --------- 30 June 1994, 23:59:59 t s 30 June 1994, 23:59:59 t+1 s 01 July 1994, 00:00:00 t+2 s+1 Timezone code wants: Real Time UNIX Time -------------------- --------- --------- 30 June 1994, 23:59:59 t s 30 June 1994, 23:59:60 t+1 s+1 01 July 1994, 00:00:00 t+2 s+2 A temporary (ugly hack) solution is to use `posix/your/time/zone' rather than `right/your/time/zone' (which is the same as `your/time/zone') for /etc/localtime. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman(a)lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. formerly known as | It is a bond more powerful than absence. We like people wollman(a)emba.uvm.edu | who like Shashish. - Claude McKenzie + Florent Vollant

2 2

Re: 18 sec
by Bradley White March 29, 1994

March 29, 1994

Garrett Wollman <wollman(a)adrastea.lcs.mit.edu> writes: > What you are seeing is the interaction of several different `features' > of NTP and FreeBSD. I'll try to explain, and again hope that somebody > out there can provide a complete solution. Here is an encore of my reply of February 7th. --- Begin forwarded message Date: Mon, 07 Feb 1994 18:05:34 -0500 (EST) From: Bradley White <bww+(a)transarc.com> Subject: Re: leap seconds To: Garrett Wollman <wollman(a)emba.uvm.edu> Cc: Paul Eggert <eggert(a)twinsun.com>, Zone Watchers <tz(a)elsie.nci.nih.gov>, freebsd-tz(a)freefall.cdrom.com Message-Id: <09490.760662334(a)capitol.transarc.com> In-Reply-To: Your message of Mon, 7 Feb 94 17:23:21 -0500 <9402072223.AA23255(a)bajoran.emba.uvm.edu> Any system that runs with ``REDO=right_*'', and which therefore wants to continue to tick normally over leap seconds, needs to do a little bit of work to generate NTP-style timestamps. That is, NTP-style timestamps are discontinuous over leaps, while ``REDO=right_*'' time_t's are continuous. Recent incantations of the `tz' package provide the time2posix() function to help in mapping between these two formats. For example, in the (old, version-1) NTP code, you need to change ... stampp->int_part = htonl(tvp->tv_sec + JAN_1970); to stampp->int_part = htonl(time2posix(tvp->tv_sec) + JAN_1970); I haven't looked at the (new, version-3) XNTP code, but I imagine the change needed there is just as trivial. After that, you will chime NTP harmoniously with the rest of the world, *and*, you will sail smoothly through leap events without the jitter or confusion suffered by your NTP peers. Bradley

1 0

AU Summer time channges (proposed).
by Robert Elz March 29, 1994

March 29, 1994

I'm not in AU right now, and haven't seen the announcementss, though there was talk of changes before I left, but I'm told there is agreement for Vic SA and Tas to switch to summer time on Oct 1, and revert to standard time Mar 31 to give exactly 6 months daylight saving (summer time really) a yearA. One would presume they'd keep the "change on a Sunday" rule, but who knows. Apparently NSW weren't impressed, but may end up changing their minds. I'm sure others in AU can give more details on this. kre

1 0

Re: EU Summer Time update [forwarded with permission]
by ado March 29, 1994

March 29, 1994

> From @doc.memex.co.uk:peter@memex.co.uk Tue Mar 29 08:03:37 1994 > Return-Path: <@doc.memex.co.uk:peter@memex.co.uk> > Received: from relay2.UU.NET by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA09181; Tue, 29 Mar 94 08:03:34 EST > Received: from young.cs.strath.ac.uk by relay2.UU.NET with SMTP > (5.61/UUNET-internet-primary) id AAwjia29244; Tue, 29 Mar 94 08:03:28 -0500 > Received: from doc.memex.co.uk by young.cs.strath.ac.uk id aa02542; > 29 Mar 94 14:02 +0100 > Received: by doc.memex.co.uk (4.1/memex_18) > id AA15065; Tue, 29 Mar 94 13:51:13 BST > Date: Tue, 29 Mar 94 13:51:13 BST > From: Peter Ilieve <peter(a)memex.co.uk> > Message-Id: <9403291251.AA15065(a)doc.memex.co.uk> > To: ado(a)elsie.nci.nih.gov > Subject: Re: EU Summer Time update > Status: RO > > > Thanks for the scoop on EU Summer Time. Is it premature to forward it to > > the time zone list? > > ... > > It is the best info available at present. My personal guess is that > nothing will be changed. I have no idea why it has taken since last > September to fail to confirm this directive, nor why it may take until > May. The first change from existing practice is not until October 95, > when the UK/Eire date is Sun>=22 rather than Sun>=23 so it is probably > safe to pass it on, even if you have to correct it later. > > > Peter

1 0

EU Summer Time update [forwarded with permission]
by ado March 29, 1994

March 29, 1994

> From @doc.memex.co.uk:peter@memex.co.uk Mon Mar 28 04:36:25 1994 > Return-Path: <@doc.memex.co.uk:peter@memex.co.uk> > Received: from relay2.UU.NET by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA12705; Mon, 28 Mar 94 04:36:22 EST > Received: from young.cs.strath.ac.uk by relay2.UU.NET with SMTP > (5.61/UUNET-internet-primary) id AAwjdu24981; Mon, 28 Mar 94 04:36:08 -0500 > Received: from doc.memex.co.uk by young.cs.strath.ac.uk id aa20721; > 28 Mar 94 10:34 +0100 > Received: by doc.memex.co.uk (4.1/memex_18) > id AA05804; Mon, 28 Mar 94 10:32:19 BST > Date: Mon, 28 Mar 94 10:32:19 BST > From: Peter Ilieve <peter(a)memex.co.uk> > Message-Id: <9403280932.AA05804(a)doc.memex.co.uk> > To: ado(a)elsie.nci.nih.gov > Subject: EU Summer Time update > Status: RO > > I now have a copy of the proposal for the 7th EC directive on summer time > arrangements (COM (93) 439 final, 27 September 1993). This is not yet > a formal directive, treat this as advance warning, some dates may still > change. > > I what looks like a triumph of British obduracy over the poor benighted > foreigners it is proposed to move to a common end date of the 4th Sunday > in October from 1997 so the foreigners will have their winter benightment > postponed by a month. The EC Commission actually asked its tame polling > organisation to conduct one of its Eurobarometer surveys which showed > `that European public opinion is very much in favour of having summer > time extended until the end of October'. > > The dates proposed are: > > 1995: last Sunday in March (26 March) to last Sunday in September (24 Sep) > (UK & Eire ending on 4th Sunday in October (22 Oct)) > 1996: last Sunday in March (31 March) to last Sunday in September (29 Sep) > (UK & Eire ending on 4th Sunday in October (27 Oct)) > 1997: last Sunday in March (30 March) to 4th Sunday in October (26 Oct) > 1998: last Sunday in March (29 March) to 4th Sunday in October (25 Oct) > > The UK/Eire end date of 22 October conflicts with your current rule of > Oct Sun>=23, and the historical UK formula of Sun after 4th Sat. The > last time 4th Sun and Sun after 4th Sat differed was in 1989, when 29 > October was used. That year was covered by a UK Summer Time Order for > only a single year and it looks as though there was a matching 4th EC > directive for just this year. I don't have the text of the 5th EC > directive (for 1990--92) but my guess would be it said 4th Sun. To > maintain strict historical accuracy you could start a new UK ending > rule of Oct Sun>=22 in 1990. A similar rule will be needed for all the > -Eur rules from 1997. > > Negotiations about joinging the EU have been concluded with Austria, > Finland, Norway and Sweden and if the current argument among the existing > members about consequential changes in voting rules can be resolved > they should join on 1 Jan 1995, and will presumably use the same > summer time rules as the existing members. I don't know what they do now. > > As I said, this is only a proposal at present. The EC information office > in Edinburgh could give a guesstimate of when the final version might > emerge. The Home Office guessed at the end of May. > I will keep you posted. > > > Peter Ilieve peter(a)memex.co.uk

1 0