- tz - lists.iana.org

[PROPOSED 1/2] Be more realistic in tzfile example
by Paul Eggert March 3, 2023

March 3, 2023

* tzfile.5 (TZ): Give a real-world TZ example instead of an imaginary one. --- tzfile.5 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tzfile.5 b/tzfile.5 index c3e86c62..1bd561ab 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -220,7 +220,7 @@ if there is no POSIX-style representation for such instants. If nonempty, the POSIX-style TZ string must agree with the local time type after the last transition time if present in the eight-byte data; for example, given the string -.q "WET0WEST,M3.5.0,M10.5.0/3" +.q "WET0WEST,M3.5.0/1,M10.5.0" then if a last transition time is in July, the transition's local time type must specify a daylight-saving time abbreviated .q "WEST" -- 2.37.2

1 1

Sunshine Protection Act in the news
by Arthur David Olson March 3, 2023

March 3, 2023

"Bill to make daylight saving time permanent reintroduced in Congress" https://thehill.com/homenews/nexstar_media_wire/3880009-bill-to-make-daylig… @dashdashado

1 0

Paraguay on its way to stay on DST
by Carlos Raúl Perasso March 2, 2023

March 2, 2023

On September 28, the Paraguayan Chamber of Deputies approved a bill that eliminates winter time in Paraguay. This would make Paraguay stay in DST throughout the year. The project was sent to the Senate for approval. After this, it could still have the presidential veto. If successful, the law would take effect after this weekend's time change, so the new rule should read as follows: Rule Para 2010 2022 - Oct Sun>=1 0:00 1:00 - Rule Para 2013 2022 - Mar Sun>=22 0:00 0 - I will keep you informed of the progress of the bill. Saludos, Carlos

2 2

Egypt daylight savings will be back
by Ahmad ElDardiry March 2, 2023

March 2, 2023

Hello, Egypt officially announced today that daylight savings will be applied from last Friday of April to last Thursday of October. https://www.mena.org.eg/ar/news/dbcall/table/textnews/id/10044253#:~:text=2… .

3 6

Time for a Lunar time zone?
by Tim McBrayer March 2, 2023

March 2, 2023

On the lighter side; we may need to consider going interplanetary. https://theweek.com/space/1021396/why-space-experts-want-to-establish-a-lun… https://epaper.bostonglobe.com/infinity/article_popover_share.aspx?guid=8fc… -- Tim McBrayer NOTICE from Ab Initio: This email (including any attachments) may contain information that is subject to confidentiality obligations or is legally privileged, and sender does not waive confidentiality or privilege. If received in error, please notify the sender, delete this email, and make no further use, disclosure, or distribution.

4 3

MJD 60000 Tonight Feb 25 Sat Midnight UTC
by Brian Inglis Feb. 25, 2023

Feb. 25, 2023

Hi folks, Tonight at midnight UTC it was 60k days since the MJD epoch 1858-11-17: 2023 Feb 25 Sat 00:00:00+0000 MJD 60000.000000 JD 2460000.500000 NTP 3886272000 Unix 1677283200 Windows 133217568000000000 No sign of anyone at SAO acknowledging the 65th year of its use since its definition to track Sputnik's orbit on an IBM 704 from 1957-10-04 to about 1958-01-04. -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry

1 0

Charset for Digest Emails
by Owen Leibman Feb. 24, 2023

Feb. 24, 2023

I have been subscribed to the “tz digest”, which comes out about once a day. Whenever a non-ASCII character is part of the message, it is rendered as multiple question marks. This seems to be because the message is sent with a header: Content-Type: text/plain; charset="us-ascii" This is only a minor nuisance. However, as an experiment, I changed my subscription to receive the messages directly rather than in digest form. A message today used an emoji outside the ASCII range, and it was rendered exactly as intended. It came with the following header: Content-Type: text/plain; charset="UTF-8"; format=flowed Is there a setting that could/should be changed so that the digest is sent with the same header? This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.

5 7

Austin Group POSIX TZ changes and Time Zone Taxonomy
by Brian Inglis Feb. 23, 2023

Feb. 23, 2023

