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

docs/site/development/development-process/design-proposals/xmb.md

@@ -1,7 +1,9 @@
 ---
-title: XMB
+title: XMB (OBSOLETE)
 ---
 
+# OBSOLETE
+
 # XMB
 
 ### Introduction
@@ -170,5 +172,3 @@ other {# weeks}}}}</msg>
 - Do the conversion from xtb into cldr format to make sure we roundtrip.
 - Figure out how to do the differences between HH and hh, etc.
     - Current thoughts: don't let the translator choose, but make it part of the xtb-cldr processing.
-
-

docs/site/index/cldr-spec.md

@@ -9,7 +9,7 @@ title: CLDR Specifications
 - [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
+- [Coverage Levels](/index/cldr-spec/coverage-levels) - Detailed descriptions of the data required for a language to be considered supported at a specific level
 - [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

docs/site/index/survey-tool/faq-and-known-bugs.md

@@ -20,7 +20,7 @@ A. You need to remove "(other)" or the equivalent from language names. In genera
 
 A. The performance of the Survey Tool has been greatly improved compared to previous versions. However, we are constantly striving to improve performance and our ability to accommodate a larger user base.
 
-If you feel a task is taking an unusual amount of time, and it is a consistent problem, please please file a bug at [newticket](http://unicode.org/cldr/trac/newticket). In the ticket, describe exactly what operation is being attempted and approximately how long it is taking to receive a response.
+If you feel a task is taking an unusual amount of time, and it is a consistent problem, please [file a ticket](/requesting_changes#how-to-file-a-ticket). In the ticket, describe exactly what operation is being attempted and approximately how long it is taking to receive a response.
 
 ***Q. How are votes weighted and the "best" item picked?***
 
@@ -67,5 +67,5 @@ The following are general known bugs and issues. For known issues in the current
 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.
 
-If you find additional problems, please [file a ticket](http://unicode.org/cldr/trac/newticket).
+If you find additional problems, please [file a ticket](/requesting_changes#how-to-file-a-ticket).
 

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](http://unicode.org/cldr/trac/newticket).
+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).
 
 There are three types of accounts:
 

docs/site/translation.md

@@ -145,7 +145,7 @@ This list will be updated as fixes are made available in Survey Tool Production.
 1. [CLDR-17694](https://unicode-org.atlassian.net/browse/CLDR-17694) - Back button in browser fails in forum under certain conditions
 2. [CLDR-17693](https://unicode-org.atlassian.net/browse/CLDR-17693) SurveyTool fatal in getDBConnection
 3. [CLDR-17658](https://unicode-org.atlassian.net/browse/CLDR-17658) - Dashboard slowness
-4. Images for the plain symbols. Non-emoji such as [€](https://cldr-smoke.unicode.org/smoketest/v#/fr/Symbols2/47925556fd2904b5), √, », ¹, §, ... do not have images in the Info Panell. \[[CLDR-13477](https://unicode-org.atlassian.net/browse/CLDR-13477)\]**Workaround**: Look at the Code column; unlike the new emoji, your browser should display them there.
+4. Images for the plain symbols. Non-emoji such as [€](https://st.unicode.org/cldr-apps/v#/fr/OtherSymbols/47925556fd2904b5), √, », ¹, §, ... do not have images in the Info Panell. \[[CLDR-13477](https://unicode-org.atlassian.net/browse/CLDR-13477)\]**Workaround**: Look at the Code column; unlike the new emoji, your browser should display them there.
 5. [CLDR-17683](https://unicode-org.atlassian.net/browse/CLDR-17683) - Some items are not able to be flagged for TC review. This is being investigated.Meanwhile, Please enter forum posts meanwhile with any comments.
 
 ## Resolved Issues

docs/site/translation/characters/short-names-and-keywords.md

@@ -47,11 +47,11 @@ Many of the emoji names are constructed, which means that in implementations emo
 	2. Hover over the ⓔ to see how some sample constructed emoji would look in English.
 	![image](../../images/Screenshot-2024-06-21-at-7.38.34.png)
 3. **Characters\Category** contain terms like “flag” (used in constructing flag names). These 3 terms are also marked with ⓔ, so make sure to review each of the examples in English and your language.
-4. **Blond/Bearded.** The people with blond hair or beards need to have names consistent with those used for hair styles (see [dark skin tone examples](https://cldr-smoke.unicode.org/cldr-apps/v#/USER/Component/4da6f737d7901c30)), such as:
-	1. [🧔 — man: beard](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/People/20a49c6ad428d880)
-	2. [👱 — person: blond hair](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/People/5cae8a8d1de49cd9)
-	3. [👱‍♂️ — man: blond hair](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/People/532f430d6e2a26f)
-	4. [👱‍♀️ — woman: blond hair](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/People/3f3d3e9ef4f5768b)
+4. **Blond/Bearded.** The people with blond hair or beards need to have names consistent with those used for hair styles (see [dark skin tone examples](https://st.unicode.org/cldr-apps/v#/USER/Component/4da6f737d7901c30)), such as:
+	1. [🧔 — man: beard](https://st.unicode.org/cldr-apps/v#/fr/People/20a49c6ad428d880)
+	2. [👱 — person: blond hair](https://st.unicode.org/cldr-apps/v#/fr/People/5cae8a8d1de49cd9)
+	3. [👱‍♂️ — man: blond hair](https://st.unicode.org/cldr-apps/v#/fr/People/532f430d6e2a26f)
+	4. [👱‍♀️ — woman: blond hair](https://st.unicode.org/cldr-apps/v#/fr/People/3f3d3e9ef4f5768b)
 
 ## FAQ Tips for character names and keywords
 

docs/site/translation/units/unit-names-and-patterns.md

@@ -36,8 +36,8 @@ Some units are compound units, like "miles per hour". When formatting, software
 |---|---|---|---|
 | **per** | {0} per {1} | **cm** / **s** , **centimeters** per **second** | Used to compose units consisting of a division of two source units when there is no specialized pattern available. See [perUnitPatterns](https://www.unicode.org/reports/tr35/tr35-general.html#perUnitPatterns). |
 | **times** | {0}-{1} | kW⋅h, kilowatt-hour | Used to compose units consisting of a multiplication of two source units when there is no specialized pattern available. See [kilowatt hour](https://en.wikipedia.org/wiki/Kilowatt-hour) . |
-| **power** (square, cubic) | square {0} | square **meters** | - Used to compose area or volume measures when there is no specialized pattern available. The width should correspond to the base unit's width, as in [{0} square meter](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/Area/5888c3421f06626c) or [{0} m²](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/Area/6b88ccc5db865200).<br /> - The short form will typically be superscripts {0}² or {0}³; the long form may be the same or may be spelled out (as in English).<br /> - The long form should be spelled out. See Long Power.<br /> - Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Quadrat{0}. |
-| **prefix** (milli-, kilo-,…) | milli{0} | milli **meter** | - Used to compose **metric** units when there is no specialized pattern available.<br /> - The width should correspond to the base unit's width, as in [{0} decimeter](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/Length/ce4591152ece6f2) or [{0} dm](https://cldr-smoke.unicode.org/cldr-apps/v#/fr/Length/1f1b7ef47cfaee78).<br /> - Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Milli{0}.<br /> - There are two different sets of prefixes:<br />&nbsp;&nbsp; - The standard prefixes are base 10, such as [mega{0}](https://st.unicode.org/cldr-apps/v#/USER/CompoundUnits/2ac0c0f7d5fff965) = ×10⁶ = ×1,000,000.<br />&nbsp;&nbsp; - The  binary  prefixes are base 1024, such as [mebi{0}](https://st.unicode.org/cldr-apps/v#/fr/CompoundUnits/61ea5a846717f829) = ×1024² = ×1,048,576. There are only a few of these, and they are only used with digital units such as byte or bit. See [Mebibyte](https://en.wikipedia.org/wiki/Byte#Multiple-byte_units) for more information. |
+| **power** (square, cubic) | square {0} | square **meters** | - Used to compose area or volume measures when there is no specialized pattern available. The width should correspond to the base unit's width, as in [{0} square meter](https://st.unicode.org/cldr-apps/v#/fr/Area/5888c3421f06626c) or [{0} m²](https://st.unicode.org/cldr-apps/v#/fr/Area/6b88ccc5db865200).<br /> - The short form will typically be superscripts {0}² or {0}³; the long form may be the same or may be spelled out (as in English).<br /> - The long form should be spelled out. See Long Power.<br /> - Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Quadrat{0}. |
+| **prefix** (milli-, kilo-,…) | milli{0} | milli **meter** | - Used to compose **metric** units when there is no specialized pattern available.<br /> - The width should correspond to the base unit's width, as in [{0} decimeter](https://st.unicode.org/cldr-apps/v#/fr/Length_Metric/ce4591152ece6f2) or [{0} dm](https://st.unicode.org/cldr-apps/v#/fr/Length_Metric/1f1b7ef47cfaee78).<br /> - Note that the base unit will be lowercased when there is no spacing around the {0}. Thus {0} Meter will be lowercased when composed with Milli{0}.<br /> - There are two different sets of prefixes:<br />&nbsp;&nbsp; - The standard prefixes are base 10, such as [mega{0}](https://st.unicode.org/cldr-apps/v#/USER/CompoundUnits/2ac0c0f7d5fff965) = ×10⁶ = ×1,000,000.<br />&nbsp;&nbsp; - The  binary  prefixes are base 1024, such as [mebi{0}](https://st.unicode.org/cldr-apps/v#/fr/CompoundUnits/61ea5a846717f829) = ×1024² = ×1,048,576. There are only a few of these, and they are only used with digital units such as byte or bit. See [Mebibyte](https://en.wikipedia.org/wiki/Byte#Multiple-byte_units) for more information. |
 
 Using these patterns, names for complex units can be formed, such as *gigawatt hour per square second*. In common cases, these complex units will have an explicit translation that you supply such as [kilowatt-hour](https://st.unicode.org/cldr-apps/v#/USER/EnergyPower/49796c300ae2d104). But for less common cases, the components will be used to form units, and you need to make sure that they are consistent.