CLDR-18888 Change incorrect ISO 636 references to ISO 639 (#4970)

Author: DavidLRowe

docs/site/_redirects

@@ -11,3 +11,6 @@
 # pages that were renamed [CLDR-17977]
 /index/cldr-spec/unicode-transliteration-guidelines* /index/cldr-spec/transliteration-guidelines
 /index/bug-reports* /requesting_changes
+
+# page that was renamed [CLDR-18888]
+/development/development-process/design-proposals/iso-636-deprecation-requests-draft* /development/development-process/design-proposals/iso-639-deprecation-requests-draft

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

@@ -50,7 +50,7 @@ In each proposal, please add a header and a TOC if it is longer than a page. You
 
 [Islamic Calendar Types](/development/development-process/design-proposals/islamic-calendar-types)
 
-[ISO 636 Deprecation Requests - DRAFT](/development/development-process/design-proposals/iso-636-deprecation-requests-draft)
+[ISO 639 Deprecation Requests - DRAFT](/development/development-process/design-proposals/iso-639-deprecation-requests-draft)
 
 [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)
 

docs/site/development/development-process/design-proposals/bcp-47-changes-draft.md

@@ -70,8 +70,8 @@ Macrolanguage Table
 | Norwegian ' no ' | Norwegian Bokmal ' nob ' = nb | To regularize, we may want to switch in CLDR from nb as the 'norm' to no. |
 | Serbo-croatian ' sh ' |  | *This is a complex situation, and we'll probably leave as is.* |
 | Kurdish 'ku' | Northern Kurdish 'kmr'? | We probably want to change the default content locale to ku-Latn |
-| Akan ' ak ' | Twi ' tw ' and Fanti ' fat' | This appears to be a mistake in ISO 639. See: ISO 636 Deprecation Requests . |
-| Persian  fas (fa) | Western Farsi pes and prs Dari | This appears to be a mistake in ISO 639. See: ISO 636 Deprecation Requests . |
+| Akan ' ak ' | Twi ' tw ' and Fanti ' fat' | This appears to be a mistake in ISO 639. See: ISO 639 Deprecation Requests . |
+| Persian  fas (fa) | Western Farsi pes and prs Dari | This appears to be a mistake in ISO 639. See: ISO 639 Deprecation Requests . |
 
 These would also go into the \<alias> element of the supplemental metadata. We may add more such aliases over time, as we find new predominant forms. Note that we still need to offer both aliases for translation in many cases. For example, we want to show both 'no' and 'nb'.
 

docs/site/development/development-process/design-proposals/iso-636-deprecation-requests-draft.md renamed to docs/site/development/development-process/design-proposals/iso-639-deprecation-requests-draft.md

@@ -1,8 +1,8 @@
 ---
-title: ISO 636 Deprecation Requests - DRAFT
+title: ISO 639 Deprecation Requests - DRAFT
 ---
 
-# ISO 636 Deprecation Requests - DRAFT
+# ISO 639 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](/index/cldr-spec/picking-the-right-language-code) and [Language Distance Data](/development/development-process/design-proposals/language-distance-data).
 

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](/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 639 Deprecation Requests - DRAFT](/development/development-process/design-proposals/iso-639-deprecation-requests-draft)
 
 \<languageDistances>
 

docs/site/development/updating-codes/external-version-metadata.md

@@ -17,7 +17,7 @@ title: Updating External Version Metadata
 | UN literacy data | [un_literacy.csv](https://github.com/unicode-org/cldr/blob/master/tools/java/org/unicode/cldr/util/data/external/un_literacy.csv) | Date at top | 2012-08 |
 | Worldbank data | [world_bank_data.csv](https://github.com/unicode-org/cldr/blob/master/tools/java/org/unicode/cldr/util/data/external/world_bank_data.csv) | Date at bottom | 2020-12-16 |
 | Factbook data | [factbook_population.txt](https://github.com/unicode-org/cldr/blob/master/tools/java/org/unicode/cldr/util/data/external/factbook_population.txt) | record when downloaded in TBD |   |
-| ISO 636 (language) data | [iso-639-3-version.tab](https://github.com/unicode-org/cldr/blob/master/tools/java/org/unicode/cldr/util/data/iso-639-3-version.tab) | Date in YYYYMMDD format | 2021-02-02 |
+| ISO 639 (language) data | [iso-639-3-version.tab](https://github.com/unicode-org/cldr/blob/master/tools/java/org/unicode/cldr/util/data/iso-639-3-version.tab) | Date in YYYYMMDD format | 2021-02-02 |
 | ISO subdivision codes | iso subdivision codes | record when downloaded  in TBD |   |
 | ISO subdivision names | iso subdivision names | record when downloaded  in TBD |   |
 | ISO currency data | iso currency data | record when downloaded  in TBD |   |

docs/site/index/cldr-spec/picking-the-right-language-code.md

@@ -76,11 +76,11 @@ Note that the CLDR likely subtag data is used to minimize scripts and regions, *
 
 In some cases, systems (or companies) may have different conventions than the Preferred\-Values in BCP 47 \-\- such as those in the Replacement column in the the [online language identifier](http://unicode.org/cldr/utility/languageid.jsp) demo. For example, for backwards compatibility, 'iw' is used with Java instead of 'he' (Hebrew). Be aware of these compatibility issues when picking the subtags. *If a target system uses a different canonical form for locale IDs than CLDR, the CLDR data needs to be processed by remapping its IDs to those of the target system.*
 
-For compatibility, it is strongly recommended that all implementations accept both the preferred values and their alternates: for example, both 'iw' and 'he'. Although BCP 47 itself only allows "\-" as a separator, Unicode language identifiers allows both "\-" and "\_" for compatibility reasons. Implementations should also accept both.
+For compatibility, it is strongly recommended that all implementations accept both the preferred values and their alternates: for example, both 'iw' and 'he'. Although BCP 47 itself only allows "\-" as a separator, Unicode language identifiers allow both "\-" and "\_" for compatibility reasons. Implementations should also accept both.
 
 ### 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'. See also: [ISO 636 Deprecation Requests](/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'. See also: [ISO 639 Deprecation Requests](/development/development-process/design-proposals/iso-639-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.
 
@@ -99,3 +99,4 @@ Wikipedia is also a great source of information, but it must be approached with
 
 
 
+

docs/site/sitemap.tsv

@@ -204,7 +204,7 @@ index
 			development/development-process/design-proposals/hebrew-months
 			development/development-process/design-proposals/index-characters
 			development/development-process/design-proposals/islamic-calendar-types
-			development/development-process/design-proposals/iso-636-deprecation-requests-draft
+			development/development-process/design-proposals/iso-639-deprecation-requests-draft
 			development/development-process/design-proposals/json-packaging-approved-by-the-cldr-tc-on-2015-03-25
 			development/development-process/design-proposals/language-data-consistency
 			development/development-process/design-proposals/language-distance-data