1 .\" $FreeBSD: head/contrib/tzcode/zic/zic.8 214411 2010-10-27 07:14:46Z edwin $
14 .Op Fl L Ar leapsecondfilename
17 .Op Fl p Ar posixrules
24 utility reads text from the file(s) named on the command line
25 and creates the time conversion information files specified in this input.
30 the standard input is read.
32 The following options are available:
33 .Bl -tag -width indent
35 Output version information and exit.
37 Do not automatically create directories.
38 If the input file(s) specify
39 an output file in a directory which does not already exist, the
40 default behavior is to attempt to create the directory.
45 will instead error out immediately.
47 Create time conversion information files in the named directory rather than
48 in the standard directory named below.
50 After creating each output file, change its group ownership to the
53 (which can be either a name or a numeric group ID).
54 .It Fl L Ar leapsecondfilename
55 Read leap second information from the file with the given name.
56 If this option is not used,
57 no leap second information appears in output files.
64 utility will act as if the input contained a link line of the form
66 .D1 No "Link timezone localtime"
68 (Note that this action has no effect on
70 since the local time zone is specified in
73 .Pa /usr/share/zoneinfo/localtime . )
75 After creating each output file, change its access mode to
77 Both numeric and alphabetic modes are accepted
83 rules when handling POSIX-format
84 time zone environment variables.
87 utility will act as if the input contained a link line of the form
89 .D1 No "Link timezone posixrules"
91 After creating each output file, change its owner to
93 (which can be either a name or a numeric user ID).
95 Complain if a year that appears in a data file is outside the range
96 of years representable by
100 Limit time values stored in output files to values that are the same
101 whether they are taken to be signed or unsigned.
102 You can use this option to generate SVVS-compatible files.
108 when checking year types (see below).
111 Input lines are made up of fields.
112 Fields are separated from one another by any number of white space characters.
113 Leading and trailing white space on input lines is ignored.
114 An unquoted sharp character (#) in the input introduces a comment which extends
115 to the end of the line the sharp character appears on.
116 White space characters and sharp characters may be enclosed in double quotes
117 (") if they are to be used as part of a field.
118 Any line that is blank (after comment stripping) is ignored.
119 Non-blank lines are expected to be of one of three types:
120 rule lines, zone lines, and link lines.
122 Names (such as month names) must be in English and are case insensitive.
123 Abbreviations, if used, must be unambiguous in context.
125 A rule line has the form:
126 .Dl "Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S"
128 .Dl "Rule US 1967 1973 \- Apr lastSun 2:00 1:00 D"
130 The fields that make up a rule line are:
131 .Bl -tag -width "LETTER/S" -offset indent
133 Give the (arbitrary) name of the set of rules this rule is part of.
135 Give the first year in which the rule applies.
136 Any integer year can be supplied; the Gregorian calendar is assumed.
139 (or an abbreviation) means the minimum year representable as an integer.
142 (or an abbreviation) means the maximum year representable as an integer.
143 Rules can describe times that are not representable as time values,
144 with the unrepresentable times ignored; this allows rules to be portable
145 among hosts with differing time value types.
147 Give the final year in which the rule applies.
156 may be used to repeat the value of the
160 Give the type of year in which the rule applies.
165 then the rule applies in all years between
172 is something else, then
175 .Li yearistype Ar year Ar type
176 to check the type of a year:
177 an exit status of zero is taken to mean that the year is of the given type;
178 an exit status of one is taken to mean that the year is not of the given type.
180 Name the month in which the rule takes effect.
181 Month names may be abbreviated.
183 Give the day on which the rule takes effect.
184 Recognized forms include:
186 .Bl -tag -width lastSun -compact -offset indent
188 the fifth of the month
190 the last Sunday in the month
192 the last Monday in the month
194 first Sunday on or after the eighth
196 last Sunday on or before the 25th
199 Names of days of the week may be abbreviated or spelled out in full.
200 Note that there must be no spaces within the
204 Give the time of day at which the rule takes effect.
205 Recognized forms include:
207 .Bl -tag -width "\&1:28:14" -offset indent -compact
211 time in hours and minutes
213 24-hour format time (for times after noon)
215 time in hours, minutes, and seconds
218 where hour 0 is midnight at the start of the day,
219 and hour 24 is midnight at the end of the day.
220 Any of these forms may be followed by the letter
222 if the given time is local
226 if the given time is local
234 if the given time is universal time;
235 in the absence of an indicator,
236 wall clock time is assumed.
238 Give the amount of time to be added to local standard time when the rule is in
240 This field has the same format as the
243 (although, of course, the
247 suffixes are not used).
259 of time zone abbreviations to be used when this rule is in effect.
262 the variable part is null.
265 A zone line has the form:
266 .Dl "Zone NAME GMTOFF RULES/SAVE FORMAT [UNTILYEAR [MONTH [DAY [TIME]]]]"
268 .Dl "Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00"
269 The fields that make up a zone line are:
270 .Bl -tag -width indent
272 The name of the time zone.
273 This is the name used in creating the time conversion information file for the
276 The amount of time to add to UTC to get standard time in this zone.
277 This field has the same format as the
281 fields of rule lines;
282 begin the field with a minus sign if time must be subtracted from UTC.
284 The name of the rule(s) that apply in the time zone or,
285 alternately, an amount of time to add to local standard time.
288 then standard time always applies in the time zone.
290 The format for time zone abbreviations in this time zone.
291 The pair of characters
293 is used to show where the
295 of the time zone abbreviation goes.
298 separates standard and daylight abbreviations.
299 .It UNTILYEAR [MONTH [DAY [TIME]]]
300 The time at which the UTC offset or the rule(s) change for a location.
301 It is specified as a year, a month, a day, and a time of day.
302 If this is specified,
303 the time zone information is generated from the given UTC offset
304 and rule change until the time specified.
305 The month, day, and time of day have the same format as the IN, ON, and AT
306 fields of a rule; trailing fields can be omitted, and default to the
307 earliest possible value for the missing fields.
309 The next line must be a
311 line; this has the same form as a zone line except that the
314 and the name are omitted, as the continuation line will
315 place information starting at the time specified as the
317 information in the previous line in the file used by the previous line.
318 Continuation lines may contain
320 information, just as zone lines do, indicating that the next line is a further
324 A link line has the form
325 .Dl "Link LINK-FROM LINK-TO"
327 .Dl "Link Europe/Istanbul Asia/Istanbul"
330 field should appear as the
332 field in some zone line;
335 field is used as an alternate name for that zone.
337 Except for continuation lines,
338 lines may appear in any order in the input.
340 Lines in the file that describes leap seconds have the following form:
341 .Dl "Leap YEAR MONTH DAY HH:MM:SS CORR R/S"
343 .Dl "Leap 1974 Dec 31 23:59:60 + S"
350 fields tell when the leap second happened.
356 if a second was added
359 if a second was skipped.
360 .\" There's no need to document the following, since it's impossible for more
361 .\" than one leap second to be inserted or deleted at a time.
362 .\" The C Standard is in error in suggesting the possibility.
363 .\" See Terry J Quinn, The BIPM and the accurate measure of time,
364 .\" Proc IEEE 79, 7 (July 1991), 894-905.
367 .\" if two seconds were added
370 .\" if two seconds were skipped.
374 should be (an abbreviation of)
376 if the leap second time given by the other fields should be interpreted as UTC
380 if the leap second time given by the other fields should be interpreted as
381 local wall clock time.
382 .Sh "EXTENDED EXAMPLE"
383 Here is an extended example of
385 input, intended to illustrate many of its features.
390 .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
392 # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
393 Rule Swiss 1940 only - Nov 2 0:00 1:00 S
394 Rule Swiss 1940 only - Dec 31 0:00 0 -
395 Rule Swiss 1941 1942 - May Sun>=1 2:00 1:00 S
396 Rule Swiss 1941 1942 - Oct Sun>=1 0:00 0
398 Rule EU 1977 1980 - Apr Sun>=1 1:00u 1:00 S
399 Rule EU 1977 only - Sep lastSun 1:00u 0 -
400 Rule EU 1978 only - Oct 1 1:00u 0 -
401 Rule EU 1979 1995 - Sep lastSun 1:00u 0 -
402 Rule EU 1981 max - Mar lastSun 1:00u 1:00 S
403 Rule EU 1996 max - Oct lastSun 1:00u 0 -
405 .ta \w'# Zone\0\0'u +\w'Europe/Zurich\0\0'u +\w'0:34:08\0\0'u +\w'RULES/SAVE\0\0'u +\w'FORMAT\0\0'u
406 # Zone NAME GMTOFF RULES FORMAT UNTIL
407 Zone Europe/Zurich 0:34:08 - LMT 1848 Sep 12
408 0:29:44 - BMT 1894 Jun
409 1:00 Swiss CE%sT 1981
412 Link Europe/Zurich Switzerland
416 In this example, the zone is named Europe/Zurich but it has an alias
418 Zurich was 34 minutes and 8 seconds west of GMT until 1848-09-12
419 at 00:00, when the offset changed to 29 minutes and 44 seconds.
420 After 1894-06-01 at 00:00 Swiss daylight saving rules (defined with
421 lines beginning with "Rule Swiss") apply, and the GMT offset became
423 From 1981 to the present, EU daylight saving rules have applied,
424 and the UTC offset has remained at one hour.
426 In 1940, daylight saving time applied from November 2 at 00:00 to
427 December 31 at 00:00.
428 In 1941 and 1942, daylight saving time applied from the first Sunday
429 in May at 02:00 to the first Sunday in October at 00:00.
430 The pre-1981 EU daylight-saving rules have no effect here, but are
431 included for completeness.
432 Since 1981, daylight saving has begun on the last Sunday in March
434 Until 1995 it ended the last Sunday in September at 01:00 UTC, but
435 this changed to the last Sunday in October starting in 1996.
437 For purposes of display, "LMT" and "BMT" were initially used,
439 Since Swiss rules and later EU rules were applied, the display name
440 for the timezone has been CET for standard time and CEST for daylight
443 For areas with more than two types of local time,
444 you may need to use local standard time in the
446 field of the earliest transition time's rule to ensure that
447 the earliest transition time recorded in the compiled file is correct.
449 If, for a particular zone, a clock advance caused by the start of
450 daylight saving coincides with and is equal to a clock retreat
451 caused by a change in UTC offset,
453 produces a single transition to daylight saving at the new UTC offset
454 (without any change in wall clock time).
455 To get separate transitions use multiple zone continuation lines
456 specifying transition instants using universal time.
458 .Bl -tag -width /usr/share/zoneinfo -compact
459 .It /usr/share/zoneinfo
460 standard directory used for created files
467 .\" This file is in the public domain, so clarified as of
468 .\" 2009-05-17 by Arthur David Olson.