JDK-6383647 : Existing locale data in Java should be customizable
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.util:i18n
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: solaris_2.5.1
- CPU: sparc
- Submitted: 2006-02-09
- Updated: 2014-06-06
- Resolved: 2012-01-31
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 8 |
|---|
8Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
The Locale Sensitive Services (LSS) SPI in Java SE 6 provides a means for users to add their own locale data. However, there is currently no way to modify the existing locale data provided in Java -- the data formerly provided in LocaleElements*.java now spread in CalendarData*.java, CollatorData*.java, CurrencyNames*.java, FormatData*.java, LocaleName*.java and TimeZoneNames*.java. An ideal solution would make available both programmatic and non-programmatic customizations.
Comments
|