| Other | Other |
|---|---|
| 1.3.1 ladybirdFixed | 1.4.0Fixed |
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Name: bb33257 Date: 02/17/98
Java Enhancement Request
Name: Localized time zone display names
Priority: High
Submitted On: 2/17/98
Contact: Alan Liu, IBM JTC
###@###.### 650-335-6651
Background
Currently, the JDK only contains English display names for time zone objects. Other systems such as Windows 95/NT provide localized names
for time zones. The JDK should contain localized time zone names, at the very least for the time zones in common usage in each locale.
Note that this API change request is not related to the request for a getDisplayName() method in TimeZone. Even without an exposed API,
users still see display names for time zones when they use SimpleDateFormat.format().
Proposed API
None. This is a resource data change only.
Implementation
Simple, once the data is obtained.
Risk assessment
Minimal risk.
SQE (product testing) impact
Little or no testing impact; some unit tests may be required to prove correct display name localization.
JCK (compatibility testing) impact
Little or no testing impact; some unit tests may be required to prove correct display name localization.
Doc impact
None.
======================================================================
al.smith@eng 2000-12-04
Test Failure is included in regression tests: java/text/Format
|