This page explains the different views used in entering in CLDR data. The exact appearance in screenshots may change as the tool is enhanced over time.
Make sure that you haven't mistakenly turned the Information Panel off! See No Information Panel.
Icons for the Dashboard are listed below.
At the bottom is a Forum button, for posting a question or request to other translators for your language. For more information, see Forum.
Some items are by default inherited from other places in the data. You have the option of voting for the inherited value or entering a different one.
The inherited values are color coded:
You can click on the link in the right sidebar to see the original value.
The regional variants menu looks something like the following (the exact appearance depends on the browser):
When you pull it down, it will show which regional variants have different values than the main language locale. The current locale will show as gray.
For this case, for example, Switzerland and Liechtenstein have a different decimal separator than German (= Germany) does. Hover over the menu item to see the value it has. In the above diagram, you'll see "." as the decimal separator for Switzerland in the yellow hover box.
If any values are incorrect, please correct them. You can do that by selecting the menu item, which will take you to the same item, but in the regional locale. For example, selecting “Belgium” above goes to the decimal separator for German (Belgium). You can then correct the item.
Normally, the only values that should be different are in date and number formats. In some locales there are other variations: for example, German (Switzerland) spells words with “ss” instead of “ß”, so differences can occur on many different pages.
If you are voting in a "child locale", i.e. the non-default locale for your language, such as pt_PT, en_AU, zh_Hant_HK, etc., you have the option to enter a vote to actively follow whatever the translation is for the parent locale.
You do this by voting for the translation highlighted in blue. If do this, you are essentially saying "always copy the parent value, even if it changes". Only vote for the blue value if you feel confident the parent value will always be suitable for your locale. In the screenshot below, this is the case for the vote for "inglês".
If you want to vote for a firm value in your locale, that should not follow the parent locale, simply click the plus button and enter the value you want to vote for. Note that this can be the same as what is currently being inherited. You'll notice after your vote that the value is not highlighted in blue, indicating it's a hard vote, as in the case of "embu" below.
An inheritance vote is useful if there are no differences in spelling conventions and political relations between your locale and the parent locale. Abstaining from voting may have the same effect, but if another vetter votes for something different, it would be unopposed by you. By voting for the blue inheritance value you make your opinion known to other vetters.
The Dashboard will show you a list of data items with warnings of different kinds. Some will require action, some may be false positives. (For the veterans, this is the redesigned Priority Viewer.)
The goal is that you should work the Dashboard down to show zero items, then review the Reports, below.
The first priority is to fix all the Missing items by supplying the correct translations.
Go through each of the sections to address the problems. These sections are explained below.
At the top of each section is an arrow symbols to show the items in the section, the title (such as Missing), the number of items, and an "Unhide" button. Below that header are a series of rows.
Each row has a link to the value in survey tool, the English value, the previous version’s value, the currently winning value, and 3-4 action buttons, as below on the right. If the currently winning value and previous version’s value are equal, then the winning value is shown with “=”.
If you click on the Fix button, you'll see a pop-up Quick Fix Panel like the following.
This panel shows a summary of what you'd see in the main page for the item, and allows you to make a quick change. If, however, you haven't changed an item of this type before, it is best to click on the link at the top to go to the main page for the item. That way, you can see other items of the same type.
There are different categories of problems.
Best is to click on the blue Code (such as Reykjavik or CNY-name in the above screenshots). You get a new window with the items in context, where you can add a translation. When you fix a Missing item it will turn to New.
Your vote is losing (see the screenshot above). If you can live with the winning item—if it is reasonable, even if you don't think it is optimal—vote for the winning item. If not, click the Forum button and give reasons for people to change their vote to what you have. You can list a number of items in the same forum post, to make it easier for people to read.
This is very similar to Losing, except in this case your vote is winning and someone else's is losing. Just look these over quickly; if someone else's item is better, then you might want to change your vote. Otherwise, click the Hide button so that you don't see it any more.
For Warnings and English Changed, you'll see something like the following. The warning message is on the top left, in this case "The value is the same as English". That is a quite common warning for languages that are close to English in the spelling of languages or territories. If the value is actually ok, then click on the Hide button (crossed eye). If not, then vote for a fix, or post on the Forum for discussion.
The New items are the newly entered items for this release, and are provided here for reference. You don't normally need to look at them.
There are two ways to clear items from the Dashboard list:
The reports show lists of items that need to be reviewed for consistency. You should look through these after you do the Dashboard to make sure that the items are consistent, when viewed in the context of others. Each of them has a link to instructions at the top. Please read these before continuing.
Translations should be what is most appropriate for ”middle-of-sentence” use. So, for example, if your language normally doesn't spell languages with a capital letter, then you shouldn’t do that here. Please see Capitalization for more details.
For important information regarding the use of plural forms for your language, please read Plurals.
If you find a problem, you may want to review FAQ & Known Bugs to see whether it has already been reported (and whether there is a work-around). If not, or if you have suggestions for improvements, please file a bug using the Feedback link at the bottom of each window. If you encounter problems or have enhancement suggestions for the survey tool, please file a ticket.
If there are other issues, you can raise them on the Unicode CLDR Mailing List.
For unofficial SurveyTool support, visit #cldr on freenode webchat — Once connected, enter your text at the very bottom of the page, and press the enter key to send text). Alternatively, use your own client to log into the #cldr channel on the freenode.net network.
If you click on the Code cell and there is no Information Panel, you may have turned it off accidentally. Go to the Gear icon at the top and make sure that the Toggle is set right.
You may sometimes see a message like the following.
These items are particularly sensitive, and require committee review. To handle them, click on the Code cell (eg, “Main Letters”). In the right-hand information panel, you'll see details. At the bottom, click on the “Flag for Review button”. On the new page, you'll see a message box. Enter the change that you want to make, and the justification for it. Then click “Post”.
After the data submission phase, any differences in the submitted data will be resolved according to the data resolution process. However, you should collaborate with the other translators where you have questions, via email and the forums.
The forum is the place to debate issues in your language. Use the forum for general topics or consistency questions. If you want to bring up a specific topic, click on the data point in the survey tool or in the Dashboard, then click the New Forum Post or Forum button to the right. This will allow you to make a forum post directly linked to the data item that will also show up when the item is selected in the survey tool, to make it visible for other linguists.
When you make a forum entry, it will be emailed to all other linguists working on the same locale. Note that the forum is sorted by parent locale and has no sub-forums for sub-locales. If you are talking about a translation in a sub-locale, be sure that you’re clear about that.