CLDR-18072 Clean up links in CLDR site (#4180)

docs/site/downloads/cldr-45.md

@@ -10,7 +10,7 @@ title: CLDR 45 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](https://www.google.com/url?q=http://cldr.unicode.org/index%23TOC-Who-uses-CLDR-&sa=D&source=editors&ust=1713652058779208&usg=AOvVaw3r8kLAP0U8srdRrX-YUWlu) (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#who-uses-cldr) (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.
 
 CLDR 45 is a closed release with no submission period, focusing on just a few areas:
 
@@ -65,7 +65,7 @@ For a full listing, see [Delta DTDs](https://unicode.org/cldr/charts/45/suppleme
 -   Metazone changes
     -   For deprecations and Greenland changes, see the supplemental data delta chart.
 
-For a full listing, see [¤¤BCP47 Delta](https://www.google.com/url?q=https://unicode.org/cldr/charts/45/delta/bcp47.html&sa=D&source=editors&ust=1713652058784981&usg=AOvVaw02X97tSG45_oChn55f3Gjw) and [¤¤Supplemental Delta](https://www.google.com/url?q=https://unicode.org/cldr/charts/45/delta/supplemental-data.html&sa=D&source=editors&ust=1713652058785221&usg=AOvVaw2OKxgUzfQepGGrI7DGbMFt)
+For a full listing, see [¤¤BCP47 Delta](https://unicode.org/cldr/charts/45/delta/bcp47.html) and [¤¤Supplemental Delta](https://unicode.org/cldr/charts/45/delta/supplemental-data.html)
 
 ### [Locale Changes](https://unicode.org/cldr/charts/45/delta/index.html)
 

docs/site/downloads/previous-releases.md

@@ -4,4 +4,4 @@ title: Previous Releases
 
 # Previous Releases
 
-This section lists recent release pages. For a full listing, see [CLDR Releases/Downloads](../index/downloads.md#cldr-releasesdownloads).
+This section lists recent release pages. For a full listing, see [CLDR Releases/Downloads](/index/downloads#cldr-releasesdownloads).

docs/site/index/charts.md

@@ -38,5 +38,5 @@ Other Data
 -   **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](/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](/requesting_changes).
 

docs/site/index/cldr-spec/coverage-levels.md

@@ -8,7 +8,7 @@ There are four main coverage levels as defined in the [UTS \#35: Unicode Locale
 
 ## Usage
 
-You can use the file **common/properties/coverageLevels.txt** (added in v41\) for a given release to filter the locales that they support. For example, see [coverageLevels.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/coverageLevels.txt). (This and other links to data files are to the development versions; see the specific version for the release you are working with.) For a detailed chart of the coverage levels, see the [locale\_coverage.html](https://unicode-org.github.io/cldr-staging/charts/43/supplemental/locale_coverage.html) file for the respective release.
+You can use the file **common/properties/coverageLevels.txt** (added in v41\) for a given release to filter the locales that they support. For example, see [coverageLevels.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/coverageLevels.txt). (This and other links to data files are to the development versions; see the specific version for the release you are working with.) For a detailed chart of the coverage levels, see the [locale\_coverage.html](https://www.unicode.org/cldr/charts/latest/supplemental/locale_coverage.html) file for the respective release.
 
 The file format is semicolon delimited, with 3 fields per line.
 
@@ -101,7 +101,7 @@ The data for the Modern Level includes:
 
 ## References
 
-For the coverage in the latest released version of CLDR, see [Locale Coverage Chart](https://unicode-org.github.io/cldr-staging/charts/latest/supplemental/locale_coverage.html).
+For the coverage in the latest released version of CLDR, see [Locale Coverage Chart](https://www.unicode.org/cldr/charts/latest/supplemental/locale_coverage.html).
 
 To see the development version of the rules used to determine coverage, see [coverageLevels.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/coverageLevels.xml). For a list of the locales at a given level, see [coverageLevels.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/coverageLevels.txt). 
 

docs/site/index/cldr-spec/transliteration-guidelines.md

@@ -6,7 +6,7 @@ title: Unicode Transliteration Guidelines
 
 ## Introduction
 
-*This document describes guidelines for the creation and use of CLDR transliterations. Please file any feedback on this document or those charts at [Locale Bugs](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md).*
+*This document describes guidelines for the creation and use of CLDR transliterations. Please file any feedback on this document or those charts at [Locale Bugs](/requesting_changes).*
 
 Transliteration is the general process of converting characters from one script to another, where the result is roughly phonetic for languages in the target script. For example, "Phobos" and "Deimos" are transliterations of Greek mythological "Φόβος" and "Δεῖμος" into Latin letters, used to name the moons of Mars.
 

docs/site/index/json-format-data.md

@@ -4,7 +4,7 @@ title: JSON Format Data
 
 # JSON Format Data
 
-**This page is out of date, see** [**CLDR Releases/Downloads: JSON Data**](https://www.google.com/url?q=https%3A%2F%2Fcldr.unicode.org%2Findex%2Fdownloads%23h.nosb01ot1guy&sa=D&sntz=1&usg=AOvVaw3XYfzHnHlYw0KHy-Or9-bW) **for details of the JSON data.**
+**This page is out of date, see** [**CLDR Releases/Downloads: JSON Data**](https://cldr.unicode.org/index/downloads#json-data) **for details of the JSON data.**
 
 The CLDR Technical Committee is pleased to announce a preliminary publishing of the CLDR 22.1 main and supplemental data in JSON format.
 
@@ -16,5 +16,5 @@ The CLDR committee welcomes comments on this specification and the data itself.
 
 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)
+To access the CLDR 22.1 data in the JSON format, click [HERE](https://home.unicode.org/basic-info/projects/#!/repos/cldr-aux/json/22.1/)
 

docs/site/index/language-support-levels.md

@@ -8,7 +8,7 @@ People often ask whether some device or application supports their language. Thi
 
 This page defines a common set of terminology for language support levels for platforms such as operating systems, browsers, etc. The goal is to have consistent terminology so that people can clearly indicate the level of support for a given language.
 
-The focus here is on the incremental changes necessary to add a language to a platform that is already a Unicode-Enabled Platform. Note that the term 'language' is used for familiarity, but what needs to be supported are [locales](https://www.google.com/url?q=https://unicode-org.github.io/cldr/ldml/tr35.html%23Unicode_Language_and_Locale_Identifiers&sa=D&source=editors&ust=1717551026933717&usg=AOvVaw3RPCbCtWzpEK4qpEXVzEtJ).
+The focus here is on the incremental changes necessary to add a language to a platform that is already a Unicode-Enabled Platform. Note that the term 'language' is used for familiarity, but what needs to be supported are [locales](https://unicode-org.github.io/cldr/ldml/tr35.html#Unicode_Language_and_Locale_Identifiers).
 
 ## Support Levels
 
@@ -64,7 +64,7 @@ There are several general characteristics of languages, based on the kinds of te
     - *Examples of large exemplar set languages: Japanese, Chinese, Korean*
 - **Display Complexity** - The glyphs used to represent a string of characters in the language are context-dependent; sequence of glyphs is not simply a 1:1 match to the sequence of characters, and the glyph for a character may be very different depending on what characters are around it. A language written right to left (aka Bidi) also has a complex display.
     - *Examples of complex display languages: Hindi, Tamil; Arabic, Hebrew*
-- **Degree of [Inflection](https://www.google.com/url?q=https://en.wikipedia.org/wiki/Inflection&sa=D&source=editors&ust=1717551026943395&usg=AOvVaw0JeJix-GF_O0Hl8E0MmoSQ)** - very roughly, how much words in the language need to change form depending on context. Typically the most important feature for message support.
+- **Degree of [Inflection](https://en.wikipedia.org/wiki/Inflection)** - very roughly, how much words in the language need to change form depending on context. Typically the most important feature for message support.
     - *Examples of highly inflected languages: Most Slavic languages (eg, Czech), some Indo-Aryan languages (eg, Marathi), Arabic, Finnish, Turkish*
 
 In general, the smaller the exemplar set, the simpler the display, and the fewer inflections, the easier it is to support a language on computers. However, when a platform or application is already able to handle a language with a certain set of characteristics, it is much easier to add other languages with those characteristics. So in general, if a platform handles a spread of languages like Japanese, Tamil, Arabic, Russian, and Turkish, it is easier to add support for other languages.

docs/site/index/locale-coverage.md

@@ -6,7 +6,7 @@ title: Locale Coverage Special Data
 
 ## Missing Features
 
-The following may be listed as Missing features in a Locale Coverage chart, such as [v45 Locale Coverage](https://www.unicode.org/cldr/charts/45/supplemental/locale_coverage.html).
+The following may be listed as Missing features in a Locale Coverage chart, such as [Latest Locale Coverage](https://www.unicode.org/cldr/charts/latest/supplemental/locale_coverage.html).
 
 ### Core
 

docs/site/index/requesting-additionsupdates-to-cldr-languagepopulation-data.md

@@ -26,9 +26,9 @@ Requests to add or change language/population data must provide the following ba
 - links to reliable sources for population/literacy data
 
 
-Reliable sources for population data and official status are required for population updates and additions. While [Ethnologue](https://www.google.com/url?q=https%3A%2F%2Fwww.ethnologue.com%2F&sa=D&sntz=1&usg=AOvVaw02Rajsyksb8nOu8MESVtKi) may be a good source for "mother tongue" or native speaker data for more common languages, it is not a sufficient source on its own for population data on most languages. Recent government or NGO-sponsored census data are typically better sources.
+Reliable sources for population data and official status are required for population updates and additions. While [Ethnologue](https://www.ethnologue.com/) may be a good source for "mother tongue" or native speaker data for more common languages, it is not a sufficient source on its own for population data on most languages. Recent government or NGO-sponsored census data are typically better sources.
 
-For language names and codes, some resources are: [Unicode CLDR charts](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Fcldr%2Fcharts%2Flatest%2F&sa=D&sntz=1&usg=AOvVaw0IfeZJzXzVdSLQDbkyoE4x), [IANA Language Subtag Registry](https://www.google.com/url?q=https%3A%2F%2Fwww.iana.org%2Fassignments%2Flanguage-subtag-registry%2Flanguage-subtag-registry&sa=D&sntz=1&usg=AOvVaw0KaE5Pb3Bfy7xyMSIiNrbi), and [Wikipedia](https://www.google.com/url?q=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMain_Page&sa=D&sntz=1&usg=AOvVaw1NobdoSkQ4MRb3AWb_nNp3) articles on individual languages.
+For language names and codes, some resources are: [Unicode CLDR charts](https://www.unicode.org/cldr/charts/46/), [IANA Language Subtag Registry](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry), and [Wikipedia](https://en.wikipedia.org/wiki/Main_Page) articles on individual languages.
 
 Also for new additions, the request must include a rationale for inclusion and discuss the importance of the addition.
 

docs/site/index/survey-tool.md

@@ -20,7 +20,7 @@ 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](/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](/requesting_changes/adding-new-locales).
 
 ### Guide
 

docs/site/index/survey-tool/survey-tool-accounts.md

@@ -8,7 +8,7 @@ title: Survey Tool Accounts
 
 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.
 
-To determine whether you need an account for what you want to do, see [When Do You Need a Survey Tool Account?](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#when-to-fix-in-survey-tool) If you only wish to report a bug, you may be able to simply [file a ticket](/requesting_changes#how-to-file-a-ticket).
+To determine whether you need an account for what you want to do, see [When Do You Need a Survey Tool Account?](/requesting_changes#when-to-fix-in-survey-tool) If you only wish to report a bug, you may be able to simply [file a ticket](/requesting_changes#how-to-file-a-ticket).
 
 There are three types of accounts:
 
@@ -17,9 +17,9 @@ There are three types of accounts:
 - 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).
+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](/requesting_changes/adding-new-locales) under [CLDR Change Requests](/requesting-changes).
 
 ## Logging in
 
-Once you have an account, open the [Unicode CLDR Survey Tool](http://unicode.org/cldr/apps/survey), click the 'Login' button and fill in your email address and password.
+Once you have an account, open the [Unicode CLDR Survey Tool](https://st.unicode.org), click the 'Login' button and fill in your email address and password.
 

docs/site/translation/getting-started/plurals.md

@@ -10,7 +10,7 @@ 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](/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](/requesting_changes) if you see a form in the Survey Tool that is not expected in your language.
 
 ![image](../../images/French-plural.PNG)