-
Enhancement
-
Resolution: Fixed
-
P2
-
None
-
b71
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8135948 | emb-9 | Naoto Sato | P2 | Resolved | Fixed | team |
---
Currently, CLDR locale data are available only when the user explicitly specifies it in a system property, e.g.,
java.locale.providers=JRE,SPI,CLDR
So although the JRE contains the CLDR locale data, it is not used at all by default.
This issue is to enable the CLDR locales without having the user specify this system property, but still have the equivalent locale provider adapter preference order as the above example.
- backported by
-
JDK-8135948 Use CLDR Locale Data by Default
-
- Resolved
-
- blocks
-
JDK-8043554 JEP 252: Use CLDR Locale Data by Default
-
- Closed
-
- duplicates
-
JDK-8114833 java.time.format.DateTimeFormatter does not work as documented
-
- Closed
-
- relates to
-
JDK-8130109 Incremental build of java.base-gensrc broken
-
- Resolved
-
-
JDK-8153041 Remove unused redundant parameter in CLDRConverter
-
- Closed
-
-
JDK-8138613 Remove SPI locale provider adapter from the default provider list
-
- Closed
-
-
JDK-8167143 CLDR timezone parsing does not work for all locales
-
- Resolved
-
-
JDK-8244843 [JDK 8u] JapanEraNameCompatTest fails
-
- Resolved
-
-
JDK-8130845 Change to CLDR Locale data in JDK 9 b71 causes SimpleDateFormat parsing errors
-
- Closed
-
-
JDK-8129881 JDK-8008577 breaks Nashorn test
-
- Closed
-
-
JDK-8131041 Garbage in output of DecimalFormat
-
- Closed
-
-
JDK-8134250 Create unit tests for CLDR unique features
-
- Closed
-
-
JDK-6712094 DateFormat produces incorrect short date pattern for en_GB locale
-
- Closed
-
-
JDK-8252383 NumberFormat.parse fails with some locale providers
-
- Closed
-