Milestone Schedule

Date Phase
2013-03-15 v23 Released
2013-09-18
 v24 Released
2014-03-19
v25 Released
 2014-05-01v26 Data Submission Begins

Walkthrough

Contents

  1. 1 Overview
    1. 1.1 Hints
    2. 1.2 Sections
    3. 1.3 Priorities
    4. 1.4 Code Lists
    5. 1.5 Other Items
    6. 1.6 Supplemental

Overview

The following is a short walkthrough of how to use the survey tool to enter data, and prioritize your work. It works best to open the Survey Tool and try it as you read. See also:
  1. Survey Tool Overview - this also has commonly-used links on the right side.
  2. Survey Tool Guide - what the icons mean, how the tool window is laid out, how to zoom, etc.
  3. Known Bugs - also contains issues to watch for, and an FAQ. Read the top section, and remember that you can consult it later.
  4. See also, What's New.

Hints




  1. If you have questions, look the FAQ, or post comments to the Forum for your locale. You can post general questions to the cldr-users list. There are links on Survey Tool Overview for more information.
  2. There is much more information in the detail view for each element, so be sure to look at the detail view on all of the items (which you can see by clicking on the item)
  3. You can now abstain from voting on a particular row if you do not have an opinion on this value, and you will be able to see this in the UI (see below).
  4. If you change an item, it will be autosaved when you exit the edit field; you do not need to remember to save each item explicitly.

Sections

When you log in to the Survey Tool, you see a list of locales:

    Survey Tool initia



Once you select a particular locale, such as French for this example, most windows have a navigation bar at the top. It looks something like the following:


    Survey Tool for locale, select category


Click on the General Info popup to select a category of CLDR data to work on, for example:

    Survey Tool for locale, select category


Clicking on the button adjacent to Locale Display Names in the above example will display a page for the first subcategory under Locale Display Names, which is Locale Name Patterns as shown below. To change to the page for a different subcategory, click the second popup that appears after Locale Display Names:

    Survey Tool for locale, select subcategory


Clicking on the button adjacent to Language in the above example will bring up the data entry page for the Languages subcategory of Locale Display Names, as shown below. Also note that just below the popups for locale category and subcategory are other controls that—for example—enable you to change the coverage level in effect (this governs how many of the possible CLDR entries are actually exposed for you to modify, and is set by default based on your organization and the locale). The link marked Instructions takes you to general Survey Tool instructions which include specific Translation Guidelines for most items.

Each row lists the CLDR code, the corresponding English value, the currently-proposed value for the locale and its approval status (under A), and other values that have been or are currently being proposed as the locale value for the entry. You will only see rows for entries that correspond to your coverage level. Depending on the status of existing votes, you may also see an Abstain column that enables you to explicitly abstain from voting on an item, or to remove your previous vote. 

Clicking on a particular item, such as “pachto” in the example below, displays additional detail about that item in the right sidebar.

    Survey Tool for locale, page for language display names


Priorities

Work on items according to priority in the table below of the status for that item marked in column “A”. There are many more details about there UI elements in the Survey Tool Guide referenced at the top of this page. The first three rows (missing values, errors and warnings) refer to problems in the field value data itself (or not yet completed data), and they appear along with the data value affected, as in the "Asu (Tanzania)" value in the picture above, which has a [warn] warning. The final four rows refer to issues with the the approval level of the entry, and show up in the "Approved" column in the UI.

Group
 		Description
 		What to do
     The field value is missing.  Add a new value if it is needed. See the details below for priorities
[stop] There is a serious error in the field value.  Choose a different value, or add a new value.
[warn] The field value has a problem, is a new value to review, or is needed for your coverage goals. Vote for the correct value, or enter a new value.
[ques] There is not an approved value: missing, disputed, or insufficient votes. Vote for the correct value, or enter a new value.
     There is a value at the level of contributed, but not approved. Vote for the correct value if you have not done so, work with 
other organization language contributors otherwise to get agreement
[okay] There is a (tentatively) approved value, with no warnings or errors.  If that value looks good, you don't have to do anything else.

The coverage levels are only an approximation of the priorities -- it takes human judgment in looking at prioritizing translation of other values. For example, the name of the Thai currency might not be important in Estonian, but important for Malay.

Here is general information about the different types of data.

Code Lists

These are pretty straightforward translations. However, there are a few pitfalls in certain cases, so be sure to look at the details on one item of each type, and read the "For more information" page.

Other Items

These involve items that can be more complicated, since they involve patterns such as "¤ #,##0.00". For example, when this pattern is used, the ¤ will be replaced by a currency symbol like $,  the "," and "." will be replaced by your language's punctuation, and the 0 and # will be replaced by your language's digits. There is much more information in the zoomed view, so be sure to look at the detail view for each type of item, and read the "For more information" page for that type.

Supplemental

  1. Look at plural rules: are the categories right for your language? If not, file a bug report and list exceptions (e.g. for currencies, use singular "euro" only). Esp. look at decimals as this is a new category.
    • Also, look at the details in on any units or currencies with "count" in the Code column to read the background info about plurals
  2. Look at the other charts for your language and country/ies, and file a bug if you see any problems.
Comments