Skip to content

Conversation

@AEApple
Copy link
Contributor

@AEApple AEApple commented Jan 14, 2026

CLDR-19204

  • Add mission statement as approved by the CLDR TC on 2026-01-14

  • Add definition for locale data

  • Rearrange definitions in alphabetical order

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

- Add definition for locale data
- Order definitions alphabetically
Added CLDR mission statement to the CLDR home page.
@github-actions
Copy link

✨ This commit deployed to https://f5832379.cldr.pages.dev
✨ This PR deployed to https://pr5288.cldr.pages.dev

Changed Pages in the last commit:

@github-actions github-actions bot added the Site Update Updates docs/site label Jan 14, 2026
@github-actions
Copy link

✨ This commit deployed to https://4c4288ed.cldr.pages.dev
✨ This PR deployed to https://pr5288.cldr.pages.dev

Changed Pages in the last commit:

@github-actions
Copy link

✨ This commit deployed to https://7877c5f5.cldr.pages.dev
✨ This PR deployed to https://pr5288.cldr.pages.dev

Changed Pages in the last commit:


## CLDR Mission

_To build and maintain the most trusted and comprehensive repository of [locale data], reflecting common usage across the world, through active participation from organizations and community members._
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have to do in this PR (eg not blocking), but I'd suggest the following change:

Suggested change
_To build and maintain the most trusted and comprehensive repository of [locale data], reflecting common usage across the world, through active participation from organizations and community members._
_To build and maintain the most trusted and comprehensive specification for and collection of [locale data], reflecting common usage across the world, through active participation from organizations and community members._
  1. "repository" has the wrong connotation in the industry, implying to many that it is not curated. So I think 'collection' is broader
  2. We underplay the value of CLDR if we just focus on the data. The specification is equally important, serving to define (for example) the structure of locale identifiers, unit identifiers and preferences, ... and the conformant use of the data.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We did hash this over both over email and in the TC meeting and reached consensus. If we need to discuss it again, we should do that in a TC meeting, not in a PR. Also note that one of the purposes of the mission statement is brevity, not an exhaustive list of what we provide.
Personally I think "repository" is fine, it is the R in CLDR after all...

# Definitions

***literate percent*** \- indicates the percentage of the country's population that is literate, based on literacy information from the World Bank, CIA Factbook, and others.
***customary modern usage*** - The terms or characters commonly used in modern contexts: newspapers, journals, lay publications, street signs, commercial signage, common geographic names, company names, and so on. It does not include terms or characters that are only commonly used in technical or academic contexts such as mathematical expressions, archaic or historic texts, citations of archaic words, liturgical texts, or pedagogical use.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
***customary modern usage*** - The terms or characters commonly used in modern contexts: newspapers, journals, lay publications, street signs, commercial signage, common geographic names, company names, and so on. It does not include terms or characters that are only commonly used in technical or academic contexts such as mathematical expressions, archaic or historic texts, citations of archaic words, liturgical texts, or pedagogical use.
***customary modern usage*** - The terms or characters commonly used in modern contexts:
newspapers, journals, lay publications, street signs, commercial signage, common geographic names, company names, and so on.
It does not include terms or characters that are only commonly used in technical or academic contexts such as mathematical expressions, archaic or historic texts, citations of archaic words, liturgical texts, pedagogical use, or formal contexts.

We want to cover the "Democratic People's Republic of Korea" vs "North Korea" issue also.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears that most of what you are doing is alphabetizings, so if you want to do this later, that's fine.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to cover the "Democratic People's Republic of Korea" vs "North Korea" issue also.

I think that's the "common geographic names" part.

@AEApple AEApple merged commit 4bbbc50 into main Jan 15, 2026
18 checks passed
@AEApple AEApple deleted the AEApple-CLDR-19204 branch January 15, 2026 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Site Update Updates docs/site

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants