Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P3
Fix Version/s: 8
Affects Version/s: 5.0, 6, 7
Component/s: core-libs
Labels:
- i18n-ldd
- release-note=done

Subcomponent:
java.text
Resolved In Build:
b55
CPU:

generic, sparc
OS:

generic, solaris_2.5.1
Verification:
Verified

Most internationalization components in Java are designed to be locale data driven. For example, if date/time format strings (e.g., "yyyy-MM-dd") and calendar component names (e.g., month names) for a locale are added to the Java runtime, java.text.DateFormat produces desired date and time output for the targetted local users without implementing a DateFormat subclass. In Java SE, however, the process for defining and deploying such locale data isn't established. Currently, you have to handcraft Java programs only to define locale data. The lack of the process makes it difficult for our localizers and licensees to add more locale support. Even maintenance of existing locale data is difficult for localizers because they are often non-Java programmers.

This RFE should address the following items.

- Define an input format for defining locale dependent data. LDML (Locale Data Markup Language) is preferred because it's a standard defined by the Unicode consortium. The input format must be committed to by Sun as the public interface for defining locale data.

- Develop a tool to generate locale data files for the runtime from the input format, assuming that interpreting an LDML file at runtime isn't feasible due to performance and footprint issues. The output file format shall remain Sun private for future extensions.

- Develop a mechanism to deploy locale data. (We may utilize Modules - JSR277 or brew our own.)

duplicates

JDK-7012373 need architectural change to fix localized Date format pattern

Closed

JDK-6332658 RFE: More locale support

Closed

JDK-6383647 Existing locale data in Java should be customizable

Closed

relates to

JDK-7193601 Build breakage with the fix to 6336885 (build-infra build)

Resolved

JDK-7196799 CLDR adapter can not be invoked when region code is specified in Locale

Closed

JDK-7151414 (cal) Support calendar type identification

Closed

JDK-7058206 Provide CalendarData SPI for week params and display field value names

Closed

JDK-8041702 Support the Bosnian Locale as bs_BA

Closed

JDK-6541880 NumberFormat for locale es_CR is wrong

Open

JDK-6560972 [Col] CollationRules should avoid new String(String)

Resolved

JDK-6369299 java.text.SimpleDateFormat: toLocalizedPattern() returns inappropriate string for many locales

Closed

JDK-7199794 Collator provider from SPI Adapter is loaded when they are assumed to be from JRE adapter

Closed

JDK-8015311 Incorporate the description for java.locale.providers system property into "Supported Locales" document

Resolved

JDK-4207993 RFE: Date formatting should support embedded forms of month names

Closed

JDK-6337471 desktop/system locale preferences support

Closed

JDK-7056110 (tz) Support timezone names from CLDR including generic names

Closed

JDK-8046117 JEP 127: Improve Locale Data Packaging and Adopt Unicode CLDR Data

Closed

(12 relates to)

Assignee:: Naoto Sato

Reporter:: Masayoshi Okutsu

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2005-10-13 22:15

Updated:: 2022-08-10 09:53

Resolved:: 2012-09-04 23:15

Imported:: 21/Sep/12 2:08 PM

Indexed:: 21/Sep/12 3:03 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates