CLDR-18161 update links to use "latest" not specific version (#4983)

DavidLRowe · web-flow · commit e50d8df475e1 · 2025-09-17T07:30:50.000-08:00
diff --git a/docs/ldml/tr35-dates.md b/docs/ldml/tr35-dates.md
@@ -1361,7 +1361,7 @@ The dayPeriodRule may span two days, such as where **night1** is [21:00, 06:00).
 
 If rounding is done—including the rounding done by the time format—then it needs to be done before the dayperiod is computed, so that the correct format is shown.
 
-For examples, see [Day Periods Chart](https://www.unicode.org/cldr/charts/46/supplemental/day_periods.html).
+For examples, see [Day Periods Chart](https://www.unicode.org/cldr/charts/latest/supplemental/day_periods.html).
 
 ## <a name="Time_Zone_Names" href="#Time_Zone_Names">Time Zone Names</a>
 
diff --git a/docs/ldml/tr35-info.md b/docs/ldml/tr35-info.md
@@ -108,7 +108,7 @@ The LDML specification is divided into the following parts:
 
 ## Introduction <a name="Supplemental_Data" href="#Supplemental_Data">Supplemental Data</a>
 
-The following represents the format for additional supplemental information. This is information that is important for internationalization and proper use of CLDR, but is not contained in the locale hierarchy. It is not localizable, nor is it overridden by locale data. The current CLDR data can be viewed in the [Supplemental Charts](https://www.unicode.org/cldr/charts/46/supplemental/index.html).
+The following represents the format for additional supplemental information. This is information that is important for internationalization and proper use of CLDR, but is not contained in the locale hierarchy. It is not localizable, nor is it overridden by locale data. The current CLDR data can be viewed in the [Supplemental Charts](https://www.unicode.org/cldr/charts/latest/supplemental/index.html).
 
 ```xml
 <!ELEMENT supplementalData (version, generation?, cldrVersion?, currencyData?, territoryContainment?, subdivisionContainment?, languageData?, territoryInfo?, postalCodeData?, calendarData?, calendarPreferenceData?, weekData?, timeData?, measurementData?, unitPreferenceData?, timezoneData?, characters?, transforms?, metadata?, codeMappings?, parentLocales?, likelySubtags?, metazoneInfo?, plurals?, telephoneCodeData?, numberingSystems?, bcp47KeywordMappings?, gender?, references?, languageMatching?, dayPeriodRuleSet*, metaZones?, primaryZones?, windowsZones?, coverageLevels?, idValidity?, rgScope?) >
@@ -143,7 +143,7 @@ Excluding groupings, in this tree:
 *   All non-overlapping regions form a strict tree rooted at World.
 *   All leaf-nodes (country) are always at depth 4. Some of these “country” regions are actually parts of other countries, such as Hong Kong (part of China). Such relationships are not part of the containment data.
 
-For a chart showing the relationships (plus the included timezones), see the [Territory Containment Chart](https://www.unicode.org/cldr/charts/46/supplemental/territory_containment_un_m_49.html). The XML structure has the following form.
+For a chart showing the relationships (plus the included timezones), see the [Territory Containment Chart](https://www.unicode.org/cldr/charts/latest/supplemental/territory_containment_un_m_49.html). The XML structure has the following form.
 
 ```xml
 <territoryContainment>
@@ -224,7 +224,7 @@ Note: Formerly (in CLDR 28 through 30):
 <!ATTLIST languagePopulation officialStatus (de_facto_official | official | official_regional | official_minority) #IMPLIED >
 ```
 
-This data provides testing information for language and territory populations. The main goal is to provide approximate figures for the literate, functional population for each language in each territory: that is, the population that is able to read and write each language, and is comfortable enough to use it with computers. For a chart of this data, see [Territory-Language Information](https://www.unicode.org/cldr/charts/46/supplemental/territory_language_information.html).
+This data provides testing information for language and territory populations. The main goal is to provide approximate figures for the literate, functional population for each language in each territory: that is, the population that is able to read and write each language, and is comfortable enough to use it with computers. For a chart of this data, see [Territory-Language Information](https://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html).
 
 _Example_
 
diff --git a/docs/ldml/tr35.md b/docs/ldml/tr35.md
@@ -717,7 +717,7 @@ If a language subtag matches the `type` attribute of a `languageAlias` element,
 
 The private use codes listed as **excluded** in _[Private Use Codes](#Private_Use_Codes)_ will never be given specific semantics in Unicode identifiers, and are thus safe for use for other purposes by other applications.
 
-The CLDR provides data for normalizing language/locale codes, including mapping overlong codes like "eng-840" or "eng-USA" to the correct code "en-US"; see the **[Aliases](https://www.unicode.org/cldr/charts/46/supplemental/aliases.html)** Chart.
+The CLDR provides data for normalizing language/locale codes, including mapping overlong codes like "eng-840" or "eng-USA" to the correct code "en-US"; see the **[Aliases](https://www.unicode.org/cldr/charts/latest/supplemental/aliases.html)** Chart.
 
 The following are special language subtags:
 
@@ -790,7 +790,7 @@ Unicode identifiers give specific semantics to the following subtags.
 
 | alpha2 | alpha3 | num | Name                         | Comment | ISO 3166-1 status |
 | ------ | ------ | --- | ---------------------------- | ------- | ----------------- |
-| `QO`   | `QOO`  | 961 | Outlying Oceania             | countries in Oceania [009] that do not have a [subcontinent](https://www.unicode.org/cldr/charts/46/supplemental/territory_containment_un_m_49.html). | private use |
+| `QO`   | `QOO`  | 961 | Outlying Oceania             | countries in Oceania [009] that do not have a [subcontinent](https://www.unicode.org/cldr/charts/latest/supplemental/territory_containment_un_m_49.html). | private use |
 | `QU`   | `QUU`  | 967 | European Union               | **deprecated**: the _canonicalized_ form is EU | private use |
 | `UK`   | -      | -   | United Kingdom               | **deprecated**: the _canonicalized_ form is GB | exceptionally reserved |
 | `XA`   | `XAA`  | 973 | Pseudo-Accents               | special code indicating derived testing locale with English + added accents and lengthened | private use |
@@ -3757,7 +3757,7 @@ The choice of locales to include depends very much upon particular implementatio
 Some information that might be useful for determining the choice is found in the
  [Supplemental Territory Information](tr35-info.md#Supplemental_Territory_Information),
 which provides information on the use of languages in different countries/regions.
-(For a human-readable chart, see [Territory-Language Information](https://www.unicode.org/cldr/charts/46/supplemental/territory_language_information.html).)
+(For a human-readable chart, see [Territory-Language Information](https://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html).)
 
 It is important to note that if a particular locale is in a vertical slice, then all of its parents should be as well, because of inheritance.
 This is not a factor if the data is fully resolved, as in the JSON format data.
@@ -3803,7 +3803,7 @@ The [DTD Annotations](#DTD_Annotations) in are used to determine whether DTD ite
 
 Though such deprecated items are still valid LDML, they are strongly discouraged, and are no longer used in CLDR.
 
-The CLDR [DTD Deltas](https://www.unicode.org/cldr/charts/46/supplemental/dtd_deltas.html) chart shows which DTD items have been deprecated in which version of CLDR.
+The CLDR [DTD Deltas](https://www.unicode.org/cldr/charts/latest/supplemental/dtd_deltas.html) chart shows which DTD items have been deprecated in which version of CLDR.
 
 The remainder of this section describes selected cases of deprecated structure, and what (if any) should be used instead.
 
@@ -4277,7 +4277,7 @@ The above algorithm is a logical statement of the process, but would obviously n
 | General                                                  | _The following are general references from the text:_ |
 | [<a name="ByType" href="#ByType">ByType</a>]             | CLDR Comparison Charts<br/>[https://cldr.unicode.org/index/charts](https://cldr.unicode.org/index/charts) |
 | [<a name="Calendars" href="#Calendars">Calendars</a>]    | Calendrical Calculations: The Millennium Edition by Edward M. Reingold, Nachum Dershowitz; Cambridge University Press; Book and CD-ROM edition (July 1, 2001); ISBN: 0521777526. Note that the algorithms given in this book are copyrighted. |
-| [<a name="Comparisons" href="#Comparisons">Comparisons</a>]             | Comparisons between locale data from different sources<br/>[https://www.unicode.org/cldr/charts/46/by_type/index.html](https://www.unicode.org/cldr/charts/46/by_type/index.html) |
+| [<a name="Comparisons" href="#Comparisons">Comparisons</a>]             | Comparisons between locale data from different sources<br/>[https://www.unicode.org/cldr/charts/latest/by_type/index.html](https://www.unicode.org/cldr/charts/latest/by_type/index.html) |
 | [<a name="CurrencyInfo" href="#CurrencyInfo">CurrencyInfo</a>]          | UNECE Currency Data<br/>[https://www.iso.org/iso-4217-currency-codes.html](https://www.iso.org/iso-4217-currency-codes.html) |
 | [<a name="DataFormats" href="#DataFormats">DataFormats</a>]             | CLDR Translation Guidelines<br/>[https://cldr.unicode.org/translation](https://cldr.unicode.org/translation) |
 | [<a name="LDML" href="#LDML">Example</a>]                               | A sample in Locale Data Markup Language<br/>[https://www.unicode.org/cldr/dtd/1.1/ldml-example.xml](https://www.unicode.org/cldr/dtd/1.1/ldml-example.xml) |
diff --git a/docs/site/index/requesting-additionsupdates-to-cldr-languagepopulation-data.md b/docs/site/index/requesting-additionsupdates-to-cldr-languagepopulation-data.md
@@ -28,7 +28,7 @@ Requests to add or change language/population data must provide the following ba
 
 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](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.
+For language names and codes, some resources are: [Unicode CLDR charts](https://www.unicode.org/cldr/charts/latest/), [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.
 
diff --git a/docs/site/translation/core-data/exemplars.md b/docs/site/translation/core-data/exemplars.md
@@ -75,7 +75,7 @@ The very last line shows an internal UnicodeSet format. You can normally ignore
 
 The exemplar character sets contain the commonly used letters for a given modern form of a language. These are used for testing and for determining the appropriate repertoire of letters for various tasks, like choosing charset converters that can handle a given language. The term “letter” is interpreted broadly, and includes characters used to form words, such as 是 or 가. It should not include presentation forms, like [U+FE90](https://util.unicode.org/UnicodeJsps/character.jsp?a=FE90) ( ‎ﺐ‎ ) ARABIC LETTER BEH FINAL FORM, or isolated Jamo characters (for Hangul).
 
-- For charts of the standard (non-CJK) exemplar characters, see a chart of the [standard exemplar characters](https://www.unicode.org/cldr/charts/45/by_type/core_data.alphabetic_information.main.html).
+- For charts of the standard (non-CJK) exemplar characters, see a chart of the [standard exemplar characters](https://www.unicode.org/cldr/charts/latest/by_type/core_data.alphabetic_information.main.html).
 - For more information, please see [Section 5.6 Character Elements](http://unicode.org/reports/tr35/tr35-6.html#Character_Elements) in UTS#35: Locale Data Markup Language (LDML).
 
 There are different categories:
diff --git a/docs/site/translation/date-time/date-time-names.md b/docs/site/translation/date-time/date-time-names.md
@@ -126,8 +126,8 @@ The time span associated with each code is different for different languages!
 ![image](../../images/date-time/Screen-Shot-2015-06-22-at-12.14.47.png)  
 
 - It shows the time span (with a 24 hour clock) for the code, and then an example (for the format codes).
-	- You can also go to the web page [Day Periods](https://www.unicode.org/cldr/charts/45/supplemental/day_periods.html), and look for your language.
-	- For example, for Malayalam, you would go to ...[day\_periods.html#ml](https://www.unicode.org/cldr/charts/45/supplemental/day_periods.html#ml) , and see that **morning2** is the period that extends from **06:00** to **12:00**.
+	- You can also go to the web page [Day Periods](https://www.unicode.org/cldr/charts/latest/supplemental/day_periods.html), and look for your language.
+	- For example, for Malayalam, you would go to ...[day\_periods.html#ml](https://www.unicode.org/cldr/charts/latest/supplemental/day_periods.html#ml) , and see that **morning2** is the period that extends from **06:00** to **12:00**.
 
 |   | Code | English | German | Russian |
 |---|---|---|---|---|
@@ -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](/requesting_changes#how-to-file-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/latest/supplemental/day_periods.html)**. If you think the rules are wrong (or missing) for your language, please [file a ticket](/requesting_changes#how-to-file-a-ticket) and supply the missing information. Here are examples for English and Chinese.
 
 | Code | English | Span | Chinese | Span |
 |---|---|---|---|---|
diff --git a/docs/site/translation/date-time/date-time-patterns.md b/docs/site/translation/date-time/date-time-patterns.md
@@ -270,7 +270,7 @@ These new patterns are available in Gregorian and Generic calendars, In these ne
 	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.)](/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.
+	2. See the [Day Periods](https://www.unicode.org/cldr/charts/latest/supplemental/day_periods.html) chart for your language.
 
 ![image](../../images/date-time/ST-flexibledayperiod.JPG)
 
