On 2016-04-08, at 09:29, Hobart Spitz wrote: > I think that if you clearly document the distinction, then I would think > that different behaviors for +hh:mm versus hh:mm would make sense. > > An alternative/additional solution, possibly too much trouble, would be to > add a timezone to the time specification: E.g. 10:30-EST, 18:15-CDT, > etc. Why too much trouble? No all countries change clocks on the same day. > IANA TZDATA accounts for this. Necessarily, it's no lightweight; utterly unsuitable for a CP function.
> I'm not sure how often this comes up, or why, so that might have a > bearing. If it's more than just clock changes in fall and spring, that > would matter. > Far more. Examples: North Korea set its clocks back 30 minutes on 2015-08-15 and nation of Samoa set its clocks forward 24 hours(!) on 2011-12-29. TZDATA accommodates this, so Linux and Java correctly convert both recent and historic timestamps. -- gil
