From aa5c2335769edc091a3e570952693d3a409e68c5 Mon Sep 17 00:00:00 2001 From: Chris Pyle Date: Sun, 1 Sep 2024 22:07:59 -0400 Subject: [PATCH] CLDR-17566 text diffs and minor changes --- docs/site/TEMP-TEXT-FILES/adding-locales.txt | 6 +++--- docs/site/TEMP-TEXT-FILES/cldr-big-red-switch.txt | 6 +++--- docs/site/TEMP-TEXT-FILES/generating-charts.txt | 13 +++---------- docs/site/development/adding-locales.md | 2 +- docs/site/development/cldr-big-red-switch.md | 2 +- .../cldr-big-red-switch/generating-charts.md | 2 +- 6 files changed, 12 insertions(+), 19 deletions(-) diff --git a/docs/site/TEMP-TEXT-FILES/adding-locales.txt b/docs/site/TEMP-TEXT-FILES/adding-locales.txt index 5765aee107c..97d59c65b21 100644 --- a/docs/site/TEMP-TEXT-FILES/adding-locales.txt +++ b/docs/site/TEMP-TEXT-FILES/adding-locales.txt @@ -7,9 +7,9 @@ Before adding a new locale, you must have the core data: see Core Data for New L Here is an example: https://github.com/unicode-org/cldr/pull/59/files Add Data in git Before starting to add a new locale, make sure you have the minimal core data that cannot be added through the Survey Tool. See above. -Create the new locale files. If you are adding a single new language locale, for example, language "xx" as spoken in country "YY", you will need two files: -common/main/xx.xml - The main locale file containing the core data. You can use the template in seed/main/und.xml as a starting point. -common/main/xx_YY.xml - An empty country locale containing the identification of xx_YY as a valid locale. You can use the template in seed/main/und_XX.xml as a starting point. +Create the new locale files. If you are adding a single new language locale, for example, language "xx" as spoken in country "YY", you will need two files: +common/main/xx.xml - The main locale file containing the core data. You can use the template in seed/main/und.xml as a starting point. +common/main/xx_YY.xml - An empty country locale containing the identification of xx_YY as a valid locale. You can use the template in seed/main/und_XX.xml as a starting point. See files are here: https://github.com/unicode-org/cldr/tree/master/seed/main Add the plural rules (if available) to common/supplemental/plurals.xml Add the day period rules (if you have them ) to common/supplemental/dayPeriods.xml diff --git a/docs/site/TEMP-TEXT-FILES/cldr-big-red-switch.txt b/docs/site/TEMP-TEXT-FILES/cldr-big-red-switch.txt index f8a4ea4c7a0..7fa0c5ab302 100644 --- a/docs/site/TEMP-TEXT-FILES/cldr-big-red-switch.txt +++ b/docs/site/TEMP-TEXT-FILES/cldr-big-red-switch.txt @@ -9,6 +9,6 @@ For each release, we add names to the Unicode CLDR Acknowledgments page: http://cldr.unicode.org/index/acknowledgments. However, names are not automatically entered there, since some people may not wish to have their names listed. If your name is not there and you would like it to be, please send me your name as it should appear on that page. Your name should be in Latin characters, optionally with names in one or more other scripts in parentheses, such as "Vladimir Weinstein (Владимир Вајнштајн)" ---- how to send this message: currently a crude process ---- -1.get list of those who contributed through Survey tool (Login as TC, under 'Manage Users', click 'Email Address of Users Who Participated' (shows all users, not just your org) -2. e-mail that list on BCC: the above message with a subject line of "[CLDR X.Y Contributor Message]", and a request to please keep the subject line intact. -3. Then, the subject line can be used to filter/locate the contributor requests. \ No newline at end of file +get list of those who contributed through Survey tool (Login as TC, under 'Manage Users', click 'Email Address of Users Who Participated' (shows all users, not just your org) +e-mail that list on BCC: the above message with a subject line of "[CLDR X.Y Contributor Message]", and a request to please keep the subject line intact. +Then, the subject line can be used to filter/locate the contributor requests. \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/generating-charts.txt b/docs/site/TEMP-TEXT-FILES/generating-charts.txt index 6549ca3b199..97e0add57c1 100644 --- a/docs/site/TEMP-TEXT-FILES/generating-charts.txt +++ b/docs/site/TEMP-TEXT-FILES/generating-charts.txt @@ -10,7 +10,7 @@ On each of the subpages, take the first chart on each page, recursively. Use the "Index" link to go back up (not the back button), and make sure it goes to the right version of the page. Check into github on cldr-staging Start Release -Make sure the version  (eg 99) is right in ToolConstants +Make sure the version (eg 99) is right in ToolConstants Make sure the last number (eg 99.0) is in CLDR_VERSIONS Set DEFAULT_CHART_VERSION = "99"; Add an new folder with that number, such as cldr-staging/docs/charts/99 @@ -40,12 +40,5 @@ Modifying the chart programs The chart programs have grown over time, and need some cleanup. For example, the supplemental charts duplicate code that is now in SupplementalDataInfo. ShowLanguages. The messages that they use are in a file util/data/chart_messages.html. The right cell contains the key, which is extracted by lines like: -PrintWriter pw = new PrintWriter(new FormattedFileWriter(index, "Zone \u2192 Tzid", null)); -The key will be zone_tzid, in this case. -Generate -Start Release -Mid-release -Prefinal Release -Final Release -Modifying the chart programs -ShowLanguages. \ No newline at end of file + PrintWriter pw = new PrintWriter(new FormattedFileWriter(index, "Zone \u2192 Tzid", null)); +The key will be zone_tzid, in this case. \ No newline at end of file diff --git a/docs/site/development/adding-locales.md b/docs/site/development/adding-locales.md index b88dc4c19ba..176974acbed 100644 --- a/docs/site/development/adding-locales.md +++ b/docs/site/development/adding-locales.md @@ -12,7 +12,7 @@ If you are just adding a new country locale (eg we have a locale for the languag ### Minimal Structure -Before adding a new locale, you must have the core data: see[Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales) for the process. +Before adding a new locale, you must have the core data: see [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales) for the process. Here is an example: https://github.com/unicode-org/cldr/pull/59/files diff --git a/docs/site/development/cldr-big-red-switch.md b/docs/site/development/cldr-big-red-switch.md index b744d4c939a..68d6e47a301 100644 --- a/docs/site/development/cldr-big-red-switch.md +++ b/docs/site/development/cldr-big-red-switch.md @@ -8,7 +8,7 @@ title: CLDR: Big Red Switch *All: remember to make sure that the* ***target: X*** *is set on all the X bugs, otherwise the Release Changes link won't pick them up.* -*Items marked \* are for the "Little Red Switch": dot\-dot releases (*supplemental data, ids, timezones, small spec fixes). Items marked \*\* are only done for a LRS if there was a DTD change. +*Items marked \* are for the "Little Red Switch": dot\-dot releases (supplemental data, ids, timezones, small spec fixes). Items marked \*\* are only done for a LRS if there was a DTD change.* ### Trial New Version (Let us know if you need write access!) diff --git a/docs/site/development/cldr-big-red-switch/generating-charts.md b/docs/site/development/cldr-big-red-switch/generating-charts.md index e73bb526c17..cc2136b6d94 100644 --- a/docs/site/development/cldr-big-red-switch/generating-charts.md +++ b/docs/site/development/cldr-big-red-switch/generating-charts.md @@ -30,7 +30,7 @@ The input for this is the cldr\-staging/production file, and the output is in gi 1. Use the VM arguements 1. \-DCHART\_VERSION\=**99** - 2. \-DCHART\_STATUS\=**beta** // \=*default*, uses trunk, calls it β' + 2. \-DCHART\_STATUS\=**beta** // \=*default*, uses trunk, calls it β ## Prefinal Release