3 zic \- time zone compiler
34 \\$3\*(lq\\$1\*(rq\\$2
37 reads text from the file(s) named on the command line
38 and creates the time conversion information files specified in this input.
43 the standard input is read.
45 These options are available:
48 Create time conversion information files in the named directory rather than
49 in the standard directory named below.
52 Use the given time zone as local time.
54 will act as if the input contained a link line of the form
57 Link \fItimezone\fP localtime
60 Use the given time zone's rules when handling POSIX-format
61 time zone environment variables.
63 will act as if the input contained a link line of the form
66 Link \fItimezone\fP posixrules
68 .BI "\-L " leapsecondfilename
69 Read leap second information from the file with the given name.
70 If this option is not used,
71 no leap second information appears in output files.
74 Complain if a year that appears in a data file is outside the range
75 of years representable by
80 Limit time values stored in output files to values that are the same
81 whether they're taken to be signed or unsigned.
82 You can use this option to generate SVVS-compatible files.
89 when checking year types (see below).
91 Input lines are made up of fields.
92 Fields are separated from one another by any number of white space characters.
93 Leading and trailing white space on input lines is ignored.
94 An unquoted sharp character (#) in the input introduces a comment which extends
95 to the end of the line the sharp character appears on.
96 White space characters and sharp characters may be enclosed in double quotes
97 (") if they're to be used as part of a field.
98 Any line that is blank (after comment stripping) is ignored.
99 Non-blank lines are expected to be of one of three types:
100 rule lines, zone lines, and link lines.
102 A rule line has the form
105 .ta \w'Rule\0\0'u +\w'NAME\0\0'u +\w'FROM\0\0'u +\w'1973\0\0'u +\w'TYPE\0\0'u +\w'Apr\0\0'u +\w'lastSun\0\0'u +\w'2:00\0\0'u +\w'SAVE\0\0'u
107 Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
112 Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
115 The fields that make up a rule line are:
118 Gives the (arbitrary) name of the set of rules this rule is part of.
121 Gives the first year in which the rule applies.
122 Any integer year can be supplied; the Gregorian calendar is assumed.
125 (or an abbreviation) means the minimum year representable as an integer.
128 (or an abbreviation) means the maximum year representable as an integer.
129 Rules can describe times that are not representable as time values,
130 with the unrepresentable times ignored; this allows rules to be portable
131 among hosts with differing time value types.
134 Gives the final year in which the rule applies.
143 may be used to repeat the value of the
148 Gives the type of year in which the rule applies.
153 then the rule applies in all years between
160 is something else, then
164 \fByearistype\fP \fIyear\fP \fItype\fP
166 to check the type of a year:
167 an exit status of zero is taken to mean that the year is of the given type;
168 an exit status of one is taken to mean that the year is not of the given type.
171 Names the month in which the rule takes effect.
172 Month names may be abbreviated.
175 Gives the day on which the rule takes effect.
176 Recognized forms include:
181 5 the fifth of the month
182 lastSun the last Sunday in the month
183 lastMon the last Monday in the month
184 Sun>=8 first Sunday on or after the eighth
185 Sun<=25 last Sunday on or before the 25th
189 Names of days of the week may be abbreviated or spelled out in full.
190 Note that there must be no spaces within the
195 Gives the time of day at which the rule takes effect.
196 Recognized forms include:
202 2:00 time in hours and minutes
203 15:00 24-hour format time (for times after noon)
204 1:28:14 time in hours, minutes, and seconds
209 where hour 0 is midnight at the start of the day,
210 and hour 24 is midnight at the end of the day.
211 Any of these forms may be followed by the letter
213 if the given time is local
217 if the given time is local
225 if the given time is universal time;
226 in the absence of an indicator,
227 wall clock time is assumed.
230 Gives the amount of time to be added to local standard time when the rule is in
232 This field has the same format as the
235 (although, of course, the
239 suffixes are not used).
252 of time zone abbreviations to be used when this rule is in effect.
255 the variable part is null.
257 A zone line has the form
261 .ta \w'Zone\0\0'u +\w'Australia/Adelaide\0\0'u +\w'GMTOFF\0\0'u +\w'RULES/SAVE\0\0'u +\w'FORMAT\0\0'u
262 Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL]
267 Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
270 The fields that make up a zone line are:
273 The name of the time zone.
274 This is the name used in creating the time conversion information file for the
278 The amount of time to add to UTC to get standard time in this zone.
279 This field has the same format as the
283 fields of rule lines;
284 begin the field with a minus sign if time must be subtracted from UTC.
287 The name of the rule(s) that apply in the time zone or,
288 alternately, an amount of time to add to local standard time.
291 then standard time always applies in the time zone.
294 The format for time zone abbreviations in this time zone.
295 The pair of characters
297 is used to show where the
299 of the time zone abbreviation goes.
302 separates standard and daylight abbreviations.
305 The time at which the UTC offset or the rule(s) change for a location.
306 It is specified as a year, a month, a day, and a time of day.
307 If this is specified,
308 the time zone information is generated from the given UTC offset
309 and rule change until the time specified.
310 The month, day, and time of day have the same format as the IN, ON, and AT
311 columns of a rule; trailing columns can be omitted, and default to the
312 earliest possible value for the missing columns.
314 The next line must be a
316 line; this has the same form as a zone line except that the
319 and the name are omitted, as the continuation line will
320 place information starting at the time specified as the
322 field in the previous line in the file used by the previous line.
323 Continuation lines may contain an
325 field, just as zone lines do, indicating that the next line is a further
328 A link line has the form
332 .ta \w'Link\0\0'u +\w'Europe/Istanbul\0\0'u
333 Link LINK-FROM LINK-TO
338 Link Europe/Istanbul Asia/Istanbul
343 field should appear as the
345 field in some zone line;
348 field is used as an alternate name for that zone.
350 Except for continuation lines,
351 lines may appear in any order in the input.
353 Lines in the file that describes leap seconds have the following form:
356 .ta \w'Leap\0\0'u +\w'YEAR\0\0'u +\w'MONTH\0\0'u +\w'DAY\0\0'u +\w'HH:MM:SS\0\0'u +\w'CORR\0\0'u
358 Leap YEAR MONTH DAY HH:MM:SS CORR R/S
363 Leap 1974 Dec 31 23:59:60 + S
372 fields tell when the leap second happened.
378 if a second was added
381 if a second was skipped.
382 .\" There's no need to document the following, since it's impossible for more
383 .\" than one leap second to be inserted or deleted at a time.
384 .\" The C Standard is in error in suggesting the possibility.
385 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
386 .\" Proc IEEE 79, 7 (July 1991), 894-905.
389 .\" if two seconds were added
392 .\" if two seconds were skipped.
396 should be (an abbreviation of)
398 if the leap second time given by the other fields should be interpreted as UTC
402 if the leap second time given by the other fields should be interpreted as
403 local wall clock time.
405 For areas with more than two types of local time,
406 you may need to use local standard time in the
408 field of the earliest transition time's rule to ensure that
409 the earliest transition time recorded in the compiled file is correct.
411 /usr/local/etc/zoneinfo standard directory used for created files
413 newctime(3), tzfile(5), zdump(8)