Home | History | Annotate | Line # | Download | only in time
theory.html revision 1.21 
      1   1.4  christos <!DOCTYPE html>
      2   1.1  christos <html lang="en">
      3   1.1  christos <head>
      4   1.1  christos   <title>Theory and pragmatics of the tz code and data</title>
      5   1.1  christos   <meta charset="UTF-8">
      6   1.4  christos   <style>
      7   1.4  christos     pre {margin-left: 2em; white-space: pre-wrap;}
      8   1.4  christos   </style>
      9   1.1  christos </head>
     10   1.1  christos 
     11   1.1  christos <body>
     12   1.3  christos <h1>Theory and pragmatics of the <code><abbr>tz</abbr></code> code and data</h1>
     13   1.1  christos   <h3>Outline</h3>
     14   1.1  christos   <nav>
     15   1.1  christos     <ul>
     16   1.3  christos       <li><a href="#scope">Scope of the <code><abbr>tz</abbr></code>
     17   1.3  christos 	  database</a></li>
     18   1.7  christos       <li><a href="#naming">Timezone identifiers</a></li>
     19   1.1  christos       <li><a href="#abbreviations">Time zone abbreviations</a></li>
     20   1.3  christos       <li><a href="#accuracy">Accuracy of the <code><abbr>tz</abbr></code>
     21   1.3  christos 	  database</a></li>
     22   1.1  christos       <li><a href="#functions">Time and date functions</a></li>
     23   1.1  christos       <li><a href="#stability">Interface stability</a></li>
     24   1.9  christos       <li><a href="#leapsec">Leap seconds</a></li>
     25   1.1  christos       <li><a href="#calendar">Calendrical issues</a></li>
     26  1.18  christos       <li><a href="#planets">Time and time zones off earth</a></li>
     27   1.1  christos     </ul>
     28   1.1  christos   </nav>
     29   1.1  christos 
     30   1.3  christos <section>
     31   1.3  christos   <h2 id="scope">Scope of the <code><abbr>tz</abbr></code> database</h2>
     32   1.1  christos <p>
     33   1.3  christos The <a
     34   1.3  christos href="https://www.iana.org/time-zones"><code><abbr>tz</abbr></code>
     35   1.3  christos database</a> attempts to record the history and predicted future of
     36  1.10  christos civil time scales.
     37   1.3  christos It organizes <a href="tz-link.html">time zone and daylight saving time
     38   1.3  christos data</a> by partitioning the world into <a
     39   1.4  christos href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"><dfn>timezones</dfn></a>
     40   1.3  christos whose clocks all agree about timestamps that occur after the <a
     41   1.3  christos href="https://en.wikipedia.org/wiki/Unix_time">POSIX Epoch</a>
     42   1.3  christos (1970-01-01 00:00:00 <a
     43   1.3  christos href="https://en.wikipedia.org/wiki/Coordinated_Universal_Time"><abbr
     44   1.3  christos title="Coordinated Universal Time">UTC</abbr></a>).
     45   1.3  christos Although 1970 is a somewhat-arbitrary cutoff, there are significant
     46   1.3  christos challenges to moving the cutoff earlier even by a decade or two, due
     47   1.3  christos to the wide variety of local practices before computer timekeeping
     48   1.3  christos became prevalent.
     49  1.12  christos Most timezones correspond to a notable location and the database
     50  1.12  christos records all known clock transitions for that location;
     51  1.12  christos some timezones correspond instead to a fixed <abbr>UTC</abbr> offset.
     52   1.1  christos </p>
     53   1.1  christos 
     54   1.1  christos <p>
     55   1.4  christos Each timezone typically corresponds to a geographical region that is
     56   1.4  christos smaller than a traditional time zone, because clocks in a timezone
     57   1.4  christos all agree after 1970 whereas a traditional time zone merely
     58   1.4  christos specifies current standard time. For example, applications that deal
     59   1.4  christos with current and future timestamps in the traditional North
     60   1.4  christos American mountain time zone can choose from the timezones
     61   1.4  christos <code>America/Denver</code> which observes US-style daylight saving
     62  1.12  christos time (<abbr>DST</abbr>),
     63  1.12  christos and <code>America/Phoenix</code> which does not observe <abbr>DST</abbr>.
     64   1.4  christos Applications that also deal with past timestamps in the mountain time
     65   1.4  christos zone can choose from over a dozen timezones, such as
     66   1.4  christos <code>America/Boise</code>, <code>America/Edmonton</code>, and
     67   1.4  christos <code>America/Hermosillo</code>, each of which currently uses mountain
     68   1.4  christos time but differs from other timezones for some timestamps after 1970.
     69   1.4  christos </p>
     70   1.4  christos 
     71   1.4  christos <p>
     72  1.12  christos Clock transitions before 1970 are recorded for location-based timezones,
     73   1.1  christos because most systems support timestamps before 1970 and could
     74   1.1  christos misbehave if data entries were omitted for pre-1970 transitions.
     75   1.1  christos However, the database is not designed for and does not suffice for
     76   1.1  christos applications requiring accurate handling of all past times everywhere,
     77   1.1  christos as it would take far too much effort and guesswork to record all
     78   1.1  christos details of pre-1970 civil timekeeping.
     79   1.3  christos Although some information outside the scope of the database is
     80   1.2  christos collected in a file <code>backzone</code> that is distributed along
     81   1.2  christos with the database proper, this file is less reliable and does not
     82   1.2  christos necessarily follow database guidelines.
     83   1.1  christos </p>
     84   1.1  christos 
     85   1.1  christos <p>
     86   1.3  christos As described below, reference source code for using the
     87   1.3  christos <code><abbr>tz</abbr></code> database is also available.
     88   1.3  christos The <code><abbr>tz</abbr></code> code is upwards compatible with <a
     89   1.3  christos href="https://en.wikipedia.org/wiki/POSIX">POSIX</a>, an international
     90   1.3  christos standard for <a
     91   1.3  christos href="https://en.wikipedia.org/wiki/Unix">UNIX</a>-like systems.
     92  1.20  christos As of this writing, the current edition of POSIX is POSIX.1-2024,
     93  1.20  christos which has been published but not yet in HTML form.
     94  1.20  christos Unlike its predecessor POSIX.1-2017 (<a
     95   1.8  christos href="https://pubs.opengroup.org/onlinepubs/9699919799/"> The Open
     96   1.3  christos Group Base Specifications Issue 7</a>, IEEE Std 1003.1-2017, 2018
     97  1.20  christos Edition), POSIX.1-2024 requires support for the
     98  1.20  christos <code><abbr>tz</abbr></code> database, which has a
     99  1.20  christos model for describing civil time that is more complex than the
    100  1.20  christos standard and daylight saving times required by POSIX.1-2017.
    101   1.4  christos A <code><abbr>tz</abbr></code> timezone corresponds to a ruleset that can
    102   1.3  christos have more than two changes per year, these changes need not merely
    103   1.3  christos flip back and forth between two alternatives, and the rules themselves
    104   1.3  christos can change at times.
    105   1.9  christos Whether and when a timezone changes its clock,
    106   1.9  christos and even the timezone's notional base offset from <abbr>UTC</abbr>,
    107   1.9  christos are variable.
    108   1.4  christos It does not always make sense to talk about a timezone's
    109   1.4  christos "base offset", which is not necessarily a single number.
    110   1.1  christos </p>
    111   1.1  christos 
    112   1.3  christos </section>
    113   1.1  christos 
    114   1.3  christos <section>
    115   1.7  christos   <h2 id="naming">Timezone identifiers</h2>
    116   1.1  christos <p>
    117   1.7  christos Each timezone has a name that uniquely identifies the timezone.
    118   1.1  christos Inexperienced users are not expected to select these names unaided.
    119   1.1  christos Distributors should provide documentation and/or a simple selection
    120   1.4  christos interface that explains each name via a map or via descriptive text like
    121  1.10  christos "Czech Republic" instead of the timezone name "<code>Europe/Prague</code>".
    122   1.4  christos If geolocation information is available, a selection interface can
    123   1.4  christos locate the user on a timezone map or prioritize names that are
    124   1.4  christos geographically close. For an example selection interface, see the
    125   1.3  christos <code>tzselect</code> program in the <code><abbr>tz</abbr></code> code.
    126  1.21  christos Unicode's <a href="https://cldr.unicode.org">Common Locale Data
    127  1.21  christos Repository (<abbr>CLDR</abbr>)</a>
    128  1.21  christos contains data that may be useful for other selection
    129  1.10  christos interfaces; it maps timezone names like <code>Europe/Prague</code> to
    130  1.10  christos locale-dependent strings like "Prague", "Praha", "", and "".
    131   1.1  christos </p>
    132   1.1  christos 
    133   1.1  christos <p>
    134   1.3  christos The naming conventions attempt to strike a balance
    135   1.1  christos among the following goals:
    136   1.1  christos </p>
    137   1.3  christos 
    138   1.1  christos <ul>
    139   1.1  christos   <li>
    140   1.4  christos     Uniquely identify every timezone where clocks have agreed since 1970.
    141   1.3  christos     This is essential for the intended use: static clocks keeping local
    142   1.3  christos     civil time.
    143   1.1  christos   </li>
    144   1.1  christos   <li>
    145   1.4  christos     Indicate to experts where the timezone's clocks typically are.
    146   1.1  christos   </li>
    147   1.1  christos   <li>
    148   1.3  christos     Be robust in the presence of political changes.
    149   1.7  christos     For example, names are typically not tied to countries, to avoid
    150   1.3  christos     incompatibilities when countries change their name (e.g.,
    151   1.7  christos     Swaziland&rarr;Eswatini) or when locations change countries (e.g., Hong
    152   1.3  christos     Kong from UK colony to China).
    153   1.7  christos     There is no requirement that every country or national
    154   1.7  christos     capital must have a timezone name.
    155   1.1  christos   </li>
    156   1.1  christos   <li>
    157   1.3  christos     Be portable to a wide variety of implementations.
    158   1.1  christos   </li>
    159   1.1  christos   <li>
    160   1.3  christos     Use a consistent naming conventions over the entire world.
    161   1.1  christos   </li>
    162   1.1  christos </ul>
    163   1.3  christos 
    164   1.1  christos <p>
    165  1.20  christos Names normally have the format
    166   1.3  christos <var>AREA</var><code>/</code><var>LOCATION</var>, where
    167   1.4  christos <var>AREA</var> is a continent or ocean, and
    168   1.4  christos <var>LOCATION</var> is a specific location within the area.
    169   1.3  christos North and South America share the same area, '<code>America</code>'.
    170   1.3  christos Typical names are '<code>Africa/Cairo</code>',
    171   1.3  christos '<code>America/New_York</code>', and '<code>Pacific/Honolulu</code>'.
    172   1.3  christos Some names are further qualified to help avoid confusion; for example,
    173   1.3  christos '<code>America/Indiana/Petersburg</code>' distinguishes Petersburg,
    174   1.3  christos Indiana from other Petersburgs in America.
    175   1.1  christos </p>
    176   1.1  christos 
    177   1.1  christos <p>
    178   1.3  christos Here are the general guidelines used for
    179   1.4  christos choosing timezone names,
    180   1.1  christos in decreasing order of importance:
    181   1.1  christos </p>
    182   1.3  christos 
    183   1.1  christos <ul>
    184   1.1  christos   <li>
    185   1.3  christos     Use only valid POSIX file name components (i.e., the parts of
    186   1.3  christos     names other than '<code>/</code>').
    187   1.3  christos     Do not use the file name components '<code>.</code>' and
    188   1.3  christos     '<code>..</code>'.
    189   1.3  christos     Within a file name component, use only <a
    190   1.3  christos     href="https://en.wikipedia.org/wiki/ASCII">ASCII</a> letters,
    191   1.3  christos     '<code>.</code>', '<code>-</code>' and '<code>_</code>'.
    192   1.3  christos     Do not use digits, as that might create an ambiguity with <a
    193  1.20  christos     href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03">POSIX's proleptic
    194   1.3  christos     <code>TZ</code> strings</a>.
    195   1.3  christos     A file name component must not exceed 14 characters or start with
    196   1.3  christos     '<code>-</code>'.
    197  1.12  christos     E.g., prefer <code>America/Noronha</code> to
    198  1.12  christos     <code>America/Fernando_de_Noronha</code>.
    199   1.3  christos     Exceptions: see the discussion of legacy names below.
    200   1.1  christos   </li>
    201   1.1  christos   <li>
    202   1.3  christos     A name must not be empty, or contain '<code>//</code>', or
    203   1.3  christos     start or end with '<code>/</code>'.
    204  1.21  christos     Also, a name must not be '<code>Etc/Unknown</code>', as
    205  1.21  christos     <abbr>CLDR</abbr> uses that string for an unknown or invalid timezone.
    206   1.1  christos   </li>
    207   1.1  christos   <li>
    208   1.3  christos     Do not use names that differ only in case.
    209   1.3  christos     Although the reference implementation is case-sensitive, some
    210   1.3  christos     other implementations are not, and they would mishandle names
    211   1.3  christos     differing only in case.
    212   1.1  christos   </li>
    213   1.1  christos   <li>
    214   1.3  christos     If one name <var>A</var> is an initial prefix of another
    215   1.3  christos     name <var>AB</var> (ignoring case), then <var>B</var> must not
    216   1.3  christos     start with '<code>/</code>', as a regular file cannot have the
    217   1.3  christos     same name as a directory in POSIX.
    218   1.3  christos     For example, <code>America/New_York</code> precludes
    219   1.3  christos     <code>America/New_York/Bronx</code>.
    220   1.1  christos   </li>
    221   1.1  christos   <li>
    222   1.3  christos     Uninhabited regions like the North Pole and Bouvet Island
    223   1.3  christos     do not need locations, since local time is not defined there.
    224   1.1  christos   </li>
    225   1.1  christos   <li>
    226  1.21  christos     If all clocks in a region have agreed since 1970,
    227  1.21  christos     give them just one name even if some of the clocks disagreed before 1970,
    228  1.21  christos     or reside in different countries or in notable or faraway locations.
    229   1.3  christos     Otherwise these tables would become annoyingly large.
    230  1.21  christos     For example, do not create a name <code>Indian/Crozet</code>
    231  1.21  christos     as a near-duplicate or alias of <code>Asia/Dubai</code>
    232  1.21  christos     merely because they are different countries or territories,
    233  1.21  christos     or their clocks disagreed before 1970, or the
    234  1.21  christos     <a href="https://en.wikipedia.org/wiki/Crozet_Islands">Crozet Islands</a>
    235  1.21  christos     are notable in their own right,
    236  1.21  christos     or the Crozet Islands are not adjacent to other locations
    237  1.21  christos     that use <code>Asia/Dubai</code>.
    238   1.1  christos   </li>
    239   1.1  christos   <li>
    240   1.7  christos     If boundaries between regions are fluid, such as during a war or
    241   1.7  christos     insurrection, do not bother to create a new timezone merely
    242   1.7  christos     because of yet another boundary change. This helps prevent table
    243   1.7  christos     bloat and simplifies maintenance.
    244   1.7  christos   </li>
    245   1.7  christos   <li>
    246   1.3  christos     If a name is ambiguous, use a less ambiguous alternative;
    247   1.3  christos     e.g., many cities are named San Jos and Georgetown, so
    248   1.3  christos     prefer <code>America/Costa_Rica</code> to
    249   1.3  christos     <code>America/San_Jose</code> and <code>America/Guyana</code>
    250   1.3  christos     to <code>America/Georgetown</code>.
    251   1.1  christos   </li>
    252   1.1  christos   <li>
    253   1.3  christos     Keep locations compact.
    254   1.3  christos     Use cities or small islands, not countries or regions, so that any
    255   1.3  christos     future changes do not split individual locations into different
    256   1.4  christos     timezones.
    257   1.3  christos     E.g., prefer <code>Europe/Paris</code> to <code>Europe/France</code>,
    258   1.3  christos     since
    259   1.3  christos     <a href="https://en.wikipedia.org/wiki/Time_in_France#History">France
    260   1.3  christos     has had multiple time zones</a>.
    261   1.1  christos   </li>
    262   1.1  christos   <li>
    263   1.3  christos     Use mainstream English spelling, e.g., prefer
    264   1.4  christos     <code>Europe/Rome</code> to <code>Europa/Roma</code>, and
    265   1.3  christos     prefer <code>Europe/Athens</code> to the Greek
    266   1.4  christos     <code>/</code> or the Romanized
    267   1.4  christos     <code>Evrpi/Athna</code>.
    268   1.3  christos     The POSIX file name restrictions encourage this guideline.
    269   1.1  christos   </li>
    270   1.1  christos   <li>
    271   1.3  christos     Use the most populous among locations in a region,
    272   1.3  christos     e.g., prefer <code>Asia/Shanghai</code> to
    273   1.3  christos     <code>Asia/Beijing</code>.
    274   1.3  christos     Among locations with similar populations, pick the best-known
    275   1.3  christos     location, e.g., prefer <code>Europe/Rome</code> to
    276   1.3  christos     <code>Europe/Milan</code>.
    277   1.1  christos   </li>
    278   1.1  christos   <li>
    279   1.3  christos     Use the singular form, e.g., prefer <code>Atlantic/Canary</code> to
    280   1.3  christos     <code>Atlantic/Canaries</code>.
    281   1.1  christos   </li>
    282   1.1  christos   <li>
    283   1.3  christos     Omit common suffixes like '<code>_Islands</code>' and
    284   1.3  christos     '<code>_City</code>', unless that would lead to ambiguity.
    285   1.3  christos     E.g., prefer <code>America/Cayman</code> to
    286   1.3  christos     <code>America/Cayman_Islands</code> and
    287   1.3  christos     <code>America/Guatemala</code> to
    288   1.3  christos     <code>America/Guatemala_City</code>, but prefer
    289   1.3  christos     <code>America/Mexico_City</code> to
    290   1.3  christos     <code>America/Mexico</code>
    291   1.3  christos     because <a href="https://en.wikipedia.org/wiki/Time_in_Mexico">the
    292   1.3  christos     country of Mexico has several time zones</a>.
    293   1.1  christos   </li>
    294   1.1  christos   <li>
    295   1.3  christos     Use '<code>_</code>' to represent a space.
    296   1.1  christos   </li>
    297   1.1  christos   <li>
    298   1.3  christos     Omit '<code>.</code>' from abbreviations in names.
    299   1.3  christos     E.g., prefer <code>Atlantic/St_Helena</code> to
    300   1.3  christos     <code>Atlantic/St._Helena</code>.
    301   1.1  christos   </li>
    302   1.1  christos   <li>
    303   1.3  christos     Do not change established names if they only marginally violate
    304   1.3  christos     the above guidelines.
    305   1.3  christos     For example, do not change the existing name <code>Europe/Rome</code> to
    306   1.3  christos     <code>Europe/Milan</code> merely because Milan's population has grown
    307   1.3  christos     to be somewhat greater than Rome's.
    308   1.1  christos   </li>
    309   1.1  christos   <li>
    310   1.3  christos     If a name is changed, put its old spelling in the
    311  1.13  christos     '<code>backward</code>' file as a link to the new spelling.
    312   1.3  christos     This means old spellings will continue to work.
    313   1.9  christos     Ordinarily a name change should occur only in the rare case when
    314   1.9  christos     a location's consensus English-language spelling changes; for example,
    315   1.9  christos     in 2008 <code>Asia/Calcutta</code> was renamed to <code>Asia/Kolkata</code>
    316   1.9  christos     due to long-time widespread use of the new city name instead of the old.
    317   1.1  christos   </li>
    318   1.1  christos </ul>
    319   1.1  christos 
    320   1.1  christos <p>
    321   1.7  christos Guidelines have evolved with time, and names following old versions of
    322   1.8  christos these guidelines might not follow the current version. When guidelines
    323   1.7  christos have changed, old names continue to be supported. Guideline changes
    324   1.7  christos have included the following:
    325   1.1  christos </p>
    326   1.1  christos 
    327   1.7  christos <ul>
    328   1.7  christos <li>
    329   1.7  christos Older versions of this package used a different naming scheme.
    330   1.1  christos See the file '<code>backward</code>' for most of these older names
    331   1.1  christos (e.g., '<code>US/Eastern</code>' instead of '<code>America/New_York</code>').
    332   1.1  christos The other old-fashioned names still supported are
    333   1.3  christos '<code>WET</code>', '<code>CET</code>', '<code>MET</code>', and
    334   1.3  christos '<code>EET</code>' (see the file '<code>europe</code>').
    335   1.7  christos </li>
    336   1.1  christos 
    337   1.7  christos <li>
    338   1.1  christos Older versions of this package defined legacy names that are
    339   1.3  christos incompatible with the first guideline of location names, but which are
    340   1.3  christos still supported.
    341   1.3  christos These legacy names are mostly defined in the file
    342   1.3  christos '<code>etcetera</code>'.
    343   1.3  christos Also, the file '<code>backward</code>' defines the legacy names
    344  1.16  christos '<code>Etc/GMT0</code>', '<code>Etc/GMT-0</code>', '<code>Etc/GMT+0</code>',
    345   1.3  christos '<code>GMT0</code>', '<code>GMT-0</code>' and '<code>GMT+0</code>',
    346   1.3  christos and the file '<code>northamerica</code>' defines the legacy names
    347   1.3  christos '<code>EST5EDT</code>', '<code>CST6CDT</code>',
    348   1.3  christos '<code>MST7MDT</code>', and '<code>PST8PDT</code>'.
    349   1.7  christos </li>
    350   1.7  christos 
    351   1.7  christos <li>
    352   1.8  christos Older versions of these guidelines said that
    353   1.7  christos there should typically be at least one name for each <a
    354   1.7  christos href="https://en.wikipedia.org/wiki/ISO_3166-1"><abbr
    355   1.7  christos title="International Organization for Standardization">ISO</abbr>
    356   1.7  christos 3166-1</a> officially assigned two-letter code for an inhabited
    357   1.7  christos country or territory.
    358   1.7  christos This old guideline has been dropped, as it was not needed to handle
    359   1.7  christos timestamps correctly and it increased maintenance burden.
    360   1.7  christos </li>
    361   1.7  christos </ul>
    362   1.7  christos 
    363   1.7  christos <p>
    364  1.13  christos The file <code>zone1970.tab</code> lists geographical locations used
    365   1.7  christos to name timezones.
    366   1.7  christos It is intended to be an exhaustive list of names for geographic
    367   1.7  christos regions as described above; this is a subset of the timezones in the data.
    368  1.13  christos Although a <code>zone1970.tab</code> location's
    369   1.7  christos <a href="https://en.wikipedia.org/wiki/Longitude">longitude</a>
    370   1.7  christos corresponds to
    371   1.7  christos its <a href="https://en.wikipedia.org/wiki/Local_mean_time">local mean
    372   1.7  christos time (<abbr>LMT</abbr>)</a> offset with one hour for every 15&deg;
    373   1.7  christos east longitude, this relationship is not exact.
    374  1.13  christos The backward-compatibility file <code>zone.tab</code> is similar
    375  1.13  christos but conforms to the older-version guidelines related to <abbr>ISO</abbr> 3166-1;
    376  1.13  christos it lists only one country code per entry and unlike <code>zone1970.tab</code>
    377  1.13  christos it can list names defined in <code>backward</code>.
    378  1.19  christos Applications that process only timestamps from now on can instead use the file
    379  1.19  christos <code>zonenow.tab</code>, which partitions the world more coarsely,
    380  1.19  christos into regions where clocks agree now and in the predicted future;
    381  1.19  christos this file is smaller and simpler than <code>zone1970.tab</code>
    382  1.19  christos and <code>zone.tab</code>.
    383   1.1  christos </p>
    384   1.1  christos 
    385   1.1  christos <p>
    386  1.13  christos The database defines each timezone name to be a zone, or a link to a zone.
    387  1.13  christos The source file <code>backward</code> defines links for backward
    388  1.13  christos compatibility; it does not define zones.
    389  1.13  christos Although <code>backward</code> was originally designed to be optional,
    390  1.13  christos nowadays distributions typically use it
    391  1.13  christos and no great weight should be attached to whether a link
    392  1.13  christos is defined in <code>backward</code> or in some other file.
    393  1.13  christos The source file <code>etcetera</code> defines names that may be useful
    394  1.20  christos on platforms that do not support proleptic <code>TZ</code> strings
    395  1.20  christos like <code>&lt;+08&gt;-8</code>;
    396  1.13  christos no other source file other than <code>backward</code>
    397  1.13  christos contains links to its zones.
    398  1.14  christos One of <code>etcetera</code>'s names is <code>Etc/UTC</code>,
    399  1.13  christos used by functions like <code>gmtime</code> to obtain leap
    400  1.13  christos second information on platforms that support leap seconds.
    401  1.14  christos Another <code>etcetera</code> name, <code>GMT</code>,
    402  1.14  christos is used by older code releases.
    403   1.1  christos </p>
    404   1.3  christos </section>
    405   1.1  christos 
    406   1.3  christos <section>
    407   1.3  christos   <h2 id="abbreviations">Time zone abbreviations</h2>
    408   1.1  christos <p>
    409   1.1  christos When this package is installed, it generates time zone abbreviations
    410   1.1  christos like '<code>EST</code>' to be compatible with human tradition and POSIX.
    411   1.3  christos Here are the general guidelines used for choosing time zone abbreviations,
    412   1.1  christos in decreasing order of importance:
    413   1.3  christos </p>
    414   1.3  christos 
    415   1.1  christos <ul>
    416   1.1  christos   <li>
    417   1.3  christos     Use three to six characters that are ASCII alphanumerics or
    418   1.3  christos     '<code>+</code>' or '<code>-</code>'.
    419   1.3  christos     Previous editions of this database also used characters like
    420   1.3  christos     space and '<code>?</code>', but these characters have a
    421   1.3  christos     special meaning to the
    422   1.3  christos     <a href="https://en.wikipedia.org/wiki/Unix_shell">UNIX shell</a>
    423   1.3  christos     and cause commands like
    424   1.8  christos     '<code><a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#set">set</a>
    425   1.8  christos     `<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html">date</a>`</code>'
    426   1.3  christos     to have unexpected effects.
    427   1.3  christos     Previous editions of this guideline required upper-case letters, but the
    428   1.3  christos     Congressman who introduced
    429   1.3  christos     <a href="https://en.wikipedia.org/wiki/Chamorro_Time_Zone">Chamorro
    430   1.3  christos     Standard Time</a> preferred "ChST", so lower-case letters are now
    431   1.3  christos     allowed.
    432   1.3  christos     Also, POSIX from 2001 on relaxed the rule to allow '<code>-</code>',
    433   1.3  christos     '<code>+</code>', and alphanumeric characters from the portable
    434   1.3  christos     character set in the current locale.
    435   1.3  christos     In practice ASCII alphanumerics and '<code>+</code>' and
    436   1.3  christos     '<code>-</code>' are safe in all locales.
    437   1.3  christos 
    438   1.3  christos     <p>
    439   1.3  christos     In other words, in the C locale the POSIX extended regular
    440   1.3  christos     expression <code>[-+[:alnum:]]{3,6}</code> should match the
    441   1.3  christos     abbreviation.
    442  1.20  christos     This guarantees that all abbreviations could have been specified
    443  1.20  christos     explicitly by a POSIX proleptic <code>TZ</code> string.
    444   1.3  christos     </p>
    445   1.3  christos   </li>
    446   1.3  christos   <li>
    447   1.3  christos     Use abbreviations that are in common use among English-speakers,
    448   1.3  christos     e.g., 'EST' for Eastern Standard Time in North America.
    449   1.3  christos     We assume that applications translate them to other languages
    450   1.3  christos     as part of the normal localization process; for example,
    451   1.3  christos     a French application might translate 'EST' to 'HNE'.
    452   1.3  christos 
    453   1.3  christos     <p>
    454   1.3  christos     <small>These abbreviations (for standard/daylight/etc. time) are:
    455   1.3  christos       ACST/ACDT Australian Central,
    456   1.3  christos       AST/ADT/APT/AWT/ADDT Atlantic,
    457   1.3  christos       AEST/AEDT Australian Eastern,
    458   1.3  christos       AHST/AHDT Alaska-Hawaii,
    459   1.3  christos       AKST/AKDT Alaska,
    460   1.3  christos       AWST/AWDT Australian Western,
    461   1.3  christos       BST/BDT Bering,
    462   1.3  christos       CAT/CAST Central Africa,
    463   1.3  christos       CET/CEST/CEMT Central European,
    464   1.3  christos       ChST Chamorro,
    465  1.18  christos       CST/CDT/CWT/CPT Central [North America],
    466   1.3  christos       CST/CDT China,
    467   1.3  christos       GMT/BST/IST/BDST Greenwich,
    468   1.3  christos       EAT East Africa,
    469  1.18  christos       EST/EDT/EWT/EPT Eastern [North America],
    470   1.3  christos       EET/EEST Eastern European,
    471   1.6  christos       GST/GDT Guam,
    472   1.5  christos       HST/HDT/HWT/HPT Hawaii,
    473   1.9  christos       HKT/HKST/HKWT Hong Kong,
    474   1.3  christos       IST India,
    475   1.3  christos       IST/GMT Irish,
    476   1.3  christos       IST/IDT/IDDT Israel,
    477   1.3  christos       JST/JDT Japan,
    478   1.3  christos       KST/KDT Korea,
    479   1.3  christos       MET/MEST Middle European (a backward-compatibility alias for
    480   1.3  christos 	Central European),
    481   1.3  christos       MSK/MSD Moscow,
    482  1.18  christos       MST/MDT/MWT/MPT Mountain,
    483   1.3  christos       NST/NDT/NWT/NPT/NDDT Newfoundland,
    484   1.3  christos       NST/NDT/NWT/NPT Nome,
    485   1.3  christos       NZMT/NZST New Zealand through 1945,
    486   1.3  christos       NZST/NZDT New Zealand 1946&ndash;present,
    487   1.3  christos       PKT/PKST Pakistan,
    488  1.18  christos       PST/PDT/PWT/PPT Pacific,
    489   1.4  christos       PST/PDT Philippine,
    490   1.3  christos       SAST South Africa,
    491   1.3  christos       SST Samoa,
    492  1.14  christos       UTC Universal,
    493   1.3  christos       WAT/WAST West Africa,
    494   1.3  christos       WET/WEST/WEMT Western European,
    495   1.3  christos       WIB Waktu Indonesia Barat,
    496   1.3  christos       WIT Waktu Indonesia Timur,
    497   1.3  christos       WITA Waktu Indonesia Tengah,
    498   1.3  christos       YST/YDT/YWT/YPT/YDDT Yukon</small>.
    499   1.3  christos     </p>
    500   1.3  christos   </li>
    501   1.3  christos   <li>
    502   1.3  christos     <p>
    503   1.3  christos     For times taken from a city's longitude, use the
    504   1.3  christos     traditional <var>x</var>MT notation.
    505   1.3  christos     The only abbreviation like this in current use is '<abbr>GMT</abbr>'.
    506   1.3  christos     The others are for timestamps before 1960,
    507   1.3  christos     except that Monrovia Mean Time persisted until 1972.
    508   1.3  christos     Typically, numeric abbreviations (e.g., '<code>-</code>004430' for
    509   1.3  christos     MMT) would cause trouble here, as the numeric strings would exceed
    510   1.3  christos     the POSIX length limit.
    511   1.3  christos     </p>
    512   1.3  christos 
    513   1.3  christos     <p>
    514   1.3  christos     <small>These abbreviations are:
    515  1.12  christos       AMT Asuncin, Athens;
    516  1.18  christos       BMT Baghdad, Bangkok, Batavia, Bermuda, Bern, Bogot,
    517  1.11  christos         Brussels, Bucharest;
    518  1.12  christos       CMT Calamarca, Caracas, Chisinau, Coln, Crdoba;
    519   1.3  christos       DMT Dublin/Dunsink;
    520   1.3  christos       EMT Easter;
    521   1.3  christos       FFMT Fort-de-France;
    522   1.3  christos       FMT Funchal;
    523   1.3  christos       GMT Greenwich;
    524   1.3  christos       HMT Havana, Helsinki, Horta, Howrah;
    525   1.3  christos       IMT Irkutsk, Istanbul;
    526   1.3  christos       JMT Jerusalem;
    527  1.14  christos       KMT Kaunas, Kyiv, Kingston;
    528  1.18  christos       LMT Lima, Lisbon, local;
    529   1.3  christos       MMT Macassar, Madras, Mal, Managua, Minsk, Monrovia, Montevideo,
    530   1.3  christos 	Moratuwa, Moscow;
    531   1.3  christos       PLMT Ph Lin;
    532   1.3  christos       PMT Paramaribo, Paris, Perm, Pontianak, Prague;
    533   1.3  christos       PMMT Port Moresby;
    534  1.18  christos       PPMT Port-au-Prince;
    535   1.3  christos       QMT Quito;
    536   1.3  christos       RMT Rangoon, Riga, Rome;
    537   1.3  christos       SDMT Santo Domingo;
    538   1.3  christos       SJMT San Jos;
    539   1.3  christos       SMT Santiago, Simferopol, Singapore, Stanley;
    540   1.3  christos       TBMT Tbilisi;
    541   1.3  christos       TMT Tallinn, Tehran;
    542  1.18  christos       WMT Warsaw.</small>
    543   1.3  christos     </p>
    544   1.3  christos 
    545   1.3  christos     <p>
    546   1.3  christos     <small>A few abbreviations also follow the pattern that
    547   1.4  christos     <abbr>GMT</abbr>/<abbr>BST</abbr> established for time in the UK.
    548   1.3  christos     They are:
    549  1.11  christos       BMT/BST for Bermuda 1890&ndash;1930,
    550   1.3  christos       CMT/BST for Calamarca Mean Time and Bolivian Summer Time
    551   1.3  christos 	1890&ndash;1932,
    552   1.3  christos       DMT/IST for Dublin/Dunsink Mean Time and Irish Summer Time
    553   1.3  christos 	1880&ndash;1916,
    554   1.3  christos       MMT/MST/MDST for Moscow 1880&ndash;1919, and
    555   1.3  christos       RMT/LST for Riga Mean Time and Latvian Summer time 1880&ndash;1926.
    556  1.12  christos     </small>
    557   1.3  christos     </p>
    558   1.3  christos   </li>
    559   1.3  christos   <li>
    560   1.3  christos     Use '<abbr>LMT</abbr>' for local mean time of locations before the
    561   1.3  christos     introduction of standard time; see "<a href="#scope">Scope of the
    562   1.3  christos     <code><abbr>tz</abbr></code> database</a>".
    563   1.3  christos   </li>
    564   1.3  christos   <li>
    565   1.3  christos     If there is no common English abbreviation, use numeric offsets like
    566   1.4  christos     <code>-</code>05 and <code>+</code>0530 that are generated
    567   1.3  christos     by <code>zic</code>'s <code>%z</code> notation.
    568   1.3  christos   </li>
    569   1.3  christos   <li>
    570   1.3  christos     Use current abbreviations for older timestamps to avoid confusion.
    571   1.3  christos     For example, in 1910 a common English abbreviation for time
    572   1.3  christos     in central Europe was 'MEZ' (short for both "Middle European
    573   1.3  christos     Zone" and for "Mitteleuropische Zeit" in German).
    574   1.3  christos     Nowadays 'CET' ("Central European Time") is more common in
    575   1.3  christos     English, and the database uses 'CET' even for circa-1910
    576   1.3  christos     timestamps as this is less confusing for modern users and avoids
    577   1.3  christos     the need for determining when 'CET' supplanted 'MEZ' in common
    578   1.3  christos     usage.
    579   1.3  christos   </li>
    580   1.3  christos   <li>
    581   1.4  christos     Use a consistent style in a timezone's history.
    582   1.4  christos     For example, if a history tends to use numeric
    583   1.3  christos     abbreviations and a particular entry could go either way, use a
    584   1.3  christos     numeric abbreviation.
    585   1.3  christos   </li>
    586   1.3  christos   <li>
    587   1.3  christos     Use
    588   1.3  christos     <a href="https://en.wikipedia.org/wiki/Universal_Time">Universal Time</a>
    589   1.3  christos     (<abbr>UT</abbr>) (with time zone abbreviation '<code>-</code>00') for
    590   1.3  christos     locations while uninhabited.
    591   1.3  christos     The leading '<code>-</code>' is a flag that the <abbr>UT</abbr> offset is in
    592   1.3  christos     some sense undefined; this notation is derived
    593  1.21  christos     from <a href="https://www.rfc-editor.org/rfc/rfc3339">Internet
    594   1.4  christos     <abbr title="Request For Comments">RFC</abbr> 3339</a>.
    595  1.20  christos     (The abbreviation 'Z' that
    596  1.21  christos     <a href="https://www.rfc-editor.org/rfc/rfc9557">Internet
    597  1.20  christos     <abbr>RFC</abbr> 9557</a> uses for this concept
    598  1.20  christos     would violate the POSIX requirement
    599  1.20  christos     of at least three characters in an abbreviation.)
    600   1.1  christos   </li>
    601   1.1  christos </ul>
    602   1.3  christos 
    603   1.1  christos <p>
    604   1.1  christos Application writers should note that these abbreviations are ambiguous
    605   1.2  christos in practice: e.g., 'CST' means one thing in China and something else
    606   1.2  christos in North America, and 'IST' can refer to time in India, Ireland or
    607   1.3  christos Israel.
    608   1.3  christos To avoid ambiguity, use numeric <abbr>UT</abbr> offsets like
    609   1.2  christos '<code>-</code>0600' instead of time zone abbreviations like 'CST'.
    610   1.1  christos </p>
    611   1.3  christos </section>
    612   1.1  christos 
    613   1.3  christos <section>
    614   1.3  christos   <h2 id="accuracy">Accuracy of the <code><abbr>tz</abbr></code> database</h2>
    615   1.1  christos <p>
    616   1.3  christos The <code><abbr>tz</abbr></code> database is not authoritative, and it
    617   1.3  christos surely has errors.
    618   1.2  christos Corrections are welcome and encouraged; see the file <code>CONTRIBUTING</code>.
    619   1.1  christos Users requiring authoritative data should consult national standards
    620   1.1  christos bodies and the references cited in the database's comments.
    621   1.1  christos </p>
    622   1.1  christos 
    623   1.1  christos <p>
    624   1.3  christos Errors in the <code><abbr>tz</abbr></code> database arise from many sources:
    625   1.1  christos </p>
    626   1.3  christos 
    627   1.1  christos <ul>
    628   1.1  christos   <li>
    629   1.3  christos     The <code><abbr>tz</abbr></code> database predicts future
    630   1.3  christos     timestamps, and current predictions
    631   1.3  christos     will be incorrect after future governments change the rules.
    632   1.3  christos     For example, if today someone schedules a meeting for 13:00 next
    633   1.3  christos     October 1, Casablanca time, and tomorrow Morocco changes its
    634   1.3  christos     daylight saving rules, software can mess up after the rule change
    635   1.3  christos     if it blithely relies on conversions made before the change.
    636   1.3  christos   </li>
    637   1.3  christos   <li>
    638   1.3  christos     The pre-1970 entries in this database cover only a tiny sliver of how
    639   1.3  christos     clocks actually behaved; the vast majority of the necessary
    640   1.3  christos     information was lost or never recorded.
    641   1.4  christos     Thousands more timezones would be needed if
    642   1.3  christos     the <code><abbr>tz</abbr></code> database's scope were extended to
    643   1.3  christos     cover even just the known or guessed history of standard time; for
    644   1.3  christos     example, the current single entry for France would need to split
    645   1.3  christos     into dozens of entries, perhaps hundreds.
    646   1.3  christos     And in most of the world even this approach would be misleading
    647   1.3  christos     due to widespread disagreement or indifference about what times
    648   1.3  christos     should be observed.
    649   1.3  christos     In her 2015 book
    650   1.3  christos     <cite><a
    651  1.15  christos     href="https://www.hup.harvard.edu/catalog.php?isbn=9780674286146">The
    652   1.3  christos     Global Transformation of Time, 1870&ndash;1950</a></cite>,
    653   1.3  christos     Vanessa Ogle writes
    654   1.3  christos     "Outside of Europe and North America there was no system of time
    655   1.3  christos     zones at all, often not even a stable landscape of mean times,
    656   1.3  christos     prior to the middle decades of the twentieth century".
    657   1.3  christos     See: Timothy Shenk, <a
    658   1.3  christos href="https://www.dissentmagazine.org/blog/booked-a-global-history-of-time-vanessa-ogle">Booked:
    659   1.3  christos       A Global History of Time</a>. <cite>Dissent</cite> 2015-12-17.
    660   1.3  christos   </li>
    661   1.3  christos   <li>
    662   1.3  christos     Most of the pre-1970 data entries come from unreliable sources, often
    663   1.3  christos     astrology books that lack citations and whose compilers evidently
    664   1.3  christos     invented entries when the true facts were unknown, without
    665   1.3  christos     reporting which entries were known and which were invented.
    666   1.3  christos     These books often contradict each other or give implausible entries,
    667   1.3  christos     and on the rare occasions when they are checked they are
    668   1.3  christos     typically found to be incorrect.
    669   1.3  christos   </li>
    670   1.3  christos   <li>
    671   1.3  christos     For the UK the <code><abbr>tz</abbr></code> database relies on
    672   1.3  christos     years of first-class work done by
    673   1.3  christos     Joseph Myers and others; see
    674   1.3  christos     "<a href="https://www.polyomino.org.uk/british-time/">History of
    675   1.3  christos     legal time in Britain</a>".
    676   1.3  christos     Other countries are not done nearly as well.
    677   1.3  christos   </li>
    678   1.3  christos   <li>
    679   1.3  christos     Sometimes, different people in the same city maintain clocks
    680   1.3  christos     that differ significantly.
    681   1.3  christos     Historically, railway time was used by railroad companies (which
    682   1.3  christos     did not always
    683   1.3  christos     agree with each other), church-clock time was used for birth
    684   1.3  christos     certificates, etc.
    685   1.3  christos     More recently, competing political groups might disagree about
    686   1.3  christos     clock settings. Often this is merely common practice, but
    687   1.3  christos     sometimes it is set by law.
    688   1.3  christos     For example, from 1891 to 1911 the <abbr>UT</abbr> offset in France
    689   1.3  christos     was legally <abbr>UT</abbr> +00:09:21 outside train stations and
    690   1.3  christos     <abbr>UT</abbr> +00:04:21 inside. Other examples include
    691   1.3  christos     Chillicothe in 1920, Palm Springs in 1946/7, and Jerusalem and
    692   1.3  christos     rmqi to this day.
    693   1.3  christos   </li>
    694   1.3  christos   <li>
    695   1.3  christos     Although a named location in the <code><abbr>tz</abbr></code>
    696   1.3  christos     database stands for the containing region, its pre-1970 data
    697   1.3  christos     entries are often accurate for only a small subset of that region.
    698   1.3  christos     For example, <code>Europe/London</code> stands for the United
    699   1.3  christos     Kingdom, but its pre-1847 times are valid only for locations that
    700   1.3  christos     have London's exact meridian, and its 1847 transition
    701   1.3  christos     to <abbr>GMT</abbr> is known to be valid only for the L&amp;NW and
    702   1.3  christos     the Caledonian railways.
    703   1.3  christos   </li>
    704   1.3  christos   <li>
    705   1.3  christos     The <code><abbr>tz</abbr></code> database does not record the
    706   1.4  christos     earliest time for which a timezone's
    707   1.3  christos     data entries are thereafter valid for every location in the region.
    708   1.3  christos     For example, <code>Europe/London</code> is valid for all locations
    709   1.3  christos     in its region after <abbr>GMT</abbr> was made the standard time,
    710   1.3  christos     but the date of standardization (1880-08-02) is not in the
    711   1.3  christos     <code><abbr>tz</abbr></code> database, other than in commentary.
    712   1.4  christos     For many timezones the earliest time of
    713   1.3  christos     validity is unknown.
    714   1.3  christos   </li>
    715   1.3  christos   <li>
    716   1.3  christos     The <code><abbr>tz</abbr></code> database does not record a
    717   1.3  christos     region's boundaries, and in many cases the boundaries are not known.
    718   1.4  christos     For example, the timezone
    719   1.3  christos     <code>America/Kentucky/Louisville</code> represents a region
    720   1.3  christos     around the city of Louisville, the boundaries of which are
    721   1.3  christos     unclear.
    722   1.3  christos   </li>
    723   1.3  christos   <li>
    724   1.3  christos     Changes that are modeled as instantaneous transitions in the
    725   1.3  christos     <code><abbr>tz</abbr></code>
    726   1.3  christos     database were often spread out over hours, days, or even decades.
    727   1.3  christos   </li>
    728   1.3  christos   <li>
    729   1.3  christos     Even if the time is specified by law, locations sometimes
    730   1.3  christos     deliberately flout the law.
    731   1.3  christos   </li>
    732   1.3  christos   <li>
    733   1.3  christos     Early timekeeping practices, even assuming perfect clocks, were
    734   1.3  christos     often not specified to the accuracy that the
    735   1.3  christos     <code><abbr>tz</abbr></code> database requires.
    736   1.3  christos   </li>
    737   1.3  christos   <li>
    738  1.10  christos     The <code><abbr>tz</abbr></code> database cannot represent stopped clocks.
    739  1.10  christos     However, on 1911-03-11 at 00:00, some public-facing French clocks
    740  1.10  christos     were changed by stopping them for a few minutes to effect a transition.
    741  1.10  christos     The <code><abbr>tz</abbr></code> database models this via a
    742  1.10  christos     backward transition; the relevant French legislation does not
    743  1.10  christos     specify exactly how the transition was to occur.
    744  1.10  christos   </li>
    745  1.10  christos   <li>
    746   1.3  christos     Sometimes historical timekeeping was specified more precisely
    747   1.3  christos     than what the <code><abbr>tz</abbr></code> code can handle.
    748  1.12  christos     For example, from 1880 to 1916 clocks in Ireland observed Dublin Mean
    749   1.3  christos     Time (estimated to be <abbr>UT</abbr>
    750  1.14  christos     &minus;00:25:21.1); although the <code><abbr>tz</abbr></code>
    751  1.14  christos     source data can represent the .1 second, TZif files and the code cannot.
    752   1.3  christos     In practice these old specifications were rarely if ever
    753   1.3  christos     implemented to subsecond precision.
    754   1.3  christos   </li>
    755   1.3  christos   <li>
    756   1.3  christos     Even when all the timestamp transitions recorded by the
    757   1.3  christos     <code><abbr>tz</abbr></code> database are correct, the
    758   1.3  christos     <code><abbr>tz</abbr></code> rules that generate them may not
    759   1.3  christos     faithfully reflect the historical rules.
    760   1.3  christos     For example, from 1922 until World War II the UK moved clocks
    761   1.3  christos     forward the day following the third Saturday in April unless that
    762   1.3  christos     was Easter, in which case it moved clocks forward the previous
    763   1.3  christos     Sunday.
    764   1.3  christos     Because the <code><abbr>tz</abbr></code> database has no
    765   1.3  christos     way to specify Easter, these exceptional years are entered as
    766   1.3  christos     separate <code><abbr>tz</abbr> Rule</code> lines, even though the
    767   1.3  christos     legal rules did not change.
    768   1.4  christos     When transitions are known but the historical rules behind them are not,
    769   1.4  christos     the database contains <code>Zone</code> and <code>Rule</code>
    770   1.4  christos     entries that are intended to represent only the generated
    771   1.4  christos     transitions, not any underlying historical rules; however, this
    772   1.4  christos     intent is recorded at best only in commentary.
    773   1.3  christos   </li>
    774   1.3  christos   <li>
    775   1.4  christos     The <code><abbr>tz</abbr></code> database models time
    776   1.3  christos     using the <a
    777   1.3  christos     href="https://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar">proleptic
    778   1.4  christos     Gregorian calendar</a> with days containing 24 equal-length hours
    779   1.4  christos     numbered 00 through 23, except when clock transitions occur.
    780   1.4  christos     Pre-standard time is modeled as local mean time.
    781   1.4  christos     However, historically many people used other calendars and other timescales.
    782   1.3  christos     For example, the Roman Empire used
    783   1.3  christos     the <a href="https://en.wikipedia.org/wiki/Julian_calendar">Julian
    784   1.3  christos     calendar</a>,
    785   1.3  christos     and <a href="https://en.wikipedia.org/wiki/Roman_timekeeping">Roman
    786   1.3  christos     timekeeping</a> had twelve varying-length daytime hours with a
    787   1.3  christos     non-hour-based system at night.
    788   1.4  christos     And even today, some local practices diverge from the Gregorian
    789   1.4  christos     calendar with 24-hour days. These divergences range from
    790   1.4  christos     relatively minor, such as Japanese bars giving times like "24:30" for the
    791   1.4  christos     wee hours of the morning, to more-significant differences such as <a
    792  1.19  christos     href="https://theworld.org/stories/2015-01-30/if-you-have-meeting-ethiopia-you-better-double-check-time">the
    793   1.4  christos     east African practice of starting the day at dawn</a>, renumbering
    794   1.4  christos     the Western 06:00 to be 12:00. These practices are largely outside
    795   1.4  christos     the scope of the <code><abbr>tz</abbr></code> code and data, which
    796   1.4  christos     provide only limited support for date and time localization
    797  1.20  christos     such as that required by POSIX.
    798  1.12  christos     If <abbr>DST</abbr> is not used a different time zone
    799   1.4  christos     can often do the trick; for example, in Kenya a <code>TZ</code> setting
    800   1.4  christos     like <code>&lt;-03&gt;3</code> or <code>America/Cayenne</code> starts
    801   1.4  christos     the day six hours later than <code>Africa/Nairobi</code> does.
    802   1.3  christos   </li>
    803   1.3  christos   <li>
    804   1.3  christos     Early clocks were less reliable, and data entries do not represent
    805   1.3  christos     clock error.
    806   1.3  christos   </li>
    807   1.3  christos   <li>
    808   1.3  christos     The <code><abbr>tz</abbr></code> database assumes Universal Time
    809   1.3  christos     (<abbr>UT</abbr>) as an origin, even though <abbr>UT</abbr> is not
    810   1.3  christos     standardized for older timestamps.
    811   1.3  christos     In the <code><abbr>tz</abbr></code> database commentary,
    812   1.3  christos     <abbr>UT</abbr> denotes a family of time standards that includes
    813   1.3  christos     Coordinated Universal Time (<abbr>UTC</abbr>) along with other
    814   1.3  christos     variants such as <abbr>UT1</abbr> and <abbr>GMT</abbr>,
    815   1.3  christos     with days starting at midnight.
    816   1.3  christos     Although <abbr>UT</abbr> equals <abbr>UTC</abbr> for modern
    817   1.3  christos     timestamps, <abbr>UTC</abbr> was not defined until 1960, so
    818  1.18  christos     commentary uses the more general abbreviation <abbr>UT</abbr> for
    819   1.3  christos     timestamps that might predate 1960.
    820   1.3  christos     Since <abbr>UT</abbr>, <abbr>UT1</abbr>, etc. disagree slightly,
    821   1.3  christos     and since pre-1972 <abbr>UTC</abbr> seconds varied in length,
    822   1.3  christos     interpretation of older timestamps can be problematic when
    823   1.3  christos     subsecond accuracy is needed.
    824   1.3  christos   </li>
    825   1.3  christos   <li>
    826   1.3  christos     Civil time was not based on atomic time before 1972, and we do not
    827   1.3  christos     know the history of
    828   1.3  christos     <a href="https://en.wikipedia.org/wiki/Earth's_rotation">earth's
    829   1.3  christos     rotation</a> accurately enough to map <a
    830   1.3  christos     href="https://en.wikipedia.org/wiki/International_System_of_Units"><abbr
    831   1.3  christos     title="International System of Units">SI</abbr></a> seconds to
    832   1.3  christos     historical <a href="https://en.wikipedia.org/wiki/Solar_time">solar time</a>
    833   1.3  christos     to more than about one-hour accuracy.
    834   1.3  christos     See: Stephenson FR, Morrison LV, Hohenkerk CY.
    835   1.4  christos     <a href="https://dx.doi.org/10.1098/rspa.2016.0404">Measurement of
    836   1.3  christos     the Earth's rotation: 720 BC to AD 2015</a>.
    837  1.15  christos     <cite>Proc Royal Soc A</cite>. 2016;472:20160404.
    838   1.3  christos     Also see: Espenak F. <a
    839   1.3  christos     href="https://eclipse.gsfc.nasa.gov/SEhelp/uncertainty2004.html">Uncertainty
    840   1.3  christos     in Delta T (T)</a>.
    841   1.3  christos   </li>
    842   1.3  christos   <li>
    843   1.3  christos     The relationship between POSIX time (that is, <abbr>UTC</abbr> but
    844   1.3  christos     ignoring <a href="https://en.wikipedia.org/wiki/Leap_second">leap
    845  1.18  christos     seconds</a>) and <abbr>UTC</abbr> is not agreed upon.
    846  1.18  christos     This affects time stamps during the leap second era (1972&ndash;2035).
    847   1.3  christos     Although the POSIX
    848   1.3  christos     clock officially stops during an inserted leap second, at least one
    849   1.3  christos     proposed standard has it jumping back a second instead; and in
    850   1.3  christos     practice POSIX clocks more typically either progress glacially during
    851   1.3  christos     a leap second, or are slightly slowed while near a leap second.
    852   1.3  christos   </li>
    853   1.3  christos   <li>
    854   1.3  christos     The <code><abbr>tz</abbr></code> database does not represent how
    855   1.3  christos     uncertain its information is.
    856   1.3  christos     Ideally it would contain information about when data entries are
    857   1.3  christos     incomplete or dicey.
    858   1.3  christos     Partial temporal knowledge is a field of active research, though,
    859   1.3  christos     and it is not clear how to apply it here.
    860   1.1  christos   </li>
    861   1.1  christos </ul>
    862   1.1  christos 
    863   1.1  christos <p>
    864   1.3  christos In short, many, perhaps most, of the <code><abbr>tz</abbr></code>
    865   1.3  christos database's pre-1970 and future timestamps are either wrong or
    866   1.3  christos misleading.
    867   1.3  christos Any attempt to pass the
    868   1.3  christos <code><abbr>tz</abbr></code> database off as the definition of time
    869   1.3  christos should be unacceptable to anybody who cares about the facts.
    870   1.3  christos In particular, the <code><abbr>tz</abbr></code> database's
    871   1.3  christos <abbr>LMT</abbr> offsets should not be considered meaningful, and
    872   1.4  christos should not prompt creation of timezones
    873   1.3  christos merely because two locations
    874   1.3  christos differ in <abbr>LMT</abbr> or transitioned to standard time at
    875   1.3  christos different dates.
    876   1.3  christos </p>
    877   1.3  christos </section>
    878   1.3  christos 
    879   1.3  christos <section>
    880   1.3  christos   <h2 id="functions">Time and date functions</h2>
    881   1.3  christos <p>
    882   1.3  christos The <code><abbr>tz</abbr></code> code contains time and date functions
    883   1.3  christos that are upwards compatible with those of POSIX.
    884   1.3  christos Code compatible with this package is already
    885   1.3  christos <a href="tz-link.html#tzdb">part of many platforms</a>, where the
    886   1.3  christos primary use of this package is to update obsolete time-related files.
    887   1.3  christos To do this, you may need to compile the time zone compiler
    888  1.20  christos <code>zic</code> supplied with this package instead of using the
    889  1.20  christos system <code>zic</code>, since the format of <code>zic</code>'s
    890   1.3  christos input is occasionally extended, and a platform may still be shipping
    891   1.3  christos an older <code>zic</code>.
    892   1.1  christos </p>
    893   1.1  christos 
    894  1.20  christos <p>
    895  1.20  christos In POSIX, time display in a process is controlled by the
    896  1.20  christos environment variable <code>TZ</code>, which can have two forms:
    897  1.20  christos </p>
    898   1.1  christos <ul>
    899   1.1  christos   <li>
    900  1.20  christos     A <dfn>proleptic <code>TZ</code></dfn> value
    901  1.20  christos     like <code>CET-1CEST,M3.5.0,M10.5.0/3</code> uses a complex
    902  1.20  christos     notation that specifies a single standard time along with daylight
    903  1.20  christos     saving rules that apply to all years past, present, and future.
    904  1.20  christos   </li>
    905  1.20  christos   <li>
    906  1.20  christos     A <dfn>geographical <code>TZ</code></dfn> value
    907  1.20  christos     like <code>Europe/Berlin</code> names a location that stands for
    908  1.20  christos     civil time near that location, which can have more than
    909  1.20  christos     one standard time and more than one set of daylight saving rules,
    910  1.20  christos     to record timekeeping practice more accurately.
    911  1.20  christos     These names are defined by the <code><abbr>tz</abbr></code> database.
    912  1.20  christos   </li>
    913  1.20  christos </ul>
    914  1.20  christos 
    915  1.20  christos <h3 id="POSIX.1-2017">POSIX.1-2017 properties and limitations</h3>
    916  1.20  christos <p>
    917  1.20  christos Some platforms support only the features required by POSIX.1-2017,
    918  1.20  christos and have not yet upgraded to POSIX.1-2024.
    919  1.20  christos Code intended to be portable to these platforms must deal
    920  1.20  christos with problems that were fixed in later POSIX editions.
    921  1.20  christos </p>
    922  1.20  christos 
    923  1.20  christos <ul>
    924  1.20  christos   <li>
    925  1.20  christos     POSIX.1-2017 does not require support for geographical <code>TZ</code>,
    926  1.20  christos     and there is no convenient and efficient way to determine
    927  1.20  christos     the <abbr>UT</abbr> offset and time zone abbreviation of arbitrary
    928  1.20  christos     timestamps, particularly for timezones
    929  1.20  christos     that do not fit into the POSIX model.
    930  1.20  christos   </li>
    931  1.20  christos   <li>
    932   1.1  christos     <p>
    933  1.20  christos     The proleptic <code>TZ</code> string,
    934  1.20  christos     which is all that POSIX.1-2017 requires,
    935  1.20  christos     has a format that is hard to describe and is error-prone in practice.
    936  1.20  christos     Also, proleptic <code>TZ</code> strings cannot deal with daylight
    937   1.3  christos     saving time rules not based on the Gregorian calendar (as in
    938  1.18  christos     Morocco), or with situations where more than two time zone
    939   1.3  christos     abbreviations or <abbr>UT</abbr> offsets are used in an area.
    940   1.1  christos     </p>
    941   1.3  christos 
    942   1.1  christos     <p>
    943  1.20  christos     A proleptic <code>TZ</code> string has the following format:
    944   1.1  christos     </p>
    945   1.3  christos 
    946   1.1  christos     <p>
    947   1.3  christos     <var>stdoffset</var>[<var>dst</var>[<var>offset</var>][<code>,</code><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]]]
    948   1.1  christos     </p>
    949   1.3  christos 
    950   1.1  christos     <p>
    951   1.3  christos     where:
    952   1.3  christos     </p>
    953   1.3  christos 
    954   1.1  christos     <dl>
    955   1.1  christos       <dt><var>std</var> and <var>dst</var></dt><dd>
    956   1.3  christos 	are 3 or more characters specifying the standard
    957   1.4  christos 	and daylight saving time (<abbr>DST</abbr>) zone abbreviations.
    958   1.3  christos 	Starting with POSIX.1-2001, <var>std</var> and <var>dst</var>
    959   1.3  christos 	may also be in a quoted form like '<code>&lt;+09&gt;</code>';
    960   1.3  christos 	this allows "<code>+</code>" and "<code>-</code>" in the names.
    961   1.1  christos       </dd>
    962   1.1  christos       <dt><var>offset</var></dt><dd>
    963   1.3  christos 	is of the form
    964   1.3  christos 	'<code>[&plusmn;]<var>hh</var>:[<var>mm</var>[:<var>ss</var>]]</code>'
    965   1.3  christos 	and specifies the offset west of <abbr>UT</abbr>.
    966   1.3  christos 	'<var>hh</var>' may be a single digit;
    967   1.3  christos 	0&le;<var>hh</var>&le;24.
    968   1.3  christos 	The default <abbr>DST</abbr> offset is one hour ahead of
    969   1.3  christos 	standard time.
    970   1.1  christos       </dd>
    971   1.1  christos       <dt><var>date</var>[<code>/</code><var>time</var>]<code>,</code><var>date</var>[<code>/</code><var>time</var>]</dt><dd>
    972   1.3  christos 	specifies the beginning and end of <abbr>DST</abbr>.
    973   1.3  christos 	If this is absent, the system supplies its own ruleset
    974  1.18  christos 	for <abbr>DST</abbr>, typically	current <abbr>US</abbr>
    975  1.18  christos 	<abbr>DST</abbr> rules.
    976   1.1  christos       </dd>
    977   1.1  christos       <dt><var>time</var></dt><dd>
    978   1.3  christos 	takes the form
    979   1.3  christos 	'<var>hh</var><code>:</code>[<var>mm</var>[<code>:</code><var>ss</var>]]'
    980   1.3  christos 	and defaults to 02:00.
    981   1.3  christos 	This is the same format as the offset, except that a
    982   1.3  christos 	leading '<code>+</code>' or '<code>-</code>' is not allowed.
    983   1.1  christos       </dd>
    984   1.1  christos       <dt><var>date</var></dt><dd>
    985   1.3  christos 	takes one of the following forms:
    986   1.1  christos 	<dl>
    987   1.1  christos 	  <dt>J<var>n</var> (1&le;<var>n</var>&le;365)</dt><dd>
    988   1.3  christos 	    origin-1 day number not counting February 29
    989   1.3  christos 	  </dd>
    990   1.1  christos 	  <dt><var>n</var> (0&le;<var>n</var>&le;365)</dt><dd>
    991   1.3  christos 	    origin-0 day number counting February 29 if present
    992   1.3  christos 	  </dd>
    993   1.3  christos 	  <dt><code>M</code><var>m</var><code>.</code><var>n</var><code>.</code><var>d</var>
    994   1.3  christos 	    (0[Sunday]&le;<var>d</var>&le;6[Saturday], 1&le;<var>n</var>&le;5,
    995   1.3  christos 	    1&le;<var>m</var>&le;12)</dt><dd>
    996   1.3  christos 	    for the <var>d</var>th day of week <var>n</var> of
    997   1.3  christos 	    month <var>m</var> of the year, where week 1 is the first
    998   1.3  christos 	    week in which day <var>d</var> appears, and
    999   1.3  christos 	    '<code>5</code>' stands for the last week in which
   1000   1.3  christos 	    day <var>d</var> appears (which may be either the 4th or
   1001   1.3  christos 	    5th week).
   1002   1.3  christos 	    Typically, this is the only useful form; the <var>n</var>
   1003   1.3  christos 	    and <code>J</code><var>n</var> forms are rarely used.
   1004   1.1  christos 	  </dd>
   1005   1.3  christos 	</dl>
   1006   1.3  christos       </dd>
   1007   1.3  christos     </dl>
   1008   1.3  christos 
   1009   1.3  christos     <p>
   1010  1.20  christos     Here is an example proleptic <code>TZ</code> string for New
   1011   1.3  christos     Zealand after 2007.
   1012   1.3  christos     It says that standard time (<abbr>NZST</abbr>) is 12 hours ahead
   1013   1.3  christos     of <abbr>UT</abbr>, and that daylight saving time
   1014   1.3  christos     (<abbr>NZDT</abbr>) is observed from September's last Sunday at
   1015   1.3  christos     02:00 until April's first Sunday at 03:00:
   1016   1.3  christos     </p>
   1017   1.3  christos 
   1018   1.3  christos     <pre><code>TZ='NZST-12NZDT,M9.5.0,M4.1.0/3'</code></pre>
   1019   1.3  christos 
   1020   1.3  christos     <p>
   1021  1.20  christos     This proleptic <code>TZ</code> string is hard to remember, and
   1022   1.3  christos     mishandles some timestamps before 2008.
   1023  1.20  christos     With this package you can use a geographical <code>TZ</code> instead:
   1024   1.3  christos     </p>
   1025   1.3  christos 
   1026   1.3  christos     <pre><code>TZ='Pacific/Auckland'</code></pre>
   1027   1.3  christos   </li>
   1028  1.20  christos </ul>
   1029  1.20  christos 
   1030  1.20  christos <p>
   1031  1.20  christos POSIX.1-2017 also has the limitations of POSIX.1-2024,
   1032  1.20  christos discussed in the next section.
   1033  1.20  christos </p>
   1034  1.20  christos 
   1035  1.20  christos <h3 id="POSIX.1-2024">POSIX.1-2024 properties and limitations</h3>
   1036  1.20  christos <p>
   1037  1.20  christos POSIX.1-2024 extends POSIX.1-2017 in the following significant ways:
   1038  1.20  christos </p>
   1039  1.20  christos <ul>
   1040  1.20  christos   <li>
   1041  1.20  christos     POSIX.1-2024 requires support for geographical <code>TZ</code>.
   1042  1.20  christos     Earlier POSIX editions require support only for proleptic <code>TZ</code>.
   1043  1.20  christos   </li>
   1044  1.20  christos   <li>
   1045  1.20  christos     POSIX.1-2024 requires <code>struct tm</code>
   1046  1.20  christos     to have a <abbr>UT</abbr> offset member <code>tm_gmtoff</code>
   1047  1.20  christos     and a time zone abbreviation member <code>tm_zone</code>.
   1048  1.20  christos     Earlier POSIX editions lack this requirement.
   1049  1.20  christos   </li>
   1050   1.3  christos   <li>
   1051  1.20  christos     DST transition times can range from &minus;167:59:59
   1052  1.20  christos     to 167:59:59 instead of merely from 00:00:00 to 24:59:59.
   1053  1.20  christos     This allows for proleptic TZ strings
   1054  1.20  christos     like <code>"&lt;-02&gt;2&lt;-01&gt;,M3.5.0/-1,M10.5.0/0"</code>
   1055  1.20  christos     where the transition time &minus;1:00 means 23:00 the previous day.
   1056   1.3  christos   </li>
   1057  1.20  christos </ul>
   1058  1.20  christos <p>
   1059  1.20  christos However POSIX.1-2024, like earlier POSIX editions, has some limitations:
   1060  1.20  christos <ul>
   1061   1.3  christos   <li>
   1062   1.3  christos     The <code>TZ</code> environment variable is process-global, which
   1063   1.3  christos     makes it hard to write efficient, thread-safe applications that
   1064   1.4  christos     need access to multiple timezones.
   1065   1.3  christos   </li>
   1066   1.3  christos   <li>
   1067   1.3  christos     In POSIX, there is no tamper-proof way for a process to learn the
   1068   1.8  christos     system's best idea of local (wall clock) time.
   1069   1.4  christos     This is important for applications that an administrator wants
   1070   1.3  christos     used only at certain times &ndash; without regard to whether the
   1071   1.3  christos     user has fiddled the
   1072   1.3  christos     <code>TZ</code> environment variable.
   1073   1.3  christos     While an administrator can "do everything in <abbr>UT</abbr>" to
   1074   1.3  christos     get around the problem, doing so is inconvenient and precludes
   1075   1.4  christos     handling daylight saving time shifts &ndash; as might be required to
   1076   1.4  christos     limit phone calls to off-peak hours.
   1077   1.3  christos   </li>
   1078   1.3  christos   <li>
   1079  1.20  christos     POSIX requires that <code>time_t</code> clock counts exclude leap
   1080  1.20  christos     seconds.
   1081   1.3  christos   </li>
   1082   1.3  christos   <li>
   1083  1.20  christos     POSIX does not define the <abbr>DST</abbr> transitions
   1084  1.20  christos     for <code>TZ</code> values like
   1085  1.20  christos     "<code>EST5EDT</code>".
   1086  1.20  christos     Traditionally the current <abbr>US</abbr> <abbr>DST</abbr> rules
   1087  1.20  christos     were used to interpret such values, but this meant that the
   1088  1.20  christos     <abbr>US</abbr> <abbr>DST</abbr> rules were compiled into each
   1089  1.20  christos     time conversion package, and when
   1090  1.20  christos     <abbr>US</abbr> time conversion rules changed (as in the United
   1091  1.20  christos     States in 1987 and again in 2007), all packages that
   1092  1.20  christos     interpreted <code>TZ</code> values had to be updated
   1093  1.20  christos     to ensure proper results.
   1094   1.3  christos   </li>
   1095  1.20  christos </ul>
   1096  1.20  christos 
   1097  1.20  christos <h3 id="POSIX-extensions">Extensions to POSIX in the
   1098  1.20  christos <code><abbr>tz</abbr></code> code</h3>
   1099  1.20  christos <p>
   1100  1.20  christos   The <code><abbr>tz</abbr></code> code defines some properties
   1101  1.20  christos   left unspecified by POSIX, and attempts to support some
   1102  1.20  christos   extensions to POSIX.
   1103  1.20  christos </p>
   1104  1.20  christos 
   1105  1.20  christos <ul>
   1106   1.3  christos   <li>
   1107   1.3  christos     The <code><abbr>tz</abbr></code> code attempts to support all the
   1108   1.3  christos     <code>time_t</code> implementations allowed by POSIX.
   1109   1.3  christos     The <code>time_t</code> type represents a nonnegative count of seconds
   1110   1.3  christos     since 1970-01-01 00:00:00 <abbr>UTC</abbr>, ignoring leap seconds.
   1111   1.3  christos     In practice, <code>time_t</code> is usually a signed 64- or 32-bit
   1112   1.3  christos     integer; 32-bit signed <code>time_t</code> values stop working after
   1113   1.3  christos     2038-01-19 03:14:07 <abbr>UTC</abbr>, so new implementations these
   1114   1.3  christos     days typically use a signed 64-bit integer.
   1115   1.3  christos     Unsigned 32-bit integers are used on one or two platforms, and 36-bit
   1116   1.3  christos     and 40-bit integers are also used occasionally.
   1117   1.3  christos     Although earlier POSIX versions allowed <code>time_t</code> to be a
   1118   1.4  christos     floating-point type, this was not supported by any practical system,
   1119  1.20  christos     and POSIX.1-2013+ and the <code><abbr>tz</abbr></code> code both
   1120   1.3  christos     require <code>time_t</code> to be an integer type.
   1121   1.1  christos   </li>
   1122   1.1  christos   <li>
   1123   1.1  christos     <p>
   1124  1.20  christos     If the <code>TZ</code> environment variable uses the geographical format,
   1125  1.20  christos     it is used in generating
   1126  1.20  christos     the name of a file from which time-related information is read.
   1127   1.4  christos     The file's format is <dfn><abbr>TZif</abbr></dfn>,
   1128   1.7  christos     a timezone information format that contains binary data; see
   1129  1.21  christos     <a href="https://www.rfc-editor.org/rfc/9636">Internet
   1130  1.21  christos     <abbr>RFC</abbr> 9636</a>.
   1131   1.3  christos     The daylight saving time rules to be used for a
   1132   1.4  christos     particular timezone are encoded in the
   1133   1.4  christos     <abbr>TZif</abbr> file; the format of the file allows <abbr>US</abbr>,
   1134   1.4  christos     Australian, and other rules to be encoded, and
   1135   1.3  christos     allows for situations where more than two time zone
   1136   1.3  christos     abbreviations are used.
   1137   1.1  christos     </p>
   1138   1.1  christos     <p>
   1139  1.20  christos     When the <code><abbr>tz</abbr></code> code was developed in the 1980s,
   1140  1.20  christos     it was recognized that allowing the <code>TZ</code> environment
   1141   1.3  christos     variable to take on values such as '<code>America/New_York</code>'
   1142   1.3  christos     might cause "old" programs (that expect <code>TZ</code> to have a
   1143  1.20  christos     certain format) to operate incorrectly; consideration was given to using
   1144   1.3  christos     some other environment variable (for example, <code>TIMEZONE</code>)
   1145   1.4  christos     to hold the string used to generate the <abbr>TZif</abbr> file's name.
   1146   1.3  christos     In the end, however, it was decided to continue using
   1147   1.3  christos     <code>TZ</code>: it is widely used for time zone purposes;
   1148   1.3  christos     separately maintaining both <code>TZ</code>
   1149   1.3  christos     and <code>TIMEZONE</code> seemed a nuisance; and systems where
   1150   1.3  christos     "new" forms of <code>TZ</code> might cause problems can simply
   1151   1.4  christos     use legacy <code>TZ</code> values such as "<code>EST5EDT</code>" which
   1152   1.4  christos     can be used by "new" programs as well as by "old" programs that
   1153   1.4  christos     assume pre-POSIX <code>TZ</code> values.
   1154   1.1  christos     </p>
   1155   1.3  christos   </li>
   1156   1.3  christos   <li>
   1157   1.3  christos     Functions <code>tzalloc</code>, <code>tzfree</code>,
   1158   1.3  christos     <code>localtime_rz</code>, and <code>mktime_z</code> for
   1159   1.3  christos     more-efficient thread-safe applications that need to use multiple
   1160   1.4  christos     timezones.
   1161   1.3  christos     The <code>tzalloc</code> and <code>tzfree</code> functions
   1162   1.3  christos     allocate and free objects of type <code>timezone_t</code>,
   1163   1.3  christos     and <code>localtime_rz</code> and <code>mktime_z</code> are
   1164   1.3  christos     like <code>localtime_r</code> and <code>mktime</code> with an
   1165   1.3  christos     extra <code>timezone_t</code> argument.
   1166  1.20  christos     The functions were inspired by <a href="https://netbsd.org">NetBSD</a>.
   1167   1.3  christos   </li>
   1168   1.3  christos   <li>
   1169   1.3  christos     Negative <code>time_t</code> values are supported, on systems
   1170   1.3  christos     where <code>time_t</code> is signed.
   1171   1.3  christos   </li>
   1172   1.3  christos   <li>
   1173   1.9  christos     These functions can account for leap seconds;
   1174   1.9  christos     see <a href="#leapsec">Leap seconds</a> below.
   1175   1.3  christos   </li>
   1176   1.1  christos </ul>
   1177   1.3  christos 
   1178   1.3  christos <h3 id="vestigial">POSIX features no longer needed</h3>
   1179   1.1  christos <p>
   1180   1.3  christos POSIX and <a href="https://en.wikipedia.org/wiki/ISO_C"><abbr>ISO</abbr> C</a>
   1181   1.3  christos define some <a href="https://en.wikipedia.org/wiki/API"><abbr
   1182   1.3  christos title="application programming interface">API</abbr>s</a> that are vestigial:
   1183   1.3  christos they are not needed, and are relics of a too-simple model that does
   1184   1.3  christos not suffice to handle many real-world timestamps.
   1185   1.3  christos Although the <code><abbr>tz</abbr></code> code supports these
   1186   1.3  christos vestigial <abbr>API</abbr>s for backwards compatibility, they should
   1187   1.3  christos be avoided in portable applications.
   1188   1.3  christos The vestigial <abbr>API</abbr>s are:
   1189   1.1  christos </p>
   1190   1.1  christos <ul>
   1191   1.1  christos   <li>
   1192   1.3  christos     The POSIX <code>tzname</code> variable does not suffice and is no
   1193   1.3  christos     longer needed.
   1194  1.20  christos     It is planned to be removed in a future edition of POSIX.
   1195   1.3  christos     To get a timestamp's time zone abbreviation, consult
   1196   1.3  christos     the <code>tm_zone</code> member if available; otherwise,
   1197   1.3  christos     use <code>strftime</code>'s <code>"%Z"</code> conversion
   1198   1.3  christos     specification.
   1199   1.3  christos   </li>
   1200   1.3  christos   <li>
   1201   1.3  christos     The POSIX <code>daylight</code> and <code>timezone</code>
   1202   1.3  christos     variables do not suffice and are no longer needed.
   1203  1.20  christos     They are planned to be removed in a future edition of POSIX.
   1204   1.3  christos     To get a timestamp's <abbr>UT</abbr> offset, consult
   1205   1.3  christos     the <code>tm_gmtoff</code> member if available; otherwise,
   1206   1.3  christos     subtract values returned by <code>localtime</code>
   1207   1.3  christos     and <code>gmtime</code> using the rules of the Gregorian calendar,
   1208   1.3  christos     or use <code>strftime</code>'s <code>"%z"</code> conversion
   1209   1.3  christos     specification if a string like <code>"+0900"</code> suffices.
   1210   1.3  christos   </li>
   1211   1.3  christos   <li>
   1212   1.3  christos     The <code>tm_isdst</code> member is almost never needed and most of
   1213   1.3  christos     its uses should be discouraged in favor of the abovementioned
   1214   1.3  christos     <abbr>API</abbr>s.
   1215  1.21  christos     It was intended as an index into the <code>tzname</code> variable,
   1216  1.21  christos     but as mentioned previously that usage is obsolete.
   1217   1.3  christos     Although it can still be used in arguments to
   1218   1.3  christos     <code>mktime</code> to disambiguate timestamps near
   1219  1.15  christos     a <abbr>DST</abbr> transition when the clock jumps back on
   1220  1.15  christos     platforms lacking <code>tm_gmtoff</code>, this
   1221  1.21  christos     disambiguation works only for proleptic <code>TZ</code> strings;
   1222  1.21  christos     it does not work in general for geographical timezones,
   1223  1.21  christos     such as when a location changes to a time zone with a
   1224   1.3  christos     lesser <abbr>UT</abbr> offset.
   1225   1.3  christos   </li>
   1226   1.3  christos </ul>
   1227   1.3  christos 
   1228   1.3  christos <h3 id="other-portability">Other portability notes</h3>
   1229   1.3  christos <ul>
   1230   1.3  christos   <li>
   1231   1.3  christos     The <a href="https://en.wikipedia.org/wiki/Version_7_Unix">7th Edition
   1232   1.3  christos     UNIX</a> <code>timezone</code> function is not present in this
   1233   1.3  christos     package; it is impossible to reliably map <code>timezone</code>'s
   1234   1.3  christos     arguments (a "minutes west of <abbr>GMT</abbr>" value and a
   1235   1.3  christos     "daylight saving time in effect" flag) to a time zone
   1236   1.3  christos     abbreviation, and we refuse to guess.
   1237   1.3  christos     Programs that in the past used the <code>timezone</code> function
   1238   1.3  christos     may now examine <code>localtime(&amp;clock)-&gt;tm_zone</code>
   1239   1.3  christos     (if <code>TM_ZONE</code> is defined) or
   1240  1.21  christos     use <code>strftime</code> with a <code>%Z</code> conversion specification
   1241  1.21  christos     to learn the correct time
   1242   1.3  christos     zone abbreviation to use.
   1243   1.3  christos   </li>
   1244   1.3  christos   <li>
   1245   1.3  christos     The <a
   1246   1.3  christos     href="https://en.wikipedia.org/wiki/History_of_the_Berkeley_Software_Distribution#4.2BSD"><abbr>4.2BSD</abbr></a>
   1247   1.3  christos     <code>gettimeofday</code> function is not
   1248   1.3  christos     used in this package.
   1249   1.3  christos     This formerly let users obtain the current <abbr>UTC</abbr> offset
   1250   1.3  christos     and <abbr>DST</abbr> flag, but this functionality was removed in
   1251   1.3  christos     later versions of <abbr>BSD</abbr>.
   1252   1.3  christos   </li>
   1253   1.3  christos   <li>
   1254   1.3  christos     In <abbr>SVR2</abbr>, time conversion fails for near-minimum or
   1255   1.3  christos     near-maximum <code>time_t</code> values when doing conversions
   1256   1.3  christos     for places that do not use <abbr>UT</abbr>.
   1257   1.3  christos     This package takes care to do these conversions correctly.
   1258   1.3  christos     A comment in the source code tells how to get compatibly wrong
   1259   1.3  christos     results.
   1260   1.3  christos   </li>
   1261   1.3  christos   <li>
   1262   1.3  christos     The functions that are conditionally compiled
   1263  1.18  christos     if <code>STD_INSPIRED</code> is nonzero should, at this point, be
   1264   1.3  christos     looked on primarily as food for thought.
   1265   1.3  christos     They are not in any sense "standard compatible" &ndash; some are
   1266   1.3  christos     not, in fact, specified in <em>any</em> standard.
   1267   1.3  christos     They do, however, represent responses of various authors to
   1268   1.3  christos     standardization proposals.
   1269   1.3  christos   </li>
   1270   1.3  christos   <li>
   1271   1.4  christos     Other time conversion proposals, in particular those supported by the
   1272   1.4  christos     <a href="https://howardhinnant.github.io/date/tz.html">Time Zone
   1273   1.4  christos     Database Parser</a>, offer a wider selection of functions
   1274   1.3  christos     that provide capabilities beyond those provided here.
   1275   1.3  christos     The absence of such functions from this package is not meant to
   1276   1.3  christos     discourage the development, standardization, or use of such
   1277   1.3  christos     functions.
   1278   1.3  christos     Rather, their absence reflects the decision to make this package
   1279   1.3  christos     contain valid extensions to POSIX, to ensure its broad
   1280   1.3  christos     acceptability.
   1281   1.3  christos     If more powerful time conversion functions can be standardized, so
   1282   1.3  christos     much the better.
   1283   1.1  christos   </li>
   1284   1.1  christos </ul>
   1285   1.3  christos </section>
   1286   1.1  christos 
   1287   1.3  christos <section>
   1288   1.3  christos   <h2 id="stability">Interface stability</h2>
   1289   1.1  christos <p>
   1290   1.3  christos The <code><abbr>tz</abbr></code> code and data supply the following interfaces:
   1291   1.1  christos </p>
   1292   1.1  christos 
   1293   1.1  christos <ul>
   1294   1.1  christos   <li>
   1295   1.4  christos     A set of timezone names as per
   1296   1.7  christos       "<a href="#naming">Timezone identifiers</a>" above.
   1297   1.1  christos   </li>
   1298   1.1  christos   <li>
   1299   1.3  christos     Library functions described in "<a href="#functions">Time and date
   1300   1.3  christos       functions</a>" above.
   1301   1.1  christos   </li>
   1302   1.1  christos   <li>
   1303   1.3  christos     The programs <code>tzselect</code>, <code>zdump</code>,
   1304   1.3  christos     and <code>zic</code>, documented in their man pages.
   1305   1.1  christos   </li>
   1306   1.1  christos   <li>
   1307   1.3  christos     The format of <code>zic</code> input files, documented in
   1308   1.3  christos     the <code>zic</code> man page.
   1309   1.1  christos   </li>
   1310   1.1  christos   <li>
   1311   1.3  christos     The format of <code>zic</code> output files, documented in
   1312   1.3  christos     the <code>tzfile</code> man page.
   1313   1.1  christos   </li>
   1314   1.1  christos   <li>
   1315   1.3  christos     The format of zone table files, documented in <code>zone1970.tab</code>.
   1316   1.1  christos   </li>
   1317   1.1  christos   <li>
   1318   1.3  christos     The format of the country code file, documented in <code>iso3166.tab</code>.
   1319   1.1  christos   </li>
   1320   1.1  christos   <li>
   1321   1.3  christos     The version number of the code and data, as the first line of
   1322   1.3  christos     the text file '<code>version</code>' in each release.
   1323   1.1  christos   </li>
   1324   1.1  christos </ul>
   1325   1.3  christos 
   1326   1.1  christos <p>
   1327   1.1  christos Interface changes in a release attempt to preserve compatibility with
   1328   1.3  christos recent releases.
   1329   1.3  christos For example, <code><abbr>tz</abbr></code> data files typically do not
   1330  1.18  christos rely on recently added <code>zic</code> features, so that users can
   1331   1.3  christos run older <code>zic</code> versions to process newer data files.
   1332   1.3  christos <a href="tz-link.html#download">Downloading
   1333   1.3  christos the <code><abbr>tz</abbr></code> database</a> describes how releases
   1334   1.3  christos are tagged and distributed.
   1335   1.1  christos </p>
   1336   1.1  christos 
   1337   1.1  christos <p>
   1338   1.3  christos Interfaces not listed above are less stable.
   1339   1.3  christos For example, users should not rely on particular <abbr>UT</abbr>
   1340   1.3  christos offsets or abbreviations for timestamps, as data entries are often
   1341   1.3  christos based on guesswork and these guesses may be corrected or improved.
   1342   1.1  christos </p>
   1343   1.7  christos 
   1344   1.7  christos <p>
   1345   1.7  christos Timezone boundaries are not part of the stable interface.
   1346   1.7  christos For example, even though the <samp>Asia/Bangkok</samp> timezone
   1347   1.7  christos currently includes Chang Mai, Hanoi, and Phnom Penh, this is not part
   1348   1.7  christos of the stable interface and the timezone can split at any time.
   1349   1.7  christos If a calendar application records a future event in some location other
   1350   1.7  christos than Bangkok by putting "<samp>Asia/Bangkok</samp>" in the event's record,
   1351   1.7  christos the application should be robust in the presence of timezone splits
   1352   1.7  christos between now and the future time.
   1353   1.7  christos </p>
   1354   1.3  christos </section>
   1355   1.1  christos 
   1356   1.3  christos <section>
   1357   1.9  christos   <h2 id="leapsec">Leap seconds</h2>
   1358   1.9  christos <p>
   1359  1.18  christos Leap seconds were introduced in 1972 to accommodate the
   1360  1.18  christos difference between atomic time and the less regular rotation of the earth.
   1361  1.20  christos Unfortunately they have caused so many problems with civil
   1362  1.20  christos timekeeping that there are
   1363  1.20  christos <a href="https://www.bipm.org/en/cgpm-2022/resolution-4">plans
   1364  1.20  christos to discontinue them by 2035</a>.
   1365  1.20  christos Even if these plans come to fruition, a record of leap seconds will still be
   1366  1.20  christos needed to resolve timestamps from 1972 through 2035,
   1367  1.20  christos and there may also be a need to record whatever mechanism replaces them.
   1368  1.18  christos </p>
   1369  1.18  christos 
   1370  1.18  christos <p>
   1371   1.9  christos The <code><abbr>tz</abbr></code> code and data can account for leap seconds,
   1372   1.9  christos thanks to code contributed by Bradley White.
   1373   1.9  christos However, the leap second support of this package is rarely used directly
   1374   1.9  christos because POSIX requires leap seconds to be excluded and many
   1375   1.9  christos software packages would mishandle leap seconds if they were present.
   1376   1.9  christos Instead, leap seconds are more commonly handled by occasionally adjusting
   1377   1.9  christos the operating system kernel clock as described in
   1378   1.9  christos <a href="tz-link.html#precision">Precision timekeeping</a>,
   1379   1.9  christos and this package by default installs a <samp>leapseconds</samp> file
   1380   1.9  christos commonly used by
   1381  1.15  christos <a href="https://www.ntp.org"><abbr title="Network Time Protocol">NTP</abbr></a>
   1382   1.9  christos software that adjusts the kernel clock.
   1383   1.9  christos However, kernel-clock twiddling approximates UTC only roughly,
   1384  1.18  christos and systems needing more precise UTC can use this package's leap
   1385   1.9  christos second support directly.
   1386   1.9  christos </p>
   1387   1.9  christos 
   1388   1.9  christos <p>
   1389  1.18  christos The directly supported mechanism assumes that <code>time_t</code>
   1390   1.9  christos counts of seconds since the POSIX epoch normally include leap seconds,
   1391   1.9  christos as opposed to POSIX <code>time_t</code> counts which exclude leap seconds.
   1392   1.9  christos This modified timescale is converted to <abbr>UTC</abbr>
   1393  1.12  christos at the same point that time zone and <abbr>DST</abbr>
   1394  1.12  christos adjustments are applied &ndash;
   1395   1.9  christos namely, at calls to <code>localtime</code> and analogous functions &ndash;
   1396   1.9  christos and the process is driven by leap second information
   1397   1.9  christos stored in alternate versions of the <abbr>TZif</abbr> files.
   1398   1.9  christos Because a leap second adjustment may be needed even
   1399   1.9  christos if no time zone correction is desired,
   1400   1.9  christos calls to <code>gmtime</code>-like functions
   1401   1.9  christos also need to consult a <abbr>TZif</abbr> file,
   1402  1.14  christos conventionally named <samp><abbr>Etc/UTC</abbr></samp>
   1403  1.14  christos (<samp><abbr>GMT</abbr></samp> in previous versions),
   1404   1.9  christos to see whether leap second corrections are needed.
   1405   1.9  christos To convert an application's <code>time_t</code> timestamps to or from
   1406   1.9  christos POSIX <code>time_t</code> timestamps (for use when, say,
   1407   1.9  christos embedding or interpreting timestamps in portable
   1408   1.9  christos <a href="https://en.wikipedia.org/wiki/Tar_(computing)"><code>tar</code></a>
   1409   1.9  christos files),
   1410   1.9  christos the application can call the utility functions
   1411   1.9  christos <code>time2posix</code> and <code>posix2time</code>
   1412   1.9  christos included with this package.
   1413   1.9  christos </p>
   1414   1.9  christos 
   1415   1.9  christos <p>
   1416   1.9  christos If the POSIX-compatible <abbr>TZif</abbr> file set is installed
   1417   1.9  christos in a directory whose basename is <samp>zoneinfo</samp>, the
   1418   1.9  christos leap-second-aware file set is by default installed in a separate
   1419   1.9  christos directory <samp>zoneinfo-leaps</samp>.
   1420   1.9  christos Although each process can have its own time zone by setting
   1421   1.9  christos its <code>TZ</code> environment variable, there is no support for some
   1422   1.9  christos processes being leap-second aware while other processes are
   1423   1.9  christos POSIX-compatible; the leap-second choice is system-wide.
   1424   1.9  christos So if you configure your kernel to count leap seconds, you should also
   1425   1.9  christos discard <samp>zoneinfo</samp> and rename <samp>zoneinfo-leaps</samp>
   1426   1.9  christos to <samp>zoneinfo</samp>.
   1427   1.9  christos Alternatively, you can install just one set of <abbr>TZif</abbr> files
   1428   1.9  christos in the first place; see the <code>REDO</code> variable in this package's
   1429   1.9  christos <a href="https://en.wikipedia.org/wiki/Makefile">makefile</a>.
   1430   1.9  christos </p>
   1431   1.9  christos </section>
   1432   1.9  christos 
   1433   1.9  christos <section>
   1434   1.3  christos   <h2 id="calendar">Calendrical issues</h2>
   1435   1.1  christos <p>
   1436   1.1  christos Calendrical issues are a bit out of scope for a time zone database,
   1437   1.1  christos but they indicate the sort of problems that we would run into if we
   1438   1.3  christos extended the time zone database further into the past.
   1439   1.3  christos An excellent resource in this area is Edward M. Reingold
   1440   1.3  christos and Nachum Dershowitz, <cite><a
   1441   1.3  christos href="https://www.cambridge.org/fr/academic/subjects/computer-science/computing-general-interest/calendrical-calculations-ultimate-edition-4th-edition">Calendrical
   1442   1.3  christos Calculations: The Ultimate Edition</a></cite>, Cambridge University Press (2018).
   1443   1.3  christos Other information and sources are given in the file '<code>calendars</code>'
   1444   1.3  christos in the <code><abbr>tz</abbr></code> distribution.
   1445   1.3  christos They sometimes disagree.
   1446   1.3  christos </p>
   1447   1.3  christos </section>
   1448   1.3  christos 
   1449   1.3  christos <section>
   1450  1.18  christos   <h2 id="planets">Time and time zones off Earth</h2>
   1451  1.18  christos <p>
   1452  1.18  christos The European Space Agency is <a
   1453  1.18  christos href='https://www.esa.int/Applications/Navigation/Telling_time_on_the_Moon'>considering</a>
   1454  1.18  christos the establishment of a reference timescale for the Moon, which has
   1455  1.18  christos days roughly equivalent to 29.5 Earth days, and where relativistic
   1456  1.18  christos effects cause clocks to tick slightly faster than on Earth.
   1457  1.20  christos Also, <abbr title="National Aeronautics and Space Administration">NASA</abbr>
   1458  1.20  christos has been <a
   1459  1.20  christos href='https://www.whitehouse.gov/wp-content/uploads/2024/04/Celestial-Time-Standardization-Policy.pdf'>ordered</a>
   1460  1.20  christos to consider the establishment of Coordinated Lunar Time (<abbr>LTC</abbr>).
   1461  1.20  christos It is not yet known whether the US and European efforts will result in
   1462  1.20  christos multiple timescales on the Moon.
   1463  1.18  christos </p>
   1464  1.18  christos 
   1465   1.3  christos <p>
   1466  1.10  christos Some people's work schedules have used
   1467  1.10  christos <a href="https://en.wikipedia.org/wiki/Timekeeping_on_Mars">Mars time</a>.
   1468   1.3  christos Jet Propulsion Laboratory (JPL) coordinators kept Mars time on
   1469   1.3  christos and off during the
   1470   1.6  christos <a href="https://en.wikipedia.org/wiki/Mars_Pathfinder">Mars
   1471  1.10  christos Pathfinder</a> mission (1997).
   1472   1.3  christos Some of their family members also adapted to Mars time.
   1473   1.3  christos Dozens of special Mars watches were built for JPL workers who kept
   1474  1.10  christos Mars time during the
   1475  1.10  christos <a href="https://en.wikipedia.org/wiki/Mars_Exploration_Rover">Mars
   1476  1.10  christos Exploration Rovers (MER)</a> mission (2004&ndash;2018).
   1477  1.10  christos These timepieces looked like normal Seikos and Citizens but were adjusted
   1478  1.10  christos to use Mars seconds rather than terrestrial seconds, although
   1479  1.10  christos unfortunately the adjusted watches were unreliable and appear to have
   1480  1.10  christos had only limited use.
   1481   1.1  christos </p>
   1482   1.1  christos 
   1483   1.1  christos <p>
   1484   1.1  christos A Mars solar day is called a "sol" and has a mean period equal to
   1485   1.3  christos about 24 hours 39 minutes 35.244 seconds in terrestrial time.
   1486   1.3  christos It is divided into a conventional 24-hour clock, so each Mars second
   1487   1.3  christos equals about 1.02749125 terrestrial seconds.
   1488  1.10  christos (One MER worker noted, "If I am working Mars hours, and Mars hours are
   1489  1.10  christos 2.5% more than Earth hours, shouldn't I get an extra 2.5% pay raise?")
   1490   1.1  christos </p>
   1491   1.1  christos 
   1492   1.1  christos <p>
   1493   1.3  christos The <a href="https://en.wikipedia.org/wiki/Prime_meridian">prime
   1494   1.3  christos meridian</a> of Mars goes through the center of the crater
   1495   1.3  christos <a href="https://en.wikipedia.org/wiki/Airy-0">Airy-0</a>, named in
   1496   1.3  christos honor of the British astronomer who built the Greenwich telescope that
   1497   1.3  christos defines Earth's prime meridian.
   1498   1.3  christos Mean solar time on the Mars prime meridian is
   1499   1.6  christos called Mars Coordinated Time (<abbr>MTC</abbr>).
   1500   1.1  christos </p>
   1501   1.1  christos 
   1502   1.1  christos <p>
   1503   1.1  christos Each landed mission on Mars has adopted a different reference for
   1504   1.4  christos solar timekeeping, so there is no real standard for Mars time zones.
   1505  1.10  christos For example, the MER mission defined two time zones "Local
   1506   1.3  christos Solar Time A" and "Local Solar Time B" for its two missions, each zone
   1507   1.3  christos designed so that its time equals local true solar time at
   1508   1.3  christos approximately the middle of the nominal mission.
   1509  1.10  christos The A and B zones differ enough so that an MER worker assigned to
   1510  1.10  christos the A zone might suffer "Mars lag" when switching to work in the B zone.
   1511   1.3  christos Such a "time zone" is not particularly suited for any application
   1512   1.3  christos other than the mission itself.
   1513   1.1  christos </p>
   1514   1.1  christos 
   1515   1.1  christos <p>
   1516   1.1  christos Many calendars have been proposed for Mars, but none have achieved
   1517   1.3  christos wide acceptance.
   1518   1.3  christos Astronomers often use Mars Sol Date (<abbr>MSD</abbr>) which is a
   1519   1.1  christos sequential count of Mars solar days elapsed since about 1873-12-29
   1520   1.3  christos 12:00 <abbr>GMT</abbr>.
   1521   1.1  christos </p>
   1522   1.1  christos 
   1523   1.1  christos <p>
   1524   1.1  christos In our solar system, Mars is the planet with time and calendar most
   1525   1.3  christos like Earth's.
   1526   1.3  christos On other planets, Sun-based time and calendars would work quite
   1527   1.3  christos differently.
   1528   1.3  christos For example, although Mercury's
   1529   1.3  christos <a href="https://en.wikipedia.org/wiki/Rotation_period">sidereal
   1530   1.3  christos rotation period</a> is 58.646 Earth days, Mercury revolves around the
   1531   1.3  christos Sun so rapidly that an observer on Mercury's equator would see a
   1532   1.3  christos sunrise only every 175.97 Earth days, i.e., a Mercury year is 0.5 of a
   1533   1.3  christos Mercury day.
   1534   1.3  christos Venus is more complicated, partly because its rotation is slightly
   1535   1.3  christos <a href="https://en.wikipedia.org/wiki/Retrograde_motion">retrograde</a>:
   1536   1.3  christos its year is 1.92 of its days.
   1537   1.3  christos Gas giants like Jupiter are trickier still, as their polar and
   1538   1.3  christos equatorial regions rotate at different rates, so that the length of a
   1539   1.3  christos day depends on latitude.
   1540   1.3  christos This effect is most pronounced on Neptune, where the day is about 12
   1541   1.3  christos hours at the poles and 18 hours at the equator.
   1542   1.1  christos </p>
   1543   1.1  christos 
   1544   1.1  christos <p>
   1545   1.3  christos Although the <code><abbr>tz</abbr></code> database does not support
   1546   1.3  christos time on other planets, it is documented here in the hopes that support
   1547   1.3  christos will be added eventually.
   1548   1.1  christos </p>
   1549   1.1  christos 
   1550   1.1  christos <p>
   1551   1.3  christos Sources for time on other planets:
   1552   1.1  christos </p>
   1553   1.3  christos 
   1554   1.1  christos <ul>
   1555   1.1  christos   <li>
   1556   1.3  christos     Michael Allison and Robert Schmunk,
   1557   1.3  christos     "<a href="https://www.giss.nasa.gov/tools/mars24/help/notes.html">Technical
   1558   1.3  christos       Notes on Mars Solar Time as Adopted by the Mars24 Sunclock</a>"
   1559  1.10  christos     (2020-03-08).
   1560  1.10  christos   </li>
   1561  1.10  christos   <li>
   1562  1.10  christos     Zara Mirmalek,
   1563  1.10  christos     <em><a href="https://mitpress.mit.edu/books/making-time-mars">Making
   1564  1.10  christos 	Time on Mars</a></em>, MIT Press (March 2020), ISBN 978-0262043854.
   1565   1.1  christos   </li>
   1566   1.1  christos   <li>
   1567   1.3  christos     Jia-Rui Chong,
   1568   1.8  christos     "<a href="https://www.latimes.com/archives/la-xpm-2004-jan-14-sci-marstime14-story.html">Workdays
   1569   1.3  christos     Fit for a Martian</a>", <cite>Los Angeles Times</cite>
   1570   1.3  christos     (2004-01-14), pp A1, A20&ndash;A21.
   1571   1.1  christos   </li>
   1572   1.1  christos   <li>
   1573   1.3  christos     Tom Chmielewski,
   1574   1.3  christos     "<a href="https://www.theatlantic.com/technology/archive/2015/02/jet-lag-is-worse-on-mars/386033/">Jet
   1575   1.3  christos     Lag Is Worse on Mars</a>", <cite>The Atlantic</cite> (2015-02-26)
   1576   1.1  christos   </li>
   1577   1.1  christos   <li>
   1578   1.3  christos     Matt Williams,
   1579   1.3  christos     "<a href="https://www.universetoday.com/37481/days-of-the-planets/">How
   1580   1.3  christos     long is a day on the other planets of the solar system?</a>"
   1581   1.4  christos     (2016-01-20).
   1582   1.1  christos   </li>
   1583   1.1  christos </ul>
   1584   1.3  christos </section>
   1585   1.1  christos 
   1586   1.3  christos <footer>
   1587   1.3  christos   <hr>
   1588   1.3  christos   This file is in the public domain, so clarified as of 2009-05-17 by
   1589   1.3  christos   Arthur David Olson.
   1590   1.3  christos </footer>
   1591   1.1  christos </body>
   1592   1.1  christos </html>
   1593