Hi folks, Saw that the Austin Group is proposing to support *some* time zones in POSIX issue 8; see: https://www.austingroupbugs.net/view.php?id=1619 TZ=Area/Location Some of the zones could be categorized as they have proposed, but that uses terminology that I don't think we would approve of, leaves a lot of zones in the tzdb unsupported and unaddressed, and omits a whole reality which I have attempted to categorize in the attached. Perhaps some here would like to come up with better facts, names, terminology, and wording, and propose an update to the Austin Group, that better reflects what exists, and what they are meant to be standardizing? If they are going to standardize this, they should either do it properly, or drop it entirely, maintaining the status quo, as they are not going to be helping with their inaccurate terminology, and limited support! -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry

4 5

Re: [tz] IANA compilation problem
by Paul Eggert Feb. 22, 2023

Feb. 22, 2023

On 1/26/23 20:08, Steven Shuriff wrote: > I am getting compilation errors with the tz code involving UINTMAX_MAX. > This is happening on Windows and on VMS. Both are using older compilers. > > Windows is getting: > zic.c(1317) : error C2065: 'UINTMAX_MAX' : undeclared identifier > zic.c(2358) : warning C4116: unnamed type definition in parentheses > > > VMS is getting: > uint_fast64_t unfair_min = - ((UINTMAX_MAX % base__6 + 1) % base__6); > .................................^ > %CC-E-UNDECLARED, In the initializer for unfair_min, "UINTMAX_MAX" is not declared. > at line number 1272 in file DEVVS1$DKA0:[COMMON_INGSRC.TREASURE.IANA.iana.tmp]zic.c;33 > Failed to build zic > > > Besides upgrading the compilers (not possible at this time) is there any possible solution? Sorry, I didn't see this private email until now. Please try the attached patch, which I installed into the development repository. It fixes a portability bug present since TZDB release 2022f. As mentioned in <https://mm.icann.org/pipermail/tz/2022-December/032399.html> I'm planning to phase out support for C89, as these old compilers are not much used nowadays and the cost of maintaining the ports to these compilers is starting to outweigh the benefit. In the next release if you still need support for old compilers the plan is that you'll need to compile with -DPORT_TO_C89 and/or -DSUPPORT_C99. This is intended to be a heads-up for builders on obsolete platforms.

2 2

Palestine time zone web page
by heba.hamad Feb. 1, 2023

Feb. 1, 2023

2 1

tzdata timezone problem
by 刘宇 Jan. 31, 2023

Jan. 31, 2023

Hello: Maybe it's wrong to calculate local time by using the latest version tzdada2022g when zoneid is "America/Ojinaga". Thanks

2 1

Looking for details on timezones “right/…”
by Jens Tröger Jan. 30, 2023

Jan. 30, 2023

Hello, Today I stumbled upon timezone strings like “right/UTC”, “right/America/Jujuy”, and so forth, but I’m unable to find details on the meaning & classification of the “right/” here and how it relates to actual UTC and other timezones. I’d appreciate pointers or clarifications. Thank you kindly, Jens -- Jens Tröger https://savage.light-speed.de/

6 8

In the news: Russia wants to put illegally occupied regions to Moscow Time
by Derick Rethans Jan. 27, 2023

Jan. 27, 2023

Hi, saw this in the news: https://www.newsweek.com/russia-moscow-time-zone-ukraine-annexed-territorie… cheers, Derick

6 8

Dead PTB link
by Benjamin Drung Jan. 27, 2023

Jan. 27, 2023

Hi, I noticed that the PTB link http://www.ptb.de/de/org/4/44/441/salt.htm is dead. See attached patch (for git am) to update it to the current location. -- Benjamin Drung Debian & Ubuntu Developer

2 1

[PROPOSED 1/2] Update IDL commentary
by Paul Eggert Jan. 25, 2023

Jan. 25, 2023

