2014-05-28 23:13:27 +04:00
|
|
|
.\" $NetBSD: zic.8,v 1.22 2014/05/28 19:13:27 christos Exp $
|
|
|
|
.Dd May 28, 2014
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dt ZIC 8
|
2009-03-09 22:24:26 +03:00
|
|
|
.Os
|
2001-09-16 22:02:44 +04:00
|
|
|
.Sh NAME
|
|
|
|
.Nm zic
|
|
|
|
.Nd time zone compiler
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
.Nm
|
2003-10-29 23:43:27 +03:00
|
|
|
.Op Fl \-version
|
2001-09-16 22:02:44 +04:00
|
|
|
.Op Fl d Ar directory
|
|
|
|
.Op Fl L Ar leapsecondfilename
|
|
|
|
.Op Fl l Ar localtime
|
|
|
|
.Op Fl p Ar posixrules
|
|
|
|
.Op Fl s
|
|
|
|
.Op Fl v
|
|
|
|
.Op Fl y Ar command
|
|
|
|
.Op Ar Filename ...
|
|
|
|
.Sh DESCRIPTION
|
|
|
|
.Nm
|
1995-03-10 10:08:14 +03:00
|
|
|
reads text from the file(s) named on the command line
|
|
|
|
and creates the time conversion information files specified in this input.
|
|
|
|
If a
|
2001-09-16 22:02:44 +04:00
|
|
|
.Ar filename
|
1995-03-10 10:08:14 +03:00
|
|
|
is
|
2001-09-16 22:02:44 +04:00
|
|
|
.Ar \&- ,
|
1995-03-10 10:08:14 +03:00
|
|
|
the standard input is read.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
These options are available:
|
2003-10-29 23:43:27 +03:00
|
|
|
.Bl -tag -width XXXXXXXXXX -compact
|
|
|
|
.It Fl \-version
|
|
|
|
Output version information and exit.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It Fl d Ar directory
|
1995-03-10 10:08:14 +03:00
|
|
|
Create time conversion information files in the named directory rather than
|
|
|
|
in the standard directory named below.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It Fl L Ar leapsecondfilename
|
|
|
|
Read leap second information from the file with the given name.
|
|
|
|
If this option is not used,
|
|
|
|
no leap second information appears in output files.
|
|
|
|
.It Fl l Ar timezone
|
1995-03-10 10:08:14 +03:00
|
|
|
Use the given time zone as local time.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Nm
|
1995-03-10 10:08:14 +03:00
|
|
|
will act as if the input contained a link line of the form
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Link timezone localtime
|
|
|
|
.It Fl p Ar timezone
|
1995-03-10 10:08:14 +03:00
|
|
|
Use the given time zone's rules when handling POSIX-format
|
|
|
|
time zone environment variables.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Nm
|
1995-03-10 10:08:14 +03:00
|
|
|
will act as if the input contained a link line of the form
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Link timezone posixrules
|
|
|
|
.It Fl s
|
1995-03-10 10:08:14 +03:00
|
|
|
Limit time values stored in output files to values that are the same
|
|
|
|
whether they're taken to be signed or unsigned.
|
|
|
|
You can use this option to generate SVVS-compatible files.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It Fl v
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
Be more verbose, and complain about the following situations:
|
|
|
|
.Bl -dash
|
|
|
|
.It The input data specifies a link to a link.
|
|
|
|
.It A year that appears in a data file is outside the range
|
|
|
|
.It A time of 24:00 or more appears in the input.
|
|
|
|
Pre-1998 versions of
|
|
|
|
.Xr zic 8
|
|
|
|
prohibit 24:00, and pre-2007 versions prohibit times greater than 24:00.
|
|
|
|
.It A rule goes past the start or end of the month.
|
|
|
|
Pre-2004 versions of
|
|
|
|
.Xr zic 8
|
|
|
|
prohibit this.
|
|
|
|
.It The output file does not contain all the information about the
|
|
|
|
long-term future of a zone, because the future cannot be summarized as
|
|
|
|
an extended POSIX TZ string.
|
|
|
|
For example, as of 2013 this problem
|
|
|
|
occurs for Iran's daylight-saving rules for the predicted future, as
|
|
|
|
these rules are based on the Iranian calendar, which cannot be
|
|
|
|
represented.
|
|
|
|
.It The output contains data that may not be handled properly by client
|
|
|
|
code designed for older
|
|
|
|
.Xr zic 8
|
|
|
|
output formats.
|
|
|
|
These compatibility issues affect only time stamps
|
|
|
|
before 1970 or after the start of 2038.
|
|
|
|
.It A time zone abbreviation has fewer than 3 characters.
|
|
|
|
POSIX requires at least 3.
|
|
|
|
.El
|
2001-09-16 22:02:44 +04:00
|
|
|
.It Fl y Ar command
|
1995-03-10 10:08:14 +03:00
|
|
|
Use the given
|
2001-09-16 22:02:44 +04:00
|
|
|
.Ar command
|
1995-03-10 10:08:14 +03:00
|
|
|
rather than
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em yearistype
|
1995-03-10 10:08:14 +03:00
|
|
|
when checking year types (see below).
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
Input lines are made up of fields.
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
Fields are separated from one another by one or more white space characters.
|
1995-03-10 10:08:14 +03:00
|
|
|
Leading and trailing white space on input lines is ignored.
|
|
|
|
An unquoted sharp character (#) in the input introduces a comment which extends
|
|
|
|
to the end of the line the sharp character appears on.
|
2001-09-16 22:02:44 +04:00
|
|
|
White space characters and sharp characters may be enclosed in double
|
|
|
|
quotes
|
|
|
|
.Pq \&"
|
|
|
|
.\" XXX "
|
|
|
|
if they're to be used as part of a field.
|
1995-03-10 10:08:14 +03:00
|
|
|
Any line that is blank (after comment stripping) is ignored.
|
|
|
|
Non-blank lines are expected to be of one of three types:
|
|
|
|
rule lines, zone lines, and link lines.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
2011-09-04 14:10:26 +04:00
|
|
|
Names (such as month names) must be in English and are case insensitive.
|
|
|
|
Abbreviations, if used, must be unambiguous in context.
|
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
A rule line has the form
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
|
1995-03-10 10:08:14 +03:00
|
|
|
For example:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
|
1995-03-10 10:08:14 +03:00
|
|
|
The fields that make up a rule line are:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Bl -tag -width "LETTER/S" -compact
|
|
|
|
.It NAME
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the (arbitrary) name of the set of rules this rule is part of.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It FROM
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the first year in which the rule applies.
|
|
|
|
Any integer year can be supplied; the Gregorian calendar is assumed.
|
|
|
|
The word
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em minimum
|
1995-03-10 10:08:14 +03:00
|
|
|
(or an abbreviation) means the minimum year representable as an integer.
|
|
|
|
The word
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em maximum
|
1995-03-10 10:08:14 +03:00
|
|
|
(or an abbreviation) means the maximum year representable as an integer.
|
|
|
|
Rules can describe times that are not representable as time values,
|
|
|
|
with the unrepresentable times ignored; this allows rules to be portable
|
|
|
|
among hosts with differing time value types.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It TO
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the final year in which the rule applies.
|
|
|
|
In addition to
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em minimum
|
1995-03-10 10:08:14 +03:00
|
|
|
and
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em maximum
|
1995-03-10 10:08:14 +03:00
|
|
|
(as above),
|
|
|
|
the word
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em only
|
1995-03-10 10:08:14 +03:00
|
|
|
(or an abbreviation)
|
|
|
|
may be used to repeat the value of the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em FROM
|
1995-03-10 10:08:14 +03:00
|
|
|
field.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It TYPE
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the type of year in which the rule applies.
|
|
|
|
If
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em TYPE
|
1995-03-10 10:08:14 +03:00
|
|
|
is
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em \&-
|
1995-03-10 10:08:14 +03:00
|
|
|
then the rule applies in all years between
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em FROM
|
1995-03-10 10:08:14 +03:00
|
|
|
and
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em TO
|
1995-03-10 10:08:14 +03:00
|
|
|
inclusive.
|
|
|
|
If
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em TYPE
|
1995-03-10 10:08:14 +03:00
|
|
|
is something else, then
|
2001-09-16 22:02:44 +04:00
|
|
|
.Nm
|
1995-03-10 10:08:14 +03:00
|
|
|
executes the command
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
|
|
|
.Ic yearistype Ar year type
|
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
to check the type of a year:
|
|
|
|
an exit status of zero is taken to mean that the year is of the given type;
|
|
|
|
an exit status of one is taken to mean that the year is not of the given type.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It IN
|
1995-03-10 10:08:14 +03:00
|
|
|
Names the month in which the rule takes effect.
|
|
|
|
Month names may be abbreviated.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It ON
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the day on which the rule takes effect.
|
|
|
|
Recognized forms include:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Bl -tag -width lastSun -compact -offset indent
|
|
|
|
.It 5
|
|
|
|
the fifth of the month
|
|
|
|
.It lastSun
|
|
|
|
the last Sunday in the month
|
|
|
|
.It lastMon
|
|
|
|
the last Monday in the month
|
2002-02-08 04:21:55 +03:00
|
|
|
.It Sun\*[Ge]8
|
2001-09-16 22:02:44 +04:00
|
|
|
first Sunday on or after the eighth
|
2002-02-08 04:21:55 +03:00
|
|
|
.It Sun\*[Le]25
|
2001-09-16 22:02:44 +04:00
|
|
|
last Sunday on or before the 25th
|
|
|
|
.El
|
1995-03-10 10:08:14 +03:00
|
|
|
Names of days of the week may be abbreviated or spelled out in full.
|
|
|
|
Note that there must be no spaces within the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em ON
|
1995-03-10 10:08:14 +03:00
|
|
|
field.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It AT
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the time of day at which the rule takes effect.
|
|
|
|
Recognized forms include:
|
2003-06-30 16:02:08 +04:00
|
|
|
.Bl -tag -width "1X28X14" -compact -offset indent
|
2001-09-16 22:02:44 +04:00
|
|
|
.It 2
|
|
|
|
time in hours
|
|
|
|
.It 2:00
|
|
|
|
time in hours and minutes
|
|
|
|
.It 15:00
|
|
|
|
24-hour format time (for times after noon)
|
|
|
|
.It 1:28:14
|
|
|
|
time in hours, minutes, and seconds
|
|
|
|
.It \-
|
|
|
|
equivalent to 0
|
|
|
|
.El
|
1998-10-04 23:27:55 +04:00
|
|
|
where hour 0 is midnight at the start of the day,
|
|
|
|
and hour 24 is midnight at the end of the day.
|
1995-03-10 10:08:14 +03:00
|
|
|
Any of these forms may be followed by the letter
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em w
|
1995-03-10 10:08:14 +03:00
|
|
|
if the given time is local
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq wall clock
|
1995-03-10 10:08:14 +03:00
|
|
|
time,
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em s
|
1995-03-10 10:08:14 +03:00
|
|
|
if the given time is local
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq standard
|
1995-03-10 10:08:14 +03:00
|
|
|
time, or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em u
|
1995-03-10 10:08:14 +03:00
|
|
|
(or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em g
|
1995-03-10 10:08:14 +03:00
|
|
|
or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em z )
|
1995-03-10 10:08:14 +03:00
|
|
|
if the given time is universal time;
|
|
|
|
in the absence of an indicator,
|
|
|
|
wall clock time is assumed.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It SAVE
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the amount of time to be added to local standard time when the rule is in
|
|
|
|
effect.
|
|
|
|
This field has the same format as the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em AT
|
1995-03-10 10:08:14 +03:00
|
|
|
field
|
|
|
|
(although, of course, the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em w
|
1995-03-10 10:08:14 +03:00
|
|
|
and
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em s
|
1995-03-10 10:08:14 +03:00
|
|
|
suffixes are not used).
|
2001-09-16 22:02:44 +04:00
|
|
|
.It LETTER/S
|
1995-03-10 10:08:14 +03:00
|
|
|
Gives the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq variable part
|
1995-03-10 10:08:14 +03:00
|
|
|
(for example, the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq S
|
1995-03-10 10:08:14 +03:00
|
|
|
or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq D
|
1995-03-10 10:08:14 +03:00
|
|
|
in
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq EST
|
1995-03-10 10:08:14 +03:00
|
|
|
or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq EDT )
|
1995-03-10 10:08:14 +03:00
|
|
|
of time zone abbreviations to be used when this rule is in effect.
|
|
|
|
If this field is
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em \&- ,
|
1995-03-10 10:08:14 +03:00
|
|
|
the variable part is null.
|
2001-09-16 22:02:44 +04:00
|
|
|
.El
|
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
A zone line has the form
|
2010-01-01 01:49:15 +03:00
|
|
|
.sp
|
2010-01-08 22:20:21 +03:00
|
|
|
.Dl Zone NAME GMTOFF RULES/SAVE FORMAT [UNTILYEAR [MONTH [DAY [TIME]]]]
|
1995-03-10 10:08:14 +03:00
|
|
|
For example:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
|
1995-03-10 10:08:14 +03:00
|
|
|
The fields that make up a zone line are:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Bl -tag -width "RULES/SAVE" -compact
|
|
|
|
.It NAME
|
1995-03-10 10:08:14 +03:00
|
|
|
The name of the time zone.
|
|
|
|
This is the name used in creating the time conversion information file for the
|
|
|
|
zone.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It GMTOFF
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
The amount of time to add to UT to get standard time in this zone.
|
1995-03-10 10:08:14 +03:00
|
|
|
This field has the same format as the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em AT
|
1995-03-10 10:08:14 +03:00
|
|
|
and
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em SAVE
|
1995-03-10 10:08:14 +03:00
|
|
|
fields of rule lines;
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
begin the field with a minus sign if time must be subtracted from UT.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It RULES/SAVE
|
1995-03-10 10:08:14 +03:00
|
|
|
The name of the rule(s) that apply in the time zone or,
|
1997-03-08 16:47:08 +03:00
|
|
|
alternatively, an amount of time to add to local standard time.
|
1995-03-10 10:08:14 +03:00
|
|
|
If this field is
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em \&-
|
1995-03-10 10:08:14 +03:00
|
|
|
then standard time always applies in the time zone.
|
2001-09-16 22:02:44 +04:00
|
|
|
.It FORMAT
|
1995-03-10 10:08:14 +03:00
|
|
|
The format for time zone abbreviations in this time zone.
|
|
|
|
The pair of characters
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em %s
|
1995-03-10 10:08:14 +03:00
|
|
|
is used to show where the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq variable part
|
1995-03-10 10:08:14 +03:00
|
|
|
of the time zone abbreviation goes.
|
1997-03-08 16:47:08 +03:00
|
|
|
Alternatively,
|
2001-09-16 22:02:44 +04:00
|
|
|
a slash
|
|
|
|
.Pq \&/
|
1995-03-10 10:08:14 +03:00
|
|
|
separates standard and daylight abbreviations.
|
2010-01-08 22:20:21 +03:00
|
|
|
.It UNTILYEAR [MONTH [DAY [TIME]]]
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
The time at which the UT offset or the rule(s) change for a location.
|
1995-03-10 10:08:14 +03:00
|
|
|
It is specified as a year, a month, a day, and a time of day.
|
|
|
|
If this is specified,
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
the time zone information is generated from the given UT offset
|
1995-03-10 10:08:14 +03:00
|
|
|
and rule change until the time specified.
|
1997-06-18 05:12:39 +04:00
|
|
|
The month, day, and time of day have the same format as the IN, ON, and AT
|
2010-01-01 01:49:15 +03:00
|
|
|
fields of a rule; trailing fields can be omitted, and default to the
|
|
|
|
earliest possible value for the missing fields.
|
2010-01-08 22:20:21 +03:00
|
|
|
.El
|
1995-03-10 10:08:14 +03:00
|
|
|
The next line must be a
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq continuation
|
1995-03-10 10:08:14 +03:00
|
|
|
line; this has the same form as a zone line except that the
|
|
|
|
string
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq Zone
|
1995-03-10 10:08:14 +03:00
|
|
|
and the name are omitted, as the continuation line will
|
|
|
|
place information starting at the time specified as the
|
2010-01-08 22:20:21 +03:00
|
|
|
.Em until
|
2010-01-01 01:49:15 +03:00
|
|
|
information in the previous line in the file used by the previous line.
|
|
|
|
Continuation lines may contain
|
2010-01-08 22:20:21 +03:00
|
|
|
.Em until
|
2010-01-01 01:49:15 +03:00
|
|
|
information, just as zone lines do, indicating that the next line is a further
|
1995-03-10 10:08:14 +03:00
|
|
|
continuation.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
A link line has the form
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Link LINK-FROM LINK-TO
|
1995-03-10 10:08:14 +03:00
|
|
|
For example:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Link Europe/Istanbul Asia/Istanbul
|
1995-03-10 10:08:14 +03:00
|
|
|
The
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em LINK-FROM
|
1995-03-10 10:08:14 +03:00
|
|
|
field should appear as the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em NAME
|
1995-03-10 10:08:14 +03:00
|
|
|
field in some zone line;
|
|
|
|
the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em LINK-TO
|
1997-03-08 16:47:08 +03:00
|
|
|
field is used as an alternative name for that zone.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
Except for continuation lines,
|
|
|
|
lines may appear in any order in the input.
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
However, the behavior is unspecified if multiple zone or link lines
|
|
|
|
define the same name, or if the source of one link line is the target
|
|
|
|
of another.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Pp
|
1995-03-10 10:08:14 +03:00
|
|
|
Lines in the file that describes leap seconds have the following form:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Leap YEAR MONTH DAY HH:MM:SS CORR R/S
|
1995-03-10 10:08:14 +03:00
|
|
|
For example:
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dl Leap 1974 Dec 31 23:59:60 + S
|
1995-03-10 10:08:14 +03:00
|
|
|
The
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em YEAR ,
|
|
|
|
.Em MONTH ,
|
|
|
|
.Em DAY ,
|
1995-03-10 10:08:14 +03:00
|
|
|
and
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em HH:MM:SS
|
1995-03-10 10:08:14 +03:00
|
|
|
fields tell when the leap second happened.
|
|
|
|
The
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em CORR
|
1995-03-10 10:08:14 +03:00
|
|
|
field
|
|
|
|
should be
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq \&+
|
1995-03-10 10:08:14 +03:00
|
|
|
if a second was added
|
|
|
|
or
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq \&-
|
1995-03-10 10:08:14 +03:00
|
|
|
if a second was skipped.
|
|
|
|
.\" There's no need to document the following, since it's impossible for more
|
|
|
|
.\" than one leap second to be inserted or deleted at a time.
|
|
|
|
.\" The C Standard is in error in suggesting the possibility.
|
|
|
|
.\" See Terry J Quinn, The BIPM and the accurate measure of time,
|
|
|
|
.\" Proc IEEE 79, 7 (July 1991), 894-905.
|
|
|
|
.\" or
|
2001-09-16 22:02:44 +04:00
|
|
|
.\" .Dq ++
|
1995-03-10 10:08:14 +03:00
|
|
|
.\" if two seconds were added
|
|
|
|
.\" or
|
2001-09-16 22:02:44 +04:00
|
|
|
.\" .Dq --
|
1995-03-10 10:08:14 +03:00
|
|
|
.\" if two seconds were skipped.
|
|
|
|
The
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em R/S
|
1995-03-10 10:08:14 +03:00
|
|
|
field
|
|
|
|
should be (an abbreviation of)
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq Stationary
|
1998-01-22 10:06:56 +03:00
|
|
|
if the leap second time given by the other fields should be interpreted as UTC
|
1995-03-10 10:08:14 +03:00
|
|
|
or
|
|
|
|
(an abbreviation of)
|
2001-09-16 22:02:44 +04:00
|
|
|
.Dq Rolling
|
1995-03-10 10:08:14 +03:00
|
|
|
if the leap second time given by the other fields should be interpreted as
|
|
|
|
local wall clock time.
|
2010-01-08 22:20:21 +03:00
|
|
|
.El
|
|
|
|
.Sh EXTENDED EXAMPLE
|
2010-01-01 01:49:15 +03:00
|
|
|
Here is an extended example of
|
2010-01-08 22:20:21 +03:00
|
|
|
.Ic zic
|
2010-01-01 01:49:15 +03:00
|
|
|
input, intended to illustrate many of its features.
|
2010-01-08 22:20:21 +03:00
|
|
|
.Bl -column -compact "# Rule" "Swiss" "FROM" "1995" "TYPE" "Oct" "lastSun" "1:00u" "SAVE" "LETTER/S"
|
|
|
|
.It # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
.It Rule Swiss 1941 1942 - May Mon>=1 1:00 1:00 S
|
|
|
|
.It Rule Swiss 1941 1942 - Oct Mon>=1 2:00 0 -
|
2010-01-08 22:20:21 +03:00
|
|
|
.Pp
|
|
|
|
.It Rule EU 1977 1980 - Apr Sun>=1 1:00u 1:00 S
|
|
|
|
.It Rule EU 1977 only - Sep lastSun 1:00u 0 -
|
|
|
|
.It Rule EU 1978 only - Oct 1 1:00u 0 -
|
|
|
|
.It Rule EU 1979 1995 - Sep lastSun 1:00u 0 -
|
|
|
|
.It Rule EU 1981 max - Mar lastSun 1:00u 1:00 S
|
|
|
|
.It Rule EU 1996 max - Oct lastSun 1:00u 0 -
|
|
|
|
.El
|
|
|
|
.Pp
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
.Bl -column -compact "# Zone" "Europe/Zurich" "0:34:08" "RULES/SAVE" "FORMAT" "UNTIL"
|
|
|
|
.It # Zone NAME GMTOFF RULES/SAVE FORMAT UNTIL
|
|
|
|
.It Zone Europe/Zurich 0:34:08 - LMT 1853 Jul 16
|
2010-01-08 22:20:21 +03:00
|
|
|
.It 0:29:44 - BMT 1894 Jun
|
|
|
|
.It 1:00 Swiss CE%sT 1981
|
|
|
|
.It 1:00 EU CE%sT
|
|
|
|
.It Link Europe/Zurich Switzerland
|
|
|
|
.El
|
|
|
|
.Pp
|
2010-01-01 01:49:15 +03:00
|
|
|
In this example, the zone is named Europe/Zurich but it has an alias
|
2010-05-30 11:57:08 +04:00
|
|
|
as Switzerland.
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
This example says that Zurich was 34 minutes and 8
|
|
|
|
seconds west of UT until 1853-07-16 at 00:00, when the legal offset
|
|
|
|
was changed to 7\(de\|26\(fm\|22.50\(sd; although this works out to
|
|
|
|
0:29:45.50, the input format cannot represent fractional seconds so it
|
|
|
|
is rounded here.
|
|
|
|
After 1894-06-01 at 00:00 Swiss daylight saving rules
|
|
|
|
(defined with lines beginning with "Rule Swiss") apply, and the UT offset
|
2010-05-30 11:57:08 +04:00
|
|
|
became one hour.
|
|
|
|
From 1981 to the present, EU daylight saving rules have
|
2010-01-01 01:49:15 +03:00
|
|
|
applied, and the UTC offset has remained at one hour.
|
2010-01-08 22:20:21 +03:00
|
|
|
.Pp
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
In 1941 and 1942, daylight saving time applied from the first Monday
|
|
|
|
in May at 01:00 to the first Monday in October at 02:00.
|
2010-01-01 01:49:15 +03:00
|
|
|
The pre-1981 EU daylight-saving rules have no effect
|
2010-05-30 11:57:08 +04:00
|
|
|
here, but are included for completeness.
|
|
|
|
Since 1981, daylight
|
2010-01-01 01:49:15 +03:00
|
|
|
saving has begun on the last Sunday in March at 01:00 UTC.
|
|
|
|
Until 1995 it ended the last Sunday in September at 01:00 UTC,
|
|
|
|
but this changed to the last Sunday in October starting in 1996.
|
2010-01-08 22:20:21 +03:00
|
|
|
.Pp
|
2010-01-01 01:49:15 +03:00
|
|
|
For purposes of
|
2010-05-30 11:57:08 +04:00
|
|
|
display, "LMT" and "BMT" were initially used, respectively.
|
|
|
|
Since
|
2010-01-01 01:49:15 +03:00
|
|
|
Swiss rules and later EU rules were applied, the display name for the
|
|
|
|
timezone has been CET for standard time and CEST for daylight saving
|
|
|
|
time.
|
2010-01-08 22:20:21 +03:00
|
|
|
.Sh NOTES
|
1995-03-10 10:08:14 +03:00
|
|
|
For areas with more than two types of local time,
|
|
|
|
you may need to use local standard time in the
|
2001-09-16 22:02:44 +04:00
|
|
|
.Em AT
|
1995-03-10 10:08:14 +03:00
|
|
|
field of the earliest transition time's rule to ensure that
|
|
|
|
the earliest transition time recorded in the compiled file is correct.
|
2010-01-08 22:20:21 +03:00
|
|
|
.Pp
|
2010-01-01 01:49:15 +03:00
|
|
|
If,
|
|
|
|
for a particular zone,
|
|
|
|
a clock advance caused by the start of daylight saving
|
|
|
|
coincides with and is equal to
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
a clock retreat caused by a change in UT offset,
|
2010-01-08 22:20:21 +03:00
|
|
|
.Ic zic
|
Welcome to tzcode 2013e:
Changes affecting API
The 'zic' command now outputs a dummy transition when far-future
data can't be summarized using a TZ string, and uses a 402-year
window rather than a 400-year window. For the current data, this
affects only the Asia/Tehran file. It does not affect any of the
time stamps that this file represents, so zdump outputs the same
information as before. (Thanks to Andrew Main (Zefram).)
The 'date' command has a new '-r' option, which lets you specify
the integer time to display, a la FreeBSD.
The 'tzselect' command has two new options '-c' and '-n', which lets you
select a zone based on latitude and longitude.
The 'zic' command's '-v' option now warns about constructs that
require the new version-3 binary file format. (Thanks to Arthur
David Olson for the suggestion.)
Support for floating-point time_t has been removed.
It was always dicey, and POSIX no longer requires it.
(Thanks to Eric Blake for suggesting to the POSIX committee to
remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy
Heninger, Arthur David Olson, and Alois Treindl, for reporting
bugs and elucidating some of the corners of the old floating-point
implementation.)
The signatures of 'offtime', 'timeoff', and 'gtime' have been
changed back to the old practice of using 'long' to represent UT
offsets. This had been inadvertently and mistakenly changed to
'int_fast32_t'. (Thanks to Christos Zoulos.)
The code avoids undefined behavior on integer overflow in some
more places, including gmtime, localtime, mktime and zdump.
Changes affecting the zdump utility
zdump now outputs "UT" when referring to Universal Time, not "UTC".
"UTC" does not make sense for time stamps that predate the introduction
of UTC, whereas "UT", a more-generic term, does. (Thanks to Steve Allen
for clarifying UT vs UTC.)
Data changes affecting behavior of tzselect and similar programs
Country code BQ is now called the more-common name "Caribbean Netherlands"
rather than the more-official "Bonaire, St Eustatius & Saba".
Remove from zone.tab the names America/Montreal, America/Shiprock,
and Antarctica/South_Pole, as they are equivalent to existing
same-country-code zones for post-1970 time stamps. The data for
these names are unchanged, so the names continue to work as before.
Changes affecting code internals
zic -c now runs way faster on 64-bit hosts when given large numbers.
zic now uses vfprintf to avoid allocating and freeing some memory.
tzselect now computes the list of continents from the data,
rather than have it hard-coded.
Minor changes pacify GCC 4.7.3 and GCC 4.8.1.
Changes affecting the build procedure
The 'leapseconds' file is now generated automatically from a
new file 'leap-seconds.list', which is a copy of
<ftp://time.nist.gov/pub/leap-seconds.list>.
A new source file 'leapseconds.awk' implements this.
The goal is simplification of the future maintenance of 'leapseconds'.
When building the 'posix' or 'right' subdirectories, if the
subdirectory would be a copy of the default subdirectory, it is
now made a symbolic link if that is supported. This saves about
2 MB of file system space.
The links America/Shiprock and Antarctica/South_Pole have been
moved to the 'backward' file. This affects only nondefault builds
that omit 'backward'.
Changes affecting documentation and commentary
Changes to the 'tzfile' man page
It now mentions that the binary file format may be extended in
future versions by appending data.
It now refers to the 'zdump' and 'zic' man pages.
Changes to the 'zic' man page
It lists conditions that elicit a warning with '-v'.
It says that the behavior is unspecified when duplicate names
are given, or if the source of one link is the target of another.
Its examples are updated to match the latest data.
The definition of white space has been clarified slightly.
(Thanks to Michael Deckers.)
Changes to the 'Theory' file
There is a new section about the accuracy of the tz database,
describing the many ways that errors can creep in, and
explaining why so many of the pre-1970 time stamps are wrong or
misleading (thanks to Steve Allen, Lester Caine, and Garrett
Wollman for discussions that contributed to this).
The 'Theory' file describes LMT better (this follows a
suggestion by Guy Harris).
It refers to the 2013 edition of POSIX rather than the 2004 edition.
It's mentioned that excluding 'backward' should not affect the
other data, and it suggests at least one zone.tab name per
inhabited country (thanks to Stephen Colebourne).
Some longstanding restrictions on names are documented, e.g.,
'America/New_York' precludes 'America/New_York/Bronx'.
It gives more reasons for the 1970 cutoff.
It now mentions which time_t variants are supported, such as
signed integer time_t. (Thanks to Paul Goyette for reporting
typos in an experimental version of this change.)
(Thanks to Philip Newton for correcting typos in these changes.)
Documentation and commentary is more careful to distinguish UT in
general from UTC in particular. (Thanks to Steve Allen.)
Add a better source for the Zurich 1894 transition.
(Thanks to Pierre-Yves Berger.)
Update shapefile citations in tz-link.htm. (Thanks to Guy Harris.)
2013-09-20 23:06:54 +04:00
|
|
|
produces a single transition to daylight saving at the new UT offset
|
2010-01-01 01:49:15 +03:00
|
|
|
(without any change in wall clock time).
|
|
|
|
To get separate transitions
|
|
|
|
use multiple zone continuation lines
|
|
|
|
specifying transition instants using universal time.
|
2014-05-28 23:13:27 +04:00
|
|
|
.Pp
|
|
|
|
Time stamps well before the Big Bang are silently omitted from the output.
|
|
|
|
This works around bugs in software that mishandles large negative time stamps.
|
|
|
|
Call it sour grapes, but pre-Big-Bang time stamps are physically suspect anyway.
|
|
|
|
The pre-Big-Bang cutoff time is approximate and may change in future versions.
|
2001-09-16 22:02:44 +04:00
|
|
|
.Sh FILES
|
|
|
|
.Pa /usr/share/zoneinfo
|
|
|
|
- standard directory used for created files
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr ctime 3 ,
|
|
|
|
.Xr tzfile 5 ,
|
|
|
|
.Xr zdump 8
|
2011-09-04 14:10:26 +04:00
|
|
|
.\" @(#)zic.8 8.6
|
2010-01-01 01:49:15 +03:00
|
|
|
.\" This file is in the public domain, so clarified as of
|
|
|
|
.\" 2009-05-17 by Arthur David Olson.
|