-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
7
-
None
-
other
-
solaris_10
ConvertLocaleDataTool needs some adjustment
1. Currently the tool can produce files with duplicated contens under the same language code for CalendarData properties files. For example, CalendarData_sr_RS.properties and CalendarData_sr_ME.properties can be newly generated with the same data. In such case, CalendarData_sr.properties should be created and discard CalendarData_sr_RS.properties and CalendarData_sr_ME.properties. This became an issue starting CLDR 1.4. CLDR 1.4 moved weekData and monthData to SupplementalData.xml file, and CLDR does not associate these data with any language code, but just territory code while JRE's CalendarData must have language code. Tool should examine the contents of the CalendarData files under the same language code, and create a new CalendarData_[language code].properties file to gather all the comon data.
2. This tool should be integrated into our j2se ws (make) and generate the data during the build time
1. Currently the tool can produce files with duplicated contens under the same language code for CalendarData properties files. For example, CalendarData_sr_RS.properties and CalendarData_sr_ME.properties can be newly generated with the same data. In such case, CalendarData_sr.properties should be created and discard CalendarData_sr_RS.properties and CalendarData_sr_ME.properties. This became an issue starting CLDR 1.4. CLDR 1.4 moved weekData and monthData to SupplementalData.xml file, and CLDR does not associate these data with any language code, but just territory code while JRE's CalendarData must have language code. Tool should examine the contents of the CalendarData files under the same language code, and create a new CalendarData_[language code].properties file to gather all the comon data.
2. This tool should be integrated into our j2se ws (make) and generate the data during the build time