From 81fb744538d89fbed90a3977aea12b003a510754 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 27 Jun 2018 11:37:33 -0700 Subject: [PROPOSED 2/3] Make last time type agree with draft TZif * tzfile.5: Say that the last time type is used only for consistency checking, instead of saying that it governs one second. Also, it matters only in the 64-bit data. --- tzfile.5 | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tzfile.5 b/tzfile.5 index ee7befb..79b19bf 100644 --- a/tzfile.5 +++ b/tzfile.5 @@ -68,11 +68,12 @@ at which the rules for computing local time change. .IP * .I tzh_timecnt one-byte unsigned integer values; -each one tells which of the different types of local time types +each one but the last tells which of the different types of local time types described in the file is associated with the time period starting with the same-indexed transition time -and continuing up to but not including the next transition time -(or continuing for one second, if this is the last transition). +and continuing up to but not including the next transition time. +(The last time type is present only for consistency checking with the +POSIX-style TZ string described below.) These values serve as indices into the next field. .IP * .I tzh_typecnt @@ -165,7 +166,7 @@ or for all instants if the file has no transitions. The POSIX-style TZ string is empty (i.e., nothing between the newlines) if there is no POSIX representation for such instants. If nonempty, the POSIX-style TZ string must agree with the local time -type after both data's last transition times if present; +type after the last transition time if present in the eight-byte data; for example, given the string .q "WET0WEST,M3.5.0,M10.5.0/3" then if a last transition time is in July, the transition's local time -- 2.7.4