Update CLDR to Version 49.0

XMLWordPrintable

    • Type: CSR
    • Resolution: Unresolved
    • Priority: P3
    • 27
    • Component/s: core-libs
    • None
    • behavioral
    • low
    • Hide
      As always, upgrading locale data has some risk of breaking applications that use locale-sensitive operations. Notable changes in
      CLDR-19106: zh_Hant short date+time formats can't be parsed (#5219) // zh_HK dateTimeFormat: "{0}{1}" -> "{0} {1}"
      Show
      As always, upgrading locale data has some risk of breaking applications that use locale-sensitive operations. Notable changes in CLDR-19106: zh_Hant short date+time formats can't be parsed (#5219) // zh_HK dateTimeFormat: "{0}{1}" -> "{0} {1}"
    • Java API
    • JDK

      Summary

      Update CLDR to Version 49.0

      Problem

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

      Solution

      Incorporate the CLDR version 49 locale data

      Specification

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

         * <thead>
   * <tr><th scope="col">JDK release</th>
   *     <th scope="col">CLDR version</th></tr>
   * </thead>
   * <tbody>
+  * <tr><th scope="row" style="text-align:left">JDK 27</th>
+  *     <td>CLDR 49</td></tr>
   * <tr><th scope="row" style="text-align:left">JDK 26</th>
   *     <td>CLDR 48</td></tr>
   * <tr><th scope="row" style="text-align:left">JDK 25</th>
   *     <td>CLDR 47</td></tr>
   * <tr><th scope="row" style="text-align:left">JDK 24</th>

            Assignee:
            Naoto Sato
            Reporter:
            Naoto Sato
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: