Information Hub for Linguists

This page was last modified on: December 7, 2018. 

Contents

  1. 1 Data stability
  2. 2 Current Survey Tool stage
  3. 3 What's new in this release
  4. 4 Translation Guides
  5. 5 Known Issues
  6. 6 Resolved Issues
  7. 7 Survey Tool Stages 
    1. 7.1 Shakedown
    2. 7.2 Submission (Limited)
    3. 7.3 Submission (General)
    4. 7.4 Vetting
    5. 7.5 Resolution
  8. 8 Targeted Locales
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.

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 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.

Current Survey Tool stage

The survey tool opened for CLDR v35 submissions. For full schedule, please refer to Milestone Schedule in the left navigation.

Due to the time of year, the v35 submission has a limited scope, and you can only change certain rows. Please see Submission (Limited) for more details before starting.

What's new in this release

  1. Import of old votes is automatic. See Login and Import of old votes for full explanation. For v35 limited scope, we recommend that you Do Not manually import in old votes that do not match the last released value. You will not be able to work on these items unless they are part of the limited scope. Exception to this would be new languages, where all data points are open for submission.
  2. Survey tool UI. There are the following improvements, particularly for the Voting experience: 
    1. The ✩ icon. This is consistently available either in the Winning or Others columns to indicate the last released value. 
    2. Regional locales. 
      1. The inherited values work better now, and should show up consistently. If you are working in a sub_locale, and see issues related to inheritance, please file a ticket.
      2. The vote status column will show an orange-up arrow if the winning item is inherited and it does not have the required number of unconflicted votes. See Regional Inheritance section in the Survey Tool guide.
    3. The vote.png icon. This has been removed from the survey tool. (It used to show items you voted on that were not winning. Instead, you can see your votes in the right pane where all active votes are listed.)
    4. Sections. Some items are now found in different sections. This affects Characters, Core Data, and Miscellaneous.
  3. Performance enhancements. These include:
    1. Pop-up window stability. The pop-up window for adding items will not disappear unexpectedly. Ticket #11265
    2. Focus will not be lost due to backspace or arrow keys. Ticket #11218
    3. Going to your locale will be faster. Ticket #9566
    4. Switching between section will be faster. Ticket #11211
  4. Missing data due to changes in the Coverage Level. For full details, see Survey Tool Coverage. 
    1. You will see either additional missing data or will not see some of the data points that you worked on in the past. (e.g. some of the lesser-used language names will not be exposed in the Modern coverage level). 
    2. The following languages have moved coverage levels: 
      1. Somali (so) and Javanese (jv) have moved up to Modern coverage; therefore, will require more data collection.
      2. Cebuano (ceb), Hausa (ha), Igbo (ig), Yoruba (yo) have moved to Basic coverage.
  5. New Errors Detected. The error detection has been improved:
    1. Collisions between emoji flags and others are detected. For example, “日本” for both 🇯🇵 & 🗾 will cause an error.
    2. Collisions between different typographic terms used for font names are now detected. For example, you can't use the same phrase for wdth-100 as for wght-400. For guidance, see Typographic Names.

Translation Guides

Sections of the translation guides that have been updated in preparation for this contribution period.
  1. 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.[Same workaround as v34]
  2. Emoji names and keyword translation guide has been updated. If you are new to emoji names and keywords or as a refresher, please review this page before starting on Emoji names and keywords. 
  3. Country/Region (Territory) Names for clarity in areas where we have seen confusion.
  4. For items that do not work in your language, please don't simply accept to use the 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”.
    1. Pashto: There will be several missing data in the Date & Time formats including "quarters" (see Ticket #11565). Please provide an appropriate translations for the missing data.
  5. Typographic Names. Added guidance on collision errors.

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. “Unknown language” shows up at the bottom of the Vetters locales.
  2. Bidi: Reports for Date/Time need right-to-left cells; numbers report using ASCII digits; exemplar sets hard to read because of bidi ordering.
  3. When the coverage is set lower, sections like Characters in the left pull-out show up but are empty. BCP47 and Supplemental should never appear, since they are not locale-specific data. Ticket #11248

Resolved Issues
    Previously listed on the known issues that have been resolved:
    1. ✩ icon that were showing Others column if the Winning value is identical to inheritance at the beginning of the cycle with no new votes. Resolved Ticket#11611
    2. Auto-import of old votes at first log-in may take some time and may look like it is not responding. A new message has been added while the import process is in progress. Resolved Ticket #11641

    Survey Tool Stages 

    Shakedown

    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.

    Submission (Limited)

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

    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.
    † Among the Missing for v35 are new items for translation: Emoji 12, generic calendar date-intervals, more measurement units, a narrow list format (“&” in English), and a few others. (On the Dashboard, New means winning values that have changed since the last release.)

    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 Errors* and 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 Dashboard, New 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. 

    Vetting

    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:

    Resolution

    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:
    • Basic level: Cebuano (ceb), Hausa (ha), Igbo (ig), Yoruba (yo)
    • Modern level (raised from Basic): Javanese (jv), Somali (so)
    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 (39): View All
    Comments