JDK-6276059 : Inconsistent handling of localized names from TimeZoneNameProvider
- Type: Bug
- Component: core-libs
- Sub-Component: java.util:i18n
- Affected Version: 6
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-05-25
- Updated: 2010-04-03
- Resolved: 2005-08-15
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b48Fixed  |
Related Reports
|
Relates :
|
Description
Currently, localized names from TimeZoneNameProvider.getDisplayName() are for standard time zone ids, and JRE internally translates them into their alias time zone names.
But standard vs. alias time zone id definition in the tz database sometimes changes, eg. to correct spellings ("Asia/Dacca" to "Asia/Dhaka"), and if an older time zone name provider provides localized names according to the older standard ids, that would never picked up by the JRE, since it may have become aliases at some point.
###@###.### 2005-05-25 17:39:22 GMT
Comments
|