On 2020-10-26 07:10, P Chan wrote:

...

Here is a full list of the orders related to the DST in Mandatory Palestine/Israel in 1940-2004.

Sorry, I suppose the text should be shown directly on the archive, instead of an attachment.

Given the lack of control of MIME type flagging in most email clients, it can be helpful to use indicative suffixes e.g .txt on text files, to avoid them being flagged as yours was "application/octet-stream", although many apps (e.g file) still seem to struggle with files using UTF-8 for some reason. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]

Thanks very much for all that work. I found only a couple of typos. First, the line beginning with "2000 Temporary Provisions" should end with 2000-10-06 not 2000-09-06. Second, citation 3 should be https://findit.library.yale.edu/images_layout/view?parentoid=15537491&increm... instead of the same URL ending in "=958". I ran into several ambiguities, where a transition at “midnight” might have been at 00:00 or 24:00, and might have been at standard time or daylight saving time. When resolving these ambiguities, I attempted to minimize the changes from existing tzdb. Most likely some errors remain, but still we should be better off than we were before. I installed the attached proposed patch to implement this. It reformats your file to fit into 80 columns when included as a comment. There are so many changes I didn't detail them all in NEWS, and I removed similar detail from Kenya news to be consistent. To give people a feel for the timestamp changes involved, I am also attaching the output of "diff -U4 to2050.tzs to2050new.tzs". This lists all changed timestamps. The columns are date, hour of day, UTC offset, abbreviation, and tm_isdst flag, with all columns (including hour) being in effect just *after* the transition.