-
Bug
-
Resolution: Fixed
-
P3
-
1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.6, 1.1.7, 1.1.8, 1.2.0, 1.2.1, 1.2.2, 1.3.0
-
kestrel
-
generic, other, x86, sparc
-
generic, solaris_2.5.1, solaris_2.6, windows_95, windows_98, windows_nt
Another problem of platform-to-java time zone mapping is that it's based on numeric comparisons (except for English Windows). Therefore, there is no way to distinguish two (or more) different time zones that have the same GMT offset. Use of Daylight Saving Time is a parameter for the maching, but different DST schedule is not considered, which also causes mapping errors for some time zones.
- duplicates
-
JDK-4044013 VM not detecting host timezone correctly (was Clock is not displaying correct ti
-
- Closed
-
-
JDK-4208984 Win32: Wrong default timezone in Melbourne Australia
-
- Closed
-
-
JDK-4225280 British Summer Time still not working
-
- Closed
-
-
JDK-4341030 Only one set of Daylight Saving rules can apply for each offset from GMT
-
- Closed
-
- relates to
-
JDK-4267616 wrong time offsets, and short time representation [NT jdk1.2.1's TimeZone]
-
- Closed
-
-
JDK-4290844 WinNT: problem of default time zone
-
- Resolved
-
-
JDK-4256567 Java TimeZone needs more timezones to support platform timezones
-
- Resolved
-
-
JDK-6390869 TimeZone.getDefault() returns different timezones for Windows GMT-12 when DST is checked and not.
-
- Resolved
-
-
JDK-4276858 Regression test: java/util/TimeZone/WinTZVM.sh error
-
- Closed
-