--- 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
--- africa | 2 +- antarctica | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/africa b/africa index cfb9283c..90018808 100644 --- a/africa +++ b/africa @@ -1210,7 +1210,7 @@ Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 # https://libsysdigi.library.illinois.edu/ilharvest/Africana/Books2011-05/3064... # "On January 1st [1914], a universal standard time for Nigeria was adopted, # viz., half an hour fast on Greenwich mean time, corresponding to the meridian -# 7 [degrees] 30' E. long." +# 7° 30' E. long." # Lloyd's Register of Shipping (1915) says "Hitherto the time observed in Lagos # was the local mean time. On 1st January, 1914, standard time for the whole of # Nigeria was introduced ... Lagos time has been advanced about 16 minutes diff --git a/antarctica b/antarctica index f02755ae..fc603e99 100644 --- a/antarctica +++ b/antarctica @@ -292,7 +292,7 @@ Zone Antarctica/Rothera 0 - -00 1976 Dec 1 # but that he found it more convenient to keep GMT+12 # as supplies for the station were coming from McMurdo Sound, # which was on GMT+12 because New Zealand was on GMT+12 all year -# at that time (1957). (Source: Siple's book 90 Degrees South.) +# at that time (1957). (Source: Siple's book 90° South.) # # From Susan Smith # http://www.cybertours.com/whs/pole10.html -- 2.37.2
Hm, I don't think that using the degree symbol instead of something like [deg] or [degree] in source code (message texts or comments) is a good idea because the degree symbol is part of the extended character set which depends on code page currently selected by the user, and thus may be displayed correctly, or not. In one of my own projects which originates in the time when MS-DOS was current, I had used the degree and other symbols of the extended character set both in log message texts and in comments. If you look at those log messages or source code today with tools running on Windows, Linux, etc. these symbols were mostly displayed as garbage characters, so I just replaced them with "deg" etc., which is plain ASCII and thus always displayed correctly. So exactly the opposite of what is proposed here. Just my 2 ct, though. Martin Paul Eggert via tz wrote:
--- africa | 2 +- antarctica | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/africa b/africa index cfb9283c..90018808 100644 --- a/africa +++ b/africa @@ -1210,7 +1210,7 @@ Zone Africa/Windhoek 1:08:24 - LMT 1892 Feb 8 # https://libsysdigi.library.illinois.edu/ilharvest/Africana/Books2011-05/3064... # "On January 1st [1914], a universal standard time for Nigeria was adopted, # viz., half an hour fast on Greenwich mean time, corresponding to the meridian -# 7 [degrees] 30' E. long." +# 7° 30' E. long." # Lloyd's Register of Shipping (1915) says "Hitherto the time observed in Lagos # was the local mean time. On 1st January, 1914, standard time for the whole of # Nigeria was introduced ... Lagos time has been advanced about 16 minutes diff --git a/antarctica b/antarctica index f02755ae..fc603e99 100644 --- a/antarctica +++ b/antarctica @@ -292,7 +292,7 @@ Zone Antarctica/Rothera 0 - -00 1976 Dec 1 # but that he found it more convenient to keep GMT+12 # as supplies for the station were coming from McMurdo Sound, # which was on GMT+12 because New Zealand was on GMT+12 all year -# at that time (1957). (Source: Siple's book 90 Degrees South.) +# at that time (1957). (Source: Siple's book 90° South.) # # From Susan Smith # http://www.cybertours.com/whs/pole10.html
-- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki@meinberg.de Phone: +49 5281 9309-414 Linkedin: https://www.linkedin.com/in/martinburnicki/ Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Websites: https://www.meinberg.de https://www.meinbergglobal.com
On 1/24/23 00:52, Martin Burnicki wrote:
I don't think that using the degree symbol instead of something like [deg] or [degree] in source code (message texts or comments) is a good idea because the degree symbol is part of the extended character set which depends on code page currently selected by the user, and thus may be displayed correctly, or not.
As mentioned in NEWS, TZDB commentary has been using been using some UTF-8 encoded characters since release 2018d. The set of characters used has included ‘°’ (U+00B0 DEGREE SIGN). This doesn’t seem to have been much of a problem, as widespread support for UTF-8 has largely obsoleted problems with 8-bit encodings that rely on extended character sets and code pages. See, for example, <https://en.wikipedia.org/wiki/Popularity_of_text_encodings>. The recent patch catches a couple of instances of ‘°’ that I missed back in 2018.
On 1/24/23 16:08:33, Paul Eggert via tz wrote:
This doesn’t seem to have been much of a problem, as widespread support for UTF-8 has largely obsoleted problems with 8-bit encodings that rely on extended character sets and code pages. See, for example, <https://en.wikipedia.org/wiki/Popularity_of_text_encodings>.
While I remain a UTF-8 partisan, I concede that it doesn't play well with field widths in formatted output such as many implementations of printf().
The recent patch catches a couple of instances of ‘°’ that I missed back in 2018.
That came to my mail reader as <https://www.fileformat.info/info/unicode/char/b0/index.htm>. Had you composed it as such, or did an MTA fix it for you? -- gil
On 1/24/23 16:28, Paul Gilmartin via tz wrote:
The recent patch catches a couple of instances of ‘°’ that I missed back in 2018.
That came to my mail reader as <https://www.fileformat.info/info/unicode/char/b0/index.htm>. Had you composed it as such, or did an MTA fix it for you?
The former. I copied and pasted from TZDB’s source. I had originally composed it in the source by typing “C-x 8 RET DEGREE SIGN RET” into Emacs. Another way I could have typed it would have been “Caps-Lock o o” since I have Caps Lock bound to Compose in GNOME. However, Emacs supports arbitrary Unicode code points better than GNOME does so I tend to do things the Emacs way even though it’s more painful for this particular case. In writing this email I noticed that we don’t need UNUSUAL_OK_IPA any more. That macro was put in when the ‘europe’ file had the commentary “common pronunciation in Ukrainian, namely [ˈkɪjiu̯] (IPA)”. Since the commentary no longer opines on how to pronounce “Київ” in Ukrainian it no longer uses “u̯”, so I installed the attached further patch.
participants (3)
-
Martin Burnicki -
Paul Eggert -
Paul Gilmartin