Lines Matching +full:four +full:- +full:byte

2 .\" 1996-06-05 by Arthur David Olson.
15 Each file is a sequence of 8-bit bytes.
17 more bytes in network order (bigendian, or high-order byte first),
20 and a boolean is represented by a one-byte binary integer that is
22 The format begins with a 44-byte header containing the following fields:
24 .Bl -bullet
26 The magic four-byte ASCII sequence
30 A byte identifying the version of the file's format
39 Six four-byte integer values, in the following order:
41 .Bl -tag -compat -width tzh_ttisstdcnt
63 .Bl -tag -compat -width tzh_timecnt
65 four-byte signed integer values sorted in ascending order.
66 These values are written in network byte order.
71 one-byte unsigned integer values;
74 starting with the same-indexed transition time
83 .Bd -literal -offset indent
91 Each structure is written as a four-byte signed integer value for
93 in network byte order, followed by a one-byte boolean for
95 and a one-byte value for
110 entries in the file; if the designated string is "\*-00", the
115 value is never equal to \-2**31, to let 32-bit clients negate it without
119 is in the range [\-89999, 93599] (i.e., more than \-25 hours and less
121 already support the POSIX-required range [\-24:59:59, 25:59:59].
124 which are null-terminated byte strings, each indexed by the
127 The byte strings can overlap if one is a suffix of the other.
130 pairs of four-byte values, written in network byte order;
148 or \-1 for a negative leap second.
149 If the leap second table is empty, the leap-second correction is zero
152 the leap-second correction is zero if the first pair's correction is 1 or \-1,
156 standard/wall indicators, each stored as a one-byte boolean;
160 UT/local indicators, each stored as a one-byte boolean;
171 For example, when TZ="EET\*-2EEST" and there is no TZif file "EET\*-2EEST",
173 well-known name "posixrules" that is present only for this purpose and
176 the default rules are installation-dependent, and no implementation
180 TZ="EET\*-2EEST,M3.5.0/3,M10.5.0/4" if POSIX conformance is required
194 For version-2-format timezone files,
198 (Leap second counts remain four bytes.)
199 After the second header and data comes a newline-enclosed string
207 type after the last transition time if present in the eight-byte data;
211 type must specify a daylight-saving time abbreviated
218 For version-3-format timezone files, a TZ string (see
220 may use the following POSIX.1-2024 extensions to POSIX.1-2017:
221 First, as in TZ="<\*-02>2<\*-01>,M3.5.0/\*-1,M10.5.0/0",
223 \-167 through 167 instead of being limited to unsigned values
229 For version-4-format TZif files,
231 +1 nor \-1, to represent truncation of the TZif file at the start.
237 the added leap seconds will change how post-expiration timestamps are treated.
258 header and data block should be a contiguous sub-sequence
263 contiguous sub-sequence.
272 post-expiration timestamps, or process them as if the expiration
278 .Dq "\*-" ,
304 .Bl -bullet
323 new-version data useful even for older-version readers.
329 .Bl -bullet
340 they cannot parse the POSIX.1-2024 extensions to POSIX.1-2017
343 than necessary, so that only far-future timestamps are
351 (\-04).
355 for a time zone with a never-used standard time (XXX, \-03)
356 and negative daylight saving time (EDT, \-04) all year.
362 Atlantic Standard Time (\-04).
373 Some stripped-down readers ignore everything but the footer,
381 .Dq <+01>\*-1 ,
388 As a partial workaround, a writer can output a dummy (no-op)
392 transition that has a timestamp not less than \-2**31.
393 Readers that support only 32-bit timestamps are likely to be
395 64-bit transitions only some of which are representable in 32
398 transition at timestamp \-2**31.
401 the minimum possible signed 64-bit value.
402 Timestamps less than \-2**59 are not recommended.
417 non-ASCII characters.
423 .Dq "\*-",
429 daylight-saving time UT offsets that are less than the UT
433 .Dq "IST\*-1GMT0,M10.5.0,M3.5.0/1",
447 a positive leap second 78796801 (1972-06-30 23:59:60 UTC), some readers will
458 .Bl -bullet
462 in mind if they need to deal with pre-1970 data.
470 .Dq "\*-08"
473 .Dq "\*-" ,
477 traditional range of \-12 through +12 hours, and so do not
481 Some readers mishandle UT offsets in the range [\-3599, \-1]
482 seconds from UT, because they integer-divide the offset by