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

FAQ and Known Bugs

Contents

  1. 1 Known Issues for the 1.8 Beta
  2. 2 Issues to Watch For
  3. 3 FAQ (Frequently Asked Questions)
  4. 4 Known Bugs
    1. 4.1 Operation
    2. 4.2 Navigation
    3. 4.3 Examples and Help
    4. 4.4 Formatting
    5. 4.5 Errors and Voting
    6. 4.6 Features not in this Version
The following are known bugs and issues. Some will be fixed during the vetting period; for some there are work-arounds in the FAQ; for others, send an email to cldr-users@unicode.org.

Known Issues for the 1.8 Beta

This section will be updated with any known issues with the Survey Tool 1.8 time period.
  1. You may see %%$%% in the Code field. While ugly, that won't affect operation.
    1. eg http://unicode.org/cldr/apps/survey?_=zu&forum=zu&xpath=18274
  2. Some fields may show up as (empty)
    1. eg http://unicode.org/cldr/apps/survey?_=zu&forum=zu&xpath=1827
  3. Certain new territories (AC, CP, EA,...) and the language ssy are missing English translations
    1. eg http://unicode.org/cldr/apps/survey?_=zu&x=territories
  4. ...

Issues to Watch For

The English translations have changed for the following items, and you should adjust your native language terms to correspond:

