In order to bridge the gap between the offset information in TZDB and the simple scheme generic/standard/daylight in CLDR, would it not be a good enhancement to TZDB source format to add an extra column per rule line to flag if the dst offset (equal if zero, negative or positive) has to be considered as associated with standard time labelling? Then the consumer would not have to reason about (dstOffset == 0) <=> isStandardTimeFormat() as actually done in Java software. Such a column could even be enhanced by an extra state for the ramadan situation in some Arabic countries when the clock only temporarily switches back (enabling a better name). The actual column containing an abbreviation is not really clear about this name-offset-association IMHO and can therefore not be evaluated by source code based tz-compilers. Am 25.01.2018 um 22:20 schrieb Paul Eggert:
On 01/25/2018 12:43 PM, Paul G wrote:
Is this version information file intended for actual distribution and/or distributed by anyone? Although the version file is intended to be stable and useful for distributors who want to install it, it wasn't added until 2016h, tzdb Makefile does not install it, and I don't know of any distributions that install it. The file tzdata.zi is installed by default and it contains a version number, but this wasn't added until 2018a and hardly anybody uses it in production now.