--- australasia | 36 +++++++++++++++--------------------- 1 file changed, 15 insertions(+), 21 deletions(-) diff --git a/australasia b/australasia index 749b72c8..84d94b99 100644 --- a/australasia +++ b/australasia @@ -2199,24 +2199,18 @@ Zone Pacific/Efate 11:13:16 - LMT 1912 Jan 13 # Vila # an international standard, there are some places on the high seas where the # correct date is ambiguous. -# From Wikipedia <https://en.wikipedia.org/wiki/Time_zone> (2005-08-31): -# Before 1920, all ships kept local apparent time on the high seas by setting -# their clocks at night or at the morning sight so that, given the ship's -# speed and direction, it would be 12 o'clock when the Sun crossed the ship's -# meridian (12 o'clock = local apparent noon). During 1917, at the -# Anglo-French Conference on Time-keeping at Sea, it was recommended that all -# ships, both military and civilian, should adopt hourly standard time zones -# on the high seas. Whenever a ship was within the territorial waters of any -# nation it would use that nation's standard time. The captain was permitted -# to change his ship's clocks at a time of his choice following his ship's -# entry into another zone time - he often chose midnight. These zones were -# adopted by all major fleets between 1920 and 1925 but not by many -# independent merchant ships until World War II. - -# From Paul Eggert, using references suggested by Oscar van Vlijmen -# (2005-03-20): -# -# The American Practical Navigator (2002) -# http://pollux.nss.nima.mil/pubs/pubs_j_apn_sections.html?rid=187 -# talks only about the 180-degree meridian with respect to ships in -# international waters; it ignores the international date line. +# From Wikipedia <https://en.wikipedia.org/wiki/Nautical_time> (2023-01-23): +# The nautical time zone system is analogous to the terrestrial time zone +# system for use on high seas. Under the system time changes are required for +# changes of longitude in one-hour steps. The one-hour step corresponds to a +# time zone width of 15° longitude. The 15° gore that is offset from GMT or +# UT1 (not UTC) by twelve hours is bisected by the nautical date line into two +# 7°30' gores that differ from GMT by ±12 hours. A nautical date line is +# implied but not explicitly drawn on time zone maps. It follows the 180th +# meridian except where it is interrupted by territorial waters adjacent to +# land, forming gaps: it is a pole-to-pole dashed line. + +# From Paul Eggert (2023-01-23): +# The American Practical Navigator <https://msi.nga.mil/Publications/APN>, +# 2019 edition, merely says that the International Date Line +# "coincides with the 180th meridian over most of its length." -- 2.37.2

3 5

[PROPOSED 1/4] Allow “§” etc. in commentary
by Paul Eggert Jan. 24, 2023

Jan. 24, 2023

* Makefile (UNUSUAL_OK_LATIN_1): Allow all non-alphabetic, non-ASCII printable characters that are Latin-1. This is primarily for “§” and we might as well allow them all since even XEmacs 21 supports them all. --- Makefile | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 721a7452..17e3bb57 100644 --- a/Makefile +++ b/Makefile @@ -459,9 +459,10 @@ SAFE_CHARSET3= 'abcdefghijklmnopqrstuvwxyz{|}~' SAFE_CHARSET= $(SAFE_CHARSET1)$(SAFE_CHARSET2)$(SAFE_CHARSET3) SAFE_CHAR= '[]'$(SAFE_CHARSET)'-]' -# These characters are Latin-1, and so are likely to be displayable -# even in editors with limited character sets. -UNUSUAL_OK_LATIN_1 = «°±»½¾× +# These non-alphabetic, non-ASCII printable characters are Latin-1, +# and so are likely displayable even in editors like XEmacs 21 +# that have limited character sets. +UNUSUAL_OK_LATIN_1 = ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿×÷ # This IPA symbol is represented in Unicode as the composition of # U+0075 and U+032F, and U+032F is not considered alphabetic by some # grep implementations that do not grok composition. -- 2.37.2

4 7

No leap second on 2023-06-30
by Tim Parenti Jan. 20, 2023

Jan. 20, 2023

Per IERS, Bulletin C 65 (2023-01-09) https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.65 …and forwarded below. A patch updating leap-seconds.list from NIST is attached, and is installed in the development repository. -- Tim Parenti ---------- Forwarded message --------- From: IERS EOP Product Center <iers.eoppc(a)obspm.fr> Date: Mon, 9 Jan 2023 at 05:36 Subject: Bulletin C number 65 To: <bulc.iers(a)obspm.fr> INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE DE L'IERS OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : +33 1 40 51 23 35 e-mail : services.iers(a)obspm.fr http://hpiers.obspm.fr/eop-pc Paris, 09 January 2023 Bulletin C 65 To authorities responsible for the measurement and distribution of time INFORMATION ON UTC - TAI NO leap second will be introduced at the end of June 2023. The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is : from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37 s Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC, or to confirm that there will be no time step at the next possible date. Christian BIZOUARD Director Earth Orientation Center of IERS Observatoire de Paris, France

1 0

Maryland House Bill 165--permanent DST
by Arthur David Olson Jan. 19, 2023

