JDK-8167322 : Release Note: Use CLDR locale data by default
  • Type: Sub-task
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Delivered
  • OS: generic
  • CPU: generic
  • Submitted: 2016-10-06
  • Updated: 2017-09-22
  • Resolved: 2017-09-22
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.
In JDK 9, the default locale data uses data derived from the Unicode Consortium's Common Locale Data Repository (CLDR). As a result, users may see differences in locale sensitive services behavior and/or translations. For example, CLDR does not provide localized display names for most 3-letter time zone IDs, thus the display names may be different from JDK 8 and older. The JDK continues to ship with the legacy JRE locale data and the system property `java.locale.providers` can be used to configure the lookup order. To enable behavior compatible with JDK 8, the system property can be set with:


For more detail, refer to the [JEP 252][jep252].

[jep252]: http://openjdk.java.net/jeps/252
Re-opened to modify the RN content to include more detailed compatibility notes, such as differences for 3-letter time zone ID.