From 2a17138c0ad267abdaf8df1b4168e2443722367b Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Fri, 4 Oct 2024 14:30:20 -0500 Subject: [PATCH] CLDR-17999 site: fix some markdown links from https://cldr.unicode.org (#4109) --- docs/site/ddl.md | 2 +- docs/site/development/adding-locales.md | 6 +- docs/site/development/cldr-big-red-switch.md | 2 +- .../cldr-big-red-switch/generating-charts.md | 4 +- .../site/development/cldr-development-site.md | 18 +-- .../updating-englishroot.md | 2 +- .../documenting-cldr-tools.md | 4 +- docs/site/development/creating-the-archive.md | 8 +- docs/site/development/development-process.md | 8 +- .../development-process/design-proposals.md | 108 +++++++++--------- .../design-proposals/bcp-47-changes-draft.md | 10 +- .../design-proposals/change-to-sites.md | 2 +- ...-forms-for-datetime-elements-and-others.md | 2 +- .../iso-636-deprecation-requests-draft.md | 2 +- ...g-approved-by-the-cldr-tc-on-2015-03-25.md | 2 +- .../language-distance-data.md | 2 +- .../pattern-character-for-related-year.md | 2 +- .../design-proposals/post-mortem.md | 2 +- docs/site/development/maven.md | 4 +- docs/site/development/new-cldr-developers.md | 4 +- docs/site/development/running-tests.md | 6 +- docs/site/development/updating-codes.md | 28 ++--- .../likelysubtags-and-default-content.md | 2 +- .../updating-codes/update-currency-codes.md | 2 +- .../update-language-script-info.md | 8 +- .../update-languagescriptregion-subtags.md | 6 +- .../update-time-zone-data-for-zoneparser.md | 2 +- .../updating-codes/update-validity-xml.md | 2 +- .../updating-population-gdp-literacy.md | 2 +- .../updating-script-metadata.md | 6 +- .../updating-subdivision-codes.md | 2 +- .../updating-subdivision-translations.md | 4 +- docs/site/development/updating-dtds.md | 20 ++-- docs/site/downloads/cldr-31.md | 4 +- docs/site/downloads/cldr-32.md | 4 +- docs/site/downloads/cldr-33-1.md | 4 +- docs/site/downloads/cldr-33.md | 4 +- docs/site/downloads/cldr-34.md | 8 +- docs/site/downloads/cldr-35.md | 4 +- docs/site/downloads/cldr-36.md | 4 +- docs/site/downloads/cldr-37.md | 4 +- docs/site/downloads/cldr-38.md | 4 +- docs/site/downloads/cldr-39.md | 4 +- docs/site/downloads/cldr-40.md | 4 +- docs/site/downloads/cldr-41.md | 6 +- docs/site/downloads/cldr-42.md | 4 +- docs/site/downloads/cldr-43.md | 14 +-- docs/site/downloads/cldr-44.md | 20 ++-- docs/site/downloads/cldr-45.md | 6 +- docs/site/downloads/cldr-46.md | 60 +++++----- docs/site/index.md | 18 +-- docs/site/index/charts.md | 6 +- docs/site/index/cldr-spec.md | 14 +-- .../index/cldr-spec/collation-guidelines.md | 4 +- .../cldr-spec/core-data-for-new-locales.md | 12 +- docs/site/index/cldr-spec/coverage-levels.md | 8 +- docs/site/index/cldr-spec/currency-process.md | 2 +- .../picking-the-right-language-code.md | 10 +- docs/site/index/cldr-spec/plural-rules.md | 4 +- docs/site/index/corrigenda.md | 2 +- docs/site/index/downloads.md | 58 +++++----- docs/site/index/draft-schedule.md | 4 +- docs/site/index/json-format-data.md | 2 +- docs/site/index/keyboard-workgroup.md | 4 +- docs/site/index/locale-coverage.md | 6 +- docs/site/index/process.md | 10 +- docs/site/index/survey-tool.md | 8 +- .../index/survey-tool/bulk-data-upload.md | 6 +- docs/site/index/survey-tool/coverage.md | 4 +- .../index/survey-tool/faq-and-known-bugs.md | 10 +- docs/site/index/survey-tool/managing-users.md | 6 +- .../index/survey-tool/survey-tool-accounts.md | 4 +- docs/site/requesting_changes.md | 14 +-- docs/site/translation.md | 54 ++++----- docs/site/translation/characters.md | 6 +- .../characters/short-names-and-keywords.md | 8 +- .../characters/typographic-names.md | 4 +- docs/site/translation/core-data.md | 6 +- docs/site/translation/core-data/characters.md | 2 +- docs/site/translation/core-data/exemplars.md | 2 +- .../translation/currency-names-and-symbols.md | 2 +- .../currency-names.md | 4 +- docs/site/translation/date-time.md | 8 +- .../translation/date-time/date-time-names.md | 26 ++--- .../date-time/date-time-patterns.md | 32 +++--- .../date-time/date-time-symbols.md | 12 +- docs/site/translation/displaynames.md | 10 +- .../countryregion-territory-names.md | 4 +- .../displaynames/languagelocale-names.md | 6 +- .../displaynames/locale-option-names-key.md | 4 +- .../translation/displaynames/script-names.md | 4 +- docs/site/translation/error-codes.md | 4 +- docs/site/translation/getting-started.md | 24 ++-- .../getting-started/errors-and-warnings.md | 10 +- .../site/translation/getting-started/guide.md | 42 +++---- .../translation/getting-started/plurals.md | 12 +- .../getting-started/review-formats.md | 2 +- .../getting-started/survey-tool-phases.md | 18 +-- .../getting-started/vetting-view.md | 12 +- .../translation/grammatical-inflection.md | 2 +- docs/site/translation/language-specific.md | 6 +- .../miscellaneous-person-name-formats.md | 2 +- .../translation/number-currency-formats.md | 6 +- .../number-and-currency-patterns.md | 8 +- .../number-currency-formats/number-symbols.md | 2 +- .../translation/time-zones-and-city-names.md | 4 +- .../translation/translation-guide-general.md | 6 +- .../default-content.md | 2 +- docs/site/translation/unique-translations.md | 6 +- docs/site/translation/units.md | 4 +- .../units/unit-names-and-patterns.md | 2 +- 111 files changed, 513 insertions(+), 513 deletions(-) diff --git a/docs/site/ddl.md b/docs/site/ddl.md index 04052e88a5e..8cf2f72cb7c 100644 --- a/docs/site/ddl.md +++ b/docs/site/ddl.md @@ -4,7 +4,7 @@ title: CLDR DDL Subcommittee # CLDR DDL Subcommittee -The Common Locale Data Repository (CLDR) is [widely used](https://cldr.unicode.org/index), and the content has grown dramatically over the years with participation by organizations of all types and sizes, as well as many individual contributors. +The Common Locale Data Repository (CLDR) is [widely used](/index), and the content has grown dramatically over the years with participation by organizations of all types and sizes, as well as many individual contributors. Contributors for Digitally Disadvantaged Languages (DDL) face unique challenges. The CLDR-DDL subcommittee has been formed to evaluate mechanisms to make it easier for contributors for DDLs to: diff --git a/docs/site/development/adding-locales.md b/docs/site/development/adding-locales.md index 464a8a5089b..10516b1b0aa 100644 --- a/docs/site/development/adding-locales.md +++ b/docs/site/development/adding-locales.md @@ -4,7 +4,7 @@ title: Adding a new locale to CLDR # Adding a new locale to CLDR -NOTE: this is an internal page for TC developers. Others should see [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales). +NOTE: this is an internal page for TC developers. Others should see [Core Data for New Locales](/index/cldr-spec/core-data-for-new-locales). ### Country Locales @@ -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](/index/cldr-spec/core-data-for-new-locales) for the process. Here is an example: https://github.com/unicode-org/cldr/pull/59/files @@ -33,7 +33,7 @@ Here is an example: https://github.com/unicode-org/cldr/pull/59/files - The default content locale is usually the locale where the most people speak the language in question. - If the language is not already in common/supplemental/likelySubtags.xml - Send the literate pop information to Rick, or file a bug, if the language is not already in the supplemental data. - - Once he has added, run the tool in [LikelySubtags and Default Content](https://cldr.unicode.org/development/updating-codes/likelysubtags-and-default-content) to add the new language and its associated subtags to common/supplemental/likelySubtags.xml + - Once he has added, run the tool in [LikelySubtags and Default Content](/development/updating-codes/likelysubtags-and-default-content) to add the new language and its associated subtags to common/supplemental/likelySubtags.xml - Also add the English translation for any new languages in **common/main/en.xml** - If requested, add to vendor targets (Locale.txt), and to Cldr where resources are committed. - Run the tests (will be done automatically when a PR is created) diff --git a/docs/site/development/cldr-big-red-switch.md b/docs/site/development/cldr-big-red-switch.md index 68d35af128b..bad4d2592a5 100644 --- a/docs/site/development/cldr-big-red-switch.md +++ b/docs/site/development/cldr-big-red-switch.md @@ -12,7 +12,7 @@ title: 'CLDR: Big Red Switch' ### Trial New Version (Let us know if you need write access!) -(For editors: [List View of BRS](https://cldr.unicode.org/development/cldr-big-red-switch/list-view-of-brs), [Spreadsheet View](https://docs.google.com/spreadsheets/d/1dIOLxKX2gW7BRDVdMBH9qr1GdxpPj8Bc1Pe-02p_92k/edit#gid=0)) +(For editors: [List View of BRS](/development/cldr-big-red-switch/list-view-of-brs), [Spreadsheet View](https://docs.google.com/spreadsheets/d/1dIOLxKX2gW7BRDVdMBH9qr1GdxpPj8Bc1Pe-02p_92k/edit#gid=0)) ## Contributor Message 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 4de770558bb..bd89516a8b1 100644 --- a/docs/site/development/cldr-big-red-switch/generating-charts.md +++ b/docs/site/development/cldr-big-red-switch/generating-charts.md @@ -23,7 +23,7 @@ The input for this is the cldr\-staging/production file, and the output is in gi 1. Make sure the *last* number (eg **99\.0**) is in CLDR\_VERSIONS 2. Set DEFAULT\_CHART\_VERSION \= "99"; 2. Add an new folder with that number, such as cldr\-staging/docs/charts/**99** -3. Create the archive ([Creating the Archive](https://cldr.unicode.org/development/creating-the-archive)) with at least the last release (if you don't have it already) +3. Create the archive ([Creating the Archive](/development/creating-the-archive)) with at least the last release (if you don't have it already) 4. **Use the same VM arguments as Mid\-Release** ## Mid\-release @@ -49,7 +49,7 @@ The input for this is the cldr\-staging/production file, and the output is in gi 1. \-DCHART\_VERSION\=**99** 2. \-DCHART\_STATUS\=**release** (only uses the cldr\-archive, no β) 2. Change the page to add the new release -3. Check the redirection links on [test\-chart\-links](https://cldr.unicode.org/development/cldr-big-red-switch/test-chart-links). +3. Check the redirection links on [test\-chart\-links](/development/cldr-big-red-switch/test-chart-links). 4. On index.html; open it, and fix the version (eg to 25β \=\> 25\) ## Modifying the chart programs diff --git a/docs/site/development/cldr-development-site.md b/docs/site/development/cldr-development-site.md index 0bb27878765..dd3ac70fcdc 100644 --- a/docs/site/development/cldr-development-site.md +++ b/docs/site/development/cldr-development-site.md @@ -6,15 +6,15 @@ title: CLDR Development Site Some of the key pages for developers are: -1. [New CLDR Developers](https://cldr.unicode.org/development/new-cldr-developers) - 1. [Maven Setup](https://cldr.unicode.org/development/maven) (for command line & Eclipse) - 1. Obsolete (but may still contain useful nuggets): [Eclipse Setup](https://cldr.unicode.org/development/eclipse-setup) - 2. [Eclipse](https://cldr.unicode.org/development/running-survey-tool/building-and-running-the-survey-tool-on-eclipse) (survey tool) -2. [Handling Tickets (bugs/enhancements)](https://cldr.unicode.org/development/development-process) -3. [Updating DTDs](https://cldr.unicode.org/development/updating-dtds) -4. [Editing CLDR Spec](https://cldr.unicode.org/development/editing-cldr-spec) - 1. [CLDR: Big Red Switch](https://cldr.unicode.org/development/cldr-big-red-switch) (checklist for release) -5. [Adding a new locale to CLDR](https://cldr.unicode.org/development/adding-locales) +1. [New CLDR Developers](/development/new-cldr-developers) + 1. [Maven Setup](/development/maven) (for command line & Eclipse) + 1. Obsolete (but may still contain useful nuggets): [Eclipse Setup](/development/eclipse-setup) + 2. [Eclipse](/development/running-survey-tool/building-and-running-the-survey-tool-on-eclipse) (survey tool) +2. [Handling Tickets (bugs/enhancements)](/development/development-process) +3. [Updating DTDs](/development/updating-dtds) +4. [Editing CLDR Spec](/development/editing-cldr-spec) + 1. [CLDR: Big Red Switch](/development/cldr-big-red-switch) (checklist for release) +5. [Adding a new locale to CLDR](/development/adding-locales) The subpages listed give more information on internal CLDR development. See also: [Sitemap](https://sites.google.com/site/cldr/system/app/pages/sitemap/hierarchy). diff --git a/docs/site/development/cldr-development-site/updating-englishroot.md b/docs/site/development/cldr-development-site/updating-englishroot.md index 21fcfdeeb0b..3c05c9cc290 100644 --- a/docs/site/development/cldr-development-site/updating-englishroot.md +++ b/docs/site/development/cldr-development-site/updating-englishroot.md @@ -18,7 +18,7 @@ The tool is in tools/java/org/unicode/cldr/tool/GenerateBirth.java. It requires **CldrUtility.ARCHIVE\_DIRECTORY** -1. Create the archive ([Creating the Archive](https://cldr.unicode.org/development/creating-the-archive)) with all releases (if you don't have it already) +1. Create the archive ([Creating the Archive](/development/creating-the-archive)) with all releases (if you don't have it already) 2. The archive directory should have the latest version of every major and minor version (where versions before 21\.0 have the major version split across the top two fields). 3. You will probably need to modify both CldrVersion.java and ToolConstants.java to bring them up to date. diff --git a/docs/site/development/coding-cldr-tools/documenting-cldr-tools.md b/docs/site/development/coding-cldr-tools/documenting-cldr-tools.md index d725333ebae..d7112f26f5d 100644 --- a/docs/site/development/coding-cldr-tools/documenting-cldr-tools.md +++ b/docs/site/development/coding-cldr-tools/documenting-cldr-tools.md @@ -8,7 +8,7 @@ title: Documenting CLDR Tools You can add the @CLDRTool annotation to any class in cldr\-code that has a main() function, and it will be documented as part of the JAR cldr\-code.jar is used. -See [CLDR Tools](https://cldr.unicode.org/development/cldr-tools) for general information about obtaining and using CLDR tools. +See [CLDR Tools](/development/cldr-tools) for general information about obtaining and using CLDR tools. ## Coding it @@ -41,5 +41,5 @@ Additional parameters: - **hidden** \- if non\-empty, this specifies a reason to *not* show the tool when running "java \-jar" without "\-l". For example, the main() function may be a less\-useful internal tool, or a test. ## Documenting it -Assuming your tools’s alias is *myalias,* create a new subpage with the URL http://cldr.unicode.org/tools/myalias (a subpage of [CLDR Tools](https://cldr.unicode.org/development/cldr-tools)). Fill this page out with information about how to use your tool. +Assuming your tools’s alias is *myalias,* create a new subpage with the URL http://cldr.unicode.org/tools/myalias (a subpage of [CLDR Tools](/development/cldr-tools)). Fill this page out with information about how to use your tool. diff --git a/docs/site/development/creating-the-archive.md b/docs/site/development/creating-the-archive.md index 89726127743..827f6867526 100644 --- a/docs/site/development/creating-the-archive.md +++ b/docs/site/development/creating-the-archive.md @@ -6,9 +6,9 @@ title: Checking out the CLDR Archive A number of the tools in CLDR depend on access to older versions. These tools include: -- [Generating Charts](https://cldr.unicode.org/development/cldr-big-red-switch/generating-charts) -- [Update Validity XML](https://cldr.unicode.org/development/updating-codes/update-validity-xml) -- [Updating English/Root](https://cldr.unicode.org/development/cldr-development-site/updating-englishroot) +- [Generating Charts](/development/cldr-big-red-switch/generating-charts) +- [Update Validity XML](/development/updating-codes/update-validity-xml) +- [Updating English/Root](/development/cldr-development-site/updating-englishroot) - \[Note: add others when we find them] - Some tests - TestCompatibility.java @@ -20,7 +20,7 @@ A number of the tools in CLDR depend on access to older versions. These tools in ### Here's how to do that. -1. Create an archive directory **cldr\-archive**. The Simplest is if it on the same level as your local CLDR repository. In other words, if your [CLDR\_DIR](https://cldr.unicode.org/development/cldr-development-site/running-cldr-tools) is .../workspace/cldr, then create the directory  **…/workspace/cldr\-archive**
+1. Create an archive directory **cldr\-archive**. The Simplest is if it on the same level as your local CLDR repository. In other words, if your [CLDR\_DIR](/development/cldr-development-site/running-cldr-tools) is .../workspace/cldr, then create the directory  **…/workspace/cldr\-archive**
(Note: The Java property **ARCHIVE** can be used to overide the path to cldr\-archive). 2. Open up ToolConstants.java and look at ToolConstants.CLDR\_VERSIONS. You'll see something like: 1. **public static final** List\ ***CLDR\_VERSIONS*** \= ImmutableList.of( diff --git a/docs/site/development/development-process.md b/docs/site/development/development-process.md index fb91d86899f..21df193f016 100644 --- a/docs/site/development/development-process.md +++ b/docs/site/development/development-process.md @@ -87,12 +87,12 @@ When a ticket is in design, the owner is responsible for bringing back to the co ### DTD Changes -- **If you are making any DTD changes, please follow the instructions on** [**Updating DTDs**](https://cldr.unicode.org/development/updating-dtds)**.** +- **If you are making any DTD changes, please follow the instructions on** [**Updating DTDs**](/development/updating-dtds)**.** ### Testing! - Add unit tests for changes you make, then -- **Make sure to run the tests in** [**Running Tests**](https://cldr.unicode.org/development/running-tests)**!** +- **Make sure to run the tests in** [**Running Tests**](/development/running-tests)**!** Skipping test failures @@ -120,8 +120,8 @@ If there is a test failure that is due to a bug that cannot be fixed right now ( 2. ***Check*** [http://unicode.org/cldr/trac/timeline?changeset\=on\&build\=on\&daysback\=8](http://unicode.org/cldr/trac/timeline?changeset=on&build=on&daysback=8) to verify that no changes "slipped in" 3. ***Add a line PUSHING*** 4. ***Push to production*** -5. *If there were noticeable changes, put them in* [*http://cldr.unicode.org/index/survey\-tool\#TOC\-Latest\-Updates*](http://cldr.unicode.org/index/survey-tool#TOC-Latest-Updates) ***(move the old items up to Tool Updates).*** -6. *If it was a Known Bug, remove from* [*https://sites.google.com/site/cldr/index/survey\-tool/known\-bugs*](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs)***.*** +5. *If there were noticeable changes, put them in* [*http://cldr.unicode.org/index/survey\-tool\#TOC\-Latest\-Updates*](/index/survey-tool#TOC-Latest-Updates) ***(move the old items up to Tool Updates).*** +6. *If it was a Known Bug, remove from* [*https://sites.google.com/site/cldr/index/survey\-tool/known\-bugs*](/index/survey-tool/faq-and-known-bugs)***.*** 7. ***Change status of all READY and PUSHING items to PUSHED.*** 8. ***You can delete some older items that are no longer relevant.*** 9. ***If the spreadsheet data seems stale, switch to the BuildsCheckins tab, and increment the 'to update' cell. \[ If anyone knows a better way to structure the spreadsheet, please feel free.. \-srl]*** diff --git a/docs/site/development/development-process/design-proposals.md b/docs/site/development/development-process/design-proposals.md index b065233d9d5..d861b368106 100644 --- a/docs/site/development/development-process/design-proposals.md +++ b/docs/site/development/development-process/design-proposals.md @@ -6,111 +6,111 @@ title: Design Proposals This section contains design proposals, listed as subpages below. -In each proposal, please add a header and a TOC if it is longer than a page. You can cut&paste the structure in [Proposed Collation Additions](https://cldr.unicode.org/development/development-process/design-proposals/proposed-collation-additions) and make the necessary changes. +In each proposal, please add a header and a TOC if it is longer than a page. You can cut&paste the structure in [Proposed Collation Additions](/development/development-process/design-proposals/proposed-collation-additions) and make the necessary changes. -[Alternate Time Formats](https://cldr.unicode.org/development/development-process/design-proposals/alternate-time-formats) +[Alternate Time Formats](/development/development-process/design-proposals/alternate-time-formats) -[BCP 47 Changes (DRAFT)](https://cldr.unicode.org/development/development-process/design-proposals/bcp-47-changes-draft) +[BCP 47 Changes (DRAFT)](/development/development-process/design-proposals/bcp-47-changes-draft) -[BCP47 Syntax Mapping](https://cldr.unicode.org/development/development-process/design-proposals/bcp47-syntax-mapping) +[BCP47 Syntax Mapping](/development/development-process/design-proposals/bcp47-syntax-mapping) -[BCP47 Validation and Canonicalization](https://cldr.unicode.org/development/development-process/design-proposals/bcp47-validation-and-canonicalization) +[BCP47 Validation and Canonicalization](/development/development-process/design-proposals/bcp47-validation-and-canonicalization) -[BIDI handling of Structured Text](https://cldr.unicode.org/development/development-process/design-proposals/bidi-handling-of-structured-text) +[BIDI handling of Structured Text](/development/development-process/design-proposals/bidi-handling-of-structured-text) -[Change to Sites?](https://cldr.unicode.org/development/development-process/design-proposals/change-to-sites) +[Change to Sites?](/development/development-process/design-proposals/change-to-sites) -[Chinese (and other) calendar support, intercalary months, year cycles](https://cldr.unicode.org/development/development-process/design-proposals/chinese-and-other-calendar-support-intercalary-months-year-cycles) +[Chinese (and other) calendar support, intercalary months, year cycles](/development/development-process/design-proposals/chinese-and-other-calendar-support-intercalary-months-year-cycles) -[Consistent Casing](https://cldr.unicode.org/development/development-process/design-proposals/consistent-casing) +[Consistent Casing](/development/development-process/design-proposals/consistent-casing) -[Coverage Revision](https://cldr.unicode.org/development/development-process/design-proposals/coverage-revision) +[Coverage Revision](/development/development-process/design-proposals/coverage-revision) -[Currency Code Fallback](https://cldr.unicode.org/development/development-process/design-proposals/currency-code-fallback) +[Currency Code Fallback](/development/development-process/design-proposals/currency-code-fallback) -[Day-Period Design](https://cldr.unicode.org/development/development-process/design-proposals/day-period-design) +[Day-Period Design](/development/development-process/design-proposals/day-period-design) -[Delimiter (Quotation Mark) Proposal](https://cldr.unicode.org/development/development-process/design-proposals/delimiter-quotation-mark-proposal) +[Delimiter (Quotation Mark) Proposal](/development/development-process/design-proposals/delimiter-quotation-mark-proposal) -[English Inheritance](https://cldr.unicode.org/development/development-process/design-proposals/english-inheritance) +[English Inheritance](/development/development-process/design-proposals/english-inheritance) -[European Ordering Rules Issues](https://cldr.unicode.org/development/development-process/design-proposals/european-ordering-rules-issues) +[European Ordering Rules Issues](/development/development-process/design-proposals/european-ordering-rules-issues) -[Extended Windows-Olson zid mapping](https://cldr.unicode.org/development/development-process/design-proposals/extended-windows-olson-zid-mapping) +[Extended Windows-Olson zid mapping](/development/development-process/design-proposals/extended-windows-olson-zid-mapping) -[Fractional Plurals](https://cldr.unicode.org/development/development-process/design-proposals/fractional-plurals) +[Fractional Plurals](/development/development-process/design-proposals/fractional-plurals) -[Generic calendar data](https://cldr.unicode.org/development/development-process/design-proposals/generic-calendar-data) +[Generic calendar data](/development/development-process/design-proposals/generic-calendar-data) -[Grammar & capitalization forms for date/time elements and others](https://cldr.unicode.org/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others) +[Grammar & capitalization forms for date/time elements and others](/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others) -[Grapheme Usage](https://cldr.unicode.org/development/development-process/design-proposals/grapheme-usage) +[Grapheme Usage](/development/development-process/design-proposals/grapheme-usage) -[Hebrew Months](https://cldr.unicode.org/development/development-process/design-proposals/hebrew-months) +[Hebrew Months](/development/development-process/design-proposals/hebrew-months) -[Index Characters](https://cldr.unicode.org/development/development-process/design-proposals/index-characters) +[Index Characters](/development/development-process/design-proposals/index-characters) -[Islamic Calendar Types](https://cldr.unicode.org/development/development-process/design-proposals/islamic-calendar-types) +[Islamic Calendar Types](/development/development-process/design-proposals/islamic-calendar-types) -[ISO 636 Deprecation Requests - DRAFT](https://cldr.unicode.org/development/development-process/design-proposals/iso-636-deprecation-requests-draft) +[ISO 636 Deprecation Requests - DRAFT](/development/development-process/design-proposals/iso-636-deprecation-requests-draft) -[JSON Packaging (Approved by the CLDR TC on 2015-03-25)](https://cldr.unicode.org/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25) +[JSON Packaging (Approved by the CLDR TC on 2015-03-25)](/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25) -[Language Data Consistency](https://cldr.unicode.org/development/development-process/design-proposals/language-data-consistency) +[Language Data Consistency](/development/development-process/design-proposals/language-data-consistency) -[Language Distance Data](https://cldr.unicode.org/development/development-process/design-proposals/language-distance-data) +[Language Distance Data](/development/development-process/design-proposals/language-distance-data) -[List Formatting](https://cldr.unicode.org/development/development-process/design-proposals/list-formatting) +[List Formatting](/development/development-process/design-proposals/list-formatting) -[Locale Format](https://cldr.unicode.org/development/development-process/design-proposals/locale-format) +[Locale Format](/development/development-process/design-proposals/locale-format) -[Localized GMT Format](https://cldr.unicode.org/development/development-process/design-proposals/localized-gmt-format) +[Localized GMT Format](/development/development-process/design-proposals/localized-gmt-format) -[Math Formula Preferences](https://cldr.unicode.org/development/development-process/design-proposals/math-formula-preferences) +[Math Formula Preferences](/development/development-process/design-proposals/math-formula-preferences) -[New BCP47 Extension T Fields](https://cldr.unicode.org/development/development-process/design-proposals/new-bcp47-extension-t-fields) +[New BCP47 Extension T Fields](/development/development-process/design-proposals/new-bcp47-extension-t-fields) -[New Time Zone Patterns](https://cldr.unicode.org/development/development-process/design-proposals/new-time-zone-patterns) +[New Time Zone Patterns](/development/development-process/design-proposals/new-time-zone-patterns) -[Path Filtering](https://cldr.unicode.org/development/development-process/design-proposals/path-filtering) +[Path Filtering](/development/development-process/design-proposals/path-filtering) -[Pattern character for “related year”](https://cldr.unicode.org/development/development-process/design-proposals/pattern-character-for-related-year) +[Pattern character for “related year”](/development/development-process/design-proposals/pattern-character-for-related-year) -[Pinyin Fixes](https://cldr.unicode.org/development/development-process/design-proposals/pinyin-fixes) +[Pinyin Fixes](/development/development-process/design-proposals/pinyin-fixes) -[Post Mortem](https://cldr.unicode.org/development/development-process/design-proposals/post-mortem) +[Post Mortem](/development/development-process/design-proposals/post-mortem) -[Proposed Collation Additions](https://cldr.unicode.org/development/development-process/design-proposals/proposed-collation-additions) +[Proposed Collation Additions](/development/development-process/design-proposals/proposed-collation-additions) -[Resolution of CLDR files](https://cldr.unicode.org/development/development-process/design-proposals/resolution-of-cldr-files) +[Resolution of CLDR files](/development/development-process/design-proposals/resolution-of-cldr-files) -[script-metadata](https://cldr.unicode.org/development/development-process/design-proposals/script-metadata) +[script-metadata](/development/development-process/design-proposals/script-metadata) -[Search collators](https://cldr.unicode.org/development/development-process/design-proposals/search-collators) +[Search collators](/development/development-process/design-proposals/search-collators) -[Secular/neutral eras](https://cldr.unicode.org/development/development-process/design-proposals/secularneutral-eras) +[Secular/neutral eras](/development/development-process/design-proposals/secularneutral-eras) -[Specifying text break variants in locale IDs](https://cldr.unicode.org/development/development-process/design-proposals/specifying-text-break-variants-in-locale-ids) +[Specifying text break variants in locale IDs](/development/development-process/design-proposals/specifying-text-break-variants-in-locale-ids) -[Suggested Exemplar Revisions](https://cldr.unicode.org/development/development-process/design-proposals/suggested-exemplar-revisions) +[Suggested Exemplar Revisions](/development/development-process/design-proposals/suggested-exemplar-revisions) -[Supported NumberingSystems](https://cldr.unicode.org/development/development-process/design-proposals/supported-numberingsystems) +[Supported NumberingSystems](/development/development-process/design-proposals/supported-numberingsystems) -[Thoughts on Survey Tool Backend](https://cldr.unicode.org/development/development-process/design-proposals/thoughts-on-survey-tool-backend) +[Thoughts on Survey Tool Backend](/development/development-process/design-proposals/thoughts-on-survey-tool-backend) -[Time Zone Data Reorganization](https://cldr.unicode.org/development/development-process/design-proposals/time-zone-data-reorganization) +[Time Zone Data Reorganization](/development/development-process/design-proposals/time-zone-data-reorganization) -[Transform Fallback](https://cldr.unicode.org/development/development-process/design-proposals/transform-fallback) +[Transform Fallback](/development/development-process/design-proposals/transform-fallback) -[Transform keywords](https://cldr.unicode.org/development/development-process/design-proposals/transform-keywords) +[Transform keywords](/development/development-process/design-proposals/transform-keywords) -[Unihan Data](https://cldr.unicode.org/development/development-process/design-proposals/unihan-data) +[Unihan Data](/development/development-process/design-proposals/unihan-data) -[Units: pixels, ems, display resolution](https://cldr.unicode.org/development/development-process/design-proposals/units-pixels-ems-display-resolution) +[Units: pixels, ems, display resolution](/development/development-process/design-proposals/units-pixels-ems-display-resolution) -[UTS #35 Splitting](https://cldr.unicode.org/development/development-process/design-proposals/uts-35-splitting) +[UTS #35 Splitting](/development/development-process/design-proposals/uts-35-splitting) -[Voting](https://cldr.unicode.org/development/development-process/design-proposals/voting) +[Voting](/development/development-process/design-proposals/voting) -[XMB](https://cldr.unicode.org/development/development-process/design-proposals/xmb) +[XMB](/development/development-process/design-proposals/xmb) diff --git a/docs/site/development/development-process/design-proposals/bcp-47-changes-draft.md b/docs/site/development/development-process/design-proposals/bcp-47-changes-draft.md index c26c3eeaf03..4a619cb4c1f 100644 --- a/docs/site/development/development-process/design-proposals/bcp-47-changes-draft.md +++ b/docs/site/development/development-process/design-proposals/bcp-47-changes-draft.md @@ -4,7 +4,7 @@ title: BCP 47 Changes (DRAFT) # BCP 47 Changes (DRAFT) -With the new release of the new version of [BCP 47](http://www.inter-locale.com/ID/draft-ietf-ltru-4646bis-18.html), there are various changes we need to make in Unicode CLDR and LDML. Already in CLDR 1.7 we have made modifications anticipating the release: see [BCP 47 Tag Conversion](http://unicode.org/reports/tr35/#BCP_47_Tag_Conversion) in the spec (and the orginal [design proposal](https://cldr.unicode.org/development/development-process/design-proposals/bcp47-syntax-mapping)), but more changes need to be made. +With the new release of the new version of [BCP 47](http://www.inter-locale.com/ID/draft-ietf-ltru-4646bis-18.html), there are various changes we need to make in Unicode CLDR and LDML. Already in CLDR 1.7 we have made modifications anticipating the release: see [BCP 47 Tag Conversion](http://unicode.org/reports/tr35/#BCP_47_Tag_Conversion) in the spec (and the orginal [design proposal](/development/development-process/design-proposals/bcp47-syntax-mapping)), but more changes need to be made. ## Formula @@ -37,10 +37,10 @@ B. We show a script code S for translation if and only if it is one of the scrip \* *official status* means official, de facto official, official regional, or de facto official regional. -† *population* means literate 14-day active users (well, theoretically - we can only get an approximation of that), based on [CLDR figures](http://www.unicode.org/cldr/data/charts/supplemental/language_territory_information.html). Our concern is with written language, not spoken, and so we don't focus on variants that don't have much written usage; moreover, the population figures we want to focus on are the literate population. For this reason and others, we don't rely on the Ethnologue figures. See also [Picking the Right Language Code](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code). +† *population* means literate 14-day active users (well, theoretically - we can only get an approximation of that), based on [CLDR figures](http://www.unicode.org/cldr/data/charts/supplemental/language_territory_information.html). Our concern is with written language, not spoken, and so we don't focus on variants that don't have much written usage; moreover, the population figures we want to focus on are the literate population. For this reason and others, we don't rely on the Ethnologue figures. See also [Picking the Right Language Code](/index/cldr-spec/picking-the-right-language-code). -**Please review the generated lists in** [**Filtered Scripts and Languages**](https://cldr.unicode.org/development/development-process/design-proposals/bcp-47-changes-draft)**.** A spreadsheet with some details is on. The first column is the language, 2rd is the world population of the language (literate), and the remaining columns are the reasons (data for 1.1, 1.2, 1.3 from the above). +**Please review the generated lists in** [**Filtered Scripts and Languages**](/development/development-process/design-proposals/bcp-47-changes-draft)**.** A spreadsheet with some details is on. The first column is the language, 2rd is the world population of the language (literate), and the remaining columns are the reasons (data for 1.1, 1.2, 1.3 from the above). Known issues: @@ -55,7 +55,7 @@ We would add the lists to the supplemental metadata for access by the tools. The ## Other Changes -We also need to make other changes to the spec in regards to the new version of BCP 47. In particular, those [macrolanguages](http://www.sil.org/iso639-3/macrolanguages.asp) with an encompassed language that is a "predominant form", CLDR treats the predominant form and the macrolanguage as aliases. See [Locale Field Definitions](http://unicode.org/reports/tr35/#Locale_Field_Definitions) in the spec. We need to flesh that table out to include all of the [macrolanguages](http://www.sil.org/iso639-3/macrolanguages.asp) that are in the [Included Languages](https://cldr.unicode.org/development/development-process/design-proposals/bcp-47-changes-draft), such as Azerbaijani. Here is a start at that (but still just draft). The first part of this list is from a draft of BCP 47bis. The last three are codes that are in the current (2006) version of BCP 47. +We also need to make other changes to the spec in regards to the new version of BCP 47. In particular, those [macrolanguages](http://www.sil.org/iso639-3/macrolanguages.asp) with an encompassed language that is a "predominant form", CLDR treats the predominant form and the macrolanguage as aliases. See [Locale Field Definitions](http://unicode.org/reports/tr35/#Locale_Field_Definitions) in the spec. We need to flesh that table out to include all of the [macrolanguages](http://www.sil.org/iso639-3/macrolanguages.asp) that are in the [Included Languages](/development/development-process/design-proposals/bcp-47-changes-draft), such as Azerbaijani. Here is a start at that (but still just draft). The first part of this list is from a draft of BCP 47bis. The last three are codes that are in the current (2006) version of BCP 47. Macrolanguage Table @@ -98,7 +98,7 @@ Also, we should consider modifying the canonical form of language identifiers so ## Filtered Scripts and Languages -The following script/language names would be included (/excluded) from default translation. For the method used to get this list, see [Formula](https://cldr.unicode.org/development/development-process/design-proposals/bcp-47-changes-draft). +The following script/language names would be included (/excluded) from default translation. For the method used to get this list, see [Formula](/development/development-process/design-proposals/bcp-47-changes-draft). The languages are listed in the format Abkhazian [ab]-OR, where [xx] is the code, and "OR" is the abbreviated "best" status in some territory: **U**nknown, **O**fficial **R**egional, **O**fficial **M**inority, **D**e facto official, **O**fficial. diff --git a/docs/site/development/development-process/design-proposals/change-to-sites.md b/docs/site/development/development-process/design-proposals/change-to-sites.md index c9ee9f94423..24ba78f8587 100644 --- a/docs/site/development/development-process/design-proposals/change-to-sites.md +++ b/docs/site/development/development-process/design-proposals/change-to-sites.md @@ -4,7 +4,7 @@ title: Change to Sites? # Change to Sites? -We are using Sites ([http://cldr.unicode.org/](http://cldr.unicode.org/)) to host all of the CLDR development web pages. I took a look at the cldr pages, and the following are not in Sites. The question is, should we move them (or some of them) to Sites? +We are using Sites ([http://cldr.unicode.org/](/)) to host all of the CLDR development web pages. I took a look at the cldr pages, and the following are not in Sites. The question is, should we move them (or some of them) to Sites? Advantages diff --git a/docs/site/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others.md b/docs/site/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others.md index 206766d29a4..9d0109686f6 100644 --- a/docs/site/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others.md +++ b/docs/site/development/development-process/design-proposals/grammar-capitalization-forms-for-datetime-elements-and-others.md @@ -90,7 +90,7 @@ The current choice between “format” and “standalone” forms conflates all ### 3. Related docs -Mark had some [discussion and ideas](https://cldr.unicode.org/development/development-process/design-proposals/consistent-casing) in [#2269](http://unicode.org/cldr/trac/ticket/2269). +Mark had some [discussion and ideas](/development/development-process/design-proposals/consistent-casing) in [#2269](http://unicode.org/cldr/trac/ticket/2269). ## C. Outline of proposed solution diff --git a/docs/site/development/development-process/design-proposals/iso-636-deprecation-requests-draft.md b/docs/site/development/development-process/design-proposals/iso-636-deprecation-requests-draft.md index ba16add846d..d9953adfe75 100644 --- a/docs/site/development/development-process/design-proposals/iso-636-deprecation-requests-draft.md +++ b/docs/site/development/development-process/design-proposals/iso-636-deprecation-requests-draft.md @@ -4,7 +4,7 @@ title: ISO 636 Deprecation Requests - DRAFT # ISO 636 Deprecation Requests - DRAFT -We have become aware over time of cases where ISO 639 inaccurately assigns different language codes to the same language. Its goal is to distinguish all and only those languages that are are not mutually comprehensible. Making too many distinctions can be as harmful as making too few, since it artificially separates two dialects, and disrupts the ability of software to identify them as variants. The remedy used in the past has been to deprecate codes: for example, [mol (mo)](http://www.sil.org/iso639-3/documentation.asp?id=mol) has been merged with [rol (ro)](http://www.sil.org/iso639-3/documentation.asp?id=rol). See also [Picking the Right Language Code](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) and [Language Distance Data](https://cldr.unicode.org/development/development-process/design-proposals/language-distance-data). +We have become aware over time of cases where ISO 639 inaccurately assigns different language codes to the same language. Its goal is to distinguish all and only those languages that are are not mutually comprehensible. Making too many distinctions can be as harmful as making too few, since it artificially separates two dialects, and disrupts the ability of software to identify them as variants. The remedy used in the past has been to deprecate codes: for example, [mol (mo)](http://www.sil.org/iso639-3/documentation.asp?id=mol) has been merged with [rol (ro)](http://www.sil.org/iso639-3/documentation.asp?id=rol). See also [Picking the Right Language Code](/index/cldr-spec/picking-the-right-language-code) and [Language Distance Data](/development/development-process/design-proposals/language-distance-data). The current cases in question are listed below. However we need to collate and organize a background document of information before we go further. diff --git a/docs/site/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25.md b/docs/site/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25.md index 0085a33c549..651182e390b 100644 --- a/docs/site/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25.md +++ b/docs/site/development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25.md @@ -4,7 +4,7 @@ title: JSON Packaging (Approved by the CLDR TC on 2015-03-25) # JSON Packaging (Approved by the CLDR TC on 2015-03-25) -***This page is out of date, see*** [***http://cldr.unicode.org/index/downloads#TOC-JSON-Data***](http://cldr.unicode.org/index/downloads#TOC-JSON-Data) ***for details of the JSON data.*** +***This page is out of date, see*** [***http://cldr.unicode.org/index/downloads#TOC-JSON-Data***](/index/downloads#TOC-JSON-Data) ***for details of the JSON data.*** ## Overview diff --git a/docs/site/development/development-process/design-proposals/language-distance-data.md b/docs/site/development/development-process/design-proposals/language-distance-data.md index 979b8b1502a..a385b1bdd14 100644 --- a/docs/site/development/development-process/design-proposals/language-distance-data.md +++ b/docs/site/development/development-process/design-proposals/language-distance-data.md @@ -115,7 +115,7 @@ Note that this doesn't have to be an N x M algorithm. Because there is a minimum ## Data Sample -The data is designed to be relatively simple to understand. It would typically be processed into an internal format for fast processing. The data does not need to be exact; only the relative computed values are important. However, for keep the types of fields apart, they are given very different values. TODO: add values for [ISO 636 Deprecation Requests - DRAFT](https://cldr.unicode.org/development/development-process/design-proposals/iso-636-deprecation-requests-draft) +The data is designed to be relatively simple to understand. It would typically be processed into an internal format for fast processing. The data does not need to be exact; only the relative computed values are important. However, for keep the types of fields apart, they are given very different values. TODO: add values for [ISO 636 Deprecation Requests - DRAFT](/development/development-process/design-proposals/iso-636-deprecation-requests-draft) \ diff --git a/docs/site/development/development-process/design-proposals/pattern-character-for-related-year.md b/docs/site/development/development-process/design-proposals/pattern-character-for-related-year.md index 57c259bf07a..2fb4f51afbf 100644 --- a/docs/site/development/development-process/design-proposals/pattern-character-for-related-year.md +++ b/docs/site/development/development-process/design-proposals/pattern-character-for-related-year.md @@ -27,5 +27,5 @@ In ICU, each calendar could provide an internal method that would return that of The data and format requirements for section 2.2 above are more complex and not addressed here -See also the earlier discussion of these issues in section F.11 of the proposal “[Chinese (and other) calendar support, intercalary months, year cycles](https://cldr.unicode.org/development/development-process/design-proposals/chinese-and-other-calendar-support-intercalary-months-year-cycles).” +See also the earlier discussion of these issues in section F.11 of the proposal “[Chinese (and other) calendar support, intercalary months, year cycles](/development/development-process/design-proposals/chinese-and-other-calendar-support-intercalary-months-year-cycles).” diff --git a/docs/site/development/development-process/design-proposals/post-mortem.md b/docs/site/development/development-process/design-proposals/post-mortem.md index b3838c0b869..fabda5b8a29 100644 --- a/docs/site/development/development-process/design-proposals/post-mortem.md +++ b/docs/site/development/development-process/design-proposals/post-mortem.md @@ -11,7 +11,7 @@ Drivers marked in [...]. Drivers are to file bugs, put together plan for how to 1. Spec done late, little review, little time for public review. We should have a formal release and announcement ahead of time. Splitting up the spec into functional pieces, maintained in Sites, could let us put the introductory info into the pieces at the start. Move the design doc into the spec once approved. Point the survey tool to relevant parts of the spec. Sync up spec for each milestone. **[Peter, Mark]** 2. How to get metazone translated. Not enough coverage. We ask for translations that are not needed in the survey tool; those also contribute to the lack of coverage. 1. Make coverage be data driven. - 2. Make metazone coverage exclude items that never need coverage; be dependant on the language (and the territories that use it). [http://cldr.unicode.org/development/design-proposals/coverage-revision](http://cldr.unicode.org/development/design-proposals/coverage-revision) + 2. Make metazone coverage exclude items that never need coverage; be dependant on the language (and the territories that use it). [http://cldr.unicode.org/development/design-proposals/coverage-revision](/development/design-proposals/coverage-revision) 3. Make coverage visible in ST. 4. Make metazones easier to understand in the ST. Better examples of how they affect zones. 5. CommonlyUsed can't be effectively entered in ST. diff --git a/docs/site/development/maven.md b/docs/site/development/maven.md index 8b1ee268d59..0eb520dff56 100644 --- a/docs/site/development/maven.md +++ b/docs/site/development/maven.md @@ -75,7 +75,7 @@ In the CLDR repo root, go into the tools directory and run: ```mvn package``` -This will run all tests and create the all\-in\-one **tools/cldr\-code/target/cldr\-code.jar**. See [CLDR Tools](https://cldr.unicode.org/development/cldr-tools) for details on how to use this jar file. +This will run all tests and create the all\-in\-one **tools/cldr\-code/target/cldr\-code.jar**. See [CLDR Tools](/development/cldr-tools) for details on how to use this jar file. ### More details @@ -112,7 +112,7 @@ mvn -DCLDR_DIR=$HOME/src/cldr exec:java -pl cldr-code -Dexec.mainClass=org.unico 1. See also “[Set up Eclipse for Survey Tool](https://docs.google.com/document/d/1wkJsoQXPcGN_dlCzXzwhfjQoq9Mes7VezIRmNrHWV8c/edit)” 2. To run the SurveyTool components you will need the IDE for Enterprise Developers, you can download this from https://www.eclipse.org/downloads/packages/ -3. Make sure the config files are set up first ([**3.2** Configuring Maven](https://cldr.unicode.org/development/maven)), and that CLDR is checked out locally from git in some directory. +3. Make sure the config files are set up first ([**3.2** Configuring Maven](/development/maven)), and that CLDR is checked out locally from git in some directory. 4. Go to File \-\> Import, choose Maven and import Existing Maven Projects (see image at right) ![image](../images/development/maven1.png) diff --git a/docs/site/development/new-cldr-developers.md b/docs/site/development/new-cldr-developers.md index 17054442652..cc7c2b38e7c 100644 --- a/docs/site/development/new-cldr-developers.md +++ b/docs/site/development/new-cldr-developers.md @@ -42,7 +42,7 @@ Command line: Via eclipse: -1. Go [here](https://cldr.unicode.org/development/eclipse-setup%23TOC-Test) +1. Go [here](/development/eclipse-setup%23TOC-Test) Once you are all set up, be sure to read the development process, for how to handle tickets, when you can't make changes, etc. @@ -56,7 +56,7 @@ The table below points to documentation for various tasks. | performance work | http://cldr.unicode.org/development/perf-testing | | survey tool database work | http://cldr.unicode.org/development/running-survey-tool/cldr-properties/db | -Other useful pages are under [CLDR Development Site](https://cldr.unicode.org/development/cldr-development-site); you can also use the search box. +Other useful pages are under [CLDR Development Site](/development/cldr-development-site); you can also use the search box. [UTS #35: Unicode Locale Data Markup Language (LDML)](https://www.unicode.org/reports/tr35/) is the specification of the XML format used for CLDR data, including the interpretation of the CLDR data. diff --git a/docs/site/development/running-tests.md b/docs/site/development/running-tests.md index ee445cd631c..4a1ccefbb16 100644 --- a/docs/site/development/running-tests.md +++ b/docs/site/development/running-tests.md @@ -7,7 +7,7 @@ title: Running Tests You will always need to run tests when you do a check\-in. 1. Preconditions - - If you change the DTD, be sure to read and follow [Updating DTDs](https://cldr.unicode.org/development/updating-dtds) first. + - If you change the DTD, be sure to read and follow [Updating DTDs](/development/updating-dtds) first. - If you added a new feature or fixed a significant bug, add a unit test for it. - See unittest/NumberingSystemsTest as an example. - Remember to add to unittest/TestAll @@ -19,8 +19,8 @@ You will always need to run tests when you do a check\-in. - If you know what you are doing, you can run a set of filtered tests. 4. Other tests 1. The unit tests are not complete, so you get a better workout if you are doing anything fancy by running: - 2. [**NewLdml2IcuConverter**](https://cldr.unicode.org/development/coding-cldr-tools/newldml2icuconverter) - 3. [**Generating Charts**](https://cldr.unicode.org/development/cldr-big-red-switch/generating-charts) + 2. [**NewLdml2IcuConverter**](/development/coding-cldr-tools/newldml2icuconverter) + 3. [**Generating Charts**](/development/cldr-big-red-switch/generating-charts) 1. If you have interesting new data, write a chart for it. See subclasses of Chart.java for examples. ## Running tests on the command line diff --git a/docs/site/development/updating-codes.md b/docs/site/development/updating-codes.md index 980f54f0b01..b204127b7e5 100644 --- a/docs/site/development/updating-codes.md +++ b/docs/site/development/updating-codes.md @@ -8,26 +8,26 @@ title: Updating Codes ### Steps -First read [Running Tools](https://cldr.unicode.org/development/running-tools) - -1. Update [Script Metadata](https://cldr.unicode.org/development/updating-codes/updating-script-metadata) -2. [Update Population/GDP/Literacy](https://cldr.unicode.org/development/updating-codes/updating-population-gdp-literacy) -3. [Update Language/Script/Region Subtags](https://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags) -4. [Update Subdivision Codes](https://cldr.unicode.org/development/updating-codes/updating-subdivision-codes) -5. [Update Subdivision translations](https://cldr.unicode.org/development/updating-codes/updating-subdivision-translations) (new) -6. [Update Currency Codes](https://cldr.unicode.org/development/updating-codes/update-currency-codes) -7. [Update Time Zone Data for ZoneParser](https://cldr.unicode.org/development/updating-codes/update-time-zone-data-for-zoneparser) -8. [Update Validity XML](https://cldr.unicode.org/development/updating-codes/update-validity-xml) - 1. [Update Language/Script/Country Information](https://cldr.unicode.org/development/updating-codes/update-language-script-info) - 2. [LikelySubtags and Default Content](https://cldr.unicode.org/development/updating-codes/likelysubtags-and-default-content) +First read [Running Tools](/development/running-tools) + +1. Update [Script Metadata](/development/updating-codes/updating-script-metadata) +2. [Update Population/GDP/Literacy](/development/updating-codes/updating-population-gdp-literacy) +3. [Update Language/Script/Region Subtags](/development/updating-codes/update-languagescriptregion-subtags) +4. [Update Subdivision Codes](/development/updating-codes/updating-subdivision-codes) +5. [Update Subdivision translations](/development/updating-codes/updating-subdivision-translations) (new) +6. [Update Currency Codes](/development/updating-codes/update-currency-codes) +7. [Update Time Zone Data for ZoneParser](/development/updating-codes/update-time-zone-data-for-zoneparser) +8. [Update Validity XML](/development/updating-codes/update-validity-xml) + 1. [Update Language/Script/Country Information](/development/updating-codes/update-language-script-info) + 2. [LikelySubtags and Default Content](/development/updating-codes/likelysubtags-and-default-content) 3. Update IANA/FIPS Mappings 1. TBD - Describe what to do. The URLs are 2. http://www.iana.org/domain-names.htm 3. http://www.iana.org/root-whois/index.html 4. http://data.iana.org/TLD/tlds-alpha-by-domain.txt 9. Reformat plurals/ordinals.xml with GeneratedPluralRules.java. Review carefully before checking in. - 1. Regenerate Supplemental Charts: [Generating Charts](https://cldr.unicode.org/development/cldr-big-red-switch/generating-charts) + 1. Regenerate Supplemental Charts: [Generating Charts](/development/cldr-big-red-switch/generating-charts) -For information about **Version Info** and external metadata, see [Updating External Metadata](https://cldr.unicode.org/development/updating-codes/external-version-metadata) +For information about **Version Info** and external metadata, see [Updating External Metadata](/development/updating-codes/external-version-metadata) diff --git a/docs/site/development/updating-codes/likelysubtags-and-default-content.md b/docs/site/development/updating-codes/likelysubtags-and-default-content.md index 93179fdc23d..08a8cfdced9 100644 --- a/docs/site/development/updating-codes/likelysubtags-and-default-content.md +++ b/docs/site/development/updating-codes/likelysubtags-and-default-content.md @@ -4,7 +4,7 @@ title: LikelySubtags and Default Content # LikelySubtags and Default Content -1. First make sure that you do [Update Language/Script/Region Subtags](https://cldr.unicode.org/development/updating-codes/update-languagescriptregion-subtags) first +1. First make sure that you do [Update Language/Script/Region Subtags](/development/updating-codes/update-languagescriptregion-subtags) first 2. Run GenerateMaximalLocales with VM argument ```-DCLDR_DIR``` set to your cldr directory to generate the likely subtag data **AND** the default content locales. 1. If you are trying to debug, add the VM argument ```-DGenerateMaximalLocalesDebug``` 3. Input data: diff --git a/docs/site/development/updating-codes/update-currency-codes.md b/docs/site/development/updating-codes/update-currency-codes.md index 880a433e895..dae7372df88 100644 --- a/docs/site/development/updating-codes/update-currency-codes.md +++ b/docs/site/development/updating-codes/update-currency-codes.md @@ -19,7 +19,7 @@ title: Update Currency Codes - *Review all amendments that are dated after the previous update , and patch the XML files and the* ```supplementalData.xml``` *as below.* - *Record the last number viewed in the URL above.* - *(There is a "download all amendments" link now that has a spreadsheet summary.)* - - **Record the version: See** [**Updating External Metadata**](https://cldr.unicode.org/development/updating-codes/external-version-metadata) + - **Record the version: See** [**Updating External Metadata**](/development/updating-codes/external-version-metadata) - If there are no diffs in the two iso tables, and no relevant changes in the amendments, you are done. - Run ```CountItems -Dmethod=generateCurrencyItems``` to generate the new currency list. - If any currency is missing from ISO4217\.txt, the program will throw an exception and will print a list of items at the end that need to be added to the ISO4217\.txt file. Add as described below. diff --git a/docs/site/development/updating-codes/update-language-script-info.md b/docs/site/development/updating-codes/update-language-script-info.md index 0035354305f..5abed58db78 100644 --- a/docs/site/development/updating-codes/update-language-script-info.md +++ b/docs/site/development/updating-codes/update-language-script-info.md @@ -9,9 +9,9 @@ title: Update Language Script Info 1. https://github.com/unicode-org/cldr/tree/main/tools/cldr-code/src/main/resources/org/unicode/cldr/util/data has files with this form: 1. **country\_language\_population.tsv** 2. **language\_script.tsv** - 3. For a descriptions of the contents, see [Language Script Guidelines](https://cldr.unicode.org/development/updating-codes/update-language-script-info/language-script-description) + 3. For a descriptions of the contents, see [Language Script Guidelines](/development/updating-codes/update-language-script-info/language-script-description) 1. Do not edit the above files with a plain text editor; they are tab\-delimited UTF\-8 with many fields and should be imported/edited with a spreadsheet editor. Excel or Google sheets should also work fine. -2. The world bank, un, and factbook data should be updated as per [Updating Population, GDP, Literacy](https://cldr.unicode.org/development/updating-codes/updating-population-gdp-literacy) +2. The world bank, un, and factbook data should be updated as per [Updating Population, GDP, Literacy](/development/updating-codes/updating-population-gdp-literacy) 3. Note that there is an auxiliary file **util/data/external/other\_country\_data.txt**, which contains data that supplements the others. If there are errors below because the country population is less than the language population, then that file may need updating. 1. Run the tool **ConvertLanguageData**. 1. \-DADD\_POP\=**true**; for error messages. @@ -32,9 +32,9 @@ title: Update Language Script Info ### Update the supplementalData.xml \ -1. For UN M.49 codes, see [Updating UN Codes](https://cldr.unicode.org/development/updating-codes/updating-un-codes) +1. For UN M.49 codes, see [Updating UN Codes](/development/updating-codes/updating-un-codes) 2. For the UN, go to https://www.un.org/en/member-states/index.html. Copy the table, and paste into util/data/external/un\_member\_states\_raw.txt. Diff with old. **BROKEN LINK** -3. For the EU, see instructions on [Updating UN Codes](https://cldr.unicode.org/development/updating-codes/updating-un-codes) +3. For the EU, see instructions on [Updating UN Codes](/development/updating-codes/updating-un-codes) 4. For the EZ, do the same with , into util/data/external/ez\_member\_states\_raw.txt  **BROKEN LINK** 1. If there are changes, update \ diff --git a/docs/site/development/updating-codes/update-languagescriptregion-subtags.md b/docs/site/development/updating-codes/update-languagescriptregion-subtags.md index bbb662f8440..0777f873461 100644 --- a/docs/site/development/updating-codes/update-languagescriptregion-subtags.md +++ b/docs/site/development/updating-codes/update-languagescriptregion-subtags.md @@ -35,9 +35,9 @@ title: Update Language/Script/Region Subtags - Compare total counts with tool output:  example "*formerly\_used \|\|  22*"  coinciding with 22 Formerly Used codes - If something is wrong, you'll have to scroll through the code list and/or dig around for the updates - Check if ISO has done something destabilizing with codes: you need to handle it specially. -- **Record the version: See [Updating External Metadata](https://cldr.unicode.org/development/updating-codes/external-version-metadata)** -- Do validity checks and regenerate: for details see [Validity](https://cldr.unicode.org/development/updating-codes/update-validity-xml) - - You'll have to do this again in [Updating Subdivision Codes](https://cldr.unicode.org/development/updating-codes/updating-subdivision-codes). +- **Record the version: See [Updating External Metadata](/development/updating-codes/external-version-metadata)** +- Do validity checks and regenerate: for details see [Validity](/development/updating-codes/update-validity-xml) + - You'll have to do this again in [Updating Subdivision Codes](/development/updating-codes/updating-subdivision-codes). - Edit common/main/en.xml to add any new names, based on the Descriptions in the registry file. - *You only need to add new languages and scripts that we add to supplementalMetaData.* - But you need all territories. diff --git a/docs/site/development/updating-codes/update-time-zone-data-for-zoneparser.md b/docs/site/development/updating-codes/update-time-zone-data-for-zoneparser.md index eeec6c293c6..12f11432d6b 100644 --- a/docs/site/development/updating-codes/update-time-zone-data-for-zoneparser.md +++ b/docs/site/development/updating-codes/update-time-zone-data-for-zoneparser.md @@ -30,5 +30,5 @@ Note: This is usually done as a part of full time zone data update process. - **Note**: leapseconds might be removed from the list later. 4. Edit the file {CLDR\_DIR}}/tools/cldr\-code/src/main/resources/org/unicode/cldr/util/data/tzdb\-version.txt - This file contains just one line text specifying a version of Time Zone Database, e.g. 2021a. -5. **Record the version: See** [**Updating External Metadata**](https://cldr.unicode.org/development/updating-codes/external-version-metadata) +5. **Record the version: See** [**Updating External Metadata**](/development/updating-codes/external-version-metadata) diff --git a/docs/site/development/updating-codes/update-validity-xml.md b/docs/site/development/updating-codes/update-validity-xml.md index 7adb92e968c..0e66178c585 100644 --- a/docs/site/development/updating-codes/update-validity-xml.md +++ b/docs/site/development/updating-codes/update-validity-xml.md @@ -4,7 +4,7 @@ title: Update Validity XML # Update Validity XML -1. Create the archive ([Creating the Archive](https://cldr.unicode.org/development/creating-the-archive)) with at least the last release (if you don't have it already) +1. Create the archive ([Creating the Archive](/development/creating-the-archive)) with at least the last release (if you don't have it already) 2. Run GenerateValidityXML.java 3. This updates files in cldr/common/validity/. (If you set \-DSHOW\_FILES, you'll see this on the console.) 1. New files should not be generated. If there are any, something has gone wrong, so raise this as an issue on cldr\-dev. **Note:** cldr/common/validity/currency.xml contains a comment line \- *\ which will update the casing files in common/casing. When you check this in, sanity check the values, because in some cases we have have had different rules than just what the heuristics generate. - 3. TEST out the **SurveyTool** to verify that you can see/edit the new items. If users should be able to input data and are not able to, the item has not been properly added to CLDR. See [Running the Survey Tool in Eclipse](https://cldr.unicode.org/development/running-survey-tool). + 3. TEST out the **SurveyTool** to verify that you can see/edit the new items. If users should be able to input data and are not able to, the item has not been properly added to CLDR. See [Running the Survey Tool in Eclipse](/development/running-survey-tool). 4. **Data.** 1. Add necessary data to root and English. 2. (Optional) add additional data for locales (if part of main). If the data is just seed data (that you aren't sure of), make sure that you have draft="unconfirmed" on the leaf nodes. @@ -253,7 +253,7 @@ If a value has placeholders, edit Placeholders.txt: - ^//ldml/units/unit\\\[@type="day%A"\]/unitPattern ; {0}=NUMBER\_OF\_DAYS 3 2. There is a variable %A that will match attribute value syntax (or substrings). 3. \ may contain spaces, but \ must not. -4. For an example, see [8484](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) +4. For an example, see [8484](/index/bug-reports#TOC-Filing-a-Ticket) 5. Check that the ConsoleCheckCLDR **CheckForExamplars** fails if there are no placeholders in the value 6. Note: we should switch methods so that we don't need to quote \\\[, etc, but we haven't yet. @@ -322,7 +322,7 @@ There are three ways for paths to show up in the Survey Tool (and in other tooli ### OK if Missing -Certain paths don't have to be present in locales. They are not counted as Missing in the Dashboard and shouldn't have an effect on coverage. To handle these, modify the file [missingOk.txt](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) to provide a regex that captures those paths. Be careful, however, to not be overly inclusive: you want all and only those paths that are ok to skip. Typically those are paths for which root values are perfectly fine. +Certain paths don't have to be present in locales. They are not counted as Missing in the Dashboard and shouldn't have an effect on coverage. To handle these, modify the file [missingOk.txt](/index/bug-reports#TOC-Filing-a-Ticket) to provide a regex that captures those paths. Be careful, however, to not be overly inclusive: you want all and only those paths that are ok to skip. Typically those are paths for which root values are perfectly fine. ## Examples of DTD modifications @@ -332,14 +332,14 @@ The following is an example of the different files that may need to be modified. ## Modifying English/Root -Whenever you modify values in English or Root, be sure to run GenerateBirth as described on [Updating English/Root](https://cldr.unicode.org/development/cldr-development-site/updating-englishroot) and check in the results. That ensures that CheckNew works properly. This must be done before the Survey Tool starts or is in the Submission Phase. +Whenever you modify values in English or Root, be sure to run GenerateBirth as described on [Updating English/Root](/development/cldr-development-site/updating-englishroot) and check in the results. That ensures that CheckNew works properly. This must be done before the Survey Tool starts or is in the Submission Phase. ## Validation -- **Do the steps on** [**Running Tests**](https://cldr.unicode.org/development/running-tests) +- **Do the steps on** [**Running Tests**](/development/running-tests) ## Debugging Regexes -- Moved to [**Running Tests**](https://cldr.unicode.org/development/running-tests) +- Moved to [**Running Tests**](/development/running-tests) diff --git a/docs/site/downloads/cldr-31.md b/docs/site/downloads/cldr-31.md index 8c5fd992bf4..7745a4b03ed 100644 --- a/docs/site/downloads/cldr-31.md +++ b/docs/site/downloads/cldr-31.md @@ -3,7 +3,7 @@ title: 'CLDR 31 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 31 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 31 Release Note

For details, see Spec Modifications.

Migration

  • Code changes

    • The subdivision codes have been changed to all be the bcp47 format, eg "usca" instead of "US-CA". This affects supplemental containment and subdivisions, and translations in subdivisions/en.xml, etc. See Part 6, Sec 2.2 [#9942]

    • The locales in the language-territory population tables have been changed to be the canonical format, dropping the script where it is the default. So "ku_Latn" changes to "ku"

    • The exemplar/ locale data file names have also been changed to be the canonical format, dropping the script where it is the default.

  • Plural rules

    • The Portuguese plural rules have changed so that all (and only) integers and decimal fractions < 2 are singular.

  • Timezones

    • The GMT timezone has been split from the UTC timezone.

    • New timezone bcp47 codes have been added.

  • Language/Region data

    • The new literacyPercent attribute for supplemental <languagePopulation> has been broken out from writingPercent, the latter now only being used to reflect primarily-spoken languages. [#9421]

    • A new format for language matching is provided. To allow time for implementations to change over, the old data is retained, and the new data is marked as "written-new".

    • Languages "hr" and "sr" are no longer a short distance apart, for political reasons.

  • Other

    • The primary names for CZ changed from "Czech Republic" to "Czechia", with the longer name now the alternate.

Known Issues

“Week of” structure

The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

<dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

<dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

Non-unique emoji short names (fixed in 31.0.1)

Some of the emoji names are not unique. Fixes are being gathered, but are not in time for the release. See [#10116], [#10127]

Chinese stroke collation

Since CLDR 30, Chinese stroke collation has been missing entries for several basic characters. CLDR 32 reverts the stroke collation data to the CLDR 29 version; a complete fix for the underlying problem is targeted for CLDR 33. See #10497, #10642.

Others

See tickets for v31.0.1.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key

    • The Release Note contains a general description of the contents of the release, and any relevant notes about the release.

    • The Data link points to a set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see Repository Organization).

    • The Spec is the version of UTS #35: LDML that corresponds to the release.

    • The Delta document points to a list of all the bug fixes and features in the release, which be used to get the precise corresponding file changes using BugDiffs.

    • The SVN Tag can be used to get the files via Repository Access.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

For details, see Spec Modifications.

Migration

  • Code changes

    • The subdivision codes have been changed to all be the bcp47 format, eg "usca" instead of "US-CA". This affects supplemental containment and subdivisions, and translations in subdivisions/en.xml, etc. See Part 6, Sec 2.2 [#9942]

    • The locales in the language-territory population tables have been changed to be the canonical format, dropping the script where it is the default. So "ku_Latn" changes to "ku"

    • The exemplar/ locale data file names have also been changed to be the canonical format, dropping the script where it is the default.

  • Plural rules

    • The Portuguese plural rules have changed so that all (and only) integers and decimal fractions < 2 are singular.

  • Timezones

    • The GMT timezone has been split from the UTC timezone.

    • New timezone bcp47 codes have been added.

  • Language/Region data

    • The new literacyPercent attribute for supplemental <languagePopulation> has been broken out from writingPercent, the latter now only being used to reflect primarily-spoken languages. [#9421]

    • A new format for language matching is provided. To allow time for implementations to change over, the old data is retained, and the new data is marked as "written-new".

    • Languages "hr" and "sr" are no longer a short distance apart, for political reasons.

  • Other

    • The primary names for CZ changed from "Czech Republic" to "Czechia", with the longer name now the alternate.

Known Issues

“Week of” structure

The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

<dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

<dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

Non-unique emoji short names (fixed in 31.0.1)

Some of the emoji names are not unique. Fixes are being gathered, but are not in time for the release. See [#10116], [#10127]

Chinese stroke collation

Since CLDR 30, Chinese stroke collation has been missing entries for several basic characters. CLDR 32 reverts the stroke collation data to the CLDR 29 version; a complete fix for the underlying problem is targeted for CLDR 33. See #10497, #10642.

Others

See tickets for v31.0.1.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key

    • The Release Note contains a general description of the contents of the release, and any relevant notes about the release.

    • The Data link points to a set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see Repository Organization).

    • The Spec is the version of UTS #35: LDML that corresponds to the release.

    • The Delta document points to a list of all the bug fixes and features in the release, which be used to get the precise corresponding file changes using BugDiffs.

    • The SVN Tag can be used to get the files via Repository Access.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-32.md b/docs/site/downloads/cldr-32.md index e6217f25f67..02807a51549 100644 --- a/docs/site/downloads/cldr-32.md +++ b/docs/site/downloads/cldr-32.md @@ -3,7 +3,7 @@ title: 'CLDR 32 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 32 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 32 Release Note

* The measurement of the number of items is reflects the different ways that the information is represented. A single data field (element or attribute value) may result in multiple data items. For example, plural rules may be shared by multiple languages, and a single data field contains all the languages to which those rules apply. Sometimes a changed item appears as a deletion+addition, and sequences of items (such as sort order) are not counted as different even if the order changes.

The following chart shows the increase in locale-based data over time.

For more details, see the Delta Data charts.

There is a new chart that shows the current coverage levels for CLDR locales. The locales that are not as complete are marked 'seed', and available in a separate CLDR source directory.

Migration

  • Plural rules

      • The plural rules for pt_PT changed to be different than pt (=pt_BR). The "one" case is now only the integer 1.

  • Timezones

    • Persian (fa) localized GMT hour pattern contains bidi control character LRM before signs.

  • Currencies

    • The new code for STN (SAO TOME AND PRINCIPE) has been released, and will be valid as of 2018-09-01. It is included in the release with that effective date. However, it was too late to provide names for the locales.

  • Language/Region data

    • The UN code 202 (Sub-Saharan Africa) was added late in the process, and doesn't have names (except in English).

  • Other

    • Chakma is the first CLDR locale that uses completely supplemental (non-BMP) characters, which may expose some bugs in implementations.

    • Chinese stroke collation was reverted to the data from CLDR 29 as a short-term fix for problems introduced in CLDR 30 that resulted in missing entries for several basic characters. A complete fix for the underlying problem is targeted for CLDR 33. See #10497, #10642.

Known Issues

    1. New macroregions

      1. The UN code 202 (Sub-Saharan Africa) was added late in the process, and doesn't have names (except in English).

      2. The UN is now including Sark (680) which didn't get into the release.

  1. “Week of” structure

    1. The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

    2. <dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

    3. <dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

    4. Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

  2. Subdivision Names

    1. The draft subdivision names were imported from wikidata. Names that had characters outside of the language's exemplars were excluded for now. Names that would cause collisions were allowed, but marked with superscripted numbers. The goal is to clean up these names over time.

  1. German AM/PM [reverted in CLDR 32.0.1]

    1. In CLDR 32, the German AM/PM symbols were changed from “vorm.”/“nachm.” to “AM”/“PM”. This was reverted in CLDR 32.0.1 [#10735] but will be reconsidered in a future version of CLDR [#10789].

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

* The measurement of the number of items is reflects the different ways that the information is represented. A single data field (element or attribute value) may result in multiple data items. For example, plural rules may be shared by multiple languages, and a single data field contains all the languages to which those rules apply. Sometimes a changed item appears as a deletion+addition, and sequences of items (such as sort order) are not counted as different even if the order changes.

The following chart shows the increase in locale-based data over time.

For more details, see the Delta Data charts.

There is a new chart that shows the current coverage levels for CLDR locales. The locales that are not as complete are marked 'seed', and available in a separate CLDR source directory.

Migration

  • Plural rules

      • The plural rules for pt_PT changed to be different than pt (=pt_BR). The "one" case is now only the integer 1.

  • Timezones

    • Persian (fa) localized GMT hour pattern contains bidi control character LRM before signs.

  • Currencies

    • The new code for STN (SAO TOME AND PRINCIPE) has been released, and will be valid as of 2018-09-01. It is included in the release with that effective date. However, it was too late to provide names for the locales.

  • Language/Region data

    • The UN code 202 (Sub-Saharan Africa) was added late in the process, and doesn't have names (except in English).

  • Other

    • Chakma is the first CLDR locale that uses completely supplemental (non-BMP) characters, which may expose some bugs in implementations.

    • Chinese stroke collation was reverted to the data from CLDR 29 as a short-term fix for problems introduced in CLDR 30 that resulted in missing entries for several basic characters. A complete fix for the underlying problem is targeted for CLDR 33. See #10497, #10642.

Known Issues

    1. New macroregions

      1. The UN code 202 (Sub-Saharan Africa) was added late in the process, and doesn't have names (except in English).

      2. The UN is now including Sark (680) which didn't get into the release.

  1. “Week of” structure

    1. The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

    2. <dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

    3. <dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

    4. Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

  2. Subdivision Names

    1. The draft subdivision names were imported from wikidata. Names that had characters outside of the language's exemplars were excluded for now. Names that would cause collisions were allowed, but marked with superscripted numbers. The goal is to clean up these names over time.

  1. German AM/PM [reverted in CLDR 32.0.1]

    1. In CLDR 32, the German AM/PM symbols were changed from “vorm.”/“nachm.” to “AM”/“PM”. This was reverted in CLDR 32.0.1 [#10735] but will be reconsidered in a future version of CLDR [#10789].

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 33.1

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 33.1

Overview

Unicode CLDR 33.1 is an update to CLDR 33 that focuses on Unicode 11.0 support. Improvements in this release include:

  • Data

      • Updates to Unicode 11.0

      • Adds annotations (names and keywords) for Unicode 11.0 emoji, and makes improvements to previously-existing annotations.

      • Updates Chinese collation stroke order from Unicode 7.0 to Unicode 11.0, after tooling bug fixes

  • Structure*

      • No changes. The DTD Δs and DTD Diffs links above point to v33.

  • Specification*

      • There is no LDML 33.1 document. Instead, only amendments to v33 are provided, as described below in Specification Amendments.

  • Charts*

For more details, see the list of bug fixes.

Specification Amendments

There is not a new version of the LDML spec. Instead, the following are amendments to LDML33. The changed text is indicated below by green highlighting

14.1 Synthesizing Sequence Names

…

  1. If sequence is an emoji flag sequence, look up the territory name in CLDR for the corresponding ASCII characters. Set suffixName to that, and prefixName to the characterLabel for "flag", and go to step 10.

    • For example, "🇵🇫" has the regional indicator symbols PF and would map to “Flagge: Französisch-Polynesien” in German.

  2. If sequence is an emoji tag sequence, look up the subdivision name in CLDR for the corresponding ASCII characters and compose as for emoji flag sequence.

    • For example, "🏴󠁧󠁢󠁳󠁣󠁴󠁿" has TAG characters gbsct and would map to “Flagge: Schottland” in German.

  3. If sequence is a keycap sequence or 🔟, use the characterLabel for "keycap" as the prefixName and set the suffix to be the ASCII characters in the sequence (or "10" in the case of 🔟), then go to step 8.

    • For example, "#⃣" would map to "Taste: #" in German.

  4. …

  5. If sequence contains any emoji modifiers or hair components, move them (in order) into suffix, removing them from sequence.

    • For example, "👨🏿‍🦰" would map to "Mann: dunkle Hautfarbe, rotes Haar".

  6. …

  7. …

  8. Transform sequence and append to prefixName, by successively getting names for the longest subsequences, skipping any singleton ZWJ characters. If there is more than one name, use the listPatterns for "unit-short" to link them. This uses the patterns for "2", "start", "middle", and "end".

  9. …

  10. …

The /annotationsDerived/ folder has the available composed names, pre-built.

…

Migration

  • Updates German AM/PM strings to follow the English, to meet most common expectations of users of 12hr formats.

Known Issues

  1. Some of the main CLDR locales are missing a few Unicode 11.0 annotations (should be fixed in v34): #11193

    1. The segmentation rules have not been updated for changes in Unicode 11.0. This does not affect ICU, since the rules there were changed manually. Implementers may wish to patch their v33.1 versions with the data in #11203 if they use the segmentation rules independent of ICU. The changes include simplifying the break rules for Emoji and not breaking within strings of white space.

    2. The ICU4J libraries included in v33.1 were not updated to ICU 62.0. There are no known problems with using ICU 61.0, but implementers may want to update their copies to ICU 62.0.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing. The contributors to v33.1 will appear on the page later, when v34 is released.

Key to Header Links

Overview

Unicode CLDR 33.1 is an update to CLDR 33 that focuses on Unicode 11.0 support. Improvements in this release include:

  • Data

      • Updates to Unicode 11.0

      • Adds annotations (names and keywords) for Unicode 11.0 emoji, and makes improvements to previously-existing annotations.

      • Updates Chinese collation stroke order from Unicode 7.0 to Unicode 11.0, after tooling bug fixes

  • Structure*

      • No changes. The DTD Δs and DTD Diffs links above point to v33.

  • Specification*

      • There is no LDML 33.1 document. Instead, only amendments to v33 are provided, as described below in Specification Amendments.

  • Charts*

For more details, see the list of bug fixes.

Specification Amendments

There is not a new version of the LDML spec. Instead, the following are amendments to LDML33. The changed text is indicated below by green highlighting

14.1 Synthesizing Sequence Names

…

  1. If sequence is an emoji flag sequence, look up the territory name in CLDR for the corresponding ASCII characters. Set suffixName to that, and prefixName to the characterLabel for "flag", and go to step 10.

    • For example, "🇵🇫" has the regional indicator symbols PF and would map to “Flagge: Französisch-Polynesien” in German.

  2. If sequence is an emoji tag sequence, look up the subdivision name in CLDR for the corresponding ASCII characters and compose as for emoji flag sequence.

    • For example, "🏴󠁧󠁢󠁳󠁣󠁴󠁿" has TAG characters gbsct and would map to “Flagge: Schottland” in German.

  3. If sequence is a keycap sequence or 🔟, use the characterLabel for "keycap" as the prefixName and set the suffix to be the ASCII characters in the sequence (or "10" in the case of 🔟), then go to step 8.

    • For example, "#⃣" would map to "Taste: #" in German.

  4. …

  5. If sequence contains any emoji modifiers or hair components, move them (in order) into suffix, removing them from sequence.

    • For example, "👨🏿‍🦰" would map to "Mann: dunkle Hautfarbe, rotes Haar".

  6. …

  7. …

  8. Transform sequence and append to prefixName, by successively getting names for the longest subsequences, skipping any singleton ZWJ characters. If there is more than one name, use the listPatterns for "unit-short" to link them. This uses the patterns for "2", "start", "middle", and "end".

  9. …

  10. …

The /annotationsDerived/ folder has the available composed names, pre-built.

…

Migration

  • Updates German AM/PM strings to follow the English, to meet most common expectations of users of 12hr formats.

Known Issues

  1. Some of the main CLDR locales are missing a few Unicode 11.0 annotations (should be fixed in v34): #11193

    1. The segmentation rules have not been updated for changes in Unicode 11.0. This does not affect ICU, since the rules there were changed manually. Implementers may wish to patch their v33.1 versions with the data in #11203 if they use the segmentation rules independent of ICU. The changes include simplifying the break rules for Emoji and not breaking within strings of white space.

    2. The ICU4J libraries included in v33.1 were not updated to ICU 62.0. There are no known problems with using ICU 61.0, but implementers may want to update their copies to ICU 62.0.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing. The contributors to v33.1 will appear on the page later, when v34 is released.

Key to Header Links

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 33 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 33 Release Note

The following files showed the largest number of raw changes:

  • annotations/as.xml, main/as.xml, annotations/ru.xml, main/br.xml, annotations/or.xml, annotations/br.xml, annotations/ga.xml

Two changes affected the statistics:

  • The keywords (in annotations) are being treated as sets for counting purposes.

    • So old:{a | b | c} → new:{a | c | d | e} counts as one deletion and 2 additions.

  • The keywords have also had some redundancies removed: if a keyword consisted entirely of other keywords, it was removed.

    • So old:{a, a b, b} → new:{a, b}.

Migration

  • Plurals: ordinal and cardinal rules have been added for scn. The cardinal (plural) rules for Macedonian (mk) have been changed so that one➞other for {11}. Should not cause migration issues.

    • The emoji property data file ExtendedPictographic.txt has been removed from CLDR data, since the contents are now part of the UTS #51 “Unicode Emoji” data file: emoji-data.txt.

    • Adjusted the territory containment data for some regions near the South Pole, following changes in UN M49, so several of these now have new containing regions.

Known Issues

    1. New macroregions

    • UN M.49 now includes Sark (680) but ISO rejected the proposed ISO 3166-1 code, so it is not included.

    1. “Week of” structure

      • The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

      • <dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

      • <dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

      • Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

  1. Subdivision Names

    • The draft subdivision names were imported from wikidata. Names that had characters outside of the language's exemplars were excluded for now. Names that would cause collisions were allowed, but marked with superscripted numbers. The goal is to clean up these names over time.

    1. Chinese stroke collation

      • In CLDR 30 and 31, Chinese stroke collation was missing entries for several basic characters. CLDR 32 reverted the stroke collation data to the CLDR 29 version; a complete fix for the underlying problem is targeted for CLDR 34. See #10497, #10642.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

The following files showed the largest number of raw changes:

  • annotations/as.xml, main/as.xml, annotations/ru.xml, main/br.xml, annotations/or.xml, annotations/br.xml, annotations/ga.xml

Two changes affected the statistics:

  • The keywords (in annotations) are being treated as sets for counting purposes.

    • So old:{a | b | c} → new:{a | c | d | e} counts as one deletion and 2 additions.

  • The keywords have also had some redundancies removed: if a keyword consisted entirely of other keywords, it was removed.

    • So old:{a, a b, b} → new:{a, b}.

Migration

  • Plurals: ordinal and cardinal rules have been added for scn. The cardinal (plural) rules for Macedonian (mk) have been changed so that one➞other for {11}. Should not cause migration issues.

    • The emoji property data file ExtendedPictographic.txt has been removed from CLDR data, since the contents are now part of the UTS #51 “Unicode Emoji” data file: emoji-data.txt.

    • Adjusted the territory containment data for some regions near the South Pole, following changes in UN M49, so several of these now have new containing regions.

Known Issues

    1. New macroregions

    • UN M.49 now includes Sark (680) but ISO rejected the proposed ISO 3166-1 code, so it is not included.

    1. “Week of” structure

      • The structure and intended usage for the “week x of y” patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:

      • <dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>

      • <dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>

      • Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].

  1. Subdivision Names

    • The draft subdivision names were imported from wikidata. Names that had characters outside of the language's exemplars were excluded for now. Names that would cause collisions were allowed, but marked with superscripted numbers. The goal is to clean up these names over time.

    1. Chinese stroke collation

      • In CLDR 30 and 31, Chinese stroke collation was missing entries for several basic characters. CLDR 32 reverted the stroke collation data to the CLDR 29 version; a complete fix for the underlying problem is targeted for CLDR 34. See #10497, #10642.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 34 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 34 Release Note

Overview

Unicode CLDR 34 provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.

CLDR 34 included a full Survey Tool data collection phase, adding approximately 6M of data overall, resulting in the following language support:

Overview

Unicode CLDR 34 provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.

CLDR 34 included a full Survey Tool data collection phase, adding approximately 6M of data overall, resulting in the following language support:

TBD: add chart

Migration

Known Issues

(These may addressed in a maintenance update)

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

TBD: add chart

Migration

Known Issues

(These may addressed in a maintenance update)

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-35.md b/docs/site/downloads/cldr-35.md index ebf8886d2bd..510744e1bd1 100644 --- a/docs/site/downloads/cldr-35.md +++ b/docs/site/downloads/cldr-35.md @@ -3,7 +3,7 @@ title: 'CLDR 35 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 35 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 35 Release Note

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 36 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 36 Release Note

Overview

Unicode CLDR 36 provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.

A main focus this release was on infrastructure. We moved to GitHub for source code control and Jira for bug tracking, and made significant improvements in performance of the online data-gathering Survey Tool. We are also now keeping more information in the master data, reflecting the votes in the Survey Tool for the “inherited” items (see Migration).

  • Approximately 32K items added

      • Significant increase (approx 50% or more) in moderate and/or modern coverage for: ceb (Cebuano), ha (Hausa / Latin script), ig (Igbo), kok (Konkani), qu (Quechua), to (Tongan), yo (Yoruba). Additionally, the following locales had at least a 15% increase in basic coverage: az (Azerbaijani / Latin script), so (Somali / Latin script).

    • Seed data for new locales, including three native languages of N. America: cic (Chickasaw), mus (Muscogee), osa (Osage, Osage script); an (Aragonese), su (Sundanese, Latin script), szl (Silesian).

      • Additional data for new items listed below.

  • Emoji

      • Added names and keywords for Emoji 13.0 draft candidates; these are to be fleshed out further in v36.1.

      • Refined names and keywords for Emoji 12.0, including for English.

    • Measurement units:

      • Additional compoundUnitPattern ({0}⋅{1} in root) for expressing units like newton-meter (N⋅m)

      • Additional units: dot-per-centimeter, dot-per-inch, em, megapixel, pixel, pixel-per-centimeter, pixel-per-inch; decade; therm-us; bar, pascal

  • Locale identifiers and names

    • Extended Language Matching to have fallbacks for many encompassed languages. [CLDR-13244]

    • Added more languageAliases from the BCP47 language subtag registry, for deprecated languages.

    • New alt=“menu” names for certain languages, intended to provide better sorting in menus. [CLDR-11834]

      • Updated validity and collection information for geographic subregions; updated names especially for subregions of UK and Sweden.

      • Names have been added for “pseudo-regions” XA (Pseudo-Accents) and XB (Pseudo-Bidi). These are only intended for testing purposes, you may need to add special handling to remove them for production purposes. [CLDR-13100]

    • Other

    • Additions for testing:

    • Added new test directory /common/testData/, with test data for:

      • localeIdentifiers,

      • graphemeClusters (currently supported Indic languages)

      • transforms (transliterations)

      • For test purposes, added names for “pseudo-regions” XA and XB as noted above.

  • Infrastructure

      • Moved to GitHub for source code control and Jira for bug tracking (See CLDR Change Requests for new information). Queries using Trac no longer work.

      • Data in cldr repository keeps record of votes for inherited (↑↑↑) [CLDR-11989]. A new tool GenerateProductionData is used to resolve the inheritance markers and provide appropriate minimization.

      • A new cldr-staging repository contains data that has been processed with GenerateProductionData.

    • Added new API and tooling to support conversion to other formats (ICU in particular)

    • Performance improvements in Survey Tool

For details, see Detailed Specification Changes, Detailed Structure Changes, and Detailed Data Changes.

Detailed Specification Changes

For this version, the primary change in the LDML specification was to document changes in the emoji derived name algorithm.

For more detailed specification changes, see LDML36 Modifications.

Detailed Structure Changes

This version had only one structural addition and one new “alt” value for language names:

    • A new <compoundUnit type="times"> provides the pattern for combining units in a multiplicative relationship such as Newton-meters,

    • For some language names there is a new alt="menu" form which procides names more suitable for use in menus. For example:

    • <language type="yue" alt="menu">Chinese, Cantonese</language>.

Detailed Data Changes

Important data changes besides those listed in the Overview:

    • Transforms

      • Hiragana-Katakana no longer modifies the spacing dakuten U+309B, U+309C. [CLDR-13127]

      • Latin-ASCII enhanced for Latin extended C and D and some symbols. [CLDR-11383]

    • Miscellaneous

    • zh: The currency symbol for CNY changed from fullwidth ￥(FFE5) to halfwidth ¥ (00A5)

      • fr_CA : Switched to full year (not 2-digit year) in short date formats. [CLDR-11666]

      • bg: Removed “ч.” from time formats. [CLDR-11545]

      • The translations for the new name 'North Macedonia' has been refined for many languages by contributors, and those languages with no contributors have been reverted to code 'MK'. All Alt values also have been removed [CLDR-13099].

For more details see the list of bug fixes: Δ36.

Migration

    1. CLDR has moved to GitHub for source code control and Jira for bug tracking. Queries using Trac no longer work.

  1. The data in main cldr git repository includes element values with “↑↑↑”.

    1. Such values indicate that translators explicitly determined that the parent value is always valid.

    2. These values (and the paths they belong to) are removed from the release data, but tools that explicitly access the repository information directly need to remove them.

    3. A new tool in CLDR, GenerateProductionData.java, is used to strip the ↑↑↑ and minimize the data. (Those implementations that don't use that tool can remove lines that contain ↑↑↑; they will always be leaf nodes in XML.)

    4. A new repository cldr-staging contains data that has already been processed with GenerateProductionData.java (this is the data that is used for the release).

  2. Some empty files are included in /collation/, where the root data is valid for them, while some empty files are removed from /annotationsDerived and /subdivisions/

  3. Names have been added for “pseudo-regions” XA (Pseudo-Accents) and XB (Pseudo-Bidi). These are only intended for testing purposes, you may need to add special handling to remove them for production purposes. [CLDR-13100]

    1. North Macedonia: The translations for the new name 'North Macedonia' has been refined for many languages by contributors, and those languages with no contributors have been reverted to code 'MK'. All Alt values also have been removed [CLDR-13099].

  1. Other specific data changes to be aware of:

    1. zh: The currency symbol for CNY changed from fullwidth ￥(FFE5) to halfwidth ¥ (00A5)

      1. fr_CA : Switched to full year (not 2-digit year) in short date formats. [CLDR-11666]

      2. bg: Removed “ч.” from time formats. [CLDR-11545]

Known Issues

    1. The Transform charts are temporarily disabled. [CLDR-13308]

CLDR 36.1

This dot release makes incremental additions to version 36 for support of Unicode 13 and ICU 66. (These new, extra Q1 releases are for integration by vendors who could not otherwise release their products with the newest version of Unicode.)

  1. New script codes: Chrs, Diak, Kits, Yezi

  2. New numbering system: diak, segment

  3. Unicode 13.0 updates to root collation, with updated emoji collation (from CLDR 37 alpha data)

  4. Updates to Han-Latin transform and to Chinese pinyin and stroke collations from Unihan 13.0 data

  5. Updates to emoji annotations (from CLDR 37 alpha data)

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

Overview

Unicode CLDR 36 provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.

A main focus this release was on infrastructure. We moved to GitHub for source code control and Jira for bug tracking, and made significant improvements in performance of the online data-gathering Survey Tool. We are also now keeping more information in the master data, reflecting the votes in the Survey Tool for the “inherited” items (see Migration).

  • Approximately 32K items added

      • Significant increase (approx 50% or more) in moderate and/or modern coverage for: ceb (Cebuano), ha (Hausa / Latin script), ig (Igbo), kok (Konkani), qu (Quechua), to (Tongan), yo (Yoruba). Additionally, the following locales had at least a 15% increase in basic coverage: az (Azerbaijani / Latin script), so (Somali / Latin script).

    • Seed data for new locales, including three native languages of N. America: cic (Chickasaw), mus (Muscogee), osa (Osage, Osage script); an (Aragonese), su (Sundanese, Latin script), szl (Silesian).

      • Additional data for new items listed below.

  • Emoji

      • Added names and keywords for Emoji 13.0 draft candidates; these are to be fleshed out further in v36.1.

      • Refined names and keywords for Emoji 12.0, including for English.

    • Measurement units:

      • Additional compoundUnitPattern ({0}⋅{1} in root) for expressing units like newton-meter (N⋅m)

      • Additional units: dot-per-centimeter, dot-per-inch, em, megapixel, pixel, pixel-per-centimeter, pixel-per-inch; decade; therm-us; bar, pascal

  • Locale identifiers and names

    • Extended Language Matching to have fallbacks for many encompassed languages. [CLDR-13244]

    • Added more languageAliases from the BCP47 language subtag registry, for deprecated languages.

    • New alt=“menu” names for certain languages, intended to provide better sorting in menus. [CLDR-11834]

      • Updated validity and collection information for geographic subregions; updated names especially for subregions of UK and Sweden.

      • Names have been added for “pseudo-regions” XA (Pseudo-Accents) and XB (Pseudo-Bidi). These are only intended for testing purposes, you may need to add special handling to remove them for production purposes. [CLDR-13100]

    • Other

    • Additions for testing:

    • Added new test directory /common/testData/, with test data for:

      • localeIdentifiers,

      • graphemeClusters (currently supported Indic languages)

      • transforms (transliterations)

      • For test purposes, added names for “pseudo-regions” XA and XB as noted above.

  • Infrastructure

      • Moved to GitHub for source code control and Jira for bug tracking (See CLDR Change Requests for new information). Queries using Trac no longer work.

      • Data in cldr repository keeps record of votes for inherited (↑↑↑) [CLDR-11989]. A new tool GenerateProductionData is used to resolve the inheritance markers and provide appropriate minimization.

      • A new cldr-staging repository contains data that has been processed with GenerateProductionData.

    • Added new API and tooling to support conversion to other formats (ICU in particular)

    • Performance improvements in Survey Tool

For details, see Detailed Specification Changes, Detailed Structure Changes, and Detailed Data Changes.

Detailed Specification Changes

For this version, the primary change in the LDML specification was to document changes in the emoji derived name algorithm.

For more detailed specification changes, see LDML36 Modifications.

Detailed Structure Changes

This version had only one structural addition and one new “alt” value for language names:

    • A new <compoundUnit type="times"> provides the pattern for combining units in a multiplicative relationship such as Newton-meters,

    • For some language names there is a new alt="menu" form which procides names more suitable for use in menus. For example:

    • <language type="yue" alt="menu">Chinese, Cantonese</language>.

Detailed Data Changes

Important data changes besides those listed in the Overview:

    • Transforms

      • Hiragana-Katakana no longer modifies the spacing dakuten U+309B, U+309C. [CLDR-13127]

      • Latin-ASCII enhanced for Latin extended C and D and some symbols. [CLDR-11383]

    • Miscellaneous

    • zh: The currency symbol for CNY changed from fullwidth ￥(FFE5) to halfwidth ¥ (00A5)

      • fr_CA : Switched to full year (not 2-digit year) in short date formats. [CLDR-11666]

      • bg: Removed “ч.” from time formats. [CLDR-11545]

      • The translations for the new name 'North Macedonia' has been refined for many languages by contributors, and those languages with no contributors have been reverted to code 'MK'. All Alt values also have been removed [CLDR-13099].

For more details see the list of bug fixes: Δ36.

Migration

    1. CLDR has moved to GitHub for source code control and Jira for bug tracking. Queries using Trac no longer work.

  1. The data in main cldr git repository includes element values with “↑↑↑”.

    1. Such values indicate that translators explicitly determined that the parent value is always valid.

    2. These values (and the paths they belong to) are removed from the release data, but tools that explicitly access the repository information directly need to remove them.

    3. A new tool in CLDR, GenerateProductionData.java, is used to strip the ↑↑↑ and minimize the data. (Those implementations that don't use that tool can remove lines that contain ↑↑↑; they will always be leaf nodes in XML.)

    4. A new repository cldr-staging contains data that has already been processed with GenerateProductionData.java (this is the data that is used for the release).

  2. Some empty files are included in /collation/, where the root data is valid for them, while some empty files are removed from /annotationsDerived and /subdivisions/

  3. Names have been added for “pseudo-regions” XA (Pseudo-Accents) and XB (Pseudo-Bidi). These are only intended for testing purposes, you may need to add special handling to remove them for production purposes. [CLDR-13100]

    1. North Macedonia: The translations for the new name 'North Macedonia' has been refined for many languages by contributors, and those languages with no contributors have been reverted to code 'MK'. All Alt values also have been removed [CLDR-13099].

  1. Other specific data changes to be aware of:

    1. zh: The currency symbol for CNY changed from fullwidth ￥(FFE5) to halfwidth ¥ (00A5)

      1. fr_CA : Switched to full year (not 2-digit year) in short date formats. [CLDR-11666]

      2. bg: Removed “ч.” from time formats. [CLDR-11545]

Known Issues

    1. The Transform charts are temporarily disabled. [CLDR-13308]

CLDR 36.1

This dot release makes incremental additions to version 36 for support of Unicode 13 and ICU 66. (These new, extra Q1 releases are for integration by vendors who could not otherwise release their products with the newest version of Unicode.)

  1. New script codes: Chrs, Diak, Kits, Yezi

  2. New numbering system: diak, segment

  3. Unicode 13.0 updates to root collation, with updated emoji collation (from CLDR 37 alpha data)

  4. Updates to Han-Latin transform and to Chinese pinyin and stroke collations from Unihan 13.0 data

  5. Updates to emoji annotations (from CLDR 37 alpha data)

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Key to Header Links

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 37 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 37 Release Note

See Key to Header Links

Overview

Unicode CLDR provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

CLDR v37 focuses on adding new locales, enhancing support for units of measurement, adding annotations (names and search keywords) for symbols, and adding annotations for Emoji v13.

Data Changes

  • Units

    • Expanded locale preferences for units of measurement. The new unit preference and conversion data allows formatting functions to pick the right measurement units for the locale and usage, and convert input measurement into those units. See additional details in Specification Changes.

    • SI Prefixes. SI prefix patterns for "kilo{0}", "mega{0}", etc. have been added, as well as the prefix terms for square and cubic. These are fallbacks for when no combined form is available, so that the name for more unusual units like megagram or square megameter can be formed in different languages.

    • Other additions. A few unit identifiers translations been added, such as duration-century, area-square-kilometer, area-square-meter.

    • See also Migration.

  • Annotations

    • Emoji 13.0. The emoji annotations (names and search keywords) for the new Unicode 13.0 emoji are added.

    • Annotations (names and keywords) expanded to cover more than emoji. This release includes a small set of Unicode symbols (arrow, math, punctuation, currency, alphanumerics, and geometric) with more to be added in future releases. For example, see v37/annotations/romance.html.

  • Sorting

    • Emoji 13.0. The collation sequences are updated for new Unicode 13.0 and for Emoji 13.0.

  • Locales

    • New languages at Basic coverage: Fulah (Adlam), Maithili, Manipuri, Santali, Sindhi (Devanagari), Sundanese

    • New languages at Modern coverage: Nigerian Pidgin

    • See Locale Coverage Data for the coverage per locale, for both new and old locales.

  • Grammatical data

    • Grammatical features added. Grammatical features are added for many languages, a first step to allowing programmers to format units according to grammatical context (eg, the dative version of "3 kilometers").

  • Misc

    • Updates to code sets. In particular, the EU is updated (removing GB).

    • Alternate versions. In some languages

      • Some additional language names have "menu" style for alphabetizing, such as Kurdish, Central instead of Central Kurdish.

      • There are variants for Cape Verde as equivalent to Cabo Verde.

    • Myanmar-Latin transliteration added

For access to the data, see the GitHub tag above. For more details see the Delta Tickets above.

Specification Changes

The largest changes were the following:

  • Expanded locale preferences for units of measurement. The new unit preference and conversion data allows formatting functions to pick the right measurement units for the locale and usage, and convert input measurement into those units.

    • For example, a program (or database) could use 1.88 meters internally, but then for person-height have that measurement convert to 6 foot 2 inches for en_US and to 188 centimeters for de_CH.

    • Using the unit display names and list formats, those results can then be displayed according to the desired width (eg 2″ vs 2 in vs 2 inches) and using the locale display names and number formats.

    • The size of the measurement can also be taken into account, so that an infant can have a height as 18 inches, and an adult the height as 6 foot 2 inches.

  • Grammatical features added. Grammatical features are added for many languages.

    • List Patterns. Clarified that more sophisticated processing can be used, and added examples of customized processing for specific languages.

For more detailed specification changes, see the Spec above, and look at the Modifications section.

Structure Changes

  • New elements are added for enhanced unit preferences, such as the units to use for person-height in different countries. This is an initial phase; additional preferences will be added in the future.

  • Additionally, elements and data are added for unit conversions, so that programmers can supply amounts in one unit and get the right amounts to display for different locales.

  • Grammatical features are added for various languages, as a prelude to allowing programmers to format units according to grammatical context (eg, dative version of 3 kilometers)

  • The augmented constraints have been updated, so that the tests can apply those constraints to all of the CLDR data.

  • Annotations now include non-emoji. Note: emoji are distinguished from other symbols using Unicode properties.

For more information, see the Delta DTDs above.

Chart Changes

Growth

The following chart shows the growth of CLDR locale-specific data over time. It does not include the non-locale specific data, nor locale-specific data that is not collected via the Survey Tool. It is thus restricted to data items in /main and /annotations directories. The % values are percent of the current measure of Modern coverage. (That level is notched up each release.)

See also the Locale Coverage Data.

Migration

  • Seven unit identifiers with irregular components have been deprecated, and are given alias values to the regular forms. For example, square always comes before the unit, and is square, not squared. The validity data has also been updated to mark the older forms as deprecated.

      • inch-hg ⟹ inch-ofhg

      • liter-per-100kilometers ⟹ liter-per-100-kilometer

      • meter-per-second-squared ⟹ meter-per-square-second

      • millimeter-of-mercury ⟹ millimeter-ofhg

      • part-per-million ⟹ permillion

      • pound-foot ⟹ pound-force-foot

      • pound-per-square-inch ⟹ pound-force-per-square-inch

    • Some of the unit usage parameters were also deprecated, since they didn't differ in practice. (The spec has been updated to have fallback, so if these need to be distinct in the future, they would be of the form media-music or media-music-track.)

      • music-track ⟹ media

      • tv-program ⟹ media

    • The subdivision codes gbeng, gbsct, and gbwls (used for flag emoji) are now deprecated (ISO removed them from its latest data). This can affect implementations testing for validity if they don't also check for 'deprecated' in common/validity/subdivision.xml. Compare the Territory Subdivisions charts for v37 and v36.

Known Issues

  1. The expanded unit preferences are under development. The data is based on what was in CLDR v36, plus some other sources, but will be expanded in the future both to get better thresholds, and cover more cases where locales differ. See the ticket Improve unit structure and data [CLDR-13654]

  2. The Transform charts have been disabled. [CLDR-13308]

  3. The charts show spurious changes for gbeng, etc. That's because the file locations changed across releases.

  4. The JSON-format data for CLDR 37 currently omits the data from the CLDR common/supplemental files grammaticalFeatures.xml and units.xml. These are all new items in CLDR 37 except for the <unitPreferenceData>, which was formerly in supplementalData.xml. This will be addressed as soon as possible. [CLDR-13730]

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Special thanks to the contributors to Nigerian Pidgin; one of the very few locales to go from zero to Modern coverage in one submission cycle!

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

See Key to Header Links

Overview

Unicode CLDR provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

CLDR v37 focuses on adding new locales, enhancing support for units of measurement, adding annotations (names and search keywords) for symbols, and adding annotations for Emoji v13.

Data Changes

  • Units

    • Expanded locale preferences for units of measurement. The new unit preference and conversion data allows formatting functions to pick the right measurement units for the locale and usage, and convert input measurement into those units. See additional details in Specification Changes.

    • SI Prefixes. SI prefix patterns for "kilo{0}", "mega{0}", etc. have been added, as well as the prefix terms for square and cubic. These are fallbacks for when no combined form is available, so that the name for more unusual units like megagram or square megameter can be formed in different languages.

    • Other additions. A few unit identifiers translations been added, such as duration-century, area-square-kilometer, area-square-meter.

    • See also Migration.

  • Annotations

    • Emoji 13.0. The emoji annotations (names and search keywords) for the new Unicode 13.0 emoji are added.

    • Annotations (names and keywords) expanded to cover more than emoji. This release includes a small set of Unicode symbols (arrow, math, punctuation, currency, alphanumerics, and geometric) with more to be added in future releases. For example, see v37/annotations/romance.html.

  • Sorting

    • Emoji 13.0. The collation sequences are updated for new Unicode 13.0 and for Emoji 13.0.

  • Locales

    • New languages at Basic coverage: Fulah (Adlam), Maithili, Manipuri, Santali, Sindhi (Devanagari), Sundanese

    • New languages at Modern coverage: Nigerian Pidgin

    • See Locale Coverage Data for the coverage per locale, for both new and old locales.

  • Grammatical data

    • Grammatical features added. Grammatical features are added for many languages, a first step to allowing programmers to format units according to grammatical context (eg, the dative version of "3 kilometers").

  • Misc

    • Updates to code sets. In particular, the EU is updated (removing GB).

    • Alternate versions. In some languages

      • Some additional language names have "menu" style for alphabetizing, such as Kurdish, Central instead of Central Kurdish.

      • There are variants for Cape Verde as equivalent to Cabo Verde.

    • Myanmar-Latin transliteration added

For access to the data, see the GitHub tag above. For more details see the Delta Tickets above.

Specification Changes

The largest changes were the following:

  • Expanded locale preferences for units of measurement. The new unit preference and conversion data allows formatting functions to pick the right measurement units for the locale and usage, and convert input measurement into those units.

    • For example, a program (or database) could use 1.88 meters internally, but then for person-height have that measurement convert to 6 foot 2 inches for en_US and to 188 centimeters for de_CH.

    • Using the unit display names and list formats, those results can then be displayed according to the desired width (eg 2″ vs 2 in vs 2 inches) and using the locale display names and number formats.

    • The size of the measurement can also be taken into account, so that an infant can have a height as 18 inches, and an adult the height as 6 foot 2 inches.

  • Grammatical features added. Grammatical features are added for many languages.

    • List Patterns. Clarified that more sophisticated processing can be used, and added examples of customized processing for specific languages.

For more detailed specification changes, see the Spec above, and look at the Modifications section.

Structure Changes

  • New elements are added for enhanced unit preferences, such as the units to use for person-height in different countries. This is an initial phase; additional preferences will be added in the future.

  • Additionally, elements and data are added for unit conversions, so that programmers can supply amounts in one unit and get the right amounts to display for different locales.

  • Grammatical features are added for various languages, as a prelude to allowing programmers to format units according to grammatical context (eg, dative version of 3 kilometers)

  • The augmented constraints have been updated, so that the tests can apply those constraints to all of the CLDR data.

  • Annotations now include non-emoji. Note: emoji are distinguished from other symbols using Unicode properties.

For more information, see the Delta DTDs above.

Chart Changes

Growth

The following chart shows the growth of CLDR locale-specific data over time. It does not include the non-locale specific data, nor locale-specific data that is not collected via the Survey Tool. It is thus restricted to data items in /main and /annotations directories. The % values are percent of the current measure of Modern coverage. (That level is notched up each release.)

See also the Locale Coverage Data.

Migration

  • Seven unit identifiers with irregular components have been deprecated, and are given alias values to the regular forms. For example, square always comes before the unit, and is square, not squared. The validity data has also been updated to mark the older forms as deprecated.

      • inch-hg ⟹ inch-ofhg

      • liter-per-100kilometers ⟹ liter-per-100-kilometer

      • meter-per-second-squared ⟹ meter-per-square-second

      • millimeter-of-mercury ⟹ millimeter-ofhg

      • part-per-million ⟹ permillion

      • pound-foot ⟹ pound-force-foot

      • pound-per-square-inch ⟹ pound-force-per-square-inch

    • Some of the unit usage parameters were also deprecated, since they didn't differ in practice. (The spec has been updated to have fallback, so if these need to be distinct in the future, they would be of the form media-music or media-music-track.)

      • music-track ⟹ media

      • tv-program ⟹ media

    • The subdivision codes gbeng, gbsct, and gbwls (used for flag emoji) are now deprecated (ISO removed them from its latest data). This can affect implementations testing for validity if they don't also check for 'deprecated' in common/validity/subdivision.xml. Compare the Territory Subdivisions charts for v37 and v36.

Known Issues

  1. The expanded unit preferences are under development. The data is based on what was in CLDR v36, plus some other sources, but will be expanded in the future both to get better thresholds, and cover more cases where locales differ. See the ticket Improve unit structure and data [CLDR-13654]

  2. The Transform charts have been disabled. [CLDR-13308]

  3. The charts show spurious changes for gbeng, etc. That's because the file locations changed across releases.

  4. The JSON-format data for CLDR 37 currently omits the data from the CLDR common/supplemental files grammaticalFeatures.xml and units.xml. These are all new items in CLDR 37 except for the <unitPreferenceData>, which was formerly in supplementalData.xml. This will be addressed as soon as possible. [CLDR-13730]

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

Special thanks to the contributors to Nigerian Pidgin; one of the very few locales to go from zero to Modern coverage in one submission cycle!

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-38.md b/docs/site/downloads/cldr-38.md index d0554342824..2926f85906b 100644 --- a/docs/site/downloads/cldr-38.md +++ b/docs/site/downloads/cldr-38.md @@ -3,7 +3,7 @@ title: 'CLDR 38 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 38 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 38 Release Note

See Key to Header Links

Overview

Unicode CLDR provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

CLDR v38 focused on enhancing the support for existing locales: Support for units of measurement in inflected languages (phase 1), adding annotations (names and search keywords) for many more non-emoji symbols (~400), plus for Emoji v13.1. In this version, there is also substantially higher coverage for (in order of completeness): Norwegian Nynorsk, Hausa, Igbo, Breton, Quechua, Yoruba, Fulah (Adlam script), Chakma, Asturian, Sanskrit, and Dogri.

The units of measurement additions allow for support of APIs for simple unitIDs such as meter up to compound unitIDs such as cubic-meter-per-square-second or acre-feet-per-day, such as the following:

getUnitPattern(unitId, locale, width, pluralCategory, caseVariant) — to get the localized, inflected pattern for a simple or compound unit of measurement, appropriate for a position in a sentence or phrase with the appropriate pluralCategory and grammatical case (nominative, accusative, genitive, etc).

getUnitGender(unitId, locale) — to get the gender for a unit of measurement, so that other parts of a sentence or phrase can be modified to agree with that gender.

The Survey Tool has improvements in performance, and introduced structured forum requests to improve coordination among translators. We would like to thank the 393 language experts who contributed to this release.

There are some changes that affect existing specifications and data: for example, the plural rules for French changed to add a new category; the specification for using aliases is more rigorous, and some alias data has changed — along with the specification for handling locale identifier canonicalization. For more information, see Migration.

The overall changes to the data items were:

Added

155,131

Deleted

33,805

Changed

45,895

Data Changes

The following summarizes the changes to the data for this version of CLDR.

  • 13.1 Emoji and Unicode Symbols

      • Added names & search keywords for Emoji 13.1 and enhancements to existing emoji annotation data.

      • Added approximately 400 non-emoji Unicode symbols such as punctuation and currency symbols.

      • Added 2 character labels: superscript {0} and subscript {0}.

      • Aside from the CLDR target locales, emoji annotations and keywords expanded in Hausa (ha), Igbo (ig), Kalaallisut (kl), Luxembourgish (lb), Maori (mi), Manipuri (mni), Maltese (mt), Punjabi [Arabic] (pa_Arab), Kinyarwanda (rw), Tajik (tg), Tigrinya (ti), Uyghur (ug), Wolof (wo), Xhosa (xh), Yoruba (yo), with minor expansions in a few other languages.

  • Compact decimals and Units

      • Added 14 new units.

      • Added new binary prefixes.

      • Added new operand 'c' (with a synonym 'e') for languages like French (CLDR-12010)

  • Higher Coverage Levels

      • Modern: Norwegian Nynorsk

      • Moderate++: Hausa, Igbo, Breton, Quechua, Yoruba — made significant improvements, but didn't make it quite to Modern

      • Moderate: Fulah (Adlam), Chakma, Asturian

      • Basic+: Wolof, Tajik, Maori, Luxembourgish, Uyghur, Tigrinya — made significant improvements, but didn't get near to Moderate

      • Basic: Sanskrit, Dogri

  • Unit Inflections

      • Completed phase 1. The full goal is to add full case and gender support for formatted units. During phase 1, a limited number of locales (see below) and units of measurement are being handled, so that we can work kinks out of the process before expanding to all units for all locales (where we can get the grammatical structure).

      • Case & Gender: Polish (pl), Russian (ru), German (de), Hindi (hi) (in rough order of complexity)

      • Gender Only: Dutch (nl), Norwegian Bokmål (nb), Danish (da), Swedish (sv), French (fr), Italian (it), Portuguese (pt), Spanish (es)

  • Performance & Quality

      • Made substantial improvements in Survey Tool performance, lowering cost for translation.

      • Made substantial improvement in quality, using structured Forum topics to allow translators to collaborate more effectively.

      • Improved detection of translator errors.

  • ICU support

      • Improvements to CLDR API, providing a limited, stable API for extracting CLDR data.

      • Adding approximatelySign for number formatting.

  • Unicode locale identifiers and BCP 47

      • Added a new -u locale extension keyword -dx, used to specify scripts to exclude from dictionary break (for word and line break)

      • Added a new short timezone identifier: tz-glgoh

      • Revamped the language, script, region, and variant alias data to improve replacement of deprecated codes.

For access to the draft data, see the git tag above. For more details see the Delta tickets above.

JSON Data Changes

JSON data now includes data for plural ranges, grammatical inflections, typographical labels, and annotations. If you are making use of JSON data, please join the [cldr-users] mailing list where we would like to hear your feedback.

CLDR JSON data for v38 is available, please see https://github.com/unicode-org/cldr-json

Specification Changes

The largest changes were the following:

  • To make the canonicalization of locale identifiers clear and unambiguous, provided major restructuring of the specification for canonicalization. (This was done in concert with fixes to the alias data to work better with the specification.) See Migration and Annex C. LocaleId Canonicalization for more details.

  • To allow for overriding dictionary-based segmentation breaks, added the Unicode Dictionary Break Exclusion Identifier, with the new key “dx”.

  • For picking the correct units of measurement for locales, defined the userPreferences skeleton more precisely.

    • For accurate plural categories in compact numbers, added the 'c' operand to plural rules to provide formatting for languages such as French. (CLDR-12010)

  • To support inflected units of measurement (phase 1), add specifications for the new elements listed under Structure Changes and an algorithm for how to construct grammatical unit names (simple or compound).

For more detailed specification changes, see the Spec above, and look at the Modifications section.

Structure Changes

  • Added additional structure for unit inflections

    • New elements:

      • minimalPairs adds new elements caseMinimalPairs and genderMinimalPairs

      • unit adds a new element gender

      • grammaticalData adds new elements grammaticalDerivations, deriveCompound, and deriveComponent

    • New attributes for existing elements:

      • unitPattern adds a new attribute case

      • grammaticalCase, grammaticalGender, grammaticalDefiniteness add a new attribute scope

      • compoundUnitPattern1 adds new attributes case and gender

      • compoundUnitPattern adds a new attribute case

  • Number symbols adds approximatelySign element

  • Some additional attribute value constraints are added

    • for example, characterLabelPattern@type now allows for superscript and subscript values, indicated by the notation ⟪… strokes⟫➠⟪… strokes, subscript, superscript⟫ in Delta DTDs

    • some of these constraints are expanded due to new structure, while others are

For more details, see the Delta DTDs above.

Chart Changes

  • All charts are updated for the new data; for example, Romance Annotations shows the new non-emoji symbols and punctuation for Romance languages.

  • The DTD Deltas chart has a more compact representation for changes in attribute constraints, making the changes easier to see.

  • The new Grammatical Forms Charts show the new grammatical forms for units.

Growth

The following chart shows the growth of CLDR locale-specific data over time. It does not include the non-locale specific data, nor locale-specific data that is not collected via the Survey Tool. It is thus restricted to data items in /main and /annotations directories.

The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

See also the Locale Coverage Data v38 and for details of the changes see delta_summary.tsv and locale-growth.tsv

Migration

  • The plural rules for French changed to add a new category, 'many', using the new operand 'c' (with a synonym 'e'). It should only have effect on compact number handling.

    • Important: according to the spec, when there is no message for a plural category, the message for 'other' should be returned. As long as implementations observe this policy, migration to this should work without problems.

  • <languageMatches type="written"> was deprecated some time ago, and now has been removed. Clients should use <languageMatches type="written_new"> (recognizing that there are some syntax changes). CLDR-13245

  • The following locales have been moved in the folder structures. CLDR-14080

    • Seed → Common: Sanskrit (sa)

    • Common → Seed: Church Slavic (cu), Volapük (vo), Prussian (prg)

  • The specification for using aliases is more rigorous, and some alias data has changed. Programs using this data may need modification:

    • The specification processes the rules in a certain order, so the file order needs to be maintained.

    • The specification now explicitly takes multiple passes (though that can be optimized by implementations)

    • Various variantAliases are replaced by languageAliases where they require more context to be properly handed (the former specification did not handle variant aliases correctly).

      • AALAND ⇒ AX is replaced by und_aaland ⇒ und_AX

      • arevmda ⇒ hyw is replaced by two rules: hy_arevmda ⇒ hyw & und_arevmda ⇒ und

    • Some spurious aliases have been removed, where they are not properly aliases but rather partial duplications of more complete information:

      • Those covered by the parent locale data and/or likely subtag data, such as az_AZ ⇒ az_Latn_AZ

      • Those covered by canonicalization of extlang subtags, such as zh_wuu ⇒ wuu

    • Changes to the download files:

      • cldr-tools-*.zip no longer contains a built cldr.jar, use the separate cldr-tools-*.jar instead.

        • And as of v38.1 and later, cldr-tools-*.zip is no longer included at all. You can download or checkout the source tree directly from GitHub.

      • cldr-tools-*.jar is a standalone .jar file containing the CLDR tools and all needed dependencies.

      • There is a new "hashes/" subdirectory which contains GPG signatures and SHA-512 sums.

External Data Version

Known Issues

  1. The Transform charts have been disabled until the generating code could be fixed. [CLDR-11019]

  2. The JSON-format data for CLDR 38 currently omits the data from the CLDR common/supplemental files grammaticalFeatures.xml and units.xml. These are all new items in CLDR 37 except for the <unitPreferenceData>, which was formerly in supplementalData.xml. This will be addressed as soon as possible. [CLDR-13730]

  3. Hebrew compact number formatting scrambles text if embedded in RTL message [CLDR-14256]

    1. There are a number of fixes needed in the LDML specification.

    2. CLDR-14272 The documentation of @targets and @scope in grammaticalFeatures is missing; see the ticket for the missing text.

      1. CLDR-14312 replacement in subdivisionAlias in common/supplemental/supplementalMetadata.xml contains alpha{2}

      2. CLDR-14318 Should not remove "true" of tfield in UTS35 Appendix A

      3. CLDR-14319 Remove wrong/duplicated example below "Territory Exception" in UTS35 Appendix A

      4. CLDR-14320 "Put all <keywords, tfields> pairs into alphabetical order" is wrong in Appendix A of UTS35

      5. CLDR-13894 Need to use variantAlias replacement in BCP 47 Language Tag to Unicode BCP 47 Locale Identifier

      6. CLDR-14244 Document special 'alt' inheritance

CLDR 38.1

This dot release makes a very small number of incremental additions to version 38 to address the specific bugs listed in Δ38.1. The data changes are summarized in 38.1/delta/index.html. CLDR v38.1 is also included in ICU 68.2.

Migration note for CLDR 38.1:

    • As of v38.1 and later, cldr-tools-*.zip is no longer included in the download files. You can download or checkout the source tree directly from GitHub.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

See Key to Header Links

Overview

Unicode CLDR provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

CLDR v38 focused on enhancing the support for existing locales: Support for units of measurement in inflected languages (phase 1), adding annotations (names and search keywords) for many more non-emoji symbols (~400), plus for Emoji v13.1. In this version, there is also substantially higher coverage for (in order of completeness): Norwegian Nynorsk, Hausa, Igbo, Breton, Quechua, Yoruba, Fulah (Adlam script), Chakma, Asturian, Sanskrit, and Dogri.

The units of measurement additions allow for support of APIs for simple unitIDs such as meter up to compound unitIDs such as cubic-meter-per-square-second or acre-feet-per-day, such as the following:

getUnitPattern(unitId, locale, width, pluralCategory, caseVariant) — to get the localized, inflected pattern for a simple or compound unit of measurement, appropriate for a position in a sentence or phrase with the appropriate pluralCategory and grammatical case (nominative, accusative, genitive, etc).

getUnitGender(unitId, locale) — to get the gender for a unit of measurement, so that other parts of a sentence or phrase can be modified to agree with that gender.

The Survey Tool has improvements in performance, and introduced structured forum requests to improve coordination among translators. We would like to thank the 393 language experts who contributed to this release.

There are some changes that affect existing specifications and data: for example, the plural rules for French changed to add a new category; the specification for using aliases is more rigorous, and some alias data has changed — along with the specification for handling locale identifier canonicalization. For more information, see Migration.

The overall changes to the data items were:

Added

155,131

Deleted

33,805

Changed

45,895

Data Changes

The following summarizes the changes to the data for this version of CLDR.

  • 13.1 Emoji and Unicode Symbols

      • Added names & search keywords for Emoji 13.1 and enhancements to existing emoji annotation data.

      • Added approximately 400 non-emoji Unicode symbols such as punctuation and currency symbols.

      • Added 2 character labels: superscript {0} and subscript {0}.

      • Aside from the CLDR target locales, emoji annotations and keywords expanded in Hausa (ha), Igbo (ig), Kalaallisut (kl), Luxembourgish (lb), Maori (mi), Manipuri (mni), Maltese (mt), Punjabi [Arabic] (pa_Arab), Kinyarwanda (rw), Tajik (tg), Tigrinya (ti), Uyghur (ug), Wolof (wo), Xhosa (xh), Yoruba (yo), with minor expansions in a few other languages.

  • Compact decimals and Units

      • Added 14 new units.

      • Added new binary prefixes.

      • Added new operand 'c' (with a synonym 'e') for languages like French (CLDR-12010)

  • Higher Coverage Levels

      • Modern: Norwegian Nynorsk

      • Moderate++: Hausa, Igbo, Breton, Quechua, Yoruba — made significant improvements, but didn't make it quite to Modern

      • Moderate: Fulah (Adlam), Chakma, Asturian

      • Basic+: Wolof, Tajik, Maori, Luxembourgish, Uyghur, Tigrinya — made significant improvements, but didn't get near to Moderate

      • Basic: Sanskrit, Dogri

  • Unit Inflections

      • Completed phase 1. The full goal is to add full case and gender support for formatted units. During phase 1, a limited number of locales (see below) and units of measurement are being handled, so that we can work kinks out of the process before expanding to all units for all locales (where we can get the grammatical structure).

      • Case & Gender: Polish (pl), Russian (ru), German (de), Hindi (hi) (in rough order of complexity)

      • Gender Only: Dutch (nl), Norwegian Bokmål (nb), Danish (da), Swedish (sv), French (fr), Italian (it), Portuguese (pt), Spanish (es)

  • Performance & Quality

      • Made substantial improvements in Survey Tool performance, lowering cost for translation.

      • Made substantial improvement in quality, using structured Forum topics to allow translators to collaborate more effectively.

      • Improved detection of translator errors.

  • ICU support

      • Improvements to CLDR API, providing a limited, stable API for extracting CLDR data.

      • Adding approximatelySign for number formatting.

  • Unicode locale identifiers and BCP 47

      • Added a new -u locale extension keyword -dx, used to specify scripts to exclude from dictionary break (for word and line break)

      • Added a new short timezone identifier: tz-glgoh

      • Revamped the language, script, region, and variant alias data to improve replacement of deprecated codes.

For access to the draft data, see the git tag above. For more details see the Delta tickets above.

JSON Data Changes

JSON data now includes data for plural ranges, grammatical inflections, typographical labels, and annotations. If you are making use of JSON data, please join the [cldr-users] mailing list where we would like to hear your feedback.

CLDR JSON data for v38 is available, please see https://github.com/unicode-org/cldr-json

Specification Changes

The largest changes were the following:

  • To make the canonicalization of locale identifiers clear and unambiguous, provided major restructuring of the specification for canonicalization. (This was done in concert with fixes to the alias data to work better with the specification.) See Migration and Annex C. LocaleId Canonicalization for more details.

  • To allow for overriding dictionary-based segmentation breaks, added the Unicode Dictionary Break Exclusion Identifier, with the new key “dx”.

  • For picking the correct units of measurement for locales, defined the userPreferences skeleton more precisely.

    • For accurate plural categories in compact numbers, added the 'c' operand to plural rules to provide formatting for languages such as French. (CLDR-12010)

  • To support inflected units of measurement (phase 1), add specifications for the new elements listed under Structure Changes and an algorithm for how to construct grammatical unit names (simple or compound).

For more detailed specification changes, see the Spec above, and look at the Modifications section.

Structure Changes

  • Added additional structure for unit inflections

    • New elements:

      • minimalPairs adds new elements caseMinimalPairs and genderMinimalPairs

      • unit adds a new element gender

      • grammaticalData adds new elements grammaticalDerivations, deriveCompound, and deriveComponent

    • New attributes for existing elements:

      • unitPattern adds a new attribute case

      • grammaticalCase, grammaticalGender, grammaticalDefiniteness add a new attribute scope

      • compoundUnitPattern1 adds new attributes case and gender

      • compoundUnitPattern adds a new attribute case

  • Number symbols adds approximatelySign element

  • Some additional attribute value constraints are added

    • for example, characterLabelPattern@type now allows for superscript and subscript values, indicated by the notation ⟪… strokes⟫➠⟪… strokes, subscript, superscript⟫ in Delta DTDs

    • some of these constraints are expanded due to new structure, while others are

For more details, see the Delta DTDs above.

Chart Changes

  • All charts are updated for the new data; for example, Romance Annotations shows the new non-emoji symbols and punctuation for Romance languages.

  • The DTD Deltas chart has a more compact representation for changes in attribute constraints, making the changes easier to see.

  • The new Grammatical Forms Charts show the new grammatical forms for units.

Growth

The following chart shows the growth of CLDR locale-specific data over time. It does not include the non-locale specific data, nor locale-specific data that is not collected via the Survey Tool. It is thus restricted to data items in /main and /annotations directories.

The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

See also the Locale Coverage Data v38 and for details of the changes see delta_summary.tsv and locale-growth.tsv

Migration

  • The plural rules for French changed to add a new category, 'many', using the new operand 'c' (with a synonym 'e'). It should only have effect on compact number handling.

    • Important: according to the spec, when there is no message for a plural category, the message for 'other' should be returned. As long as implementations observe this policy, migration to this should work without problems.

  • <languageMatches type="written"> was deprecated some time ago, and now has been removed. Clients should use <languageMatches type="written_new"> (recognizing that there are some syntax changes). CLDR-13245

  • The following locales have been moved in the folder structures. CLDR-14080

    • Seed → Common: Sanskrit (sa)

    • Common → Seed: Church Slavic (cu), Volapük (vo), Prussian (prg)

  • The specification for using aliases is more rigorous, and some alias data has changed. Programs using this data may need modification:

    • The specification processes the rules in a certain order, so the file order needs to be maintained.

    • The specification now explicitly takes multiple passes (though that can be optimized by implementations)

    • Various variantAliases are replaced by languageAliases where they require more context to be properly handed (the former specification did not handle variant aliases correctly).

      • AALAND ⇒ AX is replaced by und_aaland ⇒ und_AX

      • arevmda ⇒ hyw is replaced by two rules: hy_arevmda ⇒ hyw & und_arevmda ⇒ und

    • Some spurious aliases have been removed, where they are not properly aliases but rather partial duplications of more complete information:

      • Those covered by the parent locale data and/or likely subtag data, such as az_AZ ⇒ az_Latn_AZ

      • Those covered by canonicalization of extlang subtags, such as zh_wuu ⇒ wuu

    • Changes to the download files:

      • cldr-tools-*.zip no longer contains a built cldr.jar, use the separate cldr-tools-*.jar instead.

        • And as of v38.1 and later, cldr-tools-*.zip is no longer included at all. You can download or checkout the source tree directly from GitHub.

      • cldr-tools-*.jar is a standalone .jar file containing the CLDR tools and all needed dependencies.

      • There is a new "hashes/" subdirectory which contains GPG signatures and SHA-512 sums.

External Data Version

Known Issues

  1. The Transform charts have been disabled until the generating code could be fixed. [CLDR-11019]

  2. The JSON-format data for CLDR 38 currently omits the data from the CLDR common/supplemental files grammaticalFeatures.xml and units.xml. These are all new items in CLDR 37 except for the <unitPreferenceData>, which was formerly in supplementalData.xml. This will be addressed as soon as possible. [CLDR-13730]

  3. Hebrew compact number formatting scrambles text if embedded in RTL message [CLDR-14256]

    1. There are a number of fixes needed in the LDML specification.

    2. CLDR-14272 The documentation of @targets and @scope in grammaticalFeatures is missing; see the ticket for the missing text.

      1. CLDR-14312 replacement in subdivisionAlias in common/supplemental/supplementalMetadata.xml contains alpha{2}

      2. CLDR-14318 Should not remove "true" of tfield in UTS35 Appendix A

      3. CLDR-14319 Remove wrong/duplicated example below "Territory Exception" in UTS35 Appendix A

      4. CLDR-14320 "Put all <keywords, tfields> pairs into alphabetical order" is wrong in Appendix A of UTS35

      5. CLDR-13894 Need to use variantAlias replacement in BCP 47 Language Tag to Unicode BCP 47 Locale Identifier

      6. CLDR-14244 Document special 'alt' inheritance

CLDR 38.1

This dot release makes a very small number of incremental additions to version 38 to address the specific bugs listed in Δ38.1. The data changes are summarized in 38.1/delta/index.html. CLDR v38.1 is also included in ICU 68.2.

Migration note for CLDR 38.1:

    • As of v38.1 and later, cldr-tools-*.zip is no longer included in the download files. You can download or checkout the source tree directly from GitHub.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-39.md b/docs/site/downloads/cldr-39.md index 5224a248b94..1e86a698f4d 100644 --- a/docs/site/downloads/cldr-39.md +++ b/docs/site/downloads/cldr-39.md @@ -3,7 +3,7 @@ title: 'CLDR 39 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 39 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 39 Release Note

See Key to Header Links

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

NOTE: The source for the LDML specification has been converted to Github Markdown (GFM) instead of HTML. The formatting is now simpler, but some features — such as formatting for table captions — are not yet complete. Improvements in the formatting for the v39 specification are planned for after the release, but no substantive changes would be made to the content. The link above goes to the directory

CLDR v39 had no submission phase. Instead the focus was on modernizing the Survey Tool software, preparing for data submission in the next release (v40). The data fixes in the release were confined to some global changes that are too difficult to do during a submission cycle, and various other fixes. There was a major change in how Norwegian is handled, in order to align the way that the locale identifiers no, nb, and nn are used. The CLDR github repo is changing the name of “master” branch to “main” branch. The unit support from the last release was integrated into ICU, and some fixes resulting from that process were made to the measurement unit data. Quite a number of fixes are made to the specification, to clarify text or fix problems in keyboards, measurement units, locale identifiers, and a few other areas.

Data Changes

DTD Changes 

Locale Changes (Sample Link)

There were general changes across all locales:

In addition, a number of other corrections were made on a per-locale basis.

Supplemental Data Changes

JSON Data Changes

JSON data is available at https://github.com/unicode-org/cldr-json/releases/tag/39.0.0 

It is also available in packages published under the npm version "39.0.0"

Note the following change:

- The npm packages now have individual README and LICENSE files [CLDR-14451]

Please note the following upcoming changes, planned for cldr-json in CLDR v40:

Specification Changes

The source for the LDML specification has been converted to Github Markdown (GFM) instead of HTML. The formatting is now simpler, but some features — such as formatting for table captions — may not be complete by the release date. Improvements in the formatting for the v39 specification are planned for after the release, but no substantive changes would be made to the content.

Chart Changes

Growth

The usual growth chart has been omitted, since this release had no data submission phase. For the previous version's chart, see Growth Chart (v38.x)

Migration

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing. Special thanks to Jan Kučera for his work on the migration to Markdown

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

See Key to Header Links

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

NOTE: The source for the LDML specification has been converted to Github Markdown (GFM) instead of HTML. The formatting is now simpler, but some features — such as formatting for table captions — are not yet complete. Improvements in the formatting for the v39 specification are planned for after the release, but no substantive changes would be made to the content. The link above goes to the directory

CLDR v39 had no submission phase. Instead the focus was on modernizing the Survey Tool software, preparing for data submission in the next release (v40). The data fixes in the release were confined to some global changes that are too difficult to do during a submission cycle, and various other fixes. There was a major change in how Norwegian is handled, in order to align the way that the locale identifiers no, nb, and nn are used. The CLDR github repo is changing the name of “master” branch to “main” branch. The unit support from the last release was integrated into ICU, and some fixes resulting from that process were made to the measurement unit data. Quite a number of fixes are made to the specification, to clarify text or fix problems in keyboards, measurement units, locale identifiers, and a few other areas.

Data Changes

DTD Changes 

Locale Changes (Sample Link)

There were general changes across all locales:

In addition, a number of other corrections were made on a per-locale basis.

Supplemental Data Changes

JSON Data Changes

JSON data is available at https://github.com/unicode-org/cldr-json/releases/tag/39.0.0 

It is also available in packages published under the npm version "39.0.0"

Note the following change:

- The npm packages now have individual README and LICENSE files [CLDR-14451]

Please note the following upcoming changes, planned for cldr-json in CLDR v40:

Specification Changes

The source for the LDML specification has been converted to Github Markdown (GFM) instead of HTML. The formatting is now simpler, but some features — such as formatting for table captions — may not be complete by the release date. Improvements in the formatting for the v39 specification are planned for after the release, but no substantive changes would be made to the content.

Chart Changes

Growth

The usual growth chart has been omitted, since this release had no data submission phase. For the previous version's chart, see Growth Chart (v38.x)

Migration

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing. Special thanks to Jan Kučera for his work on the migration to Markdown

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-40.md b/docs/site/downloads/cldr-40.md index 20d3792d9ff..038240f5001 100644 --- a/docs/site/downloads/cldr-40.md +++ b/docs/site/downloads/cldr-40.md @@ -3,7 +3,7 @@ title: 'CLDR 40 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 40 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 40 Release Note

See Key to Header Links

Overview

Unicode CLDR  provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR v40, the focus is on:

Grammatical features (gender and case)

In many languages, forming grammatical phrases requires dealing with grammatical gender and case. Without that, it can sound as bad as "on top of 3 hours" instead of "in 3 hours". The overall goal for CLDR is to supply building blocks so that implementations of advanced message formatting can handle gender and case. See also: Inflection Points.

Emoji v14 names and search keywords

CLDR supplies short names and search keywords for the new emoji, so that implementations can build on them to provide, for example, type-ahead in keyboards.

Modernized Survey Tool front end

The Survey Tool is used to gather all the data for locales. The outmoded Javascript infrastructure was modernized to make it easier to add enhancements (such as the split-screen dashboard) and to fix bugs.

Specification Improvements

The LDML specification has some important fixes and clarifications for Locale Identifiers, Dates, and Units of Measurement.

Approximately 140,000 data items were added or changed.

Data Changes

DTD Changes 

Segmentation Changes

Supplemental Data Changes

Locale Changes

File Changes

JSON Data Changes

Specification Changes

Locale Identifiers

Dates

Units of Measurement

Growth

The chart below shows the growth over time, with the additions from the latest release in the top blue section.

Migration

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+</table>" jsaction="rcuQ6b:WYd;">

See Key to Header Links

Overview

Unicode CLDR  provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR v40, the focus is on:

Grammatical features (gender and case)

In many languages, forming grammatical phrases requires dealing with grammatical gender and case. Without that, it can sound as bad as "on top of 3 hours" instead of "in 3 hours". The overall goal for CLDR is to supply building blocks so that implementations of advanced message formatting can handle gender and case. See also: Inflection Points.

Emoji v14 names and search keywords

CLDR supplies short names and search keywords for the new emoji, so that implementations can build on them to provide, for example, type-ahead in keyboards.

Modernized Survey Tool front end

The Survey Tool is used to gather all the data for locales. The outmoded Javascript infrastructure was modernized to make it easier to add enhancements (such as the split-screen dashboard) and to fix bugs.

Specification Improvements

The LDML specification has some important fixes and clarifications for Locale Identifiers, Dates, and Units of Measurement.

Approximately 140,000 data items were added or changed.

Data Changes

DTD Changes 

Segmentation Changes

Supplemental Data Changes

Locale Changes

File Changes

JSON Data Changes

Specification Changes

Locale Identifiers

Dates

Units of Measurement

Growth

The chart below shows the growth over time, with the additions from the latest release in the top blue section.

Migration

Known Issues

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-41.md b/docs/site/downloads/cldr-41.md index ee641668260..eb28969f2c8 100644 --- a/docs/site/downloads/cldr-41.md +++ b/docs/site/downloads/cldr-41.md @@ -3,7 +3,7 @@ title: 'CLDR 41 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 41 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 41 Release Note

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.


CLDR v41 is a limited-submission release. Most work was on tooling, with only specified updates to the data, namely Phase 3 of the grammatical units of measurement project. The required grammar data for the Modern coverage level increased, with 40 locales adding an average of 4% new data each. Ukrainian grew the most, by 15.6%.


The tooling changes  are targeted at the v42 general submission release. They include a number of features and improvements such as progress meter widgets in the Survey Tool. 


Finally, the Basic level has been modified to make it easier to onboard new languages, and easier for implementations to filter locale data based on coverage levels.

The following table shows the number of Languages/Locales in this version. (See the v41 Locale Coverage table for more information.)

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.


CLDR v41 is a limited-submission release. Most work was on tooling, with only specified updates to the data, namely Phase 3 of the grammatical units of measurement project. The required grammar data for the Modern coverage level increased, with 40 locales adding an average of 4% new data each. Ukrainian grew the most, by 15.6%.


The tooling changes  are targeted at the v42 general submission release. They include a number of features and improvements such as progress meter widgets in the Survey Tool. 


Finally, the Basic level has been modified to make it easier to onboard new languages, and easier for implementations to filter locale data based on coverage levels.

The following table shows the number of Languages/Locales in this version. (See the v41 Locale Coverage table for more information.)

Beyond the member organizations of the Unicode Consortium, many dedicated communities and individuals regularly contribute to updating their locales, including:

Data Changes

Because this is a limited-submission release, the data changes are limited. The focus for data this release was on Phase 3 of the project for providing grammatical information for units of measurement, with more locales reaching a modern coverage level, plus Phase 1 of a project to revamp Coverage levels.

DTD Changes 

Locale Changes

Supplemental Data Changes

File Changes

JSON Data Changes

Specification Changes

The following are the main changes in the specification:

Tooling Changes

Survey Tool

Developer

Migration

Upcoming Changes

Growth

The following shows the growth of CLDR data per year, represented as an area chart. 

Known Issues

This section will contain issues that arise after the data, code, or spec has been frozen.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+" jsaction="rcuQ6b:WYd;">

Beyond the member organizations of the Unicode Consortium, many dedicated communities and individuals regularly contribute to updating their locales, including:

Data Changes

Because this is a limited-submission release, the data changes are limited. The focus for data this release was on Phase 3 of the project for providing grammatical information for units of measurement, with more locales reaching a modern coverage level, plus Phase 1 of a project to revamp Coverage levels.

DTD Changes 

Locale Changes

Supplemental Data Changes

File Changes

JSON Data Changes

Specification Changes

The following are the main changes in the specification:

Tooling Changes

Survey Tool

Developer

Migration

Upcoming Changes

Growth

The following shows the growth of CLDR data per year, represented as an area chart. 

Known Issues

This section will contain issues that arise after the data, code, or spec has been frozen.

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-42.md b/docs/site/downloads/cldr-42.md index 950c6a544ba..fb636349063 100644 --- a/docs/site/downloads/cldr-42.md +++ b/docs/site/downloads/cldr-42.md @@ -3,7 +3,7 @@ title: 'CLDR 42 Download' --- -

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 42 Release Note

🏗 The CLDR site has been migrated to a new platform. Formatting and links continue to be fixed.

Unicode CLDR

CLDR 42 Release Note

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR 42, the focus is on:

Locale Status

CLDR v42 Language Count

Data Changes

There were two areas of focus for this release: the formatting of Personal Names, and the upgrade of Modern to include many more languages.

DTD Changes 

BCP47 Changes

Supplemental Data Changes

Locale Changes

File Changes 

JSON Data Changes

Background

Formatting people’s names

Software needs to be able to format people's names, such as John Smith or 宮崎駿. The data is typically drawn from a database, where a name record will have fields for the parts of people’s names, such as a given field with a value of “Maria”, and a surname field value of “Schmidt”. 

There are many complications in dealing with the variety of different ways this needs to be done across languages:

CLDR has added structured patterns that enable implementations to format available name fields for a given language. The formatting for a name can vary according to the available name fields, the language of the name and of the viewer, and various input settings.

The new Person Name formatting data has a tech preview status. The CLDR committee is requesting feedback on the data and structure so that it can be refined and enhanced in the next release. ICU will also be offering a tech preview API in its next release. Other clients of CLDR are recommended to try out the new data and structure, and supply feedback back to the CLDR committee in the next few months.

Specification Changes

The following are the main changes in the specification:

Growth

The following chart shows the growth of CLDR locale-specific data over time. It is restricted to data items in /main and /annotations directories, so it does not include the non-locale-specific data. The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

The detailed information on changes between v42 release and v41 are at v42 delta_summary.tsv: look at the TOTAL line for the overall counts of Added/Changed/Deleted. See v42 locale-growth.tsv for the detailed figures behind the chart.

CLDR v42 Growth

Migration

Known Issues

Upcoming changes

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+<center>See <a href="https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w" rel="nofollow" target="_blank">Key to Header Links</a>" jsaction="rcuQ6b:WYd;">

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR 42, the focus is on:

Locale Status

CLDR v42 Language Count

Data Changes

There were two areas of focus for this release: the formatting of Personal Names, and the upgrade of Modern to include many more languages.

DTD Changes 

BCP47 Changes

Supplemental Data Changes

Locale Changes

File Changes 

JSON Data Changes

Background

Formatting people’s names

Software needs to be able to format people's names, such as John Smith or 宮崎駿. The data is typically drawn from a database, where a name record will have fields for the parts of people’s names, such as a given field with a value of “Maria”, and a surname field value of “Schmidt”. 

There are many complications in dealing with the variety of different ways this needs to be done across languages:

CLDR has added structured patterns that enable implementations to format available name fields for a given language. The formatting for a name can vary according to the available name fields, the language of the name and of the viewer, and various input settings.

The new Person Name formatting data has a tech preview status. The CLDR committee is requesting feedback on the data and structure so that it can be refined and enhanced in the next release. ICU will also be offering a tech preview API in its next release. Other clients of CLDR are recommended to try out the new data and structure, and supply feedback back to the CLDR committee in the next few months.

Specification Changes

The following are the main changes in the specification:

Growth

The following chart shows the growth of CLDR locale-specific data over time. It is restricted to data items in /main and /annotations directories, so it does not include the non-locale-specific data. The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

The detailed information on changes between v42 release and v41 are at v42 delta_summary.tsv: look at the TOTAL line for the overall counts of Added/Changed/Deleted. See v42 locale-growth.tsv for the detailed figures behind the chart.

CLDR v42 Growth

Migration

Known Issues

Upcoming changes

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-43.md b/docs/site/downloads/cldr-43.md index c1eff48a650..86610d6acf6 100644 --- a/docs/site/downloads/cldr-43.md +++ b/docs/site/downloads/cldr-43.md @@ -6,16 +6,16 @@ title: CLDR 43 Release Note | No. | Date | Rel. Note | Data | Charts | Spec | Delta Tickets | GitHub Tag | Delta DTD | CLDR JSON | |:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:| -| 43 | 2023-04-12 | [v43](http://cldr.unicode.org/index/downloads/cldr-43) | [CLDR43](http://unicode.org/Public/cldr/43/) | [Charts43](https://unicode.org/cldr/charts/43#h.bzf6i36qsctj) | [LDML43](https://www.unicode.org/reports/tr35/tr35-68/tr35.html) | [ΔV43](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2243%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43](https://github.com/unicode-org/cldr/tree/release-43) | [ΔDtd43](https://cldr-smoke.unicode.org/staging-dev/charts/43/supplemental/dtd_deltas.html) | [43.0.0](https://github.com/unicode-org/cldr-json/releases/tag/43.0.0) | -| 43.1 | 2023-06-15 | [v43.1](https://cldr.unicode.org/index/downloads/cldr-43#h.qobmda543waj) | n/a | n/a | [LDML43.1](https://www.unicode.org/reports/tr35/tr35-69/tr35.html) | [ΔV43.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%2043.1%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43-1](https://github.com/unicode-org/cldr/tree/release-43-1) | See note in [43.1 Changes](https://cldr.unicode.org/index/downloads/cldr-43#h.qobmda543waj) | [43.1.0](https://github.com/unicode-org/cldr-json/releases/tag/43.1.0) | +| 43 | 2023-04-12 | [v43](/index/downloads/cldr-43) | [CLDR43](http://unicode.org/Public/cldr/43/) | [Charts43](https://unicode.org/cldr/charts/43#h.bzf6i36qsctj) | [LDML43](https://www.unicode.org/reports/tr35/tr35-68/tr35.html) | [ΔV43](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2243%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43](https://github.com/unicode-org/cldr/tree/release-43) | [ΔDtd43](https://cldr-smoke.unicode.org/staging-dev/charts/43/supplemental/dtd_deltas.html) | [43.0.0](https://github.com/unicode-org/cldr-json/releases/tag/43.0.0) | +| 43.1 | 2023-06-15 | [v43.1](/index/downloads/cldr-43#h.qobmda543waj) | n/a | n/a | [LDML43.1](https://www.unicode.org/reports/tr35/tr35-69/tr35.html) | [ΔV43.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%2043.1%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43-1](https://github.com/unicode-org/cldr/tree/release-43-1) | See note in [43.1 Changes](/index/downloads/cldr-43#h.qobmda543waj) | [43.1.0](https://github.com/unicode-org/cldr-json/releases/tag/43.1.0) | -See [Key to Header Links](https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w) +See [Key to Header Links](/index/downloads#h.xq13gabuoy9w) ## Overview -Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all [major software systems](https://cldr.unicode.org/index#TOC-Who-uses-CLDR-) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages. *It is important to review the [Migration](https://cldr.unicode.org/index/downloads/cldr-43#h.7s25aqdv767e) section for changes that might require action by implementations using CLDR directly or indirectly (eg, via ICU).* +Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all [major software systems](/index#TOC-Who-uses-CLDR-) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages. *It is important to review the [Migration](/index/downloads/cldr-43#h.7s25aqdv767e) section for changes that might require action by implementations using CLDR directly or indirectly (eg, via ICU).* -CLDR 43\.1 is a **dot release** focused on fixing specific issues. For more details for see [Version 43\.1 Changes.](https://cldr.unicode.org/index/downloads/cldr-43#h.qobmda543waj) +CLDR 43\.1 is a **dot release** focused on fixing specific issues. For more details for see [Version 43\.1 Changes.](/index/downloads/cldr-43#h.qobmda543waj) CLDR 43 is a **limited\-submission release**, focusing on just a few areas: @@ -227,7 +227,7 @@ The CLDR language matching data can *and should* be overridden whenever there is - **Seed has been merged into Common ([CLDR\-6396](https://unicode-org.atlassian.net/browse/CLDR-6396))** - All files have been moved from the **seed/** to the **common/** subdirectory. - - Implementations should make use of the **common/properties/coverageLevels.txt** file (added in CLDR v41\) to filter locale files appropriately, in place of depending on incomplete files being in seed. This file and its usage is documented at [Coverage Levels](https://cldr.unicode.org/index/cldr-spec/coverage-levels). ([CLDR\-16420](https://unicode-org.atlassian.net/browse/CLDR-16420)). + - Implementations should make use of the **common/properties/coverageLevels.txt** file (added in CLDR v41\) to filter locale files appropriately, in place of depending on incomplete files being in seed. This file and its usage is documented at [Coverage Levels](/index/cldr-spec/coverage-levels). ([CLDR\-16420](https://unicode-org.atlassian.net/browse/CLDR-16420)). - Background: Older versions of CLDR separated some locale files into a 'seed' directory, which some implementations used for filtering, but the criteria for moving from seed to common were not rigorous. To maintain compatibility with its set of locales used from previous versions, an implementation may use the **coverageLevels.txt** file filtering for Basic and above, but then also add locales that were previously included. - **Interval Formats** - A small number of interval formats (like “Dec 2 – 3”) have their spacing changed for consistency. This is unlikely to cause problems, as they are similar to a large number of similar changes in v42\. @@ -254,7 +254,7 @@ None currently. ## Acknowledgments -Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](https://cldr.unicode.org/index/acknowledgments) page for a full listing. +Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](/index/acknowledgments) page for a full listing. The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR data; in particular, see [Exhibit 1](https://unicode.org/copyright.html#Exhibit1). diff --git a/docs/site/downloads/cldr-44.md b/docs/site/downloads/cldr-44.md index e2328cf5e80..ac001619cb8 100644 --- a/docs/site/downloads/cldr-44.md +++ b/docs/site/downloads/cldr-44.md @@ -6,15 +6,15 @@ title: CLDR 44 Release Note | No. | Date | Rel. Note | Data | Charts | Spec | Delta Tickets | GitHub Tag | JSON Tag | Delta DTD | |:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:| -| 44 | 2023‑10‑31 | [v44](http://cldr.unicode.org/index/downloads/cldr-44) | [CLDR44](http://unicode.org/Public/cldr/44/) | [Charts44](https://unicode.org/cldr/charts/44/) | [LDML44](https://www.unicode.org/reports/tr35/tr35-70/tr35.html) | [Δ44](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44](https://github.com/unicode-org/cldr/tree/release-44) | [44.0.0](https://github.com/unicode-org/cldr-json/releases/tag/44.0.0)* | [ΔDtd44](https://unicode.org/cldr/charts/44/supplemental/dtd_deltas.html) | -| 44.1 | 2023‑12‑13 | [v44.1](http://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx) | n/a | n/a | [LDML44.1](https://www.unicode.org/reports/tr35/tr35-71/tr35.html) | [Δ44.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44-1](https://github.com/unicode-org/cldr/tree/release-44-1) | [44.1.0](https://github.com/unicode-org/cldr-json/releases/tag/44.1.0) | See [44.1 Changes](http://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx) | +| 44 | 2023‑10‑31 | [v44](/index/downloads/cldr-44) | [CLDR44](http://unicode.org/Public/cldr/44/) | [Charts44](https://unicode.org/cldr/charts/44/) | [LDML44](https://www.unicode.org/reports/tr35/tr35-70/tr35.html) | [Δ44](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44](https://github.com/unicode-org/cldr/tree/release-44) | [44.0.0](https://github.com/unicode-org/cldr-json/releases/tag/44.0.0)* | [ΔDtd44](https://unicode.org/cldr/charts/44/supplemental/dtd_deltas.html) | +| 44.1 | 2023‑12‑13 | [v44.1](/index/downloads/cldr-44#h.nvqx283jwsx) | n/a | n/a | [LDML44.1](https://www.unicode.org/reports/tr35/tr35-71/tr35.html) | [Δ44.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44-1](https://github.com/unicode-org/cldr/tree/release-44-1) | [44.1.0](https://github.com/unicode-org/cldr-json/releases/tag/44.1.0) | See [44.1 Changes](/index/downloads/cldr-44#h.nvqx283jwsx) | -See [Key To Header Links](https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w) +See [Key To Header Links](/index/downloads#h.xq13gabuoy9w) *Note: For NPM, the JSON data uses version 44.0.1 ## Overview -Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all [major software systems](https://cldr.unicode.org/index#h.ezpykkomyltl) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages. +Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all [major software systems](/index#h.ezpykkomyltl) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages. In CLDR 44, the focus is on: @@ -212,17 +212,17 @@ Similar behavior occurs with plural forms for units, where some plural forms may These are not always the same. In the future, some of these functions will be separated out; see [CLDR\-17095](https://unicode-org.atlassian.net/browse/CLDR-17095). - The test data file likelySubtags.txt has an error for input "qaa\-Cyrl\-CH"; the result should not be empty string as shown, it should either be FAIL or the input string (pending spec clarification). See [CLDR\-17150](https://unicode-org.atlassian.net/browse/CLDR-17150). -- The spec for \-u\-dx bcp47 subtag syntax requires further clarification. See [CLDR\-17194](https://unicode-org.atlassian.net/browse/CLDR-17194) . This is fixed in [version 44\.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx). +- The spec for \-u\-dx bcp47 subtag syntax requires further clarification. See [CLDR\-17194](https://unicode-org.atlassian.net/browse/CLDR-17194) . This is fixed in [version 44\.1](/index/downloads/cldr-44#h.nvqx283jwsx). - Subdivision translations were only updated on a limited basis. - Use 44\.0\.1 for CLDR 44 JSON NPM since 44\.0\.0 was tagged incorrectly. -- unicodeVersion in ldmlSupplemental.dtd [was not updated to 15\.1 See CLDR\-17225](https://unicode-org.atlassian.net/browse/CLDR-17225). This is fixed in [version 44\.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx). -- Missing derived emoji annotations [CLDR\-17230](https://unicode-org.atlassian.net/browse/CLDR-17230).  This is fixed in [version 44\.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx). -- There was an error in the Keyboard3 DTD in the \ element. It is corrected in [version 44\.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx), see [CLDR\-17204](https://unicode-org.atlassian.net/browse/CLDR-17204) -- The keyboard charts were not able to generate properly due to DTD changes. It is corrected in [version 44\.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx). (This fixed code was used to generate the charts for version 44\.) [CLDR\-17205](https://unicode-org.atlassian.net/browse/CLDR-17205) +- unicodeVersion in ldmlSupplemental.dtd [was not updated to 15\.1 See CLDR\-17225](https://unicode-org.atlassian.net/browse/CLDR-17225). This is fixed in [version 44\.1](/index/downloads/cldr-44#h.nvqx283jwsx). +- Missing derived emoji annotations [CLDR\-17230](https://unicode-org.atlassian.net/browse/CLDR-17230).  This is fixed in [version 44\.1](/index/downloads/cldr-44#h.nvqx283jwsx). +- There was an error in the Keyboard3 DTD in the \ element. It is corrected in [version 44\.1](/index/downloads/cldr-44#h.nvqx283jwsx), see [CLDR\-17204](https://unicode-org.atlassian.net/browse/CLDR-17204) +- The keyboard charts were not able to generate properly due to DTD changes. It is corrected in [version 44\.1](/index/downloads/cldr-44#h.nvqx283jwsx). (This fixed code was used to generate the charts for version 44\.) [CLDR\-17205](https://unicode-org.atlassian.net/browse/CLDR-17205) ## Acknowledgments -Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](https://cldr.unicode.org/index/acknowledgments) page for a full listing. +Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](/index/acknowledgments) page for a full listing. The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR data; in particular, see [Exhibit 1](https://unicode.org/copyright.html#Exhibit1). diff --git a/docs/site/downloads/cldr-45.md b/docs/site/downloads/cldr-45.md index d6515dc062d..bd897b09650 100644 --- a/docs/site/downloads/cldr-45.md +++ b/docs/site/downloads/cldr-45.md @@ -6,7 +6,7 @@ title: CLDR 45 Release Note | No. | Date | Rel. Note | Data | Charts | Spec | Delta | GitHub Tag | Delta DTD | CLDR JSON | |:---:|:----------:|:---------:|:------:|:--------:|:------------:|:---:|:----------:|:---------:|:---------:| -| 45 | 2024-04-17 | [v45](http://cldr.unicode.org/index/downloads/cldr-45) | [CLDR45](http://unicode.org/Public/cldr/45/) | [Charts45](https://unicode.org/cldr/charts/45/) | [LDML45](https://www.unicode.org/reports/tr35/tr35-72/tr35.html) | [Δ45](https://unicode-org.atlassian.net/issues/?jql=project+%3D+CLDR+AND+status+%3D+Done+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+%2245%22+ORDER+BY+component+ASC%2C+priority+DESC%2C+created+ASC) | [release-45](https://github.com/unicode-org/cldr/releases/tag/release-45) | [ΔDtd45](https://www.unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | [45.0.0](https://github.com/unicode-org/cldr-json/releases/tag/45.0.0) | +| 45 | 2024-04-17 | [v45](/index/downloads/cldr-45) | [CLDR45](http://unicode.org/Public/cldr/45/) | [Charts45](https://unicode.org/cldr/charts/45/) | [LDML45](https://www.unicode.org/reports/tr35/tr35-72/tr35.html) | [Δ45](https://unicode-org.atlassian.net/issues/?jql=project+%3D+CLDR+AND+status+%3D+Done+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+%2245%22+ORDER+BY+component+ASC%2C+priority+DESC%2C+created+ASC) | [release-45](https://github.com/unicode-org/cldr/releases/tag/release-45) | [ΔDtd45](https://www.unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | [45.0.0](https://github.com/unicode-org/cldr-json/releases/tag/45.0.0) | ## Overview @@ -138,8 +138,8 @@ For this release there are no appreciable changes. ## Acknowledgments -Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](https://cldr.unicode.org/index/acknowledgments) page for a full listing. +Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](/index/acknowledgments) page for a full listing. The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR data; in particular, see [Exhibit 1](https://unicode.org/copyright.html#Exhibit1). -For web pages with different views of CLDR data, see [http://cldr.unicode.org/index/charts](https://cldr.unicode.org/index/charts). +For web pages with different views of CLDR data, see [http://cldr.unicode.org/index/charts](/index/charts). diff --git a/docs/site/downloads/cldr-46.md b/docs/site/downloads/cldr-46.md index 8f3552c3d16..ee64cc705bd 100644 --- a/docs/site/downloads/cldr-46.md +++ b/docs/site/downloads/cldr-46.md @@ -12,12 +12,12 @@ title: CLDR 46 Release Note The data is available at [release-46-beta2](https://github.com/unicode-org/cldr/releases/tag/release-46-beta2), and the specification is available at [tr35/proposed.html](https://www.unicode.org/reports/tr35/proposed.html). -Feedback is welcome via [tickets](https://cldr.unicode.org/requesting_changes). (The CLDR site is undergoing a migration to Markdown, so the UI for navigation is temporary.) +Feedback is welcome via [tickets](/requesting_changes). (The CLDR site is undergoing a migration to Markdown, so the UI for navigation is temporary.) ## Overview Unicode CLDR provides key building blocks for software supporting the world's languages. -CLDR data is used by all [major software systems](https://cldr.unicode.org/index#who-uses-cldr) +CLDR data is used by all [major software systems](/index#who-uses-cldr) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages. @@ -63,7 +63,7 @@ The following are the most significant changes to the specification (LDML). 4. [semantic skeletons](https://cldr-smoke.unicode.org/spec/main/ldml/tr35-dates.html#Semantic_Skeletons) 5. [Grouping classes of characters](https://cldr-smoke.unicode.org/spec/main/ldml/tr35-collation.html#grouping_classes_of_characters) and other collation changes — see a summary [below](#collation-data-changes) -There are many more changes that are important to implementations, such as changes to certain identifier syntax and various algorithms. +There are many more changes that are important to implementations, such as changes to certain identifier syntax and various algorithms. See the [Modifications section](https://cldr-smoke.unicode.org/spec/main/ldml/tr35.html#Modifications) of the specification for details. ## Data Changes @@ -84,7 +84,7 @@ For a full listing, see [Delta DTDs](https://unicode.org/cldr/charts/46/suppleme 1. Added a new calendar type, `iso8601`. This is not the same as the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) standard format, which is designed just for data interchange: it is all ASCII, doesn't have all the options for fields (like "Sunday", "BC", or "AM"), and does not contain spaces. -The CLDR `iso8601` calendar uses patterns in the order: era, year, month, day, day-of-week, hour, minute, second, day-period, timezone +The CLDR `iso8601` calendar uses patterns in the order: era, year, month, day, day-of-week, hour, minute, second, day-period, timezone 2. Changed the metazone for Kazakhstan to reflect removal of Asia/Almaty, thus dropping the distinction among different regions in Kazakhstan. 3. Added support for deprecated timezone codes by remapping: `CST6CDT → America/Chicago`, `EST → America/Panama`, `EST5EDT → America/New_York`, `MST7MDT → America/Denver`, `PST8PDT → America/Los_Angeles`. 3. Units @@ -130,7 +130,7 @@ For a full listing, see [¤¤BCP47 Delta](https://unicode.org/cldr/charts/46/del 1. Major changes to emoji search keywords and short names ([see below](#emoji-search-keywords)) 2. Major changes to Chinese collation, reflecting new data in Unicode 16.0 -3. Added iso8601 patterns to root. +3. Added iso8601 patterns to root. These will use localized months, days of the week, day periods, and timezones. In this first version, the separators are not localized, and will use "-" within numeric dates, ":" within times, and " " or ", " between major elements. Full localization will await the next submission phase for CLDR. @@ -153,28 +153,28 @@ to better enable messages that contains right-to-left identifiers and text. Implementers should be aware of the following normative changes after the start of the tech review period. -* [\#885](https://github.com/unicode-org/message-format-wg/issues/885) Address equality of `name` and `literal` values, including requiring keys to use NFC -* [\#884](https://github.com/unicode-org/message-format-wg/issues/884) Add support for bidirectional isolates and strong marks in syntax and address UAX31/UTS55 requirements -* [\#883](https://github.com/unicode-org/message-format-wg/issues/883) Remove forward-compatibility promise and all reserved/private syntax. -* [\#882](https://github.com/unicode-org/message-format-wg/issues/882) Specify `bad-option` error for bad digit size options in `:number` and `:integer` functions -* [\#878](https://github.com/unicode-org/message-format-wg/issues/878) Clarify "rule" selection in `:number` and `:integer` functions -* [\#877](https://github.com/unicode-org/message-format-wg/issues/877) Match on variables instead of expressions. -* [\#854](https://github.com/unicode-org/message-format-wg/issues/854) Allow whitespace at complex message start -* [\#853](https://github.com/unicode-org/message-format-wg/issues/853) Add a "duplicate-variant" error -* [\#845](https://github.com/unicode-org/message-format-wg/issues/845) Define "attributes" feature -* [\#834](https://github.com/unicode-org/message-format-wg/issues/834) Modify the stability policy (not currently in effect due to Tech Preview) -* [\#816](https://github.com/unicode-org/message-format-wg/issues/816) Refine error handling -* [\#815](https://github.com/unicode-org/message-format-wg/issues/815) Removed machine-readable function registry as a deliverable -* [\#813](https://github.com/unicode-org/message-format-wg/issues/813) Change default of `:date` and `:datetime` date formatting from `short` to `medium` -* [\#812](https://github.com/unicode-org/message-format-wg/issues/812) Allow trailing whitespace for complex messages -* [\#793](https://github.com/unicode-org/message-format-wg/issues/793) Recommend the use of escapes only when necessary -* [\#775](https://github.com/unicode-org/message-format-wg/issues/775) Add formal definitions for variable, external variable, and local variable -* [\#774](https://github.com/unicode-org/message-format-wg/issues/774) Refactor errors, adding Message Function Errors -* [\#771](https://github.com/unicode-org/message-format-wg/issues/771) Remove inappropriate normative statement from errors.md -* [\#767](https://github.com/unicode-org/message-format-wg/issues/767) Add a test schema and [\#778](https://github.com/unicode-org/message-format-wg/issues/778) validate tests against it -* [\#775](https://github.com/unicode-org/message-format-wg/issues/775) Add a definition for `variable` -* [\#774](https://github.com/unicode-org/message-format-wg/issues/774) Refactor error types, adding a *Message Function Error* type (and subtypes) -* [\#769](https://github.com/unicode-org/message-format-wg/issues/769) Add `:test:function`, `:test:select` and `:test:format` functions for implementation testing +* [\#885](https://github.com/unicode-org/message-format-wg/issues/885) Address equality of `name` and `literal` values, including requiring keys to use NFC +* [\#884](https://github.com/unicode-org/message-format-wg/issues/884) Add support for bidirectional isolates and strong marks in syntax and address UAX31/UTS55 requirements +* [\#883](https://github.com/unicode-org/message-format-wg/issues/883) Remove forward-compatibility promise and all reserved/private syntax. +* [\#882](https://github.com/unicode-org/message-format-wg/issues/882) Specify `bad-option` error for bad digit size options in `:number` and `:integer` functions +* [\#878](https://github.com/unicode-org/message-format-wg/issues/878) Clarify "rule" selection in `:number` and `:integer` functions +* [\#877](https://github.com/unicode-org/message-format-wg/issues/877) Match on variables instead of expressions. +* [\#854](https://github.com/unicode-org/message-format-wg/issues/854) Allow whitespace at complex message start +* [\#853](https://github.com/unicode-org/message-format-wg/issues/853) Add a "duplicate-variant" error +* [\#845](https://github.com/unicode-org/message-format-wg/issues/845) Define "attributes" feature +* [\#834](https://github.com/unicode-org/message-format-wg/issues/834) Modify the stability policy (not currently in effect due to Tech Preview) +* [\#816](https://github.com/unicode-org/message-format-wg/issues/816) Refine error handling +* [\#815](https://github.com/unicode-org/message-format-wg/issues/815) Removed machine-readable function registry as a deliverable +* [\#813](https://github.com/unicode-org/message-format-wg/issues/813) Change default of `:date` and `:datetime` date formatting from `short` to `medium` +* [\#812](https://github.com/unicode-org/message-format-wg/issues/812) Allow trailing whitespace for complex messages +* [\#793](https://github.com/unicode-org/message-format-wg/issues/793) Recommend the use of escapes only when necessary +* [\#775](https://github.com/unicode-org/message-format-wg/issues/775) Add formal definitions for variable, external variable, and local variable +* [\#774](https://github.com/unicode-org/message-format-wg/issues/774) Refactor errors, adding Message Function Errors +* [\#771](https://github.com/unicode-org/message-format-wg/issues/771) Remove inappropriate normative statement from errors.md +* [\#767](https://github.com/unicode-org/message-format-wg/issues/767) Add a test schema and [\#778](https://github.com/unicode-org/message-format-wg/issues/778) validate tests against it +* [\#775](https://github.com/unicode-org/message-format-wg/issues/775) Add a definition for `variable` +* [\#774](https://github.com/unicode-org/message-format-wg/issues/774) Refactor error types, adding a *Message Function Error* type (and subtypes) +* [\#769](https://github.com/unicode-org/message-format-wg/issues/769) Add `:test:function`, `:test:select` and `:test:format` functions for implementation testing * [\#743](https://github.com/unicode-org/message-format-wg/issues/743) Collapse all escape sequence rules into one (affects the ABNF) In addition to the above, the test suite is significantly modified and updated. There will be updated tech preview implementations available in ICU (Java and C++) and in Javascript. @@ -292,10 +292,10 @@ These matched the ordering of two legacy character encodings. ## Acknowledgments Many people have made significant contributions to CLDR and LDML; -see the [Acknowledgments](https://cldr.unicode.org/index/acknowledgments) page for a full listing. +see the [Acknowledgments](/index/acknowledgments) page for a full listing. We'd especially like to acknowledge the work done by interns this release: Chris Pyle, Helena Aytenfisu (ህሊና የሺጥላ አይተንፍሱ), and Emiyare Cyril Ikwut-Ukwa. -The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR data; +The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR data; in particular, see [Exhibit 1](https://unicode.org/copyright.html#Exhibit1). -For web pages with different views of CLDR data, see [http://cldr.unicode.org/index/charts](https://cldr.unicode.org/index/charts). +For web pages with different views of CLDR data, see [http://cldr.unicode.org/index/charts](/index/charts). diff --git a/docs/site/index.md b/docs/site/index.md index 437ac46673d..f7f7da09618 100644 --- a/docs/site/index.md +++ b/docs/site/index.md @@ -8,14 +8,14 @@ title: Unicode CLDR Project - **2024-09-26 [CLDR 46 Beta](https://blog.unicode.org/2024/09/unicode-cldr-46-beta-available-for.html) available for testing and specification review** - **2024-09-05 [CLDR 46 Alpha](https://blog.unicode.org/2024/09/unicode-cldr-v46-alpha-available-for.html) available for testing** -- **2024-04-17 [CLDR 45](https://cldr.unicode.org/index/downloads/cldr-45) released** -- **2023-12-13 [CLDR 44.1](https://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx) released (an update to CLDR v44)** -- **2023-10-31 [CLDR 44](https://cldr.unicode.org/index/downloads/cldr-44) released** +- **2024-04-17 [CLDR 45](/index/downloads/cldr-45) released** +- **2023-12-13 [CLDR 44.1](/index/downloads/cldr-44#h.nvqx283jwsx) released (an update to CLDR v44)** +- **2023-10-31 [CLDR 44](/index/downloads/cldr-44) released** ## What is CLDR? -The Unicode Common Locale Data Repository (CLDR) provides key building blocks for software to support the world's languages, with the largest and most extensive standard repository of locale data available. This data is used by a [wide spectrum of companies](https://cldr.unicode.org/index#h.ezpykkomyltl) for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks. It includes: +The Unicode Common Locale Data Repository (CLDR) provides key building blocks for software to support the world's languages, with the largest and most extensive standard repository of locale data available. This data is used by a [wide spectrum of companies](/index#h.ezpykkomyltl) for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks. It includes: - **Locale-specific patterns for formatting and parsing:** dates, times, timezones, numbers and currency values, measurement units,… - **Translations of names:** languages, scripts, countries and regions, currencies, eras, months, weekdays, day periods, time zones, cities, and time units, emoji characters and sequences (and search keywords),… - **Language & script information:** characters used; plural cases; gender of lists; capitalization; rules for sorting & searching; writing direction; transliteration rules; rules for spelling out numbers; rules for segmenting text into graphemes, words, and sentences; keyboard layouts… @@ -45,7 +45,7 @@ There are other projects which consume cldr-json directly, see [here](https://gi Most developers will use CLDR indirectly, via a set of software libraries, such as [ICU](https://icu.unicode.org/), [Closure](https://github.com/google/closure-library), or [TwitterCLDR](https://blog.x.com/engineering/en_us/a/2012/twittercldr-improving-internationalization-support-in-ruby). These libraries typically compile the CLDR data into a format that is compact and easy for the library to load and use. -For those interested in the source CLDR data, it is available for each release in the XML format specified by [LDML](http://www.unicode.org/reports/tr35/). There are also tools that will convert to JSON and POSIX format. For more information, see [CLDR Releases/Downloads](https://cldr.unicode.org/index/downloads). +For those interested in the source CLDR data, it is available for each release in the XML format specified by [LDML](http://www.unicode.org/reports/tr35/). There are also tools that will convert to JSON and POSIX format. For more information, see [CLDR Releases/Downloads](/index/downloads). ## How to Contribute? @@ -53,9 +53,9 @@ CLDR is a collaborative project, which benefits by having people join and contri #### Translations and other language data -CLDR has an online tool to gather data, the [Survey Tool](https://cldr.unicode.org/index/survey-tool). The Survey Tool is open twice a year to gather data for new structure, and make corrections in previously-released data. +CLDR has an online tool to gather data, the [Survey Tool](/index/survey-tool). The Survey Tool is open twice a year to gather data for new structure, and make corrections in previously-released data. -- For languages that are already available in the Survey Tool, see [picking a locale](https://cldr.unicode.org/translation/getting-started/guide#h.6f2x50entpdr). If your locale is not already available in the Survey Tool, see [Adding new locales](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#adding-new-locales). +- For languages that are already available in the Survey Tool, see [picking a locale](/translation/getting-started/guide#h.6f2x50entpdr). If your locale is not already available in the Survey Tool, see [Adding new locales](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#adding-new-locales). - Contribute as an individual (vetter) for your language by [setting up an account](/index/survey-tool/survey-tool-accounts) - Qualifying organizations (companies, governments, institutions, etc) can request for an Organization level contribution status. Please file a [ticket](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#how-to-file-a-ticket) if you need organization set up. - Unicode [voting members](https://home.unicode.org/membership/members/) can join the technical committee for bigger impact. The CLDR Technical committee is responsible for assessing the Survey Tool features, proposals for additions or changes to structure, bug fixes, and final resolution of each release of CLDR. @@ -64,7 +64,7 @@ CLDR has an online tool to gather data, the [Survey Tool](https://cldr.unicode.o The CLDR tooling supports the interactive Survey Tool, plus all of the tooling necessary to test and process the release. Programmers interested in contributing to the tooling are welcome; they may also be interested in contributing to [ICU](http://site.icu-project.org/), which uses CLDR data. For more information, see http://cldr.unicode.org/development. -CLDR covers many different types of data, but not everything. For projects which may cover other types of data, see [Other Projects](http://cldr.unicode.org/covered-by-other-projects). +CLDR covers many different types of data, but not everything. For projects which may cover other types of data, see [Other Projects](/covered-by-other-projects). #### Tickets @@ -72,7 +72,7 @@ People may file [tickets](https://github.com/unicode-org/cldr/blob/main/docs/req ## Who has contributed? -Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](http://cldr.unicode.org/index/acknowledgments) page for a full listing. +Many people have made significant contributions to CLDR and LDML; see the [Acknowledgments](/index/acknowledgments) page for a full listing. ## What is the Schedule? diff --git a/docs/site/index/charts.md b/docs/site/index/charts.md index df10a4aba4e..5aab22e8f3a 100644 --- a/docs/site/index/charts.md +++ b/docs/site/index/charts.md @@ -8,7 +8,7 @@ The Unicode CLDR Charts provide different ways to view the Common Locale Data Re - [Latest](https://www.unicode.org/cldr/charts/latest) - The charts for the latest release version - [Dev](https://www.unicode.org/cldr/charts/dev) - A snapshot of data under development -- [Previous](https://cldr.unicode.org/index/downloads) - Previous available charts are linked from the download page in the Charts column +- [Previous](/index/downloads) - Previous available charts are linked from the download page in the Charts column The format of most of the fields in the charts will be clear from the Name and ID, such as the months of the year. The format for others, such as the date or time formats, is structured and requires more interpretation. For more information, see [UTS #35: Locale Data Markup Language (LDML)](http://www.unicode.org/reports/tr35/). @@ -35,8 +35,8 @@ Most charts have "double links" somewhere in each row. These are links that put Other Data - [**Supplemental Data**](https://www.unicode.org/cldr/charts/latest/supplemental/index.html) - General data that is not part of the locale hierarchy but is still part of CLDR. Includes: *plural rules, day-period rules, language matching, language-script information, territories (countries),* and their *subdivisions, timezones,* and so on. -- **Transform** - (Disabled temporarily) Some of the transforms in CLDR: the transliterations between different scripts. For more on transliterations, see [Transliteration Guidelines](https://cldr.unicode.org/index/cldr-spec/transliteration-guidelines). +- **Transform** - (Disabled temporarily) Some of the transforms in CLDR: the transliterations between different scripts. For more on transliterations, see [Transliteration Guidelines](/index/cldr-spec/transliteration-guidelines). - [**Keyboards**](https://www.unicode.org/cldr/charts/latest/keyboards/index.html) - Provides a view of keyboard data: layouts for different locales, mappings from characters to keyboards, and from keyboards to characters. -For more details on the locale data collection process, please see the [CLDR process](https://cldr.unicode.org/index/process). For filing or viewing bug reports, see [CLDR Bug Reports](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md). +For more details on the locale data collection process, please see the [CLDR process](/index/process). For filing or viewing bug reports, see [CLDR Bug Reports](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md). diff --git a/docs/site/index/cldr-spec.md b/docs/site/index/cldr-spec.md index 94445ef97f8..dc0e4f2c85e 100644 --- a/docs/site/index/cldr-spec.md +++ b/docs/site/index/cldr-spec.md @@ -5,12 +5,12 @@ title: CLDR Specifications # CLDR Specifications - [UTS #35: Unicode Locale Data Markup Language (LDML)](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Freports%2Ftr35%2F&sa=D&sntz=1&usg=AOvVaw3nQVa5S_8phVZOG1xv85Ie) is the specification of the XML format used for CLDR data, including the interpretation of the CLDR data. -- [Definitions](https://cldr.unicode.org/index/cldr-spec/definitions) - common definitions used in CLDR -- [Unicode Locale Extension (‘u’) for BCP 47](https://cldr.unicode.org/index/bcp47-extension) - an overview of the -u- extension -- [CLDR Survey Tool](https://cldr.unicode.org/index/survey-tool) - how to use the Survey Tool +- [Definitions](/index/cldr-spec/definitions) - common definitions used in CLDR +- [Unicode Locale Extension (‘u’) for BCP 47](/index/bcp47-extension) - an overview of the -u- extension +- [CLDR Survey Tool](/index/survey-tool) - how to use the Survey Tool - [Coverage Levels](https://www.google.com/url?q=https%3A%2F%2Fcldr.unicode.org%2Findex%2Fcldr-spec%2Fcoverage-levels&sa=D&sntz=1&usg=AOvVaw0k_LrECnZYzNCWCazI9c3c) - Detailed descriptions of the data required for a language to be considered supported at a specific level -- [Unicode Transliteration Guidelines](https://cldr.unicode.org/index/cldr-spec/transliteration-guidelines) - how to design and use Unicode transliterators -- [Picking the Right Language Identifier](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) - how to pick the right language code -- [Collation Guidelines](https://cldr.unicode.org/index/cldr-spec/collation-guidelines) - how to construct collation rules -- [JSON Bindings for CLDR Data](https://cldr.unicode.org/index/cldr-spec/cldr-json-bindings) +- [Unicode Transliteration Guidelines](/index/cldr-spec/transliteration-guidelines) - how to design and use Unicode transliterators +- [Picking the Right Language Identifier](/index/cldr-spec/picking-the-right-language-code) - how to pick the right language code +- [Collation Guidelines](/index/cldr-spec/collation-guidelines) - how to construct collation rules +- [JSON Bindings for CLDR Data](/index/cldr-spec/cldr-json-bindings) diff --git a/docs/site/index/cldr-spec/collation-guidelines.md b/docs/site/index/cldr-spec/collation-guidelines.md index 482037def72..8a89f202e63 100644 --- a/docs/site/index/cldr-spec/collation-guidelines.md +++ b/docs/site/index/cldr-spec/collation-guidelines.md @@ -10,11 +10,11 @@ The locale\-based collation rules in Unicode CLDR specify customizations of the ## Filing a Request -Requests to change the collation order for a given locale, or to supply additional variants should be filed as CLDR bug tickets. See [CLDR Change Requests](https://cldr.unicode.org/index/bug-reports) +Requests to change the collation order for a given locale, or to supply additional variants should be filed as CLDR bug tickets. See [CLDR Change Requests](/index/bug-reports) ### Rules -The request should present the precise change expressed as rules. The rules must be supplied in the syntax as specified in [http://www.unicode.org/reports/tr35/tr35\-collation.html\#Rules](http://www.unicode.org/reports/tr35/tr35-collation.html#Rules). (This used to be called the "basic syntax".) The rules must also be [Minimal Rules](https://cldr.unicode.org/index/cldr-spec/collation-guidelines) as described below: *only* differences from [http://unicode.org/charts/uca/](http://unicode.org/charts/uca/) should be specified. +The request should present the precise change expressed as rules. The rules must be supplied in the syntax as specified in [http://www.unicode.org/reports/tr35/tr35\-collation.html\#Rules](http://www.unicode.org/reports/tr35/tr35-collation.html#Rules). (This used to be called the "basic syntax".) The rules must also be [Minimal Rules](/index/cldr-spec/collation-guidelines) as described below: *only* differences from [http://unicode.org/charts/uca/](http://unicode.org/charts/uca/) should be specified. *\& c \< cs* diff --git a/docs/site/index/cldr-spec/core-data-for-new-locales.md b/docs/site/index/cldr-spec/core-data-for-new-locales.md index 94b859bce6a..fa1605c3d5d 100644 --- a/docs/site/index/cldr-spec/core-data-for-new-locales.md +++ b/docs/site/index/cldr-spec/core-data-for-new-locales.md @@ -7,13 +7,13 @@ title: Core Data for New Locales This document describes the minimal data needed for a new locale. There are two kinds of data that are relevant for new locales: 1. **Core Data** \- This is data that the CLDR committee needs from the proposer ***before*** a new locale is added. The proposer is expected to also get a Survey Tool account, and contribute towards the Basic Data. -2. **Basic Data** \- The Core data is just the first step. It is only created under the expectation that people will engage in suppling data, at a [Basic Coverage Level](https://cldr.unicode.org/index/cldr-spec/coverage-levels#h.yi1eiryx7yl4). **If the locale does not meet the [Basic Coverage Level](https://cldr.unicode.org/index/cldr-spec/coverage-levels#h.yi1eiryx7yl4) in the next Survey Tool cycle, the committee may remove the locale.** +2. **Basic Data** \- The Core data is just the first step. It is only created under the expectation that people will engage in suppling data, at a [Basic Coverage Level](/index/cldr-spec/coverage-levels#h.yi1eiryx7yl4). **If the locale does not meet the [Basic Coverage Level](/index/cldr-spec/coverage-levels#h.yi1eiryx7yl4) in the next Survey Tool cycle, the committee may remove the locale.** ## Core Data -Collect and submit the following data, using the [Core Data Submission Form](https://docs.google.com/forms/d/e/1FAIpQLSfSyz0VUSXD93IJQQdjzUCnbQwC2nwz6eiLjTaFjASQZzpoSg/viewform). *Note to translators: If you are having difficulties or questions about the following data, please contact us: [file a new bug](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket), or post a follow\-up to comment to your existing bug.* +Collect and submit the following data, using the [Core Data Submission Form](https://docs.google.com/forms/d/e/1FAIpQLSfSyz0VUSXD93IJQQdjzUCnbQwC2nwz6eiLjTaFjASQZzpoSg/viewform). *Note to translators: If you are having difficulties or questions about the following data, please contact us: [file a new bug](/index/bug-reports#TOC-Filing-a-Ticket), or post a follow\-up to comment to your existing bug.* -1. The correct language code according to [Picking the Right Language Identifier](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code). +1. The correct language code according to [Picking the Right Language Identifier](/index/cldr-spec/picking-the-right-language-code). 2. The four exemplar sets: main, auxiliary, numbers, punctuation.  - These must reflect the Unicode model. For more information, see [tr35\-general.html\#Character\_Elements](http://www.unicode.org/reports/tr35/tr35-general.html#Character_Elements). 3. Verified country data ( i.e. the population of speakers in the regions (countries) in which the language is commonly used)  @@ -21,12 +21,12 @@ Collect and submit the following data, using the [Core Data Submission Form](htt - "Users of the language" includes as either a 1st or 2nd language. The main focus is on written language. 4. Default content script and region (normally the region is the country with largest population using that language, and the customary script used for that language in that country).  - **\[[supplemental/supplementalMetadata.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/supplementalMetadata.xml#LC1654:~:text=%3CdefaultContent)]** - - *See*: [http://cldr.unicode.org/translation/translation\-guide\-general/default\-content](https://cldr.unicode.org/translation/translation-guide-general/default-content) + - *See*: [http://cldr.unicode.org/translation/translation\-guide\-general/default\-content](/translation/translation-guide-general/default-content) 5. The correct time cycle used with the language in the default content region - In common/supplemental/supplementalData.xml, this is the "timeData" element - The value should be h (1\-12\), H (0\-23\), k (1\-24\), or K (0\-11\); as defined in [https://www.unicode.org/reports/tr35/tr35\-dates.html\#Date\_Field\_Symbol\_Table](https://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) -***You must commit to supplying [the data required for the new locale to reach Basic level](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales#h.yaraq3qjxnns) during the next open CLDR submission when requesting a new locale to be added.*** +***You must commit to supplying [the data required for the new locale to reach Basic level](/index/cldr-spec/core-data-for-new-locales#h.yaraq3qjxnns) during the next open CLDR submission when requesting a new locale to be added.*** -For more information on the other coverage levels refer to [Coverage Levels](https://cldr.unicode.org/index/cldr-spec/coverage-levels)  +For more information on the other coverage levels refer to [Coverage Levels](/index/cldr-spec/coverage-levels)  diff --git a/docs/site/index/cldr-spec/coverage-levels.md b/docs/site/index/cldr-spec/coverage-levels.md index 95e895f9c27..1cec2d188e2 100644 --- a/docs/site/index/cldr-spec/coverage-levels.md +++ b/docs/site/index/cldr-spec/coverage-levels.md @@ -32,11 +32,11 @@ To filter "at that level or above", you use the fact that basic ⊂ moderate ⊂ ### Migration -As of v43, the files in **/seed/** have been moved to **/common/**. Older versions of CLDR separated some locale files into a 'seed' directory. Some implementations used for filtering, but the criteria for moving from seed to common were not rigorous. To maintain compatibility with the set of locales used from previous versions, an implementation may use the above process for Basic and above, but then also add locales that were previously included. For more information, see [CLDR 43 Release Note](https://cldr.unicode.org/index/downloads/cldr-43).  +As of v43, the files in **/seed/** have been moved to **/common/**. Older versions of CLDR separated some locale files into a 'seed' directory. Some implementations used for filtering, but the criteria for moving from seed to common were not rigorous. To maintain compatibility with the set of locales used from previous versions, an implementation may use the above process for Basic and above, but then also add locales that were previously included. For more information, see [CLDR 43 Release Note](/index/downloads/cldr-43).  ## Core Data -**The data needed for a new locale to be added. See [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales) for details on Core Data and how to submit for new locales.** +**The data needed for a new locale to be added. See [Core Data for New Locales](/index/cldr-spec/core-data-for-new-locales) for details on Core Data and how to submit for new locales.** **It is expected that during the next Survey Tool cycle after a new locale is added, the data for the Basic Coverage Level will be supplied.** @@ -70,13 +70,13 @@ Before submitting data above the Basic Level, the following must be in place: 1. Plural and Ordinal rules - As in \[supplemental/plurals.xml] and \[supplemental/ordinals.xml] - Must also include minimal pairs - - For more information, see [cldr\-spec/plural\-rules](https://cldr.unicode.org/index/cldr-spec/plural-rules). + - For more information, see [cldr\-spec/plural\-rules](/index/cldr-spec/plural-rules). 2. Casing information (only where the language uses a cased scripts according to [ScriptMetadata.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/scriptMetadata.txt)) - This will go into [common/casing](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/casing/) 3. Collation rules \[non\-Survey Tool] - This can be supplied as a list of characters, or as rule file. - The list is a space\-delimited list of the characters used by the language (in the given script). The list may include multiple\-character strings, where those are treated specially. For example, if "ch" is sorted after "h" one might see "a b c d .. g h ch i j ..." - - More sophisticated users can do a better job, supplying a file of rules as in [cldr\-spec/collation\-guidelines](https://cldr.unicode.org/index/cldr-spec/collation-guidelines). + - More sophisticated users can do a better job, supplying a file of rules as in [cldr\-spec/collation\-guidelines](/index/cldr-spec/collation-guidelines). 4. The result will be a file like: [common/collation/ar.xml](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/collation/ar.xml) or [common/collation/da.xml](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/collation/da.xml). The data for the Moderate Level includes subsets of the Modern data, both in depth and breadth. diff --git a/docs/site/index/cldr-spec/currency-process.md b/docs/site/index/cldr-spec/currency-process.md index 663c4bb690d..4e2f84b0719 100644 --- a/docs/site/index/cldr-spec/currency-process.md +++ b/docs/site/index/cldr-spec/currency-process.md @@ -12,6 +12,6 @@ There are three stages for new currency symbols (such as the recent Russian, Ind | 2 | Adopted widely in fonts and keyboards used in the relevant locales. | It is added it to the relevant locales as the standard version. | | 3 | Widely recognized outside of the locales, and in most operating systems (Android, iOS, Windows, Mac — not just the latest versions, but also older ones that have significant market share). | Added to root as the standard version. | -For more information, see [Currency Symbols \& Names](https://cldr.unicode.org/translation/currency-names-and-symbols/currency-names). +For more information, see [Currency Symbols \& Names](/translation/currency-names-and-symbols/currency-names). diff --git a/docs/site/index/cldr-spec/picking-the-right-language-code.md b/docs/site/index/cldr-spec/picking-the-right-language-code.md index bcef5c5aa58..3768860fdb0 100644 --- a/docs/site/index/cldr-spec/picking-the-right-language-code.md +++ b/docs/site/index/cldr-spec/picking-the-right-language-code.md @@ -15,7 +15,7 @@ If you are looking at a prospective language code, like "swh", the process is si ## Choosing the Base Language Code 1. Go to [iso639\-3](http://www-01.sil.org/iso639-3/codes.asp) to find the language. Typically you'll look under **Name** starting with **G** for Ganda. -2. There may be multiple entries for the item you want, so you'll need to look at all of them. For example, on the page for names starting with “P”, there are three records: “Panjabi”, “Mirpur Panjabi” and “Western Panjabi” (it is the last of these that corresponds to Lahnda). You can also try a search, but be [careful](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code). +2. There may be multiple entries for the item you want, so you'll need to look at all of them. For example, on the page for names starting with “P”, there are three records: “Panjabi”, “Mirpur Panjabi” and “Western Panjabi” (it is the last of these that corresponds to Lahnda). You can also try a search, but be [careful](/index/cldr-spec/picking-the-right-language-code). 3. You'll find an entry like:  lug  lug  **lg**  Ganda  Individual  Living  more ... @@ -27,7 +27,7 @@ While you may think that you are done, you have to verify that the three\-letter 3. Verify that is indeed the language: 1. Look at the information on the ethnologue page 2. Check Wikipedia and other web sources -4. ***AND IMPORTANTLY: Review [Caution!](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) below*** +4. ***AND IMPORTANTLY: Review [Caution!](/index/cldr-spec/picking-the-right-language-code) below*** Once you have the right three\-letter code, you are still not done. Unicode (and BCP 47\) uses the 2 letter ISO code if it exists. Unicode also uses the "macro language" where suitable. *So* @@ -38,7 +38,7 @@ Once you have the right three\-letter code, you are still not done. Unicode (and ## Choosing Script/Territory Subtags -If you need a particular variant of a language, then you'll add additional subtags, typically script or territory. Consult [Sample Subtags](http://unicode.org/cldr/utility/sample_subtags.html) for the most common choices. ***Again, review*** [***Caution!***](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) ***below.*** +If you need a particular variant of a language, then you'll add additional subtags, typically script or territory. Consult [Sample Subtags](http://unicode.org/cldr/utility/sample_subtags.html) for the most common choices. ***Again, review*** [***Caution!***](/index/cldr-spec/picking-the-right-language-code) ***below.*** ## Verifying Your Choice @@ -46,7 +46,7 @@ If you need a particular variant of a language, then you'll add additional subta 2. You need to fix the identifier and try again in *any* if the demo shows any of the following: 1. the language identifer is illegal, or 2. one of the subtags is invalid, or - 3. there are any replacement values. [\*\*](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) + 3. there are any replacement values. [\*\*](/index/cldr-spec/picking-the-right-language-code) ## Documenting Your Choice @@ -76,7 +76,7 @@ For compatibility, it is strongly recommended that all implementations accept bo ### Macrolanguages -ISO (and hence BCP 47\) has the notion of an individual language (like en \= English) versus a Collection or Macrolanguage. For compatibility, Unicode language and locale identifiers always use the Macrolanguage to identify the predominant form. Thus the Macrolanguage subtag "zh" (Chinese) is used instead of "cmn" (Mandarin). Similarly, suppose that you are looking for Kurdish written in Latin letters, as in Turkey. It is a mistake to think that because that is in the north, that you should use the subtag 'kmr' for Northern Kurdish. You should instead use [ku\-Latn\-TR](http://ku-latn/). See also: [ISO 636 Deprecation Requests](https://cldr.unicode.org/development/development-process/design-proposals/iso-636-deprecation-requests-draft). +ISO (and hence BCP 47\) has the notion of an individual language (like en \= English) versus a Collection or Macrolanguage. For compatibility, Unicode language and locale identifiers always use the Macrolanguage to identify the predominant form. Thus the Macrolanguage subtag "zh" (Chinese) is used instead of "cmn" (Mandarin). Similarly, suppose that you are looking for Kurdish written in Latin letters, as in Turkey. It is a mistake to think that because that is in the north, that you should use the subtag 'kmr' for Northern Kurdish. You should instead use [ku\-Latn\-TR](http://ku-latn/). See also: [ISO 636 Deprecation Requests](/development/development-process/design-proposals/iso-636-deprecation-requests-draft). Unicode language identifiers do not allow the "extlang" form defined in BCP 47\. For example, use "yue" instead of "zh\-yue" for Cantonese. diff --git a/docs/site/index/cldr-spec/plural-rules.md b/docs/site/index/cldr-spec/plural-rules.md index 99c8ed7ac50..a1405feff93 100644 --- a/docs/site/index/cldr-spec/plural-rules.md +++ b/docs/site/index/cldr-spec/plural-rules.md @@ -19,7 +19,7 @@ These categories are used to provide localized units, with a more natural ways o ## Reporting Defects -When you find errors or omissions in this data, please report the information with a [bug report](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). Please give examples of how the forms may differ. You don't have to give the exact rules, but it is extremely helpful! Here's an example:   +When you find errors or omissions in this data, please report the information with a [bug report](/index/bug-reports#TOC-Filing-a-Ticket). Please give examples of how the forms may differ. You don't have to give the exact rules, but it is extremely helpful! Here's an example:   **Sample Bug Report** @@ -192,7 +192,7 @@ See [LDML Language Plural Rules](http://unicode.org/reports/tr35/tr35-numbers.ht ## Plural Message Migration -The plural categories are used not only within CLDR, but also for localizing messages for different products. When the plural rules change (such as in [CLDR 24](https://cldr.unicode.org/index/downloads/cldr-24-release-note)), the following issues should be considered. Fractional support in plurals is new in CLDR 24\. Because the fractions didn't work before, the changes in categories from 23 to 24 should not cause an issue for implementations. The other changes can be categorized as Splitting or Merging categories. +The plural categories are used not only within CLDR, but also for localizing messages for different products. When the plural rules change (such as in [CLDR 24](/index/downloads/cldr-24-release-note)), the following issues should be considered. Fractional support in plurals is new in CLDR 24\. Because the fractions didn't work before, the changes in categories from 23 to 24 should not cause an issue for implementations. The other changes can be categorized as Splitting or Merging categories. There are some more complicated cases, but the following outlines the main issues to watch for, using examples. For illustration, assume a language uses "" for singular, "u" for dual, and "s" for other.​ ​ diff --git a/docs/site/index/corrigenda.md b/docs/site/index/corrigenda.md index 8feabe5dc5c..0b404fbf9fd 100644 --- a/docs/site/index/corrigenda.md +++ b/docs/site/index/corrigenda.md @@ -4,7 +4,7 @@ title: Corrigenda and Errata # Corrigenda and Errata -The Corrigenda and Errata are found on the corresponding release pages. Issues that can cause significant problems are considered corrigenda, and are listed on the corresponding release page. Problems that do not rise to the level of a corrigendum are considered errata, and are listed on the corresponding release page without being listed here. For example, errata for CLDR 1.9 may be found on [CLDR Release 1.9, Errata](https://cldr.unicode.org/index/downloads/cldr-1-9-release-note). +The Corrigenda and Errata are found on the corresponding release pages. Issues that can cause significant problems are considered corrigenda, and are listed on the corresponding release page. Problems that do not rise to the level of a corrigendum are considered errata, and are listed on the corresponding release page without being listed here. For example, errata for CLDR 1.9 may be found on [CLDR Release 1.9, Errata](/index/downloads/cldr-1-9-release-note). At this time, there is only one Corrigendum: diff --git a/docs/site/index/downloads.md b/docs/site/index/downloads.md index 6041991cd83..ed8651ae99a 100644 --- a/docs/site/index/downloads.md +++ b/docs/site/index/downloads.md @@ -4,7 +4,7 @@ title: CLDR Releases/Downloads # CLDR Releases/Downloads -*Each release of the Unicode CLDR is a stable release and may be used as reference material or cited as a normative reference by other specifications. Each version, once published, is absolutely stable and will never change. Implementations may also apply [CLDR Corrigenda](https://cldr.unicode.org/index/corrigenda) to a release. Bug reports and feature requests for subsequent versions may be filed at [Bug Reports](https://cldr.unicode.org/index/bug-reports).* +*Each release of the Unicode CLDR is a stable release and may be used as reference material or cited as a normative reference by other specifications. Each version, once published, is absolutely stable and will never change. Implementations may also apply [CLDR Corrigenda](/index/corrigenda) to a release. Bug reports and feature requests for subsequent versions may be filed at [Bug Reports](/index/bug-reports).* ## Downloads @@ -13,31 +13,31 @@ The following table lists the files for each released version. For license infor | No. | Date | Rel. Note | Data | Charts | Spec | Delta Tickets | GitHub Tag | Delta DTD | |---|---|---|---|---|---|---|---|---| -| Latest | | [latest-version](https://cldr.unicode.org/index/downloads/latest) | [latest-data](https://unicode.org/Public/cldr/45/) | [latest-charts](https://www.unicode.org/cldr/charts/45/index.html) | [latest-ldml](https://www.unicode.org/reports/tr35/) | [latest-tickets](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2245%22%20ORDER%20BY%20created%20ASC) | [release-45](https://github.com/unicode-org/cldr/tree/release-45) | [latest-delta-dtd](https://www.unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | -| Dev | | [dev-version](https://cldr.unicode.org/index/downloads/dev) | | [dev-charts](http://unicode.org/cldr/charts/dev) | [dev-ldml](http://www.unicode.org/reports/tr35/proposed.html) | [dev-tickets](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2246%22%20ORDER%20BY%20created%20ASC) | [main](https://github.com/unicode-org/cldr.git) | [dev-delta-dtd](https://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html) | -| 45 | 2024-04-17 | [v45](http://cldr.unicode.org/index/downloads/cldr-45) | [CLDR45](http://unicode.org/Public/cldr/45/) | [Charts45](https://unicode.org/cldr/charts/45/) | [LDML45](https://www.unicode.org/reports/tr35/tr35-72/tr35.html) | [Δ45](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2245%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-45](https://github.com/unicode-org/cldr/tree/release-45) | [ΔDtd45](https://unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | -| 44.1 | 2023-12-13 | [v44.1](http://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx) | n/a | n/a | [LDML44.1](https://www.unicode.org/reports/tr35/tr35-71/tr35.html) | [Δ44.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44-1](https://github.com/unicode-org/cldr/tree/release-44-1) | See [44.1 Changes](http://cldr.unicode.org/index/downloads/cldr-44#h.nvqx283jwsx) | -| 44 | 2023-10-31 | [v44](http://cldr.unicode.org/index/downloads/cldr-44) | [CLDR44](http://unicode.org/Public/cldr/44/) | [Charts44](https://unicode.org/cldr/charts/44/) | [LDML44](https://www.unicode.org/reports/tr35/tr35-70/tr35.html) | [Δ44](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44](https://github.com/unicode-org/cldr/tree/release-44) | [ΔDtd44](https://unicode.org/cldr/charts/44/supplemental/dtd_deltas.html) | -| 43.1 | 2023-06-15 | [v43.1](https://cldr.unicode.org/index/downloads/cldr-43#h.qobmda543waj) | n/a | n/a | [LDML43.1](https://www.unicode.org/reports/tr35/tr35-69/tr35.html) | [Δ43.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2243%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43-1](https://github.com/unicode-org/cldr/tree/release-43-1) | See [43.1 Changes](https://cldr.unicode.org/index/downloads/cldr-43#h.qobmda543waj) | -| 43 | 2023-04-12 | [v43](http://cldr.unicode.org/index/downloads/cldr-43) | [CLDR43](http://unicode.org/Public/cldr/43/) | [Charts43](https://www.unicode.org/cldr/charts/43/) | [LDML43](https://www.unicode.org/reports/tr35/tr35-68/tr35.html) | [Δ43](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2243%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43](https://github.com/unicode-org/cldr/tree/release-43) | [ΔDtd43](https://www.unicode.org/cldr/charts/43/supplemental/dtd_deltas.html) | -| 42 | 2022-10-19 | [v42](http://cldr.unicode.org/index/downloads/cldr-42) | [CLDR42](http://unicode.org/Public/cldr/42/) | [Charts42](https://www.unicode.org/cldr/charts/42/) | [LDML42](https://www.unicode.org/reports/tr35/tr35-67/tr35.html) | [Δ42](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2242%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-42](https://github.com/unicode-org/cldr/tree/release-42) | [ΔDtd42](https://www.unicode.org/cldr/charts/42/supplemental/dtd_deltas.html) | -| 41 | 2022-04-06 | [v41](http://cldr.unicode.org/index/downloads/cldr-41) | [CLDR41](http://unicode.org/Public/cldr/41/) | [Charts41](https://www.unicode.org/cldr/charts/41/) | [LDML41](https://www.unicode.org/reports/tr35/tr35-66/tr35.html) | [Δ41](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2241%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-41](https://github.com/unicode-org/cldr/tree/release-41) | [ΔDtd41](https://www.unicode.org/cldr/charts/41/supplemental/dtd_deltas.html) | -| 40 | 2021-10-27 | [v40](http://cldr.unicode.org/index/downloads/cldr-40) | [CLDR40](http://unicode.org/Public/cldr/40/) | [Charts40](https://www.unicode.org/cldr/charts/40/) | [LDML40](https://www.unicode.org/reports/tr35/tr35-65/tr35.html) | [Δ40](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2240%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-40](https://github.com/unicode-org/cldr/tree/release-40) | [ΔDtd40](https://www.unicode.org/cldr/charts/40/supplemental/dtd_deltas.html) | -| 39 | 2021-04-07 | [v39](http://cldr.unicode.org/index/downloads/cldr-39) | [CLDR39](http://unicode.org/Public/cldr/39/) | [Charts39](https://www.unicode.org/cldr/charts/39/) | [LDML39](https://www.unicode.org/reports/tr35/tr35-63/tr35.html) | [Δ39](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2239%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-39](https://github.com/unicode-org/cldr/tree/release-39) | [ΔDtd39](https://www.unicode.org/cldr/charts/39/supplemental/dtd_deltas.html) | -| 38.1 | 2020-12-17 | [v38.1](http://cldr.unicode.org/index/downloads/cldr-38?pli=1#TOC-CLDR-38.1) | [CLDR38.1](http://unicode.org/Public/cldr/38.1) | [Charts38.1](https://www.unicode.org/cldr/charts/38.1/index.html) | [LDML38](https://www.unicode.org/reports/tr35/tr35-61/tr35.html) | [Δ38.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2238%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-38-1](https://github.com/unicode-org/cldr/tree/release-38-1) | [ΔDtd38.1](https://www.unicode.org/cldr/charts/38.1/supplemental/dtd_deltas.html) | -| 38 | 2020-10-28 | [v38](http://cldr.unicode.org/index/downloads/cldr-38) | [CLDR38](http://unicode.org/Public/cldr/38/) | [Charts38](https://www.unicode.org/cldr/charts/38/) | [LDML38](https://www.unicode.org/reports/tr35/tr35-61/tr35.html) | [Δ38](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2238%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-38](https://github.com/unicode-org/cldr/tree/release-38) | [ΔDtd38](https://www.unicode.org/cldr/charts/38/supplemental/dtd_deltas.html) | -| 37 | 2020-04-23 | [v37](http://cldr.unicode.org/index/downloads/cldr-37) | [CLDR37](http://unicode.org/Public/cldr/37/) | [Charts37](https://www.unicode.org/cldr/charts/37/) | [LDML37](https://www.unicode.org/reports/tr35/tr35-59/tr35.html) | [Δ37](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2237%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-37](https://github.com/unicode-org/cldr/tree/release-37) | [ΔDtd37](https://www.unicode.org/cldr/charts/37/supplemental/dtd_deltas.html) | +| Latest | | [latest-version](/index/downloads/latest) | [latest-data](https://unicode.org/Public/cldr/45/) | [latest-charts](https://www.unicode.org/cldr/charts/45/index.html) | [latest-ldml](https://www.unicode.org/reports/tr35/) | [latest-tickets](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2245%22%20ORDER%20BY%20created%20ASC) | [release-45](https://github.com/unicode-org/cldr/tree/release-45) | [latest-delta-dtd](https://www.unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | +| Dev | | [dev-version](/index/downloads/dev) | | [dev-charts](http://unicode.org/cldr/charts/dev) | [dev-ldml](http://www.unicode.org/reports/tr35/proposed.html) | [dev-tickets](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2246%22%20ORDER%20BY%20created%20ASC) | [main](https://github.com/unicode-org/cldr.git) | [dev-delta-dtd](https://www.unicode.org/cldr/charts/dev/supplemental/dtd_deltas.html) | +| 45 | 2024-04-17 | [v45](/index/downloads/cldr-45) | [CLDR45](http://unicode.org/Public/cldr/45/) | [Charts45](https://unicode.org/cldr/charts/45/) | [LDML45](https://www.unicode.org/reports/tr35/tr35-72/tr35.html) | [Δ45](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2245%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-45](https://github.com/unicode-org/cldr/tree/release-45) | [ΔDtd45](https://unicode.org/cldr/charts/45/supplemental/dtd_deltas.html) | +| 44.1 | 2023-12-13 | [v44.1](/index/downloads/cldr-44#h.nvqx283jwsx) | n/a | n/a | [LDML44.1](https://www.unicode.org/reports/tr35/tr35-71/tr35.html) | [Δ44.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44-1](https://github.com/unicode-org/cldr/tree/release-44-1) | See [44.1 Changes](/index/downloads/cldr-44#h.nvqx283jwsx) | +| 44 | 2023-10-31 | [v44](/index/downloads/cldr-44) | [CLDR44](http://unicode.org/Public/cldr/44/) | [Charts44](https://unicode.org/cldr/charts/44/) | [LDML44](https://www.unicode.org/reports/tr35/tr35-70/tr35.html) | [Δ44](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2244%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-44](https://github.com/unicode-org/cldr/tree/release-44) | [ΔDtd44](https://unicode.org/cldr/charts/44/supplemental/dtd_deltas.html) | +| 43.1 | 2023-06-15 | [v43.1](/index/downloads/cldr-43#h.qobmda543waj) | n/a | n/a | [LDML43.1](https://www.unicode.org/reports/tr35/tr35-69/tr35.html) | [Δ43.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2243%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43-1](https://github.com/unicode-org/cldr/tree/release-43-1) | See [43.1 Changes](/index/downloads/cldr-43#h.qobmda543waj) | +| 43 | 2023-04-12 | [v43](/index/downloads/cldr-43) | [CLDR43](http://unicode.org/Public/cldr/43/) | [Charts43](https://www.unicode.org/cldr/charts/43/) | [LDML43](https://www.unicode.org/reports/tr35/tr35-68/tr35.html) | [Δ43](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2243%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-43](https://github.com/unicode-org/cldr/tree/release-43) | [ΔDtd43](https://www.unicode.org/cldr/charts/43/supplemental/dtd_deltas.html) | +| 42 | 2022-10-19 | [v42](/index/downloads/cldr-42) | [CLDR42](http://unicode.org/Public/cldr/42/) | [Charts42](https://www.unicode.org/cldr/charts/42/) | [LDML42](https://www.unicode.org/reports/tr35/tr35-67/tr35.html) | [Δ42](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20in%20(Fixed%2C%20%22Fix%20in%20Survey%20Tool%20(CLDR)%22%2C%20%22Fixed%20non-repo%22)%20AND%20fixVersion%20%3D%20%2242%22%20ORDER%20BY%20resolution%20ASC%2C%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-42](https://github.com/unicode-org/cldr/tree/release-42) | [ΔDtd42](https://www.unicode.org/cldr/charts/42/supplemental/dtd_deltas.html) | +| 41 | 2022-04-06 | [v41](/index/downloads/cldr-41) | [CLDR41](http://unicode.org/Public/cldr/41/) | [Charts41](https://www.unicode.org/cldr/charts/41/) | [LDML41](https://www.unicode.org/reports/tr35/tr35-66/tr35.html) | [Δ41](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2241%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-41](https://github.com/unicode-org/cldr/tree/release-41) | [ΔDtd41](https://www.unicode.org/cldr/charts/41/supplemental/dtd_deltas.html) | +| 40 | 2021-10-27 | [v40](/index/downloads/cldr-40) | [CLDR40](http://unicode.org/Public/cldr/40/) | [Charts40](https://www.unicode.org/cldr/charts/40/) | [LDML40](https://www.unicode.org/reports/tr35/tr35-65/tr35.html) | [Δ40](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2240%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-40](https://github.com/unicode-org/cldr/tree/release-40) | [ΔDtd40](https://www.unicode.org/cldr/charts/40/supplemental/dtd_deltas.html) | +| 39 | 2021-04-07 | [v39](/index/downloads/cldr-39) | [CLDR39](http://unicode.org/Public/cldr/39/) | [Charts39](https://www.unicode.org/cldr/charts/39/) | [LDML39](https://www.unicode.org/reports/tr35/tr35-63/tr35.html) | [Δ39](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2239%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-39](https://github.com/unicode-org/cldr/tree/release-39) | [ΔDtd39](https://www.unicode.org/cldr/charts/39/supplemental/dtd_deltas.html) | +| 38.1 | 2020-12-17 | [v38.1](/index/downloads/cldr-38?pli=1#TOC-CLDR-38.1) | [CLDR38.1](http://unicode.org/Public/cldr/38.1) | [Charts38.1](https://www.unicode.org/cldr/charts/38.1/index.html) | [LDML38](https://www.unicode.org/reports/tr35/tr35-61/tr35.html) | [Δ38.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2238%2E1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-38-1](https://github.com/unicode-org/cldr/tree/release-38-1) | [ΔDtd38.1](https://www.unicode.org/cldr/charts/38.1/supplemental/dtd_deltas.html) | +| 38 | 2020-10-28 | [v38](/index/downloads/cldr-38) | [CLDR38](http://unicode.org/Public/cldr/38/) | [Charts38](https://www.unicode.org/cldr/charts/38/) | [LDML38](https://www.unicode.org/reports/tr35/tr35-61/tr35.html) | [Δ38](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2238%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-38](https://github.com/unicode-org/cldr/tree/release-38) | [ΔDtd38](https://www.unicode.org/cldr/charts/38/supplemental/dtd_deltas.html) | +| 37 | 2020-04-23 | [v37](/index/downloads/cldr-37) | [CLDR37](http://unicode.org/Public/cldr/37/) | [Charts37](https://www.unicode.org/cldr/charts/37/) | [LDML37](https://www.unicode.org/reports/tr35/tr35-59/tr35.html) | [Δ37](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2237%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-37](https://github.com/unicode-org/cldr/tree/release-37) | [ΔDtd37](https://www.unicode.org/cldr/charts/37/supplemental/dtd_deltas.html) | | 36.1 | 2020-03-11 | v36.1 | [CLDR36.1](http://unicode.org/Public/cldr/36.1/) | [Charts36.1](http://www.unicode.org/cldr/charts/36.1/) | [LDML36](https://www.unicode.org/reports/tr35/tr35-57/tr35.html) | [Δ36.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20fixVersion%20%3D%20%2236.1%22%20ORDER%20BY%20component%20ASC%2C%20priority%20DESC%2C%20created%20ASC) | [release-36-1](https://github.com/unicode-org/cldr/tree/release-36-1) | [ΔDtd36.1](http://www.unicode.org/cldr/charts/36.1/supplemental/dtd_deltas.html) | -| 36 | 2019-10-04 | [v36](http://cldr.unicode.org/index/downloads/cldr-36) | [CLDR36](http://unicode.org/Public/cldr/36/) | [Charts36](http://www.unicode.org/cldr/charts/36/) | [LDML36](https://www.unicode.org/reports/tr35/tr35-57/tr35.html) | [Δ36](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2236%22%20ORDER%20BY%20created%20ASC) | [release-36](https://github.com/unicode-org/cldr/tree/release-36) | [ΔDtd36](http://www.unicode.org/cldr/charts/36/supplemental/dtd_deltas.html) | -| 35.1 | 2019-04-17 | [v35.1](http://cldr.unicode.org/index/downloads/cldr-35?pli=1#TOC-V35.1) | [CLDR35.1](http://unicode.org/Public/cldr/35.1/) | [Charts35.1](http://www.unicode.org/cldr/charts/35/) | [LDML35](https://www.unicode.org/reports/tr35/tr35-55/tr35.html) | [Δ35.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20fixVersion%20%3D%2035.1%20ORDER%20BY%20created%20ASC) | [release-35-1](https://github.com/unicode-org/cldr/tree/release-35-1) | [ΔDtd35](http://www.unicode.org/cldr/charts/35/supplemental/dtd_deltas.html) | -| 35 | 2019-03-27 | [v35](http://cldr.unicode.org/index/downloads/cldr-35) | [CLDR35](http://unicode.org/Public/cldr/35/) | [Charts35.1](http://www.unicode.org/cldr/charts/35/) | [LDML35](https://www.unicode.org/reports/tr35/tr35-55/tr35.html) | [Δ35](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20fixVersion%20%3D%20%2235%22%20ORDER%20BY%20created%20ASC) | [release-35](https://github.com/unicode-org/cldr/tree/release-35) | [ΔDtd35](http://www.unicode.org/cldr/charts/35/supplemental/dtd_deltas.html) | -| 34 | 2018-10-15 | [v34](http://cldr.unicode.org/index/downloads/cldr-34) | [CLDR34](http://unicode.org/Public/cldr/34/) | [Charts34](http://www.unicode.org/cldr/charts/34/) | [LDML34](http://www.unicode.org/reports/tr35/tr35-53/tr35.html) | [~~Δ34~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=34&group=component&max=999) | [release-34](http://www.unicode.org/repos/cldr/tags/release-34) | [ΔDtd34](http://www.unicode.org/cldr/charts/34/supplemental/dtd_deltas.html) | -| 33.1 | 2018-06-20 | [v33.1](http://cldr.unicode.org/index/downloads/cldr-33-1) | [CLDR33.1](http://unicode.org/Public/cldr/33.1/) | [Charts34*](http://www.unicode.org/cldr/charts/34/) | [LDML33*](http://www.unicode.org/reports/tr35/tr35-51/tr35.html) | [~~Δ33.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=33.1&group=component&max=999) | [release-33-1](http://www.unicode.org/repos/cldr/tags/release-33-1/) | [ΔDtd33](http://www.unicode.org/cldr/charts/33/supplemental/dtd_deltas.html) [*](http://unicode.org/cldr/trac/changeset?reponame=&new=HEAD@tags/release-33/common/dtd&old=HEAD@tags/release-33-1/common/dtd) | -| 33 | 2018-03-26 | [v33](http://cldr.unicode.org/index/downloads/cldr-33) | [CLDR33](http://unicode.org/Public/cldr/33/) | [Charts33](http://www.unicode.org/cldr/charts/33/) | [LDML33](http://www.unicode.org/reports/tr35/tr35-51/tr35.html) | [~~Δ33~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=33&group=component&max=999) | [release-33](http://www.unicode.org/repos/cldr/tags/release-33/) | [ΔDtd33](http://www.unicode.org/cldr/charts/33/supplemental/dtd_deltas.html) | -| 32.0.1 | 2017-12-08 | [v32](http://cldr.unicode.org/index/downloads/cldr-32) | [CLDR32.0.1](http://unicode.org/Public/cldr/32.0.1/) | [Charts32](http://www.unicode.org/cldr/charts/32/) | [LDML32](http://www.unicode.org/reports/tr35/tr35-49/tr35.html) | [~~Δ32.0.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=32.0.1&group=component&max=999) | [release-32-0-1](http://www.unicode.org/repos/cldr/tags/release-32-0-1/) | [ΔDtd32](http://www.unicode.org/cldr/charts/32/supplemental/dtd_deltas.html) | -| 32 | 2017-11-01 | [v32](http://cldr.unicode.org/index/downloads/cldr-32) | [CLDR32](http://unicode.org/Public/cldr/32/) | [Charts32](http://www.unicode.org/cldr/charts/32/) | [LDML32](http://www.unicode.org/reports/tr35/tr35-49/tr35.html) | [~~Δ32~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=32&group=component&max=999) | [release-32](http://www.unicode.org/repos/cldr/tags/release-32/) | [ΔDtd32](http://www.unicode.org/cldr/charts/32/supplemental/dtd_deltas.html) | -| 31.0.1 | 2017-04-07 | [v31](http://cldr.unicode.org/index/downloads/cldr-31) | [CLDR31.0.1](http://www.unicode.org/Public/cldr/31.0.1/) | [Charts31](http://www.unicode.org/cldr/charts/31/) | [LDML31](http://www.unicode.org/reports/tr35/tr35-47/tr35.html) | [~~Δ31.0.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=31&milestone=31.0.1&group=component&max=999&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=time&order=priority) | [release-31-0-1](http://www.unicode.org/repos/cldr/tags/release-31-0-1/) | | -| 31 | 2017-03-20 | [v31](http://cldr.unicode.org/index/downloads/cldr-31) | [CLDR31](http://unicode.org/Public/cldr/31/) | [Charts31](http://www.unicode.org/cldr/charts/31/) | [LDML31](http://www.unicode.org/reports/tr35/tr35-47/tr35.html) | [~~Δ31~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=31&group=component&max=999) | [release-31](http://www.unicode.org/repos/cldr/tags/release-31/) | | +| 36 | 2019-10-04 | [v36](/index/downloads/cldr-36) | [CLDR36](http://unicode.org/Public/cldr/36/) | [Charts36](http://www.unicode.org/cldr/charts/36/) | [LDML36](https://www.unicode.org/reports/tr35/tr35-57/tr35.html) | [Δ36](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%2236%22%20ORDER%20BY%20created%20ASC) | [release-36](https://github.com/unicode-org/cldr/tree/release-36) | [ΔDtd36](http://www.unicode.org/cldr/charts/36/supplemental/dtd_deltas.html) | +| 35.1 | 2019-04-17 | [v35.1](/index/downloads/cldr-35?pli=1#TOC-V35.1) | [CLDR35.1](http://unicode.org/Public/cldr/35.1/) | [Charts35.1](http://www.unicode.org/cldr/charts/35/) | [LDML35](https://www.unicode.org/reports/tr35/tr35-55/tr35.html) | [Δ35.1](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20fixVersion%20%3D%2035.1%20ORDER%20BY%20created%20ASC) | [release-35-1](https://github.com/unicode-org/cldr/tree/release-35-1) | [ΔDtd35](http://www.unicode.org/cldr/charts/35/supplemental/dtd_deltas.html) | +| 35 | 2019-03-27 | [v35](/index/downloads/cldr-35) | [CLDR35](http://unicode.org/Public/cldr/35/) | [Charts35.1](http://www.unicode.org/cldr/charts/35/) | [LDML35](https://www.unicode.org/reports/tr35/tr35-55/tr35.html) | [Δ35](https://unicode-org.atlassian.net/issues/?jql=project%20%3D%20CLDR%20AND%20status%20%3D%20Done%20AND%20fixVersion%20%3D%20%2235%22%20ORDER%20BY%20created%20ASC) | [release-35](https://github.com/unicode-org/cldr/tree/release-35) | [ΔDtd35](http://www.unicode.org/cldr/charts/35/supplemental/dtd_deltas.html) | +| 34 | 2018-10-15 | [v34](/index/downloads/cldr-34) | [CLDR34](http://unicode.org/Public/cldr/34/) | [Charts34](http://www.unicode.org/cldr/charts/34/) | [LDML34](http://www.unicode.org/reports/tr35/tr35-53/tr35.html) | [~~Δ34~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=34&group=component&max=999) | [release-34](http://www.unicode.org/repos/cldr/tags/release-34) | [ΔDtd34](http://www.unicode.org/cldr/charts/34/supplemental/dtd_deltas.html) | +| 33.1 | 2018-06-20 | [v33.1](/index/downloads/cldr-33-1) | [CLDR33.1](http://unicode.org/Public/cldr/33.1/) | [Charts34*](http://www.unicode.org/cldr/charts/34/) | [LDML33*](http://www.unicode.org/reports/tr35/tr35-51/tr35.html) | [~~Δ33.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=33.1&group=component&max=999) | [release-33-1](http://www.unicode.org/repos/cldr/tags/release-33-1/) | [ΔDtd33](http://www.unicode.org/cldr/charts/33/supplemental/dtd_deltas.html) [*](http://unicode.org/cldr/trac/changeset?reponame=&new=HEAD@tags/release-33/common/dtd&old=HEAD@tags/release-33-1/common/dtd) | +| 33 | 2018-03-26 | [v33](/index/downloads/cldr-33) | [CLDR33](http://unicode.org/Public/cldr/33/) | [Charts33](http://www.unicode.org/cldr/charts/33/) | [LDML33](http://www.unicode.org/reports/tr35/tr35-51/tr35.html) | [~~Δ33~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=33&group=component&max=999) | [release-33](http://www.unicode.org/repos/cldr/tags/release-33/) | [ΔDtd33](http://www.unicode.org/cldr/charts/33/supplemental/dtd_deltas.html) | +| 32.0.1 | 2017-12-08 | [v32](/index/downloads/cldr-32) | [CLDR32.0.1](http://unicode.org/Public/cldr/32.0.1/) | [Charts32](http://www.unicode.org/cldr/charts/32/) | [LDML32](http://www.unicode.org/reports/tr35/tr35-49/tr35.html) | [~~Δ32.0.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=32.0.1&group=component&max=999) | [release-32-0-1](http://www.unicode.org/repos/cldr/tags/release-32-0-1/) | [ΔDtd32](http://www.unicode.org/cldr/charts/32/supplemental/dtd_deltas.html) | +| 32 | 2017-11-01 | [v32](/index/downloads/cldr-32) | [CLDR32](http://unicode.org/Public/cldr/32/) | [Charts32](http://www.unicode.org/cldr/charts/32/) | [LDML32](http://www.unicode.org/reports/tr35/tr35-49/tr35.html) | [~~Δ32~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=32&group=component&max=999) | [release-32](http://www.unicode.org/repos/cldr/tags/release-32/) | [ΔDtd32](http://www.unicode.org/cldr/charts/32/supplemental/dtd_deltas.html) | +| 31.0.1 | 2017-04-07 | [v31](/index/downloads/cldr-31) | [CLDR31.0.1](http://www.unicode.org/Public/cldr/31.0.1/) | [Charts31](http://www.unicode.org/cldr/charts/31/) | [LDML31](http://www.unicode.org/reports/tr35/tr35-47/tr35.html) | [~~Δ31.0.1~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=31&milestone=31.0.1&group=component&max=999&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=time&order=priority) | [release-31-0-1](http://www.unicode.org/repos/cldr/tags/release-31-0-1/) | | +| 31 | 2017-03-20 | [v31](/index/downloads/cldr-31) | [CLDR31](http://unicode.org/Public/cldr/31/) | [Charts31](http://www.unicode.org/cldr/charts/31/) | [LDML31](http://www.unicode.org/reports/tr35/tr35-47/tr35.html) | [~~Δ31~~](http://unicode.org/cldr/trac/query?resolution=fixed&milestone=31&group=component&max=999) | [release-31](http://www.unicode.org/repos/cldr/tags/release-31/) | | | 30.0.3 | 2016-12-02 | v30 | [CLDR30.0.3](http://unicode.org/Public/cldr/30.0.3/) | [Charts30](http://www.unicode.org/cldr/charts/30/) | [LDML30](http://www.unicode.org/reports/tr35/tr35-45/tr35.html) | [~~Δ30.0.3~~](http://unicode.org/cldr/trac/query?status=closed&status=reviewing&revw=!&milestone=30.0.3&group=component&max=999&col=id&col=summary&order=priority) | [release-30-0-3](http://unicode.org/cldr/trac/browser/tags/release-30-0-3) | | | 30.0.2 | 2016-10-17 | v30 | [CLDR30.0.2](http://unicode.org/Public/cldr/30.0.2/) | [Charts30](http://www.unicode.org/cldr/charts/30/) | [LDML30](http://www.unicode.org/reports/tr35/tr35-45/tr35.html) | [~~Δ30.0.2~~](http://unicode.org/cldr/trac/query?status=closed&status=reviewing&revw=!&milestone=30.0.2&group=component&max=999&col=id&col=summary&order=priority) | [release-30-0-2](http://unicode.org/cldr/trac/browser/tags/release-30-0-2) | | | 30.0.1 | 2016-10-14 | v30 | [CLDR30.0.1](http://unicode.org/Public/cldr/30.0.1/) | [Charts30](http://www.unicode.org/cldr/charts/30/) | [LDML30](http://www.unicode.org/reports/tr35/tr35-45/tr35.html) | [~~Δ30.0.1~~](http://unicode.org/cldr/trac/query?status=closed&status=reviewing&revw=!&milestone=30.0.1&group=component&max=999&col=id&col=summary&order=priority) | [release-30-0-1](http://unicode.org/cldr/trac/browser/tags/release-30-0-1) | | @@ -59,7 +59,7 @@ The following table lists the files for each released version. For license infor | 21.0 | 2012-02-10 | v21 | [CLDR21](http://unicode.org/Public/cldr/21/) | | [LDML21](http://www.unicode.org/reports/tr35/tr35-23.html) | [~~Δ21~~](http://unicode.org/cldr/trac/query?status=closed&milestone=21m1&milestone=21m2&milestone=21) | [release-21](http://unicode.org/cldr/trac/browser/tags/release-21) | | | 2.0.1 | 2011-07-18 | v2.0.1 | [CLDR2.0.1](http://unicode.org/Public/cldr/2.0.1/) | | [LDML2.0.1](http://www.unicode.org/reports/tr35/tr35-21.html) | [~~Δ2.0.1~~](http://unicode.org/cldr/trac/query?status=closed&milestone=2.0.1) | [release-2-0-1](http://unicode.org/cldr/trac/browser/tags/release-2-0-1) | | | 2.0 | 2011-05-25 | v2.0 | [CLDR2.0](http://unicode.org/Public/cldr/2.0.0/) | | [LDML2.0](http://www.unicode.org/reports/tr35/tr35-19.html) | [~~Δ2.0~~](http://unicode.org/cldr/trac/query?status=closed&milestone=2.0&milestone=2.0m1&milestone=2.0m2) | [release-2-0](http://unicode.org/cldr/trac/browser/tags/release-2-0) | | -| 1.9.1 | 2011-03-11 | [v1.9.1](http://cldr.unicode.org/index/downloads/cldr-1-9-1) | [CLDR1.9.1](http://unicode.org/Public/cldr/1.9.1/) | | [LDML1.9](http://www.unicode.org/reports/tr35/tr35-17.html) | [~~Δ1.9.1~~](http://unicode.org/cldr/trac/query?status=closed&milestone=1.9.1) | release-1-9-1 | | +| 1.9.1 | 2011-03-11 | [v1.9.1](/index/downloads/cldr-1-9-1) | [CLDR1.9.1](http://unicode.org/Public/cldr/1.9.1/) | | [LDML1.9](http://www.unicode.org/reports/tr35/tr35-17.html) | [~~Δ1.9.1~~](http://unicode.org/cldr/trac/query?status=closed&milestone=1.9.1) | release-1-9-1 | | | 1.9 | 2010-12-01 | v1.9 | [CLDR1.9.0](http://unicode.org/Public/cldr/1.9.0/) | | [LDML1.9](http://www.unicode.org/reports/tr35/tr35-17.html) | [~~Δ1.9~~](http://unicode.org/cldr/trac/query?status=closed&order=priority&milestone=1.9m1&milestone=1.9m2&milestone=1.9RC) | release-1-9 | | | 1.8.1 | 2010-04-29 | v1.8.1 | [CLDR1.8.1](http://unicode.org/Public/cldr/1.8.1/) | | [LDML1.8.1](http://www.unicode.org/reports/tr35/tr35-16.html) | [~~Δ1.8.1~~](http://unicode.org/cldr/trac/query?status=closed&milestone=1.8.1p1&milestone=1.8.1p2&milestone=1.8.1&milestone=1.8.1o) | release-1-8-1 | | | 1.8.0 | 2010-03-17 | v1.8.0 | [CLDR1.8.0](http://unicode.org/Public/cldr/1.8.0/) | | [LDML1.8.0](http://www.unicode.org/reports/tr35/tr35-15.html) | [~~Δ1.8.0~~](http://unicode.org/cldr/trac/query?status=closed&milestone=1.8p1&milestone=1.8p2&milestone=1.8&milestone=1.8o) | release-1-8 | | @@ -86,11 +86,11 @@ The following table lists the files for each released version. For license infor | No. | Version Number | | Date | Release Date | | Rel. Note | A general description of the contents of the release, and any relevant notes about the release | -| Data | A set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see [Repository Organization](http://cldr.unicode.org/index/downloads#Repository_Organization)) | +| Data | A set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see [Repository Organization](/index/downloads#Repository_Organization)) | | Charts | A set of charts showing some of the data in the release. | | Spec | The version of [UTS #35: LDML](http://www.unicode.org/reports/tr35/) that corresponds to the release | | Delta Tickets | A list of all the tickets (fixes and features) in the release, which be used to get the precise corresponding file changes (Some earlier releases are not available in this way due to the JIRA migration, but all of the information is available in GitHub or JIRA.) | -| Github Tag | The files in the release, accessible via via [Repository Access](http://cldr.unicode.org/index/downloads#latest_draft_version). For more details see CLDR Releases (Downloads) | +| Github Tag | The files in the release, accessible via via [Repository Access](/index/downloads#latest_draft_version). For more details see CLDR Releases (Downloads) | | Delta DTDs | A link pointing to a charts of changes in the DTDs over time. | @@ -105,7 +105,7 @@ Access to the latest working snapshot of CLDR, and access to data collected for CLDR files are maintained in a git source code repository at https://github.com/unicode-org/cldr.git. -**Note**: On Sep 14, 2021, the main branch was renamed to 'main', please see [This Page](https://cldr.unicode.org/development/main-rename) for how to fix. +**Note**: On Sep 14, 2021, the main branch was renamed to 'main', please see [This Page](/development/main-rename) for how to fix. There are several ways to access the repository contents. diff --git a/docs/site/index/draft-schedule.md b/docs/site/index/draft-schedule.md index b1ee577de80..02571ad4576 100644 --- a/docs/site/index/draft-schedule.md +++ b/docs/site/index/draft-schedule.md @@ -4,8 +4,8 @@ title: Schedule # Schedule -Two releases are regularly scheduled each year, currently one in mid-October, and one in mid-March. +Two releases are regularly scheduled each year, currently one in mid-October, and one in mid-March. The March release is intended to be less data-intensive, and sometimes involves little or no vetting. The current release is found at [Current CLDR Dev Version](https://docs.google.com/spreadsheets/d/1N6inI5R84UoYlRwuCNPBOAP7ri4q2CmJmh8DC5g-S6c/edit?gid=1680747936#gid=1680747936). -For more information about the various phases of the release, see [Survey Tool stages](../translation/getting-started/survey-tool-phases.md) +For more information about the various phases of the release, see [Survey Tool stages](../translation/getting-started/survey-tool-phases) diff --git a/docs/site/index/json-format-data.md b/docs/site/index/json-format-data.md index 7e4b5667e6f..4736c89dd8e 100644 --- a/docs/site/index/json-format-data.md +++ b/docs/site/index/json-format-data.md @@ -14,7 +14,7 @@ In addition, we now have a conversion utility that can be used to convert LDML i The CLDR committee welcomes comments on this specification and the data itself. Our hope is that as more people realize that there is a standard format for CLDR data in JSON, it will become the best practice way to use CLDR data in the Javascript environment. -The JSON specification for CLDR data can be found [here](https://cldr.unicode.org/index/cldr-spec/cldr-json-bindings). +The JSON specification for CLDR data can be found [here](/index/cldr-spec/cldr-json-bindings). To access the CLDR 22.1 data in the JSON format, click [HERE](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Frepos%2Fcldr-aux%2Fjson%2F22.1%2F&sa=D&sntz=1&usg=AOvVaw3a81SHdsJi_Nf1zWGhF3rs) diff --git a/docs/site/index/keyboard-workgroup.md b/docs/site/index/keyboard-workgroup.md index ecea04db721..9da9d566d90 100644 --- a/docs/site/index/keyboard-workgroup.md +++ b/docs/site/index/keyboard-workgroup.md @@ -16,7 +16,7 @@ The CLDR Keyboard Subcommittee is developing a new cross-platform standard XML f **CLDR (Common Locale Data Repository)** -Computing devices have become increasingly personal and increasingly affordable to the point that they are now within reach of most people on the planet. The diverse linguistic requirements of the world's 7+ billion people do not scale to traditional models of software development. In response to this, Unicode [CLDR](https://cldr.unicode.org/) has emerged as a standards-based solution that empowers specialist and community input, as a means of balancing the needs of language communities with the technologies of major platform and service providers. +Computing devices have become increasingly personal and increasingly affordable to the point that they are now within reach of most people on the planet. The diverse linguistic requirements of the world's 7+ billion people do not scale to traditional models of software development. In response to this, Unicode [CLDR](/) has emerged as a standards-based solution that empowers specialist and community input, as a means of balancing the needs of language communities with the technologies of major platform and service providers. ![alt-text](../images/keyboard-workgroup-keyboards.jpeg) @@ -69,7 +69,7 @@ The CLDR Keyboard Subcommittee was formed and has been meeting since mid-2020. I Release -Updates to LDML (UTS#35) Part 7: Keyboards are scheduled to be released as part of [CLDR v45](https://cldr.unicode.org/index/downloads/cldr-45). +Updates to LDML (UTS#35) Part 7: Keyboards are scheduled to be released as part of [CLDR v45](/index/downloads/cldr-45). Implementations diff --git a/docs/site/index/locale-coverage.md b/docs/site/index/locale-coverage.md index ded10876d7b..ef44ec67a51 100644 --- a/docs/site/index/locale-coverage.md +++ b/docs/site/index/locale-coverage.md @@ -10,7 +10,7 @@ The following may be listed as Missing features in a Locale Coverage chart, such ### Core -These are supplied or generated from data supplied in [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales). +These are supplied or generated from data supplied in [Core Data for New Locales](/index/cldr-spec/core-data-for-new-locales). 1. ***default\_content** — required in supplied core data* 2. ***country\_data** — required in supplied core data* @@ -23,8 +23,8 @@ These are supplied or generated from data supplied in [Core Data for New Locales The following are needed at the Moderate level. *The first three should be present before submitting other moderate data* 1. ***casing** — for bicameral scripts, what is the normal casing for different kinds of fields (country names, language names, etc). Used internally in the Survey Tool.* -2. ***plurals** — the number of different plural forms, and the rules for deriving them. See [Plural Rules](https://cldr.unicode.org/index/cldr-spec/plural-rules)* and [Plurals & Units](https://cldr.unicode.org/translation/getting-started/plurals) -3. ***ordinals** — the number of different plural forms, and the rules for deriving them. See [Plural Rules](https://cldr.unicode.org/index/cldr-spec/plural-rules)* and [Plurals & Units](https://cldr.unicode.org/translation/getting-started/plurals) +2. ***plurals** — the number of different plural forms, and the rules for deriving them. See [Plural Rules](/index/cldr-spec/plural-rules)* and [Plurals & Units](/translation/getting-started/plurals) +3. ***ordinals** — the number of different plural forms, and the rules for deriving them. See [Plural Rules](/index/cldr-spec/plural-rules)* and [Plurals & Units](/translation/getting-started/plurals) 4. ***collation** — rules for the sorting order for a language.* ### Modern diff --git a/docs/site/index/process.md b/docs/site/index/process.md index 2ea6937ad01..c96ebf4156c 100644 --- a/docs/site/index/process.md +++ b/docs/site/index/process.md @@ -8,7 +8,7 @@ title: CLDR Process This document describes the Unicode CLDR Technical Committee's process for data collection, resolution, public feedback and release. -- The process is designed to be light-weight; in particular, the meetings are frequent, short, and informal. Most of the work is by email or phone, with a database recording requested changes (See [change request](http://cldr.unicode.org/index/bug-reports)). +- The process is designed to be light-weight; in particular, the meetings are frequent, short, and informal. Most of the work is by email or phone, with a database recording requested changes (See [change request](/index/bug-reports)). - When gathering data for a region and language, it is important to have multiple sources for that data to produce the most commonly used data. The initial versions of the data were based on best available sources, and updates with new and improvements are released twice a year with work by contributors inside and outside of the Unicode Consortium. - It is important to note that CLDR is a Repository, not a Registration. That is, contributors should NOT expect that their suggestions will simply be adopted into the repository; instead, it will be vetted by other contributors. - The [CLDR Survey Tool](http://www.unicode.org/cldr/survey_tool.html) is the main channel for collecting data, and bug/feature request are tracked in a database ([CLDR Bug Reports](http://www.unicode.org/cldr/filing_bug_reports.html)). @@ -32,8 +32,8 @@ The contributors of locale data are expected to be language speakers residing in There are two types of data in the repository: -- **Core data** (See [Core data for new locales](http://cldr.unicode.org/index/cldr-spec/minimaldata)): The content is collected from language experts typically with a CLDR Technical Committee member involvement, and is reviewed by the committee. This is required for a new language to be added in CLDR. See also [Exemplar Character Sources](http://www.unicode.org/cldr/filing_bug_reports.html#Exemplar_Characters). -- **Common locale data**: This is the bulk of the CLDR data and data collection occurs twice a year using the Survey tool. (See [How to Contribute](http://cldr.unicode.org/#TOC-How-to-Contribute-).) +- **Core data** (See [Core data for new locales](/index/cldr-spec/minimaldata)): The content is collected from language experts typically with a CLDR Technical Committee member involvement, and is reviewed by the committee. This is required for a new language to be added in CLDR. See also [Exemplar Character Sources](http://www.unicode.org/cldr/filing_bug_reports.html#Exemplar_Characters). +- **Common locale data**: This is the bulk of the CLDR data and data collection occurs twice a year using the Survey tool. (See [How to Contribute](/#TOC-How-to-Contribute-).) The following 4 states are used to differentiate the data contribution levels. The initial data contributions are normally marked as draft; this may be changed once the data is vetted. @@ -103,7 +103,7 @@ For each release, there is one optimal field value determined by the following: 2. If the oldStatus is better than the new draft status, then no change is made. Otherwise, the optimal value and its draft status are made part of the new release. - For example, if the new optimal value does not have the status of **approved**, and the previous release had an **approved** value (one that does not have an error and is not a fallback), then that previously-released value stays **approved** and replaces the optimal value in the following steps. -It is difficult to develop a formulation that provides for stability, yet allows people to make needed changes. The CLDR committee welcomes suggestions for tuning this mechanism. Such suggestions can be made by filing a [new ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). +It is difficult to develop a formulation that provides for stability, yet allows people to make needed changes. The CLDR committee welcomes suggestions for tuning this mechanism. Such suggestions can be made by filing a [new ticket](/index/bug-reports#TOC-Filing-a-Ticket). ## Data- Resolution @@ -171,7 +171,7 @@ Be aware that changes and updates to CLDR will only be taken in response to info ### Version Numbering -The locale data is frozen per version. Once a version is released, it is never modified. Any changes, however minor, will mean a newer version of the locale data being released. The version numbering scheme is "xy.z", where z is incremented for maintenance releases, and xy is incremented for regular semi-annual releases as defined by the [regular semi-annual schedule](http://cldr.unicode.org/index#TOC-General-Schedule-) +The locale data is frozen per version. Once a version is released, it is never modified. Any changes, however minor, will mean a newer version of the locale data being released. The version numbering scheme is "xy.z", where z is incremented for maintenance releases, and xy is incremented for regular semi-annual releases as defined by the [regular semi-annual schedule](/index#TOC-General-Schedule-) ### Release Schedule diff --git a/docs/site/index/survey-tool.md b/docs/site/index/survey-tool.md index b911d0dfc92..fd1fc772795 100644 --- a/docs/site/index/survey-tool.md +++ b/docs/site/index/survey-tool.md @@ -4,7 +4,7 @@ title: CLDR Survey Tool # CLDR Survey Tool -[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) +[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](/index/survey-tool/survey-tool-accounts) **|** [**Guide**](/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](/index/survey-tool/faq-and-known-bugs) ### Introduction @@ -20,11 +20,11 @@ For the Milestone schedule, see the navigation bar on the left. ### Accounts -You don't need an account to view data for a particular language. If you wish to propose changes or additions, you will need an account. For how to get one, see [Survey Tool Accounts](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts). If you would like to add data for a new locale, see [Adding New Locales](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#adding-new-locales). +You don't need an account to view data for a particular language. If you wish to propose changes or additions, you will need an account. For how to get one, see [Survey Tool Accounts](/index/survey-tool/survey-tool-accounts). If you would like to add data for a new locale, see [Adding New Locales](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#adding-new-locales). ### Guide -For an overview of how the Survey Tool works, see the [Survey Tool Guide](https://cldr.unicode.org/translation/getting-started/guide). +For an overview of how the Survey Tool works, see the [Survey Tool Guide](/translation/getting-started/guide). ### New Fields @@ -32,5 +32,5 @@ To see a summary of the new fields that will be in the next version of CLDR, see ### Development -For developers, see the [development pages](https://cldr.unicode.org/development/cldr-development-site). +For developers, see the [development pages](/development/cldr-development-site). diff --git a/docs/site/index/survey-tool/bulk-data-upload.md b/docs/site/index/survey-tool/bulk-data-upload.md index 9bb6fdfcd07..b9c9288f8cd 100644 --- a/docs/site/index/survey-tool/bulk-data-upload.md +++ b/docs/site/index/survey-tool/bulk-data-upload.md @@ -9,9 +9,9 @@ Here are the instructions for a bulk upload (of an XML file in LDML format) to t 1. Prepare your xml files \- one per locale. Each file must be valid XML and LDML for a single file. The file doesn't have to be "complete": it might contain only translations of territories, for example. - *(Note: There is a new option that allows you to download from the Dashboard as a spreadsheet, modify the spreadsheet, and then convert that spreadsheet into an XML.  To access this option:
In the menu, choose **Upload(Bulk Import)** and then **Convert XLSX to XML**. Follow the steps from there.)* 2. The locale must exist.  - - If not, see [Adding New Locales](https://cldr.unicode.org/index/bug-reports#New_Locales). + - If not, see [Adding New Locales](/index/bug-reports#New_Locales). 3. You must be logged in, and under an account with permission to write to it. - - If you don't have an account, see [Survey Tool Accounts](http://cldr.unicode.org/index/survey-tool/accounts). + - If you don't have an account, see [Survey Tool Accounts](/index/survey-tool/accounts). - Managers and TC Members can submit on behalf of another user. 4. Go to the menu, under the **Upload ( Bulk Import)**  section. Choose **Upload XML as your Vote**. 5. Put in your email address to submit as yourself. If you manage other users, you may put the email address associated with their survey tool account in to submit a vote as that user. @@ -24,7 +24,7 @@ Here are the instructions for a bulk upload (of an XML file in LDML format) to t 10. You will see a detailed list of the test results for the items you're submitting. - You can click on an item's path link (left hand side) to view that item in the surveytool - Any items with an error icon  will not be submitted. - - If the message is "Item is not writable in the Survey Tool. Please file a ticket." then you will need to [file a ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) instead. These can be filed in a single ticket. Include all the paths and the respective values. + - If the message is "Item is not writable in the Survey Tool. Please file a ticket." then you will need to [file a ticket](/index/bug-reports#TOC-Filing-a-Ticket) instead. These can be filed in a single ticket. Include all the paths and the respective values. 1. Press "Really Submit As My Vote" to submit all passing items as your vote, or revise the file and start back at Step 4. ### Example XML: diff --git a/docs/site/index/survey-tool/coverage.md b/docs/site/index/survey-tool/coverage.md index 539f7eda7cc..b4fbd4db060 100644 --- a/docs/site/index/survey-tool/coverage.md +++ b/docs/site/index/survey-tool/coverage.md @@ -6,7 +6,7 @@ title: Setting Default Coverage Levels ## Introduction to Coverage Level - For an introduction to coverage level, see the appropriate section in TR\#35, "[Coverage Levels](https://www.unicode.org/reports/tr35/tr35-info.html#Coverage_Levels)". -- To see how coverage level is used in the Survey Tool, see "[Advanced Features](https://cldr.unicode.org/translation/getting-started/guide#TOC-Advanced-Features)" in the Survey Tool guide +- To see how coverage level is used in the Survey Tool, see "[Advanced Features](/translation/getting-started/guide#TOC-Advanced-Features)" in the Survey Tool guide ## To set your organization's default coverage levels @@ -31,7 +31,7 @@ An organization that focuses on a small number of locales will probably want to Breton ; br ; modern Breton ; \*  ; moderate -To request a change in the default coverage for your locale, file a [new ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). +To request a change in the default coverage for your locale, file a [new ticket](/index/bug-reports#TOC-Filing-a-Ticket). As part of CLDR v35, the coverage level has been refined further. See ticket \#[11498](https://unicode-org.atlassian.net/browse/CLDR-11498) diff --git a/docs/site/index/survey-tool/faq-and-known-bugs.md b/docs/site/index/survey-tool/faq-and-known-bugs.md index 1c78b8205b8..174457098d0 100644 --- a/docs/site/index/survey-tool/faq-and-known-bugs.md +++ b/docs/site/index/survey-tool/faq-and-known-bugs.md @@ -4,13 +4,13 @@ title: FAQ and Known Bugs # FAQ and Known Bugs -[**Survey Tool**](http://st.unicode.org/cldr-apps/survey) **\|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **\|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **\|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) +[**Survey Tool**](http://st.unicode.org/cldr-apps/survey) **\|** [**Accounts**](/index/survey-tool/survey-tool-accounts) **\|** [**Guide**](/translation/getting-started/guide) **\|** [**FAQ and Known Bugs**](/index/survey-tool/faq-and-known-bugs) ## FAQ (Frequently Asked Questions) ***Q. Should I preserve the case of English words, like names of languages?*** -A. Beginning with CLDR 22, the new guidance is that names of items such as languages, regions, calendar and collation types, as well as names of months and weekdays in calendar data, should be capitalized as appropriate for the middle of body text. For more information, see the [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) section in the [Translation Guidelines](http://cldr.unicode.org/translation/). +A. Beginning with CLDR 22, the new guidance is that names of items such as languages, regions, calendar and collation types, as well as names of months and weekdays in calendar data, should be capitalized as appropriate for the middle of body text. For more information, see the [Capitalization](/translation/translation-guide-general/capitalization) section in the [Translation Guidelines](/translation/). ***Q. What about the warning about parentheses being discouraged in cases such as "(other)"*** @@ -24,7 +24,7 @@ If you feel a task is taking an unusual amount of time, and it is a consistent p ***Q. How are votes weighted and the "best" item picked?*** -A. You basically want to get multiple organizations to agree on the best value. For details on the voting process, see [Resolution Procedure](https://cldr.unicode.org/index/process). +A. You basically want to get multiple organizations to agree on the best value. For details on the voting process, see [Resolution Procedure](/index/process). ***Q. In the key, it says that the red box is a fallback. What does that mean?*** @@ -56,13 +56,13 @@ A. You should click on the items you have questions about, and read the informat *In many cases, even seemingly straightforward translations like the language, script, and territory names have issues.* -You can also go directly to the [Translation Guidelines](https://cldr.unicode.org/translation). +You can also go directly to the [Translation Guidelines](/translation). If you have further questions, or problems with the Survey Tool, send a message to [cldr\-users@unicode.org](mailto:cldr-users@unicode.org). ## Known Bugs, Issues, Restrictions -The following are general known bugs and issues. For known issues in the current release, see [Translation Guidelines](https://cldr.unicode.org/translation). +The following are general known bugs and issues. For known issues in the current release, see [Translation Guidelines](/translation). 1. The description of bulk uploading (http://cldr.unicode.org/index/survey-tool/upload) has not yet been updated for the new UI. 2. The description of managing users (http://cldr.unicode.org/index/survey-tool/managing-users) has not yet been updated for the new UI. diff --git a/docs/site/index/survey-tool/managing-users.md b/docs/site/index/survey-tool/managing-users.md index 35534e632a5..dde2fef0cdd 100644 --- a/docs/site/index/survey-tool/managing-users.md +++ b/docs/site/index/survey-tool/managing-users.md @@ -6,7 +6,7 @@ title: Managing Users If you have a TC or Manager level account, you can manage other translators (users). When data submission starts, you'll want to Lock the users who are no longer active, add new users, and send messages to your users. For the old users you'll want to resend passwords \-\- it is simplest just to do that for everyone once you've added new users. -When you create users, you give them permissions and choose which locales they are to work on. It is also important that you set your organization's coverage levels appropriately, see "[Setting your Organization's Coverage levels](https://cldr.unicode.org/index/survey-tool/coverage)". +When you create users, you give them permissions and choose which locales they are to work on. It is also important that you set your organization's coverage levels appropriately, see "[Setting your Organization's Coverage levels](/index/survey-tool/coverage)". ## Managing Users @@ -31,7 +31,7 @@ Set the name, email, and locales responsible. To see the locale codes, go to htt ![image](../../images/index/managingUsers3.jpg) Set the Userlevel based on your assessment of the person's skill. Normally this is "Vetter". You can use "Street" for volunteers whom you don't know. People don't have to come from your organization as long as you have confidence in them. -- See the [CLDR Process](https://cldr.unicode.org/index/process) page for a description of the user levels and their privileges. +- See the [CLDR Process](/index/process) page for a description of the user levels and their privileges. *Known bug: if you try to create a user when the user already has an account, you get an unknown error message. Often this is because the user is locked. Click on "Show locked users", find the person, and change the status (see below).* @@ -92,7 +92,7 @@ Later on, in the vetting phase, you can send messages with the outstanding dispu ## To check that all of your important locales have vetters assigned 1. Click the "Show Vetting Participation" link at the left, under the top gray bar. -2. The Gray locales are ones that are not a priority for your organization according to coverage information. (If that's wrong, see "[Changing Your Organization's Coverage Levels](https://cldr.unicode.org/index/survey-tool/coverage)" ) +2. The Gray locales are ones that are not a priority for your organization according to coverage information. (If that's wrong, see "[Changing Your Organization's Coverage Levels](/index/survey-tool/coverage)" ) 3. If you need new locales added, let your committee representative know. 4. To see what the participation of your vetters has been recently, click on the Participation Shown link at the top 1. Note: this has a bug currently where the table becomes very wide \-\- you'll have to scroll or expand your window. diff --git a/docs/site/index/survey-tool/survey-tool-accounts.md b/docs/site/index/survey-tool/survey-tool-accounts.md index 95c9495cd41..30d66e0ff93 100644 --- a/docs/site/index/survey-tool/survey-tool-accounts.md +++ b/docs/site/index/survey-tool/survey-tool-accounts.md @@ -4,7 +4,7 @@ title: Survey Tool Accounts # Survey Tool Accounts -[**Survey Tool**](http://st.unicode.org/cldr-apps/survey) **\|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **\|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **\|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) +[**Survey Tool**](http://st.unicode.org/cldr-apps/survey) **\|** [**Accounts**](/index/survey-tool/survey-tool-accounts) **\|** [**Guide**](/translation/getting-started/guide) **\|** [**FAQ and Known Bugs**](/index/survey-tool/faq-and-known-bugs) Anyone is welcome to try out the [**Survey Tool**](http://st.unicode.org/cldr-apps/survey), although only those with accounts will be able to make changes. To get an account, or if you have forgotten your login ID or password, please contact your CLDR TC representative. If you don't belong to a Unicode member organization, and are a native speaker of a language other than American English, you can obtain a guest account. @@ -14,7 +14,7 @@ There are three types of accounts: - Representatives belonging to Unicode member organizations in the CLDR technical committee will receive instructions from their CLDR contacts. - Representatives from other [Unicode member organizations](http://unicode.org/consortium/memblogo.html) (including [liaison members](http://unicode.org/consortium/memblogo.html#liais)) also get more weight in resolving conflicts. So if you are associated with a Unicode member organization, be sure to have that member's Unicode contact submit your name directly for an account. -- If there is an official organization for your language that would like to have liaison status for contributing data, please file a separate ticket under [CLDR Change Requests](https://cldr.unicode.org/index/bug-reports). +- If there is an official organization for your language that would like to have liaison status for contributing data, please file a separate ticket under [CLDR Change Requests](/index/bug-reports). - Other individuals can request accounts via the [Unicode contact form](http://www.unicode.org/reporting.html). In resolving conflicts, they are treated as if they all belong to a single organization ("Guest"). When you request an account, you must list all of the locale(s) that you would like to provide data for, using the locale codes on [Locales](http://unicode.org/cldr/apps/survey?p_codes=t). If the locale is not present in CLDR, you can request that it be added, and you will be expected to provide certain core data to begin the process. Please see [Adding New Locales](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#adding-new-locales) under [CLDR Change Requests](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#requesting-changes). diff --git a/docs/site/requesting_changes.md b/docs/site/requesting_changes.md index 362e996da23..147d4f0f394 100644 --- a/docs/site/requesting_changes.md +++ b/docs/site/requesting_changes.md @@ -19,8 +19,8 @@ In CLDR Bug Reports, please try to give as much information as possible to help A few areas are particularly tricky. -* For the sort order of a language, see [Collation Guidelines](https://cldr.unicode.org/index/cldr-spec/collation-guidelines) -* For plural rules (ordinals and cardinals), see [Plural Rules](https://cldr.unicode.org/index/cldr-spec/plural-rules) +* For the sort order of a language, see [Collation Guidelines](/index/cldr-spec/collation-guidelines) +* For plural rules (ordinals and cardinals), see [Plural Rules](/index/cldr-spec/plural-rules) ### Requesting updates to locale data through a ticket @@ -37,7 +37,7 @@ Helpful information include: Please file all tickets in English since the people who are reviewing your ticket are likely to not speak your language. You can use automated translation software if you don't speak English well enough, and include the same text in your native language as well. -Note: If you are a regular user of that language you can also contribute directly through the Survey Tool. [More information about the process including opening an account.](https://cldr.unicode.org/index/survey-tool) +Note: If you are a regular user of that language you can also contribute directly through the Survey Tool. [More information about the process including opening an account.](/index/survey-tool) ### How to File a Ticket @@ -46,7 +46,7 @@ The CLDR tickets are located at: https://unicode-org.atlassian.net/projects/CLDR To file a ticket, click the red "Create" button on the top navigation bar. See [Jira documentation](https://support.atlassian.com/jira-work-management/docs/create-issues-and-subtasks/) for additional details on how to create an issue. -You must have an account in order to file tickets. If you do not have an account, you can [request a Jira account](https://id.atlassian.com/signup?continue=https%3A%2F%2Funicode-org.atlassian.net%2Flogin%3FredirectCount%3D1%26dest-url%3Dhttps%253A%252F%252Funicode-org.atlassian.net%252Fprojects%252FCLDR%252Fissues&application=jira). +You must have an account in order to file tickets. If you do not have an account, you can [request a Jira account](https://id.atlassian.com/signup?continue=https%3A%2F%2Funicode-org.atlassian.net%2Flogin%3FredirectCount%3D1%26dest-url%3Dhttps%253A%252F%252Funicode-org.atlassian.net%252Fprojects%252FCLDR%252Fissues&application=jira). ## When to fix in survey tool @@ -55,8 +55,8 @@ during the regular CLDR development cycle. ## Adding New Locales -If you would like to add data for a new locale: +If you would like to add data for a new locale: -* Make sure that you pick the right locale code for the new data. See [Picking the Right Language Code](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) -* Gather the [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales). A new locale is only added if someone commits to supplying/maintaining the data. +* Make sure that you pick the right locale code for the new data. See [Picking the Right Language Code](/index/cldr-spec/picking-the-right-language-code) +* Gather the [Core Data for New Locales](/index/cldr-spec/core-data-for-new-locales). A new locale is only added if someone commits to supplying/maintaining the data. * Follow the instructions above to file a ticket, requesting the addition. Add the language code (#1) and core data (#2) in the ticket) diff --git a/docs/site/translation.md b/docs/site/translation.md index b0c32429dfa..a6a81dd5960 100644 --- a/docs/site/translation.md +++ b/docs/site/translation.md @@ -6,7 +6,7 @@ title: Information Hub for Linguists ### Starting Submission -During Submission, please read the CLDR Training (if new to the survey tool), please focus on the missing, provisional, and errors. Please read the [**Announcements and Updates**](https://cldr.unicode.org/translation#h.pfa5snbaw7ds). For more information about the priorities during Submission, see [Survey Tool stages](https://cldr.unicode.org/translation/getting-started/survey-tool-phases) under **Survey Tool phase: General Submission**. The [Submission phase](https://cldr.unicode.org/translation/getting-started/survey-tool-phases#h.wqmb27e55b4l) lasts until **June 11**; then the [Vetting phase](https://cldr.unicode.org/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) lasts until **June 30**. +During Submission, please read the CLDR Training (if new to the survey tool), please focus on the missing, provisional, and errors. Please read the [**Announcements and Updates**](/translation#h.pfa5snbaw7ds). For more information about the priorities during Submission, see [Survey Tool stages](/translation/getting-started/survey-tool-phases) under **Survey Tool phase: General Submission**. The [Submission phase](/translation/getting-started/survey-tool-phases#h.wqmb27e55b4l) lasts until **June 11**; then the [Vetting phase](/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) lasts until **June 30**. ### Prerequisites @@ -24,9 +24,9 @@ When a section below changes, the date will be in the header. ## Status and Schedule -The Survey Tool is now open for [Submission](https://cldr.unicode.org/translation/getting-started/survey-tool-phases#h.wqmb27e55b4l) until the start of [Vetting](https://cldr.unicode.org/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) on June 12th ([schedule](https://docs.google.com/spreadsheets/d/1N6inI5R84UoYlRwuCNPBOAP7ri4q2CmJmh8DC5g-S6c/edit#gid=1680747936)); then the [Vetting phase](https://cldr.unicode.org/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) lasts until **June 30**. +The Survey Tool is now open for [Submission](/translation/getting-started/survey-tool-phases#h.wqmb27e55b4l) until the start of [Vetting](/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) on June 12th ([schedule](https://docs.google.com/spreadsheets/d/1N6inI5R84UoYlRwuCNPBOAP7ri4q2CmJmh8DC5g-S6c/edit#gid=1680747936)); then the [Vetting phase](/translation/getting-started/survey-tool-phases#h.ddjb4w32ki37) lasts until **June 30**. -- **Disconnect error**. If you see a persistent Loading error with a disconnect message or other odd behavior, please [empty your cache](https://cldr.unicode.org/translation). +- **Disconnect error**. If you see a persistent Loading error with a disconnect message or other odd behavior, please [empty your cache](/translation). - Survey Tool email notification may be going to your spam folder. Check your spam folder regularly. - "**Same as code**" errors - when translating codes for items such as languages, regions, scripts, and keys, it is normally an error to select the code itself as the translated name. If the error appears under Typography, you can ignore it. \[[CLDR-13552](https://unicode-org.atlassian.net/browse/CLDR-13552)\] @@ -126,7 +126,7 @@ Once trained and up to speed on Critical reminders (above), log in to the [Surve 6. The symbols in the A column have been changed to be searchable in browsers (with *Find in Page*) and stand out -more on the page. See below for a table. They override the symbols in [Survey Tool Guide: Icons](https://cldr.unicode.org/translation/getting-started/guide#h.fbq7vldvjuz4). +more on the page. See below for a table. They override the symbols in [Survey Tool Guide: Icons](/translation/getting-started/guide#h.fbq7vldvjuz4). ### Important Notes @@ -169,41 +169,41 @@ This list will be updated as fixes are made available in Survey Tool Production. Before getting started to contribute data in CLDR, and jumping in to using the Survey Tool, it is important that you understand the CLDR process & take the CLDR training. It takes about 2-3 hours to complete the training. -1. **Understand the basics about the CLDR process** read the [Survey Tool Guide](https://cldr.unicode.org/translation/getting-started/guide) and an overview of the [Survey Tool Stages](https://cldr.unicode.org/translation/getting-started/survey-tool-phases). +1. **Understand the basics about the CLDR process** read the [Survey Tool Guide](/translation/getting-started/guide) and an overview of the [Survey Tool Stages](/translation/getting-started/survey-tool-phases). - New: A [video is available](https://www.youtube.com/watch?v=Wxs0TZl7Ljk) which shows how to login and begin contributing data for your locale. 2. **Read the Getting Started topics** on the Information Hub: - General translation guide - - [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) - - [Default Content](https://cldr.unicode.org/translation/translation-guide-general/default-content) - - [References](https://cldr.unicode.org/translation/translation-guide-general/references) - - [Handling Errors and Warnings](https://cldr.unicode.org/translation/getting-started/errors-and-warnings) - - [Handling Logical Group Errors](https://cldr.unicode.org/translation/getting-started/resolving-errors) - - [Plurals & Units](https://cldr.unicode.org/translation/getting-started/plurals) - - [Review Date & Time](https://cldr.unicode.org/translation/date-time) - - [Review Numbers](https://cldr.unicode.org/translation/number-currency-formats) - - [Review Zones](https://cldr.unicode.org/translation/time-zones-and-city-names) - - [Data stability](https://cldr.unicode.org/translation/getting-started/data-stability) - - [Empty cache](https://cldr.unicode.org/translation/getting-started/empty-cache) - -\*If you (individual or your organization) have not established a connection with the CLDR technical committee, start with [Survey Tool Accounts](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts). + - [Capitalization](/translation/translation-guide-general/capitalization) + - [Default Content](/translation/translation-guide-general/default-content) + - [References](/translation/translation-guide-general/references) + - [Handling Errors and Warnings](/translation/getting-started/errors-and-warnings) + - [Handling Logical Group Errors](/translation/getting-started/resolving-errors) + - [Plurals & Units](/translation/getting-started/plurals) + - [Review Date & Time](/translation/date-time) + - [Review Numbers](/translation/number-currency-formats) + - [Review Zones](/translation/time-zones-and-city-names) + - [Data stability](/translation/getting-started/data-stability) + - [Empty cache](/translation/getting-started/empty-cache) + +\*If you (individual or your organization) have not established a connection with the CLDR technical committee, start with [Survey Tool Accounts](/index/survey-tool/survey-tool-accounts). ## Critical reminders (for all linguists) You're already familiar with the CLDR process, but do keep the following in mind: 1. **Aim at commonly used language** - CLDR should reflect *common-usage* standards **not** *academic /official* standards (unless commonly followed). Keep that perspective in mind. -2. **Carefully consider changes to existing standards** - any change to an existing CLDR standard should be carefully considered and discussed with your fellow linguists in the CLDR [Forum](https://cldr.unicode.org/translation/getting-started/guide#h.fx4wl2fl31az). Remember your change will be reflected across thousands of online products! +2. **Carefully consider changes to existing standards** - any change to an existing CLDR standard should be carefully considered and discussed with your fellow linguists in the CLDR [Forum](/translation/getting-started/guide#h.fx4wl2fl31az). Remember your change will be reflected across thousands of online products! 3. **Keep consistency across logical groups** - ensure that all related entries are consistent. If you change the name of a weekday, make sure it's reflected across all related items. Check that the order of month and day are consistent in all the date formats, etc. - - *Tip: The [Reports](https://cldr.unicode.org/translation/getting-started/review-formats) are a great way to validate consistency across related logical groups, e.g. translations of date formats. Use them to proofread your work for consistency.* + - *Tip: The [Reports](/translation/getting-started/review-formats) are a great way to validate consistency across related logical groups, e.g. translations of date formats. Use them to proofread your work for consistency.* 4. **Avoid voting for English** - for items that do not work in your language, don't simply use English. Find a solution that works for your language. For example, if your language doesn't have a concept of calendar "quarters", use a translation that describes the concept "three-month period" rather than "quarter-of-a-year". 5. **Watch out for complex sections** and read the instructions carefully if in doubt: - 1. [Date & Time](https://cldr.unicode.org/translation/date-time/date-time-names) - - [Names](https://cldr.unicode.org/translation/date-time/date-time-names) - - [Patterns](https://cldr.unicode.org/translation/date-time) - - [Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols) - 2. [Time zones](https://cldr.unicode.org/translation/time-zones-and-city-names) - 3. [Plural forms](https://cldr.unicode.org/translation/getting-started/plurals) + 1. [Date & Time](/translation/date-time/date-time-names) + - [Names](/translation/date-time/date-time-names) + - [Patterns](/translation/date-time) + - [Symbols](/translation/date-time/date-time-symbols) + 2. [Time zones](/translation/time-zones-and-city-names) + 3. [Plural forms](/translation/getting-started/plurals) -*Tip: The links in the [Info Panel](https://cldr.unicode.org/translation/getting-started/guide#h.2jch1980f8sy) will point you to relevant instructions for the entry you're editing/vetting. Use it if in doubt.* +*Tip: The links in the [Info Panel](/translation/getting-started/guide#h.2jch1980f8sy) will point you to relevant instructions for the entry you're editing/vetting. Use it if in doubt.* diff --git a/docs/site/translation/characters.md b/docs/site/translation/characters.md index 20714b589c1..31d0b974254 100644 --- a/docs/site/translation/characters.md +++ b/docs/site/translation/characters.md @@ -6,7 +6,7 @@ title: Characters Characters category in the Survey tool include data that surrounds support for Emoji, Symbols, and Typography names. -- [Character Labels](https://cldr.unicode.org/translation/characters/character-labels) -- [Emoji Names and Keywords](https://cldr.unicode.org/translation/characters/short-names-and-keywords) -- [Typographic Names](https://cldr.unicode.org/translation/characters/typographic-names) +- [Character Labels](/translation/characters/character-labels) +- [Emoji Names and Keywords](/translation/characters/short-names-and-keywords) +- [Typographic Names](/translation/characters/typographic-names) diff --git a/docs/site/translation/characters/short-names-and-keywords.md b/docs/site/translation/characters/short-names-and-keywords.md index 6192a0acbfb..dc2629faf60 100644 --- a/docs/site/translation/characters/short-names-and-keywords.md +++ b/docs/site/translation/characters/short-names-and-keywords.md @@ -71,7 +71,7 @@ Many of the emoji names are constructed, which means that in implementations emo - For the Character > Categories > Label (such as [French](https://st.unicode.org/cldr-apps/v#/fr/Category/19624f4413eaac8b)), whether or not a label is plural will depend on the label and the language. The pluralization choice will not necessarily follow the English. ## Short Character Names -In CLDR we provide descriptive but short names for the characters across languages. (For reference, see [Background: Unicode Std. vs CLDR names](https://cldr.unicode.org/translation/characters-emoji-symbols/short-names-and-keywords%23TOC-Background:-Unicode-Std.-vs-CLDR-names).) +In CLDR we provide descriptive but short names for the characters across languages. (For reference, see [Background: Unicode Std. vs CLDR names](/translation/characters-emoji-symbols/short-names-and-keywords%23TOC-Background:-Unicode-Std.-vs-CLDR-names).) Goals for the short names collected in CLDR are: @@ -82,12 +82,12 @@ Goals for the short names collected in CLDR are: | **Descriptive** | Be descriptive of the prevailing color images. Don't be "over-descriptive", however. The descriptions only have to be enough to distinguish each image from the others: they shouldn't have any details beyond that. | | **Consistent** | Be consistent across images with similar features. (Don’t call 📫 a _mailbox_ and 📬 a _post box_). | | **Flexible** | It is **not a goal** to be immutable: in future versions of CLDR, you can improve names by casing new suggestions if a more appropriate names are available. | -| **Not Literal** | Names should **not just be literal translations** of the English-- the names should be based on associations to the image _in your language._ But you can be _informed_ by the English names. (Exceptions to this when there is no equivalent in your language. See [Emoji specific to a country/region](https://cldr.unicode.org/translation/characters-emoji-symbols/short-names-and-keywords#TOC-FAQ-Tips-for-character-names-and-keywords)) | +| **Not Literal** | Names should **not just be literal translations** of the English-- the names should be based on associations to the image _in your language._ But you can be _informed_ by the English names. (Exceptions to this when there is no equivalent in your language. See [Emoji specific to a country/region](/translation/characters-emoji-symbols/short-names-and-keywords#TOC-FAQ-Tips-for-character-names-and-keywords)) | When voting on the emoji names and keywords: -- Follow the middle of sentence rule. See [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) guideline. -- As usual, the names in “en” are American English; where necessary those are customized for “en-GB”. For differences for sub-locale, see [Regional Variant](https://cldr.unicode.org/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-) guideline. +- Follow the middle of sentence rule. See [Capitalization](/translation/translation-guide-general/capitalization) guideline. +- As usual, the names in “en” are American English; where necessary those are customized for “en-GB”. For differences for sub-locale, see [Regional Variant](/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-) guideline. ### Unique Names diff --git a/docs/site/translation/characters/typographic-names.md b/docs/site/translation/characters/typographic-names.md index adfdf738171..17dbe97976c 100644 --- a/docs/site/translation/characters/typographic-names.md +++ b/docs/site/translation/characters/typographic-names.md @@ -21,11 +21,11 @@ The most common problem is giving the same name to two *different* fields. For e **Slant vs Italic** -1. Slant is different than italic: in the latter, the characters are slanted, but also usually different shapes. See [Italic](http://cldr.unicode.org/translation/characters-emoji-symbols/typographic-names/italic.png). +1. Slant is different than italic: in the latter, the characters are slanted, but also usually different shapes. See [Italic](/translation/characters-emoji-symbols/typographic-names/italic.png). **Width vs Weight** -1. The wdth-100 and wght-400 (which are *normal* and *regular* in English) must have different names: *normal* is width (how wide the character is — see [Width](http://cldr.unicode.org/translation/characters-emoji-symbols/typographic-names/optical-size.png)), and *regular* is boldness (how heavy the lines in the character are — see [Weight](http://cldr.unicode.org/translation/characters-emoji-symbols/typographic-names/font-weight-2.png)). If there is not a distinction in your language, you can qualify, eg *normal-width* +1. The wdth-100 and wght-400 (which are *normal* and *regular* in English) must have different names: *normal* is width (how wide the character is — see [Width](/translation/characters-emoji-symbols/typographic-names/optical-size.png)), and *regular* is boldness (how heavy the lines in the character are — see [Weight](/translation/characters-emoji-symbols/typographic-names/font-weight-2.png)). If there is not a distinction in your language, you can qualify, eg *normal-width* 2. Similarly wdth-125 and wght-700 (in English: *wide* and *bold*) need to be different (width vs boldness) 3. However, only the first two parts of the code make a difference (up to and including the number). The last part (after the number) is purely optional. You only need to have different names for the optional ones if your language really has alternative names for the same feature. That means that you can give the same names to each of the following: - wdth-50 diff --git a/docs/site/translation/core-data.md b/docs/site/translation/core-data.md index ff5cd0e3998..cf69cceba75 100644 --- a/docs/site/translation/core-data.md +++ b/docs/site/translation/core-data.md @@ -6,7 +6,7 @@ title: Core Data These pages describe certain core data needed by CLDR. -- [Alphabetic Information](https://cldr.unicode.org/translation/core-data/characters) -- [Exemplar Characters](https://cldr.unicode.org/translation/core-data/exemplars) -- [Numbering Systems](https://cldr.unicode.org/translation/core-data/numbering-systems) +- [Alphabetic Information](/translation/core-data/characters) +- [Exemplar Characters](/translation/core-data/exemplars) +- [Numbering Systems](/translation/core-data/numbering-systems) diff --git a/docs/site/translation/core-data/characters.md b/docs/site/translation/core-data/characters.md index 71f8e824fad..de536877d1b 100644 --- a/docs/site/translation/core-data/characters.md +++ b/docs/site/translation/core-data/characters.md @@ -63,7 +63,7 @@ Currently the CLDR survey tool checks input delimiters against a predefined set ‘ U+2018 LEFT SINGLE QUOTATION MARK ’ U+2019 RIGHT SINGLE QUOTATION MARK ‚ U+201A SINGLE LOW-9 QUOTATION MARK “ U+201C LEFT DOUBLE QUOTATION MARK ” U+201D RIGHT DOUBLE QUOTATION MARK „ U+201E DOUBLE LOW-9 QUOTATION MARK 「 U+300C LEFT CORNER BRACKET 」 U+300D RIGHT CORNER BRACKET 『 U+300E LEFT WHITE CORNER BRACKET 』 U+300F RIGHT WHITE CORNER BRACKET ‹ U+2039 SINGLE LEFT-POINTING ANGLE QUOTATION MARK › U+203A SINGLE RIGHT-POINTING ANGLE QUOTATION MARK « U+00AB LEFT-POINTING DOUBLE ANGLE QUOTATION MARK » U+00BB RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK -If you need to enter a delimiter that is not one of the characters on this list, please file a new ticket by following [these instructions](https://cldr.unicode.org/index/bug-reports). +If you need to enter a delimiter that is not one of the characters on this list, please file a new ticket by following [these instructions](/index/bug-reports). ## Yes/No diff --git a/docs/site/translation/core-data/exemplars.md b/docs/site/translation/core-data/exemplars.md index 0348425e645..3e8820cbeed 100644 --- a/docs/site/translation/core-data/exemplars.md +++ b/docs/site/translation/core-data/exemplars.md @@ -110,7 +110,7 @@ Three possible solutions: 2. For currencies, if the character is part of a 'gloss', that is, it is parenthetically included for reference, and the gloss is all ASCII, then include it in brackets. You can use [square brackets] or (parentheses) in currencies. Everywhere else, please use only square brackets. - So the XAF above can be fixed by changing it to "Φράγκο [BEAC CFA]" or "Φράγκο (BEAC CFA)". For the timezone name "ACT (Ακρ)", the fix is to change to "Ακρ [ACT]". 3. If neither of these approaches is appropriate, try rephrasing the translated item to avoid the character. -4. If it really can't be avoided, then please file a [new ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) describing the problem. +4. If it really can't be avoided, then please file a [new ticket](/index/bug-reports#TOC-Filing-a-Ticket) describing the problem. **B. The exemplar characters shouldn't contain a particular character.** diff --git a/docs/site/translation/currency-names-and-symbols.md b/docs/site/translation/currency-names-and-symbols.md index a6d6fca5cd4..dfebcd564ca 100644 --- a/docs/site/translation/currency-names-and-symbols.md +++ b/docs/site/translation/currency-names-and-symbols.md @@ -25,7 +25,7 @@ Guidelines: ## Symbols -The following general guidelines are used for currency symbols. These guidelines are also subject to the CLDR [Currency Process](https://cldr.unicode.org/index/cldr-spec/currency-process). +The following general guidelines are used for currency symbols. These guidelines are also subject to the CLDR [Currency Process](/index/cldr-spec/currency-process). 1. If a symbol is not widely recognized around the world (eg shekel ₪) 1. Where the currency is official in a country, use that symbol in locales with that country (eg IL) diff --git a/docs/site/translation/currency-names-and-symbols/currency-names.md b/docs/site/translation/currency-names-and-symbols/currency-names.md index 439ba8afc12..7ef7c8f43ba 100644 --- a/docs/site/translation/currency-names-and-symbols/currency-names.md +++ b/docs/site/translation/currency-names-and-symbols/currency-names.md @@ -4,7 +4,7 @@ title: Currency Symbols # Currency Symbols -Each currency code such as USD or EUR can be represented in several ways, as given in the table below. Be sure to look at the international symbol to see which currency is being translated. For example, the English examples below are for USD. The Symbol and International code will be used in number patterns, as shown in the Examples of Usage. For more information, see [Number Patterns](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns). +Each currency code such as USD or EUR can be represented in several ways, as given in the table below. Be sure to look at the international symbol to see which currency is being translated. For example, the English examples below are for USD. The Symbol and International code will be used in number patterns, as shown in the Examples of Usage. For more information, see [Number Patterns](/translation/number-currency-formats/number-and-currency-patterns). | Type | Code | Example | Examples of Usage | Meaning | |---|---|---|---|---| @@ -14,7 +14,7 @@ Each currency code such as USD or EUR can be represented in several ways, as giv | International Code | USD | n/a | **USD** 12,345.68 | International symbol used in formatting currency amounts. Normally, this is not under translator control, so you won't even see these presented for translation, but they can be specified by the programmer. | | International Code | EUR | n/a | **EUR** 12,345.68 | ... | | Name | USD | **US Dollar** | **Dollar des États-Unis** | Descriptive name of the currency. It should be the most neutral grammatical form for your language, appropriate for menus. Typically this is nominative singular, but the conventions may be different for your language.
To provide greatest flexibility, this should use capitalization appropriate for the **middle of a sentence** . CLDR has separate contextTransforms data to specify how this should be programmatically capitalized (if at all) for different contexts such as use in menus, stand-alone use (e.g. a web page title), etc. | -| Plural forms (e.g. name-other, name-one, name-few, ...) | USD | 1 **US dollar** vs 2 **US dollars** | 1 **US dollar** vs 2 **US dollars** | Use the plural fields such as name-other and possibly name-one, name-few, etc. to indicate the different plural form(s) if plural forms are used in your language. If they are not used, typically only the name-other plural form will be shown. Follow the general [capitalization guidance](https://cldr.unicode.org/translation/translation-guide-general/capitalization) . Also see Plurals for general information on plural handling in CLDR. | +| Plural forms (e.g. name-other, name-one, name-few, ...) | USD | 1 **US dollar** vs 2 **US dollars** | 1 **US dollar** vs 2 **US dollars** | Use the plural fields such as name-other and possibly name-one, name-few, etc. to indicate the different plural form(s) if plural forms are used in your language. If they are not used, typically only the name-other plural form will be shown. Follow the general [capitalization guidance](/translation/translation-guide-general/capitalization) . Also see Plurals for general information on plural handling in CLDR. | Note: in some cases, the English currency symbol may appear as box, typically because you don't have fonts for all of the characters. This is especially the case for currency symbols recently added to Unicode, such as the following: diff --git a/docs/site/translation/date-time.md b/docs/site/translation/date-time.md index 1acb75c72e9..b1bd2098d01 100644 --- a/docs/site/translation/date-time.md +++ b/docs/site/translation/date-time.md @@ -4,8 +4,8 @@ title: Date & Time # Date & Time -- [Date & Time terminology](https://cldr.unicode.org/translation/date-time/date-times-terminology) -- [Date/Time Names](https://cldr.unicode.org/translation/date-time/date-time-names) -- [Date/Time Patterns](https://cldr.unicode.org/translation/date-time/date-time-patterns) -- [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols) +- [Date & Time terminology](/translation/date-time/date-times-terminology) +- [Date/Time Names](/translation/date-time/date-time-names) +- [Date/Time Patterns](/translation/date-time/date-time-patterns) +- [Date/Time Symbols](/translation/date-time/date-time-symbols) diff --git a/docs/site/translation/date-time/date-time-names.md b/docs/site/translation/date-time/date-time-names.md index eb06e802c2e..69adb831b16 100644 --- a/docs/site/translation/date-time/date-time-names.md +++ b/docs/site/translation/date-time/date-time-names.md @@ -4,7 +4,7 @@ title: Date/Time Names # Date/Time Names -Date/Time names is required topic to work in [Date/Time Patterns](https://cldr.unicode.org/translation/date-time/date-time-patterns). +Date/Time names is required topic to work in [Date/Time Patterns](/translation/date-time/date-time-patterns). ## Textual Fields @@ -14,12 +14,12 @@ Certain calendar fields can have both numeric and textual forms. **Textual forms - Wide (e.g. Sunday) - Abbreviated (e.g Sun) - Narrow (e.g. S) - - There are two styles. For more information, see [When to use standalone vs. formatting](https://cldr.unicode.org/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. + - There are two styles. For more information, see [When to use standalone vs. formatting](/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. - Formatting - Standalone -- Capitalization should follow the middle of a sentence rule. For more information, see [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization).   +- Capitalization should follow the middle of a sentence rule. For more information, see [Capitalization](/translation/translation-guide-general/capitalization).   - \ data can specify the capitalization for other contexts; currently this is not available in the Survey Tool, so you must file a CLDR JIRA ticket to request a change. - - Most sets of names form [Logical Groups](https://cldr.unicode.org/translation/getting-started/resolving-errors), and you need to make sure they have the same contribution status (e.g. Status: Approved) or you will get error messages. See [Logical Groups](https://cldr.unicode.org/translation/getting-started/resolving-errors) for more information. + - Most sets of names form [Logical Groups](/translation/getting-started/resolving-errors), and you need to make sure they have the same contribution status (e.g. Status: Approved) or you will get error messages. See [Logical Groups](/translation/getting-started/resolving-errors) for more information. ## Date Field Names @@ -31,7 +31,7 @@ The date field _names_ are used in user interfaces on computer systems as labels | Month | ... | | Day | ... | -The grammatical form should be whatever is typical for such isolated or stand-alone cases: generally it will be nominative singular. The letter casing should be appropriate for middle-of-sentence use, since there is now separate capitalization context data that can specify how these should be capitalized for use in a label. Also see the translation guide on [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization).  +The grammatical form should be whatever is typical for such isolated or stand-alone cases: generally it will be nominative singular. The letter casing should be appropriate for middle-of-sentence use, since there is now separate capitalization context data that can specify how these should be capitalized for use in a label. Also see the translation guide on [Capitalization](/translation/translation-guide-general/capitalization).  There are three lengths: full, short, and narrow. They are listed below along with English examples and explanations (a few of the fields are not straightforward). @@ -60,7 +60,7 @@ Era names are in Gregorian Calendar and other calendars: - There are only two values for an era in a Gregorian calendar. - The common use of these era names in English are more for religious forms. "BC" (Before Christ) and AD (Anno Domini)" - from the Latin for "The year of our Lord". - The secular equivalents of these two era names are "BCE" (Before Common Era) and "CE" (Common Era). -- Other calendars (see [Different calendars in Date/Time patterns](https://cldr.unicode.org/translation/date-time-1/date-time-patterns#TOC-Different-Calendars-)) have a different numbers of eras. +- Other calendars (see [Different calendars in Date/Time patterns](/translation/date-time-1/date-time-patterns#TOC-Different-Calendars-)) have a different numbers of eras. - The names for eras are often specific to the given calendar, such as the Japanese era names. - If other calendars are in common use in one of the countries/regions that use your language, other calendars will show under the modern coverage level. @@ -77,7 +77,7 @@ In the Gregorian calendar, these designate the four three-month periods often us This field is one of the months of the year, such as January or February.  - In many languages, it is not common to use abbreviated months. The preferred way to address this is using date/time patterns that never use the abbreviated months MMM or LLL, as explained in [Patterns without abbreviated months](https://cldr.unicode.org/translation/date-time/date-time-patterns).  + In many languages, it is not common to use abbreviated months. The preferred way to address this is using date/time patterns that never use the abbreviated months MMM or LLL, as explained in [Patterns without abbreviated months](/translation/date-time/date-time-patterns).  💡 **Translation Tips** @@ -86,7 +86,7 @@ This field is one of the months of the year, such as January or February.  - Used in patterns with a day number. (e.g. Finnish, and many Slavic languages distinguish between nominative and genitive/related) - Use the type such as the nominative case for **Standalone** month names. - Used in pattern without a day number. -- The specific values that are used in the format and stand-alone names need to be closely co-ordinated with the date patterns that will use them. See [When to use standalone vs. format names](https://cldr.unicode.org/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. +- The specific values that are used in the format and stand-alone names need to be closely co-ordinated with the date patterns that will use them. See [When to use standalone vs. format names](/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. - Some languages (for example, Catalan) use a preposition to combine the month and day number like in the format “11 de setembre” (11 of September). If the month name begins with a vowel, the preposition is contracted, for example, “12 d’octubre - Include the preposition in its correct form (contracted or not) for formatting month names - DO NOT include the preposition for standalone month names and in patterns that use standalone month names @@ -95,7 +95,7 @@ This field is one of the months of the year, such as January or February.  This field is one of the days of the week: Monday, Tuesday, Wednesday, etc... -Same as month names, you need to use different symbols to coordinate use of standalone (e.g. cccc) and format names (e.g. EEEE) in patterns. See [When to use standalone vs. format names](https://cldr.unicode.org/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. +Same as month names, you need to use different symbols to coordinate use of standalone (e.g. cccc) and format names (e.g. EEEE) in patterns. See [When to use standalone vs. format names](/translation/date-time-1/date-time-patterns#TOC-When-to-use-Standalone-vs.-Formatting) in Date/Time patterns. 💡 **Translation Tips** @@ -107,7 +107,7 @@ Same as month names, you need to use different symbols to coordinate use of stan AM/PM (special handling for locales using 24 hrs) -Also see [Additional Date/time formats](https://cldr.unicode.org/translation/date-time-1/date-time-patterns#TOC-Additional-Date-Time-Formats).  +Also see [Additional Date/time formats](/translation/date-time-1/date-time-patterns#TOC-Additional-Date-Time-Formats).  💡 **Translation Tips** @@ -169,7 +169,7 @@ In formatting, where your language has a term for midnight, it is used instead o These mark approximate periods in the day, _and those periods differ between languages_. The codes are arbitrary, and don't have to match the English meaning for your language: the important feature is the time span. The spans are approximate; in reality they may vary with the time of year (they might be dependent on sunrise), or context (someone might say they went to bed at 2 at night, and later one say that they woke up at 2 in the morning).  -**For a list of the day period IDs defined in CLDR for your language, see [Day Periods](https://www.unicode.org/cldr/charts/45/supplemental/day_periods.html)**. If you think the rules are wrong (or missing) for your language, please [file a ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) and supply the missing information. Here are examples for English and Chinese. +**For a list of the day period IDs defined in CLDR for your language, see [Day Periods](https://www.unicode.org/cldr/charts/45/supplemental/day_periods.html)**. If you think the rules are wrong (or missing) for your language, please [file a ticket](/index/bug-reports#TOC-Filing-a-Ticket) and supply the missing information. Here are examples for English and Chinese. | Code | English | Span | Chinese | Span | |---|---|---|---|---| @@ -234,7 +234,7 @@ These relative names can be programmatically capitalized (using the contextTrans 💡 **Translation Tips** -- There is a difference between unit patterns (_see [Plurals](https://cldr.unicode.org/translation/getting-started/plurals)_) such as "1 year ago" and relative names such as "Last Year". +- There is a difference between unit patterns (_see [Plurals](/translation/getting-started/plurals)_) such as "1 year ago" and relative names such as "Last Year". - Consider: - The phrase "1 year ago" has more of sense of a _duration_. - The phrase "last year" is more sense of relativity to current (For example, on January 2nd, 2019, to refer to an event on December 30th, 2018, you would refer to it as "last year", but NOT "1 year ago." @@ -244,7 +244,7 @@ These relative names can be programmatically capitalized (using the contextTrans ### Week of -There are a number of patterns like “the week of {0}” used for constructions such as “the week of April 11, 2016” or “the week of April 11–15”. The placeholder can be a full or partial date. There are related week-of date pattern that it should be as consistent with as possible, described [here](https://cldr.unicode.org/translation/date-time/date-time-patterns). +There are a number of patterns like “the week of {0}” used for constructions such as “the week of April 11, 2016” or “the week of April 11–15”. The placeholder can be a full or partial date. There are related week-of date pattern that it should be as consistent with as possible, described [here](/translation/date-time/date-time-patterns). \'week' W 'of' MMM\ diff --git a/docs/site/translation/date-time/date-time-patterns.md b/docs/site/translation/date-time/date-time-patterns.md index 7c87bfc2766..7028b5abaf3 100644 --- a/docs/site/translation/date-time/date-time-patterns.md +++ b/docs/site/translation/date-time/date-time-patterns.md @@ -10,8 +10,8 @@ _Last updated: 2018-May-14_ Pre-requisite topics to read: -- [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols) -- [Date/Time Names](https://cldr.unicode.org/translation/date-time/date-time-names) +- [Date/Time Symbols](/translation/date-time/date-time-symbols) +- [Date/Time Names](/translation/date-time/date-time-names) A date-time pattern is a string of characters in which fields representing date and time symbols are combined together with necessary "literal" strings that are used as is. @@ -26,7 +26,7 @@ There are two types of substrings that are combined in a pattern: | **yMMMd** | MMM e, y | Dec 5, 2010 | y年M月d 日 | 2010年12月5日 | There are three aspects to patterns:  -- A letter in the set {a-z; A-Z} indicates the type of calendar field: See [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols). +- A letter in the set {a-z; A-Z} indicates the type of calendar field: See [Date/Time Symbols](/translation/date-time/date-time-symbols). - For example: - M for month - d for week day @@ -37,12 +37,12 @@ There are three aspects to patterns:  - Abbreviated form: MMM  for Sep - Full form: MMMM for September - Narrow form: MMMMM (S) -- When formatting a particular date, non-numeric values (e.g. month names from Gregorian calendar) are substituted into the appropriate pattern substrings using the [Date Format Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols).  +- When formatting a particular date, non-numeric values (e.g. month names from Gregorian calendar) are substituted into the appropriate pattern substrings using the [Date Format Symbols](/translation/date-time/date-time-symbols).  - For example: - M replaced by “3” for March - MMMM replaced by “March”. - When parsing a date string, the pattern substrings will be converted into the appropriate numeric calendar data. - - **See [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols) for a brief summary of letters for different calendar fields, or [Date Field Symbol Table](http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) for a more complete and detailed list.** + - **See [Date/Time Symbols](/translation/date-time/date-time-symbols) for a brief summary of letters for different calendar fields, or [Date Field Symbol Table](http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table) for a more complete and detailed list.** - The "literal" text in the date-time pattern are used as-is when formatting, and are expected when parsing a date string. To include a single straight quote as part of the literal text, use two of them together: '' (either inside or outside a section of literal text enclosed in single straight quotes). To demonstrate how this work with examples, see the spec [Date Format Pattern Examples](http://www.unicode.org/reports/tr35/tr35-45/tr35-dates.html#Date_Format_Pattern_Examples). @@ -58,7 +58,7 @@ To demonstrate how this work with examples, see the spec [Date Format Pattern Ex ## Synchronizing Date/Time Names and Patterns -There is a tight coupling between the date/time patterns and the names that are used for date/time elements, described in [Date/Time Names](https://cldr.unicode.org/translation/date-time/date-time-names). Therefore, when supplying the data, it requires coordination between what you supply as the names and your intention on which name to use in patterns. +There is a tight coupling between the date/time patterns and the names that are used for date/time elements, described in [Date/Time Names](/translation/date-time/date-time-names). Therefore, when supplying the data, it requires coordination between what you supply as the names and your intention on which name to use in patterns. ### When to use Standalone vs. Formatting @@ -103,7 +103,7 @@ Following are examples of differences and implications based on language: 💡 **Translation Tips** - When working with patterns, look at the examples in the right information pane to validate your intention between the name and the pattern. -- In order to get the right formats for your language, you may need to change the ordering of the [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols), and change the text around them. +- In order to get the right formats for your language, you may need to change the ordering of the [Date/Time Symbols](/translation/date-time/date-time-symbols), and change the text around them. - You must match the names that should be used in patterns with intended forms of the names (wide or full, abbreviated and/or short, narrow forms)  - For example: - If you specify the time format "h:mm a", by using "a" your intention is to use the **Abbreviated formatting** name for AM/PM; thus, the end result being 2:37 PM. @@ -136,7 +136,7 @@ Using 24 hour vs 12 hour symbols: The symbols you use in time format patterns de - **k** to mean a 24-hour clock cycle running 1 through 24 (midnight plus 1 minute is 24:01). - **a**, **b**, and **B** are same as usage in 12 hour formats, but are not normally used with 24-hour time. -If a non-default country/region use a different time format than the default country/region for the language, then this difference should be added for the sub-locale. Also see [Regional variants](https://cldr.unicode.org/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-).  +If a non-default country/region use a different time format than the default country/region for the language, then this difference should be added for the sub-locale. Also see [Regional variants](/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-).  For example, if es (= es\_ES, Spanish as used in Spain) uses 24-hour time formats, but es\_US (Spanish as used in United States) uses 12 hour time formats, then es would use "HH:mm/H:mm" and es\_US would use the "h" formats as described above. . @@ -146,7 +146,7 @@ For example, if es (= es\_ES, Spanish as used in Spain) uses 24-hour time format ## Basic Date Formats -The standard Date formats include four basic formats. See Survey Tool [Formats-Standard-Date formats](https://st.unicode.org/cldr-apps/v#/USER/Gregorian/562f98c4c6b2e321). (Note that the Month symbol especially may vary (M vs MM, or MMM vs LLL). For more information, see [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols).) +The standard Date formats include four basic formats. See Survey Tool [Formats-Standard-Date formats](https://st.unicode.org/cldr-apps/v#/USER/Gregorian/562f98c4c6b2e321). (Note that the Month symbol especially may vary (M vs MM, or MMM vs LLL). For more information, see [Date/Time Symbols](/translation/date-time/date-time-symbols).) | Form | Include | English pattern examples | |---|---|---| @@ -157,7 +157,7 @@ The standard Date formats include four basic formats. See Survey Tool [Formats-S ## Additional Date-Time Formats -The basic formats as described in above sections provide a small subset of the combinations. To expand to fully cover all variations of date and time formats, a skeleton format is provided that uses the [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols) (without order or punctuation) to indicate what fields are desired.  +The basic formats as described in above sections provide a small subset of the combinations. To expand to fully cover all variations of date and time formats, a skeleton format is provided that uses the [Date/Time Symbols](/translation/date-time/date-time-symbols) (without order or punctuation) to indicate what fields are desired.  An example usage of the flexible formats would be: a software program only needs the year and month information, the flexible pattern yMMM would be used to provide the desired year and month formatting as shown in the English and Japanese examples in this table.  @@ -187,7 +187,7 @@ In languages that distinguish between nominative and genitive (or related form s - Use symbols "ccc" or "cccc" in patterns to use the standalone name - Use the symbol  "E" or "EEEE" to use the format name -To understand which pattern characters are used for standalone forms (nominative) versus format forms (genitive or related, such as partitive), see [Stand-Alone vs Format Styles](https://cldr.unicode.org/translation/date-time/date-time-symbols), see also the discussion above in [Synchronizing Date/Time Names and Patterns](https://cldr.unicode.org/translation/date-time/date-time-patterns). +To understand which pattern characters are used for standalone forms (nominative) versus format forms (genitive or related, such as partitive), see [Stand-Alone vs Format Styles](/translation/date-time/date-time-symbols), see also the discussion above in [Synchronizing Date/Time Names and Patterns](/translation/date-time/date-time-patterns). ### Supplied vs. Inferred patterns @@ -269,7 +269,7 @@ These new patterns are available in Gregorian and Generic calendars, In these ne 2. If it is equally good in two different positions, favor the position used for the 'a' pattern character. 3. If the position needs to be different depending on the width of B, please file a ticket. 2. For more information on the day periods used in your language: - 1. First see [Day Periods (AM, PM, etc.)](https://cldr.unicode.org/translation/date-time/date-time-names) for a general discussion of how day periods work. + 1. First see [Day Periods (AM, PM, etc.)](/translation/date-time/date-time-names) for a general discussion of how day periods work. 2. See the [Day Periods](https://www.unicode.org/cldr/charts/45/supplemental/day_periods.html) chart for your language. ![image](../../images/date-time/ST-flexibledayperiod.JPG) @@ -336,9 +336,9 @@ For developers who use CLDR data,  💡 **Translation Tips** -- If your language has a grammatical difference in the month names(aside from just the simple addition of a prefix or suffix), localizers will need to use a work-around construction ([file a ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket) if this is the case for your language). +- If your language has a grammatical difference in the month names(aside from just the simple addition of a prefix or suffix), localizers will need to use a work-around construction ([file a ticket](/index/bug-reports#TOC-Filing-a-Ticket) if this is the case for your language). -As described [under Date/Time Names](https://cldr.unicode.org/translation/date-time/date-time-names), CLDR also provides a relative week period pattern which is used for constructions such as “the week of April 11, 2016”. The English pattern that produces this is “the week of {0}”; the date format that replaces {0} is determined separately. Because the week-of patterns described here may appear in user interfaces that also show dates produced using the relative week period patterns, all of these patterns should be designed with consistent wording and structure. +As described [under Date/Time Names](/translation/date-time/date-time-names), CLDR also provides a relative week period pattern which is used for constructions such as “the week of April 11, 2016”. The English pattern that produces this is “the week of {0}”; the date format that replaces {0} is determined separately. Because the week-of patterns described here may appear in user interfaces that also show dates produced using the relative week period patterns, all of these patterns should be designed with consistent wording and structure. ## Flexible - Timezone Append @@ -354,9 +354,9 @@ The flexible append format for Timezone is used to compose a time and a timezone ## Date/Time Intervals -Interval patterns contain a start pattern and an end pattern (using the [Date/Time Symbols](https://cldr.unicode.org/translation/date-time/date-time-symbols)). They are used for a range of dates or times, such as "Sept 10–12" (meaning the 10th of September through the 12th of September). The interval format is used where it is necessary to make the pattern as short as possible, and elide information that does not have to be repeated. For example, the pattern used to get "Sept 10–12" in English is "MMM d–d". +Interval patterns contain a start pattern and an end pattern (using the [Date/Time Symbols](/translation/date-time/date-time-symbols)). They are used for a range of dates or times, such as "Sept 10–12" (meaning the 10th of September through the 12th of September). The interval format is used where it is necessary to make the pattern as short as possible, and elide information that does not have to be repeated. For example, the pattern used to get "Sept 10–12" in English is "MMM d–d". -Unlike simple [Date/Time Patterns](https://cldr.unicode.org/translation/date-time/date-time-patterns), these consist of two parts, typically separated by with some kind of punctuation mark (e.g. English uses en-dash " – "). Also, some fields in the second part are omitted (e.g. "d – d MMM" omits repeat of MMM for the second part). The first field that comes from the second date is marked with red in the examples below. +Unlike simple [Date/Time Patterns](/translation/date-time/date-time-patterns), these consist of two parts, typically separated by with some kind of punctuation mark (e.g. English uses en-dash " – "). Also, some fields in the second part are omitted (e.g. "d – d MMM" omits repeat of MMM for the second part). The first field that comes from the second date is marked with red in the examples below. ### Interval Formatting diff --git a/docs/site/translation/date-time/date-time-symbols.md b/docs/site/translation/date-time/date-time-symbols.md index f393838ace2..3c5d0762ce1 100644 --- a/docs/site/translation/date-time/date-time-symbols.md +++ b/docs/site/translation/date-time/date-time-symbols.md @@ -4,7 +4,7 @@ title: Date/Time Symbols # Date/Time Symbols -Symbols is a required topic to work in [Date/Time Patterns](https://cldr.unicode.org/translation/date-time/date-time-patterns) +Symbols is a required topic to work in [Date/Time Patterns](/translation/date-time/date-time-patterns) More details on date/time symbols and patterns may be found in the Spec [Date Field Symbol Table](http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table). @@ -16,7 +16,7 @@ When the software formats a date for your language, a value will be substituted Notice in the table below that there are different pattern characters for standalone and formatting. For example M to indicate the formatting and L to indicate the standalone month names. -Make sure you understand the difference between standalone and formatting patterns and use the appropriate symbols in patterns. See [when to use standalone vs. formatting](https://cldr.unicode.org/translation/date-time/date-time-patterns) in Date and Time patterns. +Make sure you understand the difference between standalone and formatting patterns and use the appropriate symbols in patterns. See [when to use standalone vs. formatting](/translation/date-time/date-time-patterns) in Date and Time patterns. | Symbol | Meaning | English example | Special note | Usage in pattern example | |:---:|---|---|---|---| @@ -30,7 +30,7 @@ Make sure you understand the difference between standalone and formatting patter | h
H
K
k | Hour | 12 | h- hour in a 12 hour clock
H-hour in a 24 hour clock system using 0-23
K -12 hour cycle using 0 through 11
k - 24 hour cycle using 1 though 24 | h:mm a = 3:25 PM
HH:mm = 15:25
K:mm a = 0:25 AM
kk:mm = 24:25 | | m | minute | 49 | | hh:mm a = 03:25 PM | | s | second | 49 | | h:mm:ss = 3:25:01 PM | -| a
b
B | day period | AM noon in the morning | a- AM or PM b-am, noon, pm, or midnight
B-"in the morning", "in the evening" (see [Day period names](https://cldr.unicode.org/translation/date-time-1/date-time-names#TOC-Day-Periods-AM-PM-etc.-))

ONLY used with "h" or K" for all a, b and B See [date/time patterns about flexible time formats](https://st.unicode.org/cldr-apps/v#/fr/Gregorian/7a365a21694f0127) even if your language does not use 12-hour time clock Also see date/time day period patterns. | h:mm a = 3:25 PM

h:mm b = 12:00 noon

h:mm B= 3:25 in the afternoon | +| a
b
B | day period | AM noon in the morning | a- AM or PM b-am, noon, pm, or midnight
B-"in the morning", "in the evening" (see [Day period names](/translation/date-time-1/date-time-names#TOC-Day-Periods-AM-PM-etc.-))

ONLY used with "h" or K" for all a, b and B See [date/time patterns about flexible time formats](https://st.unicode.org/cldr-apps/v#/fr/Gregorian/7a365a21694f0127) even if your language does not use 12-hour time clock Also see date/time day period patterns. | h:mm a = 3:25 PM

h:mm b = 12:00 noon

h:mm B= 3:25 in the afternoon | | z / v | timezone | Pacific Time, Paris Time | Don't change v to z or vice versa; just leave either z or v as in English. | h a – h a v = 5 AM – 5 PM GMT | | ' | | | If you want a sequence of one or more real letters A–Z or a–z within a pattern, you need to put it in single quotes, such as 'ta'. This is because l etters included in a format have special meaning.
For a real single quote, use '' (that is, two adjacent ' characters). | German example for skeleton h h 'Uhr' a = 1 Uhr PM | | Q | Quarter (a concept of 3 months period) | | These are calendar quarters not fiscal quarters.

4 Quarters in United States for example would be Jan-Mar, Apr-June, July-Sep, Sep-Dec. Also see 💡 **Translation Tips** below | QQQ y = Q3 1999 | @@ -62,7 +62,7 @@ The longer forms are only relevant for the fields that are non-numeric, such as ## Standalone vs. Format Styles - This section is relevant to [When to use standalone vs. Formatting](https://cldr.unicode.org/translation/date-time/date-time-patterns) in date/time patterns. + This section is relevant to [When to use standalone vs. Formatting](/translation/date-time/date-time-patterns) in date/time patterns. Some languages use two different forms of strings (*standalone* and *format*) depending on the context. Typically the *standalone* version is the nominative form of the word, and the *format* version is in the genitive (or related form). @@ -75,7 +75,7 @@ Two different characters are used: 💡 **Translation Tips** -- Standalone and Format names must be coordinated with the format strings. See [When to use standalone vs. Formatting](https://cldr.unicode.org/translation/date-time/date-time-patterns) in date/time patterns. +- Standalone and Format names must be coordinated with the format strings. See [When to use standalone vs. Formatting](/translation/date-time/date-time-patterns) in date/time patterns. - If your language uses two different form, be sure to provide the correct forms under Standalone and Formatting. For example in Brazilian Portuguese - "Dezembro" for December when standing alone; thus use LLLL - "Dezembru" when referencing December with a date (e.g. to mean "the nth day of that month"); thus, use MMMM @@ -87,7 +87,7 @@ Two different characters are used: | de gener | gener | | d'abril | abril | -These days, standalone names should not be used merely to provide capitalized forms. There are other solutions for capitalizing date symbols which provide finer control over capitalization, see [capitalization guidelines](https://cldr.unicode.org/translation/translation-guide-general/capitalization). +These days, standalone names should not be used merely to provide capitalized forms. There are other solutions for capitalizing date symbols which provide finer control over capitalization, see [capitalization guidelines](/translation/translation-guide-general/capitalization). ### Examples: diff --git a/docs/site/translation/displaynames.md b/docs/site/translation/displaynames.md index 8e89fd61759..d4b2c24a0b6 100644 --- a/docs/site/translation/displaynames.md +++ b/docs/site/translation/displaynames.md @@ -4,11 +4,11 @@ title: Displaynames # Displaynames -- [Country/Region (Territory) Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) -- [Language/Locale Name Patterns](https://cldr.unicode.org/translation/displaynames/languagelocale-name-patterns) -- [Language/Locale Names](https://cldr.unicode.org/translation/displaynames/languagelocale-names) -- [Locale Option Names (Key)](https://cldr.unicode.org/translation/displaynames/locale-option-names-key) -- [Script Names](https://cldr.unicode.org/translation/displaynames/script-names) +- [Country/Region (Territory) Names](/translation/displaynames/countryregion-territory-names) +- [Language/Locale Name Patterns](/translation/displaynames/languagelocale-name-patterns) +- [Language/Locale Names](/translation/displaynames/languagelocale-names) +- [Locale Option Names (Key)](/translation/displaynames/locale-option-names-key) +- [Script Names](/translation/displaynames/script-names) Displaynames category include the names of the fundamental data in internationalization: Languages and Country/Regions diff --git a/docs/site/translation/displaynames/countryregion-territory-names.md b/docs/site/translation/displaynames/countryregion-territory-names.md index 384ef3696ad..8fc00f01567 100644 --- a/docs/site/translation/displaynames/countryregion-territory-names.md +++ b/docs/site/translation/displaynames/countryregion-territory-names.md @@ -4,14 +4,14 @@ title: Country/Region (Territory) Names # Country/Region (Territory) Names -Country and region names (referred to as Territories in the Survey Tool) may be used as part of [Language/Locale Names](https://cldr.unicode.org/translation/displaynames/languagelocale-names), or may be used in UI menus and lists to select countries or regions. +Country and region names (referred to as Territories in the Survey Tool) may be used as part of [Language/Locale Names](/translation/displaynames/languagelocale-names), or may be used in UI menus and lists to select countries or regions. ## General Guidelines Please follow these guidelines: 1. Use the most neutral grammatical form for the country/region that is natural for these two usages above. If there is no single form that can accomplish that, favor the usage within UI menus. -2. Use the capitalization that would be appropriate in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization). +2. Use the capitalization that would be appropriate in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](/translation/translation-guide-general/capitalization). 3. Each of the names **must** be unique (see below). 4. Don't use commas and don't invert the name (eg use "South Korea", not "Korea, South"). diff --git a/docs/site/translation/displaynames/languagelocale-names.md b/docs/site/translation/displaynames/languagelocale-names.md index 83ae921be61..603a324e20d 100644 --- a/docs/site/translation/displaynames/languagelocale-names.md +++ b/docs/site/translation/displaynames/languagelocale-names.md @@ -4,9 +4,9 @@ title: Language/Locale Names # Language/Locale Names -Some language names are simple, like "English". However, it is often important to distinguish a variant of the language, even when it is only written. For example, British English and American English are often written differently. In some cases, the difference can be quite substantial, such as when the same language is written with different [scripts](https://cldr.unicode.org/translation/displaynames/script-names) (aka writing systems, like Latin letters vs Greek letters). +Some language names are simple, like "English". However, it is often important to distinguish a variant of the language, even when it is only written. For example, British English and American English are often written differently. In some cases, the difference can be quite substantial, such as when the same language is written with different [scripts](/translation/displaynames/script-names) (aka writing systems, like Latin letters vs Greek letters). -Thus more complex language names may be composed from simple languages plus variants. A pattern is used to control how the translations for language, script, and region codes are composed into a name when the compound code doesn't have a specific translation. An example is "αγγλικά (Αυστραλία)", which has the native name for "English", followed by the native word for "Australia" in parentheses. See [Patterns for Locale/Language Names](https://cldr.unicode.org/translation/displaynames/languagelocale-name-patterns). +Thus more complex language names may be composed from simple languages plus variants. A pattern is used to control how the translations for language, script, and region codes are composed into a name when the compound code doesn't have a specific translation. An example is "αγγλικά (Αυστραλία)", which has the native name for "English", followed by the native word for "Australia" in parentheses. See [Patterns for Locale/Language Names](/translation/displaynames/languagelocale-name-patterns). For the simple language names, please follow these guidelines: @@ -14,7 +14,7 @@ For the simple language names, please follow these guidelines: - Don't use commas and don't invert the name (eg use "French Creole", not "French, Creole"). - Don't use the characters "(" and ")", since they will be confusing in combination with countries or scripts in more complex language names. If you have to use brackets, use square ones: [ and ]. - The most neutral grammatical form for the language name should be chosen. -- Use the capitalization that would be appropriate for a language name in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization). +- Use the capitalization that would be appropriate for a language name in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](/translation/translation-guide-general/capitalization). ## Unique Names diff --git a/docs/site/translation/displaynames/locale-option-names-key.md b/docs/site/translation/displaynames/locale-option-names-key.md index 8ce9320d29e..256495b9dcf 100644 --- a/docs/site/translation/displaynames/locale-option-names-key.md +++ b/docs/site/translation/displaynames/locale-option-names-key.md @@ -20,7 +20,7 @@ Here are the names of Options to be translated. ## Locale Option Value Names -The following are some examples of Option+Value combinations that need translation. Where the Value for the Option is not from a small set (Currency and Private Use), then the Locale Option Pattern is used (see [Language/Locale Name Patterns](https://cldr.unicode.org/translation/displaynames/languagelocale-name-patterns). +The following are some examples of Option+Value combinations that need translation. Where the Value for the Option is not from a small set (Currency and Private Use), then the Locale Option Pattern is used (see [Language/Locale Name Patterns](/translation/displaynames/languagelocale-name-patterns). | Option | Value | English Name | Meaning | |---|---|---|---| @@ -38,6 +38,6 @@ The following are some examples of Option+Value combinations that need translati | Collation | big5han | Traditional Sort Order - Big5 | An ordering based on the character encoding Big5 (for Chinese) | | Numbers | armn | Armenian Numerals | The numbering system that uses Armenian digits. | -For transform names (BGN, Numeric, Tone, UNGEGN, x-Accents, x-Fullwidth, x-Halfwidth, x-Jamo, x-Pinyin, x-Publishing), see [Transforms](https://cldr.unicode.org/translation/transforms). +For transform names (BGN, Numeric, Tone, UNGEGN, x-Accents, x-Fullwidth, x-Halfwidth, x-Jamo, x-Pinyin, x-Publishing), see [Transforms](/translation/transforms). diff --git a/docs/site/translation/displaynames/script-names.md b/docs/site/translation/displaynames/script-names.md index d0d75072753..fcfd226acb6 100644 --- a/docs/site/translation/displaynames/script-names.md +++ b/docs/site/translation/displaynames/script-names.md @@ -21,8 +21,8 @@ For the script names, please follow these guidelines: - Don't use commas and don't invert the name (eg use "New Tai Lue", not "Tai Lue, New"). - Don't use the characters "(" and ")", since they will be confusing in combination with countries or languages in more complex language names. If you have to use brackets, use square ones: [ and ]. - The most neutral grammatical form for the script that is natural for these two usages should be chosen. If there is no single form that can accomplish that, favor the usage within language names (inside parentheses). -- Use the capitalization that would be appropriate in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](http://cldr.unicode.org/translation/capitalization). +- Use the capitalization that would be appropriate in the middle of a sentence; the \ data can specify the capitalization for other contexts. For more information, see [Capitalization](/translation/capitalization). -See also [Language Names](https://cldr.unicode.org/translation/displaynames/languagelocale-names). +See also [Language Names](/translation/displaynames/languagelocale-names). diff --git a/docs/site/translation/error-codes.md b/docs/site/translation/error-codes.md index a80f8026b11..e6d37e37857 100644 --- a/docs/site/translation/error-codes.md +++ b/docs/site/translation/error-codes.md @@ -27,6 +27,6 @@ The error message will show which placeholders are expected, with an uppercase p They allow for, and often need, duplicate placeholders. -- For plurals and ordinals, make sure to read [Determining Plural Categories](http://cldr.unicode.org/index/cldr-spec/plural-rules#TOC-Determining-Plural-Categories). -- For case and gender, make sure read [Grammatical Inflection](https://cldr.unicode.org/translation/grammatical-inflection). +- For plurals and ordinals, make sure to read [Determining Plural Categories](/index/cldr-spec/plural-rules#TOC-Determining-Plural-Categories). +- For case and gender, make sure read [Grammatical Inflection](/translation/grammatical-inflection). diff --git a/docs/site/translation/getting-started.md b/docs/site/translation/getting-started.md index 934df460918..92092978beb 100644 --- a/docs/site/translation/getting-started.md +++ b/docs/site/translation/getting-started.md @@ -6,19 +6,19 @@ title: Getting Started Before getting started to contribute data in CLDR, and jumping in to using the Survey Tool, it is important that you understand the CLDR process. -1. Understand the basics about the CLDR process and the community-based model and the Technical Committee. Read: [CLDR Process](https://cldr.unicode.org/index/process) +1. Understand the basics about the CLDR process and the community-based model and the Technical Committee. Read: [CLDR Process](/index/process) 2. Read the Getting Started topics on the Information Hub: - - [Survey Tool Guide](https://cldr.unicode.org/translation/getting-started/guide) - - [Survey Tool Stages](https://cldr.unicode.org/translation/getting-started/survey-tool-phases) - - [Handling Errors and Warnings](https://cldr.unicode.org/translation/getting-started/errors-and-warnings) - - [Handling Logical Group Errors](https://cldr.unicode.org/translation/getting-started/resolving-errors) - - [Plurals & Units](https://cldr.unicode.org/translation/getting-started/plurals) - - [Review Date & Time](https://cldr.unicode.org/translation/date-time) - - [Review Numbers](https://cldr.unicode.org/translation/number-currency-formats) - - [Review Zones](https://cldr.unicode.org/translation/time-zones-and-city-names) - - [Data stability](https://cldr.unicode.org/translation/getting-started/data-stability) - - [Empty cache](https://cldr.unicode.org/translation/getting-started/empty-cache) + - [Survey Tool Guide](/translation/getting-started/guide) + - [Survey Tool Stages](/translation/getting-started/survey-tool-phases) + - [Handling Errors and Warnings](/translation/getting-started/errors-and-warnings) + - [Handling Logical Group Errors](/translation/getting-started/resolving-errors) + - [Plurals & Units](/translation/getting-started/plurals) + - [Review Date & Time](/translation/date-time) + - [Review Numbers](/translation/number-currency-formats) + - [Review Zones](/translation/time-zones-and-city-names) + - [Data stability](/translation/getting-started/data-stability) + - [Empty cache](/translation/getting-started/empty-cache) -\*If you (individual or your organization) have not established a connection with the CLDR technical committee, start with [Survey Tool Accounts](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts). +\*If you (individual or your organization) have not established a connection with the CLDR technical committee, start with [Survey Tool Accounts](/index/survey-tool/survey-tool-accounts). diff --git a/docs/site/translation/getting-started/errors-and-warnings.md b/docs/site/translation/getting-started/errors-and-warnings.md index af26559d8ca..27bab98bc4f 100644 --- a/docs/site/translation/getting-started/errors-and-warnings.md +++ b/docs/site/translation/getting-started/errors-and-warnings.md @@ -23,13 +23,13 @@ In the above case, it is a pretty clear mistake. It is not as simple in other ca You can find some guidance under "Unique Names" in the following pages: -- [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names), -- [City Names](https://cldr.unicode.org/translation/timezones#TOC-City-Names), -- [Currency Symbols & Names](https://cldr.unicode.org/translation/currency-names-and-symbols/currency-names) +- [Country/Region Names](/translation/displaynames/countryregion-territory-names), +- [City Names](/translation/timezones#TOC-City-Names), +- [Currency Symbols & Names](/translation/currency-names-and-symbols/currency-names) **The characters ‎\[…\]‎ should not be used (Must fix)** -For what to do, see [Characters](https://cldr.unicode.org/translation/-core-data/exemplars#TOC-Handing-Warnings-in-Exemplar-characters), in the section Handling Warnings. _While these are categorized as warnings, every effort should be made to fix them._ +For what to do, see [Characters](/translation/-core-data/exemplars#TOC-Handing-Warnings-in-Exemplar-characters), in the section Handling Warnings. _While these are categorized as warnings, every effort should be made to fix them._ **Unquoted special character '.' in pattern (Must fix)** @@ -38,7 +38,7 @@ Number patterns can only contain an unquoted . when it is the decimal separator. In other cases, such as to finish an abbreviation, it must be quoted, as in: 000 tūkst'.' -For more information, see [Number Patterns](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns). +For more information, see [Number Patterns](/translation/number-currency-formats/number-and-currency-patterns). - Errors in Others column can be ignored. For example, this is an example of an Inheritance value in the Others column where the Language (Country/region) names have a collision issue. Do not vote on values that have errors. diff --git a/docs/site/translation/getting-started/guide.md b/docs/site/translation/getting-started/guide.md index 4b371695285..c76ec4885af 100644 --- a/docs/site/translation/getting-started/guide.md +++ b/docs/site/translation/getting-started/guide.md @@ -8,7 +8,7 @@ title: Survey Tool Guide _2022-11-28 Updated several images and instructions to reflect improvements, such as revised menus, buttons,regional inheritance, and the Dashboard and Forum._ -[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) +[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](/index/survey-tool/survey-tool-accounts) **|** [**Guide**](/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](/index/survey-tool/faq-and-known-bugs) The Survey tool is a web based tool for collecting CLDR data and includes various features that the contributors (vetters) should know before getting started. @@ -16,12 +16,12 @@ Note that the exact appearance in screenshots may change as the tool is enhanced ### 💡 Helpful Tips -- Please read the home page of the [Translation Guidelines](https://cldr.unicode.org/translation) before starting your data contribution. +- Please read the home page of the [Translation Guidelines](/translation) before starting your data contribution. - If you experience a **Loading...** problem with the Survey Tool, try clearing your browser cache. See [Reloading JavaScript](https://www.filecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XOjGNtMzbuM). - **Browser support** for Survey Tool includes the latest versions of Edge, Safari, Chrome, and Firefox. -- Use [Reports](https://cldr.unicode.org/translation/getting-started/guide#TOC-Reports) at the beginning to review the data in your language in a holistic manner for Date & time, Zones, and Numbers. - - Capitalization: Translations should be what is most appropriate for ”middle-of-sentence” use. So, for example, if your language normally doesn't spell languages with a capital letter, then you shouldn’t do that here. Please see [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) for more details. - - Plurals: For important information regarding the use of plural forms for your language, please read [Plurals](https://cldr.unicode.org/translation/getting-started/plurals). +- Use [Reports](/translation/getting-started/guide#TOC-Reports) at the beginning to review the data in your language in a holistic manner for Date & time, Zones, and Numbers. + - Capitalization: Translations should be what is most appropriate for ”middle-of-sentence” use. So, for example, if your language normally doesn't spell languages with a capital letter, then you shouldn’t do that here. Please see [Capitalization](/translation/translation-guide-general/capitalization) for more details. + - Plurals: For important information regarding the use of plural forms for your language, please read [Plurals](/translation/getting-started/plurals). ### Vetting Phase @@ -60,12 +60,12 @@ At a point towards the end of Survey Tool period, the Technical Committee will c 1. Only those of you working on a specific variant language (or "sub-locale") will pick a non-default region. If you work on Mexican Spanish, pick **Mexico**. (This should already be pre-selected for you.) -_Make sure that you haven't mistakenly turned the Information Panel off! See_ [_**No Information Panel**_](https://cldr.unicode.org/translation/getting-started/guide%23TOC-No-Information-Panel)_**.**_ +_Make sure that you haven't mistakenly turned the Information Panel off! See_ [_**No Information Panel**_](/translation/getting-started/guide%23TOC-No-Information-Panel)_**.**_ ### Voting view 1. Once you have selected your locale, more options show up in the left sidebar. (You’ll note that the sidebar only shows if you mouse over the **\>** character on the left.) -2. If the locale is relatively new and very complete, start working on the **Core Data** section and go through the rest of the sections. If the locale is mostly complete, then go to [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide) below. +2. If the locale is relatively new and very complete, start working on the **Core Data** section and go through the rest of the sections. If the locale is mostly complete, then go to [**Dashboard**](/translation/getting-started/guide) below. 3. Once you have selected a section, you'll see a table to enter votes in. The main table has these columns: - **Code**: the code CLDR uses to identify this data point. - **English**: the plain English value of the data point (the text you are to translate). @@ -77,7 +77,7 @@ _Make sure that you haven't mistakenly turned the Information Panel off! See_ [_ - **Others**: other suggested values, not currently winning, but available to vote for. 4. Click on one of the radio buttons to make your vote. The winning status changes in real-time so depending on vote requirements and existing votes, your vote may move your desired value to the winning column right away. 1. Look at the Regional Variants to see if any should be changed: see **Information Panel** below. -5. Once you are done with all the sections, go to the [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide)**.** +5. Once you are done with all the sections, go to the [**Dashboard**](/translation/getting-started/guide)**.** 6. Under the English column, look for "**i**" for additional information and "**e**" for an example. ![alt-text](../../images/gettingStartedGuideArabic.png) ![alt-text](../../images/gettingStartedGuideEnglish.jpg) @@ -88,7 +88,7 @@ The main panel uses icons to indicate important information and possible problem ![alt-text](../../images/gettingStartedGuideIcon.png) -(Icons for the **Dashboard** are listed in the [**Dashboard Icons**](https://cldr.unicode.org/translation/getting-started/guide) section below.) +(Icons for the **Dashboard** are listed in the [**Dashboard Icons**](/translation/getting-started/guide) section below.) ### Examples @@ -104,7 +104,7 @@ An example with an ❌ shows a case where the pattern has an inappropriate plac 6. Below that, you'll see an example. This is the same as you get by hovering over the item in the center section. 7. If there are votes, you'll see a breakdown of them; you also see the number of votes required to change the value. Unicode organization members usually have 4 votes; _vetters which are not representing a Unicode organization usually have 1 vote_. Your vote value and the vote value required for change will show on the right navigation for the selected item as shown in this screenshot (4 and 8 respectively in this case). 8. Near the bottom, you'll see a pulldown menu that shows the values for different regional Variants. Here, you can quickly compare the values and go to different sub-locales to correct inconsistencies. -9. You'll also see the New Forum Post button (as shown in the screenshot _to the right_). This is the easiest way to post discussions for the selected item. Remember that the Forum posts are at language level and not at Sub-locale level. For more information, see [Forum](https://cldr.unicode.org/translation/getting-started/guide). +9. You'll also see the New Forum Post button (as shown in the screenshot _to the right_). This is the easiest way to post discussions for the selected item. Remember that the Forum posts are at language level and not at Sub-locale level. For more information, see [Forum](/translation/getting-started/guide). 10. **No Information Panel?** - If you click on the **Code** cell and there is no **Information Panel**, you may have turned it off accidentally. Click on the **Open Info Panel** button near the top right of the window. @@ -187,7 +187,7 @@ The Dashboard will show you a list of data items with warnings of different kind ![alt-text](../../images/gettingStartedGuideDashboard.png) -The goal is that you should work the Dashboard down to show zero items, then review the [**Reports**](https://cldr.unicode.org/index/survey-tool/guide#TOC-Reports), below. +The goal is that you should work the Dashboard down to show zero items, then review the [**Reports**](/index/survey-tool/guide#TOC-Reports), below. _The first priority is to fix all the_ _**Missing**_ _items by supplying the correct translations._ @@ -273,7 +273,7 @@ You may see a message like the following when trying to modify a regional locale ![alt-text](../../images/gettingStartedGuideBrazil.png) -The reason that Brazil is grayed out is that it is the default content locale for Portuguese. So to modify pt-BR, you need to simply click on Portuguese. If you do click on Brazil, you will get to a page with the following at the top. Clicking on [default content locale](https://cldr.unicode.org/translation/translation-guide-general/default-content) will explain in more detail. +The reason that Brazil is grayed out is that it is the default content locale for Portuguese. So to modify pt-BR, you need to simply click on Portuguese. If you do click on Brazil, you will get to a page with the following at the top. Clicking on [default content locale](/translation/translation-guide-general/default-content) will explain in more detail. ![alt-text](../../images/gettingStartedGuideGeneralInfo.png) @@ -328,7 +328,7 @@ A forum post can be specific to a particular data point or a general issue. In e - A general issue that impacts multiple data points. In a general case that impacts multiple data points, you do not need to post new forum posts for every item impacted. The general issue should be flagged to other vetters and once a consensus is reached, it is expected that vetters update their votes on all impacted items. New forum posts can be used to flag to other vetters if others fail to update their votes on all impacted items. ONLY request if others have missed or have not updated consistently. -**Create forum posts from the** [**Information pane**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel)**l in the voting window.** +**Create forum posts from the** [**Information pane**](/translation/getting-started/guide#TOC-Information-Panel)**l in the voting window.** 1. Vote on an item (or add new +) for the item you want to suggest changing. @@ -353,9 +353,9 @@ A forum post can be specific to a particular data point or a general issue. In e There are two ways to respond to forum posts: - Info Panel (This is the recommended option.) -- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) +- In the Forum view (See [Working in the Forum view](/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) -**Respond from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** +**Respond from the** [**Info Panel**](/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** In the **Info Panel**, select the **Comment** button - Each posted response is labeled in Red and its response type: Agree, Decline or Comment. @@ -375,10 +375,10 @@ In the **Info Panel**, select the **Comment** button There are two ways to respond to new forum post: - Info Panel (This is the recommended option.) -- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) +- In the Forum view (See [Working in the Forum view](/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) -**Respond to forum posts from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** +**Respond to forum posts from the** [**Info Panel**](/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** 1. In the Info Panel click the **Comment** button and add your input to the open discussion. 2. The label **Discuss** in Red indicates that this is a Discuss post (to distinguish from Request posts) @@ -408,13 +408,13 @@ In the Forum view, you can respond to Request and Discuss posts. For **Request posts**, you can select your decision using the 3 available buttons: **Agree, Decline, Comment.** -See [Responding to Request posts in Information Pane](https://cldr.unicode.org/translation/getting-started/guide#TOC-Responding-to-Request-posts). +See [Responding to Request posts in Information Pane](/translation/getting-started/guide#TOC-Responding-to-Request-posts). ![alt-text](../../images/gettingStartedGuideForumPosts.png) ## Reporting Survey Tool issues -If you run into a problem with the Survey Tool functionalities, please see [FAQ & Known Bugs](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) to see whether it has already been reported (and whether there is a work-around). If not, or if you have suggestions for improvements, please file a bug using the Feedback link at the bottom of each window. If you encounter problems or have enhancement suggestions for the survey tool, please [file a ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). +If you run into a problem with the Survey Tool functionalities, please see [FAQ & Known Bugs](/index/survey-tool/faq-and-known-bugs) to see whether it has already been reported (and whether there is a work-around). If not, or if you have suggestions for improvements, please file a bug using the Feedback link at the bottom of each window. If you encounter problems or have enhancement suggestions for the survey tool, please [file a ticket](/index/bug-reports#TOC-Filing-a-Ticket). ![alt-text](../../images/gettingStartedGuideCoverage.png) @@ -438,8 +438,8 @@ The goal is to bring it to the attention to all linguists contributing in a part ## Advanced Features -1. Users familiar with CLDR XML format can upload votes (and submissions) for multiple items at once. See [**Bulk Data Upload**](https://cldr.unicode.org/index/survey-tool/bulk-data-upload)**.** -2. Organization managers can manage users for their organization (add, remove, send passwords, set locales, etc.) For more information, see [**Managing Users**](https://cldr.unicode.org/index/survey-tool/managing-users)**.** +1. Users familiar with CLDR XML format can upload votes (and submissions) for multiple items at once. See [**Bulk Data Upload**](/index/survey-tool/bulk-data-upload)**.** +2. Organization managers can manage users for their organization (add, remove, send passwords, set locales, etc.) For more information, see [**Managing Users**](/index/survey-tool/managing-users)**.** 1. Some users may want to reset their Coverage Level, with the menu that looks like the image to the right. 2. The Coverage Level determines the items that you will see for translation: the minimal level has the highest priority items. You normally start with the level marked "Default" (which will vary by your organization and locale). Each successively higher level adds more items, at successively lower priorities. You will not normally go beyond "Modern", unless you have special instructions for your organization. 3. _Note that some companies won't use the data until it is complete at a certain coverage level, typically_ _**Modern**._ diff --git a/docs/site/translation/getting-started/plurals.md b/docs/site/translation/getting-started/plurals.md index faed65ab660..46ba590444e 100644 --- a/docs/site/translation/getting-started/plurals.md +++ b/docs/site/translation/getting-started/plurals.md @@ -10,11 +10,11 @@ In CLDR, Plurals are used for localized Units and Compact numbers (under Numbers In the Survey Tool for translation purpose, plural forms shown per language will differ as only those that are relevant to that language are shown. -For example, in French, the distinction of the One and Other are available. Please see [Plural Rules](https://cldr.unicode.org/index/cldr-spec/plural-rules), and [file a ticket](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md) if you see a form in the Survey Tool that is not expected in your language. +For example, in French, the distinction of the One and Other are available. Please see [Plural Rules](/index/cldr-spec/plural-rules), and [file a ticket](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md) if you see a form in the Survey Tool that is not expected in your language. ![image](../../images/French-plural.PNG) -**Note:** Many of the sets of names form Logical Groups, and you need to make sure they have the same status or you will get error messages. See [Logical Groups](https://cldr.unicode.org/translation/getting-started/resolving-errors) for more information. +**Note:** Many of the sets of names form Logical Groups, and you need to make sure they have the same status or you will get error messages. See [Logical Groups](/translation/getting-started/resolving-errors) for more information. ## Localized Units @@ -71,17 +71,17 @@ The short and narrow forms of the display names for a unit need not be as short ## Past and Future -Unit patterns for past and future (3 hours ago, In 4 hours) are related to [Relative Dates](https://cldr.unicode.org/translation/date-time/date-time-names), and occur in the same circumstances. They need to have the same casing behavior. That is, if the translation for "Yesterday" starts with an uppercase 'Y', then the translation for "In {0} hours" needs to start with an uppercase 'I' (if it doesn't start with the placeholder). +Unit patterns for past and future (3 hours ago, In 4 hours) are related to [Relative Dates](/translation/date-time/date-time-names), and occur in the same circumstances. They need to have the same casing behavior. That is, if the translation for "Yesterday" starts with an uppercase 'Y', then the translation for "In {0} hours" needs to start with an uppercase 'I' (if it doesn't start with the placeholder). ## Minimal Pairs Minimal pairs are used to verify the different grammatical features used by a language. _**These messages are not to be translated literally; do not simply translate the English!**_ -- **Plurals (cardinals) and Ordinals.** See [Determining Plural Categories](https://cldr.unicode.org/index/cldr-spec/plural-rules#TOC-Determining-Plural-Categories). -- **Grammatical Case and Gender.** See [Grammatical Inflection](https://cldr.unicode.org/translation/grammatical-inflection) +- **Plurals (cardinals) and Ordinals.** See [Determining Plural Categories](/index/cldr-spec/plural-rules#TOC-Determining-Plural-Categories). +- **Grammatical Case and Gender.** See [Grammatical Inflection](/translation/grammatical-inflection) ## Compound Units -Units of measurement can be formed from other units and other components. For more information, see [Compound Units](https://cldr.unicode.org/translation/units/unit-names-and-patterns). +Units of measurement can be formed from other units and other components. For more information, see [Compound Units](/translation/units/unit-names-and-patterns). diff --git a/docs/site/translation/getting-started/review-formats.md b/docs/site/translation/getting-started/review-formats.md index 128addcc11f..14b32fe12f1 100644 --- a/docs/site/translation/getting-started/review-formats.md +++ b/docs/site/translation/getting-started/review-formats.md @@ -46,7 +46,7 @@ Check for consistency between different forms by looking at them side by side. ### Person Name tips -1. Please read the [Miscellaneous: Person Name Formats](https://cldr.unicode.org/translation/miscellaneous-person-name-formats) under "**Review Report**". +1. Please read the [Miscellaneous: Person Name Formats](/translation/miscellaneous-person-name-formats) under "**Review Report**". ### Date & Time Review Tips diff --git a/docs/site/translation/getting-started/survey-tool-phases.md b/docs/site/translation/getting-started/survey-tool-phases.md index 019fd776c28..3c860ddb4a9 100644 --- a/docs/site/translation/getting-started/survey-tool-phases.md +++ b/docs/site/translation/getting-started/survey-tool-phases.md @@ -23,7 +23,7 @@ There are two types of releases: full, and limited-submission. - Limited-submission - Typically with odd versions (e.g. version 37). - Selected fields are open for all locales; the voting options will be grayed out for those data points that are not in scope. - - Proceed with Submission (General), but start with the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) and focus on Errors\*, Missing†, Provisional + - Proceed with Submission (General), but start with the [Dashboard](/translation/getting-started/guide#h.bmzr9ejnlv1u) and focus on Errors\*, Missing†, Provisional - Selected locales are open for votes on all fields. - Proceed with Submission (General).  @@ -39,7 +39,7 @@ You should know in this stage: - You can start work - Expect a churn: there may be additional Tooling fixes and Data additions during this period.  - Tool may be taken down for updates more frequently during general submission -- You are expected to look for issues with the Survey tool and any other problems you encounter as a vetter. Please [file a ticket](https://cldr.unicode.org/index/bug-reports). +- You are expected to look for issues with the Survey tool and any other problems you encounter as a vetter. Please [file a ticket](/index/bug-reports). ### Survey Tool phase: General Submission @@ -47,28 +47,28 @@ _Make sure your coverage level is set correctly at the top of the page._ For new locales or ones where the goal is to increase the level, it is best to proceed page-by-page starting with the **Core Data** section. At the top of each page you can see the number of items open on the page. Then scan down the page to see all the places where you need to vote (including adding items). Some  -Then please focus on the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) view, +Then please focus on the [Dashboard](/translation/getting-started/guide#h.bmzr9ejnlv1u) view, 1. Get all **Missing**† items entered 2. Vote for all **Provisional** items (where you haven't already voted) 3. Address any remaining **Errors\*** 4. Review the **English Changed** (where the English value changed, but your locale's value didn't. These may need adjustment.) - \* Note that if the committee finds systematic errors in data, new tests can be added during the submission period, resulting in new **Errors**. - - † Among the _**Missing**_ are are new items for translation. (On the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u), **New** means winning values that have changed since the last release.) + - † Among the _**Missing**_ are are new items for translation. (On the [Dashboard](/translation/getting-started/guide#h.bmzr9ejnlv1u), **New** means winning values that have changed since the last release.) -If you are working in a sub-locales (such as fr\_CA), coordinate with others on the Forum to work on each section after it is are done in the main locale (fr). That way you avoid additional work and gratuitous differences. See voting for inheritance vs. hard votes in [Survey Tool guide](https://cldr.unicode.org/translation/getting-started/guide).  +If you are working in a sub-locales (such as fr\_CA), coordinate with others on the Forum to work on each section after it is are done in the main locale (fr). That way you avoid additional work and gratuitous differences. See voting for inheritance vs. hard votes in [Survey Tool guide](/translation/getting-started/guide).  ### Survey Tool phase: Vetting -All contributors are encourage to move their focus to the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) view. Also see [Dashboard tip](https://cldr.unicode.org/translation/getting-started/vetting-view)s to use during Vetting stage. +All contributors are encourage to move their focus to the [Dashboard](/translation/getting-started/guide#h.bmzr9ejnlv1u) view. Also see [Dashboard tip](/translation/getting-started/vetting-view)s to use during Vetting stage. 1. Any [Flagged entries](https://st.unicode.org/cldr-apps/v#flagged///) in your locale may have questions in the Forum from TC members; please add additional information to help the TC resolve them. 1. To see the Flagged items, click on the **Menu** icon in the upper left corner, under the **Forum** header see **Flagged items**: 2. Open the Dashboard, and resolve all of the Errors, Provisional Items, Disputed items, and finish Reports - 1. Consider other's opinions, by reviewing the **Disputed** and the **Losing**. See guidelines for handling [Disputed](http://cldr.unicode.org/translation/getting-started/guide#TOC-Disputed) and [Losing](http://cldr.unicode.org/translation/getting-started/guide#TOC-Losing). -3. Review all open Requests and Discussions in the [Forums](https://cldr.unicode.org/translation/getting-started/guide#h.fx4wl2fl31az), and respond. + 1. Consider other's opinions, by reviewing the **Disputed** and the **Losing**. See guidelines for handling [Disputed](/translation/getting-started/guide#TOC-Disputed) and [Losing](/translation/getting-started/guide#TOC-Losing). +3. Review all open Requests and Discussions in the [Forums](/translation/getting-started/guide#h.fx4wl2fl31az), and respond. ### Resolution (Closed to vetters) -The vetting is done, and further work is being done by the CLDR committee to resolve problems. You should periodically take a couple of minutes to check your [Forums](https://cldr.unicode.org/translation/getting-started/guide#h.fx4wl2fl31az) to see if there are any questions about language-specific items that came up. +The vetting is done, and further work is being done by the CLDR committee to resolve problems. You should periodically take a couple of minutes to check your [Forums](/translation/getting-started/guide#h.fx4wl2fl31az) to see if there are any questions about language-specific items that came up. diff --git a/docs/site/translation/getting-started/vetting-view.md b/docs/site/translation/getting-started/vetting-view.md index 6732031f596..0caf45128d1 100644 --- a/docs/site/translation/getting-started/vetting-view.md +++ b/docs/site/translation/getting-started/vetting-view.md @@ -53,13 +53,13 @@ The following are legacy tools to review votes, but the Priority Items tool is d **Review:** Priority Items |Date/Time | Zones | Numbers -You can also see a video walkthrough of the review sections on [Walkthrough](https://cldr.unicode.org/index/survey-tool/walkthrough). +You can also see a video walkthrough of the review sections on [Walkthrough](/index/survey-tool/walkthrough). -The rest of this page discusses how to do the Priority Items. Once you have done the Priority Items, [Review reports](https://cldr.unicode.org/translation/getting-started/review-formats). +The rest of this page discusses how to do the Priority Items. Once you have done the Priority Items, [Review reports](/translation/getting-started/review-formats). Remember to periodically look at the Forum for your locale. -1. On any page in your locale, near the top there is a link "[Forum](https://cldr.unicode.org/translation/getting-started/guide#TOC-Forum)". +1. On any page in your locale, near the top there is a link "[Forum](/translation/getting-started/guide#TOC-Forum)". 2. Click on it and go through the comments. 3. If there is a request to change values or votes, either respond on the Forum with why you disagree, or change your vote. 4. Some issues may be general, such as the capitalization of language names. _In the vetting period, please try to resolve these in accordance with the other items in the locale for consistency; leave anything else for the next release._ @@ -118,7 +118,7 @@ Vetting Phase _Go through the summary list, clicking the checkbox (☑) to show the issues of type you're working on._ You can click several at once if you find that easier. That will then expose the issues of that type below the summary. -After the data submission phase, any differences in the submitted data will be resolved according to the [data resolution process](https://cldr.unicode.org/index/process#TOC-Data--Resolution). +After the data submission phase, any differences in the submitted data will be resolved according to the [data resolution process](/index/process#TOC-Data--Resolution). ### How to Handle @@ -134,13 +134,13 @@ Handle each of the types of issues as follows: 1. Go to the item (by clicking the **Fix?** link). 2. Error items will be removed from the release, so they are a priority in the vetting phase. -3. Review the warning items; most of them need fixing but not all. See [Fixing Errors and Warnings](https://cldr.unicode.org/translation/getting-started/errors-and-warnings) +3. Review the warning items; most of them need fixing but not all. See [Fixing Errors and Warnings](/translation/getting-started/errors-and-warnings) ### Losing\*, Disputed\* 1. See if the winning value is ok. If so, change your vote to it, and go to the next item. -2. Otherwise, post a message to the [Forum](https://cldr.unicode.org/translation/getting-started/guide#TOC-Forum). +2. Otherwise, post a message to the [Forum](/translation/getting-started/guide#TOC-Forum). 1. State why you think the item should be changed. 2. If there are a number of items that have the same characteristic (such as the wrong capitalization), you can make that case in a single posting rather than multiple ones. diff --git a/docs/site/translation/grammatical-inflection.md b/docs/site/translation/grammatical-inflection.md index f9f6b55cd24..ccb618a03a8 100644 --- a/docs/site/translation/grammatical-inflection.md +++ b/docs/site/translation/grammatical-inflection.md @@ -71,7 +71,7 @@ You do not have to supply the *sample phrase (column 4)* in the Survey Tool, but ### Minimal Pairs: Plurals and Ordinals -See [Plural Rules](https://cldr.unicode.org/index/cldr-spec/plural-rules) +See [Plural Rules](/index/cldr-spec/plural-rules) ## Units > Compound Units diff --git a/docs/site/translation/language-specific.md b/docs/site/translation/language-specific.md index f0ba3133f37..f3f07d2e251 100644 --- a/docs/site/translation/language-specific.md +++ b/docs/site/translation/language-specific.md @@ -6,7 +6,7 @@ title: Δ - Language Specific Guidance The following pages have guidance for specific languages: -- [Lakota](https://cldr.unicode.org/translation/language-specific/lakota) -- [Odia](https://cldr.unicode.org/translation/language-specific/odia) -- [Persian](https://cldr.unicode.org/translation/language-specific/persian) +- [Lakota](/translation/language-specific/lakota) +- [Odia](/translation/language-specific/odia) +- [Persian](/translation/language-specific/persian) diff --git a/docs/site/translation/miscellaneous-person-name-formats.md b/docs/site/translation/miscellaneous-person-name-formats.md index 23e00f9449d..97313b67e46 100644 --- a/docs/site/translation/miscellaneous-person-name-formats.md +++ b/docs/site/translation/miscellaneous-person-name-formats.md @@ -10,7 +10,7 @@ That guide is embedded below, but it may be easier just to open up the [Person N The main topics are: -- [Version 44 Changes](https://cldr.unicode.org/translation/miscellaneous-person-name-formats) — *this section is important; please read carefully.* +- [Version 44 Changes](/translation/miscellaneous-person-name-formats) — *this section is important; please read carefully.* - [Why do we need formatting for people’s names?](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.wqpdugycqnvg) - [Starting out](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.q7f5rnykj886) - [Name Order For Locales](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.xquzeu24o1qf) diff --git a/docs/site/translation/number-currency-formats.md b/docs/site/translation/number-currency-formats.md index e5e7336ba68..663b68fa3fb 100644 --- a/docs/site/translation/number-currency-formats.md +++ b/docs/site/translation/number-currency-formats.md @@ -4,7 +4,7 @@ title: Number & Currency formats # Number & Currency formats -- [Number & currency patterns](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns) -- [Number symbols](https://cldr.unicode.org/translation/number-currency-formats/number-symbols) -- [Other patterns](https://cldr.unicode.org/translation/number-currency-formats/other-patterns) +- [Number & currency patterns](/translation/number-currency-formats/number-and-currency-patterns) +- [Number symbols](/translation/number-currency-formats/number-symbols) +- [Other patterns](/translation/number-currency-formats/other-patterns) diff --git a/docs/site/translation/number-currency-formats/number-and-currency-patterns.md b/docs/site/translation/number-currency-formats/number-and-currency-patterns.md index 2909f2e78bf..2246c513574 100644 --- a/docs/site/translation/number-currency-formats/number-and-currency-patterns.md +++ b/docs/site/translation/number-currency-formats/number-and-currency-patterns.md @@ -8,11 +8,11 @@ title: Number and currency patterns Pre-requisite topics to read: -- [Number Symbols](https://cldr.unicode.org/translation/number-currency-formats/number-symbols) +- [Number Symbols](/translation/number-currency-formats/number-symbols) Numbers are formatted using patterns, like "#,###.00". For example, the pattern "#,###.00" when used to format the number 12345.678 could result in "12'345,67" if the grouping separator for your locale use an apostrophe ('), and the decimal separator is a comma (,). -Whenever any of these symbols are in the English pattern, they **must be retained** in the pattern for your locale. The positions of some of them (%, ¤) may be changed, or spaces added or removed. The symbols will be replaced by the local equivalents, using the [Number Symbols](https://cldr.unicode.org/translation/number-currency-formats/number-symbols) for your language. (See 💡 Helpful Tips below the table) +Whenever any of these symbols are in the English pattern, they **must be retained** in the pattern for your locale. The positions of some of them (%, ¤) may be changed, or spaces added or removed. The symbols will be replaced by the local equivalents, using the [Number Symbols](/translation/number-currency-formats/number-symbols) for your language. (See 💡 Helpful Tips below the table) | Type | Example pattern | Meaning | |---|:---:|---| @@ -112,7 +112,7 @@ When computer programs use CLDR, the number of decimals can be changed by comput - For example, the Japanese pattern for 1000 uses a zero digit because 1,000 is expressed with the character 千. This should be avoided wherever possible, however, since it may cause display issues on devices with small screens, such as mobile phones. - In some languages the text will inflect according to the number. For example, languages that write "1 million" but "2 millions". - The patterns do not allow for gender or case inflection, so use the most neutral form. - - Remember that these are number patterns, so literal characters like a period (".") must occur within quotation marks if they are not the placeholder standing for the decimal period. See [Pattern Characters](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns). + - Remember that these are number patterns, so literal characters like a period (".") must occur within quotation marks if they are not the placeholder standing for the decimal period. See [Pattern Characters](/translation/number-currency-formats/number-and-currency-patterns). - Compact decimal patterns do not require a "0" when there is a single word or a symbol that is unique. For example, in Hebrew and Somali, 4-digit-short-one gets formatted to a single word or symbol, without an extra digit. In a Somali example,1000 would be formatted to "Kun" and not "0 Kun" (in Somali, you would express 1000 as "Kun" not "1 Kun"). - However, this can **only** be done where the number is unique. For example, in French 4-digit-short-one (1000) is used to format not only 1K, but also 1.1K. If you supply a pattern with no digits, the user can't tell what the number is suppose to be. An error will occur if you try to do this. - There is a mechanism for special cases of exact matches. A special row can be added for your language for specific numbers, such as exactly 1, where the digits must be omitted. You would see a Code value of 4-digit-short-one, for example. If your language has such cases, please file a ticket to request adding them. @@ -120,7 +120,7 @@ When computer programs use CLDR, the number of decimals can be changed by comput ## Plural Forms of Numbers -Some languages have multiple plural forms for numbers, and will have multiple plural categories for each number. See [Plural Rules and Tool](https://cldr.unicode.org/translation/plurals#TOC-Rules-and-Tool) for numbers mapped to the various plural categories.  +Some languages have multiple plural forms for numbers, and will have multiple plural categories for each number. See [Plural Rules and Tool](/translation/plurals#TOC-Rules-and-Tool) for numbers mapped to the various plural categories.  X digit-one diff --git a/docs/site/translation/number-currency-formats/number-symbols.md b/docs/site/translation/number-currency-formats/number-symbols.md index acd4906eddf..9b30d2bd482 100644 --- a/docs/site/translation/number-currency-formats/number-symbols.md +++ b/docs/site/translation/number-currency-formats/number-symbols.md @@ -4,7 +4,7 @@ title: Number Symbols # Number Symbols -The following symbols are used to format numbers. The Approved symbols for the locale will be substituted for the placeholders described in [Number Patterns](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns).  +The following symbols are used to format numbers. The Approved symbols for the locale will be substituted for the placeholders described in [Number Patterns](/translation/number-currency-formats/number-and-currency-patterns).  For English regional locales (e.g. en\_DE) where English is not the primary language of the country/region (e.g. en\_DE; English as used in Germany), the number formats and date formats should follow the **English formatting usage** in that country/region. Often, the formatting usage in English tend to follow the British or American formatting rather than the formatting of the primary language. Consult with the English versions of prominent magazines or newspapers for guidance on date and number format usage. diff --git a/docs/site/translation/time-zones-and-city-names.md b/docs/site/translation/time-zones-and-city-names.md index 2a08b5ab3b2..56be82e78ca 100644 --- a/docs/site/translation/time-zones-and-city-names.md +++ b/docs/site/translation/time-zones-and-city-names.md @@ -10,7 +10,7 @@ Time zones (such as "Pacific Time" or "France Time") can be formatted in differe - "metazone" names, such as "Pacific Time" or "Pacific Standard Time", that can apply to segments of a country or groups of countries. - location (country or city) based names, such as "Paris Time" or "Japan Standard Time" - - These are constructed using patterns (see below), plus [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) and City Names. + - These are constructed using patterns (see below), plus [Country/Region Names](/translation/displaynames/countryregion-territory-names) and City Names. - When a "metazone" name is absent, a location based name is used as a fallback. - raw offsets, like "GMT+10:00" - These are constructed using patterns (see below). @@ -74,5 +74,5 @@ The city name may also be used in formatted times, such as: **Unique Names** -City names must be unique. See [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) for techniques. +City names must be unique. See [Country/Region Names](/translation/displaynames/countryregion-territory-names) for techniques. diff --git a/docs/site/translation/translation-guide-general.md b/docs/site/translation/translation-guide-general.md index ccc16026f24..8b244d85df3 100644 --- a/docs/site/translation/translation-guide-general.md +++ b/docs/site/translation/translation-guide-general.md @@ -4,8 +4,8 @@ title: General translation Guide # General translation Guide -- [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) -- [Default Content](https://cldr.unicode.org/translation/translation-guide-general/default-content) -- [References](https://cldr.unicode.org/translation/translation-guide-general/references) +- [Capitalization](/translation/translation-guide-general/capitalization) +- [Default Content](/translation/translation-guide-general/default-content) +- [References](/translation/translation-guide-general/references) diff --git a/docs/site/translation/translation-guide-general/default-content.md b/docs/site/translation/translation-guide-general/default-content.md index 684fbe8e935..19ee52524f1 100644 --- a/docs/site/translation/translation-guide-general/default-content.md +++ b/docs/site/translation/translation-guide-general/default-content.md @@ -12,7 +12,7 @@ Each language \+ script combination is treated as a unit. (i.e. People do not mi If a language is ***not*** typically written in multiple scripts, then the script sub\-tag is omitted. For example, en\_US or ko\_KR. -Locales may also have regional variants. For example, English (US) \[en\_US] vs English (UK) \[en\_GB], or Serbian (Cyrillic, Montenegro) \[sr\_Cyrl\_ME] vs Serbian (Cyrillic, Serbia) \[sr\_Cyrl\_RS]. Regions may be countries such as China \[CN], parts of countries such as Hong Kong \[HK] or multi\-country regions such as Latin America \[419]. Also see [Regional Variants](http://cldr.unicode.org/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-). +Locales may also have regional variants. For example, English (US) \[en\_US] vs English (UK) \[en\_GB], or Serbian (Cyrillic, Montenegro) \[sr\_Cyrl\_ME] vs Serbian (Cyrillic, Serbia) \[sr\_Cyrl\_RS]. Regions may be countries such as China \[CN], parts of countries such as Hong Kong \[HK] or multi\-country regions such as Latin America \[419]. Also see [Regional Variants](/translation/getting-started/guide#TOC-Regional-Variants-also-known-as-Sub-locales-). The contents for the base language should be as widely usable (neutral) as possible, but **must be** usable without modification for its *default content locale;* this is the locale for the language’s *default region,* which is typically the region with the most speakers of the language. A default content locale has no data other than identity information, it inherits all data from its parent. diff --git a/docs/site/translation/unique-translations.md b/docs/site/translation/unique-translations.md index 154824114ca..73f6028365c 100644 --- a/docs/site/translation/unique-translations.md +++ b/docs/site/translation/unique-translations.md @@ -6,7 +6,7 @@ title: Unique Translations See the following based on the type of translation -- [Points dots and pixels](https://cldr.unicode.org/translation/units/unit-names-and-patterns) -- [Unique Emoji and Symbol Names](https://cldr.unicode.org/translation/characters/short-names-and-keywords) - - [Unique Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names#h.xkmg2o42dw29) (This is on the Country/Region page, but is the most general discussion). +- [Points dots and pixels](/translation/units/unit-names-and-patterns) +- [Unique Emoji and Symbol Names](/translation/characters/short-names-and-keywords) + - [Unique Names](/translation/displaynames/countryregion-territory-names#h.xkmg2o42dw29) (This is on the Country/Region page, but is the most general discussion). diff --git a/docs/site/translation/units.md b/docs/site/translation/units.md index 10ee380b396..c94dc030e42 100644 --- a/docs/site/translation/units.md +++ b/docs/site/translation/units.md @@ -4,6 +4,6 @@ title: Units # Units -- [Measurement systems](https://cldr.unicode.org/translation/units/measurement-systems) -- [Unit Names and Patterns](https://cldr.unicode.org/translation/units/unit-names-and-patterns) +- [Measurement systems](/translation/units/measurement-systems) +- [Unit Names and Patterns](/translation/units/unit-names-and-patterns) diff --git a/docs/site/translation/units/unit-names-and-patterns.md b/docs/site/translation/units/unit-names-and-patterns.md index 6978dd934df..7c094dbecfe 100644 --- a/docs/site/translation/units/unit-names-and-patterns.md +++ b/docs/site/translation/units/unit-names-and-patterns.md @@ -26,7 +26,7 @@ Note that if in your locale certain abbreviations are always understood to mean ## Simple Units -Simple units are cases like "{0} mile" or "{0} miles". These have from 1 to 6 [plural forms](https://cldr.unicode.org/translation/getting-started/plurals), depending on the language. Units also have a display name, such as "miles", used as labels in interfaces. +Simple units are cases like "{0} mile" or "{0} miles". These have from 1 to 6 [plural forms](/translation/getting-started/plurals), depending on the language. Units also have a display name, such as "miles", used as labels in interfaces. ## Compound Units