Jan. 19, 2023

This year's session of the Maryland state legislature is off and running. On Monday, Delegate Crosby's bill 165 was read for the first time; it would put Maryland on permanent Daylight Saving Time. A similar bill was introduced last year; it passed the House but died in a Senate committee. The bill is contingent on federal enabling legislation and on adoption of permanent DST by neighboring jurisdictions. Once the contingencies are met, the bill specifies that "this Act shall take effect on the earlier of the second Sunday of March or the first Sunday of November." So yes, if the contingencies are met on October 31, there'd be less than a week's notice of cancellation of setting clocks back. I plan to be in touch with one of my representatives to suggest a parsimonious improvement: change "earlier" to "later." There are links to the bill's text and to a status page below. @dashdashado https://mgaleg.maryland.gov/2023rs/bills_noln/hb/fhb0165.pdf https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/hb0165?ys=2023rs

1 0

not getting proper timezone for few countries
by Bhardwaj, vanshika Jan. 18, 2023

Jan. 18, 2023

Hello , We are using tzdata vendor source latest version which is 2022g in our code ,which basically return the timezones value of the country as per the mapping but we found for few of the countries we are getting alphanumeric value as an output of time-zone, like if we select India so timezones we are getting for India is IST as an output which is expected ,but if we select brasalia so timezones for Brasalia we are getting is -03 , which is alpha-numeric value , so can u please tell us when u are going to add the timezones for the rest of the countries or it will be same. Hope u will reply soon. With Regards, Vanshika Bhardwaj Associate Engineer(Eaton)

2 1

Swiss time selectable for Germany
by Benjamin Drung Jan. 17, 2023

Jan. 17, 2023

Hi, I tried tzselect for Germany and was presented with following question: Please select one of the following timezones. 1) Swiss time 2) Germany (most areas), Scandinavia We do not use Swiss time in Germany. I did some research: Germany switched to summertime in 1980 and Swiss in 1981. There is Büsingen am Hochrhein which followed Swiss and therefore deviated from Germany only in 1980. Should zone1970.tab reflect the current status (i.e. drop DE from Europe/Zurich and rename "Germany (most areas)" to "Germany" in the comments)? -- Benjamin Drung Debian & Ubuntu Developer

10 23

[PROPOSED] Be more consistent about MSK/MSD
by Paul Eggert Jan. 17, 2023

Jan. 17, 2023

* NEWS: Mention this. * europe (Europe/Volgograd, Europe/Kirov): Use the abbreviations MSK/MSD when using Moscow time, since that’s what other Russian timezones do. This fixes an inconsistency introduced in 2016g. --- NEWS | 6 ++++++ europe | 18 +++++++++--------- 2 files changed, 15 insertions(+), 9 deletions(-) diff --git a/NEWS b/NEWS index 7bd80803..fc35046c 100644 --- a/NEWS +++ b/NEWS @@ -26,6 +26,12 @@ Unreleased, experimental changes since 1970. (Thanks to Almaz Mingaleev.) This affects some pre-1948 timestamps. The old data are now in 'backzone'. + Changes to past time zone abbreviations + + When observing Moscow time, Europe/Kirov and Europe/Volgograd now + use the abbreviations MSK/MSD instead of numeric abbreviations, + for consistency with other timezones observing Moscow time. + Changes to code You can now tell tzselect local time, to simplify later choices. diff --git a/europe b/europe index 89bc3a28..b784d0ee 100644 --- a/europe +++ b/europe @@ -2656,13 +2656,13 @@ Zone Europe/Volgograd 2:57:40 - LMT 1920 Jan 3 3:00 - +03 1930 Jun 21 4:00 - +04 1961 Nov 11 4:00 Russia +04/+05 1988 Mar 27 2:00s - 3:00 Russia +03/+04 1991 Mar 31 2:00s + 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 4:00 - +04 1992 Mar 29 2:00s - 3:00 Russia +03/+04 2011 Mar 27 2:00s - 4:00 - +04 2014 Oct 26 2:00s - 3:00 - +03 2018 Oct 28 2:00s + 3:00 Russia MSK/MSD 2011 Mar 27 2:00s + 4:00 - MSK 2014 Oct 26 2:00s + 3:00 - MSK 2018 Oct 28 2:00s 4:00 - +04 2020 Dec 27 2:00s - 3:00 - +03 + 3:00 - MSK # From Paul Eggert (2016-11-11): # Europe/Saratov covers: @@ -2693,11 +2693,11 @@ Zone Europe/Saratov 3:04:18 - LMT 1919 Jul 1 0:00u Zone Europe/Kirov 3:18:48 - LMT 1919 Jul 1 0:00u 3:00 - +03 1930 Jun 21 4:00 Russia +04/+05 1989 Mar 26 2:00s - 3:00 Russia +03/+04 1991 Mar 31 2:00s + 3:00 Russia MSK/MSD 1991 Mar 31 2:00s 4:00 - +04 1992 Mar 29 2:00s - 3:00 Russia +03/+04 2011 Mar 27 2:00s - 4:00 - +04 2014 Oct 26 2:00s - 3:00 - +03 + 3:00 Russia MSK/MSD 2011 Mar 27 2:00s + 4:00 - MSK 2014 Oct 26 2:00s + 3:00 - MSK # From Tim Parenti (2014-07-03), per Oscar van Vlijmen (2001-08-25): # Europe/Samara covers... -- 2.37.2

