New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BclDateTimeZone for Windhoek (Namibia) doesn't match Windows behaviour #115

Closed
GoogleCodeExporter opened this Issue Mar 15, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@GoogleCodeExporter

GoogleCodeExporter commented Mar 15, 2015

The Windhoek time zone in Windows is particularly odd - it has a negative 
daylight saving time for some of the time, to allow for a change in standard 
time (which doesn't seem to agree with TZDB, but never mind).

There are two adjustment rules, with the boundary being at the start of 2011. 
Normally adjustment rules has the same offset both sides, but in this case the 
rule boundary also acts as a daylight saving transition, apparently. We don't 
currently cope with this. More investigation required.

Original issue reported on code.google.com by jonathan.skeet on 5 Sep 2012 at 9:28

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

Output from a quick diagnostic tool showing transitions from the BCL:

01/01/2009 01:00:00
06/04/2009 00:00:00
07/09/2009 01:00:00
05/04/2010 00:00:00
06/09/2010 01:00:00
01/01/2011 02:00:00
03/04/2011 01:00:00
05/09/2011 02:00:00
01/04/2012 01:00:00
03/09/2012 02:00:00
07/04/2013 01:00:00
02/09/2013 02:00:00

So the adjustment rule change also acts as a transition :(

Original comment by jonathan.skeet on 6 Sep 2012 at 9:13

GoogleCodeExporter commented Mar 15, 2015

Output from a quick diagnostic tool showing transitions from the BCL:

01/01/2009 01:00:00
06/04/2009 00:00:00
07/09/2009 01:00:00
05/04/2010 00:00:00
06/09/2010 01:00:00
01/01/2011 02:00:00
03/04/2011 01:00:00
05/09/2011 02:00:00
01/04/2012 01:00:00
03/09/2012 02:00:00
07/04/2013 01:00:00
02/09/2013 02:00:00

So the adjustment rule change also acts as a transition :(

Original comment by jonathan.skeet on 6 Sep 2012 at 9:13

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

This issue was closed by revision 7ed7fcbfa0da.

Original comment by jonathan.skeet on 22 Oct 2012 at 8:14

  • Changed state: Fixed

GoogleCodeExporter commented Mar 15, 2015

This issue was closed by revision 7ed7fcbfa0da.

Original comment by jonathan.skeet on 22 Oct 2012 at 8:14

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

Original comment by malcolm.rowe on 10 Nov 2012 at 10:20

  • Added labels: Milestone-1.0.0
  • Removed labels: Milestone-1.0

GoogleCodeExporter commented Mar 15, 2015

Original comment by malcolm.rowe on 10 Nov 2012 at 10:20

  • Added labels: Milestone-1.0.0
  • Removed labels: Milestone-1.0

@malcolmr malcolmr added the bug label Mar 15, 2015

@malcolmr malcolmr modified the milestone: 1.0.0 Mar 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment