Vetting Review

THIS PAGE HAS NOT YET BEEN UPDATED FOR THE NEW UI!

Once you have finished entering data, you will need to review the items for correctness. There are a number of pages to help you do that. You will see these pages listed after "Review:" near the top of your screen, such as the following:


You can also see a video walkthrough of the review sections on Walkthrough.


The rest of this page discusses how to do the Priority Items. Once you have done the Priority Items, click on the other review items and follow the instructions on those pages:
Remember to periodically look at the Forum for your locale. 
  1. On any page in your locale, near the top there is a link "Forum".
  2. Click on it and go through the comments.
  3. If there is a request to change values or votes, either respond on the Forum with why you disagree, or change your vote.
  4. Some issues may be general, such as the capitalization of language names. In the vetting period, please try to resolve these in accordance with the other items in the locale for consistency; leave anything else for the next release. 
If you have time after doing the above, it is useful to review items for consistency.
  1. Go to each Section in the survey tool
  2. Check that related items (like singular/plural) don't have spurious differences
  3. Check that closely related items have consistent translations.

Priority Items

Open your locale, such as http://unicode.org/cldr/apps/survey?_=de, and log in.

Click on Priority Items. After it loads you’ll see a view over all the possible issues for your locale. Once it loads you can leave it open while you work through the items, so you won’t have to reload very often.

Warning: 
  • Make sure your coverage level is set correctly: typically modern*. Otherwise you won't see all the issues for your language.
  • After you change your coverage, or to see the new status of changed items, you must click the Refresh Values button.
In the Priority view, you can see the important issues for your language. At the top is a summary for each kind of issue, looking something like the following:

Summary

For instructions, see Priority Items.

Count Abbr. Description
0 ☐ Error* The Survey Tool detected an error in the winning value.
411 ☐ Losing* The value that your organization chose (overall) is either not the winning value, or doesn't have enough votes to be approved.
4 ☐ Disputed* There is a dispute between other organizations that needs your help in resolving to the best value.
0 ☐ Warning* The Survey Tool detected a warning about the winning value.
265 ☐ Unsync’d* The English value changed at some point in CLDR, but the corresponding value for your language didn’t.
130 ☐ New* The winning value was altered from the last-released CLDR value.
36 ☐ Missing* Your current coverage level requires the item to be present, but it is missing.

It is followed by a list of issues, categorized by type.

How to Proceed

You will click on each of the check-boxes above that that don't have a count of zero, and follow the instructions below.

If you have any questions, please contact your organization's CLDR Technical Committee member, or email surveytool@unicode.org.

Goals

Data Submission Phase

  1. Concentrate on fixing the Missing items first, since you can't fix them in the Vetting phase.
  2. You can then work on Error, Warning and Unsync'ed items.

Vetting Phase

  1. Review the New items and Unsync'ed items to make sure that they make sense.
  2. Work on getting of the Error, Losing, Disputed counts down to zero.
    1. The Warning and Unsync'd counts might not be zero after you are done.
    2. The count for New items is informative, it just represents the changes in this release. You do not have to try to reduce it.
Go through the summary list, clicking the checkbox (☑) to show the issues of type you're working on. You can click several at once if you find that easier. That will then expose the issues of that type below the summary.

How to Handle

Handle each of the types of issues as follows:

Missing* (only applicable during Data Submission Phase)

  1. Add the missing value, or vote for an "inherited" value (in a special color)
  2. Unless there is some other error, you can't change these during the vetting phase, so make sure to get them done early!

Error*, Warning*

  1. Go to the item (by clicking the Fix? link).
  2. Error items will be removed from the release, so they are a priority in the vetting phase.
  3. Review the warning items; most of them need fixing but not all. See Fixing Errors and Warnings

Losing*, Disputed*

  1. See if the winning value is ok. If so, change your vote to it, and go to the next item.
  2. Otherwise, post a message to the Forum.
    1. State why you think the item should be changed.
    2. If there are a number of items that have the same characteristic (such as the wrong capitalization), you can make that case in a single posting rather than multiple ones.

New*

  1. Quickly scan over these values.
  2. If the values are ok, then you don't need to do anything. If not, follow the instructions above.

Unsync’d*

For the Unsync'd issues, the older English value is listed below the new one, and in Red. (See below). These often indicate that a change needs to be made in your language. For example, in the tables below
  1. The English value was changed so that the locale "zh-Hans" shows up as "Chinese (Simplified)" rather than the somewhat redundant  "Chinese (Simplified Han)". The corresponding change should be made to French.
  2. Similarly, the English was simplified for "Unknown Script"; that change should also be made to French.
  3. On the other hand, the change for that particular currency name in English is specific to English, and doesn't need to be reflected in French.
Section: names — Page: script

No. Code English CLDR 1.9.1 Winning 2.0 Fix?
358 Hans Simplified
Simplified Han
idéogrammes han simplifiés = Unsync’d*
359 Hant Traditional
Traditional Han
idéogrammes han traditionnels = Unsync’d*
360 Zzzz Unknown Script
Unknown or Invalid Script
écriture inconnue ou non valide = Unsync’d*

Section: names — Subsection: currency

No. Code English CLDR 1.9.1 Winning 2.0 Fix?
... ... ... ... ... ...
29 BIF:name Burundian Franc
Burundi Franc
franc burundais = Unsync’d*

Review

Once you have completed your items, review the Priority Items again to see that all the changes are as expected. 

Comments