Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8328980

Update CLDR to Version 45.0

XMLWordPrintable

    • Icon: CSR CSR
    • Resolution: Approved
    • Icon: P3 P3
    • 23
    • core-libs
    • None
    • behavioral
    • low
    • Hide
      As always, upgrading locale data has some risk of breaking applications that use locale-sensitive operations. One notable behavior change with this version is that the `CompactNumberFormat` with the `SHORT` style representing "million" in Italian has changed, due to the upstream CLDR fix [CLDR-17482](https://unicode-org.atlassian.net/browse/CLDR-17482))
      Show
      As always, upgrading locale data has some risk of breaking applications that use locale-sensitive operations. One notable behavior change with this version is that the `CompactNumberFormat` with the `SHORT` style representing "million" in Italian has changed, due to the upstream CLDR fix [CLDR-17482]( https://unicode-org.atlassian.net/browse/CLDR-17482) )
    • Java API
    • JDK

      Summary

      Update CLDR to Version 45.0

      Problem

      To keep up with the latest CLDR locale data in the JDK.

      Solution

      Incorporate the CLDR version 45 locale data

      Specification

      Add a row in the CLDR version vs. JDK version table in java.util.spi.LocaleServiceProvider class description as:

      --- a/src/java.base/share/classes/java/util/spi/LocaleServiceProvider.java
      +++ b/src/java.base/share/classes/java/util/spi/LocaleServiceProvider.java
      @@ -159,6 +159,8 @@
        *     <th scope="col">CLDR version</th></tr>
        * </thead>
        * <tbody>
      + * <tr><th scope="row" style="text-align:left">JDK 23</th>
      + *     <td>CLDR 45</td></tr>
        * <tr><th scope="row" style="text-align:left">JDK 22</th>
        *     <td>CLDR 44</td></tr>
        * <tr><th scope="row" style="text-align:left">JDK 21</th>

            naoto Naoto Sato
            naoto Naoto Sato
            Joe Wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: