- tz - lists.iana.org

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