Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 5861e1f

Browse filesBrowse files
committed
ICU-22221 update cldr-icu instructions, and ICU tag for integration
1 parent 69e1d70 commit 5861e1f
Copy full SHA for 5861e1f

File tree

Expand file treeCollapse file tree

2 files changed

+18
-3
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

2 files changed

+18
-3
lines changed
Open diff view settings
Collapse file

‎icu4c/source/data/cldr-icu-readme.txt‎

Copy file name to clipboardExpand all lines: icu4c/source/data/cldr-icu-readme.txt
+17-2Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,7 @@ export ANT_OPTS="-Xmx4096m"
131131
# CLDR_DIR=`cygpath -wp /build/cldr`
132132

133133
export CLDR_DIR=$HOME/cldr-myfork
134+
export CLDR_TMP_DIR=$HOME/cldr-staging
134135

135136
# 1c. ICU variables
136137

@@ -204,6 +205,12 @@ ant cleanprod
204205
ant setup
205206
ant proddata 2>&1 | tee $NOTES/cldr-newData-proddataLog.txt
206207

208+
#---
209+
# Note, for CLDR development, at this point tests are sometimes run on the production
210+
# data, see:
211+
# https://cldr.unicode.org/development/cldr-big-red-switch/brs-run-tests-on-production-data
212+
#---
213+
207214
# 5b. Build the new ICU4C data files; these include .txt files and .py files.
208215
# These new files will replace whatever was already present in the ICU4C sources.
209216
# This process uses the LdmlConverter in $TOOLS_ROOT/cldr/cldr-to-icu/;
@@ -363,8 +370,8 @@ git status
363370
# commit
364371

365372
# 16. For an official CLDR data integration into ICU, now tag the CLDR and
366-
# ICU sources with an appropriate CLDR milestone (you can check previous
367-
# tags for format), e.g.:
373+
# possibly the ICU sources with an appropriate CLDR milestone (you can check
374+
# previous tags for format), e.g.:
368375

369376
cd $CLDR_DIR
370377
git tag ...
@@ -383,5 +390,13 @@ cd $CLDR_TMP_DIR
383390
git tag ...
384391
git push --tags
385392

393+
# 18. You should publish the cldr and cldr-staging tags in github. For cldr, go to
394+
# https://github.com/unicode-org/cldr/tags and click on the tag you just created.
395+
# Click on the "Create release from tag" button at the upper right. Set release
396+
# title to be the same as the tag. Click the checkbox for "Set as a pre-release" for
397+
# all but the final release. For the description, see what was done for earlier tags.
398+
# When you are all ready, click the "Publish release" button.
399+
400+
386401

387402

Collapse file

‎tools/cldr/cldr-to-icu/pom.xml‎

Copy file name to clipboardExpand all lines: tools/cldr/cldr-to-icu/pom.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@
8383
<dependency>
8484
<groupId>com.ibm.icu</groupId>
8585
<artifactId>icu4j-for-cldr</artifactId>
86-
<version>73.1-cldr-2023-04-06</version>
86+
<version>73.1-cldr-2023-04-10</version>
8787
<!-- Note: see https://github.com/unicode-org/icu/packages/411079/versions
8888
for the icu4j-for-cldr version tag to use -->
8989
</dependency>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.