1 .\" $NetBSD: zic.8,v 1.20 2012/08/09 12:38:26 christos Exp $
12 .Op Fl L Ar leapsecondfilename
14 .Op Fl p Ar posixrules
21 reads text from the file(s) named on the command line
22 and creates the time conversion information files specified in this input.
27 the standard input is read.
29 These options are available:
30 .Bl -tag -width XXXXXXXXXX -compact
32 Output version information and exit.
34 Create time conversion information files in the named directory rather than
35 in the standard directory named below.
36 .It Fl L Ar leapsecondfilename
37 Read leap second information from the file with the given name.
38 If this option is not used,
39 no leap second information appears in output files.
41 Use the given time zone as local time.
43 will act as if the input contained a link line of the form
44 .Dl Link timezone localtime
46 Use the given time zone's rules when handling POSIX-format
47 time zone environment variables.
49 will act as if the input contained a link line of the form
50 .Dl Link timezone posixrules
52 Limit time values stored in output files to values that are the same
53 whether they're taken to be signed or unsigned.
54 You can use this option to generate SVVS-compatible files.
56 Complain if a year that appears in a data file is outside the range
57 of years representable by
60 Also complain if a time of 24:00
61 .Pq which cannot be handled by pre-1998 versions of Nm
68 when checking year types (see below).
70 Input lines are made up of fields.
71 Fields are separated from one another by any number of white space characters.
72 Leading and trailing white space on input lines is ignored.
73 An unquoted sharp character (#) in the input introduces a comment which extends
74 to the end of the line the sharp character appears on.
75 White space characters and sharp characters may be enclosed in double
79 if they're to be used as part of a field.
80 Any line that is blank (after comment stripping) is ignored.
81 Non-blank lines are expected to be of one of three types:
82 rule lines, zone lines, and link lines.
84 Names (such as month names) must be in English and are case insensitive.
85 Abbreviations, if used, must be unambiguous in context.
87 A rule line has the form
88 .Dl Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
90 .Dl Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D
91 The fields that make up a rule line are:
92 .Bl -tag -width "LETTER/S" -compact
94 Gives the (arbitrary) name of the set of rules this rule is part of.
96 Gives the first year in which the rule applies.
97 Any integer year can be supplied; the Gregorian calendar is assumed.
100 (or an abbreviation) means the minimum year representable as an integer.
103 (or an abbreviation) means the maximum year representable as an integer.
104 Rules can describe times that are not representable as time values,
105 with the unrepresentable times ignored; this allows rules to be portable
106 among hosts with differing time value types.
108 Gives the final year in which the rule applies.
117 may be used to repeat the value of the
121 Gives the type of year in which the rule applies.
126 then the rule applies in all years between
133 is something else, then
137 .Ic yearistype Ar year type
139 to check the type of a year:
140 an exit status of zero is taken to mean that the year is of the given type;
141 an exit status of one is taken to mean that the year is not of the given type.
143 Names the month in which the rule takes effect.
144 Month names may be abbreviated.
146 Gives the day on which the rule takes effect.
147 Recognized forms include:
148 .Bl -tag -width lastSun -compact -offset indent
150 the fifth of the month
152 the last Sunday in the month
154 the last Monday in the month
156 first Sunday on or after the eighth
158 last Sunday on or before the 25th
160 Names of days of the week may be abbreviated or spelled out in full.
161 Note that there must be no spaces within the
165 Gives the time of day at which the rule takes effect.
166 Recognized forms include:
167 .Bl -tag -width "1X28X14" -compact -offset indent
171 time in hours and minutes
173 24-hour format time (for times after noon)
175 time in hours, minutes, and seconds
179 where hour 0 is midnight at the start of the day,
180 and hour 24 is midnight at the end of the day.
181 Any of these forms may be followed by the letter
183 if the given time is local
187 if the given time is local
195 if the given time is universal time;
196 in the absence of an indicator,
197 wall clock time is assumed.
199 Gives the amount of time to be added to local standard time when the rule is in
201 This field has the same format as the
204 (although, of course, the
208 suffixes are not used).
220 of time zone abbreviations to be used when this rule is in effect.
223 the variable part is null.
226 A zone line has the form
228 .Dl Zone NAME GMTOFF RULES/SAVE FORMAT [UNTILYEAR [MONTH [DAY [TIME]]]]
230 .Dl Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00
231 The fields that make up a zone line are:
232 .Bl -tag -width "RULES/SAVE" -compact
234 The name of the time zone.
235 This is the name used in creating the time conversion information file for the
238 The amount of time to add to UTC to get standard time in this zone.
239 This field has the same format as the
243 fields of rule lines;
244 begin the field with a minus sign if time must be subtracted from UTC.
246 The name of the rule(s) that apply in the time zone or,
247 alternatively, an amount of time to add to local standard time.
250 then standard time always applies in the time zone.
252 The format for time zone abbreviations in this time zone.
253 The pair of characters
255 is used to show where the
257 of the time zone abbreviation goes.
261 separates standard and daylight abbreviations.
262 .It UNTILYEAR [MONTH [DAY [TIME]]]
263 The time at which the UTC offset or the rule(s) change for a location.
264 It is specified as a year, a month, a day, and a time of day.
265 If this is specified,
266 the time zone information is generated from the given UTC offset
267 and rule change until the time specified.
268 The month, day, and time of day have the same format as the IN, ON, and AT
269 fields of a rule; trailing fields can be omitted, and default to the
270 earliest possible value for the missing fields.
272 The next line must be a
274 line; this has the same form as a zone line except that the
277 and the name are omitted, as the continuation line will
278 place information starting at the time specified as the
280 information in the previous line in the file used by the previous line.
281 Continuation lines may contain
283 information, just as zone lines do, indicating that the next line is a further
286 A link line has the form
287 .Dl Link LINK-FROM LINK-TO
289 .Dl Link Europe/Istanbul Asia/Istanbul
292 field should appear as the
294 field in some zone line;
297 field is used as an alternative name for that zone.
299 Except for continuation lines,
300 lines may appear in any order in the input.
302 Lines in the file that describes leap seconds have the following form:
303 .Dl Leap YEAR MONTH DAY HH:MM:SS CORR R/S
305 .Dl Leap 1974 Dec 31 23:59:60 + S
312 fields tell when the leap second happened.
318 if a second was added
321 if a second was skipped.
322 .\" There's no need to document the following, since it's impossible for more
323 .\" than one leap second to be inserted or deleted at a time.
324 .\" The C Standard is in error in suggesting the possibility.
325 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
326 .\" Proc IEEE 79, 7 (July 1991), 894-905.
329 .\" if two seconds were added
332 .\" if two seconds were skipped.
336 should be (an abbreviation of)
338 if the leap second time given by the other fields should be interpreted as UTC
342 if the leap second time given by the other fields should be interpreted as
343 local wall clock time.
346 Here is an extended example of
348 input, intended to illustrate many of its features.
349 .Bl -column -compact "# Rule" "Swiss" "FROM" "1995" "TYPE" "Oct" "lastSun" "1:00u" "SAVE" "LETTER/S"
350 .It # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
351 .It Rule Swiss 1940 only - Nov 2 0:00 1:00 S
352 .It Rule Swiss 1940 only - Dec 31 0:00 0 -
353 .It Rule Swiss 1941 1942 - May Sun>=1 2:00 1:00 S
354 .It Rule Swiss 1941 1942 - Oct Sun>=1 0:00 0
356 .It Rule EU 1977 1980 - Apr Sun>=1 1:00u 1:00 S
357 .It Rule EU 1977 only - Sep lastSun 1:00u 0 -
358 .It Rule EU 1978 only - Oct 1 1:00u 0 -
359 .It Rule EU 1979 1995 - Sep lastSun 1:00u 0 -
360 .It Rule EU 1981 max - Mar lastSun 1:00u 1:00 S
361 .It Rule EU 1996 max - Oct lastSun 1:00u 0 -
364 .Bl -column -compact "# Zone" "Europe/Zurich" "0:29:44" "RULES" "FORMAT" "UNTIL"
365 .It # Zone NAME GMTOFF RULES FORMAT UNTIL
366 .It Zone Europe/Zurich 0:34:08 - LMT 1848 Sep 12
367 .It 0:29:44 - BMT 1894 Jun
368 .It 1:00 Swiss CE%sT 1981
370 .It Link Europe/Zurich Switzerland
373 In this example, the zone is named Europe/Zurich but it has an alias
375 Zurich was 34 minutes and 8 seconds west of GMT until
376 1848-09-12 at 00:00, when the offset changed to 29 minutes and 44
378 After 1894-06-01 at 00:00 Swiss daylight saving rules (defined
379 with lines beginning with "Rule Swiss") apply, and the GMT offset
381 From 1981 to the present, EU daylight saving rules have
382 applied, and the UTC offset has remained at one hour.
384 In 1940, daylight saving time applied from November 2 at 00:00 to
385 December 31 at 00:00.
386 In 1941 and 1942, daylight saving time applied
387 from the first Sunday in May at 02:00 to the first Sunday in October
389 The pre-1981 EU daylight-saving rules have no effect
390 here, but are included for completeness.
392 saving has begun on the last Sunday in March at 01:00 UTC.
393 Until 1995 it ended the last Sunday in September at 01:00 UTC,
394 but this changed to the last Sunday in October starting in 1996.
397 display, "LMT" and "BMT" were initially used, respectively.
399 Swiss rules and later EU rules were applied, the display name for the
400 timezone has been CET for standard time and CEST for daylight saving
403 For areas with more than two types of local time,
404 you may need to use local standard time in the
406 field of the earliest transition time's rule to ensure that
407 the earliest transition time recorded in the compiled file is correct.
410 for a particular zone,
411 a clock advance caused by the start of daylight saving
412 coincides with and is equal to
413 a clock retreat caused by a change in UTC offset,
415 produces a single transition to daylight saving at the new UTC offset
416 (without any change in wall clock time).
417 To get separate transitions
418 use multiple zone continuation lines
419 specifying transition instants using universal time.
421 .Pa /usr/share/zoneinfo
422 - standard directory used for created files
428 .\" This file is in the public domain, so clarified as of
429 .\" 2009-05-17 by Arthur David Olson.