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

Vetting Phase

Once the data submission phase closes, there is a short period for you to work with other translators to fix any remaining problems, and come to consensus on the best choice for each field. So that you and others have more stability, changes can't be made except in the case of errors or where there are multiple proposals already.

To fix the problems in the locales, please:
  • Log in
  • Review the Proposed Changes
    • Go to the Change Charts, which show the current proposed changes for locales for the next release.
    • The index chart shows a summary of the changes (it's a bit cryptic, sorry!). For example: Dutch (nl) [N:64; c:77; a:14] means that Dutch has 64 items not accepted, 77 items changed, and 14 items added.
    • Find each of your locales, and do the following. (Use CTRL-F or ⌘-F to search for your locales by name.)
      1. Open the locale changes page by clicking on the link (eg Dutch (nl)).
      2. Scan the list for changes/additions that have been accepted that you think shouldn't be, or changes/additions that have not been accepted that you think should be.
      3. If you click on the Item column, you'll go right to the Zoomed view. Fix the problem (see Fixing Problems) and Save Changes.
    • These charts are only updated twice a day, so they won't show fixes until about 1:00 and 13:00 Pacific time. So sometimes someone else has already resolved the problem.
  • Review Errors
    • Find each of your locales, and do the following:
      1. Open the locale errors page by clicking on the link (eg nl)
      2. The highest priority items are at the top, typically "error". (See Windows and Key for more information.)
      3. Click on the Section to get to the right section.
      4. You should see the problems at the top of the list (you may have to hit "Priority" in the Nav bar to get there).

        Sorted: Code Priority English-Name

      5. If you click on the Status icon, you'll go right to the Zoomed view. Fix the problem (see Fixing Problems) and Save Changes.
    • These charts are only updated twice a day, so they won't show fixes until about 1:00 and 13:00 Pacific time. So sometimes someone else has already resolved the problem.
  • Review Consistency
    • If you have time after doing the above, it is useful to review items for consistency.
    • Go to each Section in the survey tool (ie, languages | scripts | territories | variants | ...)
      • Sort by Code.
      • Check that related items (like singular/plural) don't have spurious differences
      • Check that closely related items have consistent translations.
If you have any questions, please contact your organization's CLDR Technical Committee member, or email surveytool@unicode.org.

Fixing Problems

  • Use the Survey tool to vote for the right items. Remember to click on Save Changes before you leave each page to make sure that your votes are counted.
    • During the vetting period, new data is not allowed unless an item has an error or warning.
    • Known bug: if you are trying to correct an error by clicking on a fallback item (in red, see below), the Survey tool may not let you.
  • It takes consensus among the translators to make any change, so please work with the other translators and committee members to resolve any differences that keep an item from being approved. If the best item doesn't have enough votes, or is contested, work with the other translators to resolve any differences.
    • You can use the forums to work with other translators, or direct emails, whichever you find works better.
    • Please be respectful of people's time, and try to keep any postings short and to the point.
    • Please focus your energies on items that are clearly incorrect; if the approved item is not the best, but "ok", then concentrate on other items first.
  • If you have questions or problems that are general - not specific to your locale - you can also send email to cldr-users@unicode.org -- see CLDR Users to join.
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. Please also look at the notes in the zoomed view, such as Sample Zoomed View, and the sections below in this document for more information.

Windows

Please review the items in the first sections below: Error Values, Disputed, and Unconfirmed.

Section
 Status*
 Description
 		What to do
Error Values
 		[stop] The (otherwise) optimal value is not approved, because it has an error:
  • A syntax error, such as a malformed number pattern
  • A collision, such as two different territories translated by the same name
  • A missing minimally-required field, such as a missing month name
Please look these over and suggest an alternative, or vote for an alternative if the right one is there. See Consensus.
Disputed

 [ques] [warn] The optimal value is not approved, because the votes are split.
Unconfirmed
 [ques] [warn] The optimal value is not approved, because there are not enough votes.
Tentatively Approved

 [okay] [warn] The optimal value is tentatively approved. No action necessary. (However, look over this section quickly to see that there are no errors, because of a known bug in sorting.)
Status Quo
 		[okay] [squo] [ques] [warn] There was no new value submitted during the earlier data submission phase. No action necessary.
(You can't make any changes. If there are serious problems, report them as discussed below.)
  • (*) The status is the status of the optimal value. This column shows the possible status values. For the meaning of each icon, see the Key.

Key

Group
 		Description
The following icons show the status of the "best" value for each field. Click on this icon to "zoom" in for more information. For some items, you need to zoom in order to make any changes.
[okay] There is a (tentatively) approved value, with no warnings or errors.
[ques] The value is not approved because it is disputed, has insufficient votes, or is missing.
[warn] There is probably a problem in the field value.
[stop] There is a serious error in the field value.
[squo] The field value is not approved, but no alternatives were submitted. So it is the same as in CLDR 1.4.
The following icons show information about different field values
[star] This icon is on the value that was present in Unicode CLDR 1.4 (in some cases as modified by the committee).
[vote] In the zoomed view if you hover over this icon, you see the votes for that value. You'll also see details listed below.
[disp] If you see this icon in the Locales View or after an item, that means your own organization is splitting its vote on a field. Pay special attention to resolving those issues within your organization so that your vote is not lost.
bengâglî A green background indicates a tentatively approved value. (If no other changes are made, it will be approved.)
Beng A red background indicates a "fallback", which is what would be used if all other items were deleted. A vote for this is essentially a vote for deletion.
Twi
 A blue background indicates an "alias", where the data is coming from somewhere else. For example, the days of the week for other calendars typically all derive from the Gregorian calendar's days of the week.

If the alias is not inherited, it takes committee action to make a change, so file a bug if that is needed.

References

If the item is disputed, please add a reference (see the FAQ). Ideally, the reference has a link that is sufficiently clear that an non-native speaker (a committee member) can check the reference. For example, the following link goes to a page that, while not in English, is sufficiently clear. Where needed, the reference text should explain how to interpret the page.