Time format error in Olson TZ rules for Asia

[Stephen Colebourne]

On 27 April 2010 17:15, Olson, Arthur David (NIH/NCI) [E]
<olsona at dc37a.nci.nih.gov> wrote:
>  | For this particular case, I've jumped in my time machine and changed
>  | the timezone compiler so that a rule such as...
>  |
>  |     Rule whatever 2010 max - Mar Fri>=26 2:00 1:00 D
>  |
>  | ...does the right thing.
>
>> That's good, I didn't know that we had that ability - so the Jordan rule
>> could be changed to use that, right?   That is, your comment was more to
>> the point that "lastFri" is not equivalent to "day after lastThu", rather
>> than saying that we needed to retain 24:00 in the data file.
>
> Well...the "24:00" support was introduced in 1998, while the "Fri>=26" support was introduced in 2004.
> So going with "24:00" makes more out-in-the-field time zone compilers happy.

>From a Java JSR-310 perspective, coding the 24:00 support was a real
pain. It breaks the rest of the model of the library. I handled it
with a special case boolean "is end of day".

I have no support for 26:00 (representing 2am on the following day).
Adding this to the database would thus cause real issues.

Stephen