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