CLDR 31 Release Note
Overview
Unicode CLDR 31 provides an update to the key building blocks for software supporting the world's languages. This data is used by all major software systems for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.
Some of the improvements in the release are:
Canonical codes (See Migration)
The subdivision codes have been changed to all have the bcp47 format.
The locales in the language-territory population data are in canonical format.
The timezone ID for GMT has been split from UTC.
There is a mechanism for identifying hybrid locales, such as Hinglish.
Emoji 5.0
Short names and keywords have been updated for English. (Data for other languages to be gathered in the next cycle).
Collation (sorting) adds the new 5.0 Emoji characters and sequences, and some fixes for Emoji 4.0 characters and sequences.
For Emoji usage, subdivision names for Scotland, Wales, and England have been added for 65 languages.
For changes that may affect migration to this version, see Migration.
Other structural additions and changes
Codes now use canonical form, as described above.
New structure for lenient parsing
New structure for minimal pairs (for plurals)
New language-matching structure for matching groups of countries
The literacyPercent for a region is broken out from writingPercent
For DTD changes, see DTD Deltas
For more information, see Spec Modifications.
Other data additions and changes
New timezone IDs (long form and bcp47 form).
New currency code BYR.
Minimal pairs for plural rules.
New data for lenient parsing
Enhanced Language Matching data (new elements and attributes)
Updated Windows keyboards
<fields> data fleshed out for era, weekday, dayperiod, and zone, and new <fields> data added for weekOfMonth, dayOfYear, weekdayOfMonth.
A pseudo-locale generation tool.
A number of additions to exemplar characters, such as for Arabic and Farsi
Some improvements to the Zawgyi-to-Unicode transform, and other transforms.
Collation data updated for Unihan 9.0 and for Emoji 5.0
New unit type "length-point"
For more information, see detailed delta charts.
Growth
The following gives the total overview of the change in data items in CLDR. This release did not have a data-submission cycle, so the changes reflect cleanup and bug fixes.
* The measurement of the number of items is reflects the different ways that the information is represented. A single data field (element or attribute value) may result in multiple data items. For example, plural rules may be shared by multiple languages, and a single data field contains all the languages to which those rules apply. Sometimes a changed item appears as a deletion+addition, and sequences of items (such as sort order) are not counted as different even if the order changes.
For more details, see the Delta Data charts.
JSON data
No structural changes for this release, just updated to match XML data.
Survey Tool
no changes in the Survey Tool this release
Specification changes
For details, see Spec Modifications.
Migration
Code changes
The subdivision codes have been changed to all be the bcp47 format, eg "usca" instead of "US-CA". This affects supplemental containment and subdivisions, and translations in subdivisions/en.xml, etc. See Part 6, Sec 2.2 [#9942]
The locales in the language-territory population tables have been changed to be the canonical format, dropping the script where it is the default. So "ku_Latn" changes to "ku"
The exemplar/ locale data file names have also been changed to be the canonical format, dropping the script where it is the default.
Plural rules
The Portuguese plural rules have changed so that all (and only) integers and decimal fractions < 2 are singular.
Timezones
The GMT timezone has been split from the UTC timezone.
New timezone bcp47 codes have been added.
Language/Region data
The new literacyPercent attribute for supplemental <languagePopulation> has been broken out from writingPercent, the latter now only being used to reflect primarily-spoken languages. [#9421]
A new format for language matching is provided. To allow time for implementations to change over, the old data is retained, and the new data is marked as "written-new".
Languages "hr" and "sr" are no longer a short distance apart, for political reasons.
Other
The primary names for CZ changed from "Czech Republic" to "Czechia", with the longer name now the alternate.
Known Issues
“Week of� structure
The structure and intended usage for the “week x of y� patterns is still being refined and may change. This applies especially to dateFormatItems such as the following:
<dateFormatItem id="MMMMW" count=...>'week' W 'of' MMM</dateFormatItem>
<dateFormatItem id="yw" count=...>'week' w 'of' y</dateFormatItem>
Areas of discussion include the use of the count attribute and the use of ordinal vs. cardinal numbers. For more information see [#9801].
Non-unique emoji short names (fixed in 31.0.1)
Some of the emoji names are not unique. Fixes are being gathered, but are not in time for the release. See [#10116], [#10127]
Chinese stroke collation
Since CLDR 30, Chinese stroke collation has been missing entries for several basic characters. CLDR 32 reverts the stroke collation data to the CLDR 29 version; a complete fix for the underlying problem is targeted for CLDR 33. See #10497, #10642.
Others
See tickets for v31.0.1.
Acknowledgments
Many people have made significant contributions to CLDR and LDML; see the Acknowledgments page for a full listing.
Key
The Release Note contains a general description of the contents of the release, and any relevant notes about the release.
The Data link points to a set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see Repository Organization).
The Spec is the version of UTS #35: LDML that corresponds to the release.
The Delta document points to a list of all the bug fixes and features in the release, which be used to get the precise corresponding file changes using BugDiffs.
The SVN Tag can be used to get the files via Repository Access.
For more details see CLDR Releases (Downloads).
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.
-
-2. You can choose to limit your import to specific items.
-
- 
-
-3. Scroll to the bottom to see the category selection for bulk import.
-4. Select the categories that you want to import and click the **Import selected items** button at the bottom.
-5. Go to the data categories in the Survey Tool where you have imported your old votes, these will show up in the Others column with no votes.
-6. Review and add your vote. The best practice is to create a forum entry explaining why this data should be changed and drive to gain consensus with other vetters.
-
----
-
-## Picking Locales
-
-
-
-In the left navigation bar, you will see the CLDR locale(s) for which you have permission marked with a _**pencil icon**_.
-You can view others locales but not submit contributions.
-Selecting the "Show read-only" option beneath the search bar will allow you to see the locales you don't have permissions for.
-Sometimes it can be helpful to see how other locales have decided to handle a data item if your locale doesn't yet have a commonly accepted way of writing it.
-
-Each language is followed by a list of regions that represent specific locales. The locale that is grayed out and preceded by an × is the default locale.
-The others are considered “sub-locales�. If you are working on the default locale, select the language name instead of the region name.
-For example, if you work on Spanish in general (default = Spain),
-you will see that that Spain is grayed out in the list below: choosing Spanish means that you are working on the default (Spanish for Spain).
-
-If you are working on a specific variant language (or "sub-locale"), you will need to pick a non-default region.
-For example, if you are vetting Mexican Spanish, pick **Mexico**. (You should see a pencil icon before Mexico instead of Spanish in this situation.)
-
-
-
-After you've selected your locale but before you start contributing,
-it is always good to check your [coverage level][] to make sure it matches the level you are planning to contribute to.
-Which items are shown to you for review in the [Dashboard][], along with [how your progress is tracked](#progress-widget) is based on your target coverage level.
-To check you coverage level click on the drop down to the right of the ☰ menu button.
-The coverage level which is followed by "(Default)" is your current coverage level.
-For example the coverage level in this screenshot is [Modern][]
-If your default coverage level is not correct you can follow [Reporting Survey Tool issues][] to have it fixed.
-
-
-
-1. If you hover over an item (including the English item), a tooltip will appear showing a sample value and usage of the item in context. The item itself will have a white background; other text in context will have a gray background.
-2. When you select an item (the text, **NOT** the radio button), additional information will show in the right-hand **Info Panel**. See screenshot below.
-3. Make sure you use a wide-screen monitor and enlarge your window until you can see it, something like the image below.
-4. The box at the top shows information about the code you are translating. _It also has a link that you should click on the first type you encounter that kind of item that will explain any "gotchas"._
-5. If there is an error or warning for the item, you see that in the middle.
-6. Below that, you'll see an example. This is the same as you get by hovering over the item in the center section.
-7. If there are votes, you'll see a breakdown of them; you also see the number of votes required to change the value. Unicode TC organization members usually have 6 votes; members from other [CLDR organizations][] usually have 4 votes; and _vetters who are not representing a Unicode organization usually have 1 vote_. Your vote value and the vote value required for change will show on the right navigation for the selected item as shown in this screenshot (4 and 8 respectively in this case).
-8. Near the bottom, you'll see a pulldown menu that shows the values for different regional Variants. Here, you can quickly compare the values and go to different sub-locales to correct inconsistencies.
-9. You'll also see the New Forum Post button (as shown in the screenshot _to the right_). This is the easiest way to post discussions for the selected item. Remember that the Forum posts are at language level and not at sub-locale level. For more information, see [Forum][].
-10. **No Info Panel?**
- - If you click on the **Code** cell and there is no **Info Panel**, you may have turned it off accidentally. Click on the **Open Info Panel** button near the top right of the window.
-
-
-
-### Overall progress
-
-_Progress bar shows progress of items overall for your coverage level._
-
-
-
----
-
-## Dashboard
-
-The Dashboard will show you a list of data items with warnings of different kinds. Some will require action, some may be false positives.
-At the top of the Dashboard is a header with a button for each section title (such as **Missing**) and the number of items. Below that header are a series of rows.
-The goal is that you should work the Dashboard down to show zero items, then review the [Reports][] (below).
-
-
-
-There are two ways to clear items from the **Dashboard** list:
-
-1. Fix them (such as adding a translation for a missing item).
-2. Hide them (such as for an invalid warning or when the English has changed and you've verified that the current translation is still correct).
-
-* _**Only**_ hide items if they really are false positives, **not** because you gave up on fixing them…
-* If you hide an item by mistake:
- * Unhide all the lines by clicking on the check box to the left of 'hide' in the upper right corner of the Dashboard.
- * Click on the checkbox next the the item you wish to unhide to uncheck it.
- * Hide all the lines again by clicking the check box next to 'hide' again.
-
-_The first priority is to fix all the_ _**Missing**_ **Provisional**_ and _**New**_ _items by supplying the correct translations._
-
-More details on how to clear items are available in the [Dashboard Tips][].
-
----
-
-## Searching in the Survey Tool
-
-The Survey Tool supports searching for: values, English value, and for the codes.
-In the Dashboard header, each notification category (such as "Missing" or "Abstained") has a checkbox determining whether it is shown or hidden.
-The symbols in the A column have been changed to be searchable in browsers (with *Find in Page*) and stand out more on the page. See below for a table. They override the symbols in [Survey Tool Guide: Icons](translation/getting-started/guide#icons).
-
-## Reports
-
-The reports show lists of items that need to be reviewed for consistency. Review these last, after you have voted for all the missing and provisional items this cycle, since they will not generate correctly with missing data. Reports can be found in both the dashboard as well as in the left navigation bar between the Dashboard and Forum options.
-
-[Left navigation bar view](../../images/gettingStartedGuideKorean.png)
-
-_Example of a section of the date time report:_
-
-
-
-See [Review Reports][] for more details.
-
----
-
-## Special cases
-
-**You may not make changes to this locale**
-
-You may see a message like the following when trying to modify a regional locale, like pt-BR.
-
-
-
-→
-
-
-
-The reason that Brazil is grayed out is that it is the default content locale for Portuguese. So to modify pt-BR, you need to simply click on Portuguese. If you do click on Brazil, you will get to a page with the following at the top. Click on [default content locale][] for more details.
-
-
-
-
-
-
-### Changing Protected Items
-
-Some items have change-protection in place that will stop the item value from changing without the CLDR Technical Commmittee's approval, but you can still advocate a change.
-This is indicated by the message shown below. This warning indicates that the item has particularly broad impact and changes should only be made if absolutely necessary.
-
-
-
-
-
-After hitting that **Request** button, you'll see the following.
-
-
-
-### Steps to flag a protected item for CLDR TC review:
-
-1. Vote on or Add the item you want.
-2. Click on the “**Flag for Review button**�.
-3. On the new page, you'll see a message box.
-4. Enter the change that you want to make, and add a justification for changing it.
- - Make sure that the justification is clear to people who don't speak your language.
- - Cite sources (web pages) where possible.
-5. Then click **“Post**�.
-6. Encourage others to support your request by voting for the item you're requesting.
-7. The Technical Committee will review the change request and
- - accept it, or
- - ask for more information, or
- - reject it with comments
-
-> [!Notes]
-> * The **Flag for Review** button will be available only when the item is under change-protection *and* there is a vote for an alternative in the **Others** column.
-> * If you change your vote, it removes the flag — so if you want for it still to be flagged, you have to redo the process above.
-
----
-
-## Forum
-
-Forum is the place to discuss and collaborate with other vetters on questions and issues in your language. The forum is at Language level and not at sub-locale level; if you are talking about a translation in a sub-locale, be sure that you are clear about that.
-
-It's a best practice to **create a Forum post whenever you propose a change to a previously approved value**, and provide an explanation and links to references.
-
-### Forum Etiquette
-
-While creating New Posts on Forum or participating in discussions please follow these general etiquette guidelines for best productive outcomes:
-
-- Be professional. Provide accurate, reasoned answers so that other participants can easily understand what you are talking about.
-- Be courteous. Refrain from inappropriate language and derogatory or personal attacks.
-- Don’t “SHOUT�; that is don’t use all capitals.
-- In case of disagreement, focus on the data and provide evidence to support your position. Avoid challenges that may be interpreted as a personal attack.
-- Be prepared to have your own opinions challenged or questioned, but don’t take answers personally.
-- It’s possible that participants have different expectations on the intent of the data. Clarify what you think is the intent may help especially if disputes continue.
-- Remember that open discussion is an important part of the process; abiding by these guidelines will encourage active participation by all vetters and a better end result.
-
-### Forum post workflow
-
-1. Create a new **Request**
-2. Responses by other vetters in your language with Agree, Decline, or Comment.
-3. Once resolved, the creator of the the initial Request closes the post.
-
-> Note: Any posts where the requested value becomes the winning value by the end of the CLDR cycle will be automatically closed by the CLDR TC.
-
-#### How to create a new forum post
-
-A forum post can be specific to a particular data point or a general issue. In either case, create a new forum post to an item.
-
-* A post that is specific to a particular data point.
-* A general issue that impacts multiple data points. In a general case that impacts multiple data points, you do not need to post new forum posts for every item impacted. The general issue should be flagged to other vetters and once a consensus is reached, it is expected that vetters update their votes on all impacted items. New forum posts can be used to flag to other vetters if others fail to update their votes on all impacted items. ONLY request if others have missed or have not updated consistently.
-
-##### Create forum posts from the [Info Panel][] in the voting window
-
-1. Vote on an item (or add new +) for the item you want to suggest changing.
-
-
-
-2. In the Info Panel on the right, there are two buttons to indicate the type of forum posts:
- 1. **Request** You have voted on a non-winning item, and you want to Request others to change their votes.
- 2. **Discuss** - Currently only TC members can make discuss posts.
-3. Click **Request** button and fill out the details of your request. (Note: The **Request** button is disabled unless you have voted)
-
-
-
-**Request**
-
-1. A precomposed text is included to help start your post. **Important!: Request works WITH the item you voted for currently.**
-2. _Please consider voting for “{your voted-value}�. My reasons are:_ Complete the text by filling out your reasons and links to references.
-
-
-
-3. Then **Submit.**
-
-### Responding to Request posts
-
-There are two ways to respond to forum posts:
-- Info Panel (This is the recommended option so that you can see all the context for that item.)
-- In the Forum view (See [Working in the Forum view][])
-
-**Respond from the [Info Panel][] in the voting window.**
-
-In the **Info Panel**, select the **Comment** button
-- Each posted response is labeled in Red and its response type: Agree, Decline or Comment.
-
-
-
-**Choosing your Response:** Vote, or Comment
-
-1. When you make a vote on an item that already has a Request post by another vetter, then an Agree or Decline post will be made for you automatically. If you agree with the reasons for change, you aren't required to add explanations for agreeing unless you believe it is important to add additional explanation for linguists or the CLDR TC so that the decision during this cycle is not accidentally overturned in a future cycle due to missing information about the original change.
-
-2. An **Automated Agree post** will be posted if you vote for the requested value with a precomposed reply: _(Auto-generated:) I voted for “{requested-value}�_
-
-3. If you later change your vote to something other than the requested value an automatic response will be be posted with the precomposed reply: _(Auto-generated:) I changed my vote to “{requested-value}�, which now disagrees with the request.�_
-
- 
-
-4. **Comment:** Use this option if you do not Agree, and you have other input to bring to the discussion or if you want to ask for more information.
-
-
-
-### Responding to Discuss posts
-
-Currently only the CLDR TC can post Discuss posts. They will post a Discuss post whenever feedback is needed from the linguists for a specific locale. Feedback is needed in two cases:
-
-1. Resolving errors during the [Vetting][] and [Resolution][] phases
-2. Resolving issues reported in the public CLDR Issue tracker in [JIRA][]
-
-#### Forum posts for CLDR JIRA ticket feedback
-
-CLDR users can send in data feedback using [JIRA][]. Tickets filed in JIRA will be processed as described below. Please expect to see posts by CLDR Technical Committee members (TCs) in Forums, and participate by providing your response to any tickets needing your input.
-
-The goal is to bring it to the attention to all linguists contributing in a particular language, and gather their input, so an informed decision can be made and/or suggested.
-
-1. CLDR TC members accept JIRA tickets.
-2. For each ticket assigned to them, the TC member will post a forum topic in each language mentioned in the ticket, asking for vetters to look at the issue and either make the requested change, or explain in a forum post why changes should not be made.
-3. A reason for not changing could be for example that it is a reasonable change, but doesn't exceed the 'stability' bar in the translation guidelines.
-4. TC members will monitor the forum discussion/change during the Submission phase, and will close the JIRA ticket after the forum discussion is concluded.
-
-### Working in the Forum view
-
-In the Survey Tool [Forum view][], there are multiple filtering options available for you to work more effectively.
-
-1. The Forum view can be accessed from the left navigation **Forum.**
-
-
-
-2. By default, the filter is for **Needing action**.
-
-
-
-3. Filter options:
- - **Needing action**: Forum posts included in this filter are Requests and Discussion posts by someone in your language. You have not yet taken action on either agreed or declined or posted a discussion asking for additional information. For Discussion posts, these are where you are not the last poster.
- - **Open requests by you**: Forum posts included in this filter are Requests that you have posted that you have not closed yet.
- - **All Open topics**: All posts that are open. This includes both Request and Discussions that have not closed yet.
- - **All topics:** All topics, open or closed, including forum posts from previous releases.
-
-#### Respond to forum posts in the Forum view
-
-In the Forum view, you can respond to Request post by voting for the requested item. This will trigger an automatic post with the text: "(Auto-generated:) I voted for “REQUESTED ITEM�" or by clicking on the "Comment" button to explain why you disagree with the proposal.
-
-See [Responding to Request posts in Info Panel][].
-
-
-
-### Forum email notifications
-
-1. Another way to check for posts that may need your attention is to review email notifications to the e-mail account for your locale. You can delete these notifications if they are for changes initiated by you. You can open the post directly from a link in the email.
-2. When you make a forum entry, it will be emailed to all other linguists working on locales with the same language, parent or sub-locale (i.e. **forum is at Language level and not at sub-locale level**). If you are talking about a translation in a sub-locale, be sure that you are clear about that.
-
-## Reporting Survey Tool issues
-
-If you run into a problem with the Survey Tool functionalities or if the documentation doesn't match the current Survey Tool experience, please see [FAQ & Known Bugs][] to see whether it has already been reported (and whether there is a work-around).
-
-If there is a PM (Project Manager) managing contributions for your organization, please report the issue to your PM. To get support for DDL locales check the [DDL: Help Center][] for instructions.
-
----
-
-## Advanced Survey Tool Features
-
-1. Users familiar with CLDR XML format can upload votes (and submissions) for multiple items at once. See [Bulk Data Upload][].
-2. Organization managers can manage users for their organization (add, remove, send passwords, set locales, etc.). For more information, see [Managing Users][].
- 1. Some users may want to reset their Coverage Level, with the menu that looks like the image to the right.
- 1. The Coverage Level determines the items that you will see for translation: the minimal level has the highest priority items. You normally start with the level marked "Default" (which will vary by your organization and locale). Each successively higher level adds more items, at successively lower priorities. You will not normally go beyond "[Modern][]", unless you have special instructions for your organization.
-
-> Note: Some companies won't use the data for UI localization until it is complete at a certain [coverage level][], typically _**[Modern][]**_.
-
-[Basic]: /index/cldr-spec/coverage-levels#basic-data
-[Bulk Data Upload]: /index/survey-tool/bulk-data-upload
-[CLDR Organizations]: /index/survey-tool/cldr-organization
-[coverage level]: /index/cldr-spec/coverage-levels
-[Dashboard]: /translation/getting-started/guide#dashboard
-[Dashboard category]: /translation/getting-started/vetting-view#dashboard-categories
-[Dashboard Tips]: /translation/getting-started/vetting-view
-[DDL: Help Center]: /translation/ddl#support
-[default content locale]: /translation/translation-guide-general/default-content
-[draft status]: https://www.unicode.org/reports/tr35/#attribute-draft
-[Draft status symbols]: /translation/getting-started/guide#draft-status-symbols
-[FAQ & Known Bugs]: /translation#known-issues
-[file a ticket]: /requesting_changes#how-to-file-a-ticket
-[Forum]: /translation/getting-started/guide#forum
-[Forum view]: https://st.unicode.org/cldr-apps/v#forum/USER//
-[General Submission]: /translation/getting-started/survey-tool-phases#survey-tool-phase-general-submission
-[Info Panel]: /translation/getting-started/guide#info-panel
-[Inherited Changed category]: /translation/getting-started/guide#how-to-handle-different-categories
-[**input** these from the keyboard]: /translation/core-data/exemplars#input
-[JIRA]: /requesting_changes
-[Key to Escapes]: /translation/core-data/exemplars#key-to-escapes
-[Managing Users]: /index/survey-tool/managing-users
-[Modern]: /index/cldr-spec/coverage-levels#modern-data
-[Regional Inheritance]: /translation/getting-started/guide#regional-inheritance
-[Reports]: /translation/getting-started/guide#reports
-[Reporting Survey Tool issues]: /translation/getting-started/guide#reporting-survey-tool-issues
-[Responding to Request posts in Info Panel]: /translation#responding-to-request-posts
-[Resolution]: /translation/getting-started/survey-tool-phases#resolution-closed-to-vetters
-[Review Reports]: /translation/getting-started/review-formats
-[Special Characters]: /translation/getting-started/guide#special-characters
-[Survey Tool Search functionality]: /translation/getting-started/guide#searching-in-the-survey-tool
-[Vetting]: /translation/getting-started/survey-tool-phases#survey-tool-phase-vetting
-[Working in the Forum view]: /translation/getting-started/guide#working-in-the-forum-view
+---
+title: Survey Tool Guide
+---
+
+# Survey Tool Guide
+
+### _News_
+
+- 2026-05-22 Update [Dashboard][] section and [Dashboard Tips][] with new [Dashboard category][]
+- 2026-05-04 Survey Tool Guide revised for clarity
+
+The Survey Tool is a web based tool for collecting CLDR data and includes various features that the contributors (vetters) should know before getting started.
+
+> Note: The exact appearance in screenshots may change as the tool is enhanced over time and based on your vetter level.
+
+### 💡 Helpful Tips
+
+- Please read the home page of the [Translation Guidelines](/translation) before starting your data contribution.
+ - If you experience a **Loading...** problem with the Survey Tool, try clearing your browser cache. See [Reloading JavaScript](https://www.filecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XOjGNtMzbuM).
+- **Browser support** for Survey Tool includes the latest versions of Edge, Safari, Chrome, and Firefox.
+- Use [Reports](#reports) at the beginning to review the data in your language in a holistic manner for Date & time, Zones, and Numbers.
+ - Capitalization: Translations should be what is most appropriate for �middle-of-sentence� use. So, for example, if your language normally doesn't spell languages with a capital letter, then you shouldn’t do that here. Please see [Capitalization](/translation/translation-guide-general/capitalization) for more details.
+ - Plurals: For important information regarding the use of plural forms for your language, please read [Plurals](/translation/getting-started/plurals).
+
+### Vetting Phase
+
+At a point towards the end of a Survey Tool period, the Technical Committee will change the Survey Tool to "Vetting Mode". In Vetting Mode, submitting new data/translations is no longer possible, but you can still change your votes and participate in the forum. (The exception is that you can submit new data if the currently winning value has generated an error or a warning.)
+
+---
+
+## Login and Import of old votes
+
+At the start of each CLDR cycle, you will need to go to