Lines Matching refs:CLDR

6 # Commands for regenerating ICU4C locale data (.txt files) from CLDR.
9 #    - CLDR (the source of most of the data, and some Java tools)
13 # For an official CLDR data integration into ICU, these should be clean, freshly
14 # checked-out. For released CLDR sources, an alternative to checking out sources
20 # ICU is the version number and/or a CLDR svn tag name for the revision of CLDR
23 # Note: Some versions of the OpenJDK will not build the CLDR java utilities.
45 # require http: access to files in the CLDR repository; for example, processing
72 # b) CLDR-related variables
74 # CLDR_DIR:      Path to root of CLDR sources, below which are the common and
77 #                are not running ant jar for CLDR and have a non-default output
92 # files are used in addition to the CLDR files as inputs to the CLDR data build
96 #                CLDR locales for inclusion in ICU. Update <paths> to prefer
102 #                are present in CLDR data (e.g. "de_AT", "de_BE", "de_CH", etc.)
117 # For an official CLDR data integration into ICU, there are some additional
120 # a) Don't commit anything in ICU sources (and possibly any changes in CLDR
124 # b) There are version numbers that may need manual updating in CLDR (other
132 # c) After everything is committed, you will need to tag the CLDR, ICU4J, and
143 # 1b. CLDR variables, adjust for your setup; with cygwin it might be e.g.
154 # 2. Build the CLDR Java tools
171 # operate (via CLDR's ant/CLDRConverterTool.java and ant/CLDRBuild.java) the
172 # necessary CLDR tools including LDML2ICUConverter, ConvertTransforms, etc.
178 # Unicode for access to the CLDR repository, see note on "IP address whitelisting"
200 # Fixing may entail modifying CLDR source data or tools - for example,
211 # 8. Investigate each test case failure. The first run processing new CLDR data
213 # CLDR data fix can resolve hundreds of test failures). If the error is caused
214 # by bad CLDR data, then file a CLDR bug, fix the data, and regenerate from
230 # 10. Again, investigate each failure, fixing CLDR data or ICU test cases as
255 # or fix CLDR data and repeat from step 4, as appropriate, until; there are no
257 # began testing the new CLDR data).
273 # 16. For an official CLDR data integration into ICU, now tag the CLDR and
274 # ICU sources with an appropriate CLDR milestone (you can check previous
283 --parents -m 'ticket:mmmm: tag the version used for integrating CLDR NNN'