English
Ascension Island
Clipperton Island
Diego Garcia
Ceuta and Melilla
Canary Islands
Tristan da Cunha
Myanmar [Burma]
Palestinian Territories
Congo - Kinshasa
Congo [DRC]
Congo - Brazzaville
Congo [Republic]
Côte d’Ivoire
Ivory Coast
Falkland Islands
Falkland Islands [Islas Malvinas]
Hong Kong SAR China
Hong Kong
Macedonia
Macedonia [FYROM]
Macau SAR China
Macau
Timor-Leste
East Timor
Cantonese
Comorian
Pinyin Romanization
Wade-Giles Romanization

    FAQ (Frequently Asked Questions)

    Q. Should I preserve the case of English words, like names of languages?
    A. You want to have whatever is customary for names of languages, such as when listed in computer menus. However, you want to make sure that there is consistent casing for all of the items, so before making any changes, be sure to get agreement among all the translators for your language -- otherwise we'll get a ransom note effect!
    Q. What about the warning about parentheses being discouraged in cases such as "(other)"
    A. You need to remove "(other)" or the equivalent from language names. In general, you should avoid using parentheses in the names of languages, scripts, or regions if at all possible. There is more information about this in the zoomed view.
    Q. How do I go to the zoomed view?
    A. Click on the status icon: [okay], [ques], [warn], [stop], or [squo]
    Q. Why is the tool slow?
    A. The tool may be slow if many people are active at the same time. It is also slow the first time you open a page, and especially slow after any update to the code. Also, when you make changes, it reruns the tests over all possible items that could be related, which can take some time.

    We ask your patience when this happens. If it is preventing you from doing your work, please sent a message to cldr-users@unicode.org (CLDR Users).
    Q. Is there anything else I can do about it?
    A. For those items where you can use the "unzoomed view", you can make all of the changes on the page at once, which saves time. Just remember to save your changes before leaving the page, or they will be lost!
    Q. I tried to zoom in on an item, but no window opened up. What is happening?
    A. When you zoom in, the contents open in another window (or tab). Unfortunately, your browser may not bring that window to the top, so you may have to bring that window (or tab) to the front manually. What helps, if you have a wide screen, is to right-click when zooming the first time, and open a separate window, then move that window so it doesn't overlap. The same for the References window.
    Q. How are votes weighted and the "best" item picked?
    A. You basically want to get multiple organizations to agree on the best value. For details on the voting process, see Resolution Procedure.
    Q. How do I add a reference to a value?
    A. First off, you only need references where an item is contentious -- where you want to point to a dictionary or other reference to establish that it is the right usage. Unfortunately, adding references is a bit cumbersome right now. A reference is bundled together with a value, so to add a reference to a value, go to the zoom view, copy the value to the Change box, and use the pulldown reference menu to pick the reference.
    Q. But what if the reference is not listed in the pulldown?
    A. Then you need to click on the "Add/Lookup References" link. That will take you to a page where you can add a new reference (and see all the details on the others).
    Q. In the key, it says that the red box is a fallback. What does that mean?
    A. The Unicode CLDR data uses inheritance. That means that if you are looking at English (United Kingdom) (a "sublocale") most of the data is inherited from English (which contains data for the US), called the "parent locale". Such data will show up as red. You only need to have different data in the sublocale where there are important differences in usage from the parent locale.

    Data in a sublocale may be spuriously different; that is, the parent's data may be perfectly acceptable in the sublocale, but somehow a difference has crept in. In that case, you should vote for the parent's data to reduce the gratuitous differences.
    Q. But what I see is a funny symbol like Zxxx?
    A. If there is no other translation available, what you will see is a "neutral" code, typically an ISO code. In cases where there is no such code available, such as for labels like "Month", then you may see English -- which needs to be translated.
    Q. How do I delete an item?
    A. You can only delete an item if you yourself have entered it, and there are no other votes. Go to the zoom view. You should see a checkbox marked Delete Item. Click on it and save changes. To remove a spurious difference in a sublocale, vote for the red fallback item.
    Q. What if I can't delete it?
    A. It doesn't really matter much. What is really important is to make sure the the right item is voted for; so try to get consensus as described above. If all the alternatives are really wrong, and you really don't know what the right item would be, vote for the red fallback item.
    Q. What if I want to just try out some changes, but don't want to affect the data?
    A. Everyone can add data to "Unknown or Invalid Language" (und), so you can try out the Survey tool there without worry.
    Q. What if I have questions?
    A. You should zoom in on the items you have questions about, and read the information towards the bottom of the page.

    In many cases, even seemingly straightforward translations like the language, script, and territory names have issues. For example, these may have been direct translations from ISO standards, which are quite often not the best ones names for computer interfaces.

    If you have further questions, or problems with the Survey Tool, send a message to cldr-users@unicode.org.

    Known Bugs

    Operation

    1. Losing changes when leaving a page
      • If you navigate away from a page, but don't save the changes, your changes will be lost. This also happens if there is no activity on the page for a while (like 10 minutes).
      • Work-Around: if you've made changes, don't leave a page without [Save Changes]
    2. Zooming, but don't see new window
      • When you zoom in, the contents open in another window (or tab). Unfortunately, your browser may not bring that window to the top, so you may have to bring that window (or tab) to the front manually.
      • Work-around, see the FAQ
    3. References are a bit clumsy (but you only need them in cases of disputes) Work-arounds:
      • To add a reference to an item, you have to copy the item to the Change box, and add the reference number.
      • To see what the reference numbers mean, you need to hit the "Ref:" link to see the references window.
      • If you pick a reference in the zoomed view, but don't put anything into the Change box, and no changes are made when you Save Changes -- and you see no notification of that, so you won't realize that nothing was done.
      • The change box in the references view doesn't let you change the URL. Work-around: enter in a new reference with the URL.
      • Other work-arounds: see the FAQ.
    1. Priority View Sorting
      • In the priority view, the groupings should correspond to the icons: Errors, Warnings, Unapproved Items, Approved Items, Inherited Items. However, the last three sets are not sorted in separate sections. That means that you have to look through all of the last section for problems.
      • The title text for the icons should be: the singular of the above term (eg Warning) plus " - click for details"

    Navigation

    1. When a side window (references or zoom) is opened, it may not come to the front; or if the user is in full-screen mode, may completely hide the main view.
      • Workaround: don't make the browser window full-screen, and have the zoom and references windows both visible (on large screens) or overlapping (on small ones).
    2. In a forum window, View Item and Reply should be visibly links (eg underlined).
    3. The Forum messages for an item should be always shown in the zoomed view, at the bottom.

    Examples and Help

    1. The CheckDates demo doesn't work with mm:ss.SS
    2. There needs to be a one-digit day example, to show the difference between EEEE, dd MMMM yyyy and EEEE, d MMMM yyyy

    Formatting

    1. The Change text box may overlap the following column (appears to be a browser bug, but we need to compensate for it.)
    2. The CheckNumbers and CheckDates demos should be inlined in the zoomed view, not requiring extra link click.
    3. People seem to miss some of the links on the page, like General Instructions at the top right.
    4. Code Lists and Other Items should be clearer, we call them Sections elsewhere. Perhaps List Sections and Pattern Sections?
    5. Fields that have a single space (like the French thousands separator) can't be distinguished from being empty. Invisible characters like RLM may be hard to work with.
    6. There are occasional minor display problems:
      1. overlapping text
      2. missing table lines
    7. There are some confusing messages or UI:
      1. The coverage level should be grayed during the vetting period, since it has no effect.

    Errors and Voting

    1. False error message when fixing missing value
      • When there is an error because an field is missing a value, and you add a new value, it may show you a false error message at the top saying "Warning: Needed to meet basic coverage level."
      • Work-around: ignore the message in that case.
    2. The error counts are not included in the Disputed summaries.
      • This means that the disputed counts in the summaries may understate (somewhat) the number of problems.
      • Work-Around: Go to the Error Report Index, and find the errors for your locales.
    3. Errors not sorting in the right spot.
      1. Example: http://www.unicode.org/cldr/apps/survey?_=he&forum=he&xpath=90651
      2. It should sort in the Error section -- instead it is sorting in the Tentatively Approved section:
        1. http://www.unicode.org/cldr/apps/survey?_=he&x=languages
      3. Work-Around: quickly review the Tentatively Approved section looking for Error status icons.

    Features not in this Version

    1. Sorting (collation) order is not shown. [TBD: describe workaround using ICU demo]