Hi Mark, Yes - that's the same fix that was put in the JDK releases. The issue is only relevant for the Asia/Amman TZ as you mentioned. It was fixed in 6u15(b02), 5.0u20(b02) and 1.4.2_22(b02) as mentioned by bug report. Fix to JDK 7 is due shortly also. regards, Sean. Mark Wielaard wrote: Hi, I was debugging the following bug report: http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=377 "TimeZone.getOffset() fails for some TZ" The issue is caused because there is a start rule in the Asia/Amman timezone that starts at the end of a day. SimpleTimeZone doesn't allow that. I have a simple "fix" (attached), but I haven't fully tested it yet, and don't know if there could be other problems with allowing a rule to start on the last milisecond of a day.I noticed there is a similar bug report here: http://bugs.sun.com/view_bug.do?bug_id=6851214 That is marked as "State 11-Closed, Verified, bug". There is however very little information on how this was fixed. Does anybody on this list know more? Thanks, Mark |
- <i18n dev> Jordan (Asia/Amman) versus SimpleTimeZ... Mark Wielaard
- Re: <i18n dev> Jordan (Asia/Amman) versus Si... Andrew John Hughes
- Re: <i18n dev> Jordan (Asia/Amman) versus Si... Sean Coffey
- Re: <i18n dev> Jordan (Asia/Amman) versu... Mark Wielaard