CLDR-17999 site: fix some markdown links from https://cldr.unicode.org (

#4109)

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:
 

docs/site/development/adding-locales.md

@@ -4,15 +4,15 @@ 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
 
 If you are just adding a new country locale (eg we have a locale for the language), you just need to add the new empty locale file, and Update Survey Tool. Otherwise:
 
 ### 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)

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
 

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 <http://cldr.unicode.org/index/charts> 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

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).

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.
 

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.
 

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** <br>
+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** <br>
 (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\<String\> ***CLDR\_VERSIONS*** \= ImmutableList.of(

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]***