From 513f90a7eacba6f88ce7c3c89ff786722b3984c1 Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Mon, 5 Jan 2026 13:20:05 -0600 Subject: [PATCH 1/4] CLDR-19123 site: update CLDR 42-43-44 wording around keyboard files --- docs/site/downloads/cldr-42.md | 10 +++++++++- docs/site/downloads/cldr-43.md | 5 +++++ docs/site/downloads/cldr-44.md | 4 +++- 3 files changed, 17 insertions(+), 2 deletions(-) diff --git a/docs/site/downloads/cldr-42.md b/docs/site/downloads/cldr-42.md index fb636349063..0888f914cc5 100644 --- a/docs/site/downloads/cldr-42.md +++ b/docs/site/downloads/cldr-42.md @@ -56,4 +56,12 @@ title: 'CLDR 42 Download' </table> <br> -<center>See <a href="https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w" rel="nofollow" target="_blank">Key to Header Links</a>" jsaction="rcuQ6b:WYd;">

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR 42, the focus is on:

Locale Status

CLDR v42 Language Count

Data Changes

There were two areas of focus for this release: the formatting of Personal Names, and the upgrade of Modern to include many more languages.

DTD Changes 

BCP47 Changes

Supplemental Data Changes

Locale Changes

File Changes 

JSON Data Changes

Background

Formatting people’s names

Software needs to be able to format people's names, such as John Smith or 宮崎駿. The data is typically drawn from a database, where a name record will have fields for the parts of people’s names, such as a given field with a value of “Maria”, and a surname field value of “Schmidt”. 

There are many complications in dealing with the variety of different ways this needs to be done across languages:

CLDR has added structured patterns that enable implementations to format available name fields for a given language. The formatting for a name can vary according to the available name fields, the language of the name and of the viewer, and various input settings.

The new Person Name formatting data has a tech preview status. The CLDR committee is requesting feedback on the data and structure so that it can be refined and enhanced in the next release. ICU will also be offering a tech preview API in its next release. Other clients of CLDR are recommended to try out the new data and structure, and supply feedback back to the CLDR committee in the next few months.

Specification Changes

The following are the main changes in the specification:

Growth

The following chart shows the growth of CLDR locale-specific data over time. It is restricted to data items in /main and /annotations directories, so it does not include the non-locale-specific data. The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

The detailed information on changes between v42 release and v41 are at v42 delta_summary.tsv: look at the TOTAL line for the overall counts of Added/Changed/Deleted. See v42 locale-growth.tsv for the detailed figures behind the chart.

CLDR v42 Growth

Migration

Known Issues

Upcoming changes

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+<center>See <a href="https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w" rel="nofollow" target="_blank">Key to Header Links</a>" jsaction="rcuQ6b:WYd;">

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR 42, the focus is on:

Locale Status

CLDR v42 Language Count

Data Changes

There were two areas of focus for this release: the formatting of Personal Names, and the upgrade of Modern to include many more languages.

DTD Changes 

BCP47 Changes

Supplemental Data Changes

Locale Changes

File Changes 

JSON Data Changes

Background

Formatting people’s names

Software needs to be able to format people's names, such as John Smith or 宮崎駿. The data is typically drawn from a database, where a name record will have fields for the parts of people’s names, such as a given field with a value of “Maria”, and a surname field value of “Schmidt”. 

There are many complications in dealing with the variety of different ways this needs to be done across languages:

CLDR has added structured patterns that enable implementations to format available name fields for a given language. The formatting for a name can vary according to the available name fields, the language of the name and of the viewer, and various input settings.

The new Person Name formatting data has a tech preview status. The CLDR committee is requesting feedback on the data and structure so that it can be refined and enhanced in the next release. ICU will also be offering a tech preview API in its next release. Other clients of CLDR are recommended to try out the new data and structure, and supply feedback back to the CLDR committee in the next few months.

Specification Changes

The following are the main changes in the specification:

Growth

The following chart shows the growth of CLDR locale-specific data over time. It is restricted to data items in /main and /annotations directories, so it does not include the non-locale-specific data. The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

The detailed information on changes between v42 release and v41 are at v42 delta_summary.tsv: look at the TOTAL line for the overall counts of Added/Changed/Deleted. See v42 locale-growth.tsv for the detailed figures behind the chart.

CLDR v42 Growth