1 0

localtime_r multiple times slower for Europe/Moscow timezone
by Benjamin Drung Jan. 11, 2023

Jan. 11, 2023

Hi, a Ubuntu user has been reporting in https://launchpad.net/bugs/868395 that the Europe/Moscow timezone is multiple times slower than other timezones. Here is the example bug.c code: ``` #include <time.h> #include <stdio.h> int main() { time_t t = time(0); int i; struct tm result; for(i=0; i < 10000000; i++) localtime_r(&t, &result); puts(ctime(&t)); return 0; } ``` Compile and run this code: ``` gcc -o bug bug.c time TZ=Etc/UTC ./bug time TZ=Europe/Berlin ./bug time TZ=Europe/Moscow ./bug ``` The result on my machine is that Etc/UTC, Europe/Berlin, and other timezones take around 250 to 400 ms, but Europe/Moscow takes 1200 ms. The result is the same when running in a Debian unstable, Ubuntu 22.04 (jammy) and Ubuntu 23.04 (lunar) chroot. Is that a bug? If yes, is that a bug in glibc? -- Benjamin Drung Debian & Ubuntu Developer

5 6

[PROPOSED 1/2] Fix stray ‘\’ in tzselect
by Paul Eggert Jan. 11, 2023

Jan. 11, 2023

* tzselect.ksh: Remove stray backslash that messed up the wording of a diagnostic. This glitch was introduced in commit 13980693084c36e0275828d8d46d9d9e8975be0d dated Wed Jun 27 11:24:09 2018 -0700. --- tzselect.ksh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tzselect.ksh b/tzselect.ksh index 87baaa5..cbfc677 100644 --- a/tzselect.ksh +++ b/tzselect.ksh @@ -401,7 +401,7 @@ while BEGIN { FS = "\t" } { print $NF } '` - echo >&2 'Please select one of the following timezones,' \ + echo >&2 'Please select one of the following timezones,' echo >&2 'listed roughly in increasing order' \ "of distance from $coord". doselect $regions -- 2.39.0

1 1

[PROPOSED] Omit check_sorted dependencies no longer needed
by Paul Eggert Jan. 10, 2023

Jan. 10, 2023

* Makefile (check_sorted): Omit unnecessary dependencies on iso3166.tab, zone.tab, zone1970.tab. They should have been removed in commit 1bb4263bb1716fe3ba63b26600adc9c32f1fe16e dated 2019-06-22 13:55:46 -0700. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 8bee50d..721a745 100644 --- a/Makefile +++ b/Makefile @@ -837,7 +837,7 @@ check_slashed_abbrs: $(TDATA_TO_CHECK) CHECK_CC_LIST = { n = split($$1,a,/,/); for (i=2; i<=n; i++) print a[1], a[i]; } -check_sorted: backward backzone iso3166.tab zone.tab zone1970.tab +check_sorted: backward backzone $(AWK) '/^Link/ {printf "%.5d %s\n", g, $$3} !/./ {g++}' \ backward | LC_ALL=C sort -cu $(AWK) '/^Zone/ {print $$2}' backzone | LC_ALL=C sort -cu -- 2.39.0

1 0

(no subject)
by Alfred Finamore Jan. 10, 2023

Jan. 10, 2023

Request

1 0