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