Migration

  • + +- The [Keyboard WG] is working on a major revamp of the Keyboard specification, ~planned for release in late 2022~ [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal than the original format, and therefore existing keyboard files do not interoperate, were not maintained, and will be removed. + +

Known Issues

Upcoming changes

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
+ +[Keyboard WG]: /index/keyboard-workgroup.md +[CLDR-15034]: https://unicode-org.atlassian.net/browse/CLDR-15034 +[44-keyboards]: /downloads/cldr-44.md#keyboard-changes \ No newline at end of file diff --git a/docs/site/downloads/cldr-43.md b/docs/site/downloads/cldr-43.md index 455720a5b41..29690bc1942 100644 --- a/docs/site/downloads/cldr-43.md +++ b/docs/site/downloads/cldr-43.md @@ -247,6 +247,9 @@ The CLDR language matching data can *and should* be overridden whenever there is - Likely Subtags now have an attribute to indicate the **origin** of the data. This is informational, and typically be ignored by implementations. - **Turkey / Türkiye** - In v42, the customary English name for the country code TR was "Turkey", and an alternate name was "Türkiye". In v43, the customary English name was changed to "Türkiye", and the alternate name was set to "Turkey". Translators were advised of the change, and reviewed the names in their locales to see if any needed adjustment. Implementations that wish to retain the English name "Turkey" may choose to use the alternate form. +- **Keyboards** + - The [Keyboard WG] is working on a major revamp of the Keyboard specification, [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal than the original format, and therefore existing keyboard files do not interoperate, were not maintained, and will be removed. + ## Known Issues @@ -261,3 +264,5 @@ The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR dat For web pages with different views of CLDR data, see . +[Keyboard WG]: /index/keyboard-workgroup.md +[44-keyboards]: /downloads/cldr-44.md#keyboard-changes \ No newline at end of file diff --git a/docs/site/downloads/cldr-44.md b/docs/site/downloads/cldr-44.md index f479e825e1d..c8ca4b27bdb 100644 --- a/docs/site/downloads/cldr-44.md +++ b/docs/site/downloads/cldr-44.md @@ -156,13 +156,15 @@ The following is a summary of the DTD changes which reflect changes in the struc ### Keyboard Changes -**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the Keyboard Subcommittee, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. **Note**: prior keyboard data files are not compatible, were not maintained and have also been removed. +**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the Keyboard Subcommittee, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. Note that there are additional sample keyboard data files in progress which were not complete for v44, but may be consulted as samples: - Bengali, Assamese Phonetic Keyboard (PR \#[3368](https://github.com/unicode-org/cldr/pull/3368)) - French AZERTY optimisé (PR \#[3220](https://github.com/unicode-org/cldr/pull/3220)) +**Note**: prior keyboard data files are not compatible, were not maintained and have also been removed. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect, and are not compatible with the current DTD. + See the *Known Issues* section for additional known issues. ## Specification Changes From aab1c980897b466858719f3a3b0801932818d649 Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Sat, 14 Feb 2026 11:45:33 -0600 Subject: [PATCH 2/4] CLDR-19123 site: update references to Keyboard WG and fix link --- docs/site/downloads/cldr-44.md | 4 ++-- docs/site/index/keyboard-workgroup.md | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/site/downloads/cldr-44.md b/docs/site/downloads/cldr-44.md index c8ca4b27bdb..0f8d7d036e6 100644 --- a/docs/site/downloads/cldr-44.md +++ b/docs/site/downloads/cldr-44.md @@ -156,14 +156,14 @@ The following is a summary of the DTD changes which reflect changes in the struc ### Keyboard Changes -**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the Keyboard Subcommittee, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. +**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the Keyboard WG, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. Note that there are additional sample keyboard data files in progress which were not complete for v44, but may be consulted as samples: - Bengali, Assamese Phonetic Keyboard (PR \#[3368](https://github.com/unicode-org/cldr/pull/3368)) - French AZERTY optimisé (PR \#[3220](https://github.com/unicode-org/cldr/pull/3220)) -**Note**: prior keyboard data files are not compatible, were not maintained and have also been removed. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect, and are not compatible with the current DTD. +**Note**: prior keyboard data files are not compatible, were not maintained and have also been removed in CLDR v44. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect, and are not compatible with the current DTD. See the *Known Issues* section for additional known issues. diff --git a/docs/site/index/keyboard-workgroup.md b/docs/site/index/keyboard-workgroup.md index 5e318880c1a..ee3aba1990f 100644 --- a/docs/site/index/keyboard-workgroup.md +++ b/docs/site/index/keyboard-workgroup.md @@ -4,7 +4,7 @@ title: CLDR Keyboard Working Group # CLDR Keyboard Working Group -The CLDR Keyboard Subcommittee is responsible for the development and maintenance of a standard cross-platform XML format for use by keyboard authors. +The CLDR Keyboard Working Group is responsible for the development and maintenance of a standard cross-platform XML format for use by keyboard authors. ## Background @@ -24,7 +24,7 @@ There is no central repository or contact point for this data, meaning that such ## LDML: The universal interchange format for keyboards -The CLDR Keyboard Subcommittee is currently rewriting and redeveloping the existing LDML (XML) definition for keyboards (UTS#35 part 7) in order to define core keyboard-based text input requirements for the world's languages. This format allows the physical and virtual (on-screen or touch) keyboard layouts for a language to be defined in a single file. Input Method Editors (IME) or other input methods are not currently in scope for this format. +The CLDR Keyboard Working Group is currently rewriting and redeveloping the existing LDML (XML) definition for keyboards (UTS#35 part 7) in order to define core keyboard-based text input requirements for the world's languages. This format allows the physical and virtual (on-screen or touch) keyboard layouts for a language to be defined in a single file. Input Method Editors (IME) or other input methods are not currently in scope for this format. ![alt-text](../images/keyboard-workgroup-rowkeys.png) @@ -57,7 +57,7 @@ The LDML keyboard format, and the CLDR repository, will make it much easier to d In 2012, the original LDML keyboard format was designed to describe keyboards for comparative purposes. In 2018, a [PRI was created](http://blog.unicode.org/2018/01/unicode-ldml-keyboard-enhancements.html) soliciting further feedback. -The CLDR Keyboard Subcommittee was formed and has been meeting since mid-2020. It quickly became apparent that the existing LDML format was insufficient for implementing new keyboard layouts. +The CLDR Keyboard Working Group was formed and has been meeting since mid-2020. It quickly became apparent that the existing LDML format was insufficient for implementing new keyboard layouts. ### What is the current status? @@ -75,5 +75,5 @@ Implementations ### How can I get involved? -If you want to be engaged in this workgroup, please contact the CLDR Keyboard Subcommittee via the [Unicode contact form](https://corp.unicode.org/reporting/staff-contact.html). +If you want to be engaged in this workgroup, please contact the CLDR Keyboard Working Group via the [Unicode contact form](https://unicode.org/reporting.html). From f93d13e8375a474709fbefae485a85b216a3b8fa Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Sat, 14 Feb 2026 13:43:24 -0600 Subject: [PATCH 3/4] CLDR-19123 Apply suggestions from code review Co-authored-by: Fredrik --- docs/site/downloads/cldr-43.md | 2 +- docs/site/downloads/cldr-44.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/site/downloads/cldr-43.md b/docs/site/downloads/cldr-43.md index 29690bc1942..3c382092797 100644 --- a/docs/site/downloads/cldr-43.md +++ b/docs/site/downloads/cldr-43.md @@ -248,7 +248,7 @@ The CLDR language matching data can *and should* be overridden whenever there is - **Turkey / Türkiye** - In v42, the customary English name for the country code TR was "Turkey", and an alternate name was "Türkiye". In v43, the customary English name was changed to "Türkiye", and the alternate name was set to "Turkey". Translators were advised of the change, and reviewed the names in their locales to see if any needed adjustment. Implementations that wish to retain the English name "Turkey" may choose to use the alternate form. - **Keyboards** - - The [Keyboard WG] is working on a major revamp of the Keyboard specification, [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal than the original format, and therefore existing keyboard files do not interoperate, were not maintained, and will be removed. + - The [Keyboard WG] is working on a major overhaul of the Keyboard specification, [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal and therefore existing keyboard files do not interoperate, have not been maintained, and will be removed. ## Known Issues diff --git a/docs/site/downloads/cldr-44.md b/docs/site/downloads/cldr-44.md index 0f8d7d036e6..facb19d614c 100644 --- a/docs/site/downloads/cldr-44.md +++ b/docs/site/downloads/cldr-44.md @@ -163,7 +163,7 @@ Note that there are additional sample keyboard data files in progress which were - Bengali, Assamese Phonetic Keyboard (PR \#[3368](https://github.com/unicode-org/cldr/pull/3368)) - French AZERTY optimisé (PR \#[3220](https://github.com/unicode-org/cldr/pull/3220)) -**Note**: prior keyboard data files are not compatible, were not maintained and have also been removed in CLDR v44. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect, and are not compatible with the current DTD. +**Note**: Prior keyboard data files are not compatible, have not been maintained and have also been removed in CLDR v44. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect and are not compatible with the current DTD. See the *Known Issues* section for additional known issues. From 4b91d0fb7e835a648fb8ea5f4fa4d5e78f22ed01 Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Mon, 16 Feb 2026 11:42:08 -0600 Subject: [PATCH 4/4] CLDR-19123 site: update cldr-42-43-44 per review comments Co-authored-by: Marc Durdin --- docs/site/downloads/cldr-42.md | 2 +- docs/site/downloads/cldr-43.md | 2 +- docs/site/downloads/cldr-44.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/site/downloads/cldr-42.md b/docs/site/downloads/cldr-42.md index 0888f914cc5..8851da9bad2 100644 --- a/docs/site/downloads/cldr-42.md +++ b/docs/site/downloads/cldr-42.md @@ -58,7 +58,7 @@ title: 'CLDR 42 Download' <br> <center>See <a href="https://cldr.unicode.org/index/downloads#h.xq13gabuoy9w" rel="nofollow" target="_blank">Key to Header Links</a>" jsaction="rcuQ6b:WYd;">

Overview

Unicode CLDR provides key building blocks for software supporting the world's languages. CLDR data is used by all major software systems (including all mobile phones) for their software internationalization and localization, adapting software to the conventions of different languages.

In CLDR 42, the focus is on:

Locale Status

CLDR v42 Language Count

Data Changes

There were two areas of focus for this release: the formatting of Personal Names, and the upgrade of Modern to include many more languages.

DTD Changes 

BCP47 Changes

Supplemental Data Changes

Locale Changes

File Changes 

JSON Data Changes

Background

Formatting people’s names

Software needs to be able to format people's names, such as John Smith or 宮崎駿. The data is typically drawn from a database, where a name record will have fields for the parts of people’s names, such as a given field with a value of “Maria”, and a surname field value of “Schmidt”. 

There are many complications in dealing with the variety of different ways this needs to be done across languages:

CLDR has added structured patterns that enable implementations to format available name fields for a given language. The formatting for a name can vary according to the available name fields, the language of the name and of the viewer, and various input settings.

The new Person Name formatting data has a tech preview status. The CLDR committee is requesting feedback on the data and structure so that it can be refined and enhanced in the next release. ICU will also be offering a tech preview API in its next release. Other clients of CLDR are recommended to try out the new data and structure, and supply feedback back to the CLDR committee in the next few months.

Specification Changes

The following are the main changes in the specification:

Growth

The following chart shows the growth of CLDR locale-specific data over time. It is restricted to data items in /main and /annotations directories, so it does not include the non-locale-specific data. The % values are percent of the current measure of Modern coverage. That level is notched up each release, so previous releases had many locales that were at Modern coverage as assessed at the time of their release. There is one line per year, even though there were multiple releases in most years.

The detailed information on changes between v42 release and v41 are at v42 delta_summary.tsv: look at the TOTAL line for the overall counts of Added/Changed/Deleted. See v42 locale-growth.tsv for the detailed figures behind the chart.

CLDR v42 Growth

Migration

  • -- The [Keyboard WG] is working on a major revamp of the Keyboard specification, ~planned for release in late 2022~ [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal than the original format, and therefore existing keyboard files do not interoperate, were not maintained, and will be removed. +- The [CLDR Keyboard Working Group] is working on a major revamp of the Keyboard specification, ~planned for release in late 2022~ [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal than the original format, and therefore existing keyboard files do not interoperate, were not maintained, and will be removed.

Known Issues

Upcoming changes

Acknowledgments

Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.

The Unicode Terms of Use apply to CLDR data; in particular, see Exhibit 1.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts.

Page updated
Report abuse
diff --git a/docs/site/downloads/cldr-43.md b/docs/site/downloads/cldr-43.md index 3c382092797..9b7af29d687 100644 --- a/docs/site/downloads/cldr-43.md +++ b/docs/site/downloads/cldr-43.md @@ -248,7 +248,7 @@ The CLDR language matching data can *and should* be overridden whenever there is - **Turkey / Türkiye** - In v42, the customary English name for the country code TR was "Turkey", and an alternate name was "Türkiye". In v43, the customary English name was changed to "Türkiye", and the alternate name was set to "Turkey". Translators were advised of the change, and reviewed the names in their locales to see if any needed adjustment. Implementations that wish to retain the English name "Turkey" may choose to use the alternate form. - **Keyboards** - - The [Keyboard WG] is working on a major overhaul of the Keyboard specification, [Released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal and therefore existing keyboard files do not interoperate, have not been maintained, and will be removed. + - The [CLDR Keyboard Working Group] is working on a major overhaul of the Keyboard specification, [released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal and therefore existing keyboard files do not interoperate, have not been maintained, and will be removed. ## Known Issues diff --git a/docs/site/downloads/cldr-44.md b/docs/site/downloads/cldr-44.md index facb19d614c..71a434934c5 100644 --- a/docs/site/downloads/cldr-44.md +++ b/docs/site/downloads/cldr-44.md @@ -156,7 +156,7 @@ The following is a summary of the DTD changes which reflect changes in the struc ### Keyboard Changes -**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the Keyboard WG, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. +**Keyboard** has a new DTD (keyboard3\.dtd and the \ element). This is a complete rewrite of the specification by the CLDR Keyboard Working Group, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. Note that there are additional sample keyboard data files in progress which were not complete for v44, but may be consulted as samples: