Indeed, irritating if you don't have a nroff/troff reader and you would like
to read the ".8" manual pages of the tz-code.
I converted the zic.8 page from tzcode2000c to HTML format, completely by
hand. I have no Unix/Linux OS, but I do have IBM's troff command manual page
(308 KB).
Everything after the separation line can be regarded as the HTML file in
question.
So copy those lines to a new text only file and name it "zic8.html" or
something like that.
If this doesn't work for you, I could send the HTML file as MIME-encoded
mail-attachment. Anyhow, the HTML file looked fine in the browsers Netscape
Navigator 4.7.2 and Microsoft Internet Explorer 4.5 in the Macintosh
versions.
I used no CSS (cascading style sheets) nor any fancy markup code, since
there are still no browsers in existence that support all "standards".
Please understand that my HTML conversion has NO OFFICIAL status.
It should be regarded as an experiment; still useful though.
Regards,
Oscar van Vlijmen
2000-04-19
--------------------------------------------------------------------------
<html>
<head>
<title>ZIC 8 - time zone compiler</title>
</head>
<body>
<h3>SYNOPSIS</h3>
<b>zic</b>
[
<b>-v</b>
] [
<b>-d</b>
<i> directory </i>
] [
<b>-l</b>
<i> localtime </i>
] [
<b>-p</b>
<i> posixrules </i>
] [
<b>-L</b>
<i> leapsecondfilename </i>
] [
<b>-s</b>
] [
<b>-y</b>
<i> command </i>
] [
<i> filename </i>
... ]<p>
<h3>DESCRIPTION</h3>
<i>Zic </i>reads text from the file(s) named on the command line
and creates the time conversion information files specified in this input.
If a <i>filename </i>is <b>-</b>, the standard input is read.
<br>
These options are available:<br>
<dl>
<dt><b>-d</b> <i>directory</i>
<dd>Create time conversion information files in the named directory rather
than
in the standard directory named below.
<dt><b>-l</b> <i>timezone</i>
<dd>Use the given time zone as local time.<br>
<i>Zic </i>will act as if the input contained a link line of the form:<br>
<table><tr><td>Link<td><i>timezone</i><td>localtime</table>
<dt><b>-p</b> <i>timezone</i>
<dd>Use the given time zone's rules when handling POSIX-format
time zone environment variables.<br>
<i>Zic </i>will act as if the input contained a link line of the form:<br>
<table><tr><td>Link<td><i>timezone</i><td>posixrules</table>
<dt><b>-L</b> <i>leapsecondfilename</i>
<dd>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.
<dt><b>-v</b>
<dd>Complain if a year that appears in a data file is outside the range
of years representable by <i>time (2) </i> values.
<dt><b>-s</b>
<dd>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.
<dt><b>-y</b> <i>command</i>
<dd>Use the given <i>command </i>rather than <b>yearistype</b>
when checking year types (see below).
</dl>
Input lines are made up of fields.<br>
Fields are separated from one another by any number of white space
characters.<br>
Leading and trailing white space on input lines is ignored.<br>
An unquoted sharp character (#) in the input introduces a comment which
extends
to the end of the line the sharp character appears on.<br>
White space characters and sharp characters may be enclosed in double quotes
(") if they're to be used as part of a field.<br>
Any line that is blank (after comment stripping) is ignored.<br>
Non-blank lines are expected to be of one of three types:<br>
rule lines, zone lines, and link lines.
<p>
A rule line has the form:<br>
<table border=1>
<tr><td>Rule<td>NAME<td>FROM<td>TO<td>TYPE<td>IN<td>ON<td>AT<td>SAVE<td>LETT
ER/S
<tr><td colspan=10>For example:
<tr><td>Rule<td>US<td>1967<td>1973<td>-<td>Apr<td>lastSun<td>2:00<td>1:00<td
>D
</table><p>
The fields that make up a rule line are:<br>
<dl>
<dt><b>NAME</b>
<dd>Gives the (arbitrary) name of the set of rules this rule is part of.
<dt><b>FROM</b>
<dd>Gives the first year in which the rule applies.<br>
Any integer year can be supplied; the Gregorian calendar is assumed.
The word <b>minimum</b> (or an abbreviation) means the minimum year
representable as an integer.
The word <b>maximum</b> (or an abbreviation) means the maximum year
representable as an integer.<br>
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.
<dt><b>TO</b>
<dd>Gives the final year in which the rule applies.<br>
In addition to <b>minimum</b> and <b>maximum</b> (as above), the word
<b>only</b> (or an abbreviation)
may be used to repeat the value of the <b>FROM</b> field.
<dt><b>TYPE</b>
<dd>Gives the type of year in which the rule applies.<br>
If <b>TYPE</b> is <b>-</b> then the rule applies in all years between
<b>FROM</b> and <b>TO</b> inclusive. If <b>TYPE</b> is something else, then
<i>zic </i> executes the command:
<b>yearistype</b> <i>year type</i><br>
To check the type of a year:<br>
An exit status of zero is taken to mean that the year is of the given
type;<br>
An exit status of one is taken to mean that the year is not of the given
type.<br>
<dt><b>IN</b>
<dd>Names the month in which the rule takes effect. Month names may be
abbreviated.
<dt><b>ON</b>
<dd>Gives the day on which the rule takes effect.
Recognized forms include:<br>
<table border=1>
<tr><td>5<td>the fifth of the month
<tr><td>lastSun<td>the last Sunday in the month
<tr><td>lastMon<td>the last Monday in the month
<tr><td>Sun>=8<td>first Sunday on or after the eighth
<tr><td>Sun<=25<td>last Sunday on or before the 25th
</table>
Names of days of the week may be abbreviated or spelled out in full.<br>
Note that there must be no spaces within the <b>ON</b> field.
<dt><b>AT</b>
<dd>Gives the time of day at which the rule takes effect. Recognized forms
include:<br>
<table border=1>
<tr><td>2<td>time in hours
<tr><td>2:00<td>time in hours and minutes
<tr><td>15:00<td>24-hour format time (for times after noon)
<tr><td>1:28:14<td>time in hours, minutes, and seconds
<tr><td>-<td>equivalent to 0
</table>
Where hour 0 is midnight at the start of the day, and hour 24 is midnight at
the end of the day.
Any of these forms may be followed by the letter <b>w</b> if the given time
is local "wall clock" time, <b>s</b> if the given time is local "standard"
time, or <b>u</b> (or <b>g</b> or <b>z</b>) if the given time is universal
time; in the absence of an indicator, wall clock time is assumed.
<dt><b>SAVE</b>
<dd>Gives the amount of time to be added to local standard time when the
rule is in effect.<br>
This field has the same format as the <b>AT</b> field (although, of course,
the <b>w</b> and <b>s</b> suffixes are not used).
<dt><b>LETTER/S</b>
<dd>Gives the "variable part" (for example, the "S" or "D" in "EST" or
"EDT") of time zone abbreviations to be used when this rule is in
effect.<br>
If this field is <b>-</b>, the variable part is null.
</dl>
<p>
A zone line has the form:<br>
<table border=1>
<tr><td>Zone<td>NAME<td>GMTOFF<td>RULES/SAVE<td>FORMAT<td>[UNTIL]
<tr><td colspan=6>For example:
<tr><td>Zone<td>Australia/Adelaide<td>9:30<td>Aus<td>CST<td>1971 Oct 31 2:00
</table><br>
The fields that make up a zone line are:<br>
<dl>
<dt><b>NAME</b>
<dd>The name of the time zone.
This is the name used in creating the time conversion information file for
the zone.
<dt><b>GMTOFF</b>
<dd>The amount of time to add to UTC to get standard time in this zone.
This field has the same format as the <b>AT</b> and <b>SAVE</b> fields of
rule lines;
begin the field with a minus sign if time must be subtracted from UTC.
<dt><b>RULES/SAVE</b>
<dd>The name of the rule(s) that apply in the time zone or, alternately, an
amount of time to add to local standard time. If this field is <b>-</b> then
standard time always applies in the time zone.
<dt><b>FORMAT</b>
<dd>The format for time zone abbreviations in this time zone. The pair of
characters <b>%s</b> is used to show where the "variable part" of the time
zone abbreviation goes.
Alternately, a slash (/) separates standard and daylight abbreviations.
<dt><b>UNTIL</b>
<dd>The time at which the UTC offset or the rule(s) change for a location.
It is specified as a year, a month, a day, and a time of day. If this is
specified, the time zone information is generated from the given UTC offset
and rule change until the time specified. The month, day, and time of day
have the same format as the <b>IN</b>, <b>ON</b>, and <b>AT</b> columns of a
rule; trailing columns can be omitted, and default to the earliest possible
value for the missing columns.<br>
The next line must be a 'continuation' line; this has the same form as a
zone line except that the
string "Zone" and the name are omitted, as the continuation line will place
information starting at the time specified as the <b>UNTIL</b> field in the
previous line in the file used by the previous line. Continuation lines may
contain an <b>UNTIL</b> field, just as zone lines do, indicating that the
next line is a further continuation.
</dl>
<p>
A link line has the form:
<table border=1>
<tr><td>Link<td>LINK-FROM<td>LINK-TO
<tr><td colspan=3>For example:
<tr><td>Link<td>Europe/Istanbul<td>Asia/Istanbul
</table>
The <b>LINK-FROM</b> field should appear as the <b>NAME</b> field in some
zone line;<br>
the <b>LINK-TO</b> field is used as an alternate name for that zone.<p>
Except for continuation lines, lines may appear in any order in the
input.<p>
Lines in the file that describes leap seconds have the following form:
<table border=1>
<tr><td>Leap<td>YEAR<td>MONTH<td>DAY<td>HH:MM:SS<td>CORR<td>R/S
<tr><td colspan=7>For example:
<tr><td>Leap<td>1974<td>Dec<td>31<td>23:59:60<td>+<td>S
</table>
The <b>YEAR</b>, <b>MONTH</b>, <b>DAY</b>, and <b>HH:MM:SS</b> fields tell
when the leap second happened. The <b>CORR</b> field should be "+" if a
second was added or "-" if a second was skipped.<br>
<table>
<tr><td> <td>
<font size="-1">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.</font><br>
<dl><dt><dd><i>or "++" if two seconds were added or "--" if two seconds were
skipped.</i></dl></table>
The <b>R/S</b> field should be (an abbreviation of) "Stationary" if the leap
second time given by the other fields should be interpreted as UTC or (an
abbreviation of) "Rolling" if the leap second time given by the other fields
should be interpreted as local wall clock time.
<p>
<h3>NOTE</h3>
For areas with more than two types of local time, you may need to use local
standard time in the <b>AT</b> field of the earliest transition time's rule
to ensure that the earliest transition time recorded in the compiled file is
correct.
<p>
<h3>FILE</h3>
/usr/local/etc/zoneinfo standard directory used for created files
<p>
<h3>SEE ALSO</h3>
newctime(3), tzfile(5), zdump(8)
<p>
<pre>@(#)zic.8 7.19</pre><br>
This is the HTML version of the file "zic.8" in the tzcode folder.<br>
</body>
</html>
