Differences

This shows you the differences between two versions of the page.

--- balug:covid-19 [2026-05-10T17:40:43UTC] – [Virtual Meetings] rick_moen
+++ balug:covid-19 [2026-05-10T17:44:45UTC] (current) – [Timezone Conversion] rick_moen
@@ Line 109: / Line 109: @@
 Quoting //must be as shown//, and timezone //names// must be correct, or you will get errors or (worse) silent ignoring of the provided timezone qualifier.  Use [[https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List|canonical TZ database names]]. Do //not// use familiar 3- or 4-letter shortcut names like PST and PDT, as they are neither unique nor standardised -- nor UTC offsets like UTC-8, which for many locations have DST vs. Standard Time problems:  The short names' ambiguities become more troubling the more international one's focus is.  For example, "CST" can mean either China Standard Time (UTC+8), Cuba Standard Time (UTC−5), or (North American) Central Standard Time (UTC−6), and it is also a variant name for ACST (Australian Central Standard Time, UTC+9:30). Likewise, a time zone's short name will differ depending on language, as with WET (Western European Time, UTC+0), //also// known as WEZ (Westeuropäische Zeit) in German, HEO (Heure d'Europe occidentale) in French, ZEČ (Západoevropský čas) in Czech, and ΏΔΕ (Ώρα Δυτικής Ευρώπης) in Greek. Thus the short names' deprecated status.
-(As people have asked:  No, BSD date(1), as available on MacOS, cannot do this work, for lack of the -d option.)
+As people have asked:  No, BSD date(1), as available on MacOS, cannot do this work, for lack of the -d option.
 //However//, "homebrew" to the rescue:  If you [[https://brew.sh|install homebrew]] on your Mac and run "brew install coreutils" to install the GNU coreutils, then GNU date will become available as binary executable "gdate" (as will many other fine GNU enhancements).