-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 6, 6u7
-
Component/s: core-libs
-
b116
-
generic
-
generic, windows_xp
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2185355 | 6-pool | Masayoshi Okutsu | P3 | Closed | Won't Fix |
The spec for TimeZone.getDisplayName(...) says: "If the display name is not available for the locale, then this method returns a string in the normalized custom ID format."
In fact the methods return TimeZone.getDisplayName(Locale.ENGLISH) for unavailable locales.
In fact the methods return TimeZone.getDisplayName(Locale.ENGLISH) for unavailable locales.
- backported by
-
JDK-2185355 (tz) TimeZone.getDisplayName(...) spec is inconsistent with implementation for unavailable locales
-
- Closed
-
- duplicates
-
JDK-6695566 (tz) JCK test api/java_util/TimeZone/index.html#getDisplayName: Fails on machines with GMT timezone
-
- Closed
-
- relates to
-
JDK-6955047 (tz) javadoc for TimeZone.getDisplayName(boolean daylight, int style, Locale locale) is not clear
-
- Closed
-