This
page explains the different views used in entering in CLDR data. The
exact appearance may change as the tool is enhanced over time.
Italics and yellow highlighting are used to comment on particular features below.
Navigation
Once you start on a particular locale, most windows have a navigation bar at the top. It looks like the following.
On the left is the locale structure. On the right are the different sections you will need to go through. The forum is where you and other translators for this locale can discuss problem cases. Choosing the Gregorian Calendar section (or any other section) yields the main view.
Main View
Every main view contains a navigation bar that looks something like this:
| |
|
|
|
Hit this button to save. Note that you must do this before you leave a page, or your changes are lost! |
| Sorted:
Code
Priority
English-Name |
Items 1 to 80 of 211 |
|
Normally
you'll use the Priority ordering, but to find specific items, you may
sort by Code. You may also sort items by their English names. |
| ← prev next → |
|
prev and next
will go between pages. |
| Errors and Warnings:
available date forma…– |
|
The list is
broken into sections, according to status. |
| Unconfirmed:
AM–h:mm a
|
|
There may be multiple pages in a section, so don't forget to view them all (using this
list or next/previous).
The items on other pages are non-bold. |
|
Others:
add–Thursday
Thu–S
September– |
|
Below the navigation bar, you'll see something like this:

Here
is what all these symbols and backgrounds mean. Most of the buttons
have a short explanation if you "hover" your mouse over them. When
pushed, they go do the zoomed view.
Key
| Column |
Example |
Description |
Comments |
| Status |
![ok [OK]](http://unicode.org/cldr/apps/okay.png) |
approved |
The proposed value will be approved (if no other changes are made). |
Click on any of these to zoom
in on details: warnings, examples, and demos (as available) |
![[Inherited]](http://unicode.org/cldr/apps/squo.png) |
inherited: |
The proposed value comes from the parent locale, and is approved there. |
![Unconfirmed: insufficient [Unconfirmed]](http://unicode.org/cldr/apps/ques.png) |
not approved |
The proposed value doesn't have enough votes to be approved |
![Warning: push zoom to see details [Warning]](http://unicode.org/cldr/apps/warn.png) |
warning: |
There is at least one mechanically generated warning message for this value. |
|
error: |
There is a mechanically detected error with the value. |
|
Code
|
bho |
code |
This is an internal, constant code used to access the translation, both in English and
in other languages. It is sometimes a longer value, like available date formats:[@id="Hm"] |
|
| Proposed |
bichlamar |
winner |
If nothing else is done, this will be confirmed as the value in the release. |
If the bichlamar item is the
right one, you can continue. Otherwise,
select the right value () or add a new value.
|
| blin |
loser |
If nothing else is done, this item will not be chosen. |
| bho |
inherited |
The value comes from the "parent" locale. For example, in "en_GB", this indicates a
value from 'en'. If the value is wrong for the parent, you should fix it there. |
| bugg |
alias |
The value comes from another part of this locale, or from another locale. For example,
the Japanese calendar's months may be the same as the Gregorian (Western) calendar's. |
|
grc |
untranslated |
Picking this value is the equivalent of removing a translation. |
| Ex. |
1,234.56 |
example |
Provides
examples of patterns in usage. If text is substituted in a pattern, it
is shown in gray. For example, there is a pattern used in timezones
"{0} Time". In the example, a sample value is used to show what it
would look like, as "Japan Time" |
|
| Change |
|
add proposed value |
Allows you to add new proposed value. Do this if none of the other values
are correct. Clicking in the box will automatically select the button, indicating that you are adding this item. |
|
|
n/o
|
|
no opinion / no addition |
If you have no opinion -- or you want to not add an item after clicking in the Change box , select n/o. |
|
Main View with Examples
Many
of the strings are just simple names, such as the names of the
languages above. Those are called "Code Lists" in the tool. Others are
a bit more complicated, and are either patterns or parts of patterns. For example, look at the following.
In
this case the value that you can choose is a pattern that indicates how
a number is to be formatted for your language. This is very much like
the "custom formatting" used in spreadsheets. In such cases, the tool
will show (where possible) a short example of what the format will
result in.
To see what the patterns or their components mean, click on the Status icon:
,
,
,
,
![Errors - please zoom in [Error]](http://unicode.org/cldr/apps/stop.png)
Zoom View with Examples
Status icons act as "zoom buttons". Once
you hit any of the zoom button, you get a separate window with a more
detailed view of just that item. With some browsers, this window isn't
brought up to the front, so it helps to make your main view smaller
than the full screen, and put this window to the side. The contents of the zoom view will look
like the following.
If
you created a value for an item but have since decided that the value
is incorrect, and if nobody else has voted for the value yet,
then in zoom view a "Delete item" checkbox will appear, offering you
the opportunity to delete the value.
Note
that only technical committe members will see the Create Alternate button (don't use
this unless you know what you are doing).
Whenever an item is
controversial, you should add a reference for it. Use the Add/Lookup References link,
to see the available references, add a new one if you need to. Then pick
the reference number from the list.
The links at the bottom provide help.
Demo View
Some Zoom views have demo links, where you can try out different values to see the formatting. For example, CheckNumbers results in:
Description
Dates, times, and numbers are formatted using patterns, like
"mm-dd", "#,##0.##" and so on. Different characters stand for
different parts of the number. You need to use '.' for the decimal
point and ',' for the thousands (grouping) separator, even if
they are not used in your language. For special characters used in
data and number format patterns, see Appendix F: Date Format Patterns
and Appendix G: Number Format Patters of
UTS #35: Unicode Locale Data Markup Langauge.
Supplemental Data
The supplemental
link in the navigation bar takes you to a different kind of window, for
information about languages and countries. This data was collected
based on information from the World Bank and other sources (see the top
of the pages for more information). As a native speaker you may have
better access to sources of the data than are available in English, so
we'd appreciate your reviewing this information.
| Language |
Code |
Territory |
Code |
Language Population |
German
click on each country code |
de |
Germany |
DE |
75,032,000 |
| Austria |
AT |
7,500,600 |
| Switzerland |
CH |
4,203,200 |
| ... |
|
add new |
|
0 |
If there is a major country or territory missing for the language, click
add new to
report a bug. For each of the countries that you are familiar with
where your language is in major use, click on the country code (eg AT). You'll see a view like this.
| Territory |
Code |
Terr. Pop (M) |
Terr. Literacy |
Terr. GDP ($M PPP) |
Currencies (2006...) |
Days in week (min) |
First day of week |
First day of weekend |
Last day of weekend |
Meas. system |
Paper Size |
calendar (+gregorian) |
Language |
Code |
Lang. Pop.% |
Lang. Literacy |
Report Bug |
| Austria |
AT |
8.1 |
98.0% |
267,600 |
Euro [EUR] |
4 |
mon |
sat |
sun |
metric |
A4 |
|
German |
de |
92.6% |
98.0% |
bug |
| Croatian |
hr |
1.2% |
bug |
|
add new |
|
.0% |
.0% |
If any of the details are wrong in the table, you can report a bug with the
bug link. You can also request adding another language with the
add new link. Some notes:
- The language population should be the proportion of people who are fluent (functionally) in the language, as a first or second language. Thus
the figures may add to more than 100%.
- The Days in week (min) is the minimum number of days in a week for it to count as the first week of the year (or month). For example, in some
countries there need to be 4 days in the first week (starting from the First day of week)
for it to count as week number 1; in others, what counts as the first
week may only need one day. For example, January 1, 1998 was a
Thursday. If the first day of the week is MONDAY and the minimum days
in a week is 4, then week 1 of 1998 starts on December 29, 1997, and
ends on January 4, 1998. However, if the first day of the week is
SUNDAY, then week 1 of 1998 starts on January 4, 1998, and ends on
January 10, 1998. The first three days of 1998 are then part of week 53
of 1997.