Information Hub for Linguists

2019-11-01 Survey tool will be opening early December for a limited submission.
The pages listed to the left provide guidelines for translation of CLDR strings. For an overview of the tools, please read the Survey Tool Guide before starting. If you would like to contribute data, but do not have an account, see Survey Tool Accounts.

Current Survey Tool stage: Survey tool will be opening early December for a limited submission for CLDR 37 release.

Please refer to the Milestone Schedule in the left navigation for milestones. The exact dates will be refined by the committee as we look across different needs and availability.  

Data stability

Please be mindful of data stability by carefully reviewing previously Approved data. When it's clearly incorrect, it should be changed — but for data stability, don't change the field when it is already acceptable (even if not optimal). When you have an evidence of a variant being much better and in customary use than the existing Approved data, use the Forum to bring up discussions and gain consensus to change Approved values.

What's new in this release cycle

CLDR 37 is a limited release in terms of data updates. This is a unique cycle where we will be announcing two releases:
  • v36.1: Data update will be cherry picked. There is no impact to data contribution using the survey tool. You can ignore any communication around this dot release.  
  • v37: This is a scoped data collection, which means that the data points that are scoped for contribution will be editable to you; otherwise, they'll will not have the voting options will be grayed out. 

Survey Tool (New/enhanced features)

New data

Approximately xx new data items were introduced (the exact number will vary by locale).
  • Units 

  • Emoji

  • New locales added for data contributions

    • .

Translation quality

Please review the following areas to improve translation quality before starting.

  • Falklands/Malvinas translation consistency (#11526)
    • In some languages / locales, we have found that the handling of primary/secondary names were incorrect. In some Falklands is the primary name, and Malvinas is secondary; in others it is reversed.
    • Please review the translations for consistency, and check for which should be primary for your language / locales.
    • See additional details in the Translation guide: Geopolitical sensitive names.
  • Avoiding English
    • For items that do not work in your language, please don't simply use English. Find a solution that works for your language. For example, if your language doesn't have a concept of "quarters", use a translation that describes the concept "three-month period" rather than “quarter-of-a-year”.
    • For example, a number of Pashto items were found to be in English and has been removed. Please correct the situation and supply the missing data, reviewing the others for consistency. (#11565)
  • Emoji names and search keywords
    • Not simple translations
      • Remember that the character names and keywords are not translations.
      • They are the so-called transcreations, and may be completely different than translations. Don't simply translate the English; use terms that people would use to describe the image (which will show up in the Information Panel on the right). 
      • Moreover, there may be more or fewer keywords than in English.
    • Gender-neutral

Translation guides: updated sections

  1. New Persian Language specific translation guide has been added to address common data quality issues that have been found in the last release.

Known Issues

Please review this list before getting started to avoid creating duplicate tickets. This list will be updated as fixes are made available in production. If you hit a problem, please file a ticket.

  1. Brackets "[ ]" under Alphabetic information are used to group the alphabetic information and they are not part of the data. Please ignore the [ ] in the Alphabetic information and do not try to update the data to exclude the []. Issue logged in ticket 13180

Resolved Issues

Previously listed on the known issues that have been resolved:

  1. TBD

Survey Tool Stages 


The survey tool is live and all data that you enter will be saved and used. You can start work, but there may be additional fixes during this period. So the tool may be taken down for updates more frequently than after we exit Shakedown. During Shakedown, your participation in looking for issues with the Survey tool is essential. If you find any problems in the tool, please file a ticket.


Make sure your coverage level is set correctly at the top of the page.

There are two types of releases: full, and limited-submission. 

Version 36 is a full-submission release.

For a limited-submission release, the Survey Tool will only let you add or vote in certain rows. What you can do depends on your locale:
    1. Newly targeted locales: proceed with Submission (General). 
    2. Other targeted locales: proceed with Submission (General), but start with the Dashboard step and focus on Errors*, Missing†, and English Changed.
    3. Other locales: go to the Dashboard and deal with any Errors*.
* Note that if the committee finds systematic errors in data, new tests can be added during the submission period, resulting in new Errors.

If you want to know which locales are in which categories, see Targeted Locales.

Submission (General)

Make sure your coverage level is set correctly at the top of the page.
For new locales or ones where the goal is to increase the level, it is best to proceed page-by-page starting with the Core Data section. At the top of each page you can see the number of items open on the page. Then scan down the page to see all the places where you need to vote (including adding items). Some 

Then please focus on the Dashboard view, first getting all Missing† items entered, and then addressing any remaining Errorsand reviewing the English Changed (fixing your language if necessary). 

* Note that if the committee finds systematic errors in data, new tests can be added during the submission period, resulting in new Errors.
† Among the Missing are are new items for translation(On the DashboardNew means winning values that have changed since the last release.)

If you are working in a sub-locales (such as fr_CA), coordinate with others on the Forum to work on each section after it is are done in the main locale (fr). That way you avoid additional work and gratuitous differences. See voting for inheritance vs. hard votes in Survey Tool guide


All contributors are encourage to move their focus to the Dashboard view, and:
  1. Resolve all of the Errors.
  2. Review all items in the Forums that don't show consensus yet, and try to resolve them by posting relevant information.
  3. Consider other's opinions, by reviewing the Disputed and the Losing. See guidelines for handling Disputed and Losing.
  4. Review the items that are Flagged for TC and provide comments if you have information that should be considered.  
To see the Flagged items, go to the Gear dropdown, under Forum see Flagged items:


The vetting is done, and further work is being done by the CLDR committee to resolve problems. You should periodically take a couple of minutes to check your Forums to see if there are any questions about language-specific items that came up.

Targeted Locales

The categories of locales are based on the following:

Newly targeted locales:
Other targeted locales:
  • CLDR targets: the 82 languages as listed in Locale Coverage chart with Modern, Moderate or Basic in the CLDR target column (excluding newly targeted), and certain of their regional locales.
  • Highly active communities: Cherokee, Scottish Gaelic, Faroese; other locales with >95% modern coverage in the last release.
Other locales:
  • All other locales
Subpages (42): View All