Lines Matching refs:CLDR

6 # Commands for regenerating ICU4C locale data (.txt files) from CLDR,
7 # updated to apply to CLDR 37 / ICU 67 and later versions.
10 #    - CLDR (the source of most of the data, and some Java tools)
13 #      icu4c - the target for converted CLDR data, and source for ICU4J data;
18 # For an official CLDR data integration into ICU, these should be clean, freshly
19 # checked-out. For released CLDR sources, an alternative to checking out sources
25 # ICU is the version number and/or a CLDR git tag name for the revision of CLDR
56 # b) CLDR-related variables
58 # CLDR_DIR:      This is the path to the to root of standard CLDR sources, below
61 # CLDR_CLASSES:  Path to the CLDR Tools classes directory. If not set, defaults
64 # CLDR_TMP_DIR:  Parent of temporary CLDR production data.
67 #                *** NOTE ***: In CLDR 36 and 37, the GenerateProductionData tool
90 # files are used in addition to the CLDR files as inputs to the CLDR data build
99 # For an official CLDR data integration into ICU, there are some additional
102 # a) Don't commit anything in ICU sources (and possibly any changes in CLDR
106 # b) There are version numbers that may need manual updating in CLDR (other
116 # c) After everything is committed, you will need to tag the CLDR and ICU
127 # 1b. CLDR variables, adjust for your setup; with cygwin it might be e.g.
138 # 2. Build and install the CLDR jar
143 See the $TOOLS_ROOT/cldr/lib/README.txt file for more information on the CLDR
155 # 4a. Generate the CLDR production data. This process uses ant with ICU's
159 # (usually $CLDR_TMP_DIR/production ), required if any CLDR data has changed.
189 # 4c. Update the CLDR testData files needed by ICU4C and ICU4J tests, ensuring
190 # they're representative of the newest CLDR data.
195 # 4d. Copy from CLDR common/testData/localeIdentifiers/localeCanonicalization.txt
208 # 5a. You may also want to check which files were modified in CLDR production data:
215 # Fixing may entail modifying CLDR source data or TOOLS_ROOT config files or
229 # 8. Investigate each test case failure. The first run processing new CLDR data
231 # CLDR data fix can resolve hundreds of test failures). If the error is caused
232 # by bad CLDR data, then file a CLDR bug, fix the data, and regenerate from
252 # 10. Again, investigate each failure, fixing CLDR data or ICU test cases as
284 # or fix CLDR data and repeat from step 4, as appropriate, until there are no
286 # began testing the new CLDR data).
313 # 16. For an official CLDR data integration into ICU, now tag the CLDR and
314 # ICU sources with an appropriate CLDR milestone (you can check previous