Information Hub for Linguists

This page was last modified on: May 24, 2018.

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.

Current Survey Tool stage: Shakedown

The survey tool is currently open for "shakedown" participants.  Refer to the Survey Tool stages section below for expectations for contributors during each phase. For the schedule, please refer to Milestone Schedule in the left navigation.

There are changes to the Survey Tool as outlined in the What's New in this release section below. Please read this entire document before getting started. The change in the Import at first log in is particularly important to know ahead before your first log-in.

CLDR v33.1 and v34 releases

Your contributions in this year's contribution cycle will result in two releases of CLDR.
  • CLDR v33.1 will release early June (refer to the Milestone Schedule in the left nav). The data for this release is focused on new Emoji 11 data. See What's new in this release section below to know how to identify Emoji 11 data. 
    • focus on completing the Emoji data, and fixing any errors in emoji.
    • complete your submission and vetting by May 30th
    • don't work on other data until the Emoji data is all complete and error-free.
  • CLDR v34 will release in the fall, and will include all data collected in this year's contribution cycle. Once you finish your contribution to the new Emoji, you can move directly to other data and you DO NOT need to wait for the CLDR v33.1 data freeze. The CLDR TCs will be handling the data include in v33.1 with no disruption to you.

Data stability

Please be mindful of data stability by carefully reviewing previously Approved data. When it's clearly incorrect, it should be changed. For data stability, don't change the field 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

Note: the ticket numbers are included in brackets (such as [#11056]) for those who are interested in the details.
  1. Import of old votes is automatically handled. All your votes matching the latest Approved data will be imported automatically upon first log in. If you expected to see your old votes, but do not see them after your first log in, file a ticket
    • If you have voted previously, upon log-in, you will see a message showing the number of your votes that matched the currently winning votes that have been auto-imported. 

    • You can still import old voted data that do not match the Approved data. Go to Setting (gear icon), under My Votes, then Import Old votes. You will need to review and select each of the losing items for import. Select All is not an option votes.
  2. Browser support for Survey Tool now includes the latest versions of Edge, Safari, Chrome, and Firefox. Please report issues with the latest versions of any of the supported browsers. [#10396]
  3. Emoji
    1. Finding Emoji 11: The new emoji entries for version 11 use identifiers starting with "E11:" (see image). You can do a “Find on page” to move quickly from one to the next. You can also see the Emoji 11 Unicode chart for a full list. [#10997]
    2. Keyword voting: The calculation of the winning set of keywords is now different. Beforehand, if you had the following choices, #1 would win. Now, the fact that #2 is a subset of #3 gives it a larger weight in voting, and #2 will win.
      1. {small} : 4 votes
      2. {big | large} : 3 votes
      3. {big | large | grand} : 3 votes
    3. Keyword de-duplication: If one keyword phrase is covered by other keyword phrases, then it will be removed. For example, the set {big bad wolf | big | bad | wolf}  {bad | big | wolf}. This will happen automatically as you enter values.
      1. Note that the items in the set are also automatically alphabetized: {big | bad | wolf}  {bad | big | wolf}
    4. Names included in keywords: The emoji names will get included as keywords automatically. You won't see this happen as you enter them since the name may change before the release is resolved. So this change is done later in data resolution, after the names are final. [#10537]
      1. You do not need to enter the Emoji names as Keywords explicitly — but don't bother removing them if present (since that might artificially introduce voting conflicts).
      2. Example: 
        • Name: fox face
        • Keywords: {face | fox}
        • Final keyword in the released XML: {face | fox | fox face}
  4. Priority Items: In a sublocale like French (Canada) [fr_CA], the dashboard values for Missing and Losing more accurate reflect what needs to be done. [#9505]
  5. Long Date formats: We have found that many languages misused "dd" instead of "d". Please revisit your decision for Long date formats to determine correct use of "d" vs. "dd". [#10018]
  6. Language-Specific Issues: Feedback on specific language data will be posted in language forums.
    1. For German language only: For the purpose of CLDR data, we will be using the English terms "AM/PM" as the data. CLDR provides the flexibility to use the 12 hour format even for those language who strictly use 24 hour format. In case of German, the CLDR TCs have concluded to use the English words. [#10789]
    2. For Odia language only: Do not use diacritics in transliterations. [#11044]
    3. Please participate actively in Forum postings for language-specific data feedback from CLDR users, and postings by CLDR committee members. See Survey Tool Guide.
  7. Old forum posts: Forum posts from previous contribution cycles are now available as one thread, and the version number where the posting came from are identified with the date and time stamp.  

Translation Guides

  1. The translation guides for date/time patterns and names have been updated, focusing especially on the need to synchronize different name forms such as format and standalone with the patterns that use them, and different ways of utilizing the format and standalone name forms.
  2. Timezone names and Territory names often share the same term. A list of overlapping data between Timezone and Territory names are available in this public spreadsheet. Use this spreadsheet as a reference when working on Timezone names, and bring consistency for Timezone names where they are also found in Territory names.
  3. Many of the emoji names are constructed. For example, many people emoji using hair colors and skin tones, or "flag" + country name, or keycaps, or group emoji. On each row that has an ⓔ, to see how these are formulated please make sure you (a) hover over your votes and (b) and hover over the English for comparison.
    1. Characters/Components are used for people with combinations of hair color and skin tone. Note that these have "weak" ordering: thus names and keywords may be grouped together.
    2. Some of the Character/Category fields are also used to form the constructed names, so please carefully look at each row with  also. 
    3. CLDR doesn't have gender agreement for nouns, so please try to choose the grammatical forms that work the best. For example, in some languages there will be an adjective for "light skinned" that would need to agree with the noun (man or woman). It may work to make noun phrases instead, eg "light skin" or "bald head".

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.
  • The Venezuela currency will change on June 4 from VEF to VES. VES will show as "(old)" in the header until after June 4. At that point VEF will show as (old), and VES will be unmarked

Resolved Issues

    Previously listed on the known issues that have been resolved:
    • 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.


    In the submission phase, please focus on getting all Missing items entered.
    If you are working in a sub-locales (such as fr_CA), wait until the main locale (fr) has completed submission. See voting for inheritance vs. hard votes in Survey Tool guide


    All contributors are encourage to move their focus to the Dashboard view, and unanswered items in the Forums. Consider other's opinions, by reviewing the Disputed and the Loosing. See guidelines for handling Disputed and Losing.
    Subpages (39): View All