Schedule (Tentative)

Date Phase
06.29
 1.7.1 Released
07.01
 1.8 Development starts
10.16 1.8 Data submission starts
12.02 1.8 Data submission ends - vetting starts
01.13 1.8 Data resolution, data/structure verification and correction starts
02.10 1.8 Final Candidate available
03.10 1.8 Target release date
For details, see Release Schedule.
See also Notification Services.

CLDR Project‎ > ‎CLDR Survey Tool‎ > ‎

Walkthrough

Contents

  1. 1 Overview
    1. 1.1 Hints
  2. 2 Workflow
    1. 2.1 Step-by-Step
    2. 2.2 All Other Sections
    3. 2.3 Priorities
    4. 2.4 Code Lists
    5. 2.5 Other Items
    6. 2.6 Supplemental
    7. 2.7 Calendars
    8. 2.8 Vetting

Overview

The following is a short walkthrough of how to use the survey tool to enter data, and prioritize your work. Before continuing, please look over the following pages. It works best to open the Survey Tool and try it as you read.
  1. Survey Tool Overview - this also has commonly-used links on the right side.
  2. Survey Tool Windows - 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.

Hints




  1. If you have questions, look the FAQ, Windows document, 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 zoomed view, so be sure to zoom in on items (clicking the left-hand icon), and read down the page.
  3. Click n/o if you want to uncheck the radio button, and not make a submission.
  4. It's faster if you do as much as you can in the main view, not the zoomed view -- but go to the zoomed view at least once for each type of item, to make sure you understand the issues.
  5. Remember to Save before you leave any window, including the zoomed view!

Workflow

When you log into the CLDR tool, you will see the locale(s) you have signed up for. Click on a locale to enter the Data Submission page. On this page, there are links to Code Lists (languages, scripts, territories, etc.) and Other Items (characters, numbers, etc.). These are the sections you will be editing.



Step-by-Step

The step-by-step section lets you focus in on the new items that were added in this release, or cases where the English value has changed. Go through these items first.

All Other Sections

When you open a page in one of these sections, you’ll likely see a page that looks something like this:



Priorities

Fix any items according to the following priorities. In each case, you will pick among the available values by hitting the radio button on that item, or add a new value. If you click on these icons, you'll zoom in to see more information.

Group
 		Description
 		What to do
[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 approved value: missing, disputed, or insufficient votes. Vote for the correct value, or enter a new value.
[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.
[squo] The field value is the same as the "parent". See below for priorities.

Based on the coverage goals for your organization, warnings will be automatically generated: [warn]. However, the mechanical tests are only an approximation of the priorities -- it takes human judgment in looking at prioritizing translation of other values: [squo]. For example, the name of the Thai currency might not be important in Estonian, but important for Malay.

Here are suggested priorities as you go through the data.

Code Lists

These are pretty straightforward translations. However, there are a few pitfalls in certain cases, so be sure to zoom in on one item of each type, and read down the page.

  1. Languages – focus mostly on languages that your language's speakers are likely to see in computer interfaces, not all of them (not Ancient Greek; Frisian in NL but not in Pakistan)
  2. Scripts – only a few matter (the ones with warnings)
  3. Territories – do all of them
  4. Variants – skip
  5. Keys – there are just 3, do all of them
  6. Types – just a few, do all of them
  7. Currencies
    • Do the ones in countries that your language's speakers are likely to want to see. For example, the currencies of neighboring countries. Companies that use currencies will want to translate the ones they support.
    • Some take plural forms (with "count" someplace in the Code column). See plurals under Supplemental below.
  8. Timezones – you should do all of these
  9. Metazones
    1. Metazones are now grouped by continent in the survey tool.
    2. The top priority should be the metazones that are in or closest to the country you are translating for. 
    3. Note that the continent is based on one "base" country, so America_Mountain is used in the US, Canada, and Mexico
    4. The country may be split across continents, so Irkutsk, a zone for Russia, is found in Asia, not Europe
  10. Code patterns – Typically you will translated the entries under "English" (such as "Language: {0}" => "Sprache: {0}").
    1. These are used in lists where the name of the language/script/region is not available -- the code (like "de" for German) will be substituted for the {0} placeholder. (This really should be in the Other Items list)
  11. Measurement – just 2, do both of them

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 zoom in on them, and read down the page.

  1. Characters - these are used for error checking, so review each of them them carefully.
  2. Numbers - these are for the display of numbers in your language. Review each of them carefully.
  3. Gregorian calendar - this is maybe the most complicated. See below.
  4. Other calendars - Gregorian calendar should always be the first priority, followed by any other calendars that are commonly used in your country. They will typically get most of their data from Gregorian anyway.
  5. localeDisplayPattern - do both if needed. Often this will be just confirming the default.
    1. Background: This is used to display locale (language) names, starting with a code. For example, take "en_AU". First the language code 'en' is translated, such as "anglais", then the country is translated, such as "Australie". These patterns are used to put those together, into something like "anglais (Australie)". The {0} will be replace by the language name, and the {1} will be replaced by the country name. If there is also a script, then {1} is replaced by a list, such as "uz-Arab-AF"    => "ouzbek (arabe, Afghanistan)"
  6. Units. Do all of these. Note that these use the plurals, so click on one and read the background. See plurals under Supplemental below.
  7. Misc. These are a mixed bag. Click on each for more help.
  8. References. These are only needed to record sources in case of disputes. So don't worry about them until we get to the vetting phase.

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

Calendars

You'll need to do all of these. They fall into a number of categories (unfortunately, somewhat mixed up in the presentation).

  1. Translated names of months, days, eras, am/pm, and quarters - these are pretty straightforward, but zoom in for information on the abbreviated ones and the stand-alone formats. For most languages, you only need to do 3 sets of each (wide, abbreviated, and narrow (stand-alone)), and the others inherit from them.
  2. Relative dates ("yesterday") - you don't need to do the ones that don't exist in your language. Zoom for more info.
  3. Field names ("Era") - these will appear in dialog boxes as the names of fields.
  4. Date-time patterns. These are forms like "HH:mm:ss v", where the letters are replaced by different date or time fields: in this case, hours, minutes, seconds, and timezone". Zoom for more info.
    1. Some of the Code values for these are pretty ugly, like dateTimes/​intervals/​intervalItem[@id="h"]/​greatestDifference[@id="h"]
    2. Look at the examples and zoom in to see an explanation of these at the bottom of the zoomed page.
    3. It helps to make your windows full-screen: especially if you have access to a large-screen display.

Vetting

There is an automatic report generated of errors or warnings in the locales. So once you've done the above, see Vetting for getting a head-start on fixing these problems.