diff --git a/docs/site/TEMP-TEXT-FILES/ddl.txt b/docs/site/TEMP-TEXT-FILES/ddl.txt deleted file mode 100644 index ffc93725ea4..00000000000 --- a/docs/site/TEMP-TEXT-FILES/ddl.txt +++ /dev/null @@ -1,7 +0,0 @@ -CLDR DDL Subcommittee -The Common Locale Data Repository (CLDR) is widely used, and the content has grown dramatically over the years with participation by organizations of all types and sizes, as well as many individual contributors. -Contributors for Digitally Disadvantaged Languages (DDL) face unique challenges. The CLDR-DDL subcommittee has been formed to evaluate mechanisms to make it easier for contributors for DDLs to: -become contributors to CLDR -improve the coverage for their language in CLDR -raise the status of their contributions, so that the CLDR data for their language is incorporated into more products. -The DDL Subcommittee has started to meet every other week as of June, 2023. \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/index-bcp47-extension.txt b/docs/site/TEMP-TEXT-FILES/index-bcp47-extension.txt deleted file mode 100644 index af25e2b780a..00000000000 --- a/docs/site/TEMP-TEXT-FILES/index-bcp47-extension.txt +++ /dev/null @@ -1,20 +0,0 @@ -Unicode Extensions for BCP 47 -IETF BCP 47 Tags for Identifying Languages defines the language identifiers (tags) used on the Internet and in many standards. It has an extension mechanism that allows additional information to be included. The Unicode Consortium is the maintainer of the extension ‘u’ for Locale Extensions, as described in rfc6067, and the extension 't' for Transformed Content, as described in rfc6497. -The subtags available for use in the 'u' extension provide language tag extensions that provide for additional information needed for identifying locales. The 'u' subtags consist of a set of keys and associated values (types). For example, a locale identifier for British English with numeric collation has the following form: en-GB-u-kn-true -The subtags available for use in the 't' extension provide language tag extensions that provide for additional information needed for identifying transformed content, or a request to transform content in a certain way. For example, the language tag "ja-Kana-t-it" can be used as a content tag indicates Japanese Katakana transformed from Italian. It can also be used as a request for a given transformation. -For more details on the valid subtags for these extensions, their syntax, and their meanings, see LDML Section 3.7 Unicode BCP 47 Extension Data. -Machine-Readable Files for Validity Testing -Beginning with CLDR version 1.7.2, machine-readable files are available listing the valid attributes, keys, and types for each successive version of LDML. The most recently released version is always available at http://unicode.org/Public/cldr/latest/ in a file of the form cldr-common*.zip (in older versions the file was of the form cldr-core*.zip). Inside that file, the directory "common/bcp47/" contains the data files defining the valid attributes, keys, and types. -The BCP47 data is also currently maintained in a source code repository, with each release tagged, for viewing directly without unzipping. For example, see https://github.com/unicode-org/cldr/tree/release-38/common/bcp47. The current development snapshot is found at https://github.com/unicode-org/cldr/tree/master/common/bcp47. -All releases including the latest are listed on http://cldr.unicode.org/index/downloads, with a link to each respective data directory under the column heading Data, and direct access to the repository under the GitHub Tag. -For example, the timezone.xml file looks like the following: - - - - -Using this data, an implementation would determine that "fr-u-tz-adalv" and fr-u-tz-aedxb" are both valid. Some data in the CLDR data files also requires reference to LDML for validation according to Appendix Q of LDML. For example, LDML defines the type 'codepoints' to define specific code point ranges in Unicode for specific purposes. -Version Information -The following is not necessary for correct validation of the -u- extension, but may be useful for some readers. -Each release has an associated data directory of the form "http://unicode.org/Public/cldr/", where "" is replaced by the release number. The version number for any file is given by the directory where it was downloaded from. If that information is no longer available, the version can still be accessed by looking at the common/dtd/ldml.dtd file in the cldr-common*.zip file (for older versions, the core.zip file), at the element cldrVersion, such as the following. This information is also accessible with a validating XML parser. - -For each release after CLDR 1.8, types introduced in that release are also marked in the data files by the XML attribute "since", such as in the following example: \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/index-charts.txt b/docs/site/TEMP-TEXT-FILES/index-charts.txt deleted file mode 100644 index a5210ca0799..00000000000 --- a/docs/site/TEMP-TEXT-FILES/index-charts.txt +++ /dev/null @@ -1,23 +0,0 @@ -CLDR Charts -The Unicode CLDR Charts provide different ways to view the Common Locale Data Repository data. -Latest - The charts for the latest release version -Dev - A snapshot of data under development -Previous - Previous available charts are linked from the download page in the Charts column -The format of most of the fields in the charts will be clear from the Name and ID, such as the months of the year. The format for others, such as the date or time formats, is structured and requires more interpretation. For more information, see UTS #35: Locale Data Markup Language (LDML). -Most charts have "double links" somewhere in each row. These are links that put the address of that row into the address bar of the browser for copying. -Note that not all CLDR data is included in the charts. -Version Deltas -Delta Data - Data that changed in the current release. -Delta DTDs - Differences between CLDR DTD's over time. -Locale-Based Data -Verification - Constructed data for verification: Dates, Timezones, Numbers -Summary - Provides a summary view of the main locale data. Language locales (those with no territory or variant) are presented with fully resolved data; the inherited or aliased data can be hidden if desired. Other locales do not show inherited or aliased data, just the differences from the respective language locale. The English value is provided for comparison (shown as "=" if it is equal to the localized value, and n/a if not available). The Sublocales column shows variations across locales. Hovering over each Sublocale value shows a pop-up with the locales that have that value. -By-Type - provides a side-by-side comparison of data from different locales for each field. For example, one can see all the locales that are left-to-right, or all the different translaitons of the Arabic script across languages. Data that is unconfimred or provisional is marked by a red-italic locale ID, such as ·bn_BD·. -Character Annotations - The CLDR emoji character annotations. -Subdivision Names - The (draft) CLDR subdivision names (names for states, provinces, cantons, etc.). -Collation Tailorings - Collation charts (draft) for CLDR locales. -Other Data -Supplemental Data - General data that is not part of the locale hierarchy but is still part of CLDR. Includes: plural rules, day-period rules, language matching, language-script information, territories (countries), and their subdivisions, timezones, and so on. -Transform - (Disabled temporarily) Some of the transforms in CLDR: the transliterations between different scripts. For more on transliterations, see Transliteration Guidelines. -Keyboards - Provides a view of keyboard data: layouts for different locales, mappings from characters to keyboards, and from keyboards to characters. -For more details on the locale data collection process, please see the CLDR process. For filing or viewing bug reports, see CLDR Bug Reports. \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/index-keyboard-workgroup.txt b/docs/site/TEMP-TEXT-FILES/index-keyboard-workgroup.txt deleted file mode 100644 index 4cf1cca777c..00000000000 --- a/docs/site/TEMP-TEXT-FILES/index-keyboard-workgroup.txt +++ /dev/null @@ -1,37 +0,0 @@ -CLDR Keyboard Subcommittee -The CLDR Keyboard Subcommittee is developing a new cross-platform standard XML format for use by keyboard authors for inclusion in the CLDR source repository. -News -2023-Feb-29: The CLDR-TC has authorized the proposed specification to be released as stable (out of Technical Preview). -2023-May-15: The CLDR-TC has authorized Public Review Issue #476 of the proposed specification, as a "Technical Preview." The PRI closed on 2023-Jul-15. -Background -CLDR (Common Locale Data Repository) -Computing devices have become increasingly personal and increasingly affordable to the point that they are now within reach of most people on the planet. The diverse linguistic requirements of the world's 7+ billion people do not scale to traditional models of software development. In response to this, Unicode CLDR has emerged as a standards-based solution that empowers specialist and community input, as a means of balancing the needs of language communities with the technologies of major platform and service providers. -The challenge and promise of Keyboards -Text input is a core component of most computing experiences and is most commonly achieved using a keyboard, whether hardware or virtual (on-screen or touch). However, keyboard support for most of the world's languages is either completely missing or often does not adequately support the input needs of language communities. Improving text input support for minority languages is an essential part of the Unicode mission. -Keyboard data is currently completely platform-specific. Consequently, language communities and other keyboard authors must see their designs developed independently for every platform/operating system, resulting in unnecessary duplication of technical and organizational effort. -There is no central repository or contact point for this data, meaning that such authors must separately and independently contact all platform/operating system developers. -LDML: The universal interchange format for keyboards -The CLDR Keyboard Subcommittee is currently rewriting and redeveloping the existing LDML (XML) definition for keyboards (UTS#35 part 7) in order to define core keyboard-based text input requirements for the world's languages. This format allows the physical and virtual (on-screen or touch) keyboard layouts for a language to be defined in a single file. Input Method Editors (IME) or other input methods are not currently in scope for this format. -CLDR: A home for the world's newest keyboards -Today, there are many existing platform-specific implementations and keyboard definitions. This project does not intend to remove or replace existing well-established support. -The goal of this project is that, where otherwise unsupported languages are concerned, CLDR becomes the common source for keyboard data, for use by platform/operating system developers and vendors. -As a result, CLDR will also become the point of contact for keyboard authors and language communities to submit new or updated keyboard layouts to serve those user communities. CLDR has already become the definitive and publicly available source for the world's locale data. -Unicode: Enabling the world's languages -Keyboard support is part of a multi-step, often multi-year process of enabling a new language or script. -Three critical parts of initial support for a language in content are: -Encoding, in the Unicode Standard -Display, including fonts and text layout -Input -Today, the vast majority of the languages of the world are already in the Unicode encoding. The open-source Noto font provides a wide range of fonts to support display, and the Unicode character properties play a vital role in display. However, input support often lags many years behind when a script is added to Unicode. -The LDML keyboard format, and the CLDR repository, will make it much easier to deliver text input. -Common Questions -What is the history of this effort? -In 2012, the original LDML keyboard format was designed to describe keyboards for comparative purposes. In 2018, a PRI was created soliciting further feedback. -The CLDR Keyboard Subcommittee was formed and has been meeting since mid-2020. It quickly became apparent that the existing LDML format was insufficient for implementing new keyboard layouts. -What is the current status? -Release -Updates to LDML (UTS#35) Part 7: Keyboards are scheduled to be released as part of CLDR v45. -Implementations -The SIL Keyman project is actively working on an open-source implementation of the LDML format. -How can I get involved? -If you want to be engaged in this workgroup, please contact the CLDR Keyboard Subcommittee via the Unicode contact form. \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/index-process.txt b/docs/site/TEMP-TEXT-FILES/index-process.txt deleted file mode 100644 index 58a7f404862..00000000000 --- a/docs/site/TEMP-TEXT-FILES/index-process.txt +++ /dev/null @@ -1,144 +0,0 @@ -CLDR Process -Introduction -This document describes the Unicode CLDR Technical Committee's process for data collection, resolution, public feedback and release. -The process is designed to be light-weight; in particular, the meetings are frequent, short, and informal. Most of the work is by email or phone, with a database recording requested changes (See change request). -When gathering data for a region and language, it is important to have multiple sources for that data to produce the most commonly used data. The initial versions of the data were based on best available sources, and updates with new and improvements are released twice a year with work by contributors inside and outside of the Unicode Consortium. -It is important to note that CLDR is a Repository, not a Registration. That is, contributors should NOT expect that their suggestions will simply be adopted into the repository; instead, it will be vetted by other contributors. -The CLDR Survey Tool is the main channel for collecting data, and bug/feature request are tracked in a database (CLDR Bug Reports). -The final approval of the release of any version of CLDR is up to the decision of the CLDR Technical Committee. -Formal Technical Committee Procedures -For more information on the formal procedures for the Unicode CLDR Technical Committee, see the Technical Committee Procedures for the Unicode Consortium. -Specification Changes -The UTS #35: Locale Data Markup Language (LDML) specification are kept up to date with each release with change/added structure for new data types or other features. -Requests for changes are entered in the bug/feature request database (CLDR Bug Reports). -Structural changes are always backwards-compatible. That is, previous files will continue to work. Deprecated elements remain, although their usage is strongly discouraged. -There is a standing policy for structural changes that require non-trivial code for proper implementation, such as time zone fallback or alias mechanisms. These require design discussions in the Technical Committee that demonstrates correct function according to the proposed specification. -Data- Submission and Vetting -The contributors of locale data are expected to be language speakers residing in the country/region. In particular, national standards organizations are encouraged to be involved in the data vetting process. -There are two types of data in the repository: -Core data (See Core data for new locales): The content is collected from language experts typically with a CLDR Technical Committee member involvement, and is reviewed by the committee. This is required for a new language to be added in CLDR. See also Exemplar Character Sources. -Common locale data: This is the bulk of the CLDR data and data collection occurs twice a year using the Survey tool. (See How to Contribute.) -The following 4 states are used to differentiate the data contribution levels. The initial data contributions are normally marked as draft; this may be changed once the data is vetted. -Level 1: unconfirmed -Level 2: provisional -Level 3: contributed (= minimally approved) -Level 4: approved (equivalent to an absent draft attribute) -Implementations may choose the level at which they wish to accept data. They may choose to accept even unconfirmed data if having some data is better than no data for their purpose. Approved data are vetted by language speakers; however, this does not mean that the data is guaranteed to be error-free -- this is simply the best judgment of the vetters and the committee according to the process. -Survey Tool User Levels -There are multiple levels of access and control: -Vetter Level Number of Votes Description -TC Member 50 / 6 or 4 - Manage users in their organization -- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) -- Can see the email addresses for all vetters in their organization -- Only uses a 50 vote for items agreed to by the CLDR technical Committee -- TC members may have a 6 or 4 regular vote depending on how actively their organization participates in the TC -TC Organization Managers 6 - Manage users in their organization -- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) -- Can see the email addresses for all vetters in their organization -Organization Managers 4 -Manage users in their organization -- Can vet and submit data for all locales (However, their vetting work is only done to correct issues.) -- Can see the email addresses for all vetters in their organization -TC Organization Vetter 6 - Can vet and submit data for a particular set of locales. -- Can see the email addresses for submitted data in their locales. -- Cannot manage other users. -Organization Vetter 4 - Can vet and submit data for a particular set of locales -- Can see the email addresses for submitted data in their locales. -- Cannot manage other users. -Guest Vetter 1 - Can vet and submit data for a particular set of locales -- Cannot see email addresses. -- Cannot manage other users. -Locked Vetter 0 - If a user is locked or removed, then their vote is considered a zero weight. -These levels are decided by the technical committee and the TC representative for the respective organizations. -Unicode TC members (full/institutional/supporting) can assign its users to Regular or Guest level, and with approval of the TC, users at the Expert level. -TC Organizations that are fully engaged in the CLDR Technical Committee are given a higher vote level of 6 votes to reflect their level of expertise and coordination in the working of CLDR and the survey tool as compared to the normal organization vote level of 4 votes -Liaison or associate members can assign to Guest, or to other levels with approval of the TC. -The liaison/associate member him/herself gets TC status in order to manage users, but gets a Guest status in terms of voting, unless the committee approves a higher level. -Users assigned to "unicode.org" are normally assigned as Guest, but the committee can assign a different level. -Voting Process -Each user gets a vote on each value, but the strength of the vote varies according to the user level (see table above). -For each value, each organization gets a vote based on the maximum (not cumulative) strength of the votes of its users who voted on that item. -For example, if an organization has 10 Vetters for one locale, if the highest user level who voted has user level of 4 votes, then the vote count attributed to the organization as a whole is 4 for that item. -Optimal Field Value -For each release, there is one optimal field value determined by the following: -Add up the votes for each value from each organization. -Sort the possible alternative values for a given field -by the most votes (descending) -then by UCA order of the values (ascending) -The first value is the optimal value (O). -The second value (if any) is the next best value (N). -Draft Status of Optimal Field Value -Let O be the optimal value's vote, N be the vote of the next best value (or zero if there is none), and G be the number of organizations that voted for the optimal value. Let oldStatus be the draft status of the previously released value. -Assign the draft status according to the first of the conditions below that applies: -Resulting Draft Status Condition -approved - O > N and O ≥ 8, for established locales* -- O > N and O ≥ 4, for other locales -contributed - O > N and O ≥ 4 and oldstatus < contributed -- O > N and O ≥ 2 and G ≥ 2 -provisional O ≥ N and O ≥ 2 -unconfirmed otherwise -Established locales are currently found in coverageLevels.xml, with approvalRequirement[@votes="8"] -Some specific items have an even higher threshold. See approvalRequirement elements in coverageLevels.xml for details. -If the oldStatus is better than the new draft status, then no change is made. Otherwise, the optimal value and its draft status are made part of the new release. -For example, if the new optimal value does not have the status of approved, and the previous release had an approved value (one that does not have an error and is not a fallback), then that previously-released value stays approved and replaces the optimal value in the following steps. -It is difficult to develop a formulation that provides for stability, yet allows people to make needed changes. The CLDR committee welcomes suggestions for tuning this mechanism. Such suggestions can be made by filing a new ticket. -Data- Resolution -After the contribution of collecting and vetting data, the data needs to be refined free of errors for the release: -Collisions errors are resolved by retaining one of the values and removing the other(s). -The resolution choice is based on the judgment of the committee, typically according to which field is most commonly used. -When an item is removed, an alternate may then become the new optimal value. -All values with errors are removed. -Non-optimal values are handled as follows -Those with no votes are removed. -Those with votes are marked with alt=proposed and given the draft status: unconfirmed -If a locale does not have minimal data (at least at a provisional level), then it may be excluded from the release. Where this is done, it may be restored to the repository for the next submission cycle. -This process can be fine-tuned by the Technical Committee as needed, to resolve any problems that turn up. A committee decision can also override any of the above process for any specific values. -For more information see the key links in CLDR Survey Tool (especially the Vetting Phase). -Notes: -If data has a formal problem, it can be fixed directly (in CVS) without going through the above process. Examples include: -syntactic problems in pattern, extra trailing spaces, inconsistent decimals, mechanical sweeps to change attributes, translatable characters not quoted in patterns, changing ' (punctuation mark) to curly apostrophe or s-cedilla to s-comma-below, removing disallowed exemplar characters (non-letter, number, mark, uppercase when there is a lowercase). -These are changed in-place, without changing the draft status. -Linguistically-sensitive data should always go through the survey tool. Examples include: -names of months, territories, number formats, changing ASCII apostrophe to U+02BC modifier letter apostrophe or U+02BB modifier letter turned comma, or U+02BD modifier letter reversed comma, adding/removing normal exemplar characters. -The TC committee can authorize bulk submissions of new data directly (CVS), with all new data marked draft="unconfirmed" (or other status decided by the committee), but only where the data passes the CheckCLDR console tests. -The survey tool does not currently handle all CLDR data. For data it doesn't cover, the regular bug system is used to submit new data or ask for revisions of this data. In particular: -Collation, transforms, or text segmentation, which are more complex. -For collation data, see the comparison charts at http://www.unicode.org/cldr/comparison_charts.html or the XML data at http://unicode.org/cldr/data/common/collation/ -For transforms, see the XML data at http://unicode.org/cldr/data/common/transforms/ -Non-linguistic locale data: -XML data: http://unicode.org/cldr/data/common/supplemental/ -HTML view: http://www.unicode.org/cldr/data/diff/supplemental/supplemental.html -Prioritization -There may be conflicting common practices or standards for a given country and language. Thus LDML provides keyword variants to reflect the different practices (for example, for German it allows the distinction between PHONEBOOK and DICTIONARY collation.). -When there is an existing national standard for a country that is widely accepted in practice, the goal is to follow that standard as much as possible. Where the common practice in the country deviates from the national standard, or if there are multiple conflicting common practices, or options in conforming to the national standard, or conflicting national standards, multiple variants may be entered into the CLDR, distinguished by keyword variants or variant locale identifiers. -Where a data value is identified as following a particular national standard (or other reference), the goal is to keep that data aligned with that standard. There is, however, no guarantee that data will be tagged with any or all of the national standards that it follows. -Maintenance Releases -Maintenance releases, such as 26.1, are issued whenever the standard identifiers change (that is, BCP 47 identifiers, Time zone identifiers, or ISO 4217 Currency identifiers). Updates to identifiers will also mean updating the English names for those identifiers. -Corrigenda may also be included in maintenance releases. Maintenance releases may also be issued if there are substantive changes to supplemental data (non-language such as script info, transforms) data or other critical data changes that impact the CLDR data users community. -The structure and DTD may change, but except for additions or for small bug fixes, data will not be changed in a way that would affect the content of resolved data. -Data Retention Policy -Public Feedback Process -The public can supply formal feedback into CLDR via the Survey Tool or by filing a Bug Report or Feature Request. There is also a public forum for questions at CLDRMailing List (details on archives are found there). -There is also a members-only CLDRmailing list for members of the CLDR Technical Committee. -Public Review Issues may be posted in cases where broader public feedback is desired on a particular issue. -Be aware that changes and updates to CLDR will only be taken in response to information entered in the Survey Tool or by filing a Bug Report or Feature Request. Discussion on public mailing lists is not monitored; no actions will be taken in response to such discussion -- only in response to filed bugs. The process of checking and entering data takes time and effort; so even when bugs/feature requests are accepted, it may take some time before they are in a release of CLDR. -Data Release Process -Version Numbering -The locale data is frozen per version. Once a version is released, it is never modified. Any changes, however minor, will mean a newer version of the locale data being released. The version numbering scheme is "xy.z", where z is incremented for maintenance releases, and xy is incremented for regular semi-annual releases as defined by the regular semi-annual schedule -Release Schedule -Early releases of a version of the common locale data will be issued as either alpha or beta releases, available for public feedback. The dates for the next scheduled release will be on CLDR Project. -The schedule milestones are listed below. -Milestone JiraPhase Description -Survey Tool Shakedown Selected survey tool users try out the survey tool and supply feedback. The contributed data will be considered as real data. -Data Submission dsub All survey tool registered u sers can add data and vet (vote for) for data -Data Vetting dvet The survey tool users focus shifts to resolving data differences/disputes, and resolve errors. -Data Resolution T he data contribution is closed for general contributors. The Technical Committee will close remaining errors and issues found during the release process . -Alpha and Beta releases rc The release candidates are available for testing. Only showstoppers will be triage and fixed at this point. -Release final Release completed with referenceable release notes and links. -Labels in the Jira column correspond to the phase field in Jira. Phase field in Jira is used to identify tickets that need to be completed before the start of each milestone (table above). -Meetings and Communication -The currently-scheduled meetings are listed on the Unicode Calendar. Meetings are held by phone, every week at 8:00 AM Pacific Time (-08:00 GMT in winter, -07:00 GMT in summer). Additional meeting is scheduled every other Mondays depending on the need and people's availability. -There is an internal email list for the Unicode CLDR Technical Committee, open to Unicode members and invited experts. All national standards bodies who are interested in locale data are also invited to become involved by establishing a Liaison membership in the Unicode Consortium, to gain access to this list. -Officers -The current Technical Committee Officers are: -Chair: Mark Davis (Google) -Vice-Chair: Annemarie Apple (Google) \ No newline at end of file diff --git a/docs/site/TEMP-TEXT-FILES/index-survey-tool.txt b/docs/site/TEMP-TEXT-FILES/index-survey-tool.txt deleted file mode 100644 index 5aeb81462c1..00000000000 --- a/docs/site/TEMP-TEXT-FILES/index-survey-tool.txt +++ /dev/null @@ -1,16 +0,0 @@ -CLDR Survey Tool -Survey Tool | Accounts | Guide | FAQ and Known Bugs -Introduction -CLDR provides key building blocks for software to support the world's languages, with the largest and most extensive standard repository of locale data available. -Translations in the Unicode Common Locale Data Repository are gathered and processed via what is called the Survey Tool, an online tool that can be used to view data for different languages and propose additions or changes. This tool provides a way to propose new localized data, see what others have proposed, and communicate with them to resolve differences. During each submission period, contributors from Unicode Consortium members, other organizations and the public at large are invited to review the data for their languages and countries, and propose new translations of terms or modifications, including language translations entirely new to the repository. -Below are the main pages to look at. -Schedule -For the Milestone schedule, see the navigation bar on the left. -Accounts -You don't need an account to view data for a particular language. If you wish to propose changes or additions, you will need an account. For how to get one, see Survey Tool Accounts. If you would like to add data for a new locale, see Adding New Locales. -Guide -For an overview of how the Survey Tool works, see the Survey Tool Guide. -New Fields -To see a summary of the new fields that will be in the next version of CLDR, see http://cldr.unicode.org/index/downloads/dev. At the top of that page you can follow a link to the beta release page. -Development -For developers, see the development pages. \ No newline at end of file diff --git a/docs/site/images/GettingStartedGuideImportOldVotes.png b/docs/site/images/GettingStartedGuideImportOldVotes.png new file mode 100644 index 00000000000..74a31caed99 Binary files /dev/null and b/docs/site/images/GettingStartedGuideImportOldVotes.png differ diff --git a/docs/site/images/errors-and-warnings.png b/docs/site/images/errors-and-warnings.png new file mode 100644 index 00000000000..980d1ef3b1f Binary files /dev/null and b/docs/site/images/errors-and-warnings.png differ diff --git a/docs/site/images/gettingStartedGuideAgree.png b/docs/site/images/gettingStartedGuideAgree.png new file mode 100644 index 00000000000..e796f6307d0 Binary files /dev/null and b/docs/site/images/gettingStartedGuideAgree.png differ diff --git a/docs/site/images/gettingStartedGuideArabic.png b/docs/site/images/gettingStartedGuideArabic.png new file mode 100644 index 00000000000..88fb621784b Binary files /dev/null and b/docs/site/images/gettingStartedGuideArabic.png differ diff --git a/docs/site/images/gettingStartedGuideAutoAgree.png b/docs/site/images/gettingStartedGuideAutoAgree.png new file mode 100644 index 00000000000..675cd9f1971 Binary files /dev/null and b/docs/site/images/gettingStartedGuideAutoAgree.png differ diff --git a/docs/site/images/gettingStartedGuideBrazil.png b/docs/site/images/gettingStartedGuideBrazil.png new file mode 100644 index 00000000000..676a20675c9 Binary files /dev/null and b/docs/site/images/gettingStartedGuideBrazil.png differ diff --git a/docs/site/images/gettingStartedGuideCharsInUse.jpeg b/docs/site/images/gettingStartedGuideCharsInUse.jpeg new file mode 100644 index 00000000000..f57a7161ece Binary files /dev/null and b/docs/site/images/gettingStartedGuideCharsInUse.jpeg differ diff --git a/docs/site/images/gettingStartedGuideColorCode.png b/docs/site/images/gettingStartedGuideColorCode.png new file mode 100644 index 00000000000..a443d5803e1 Binary files /dev/null and b/docs/site/images/gettingStartedGuideColorCode.png differ diff --git a/docs/site/images/gettingStartedGuideComment.png b/docs/site/images/gettingStartedGuideComment.png new file mode 100644 index 00000000000..77b4a39ad88 Binary files /dev/null and b/docs/site/images/gettingStartedGuideComment.png differ diff --git a/docs/site/images/gettingStartedGuideCookies.png b/docs/site/images/gettingStartedGuideCookies.png new file mode 100644 index 00000000000..7ae1f902c4c Binary files /dev/null and b/docs/site/images/gettingStartedGuideCookies.png differ diff --git a/docs/site/images/gettingStartedGuideCoverage.png b/docs/site/images/gettingStartedGuideCoverage.png new file mode 100644 index 00000000000..6b14f164839 Binary files /dev/null and b/docs/site/images/gettingStartedGuideCoverage.png differ diff --git a/docs/site/images/gettingStartedGuideDashboard.png b/docs/site/images/gettingStartedGuideDashboard.png new file mode 100644 index 00000000000..a9cf5595f29 Binary files /dev/null and b/docs/site/images/gettingStartedGuideDashboard.png differ diff --git a/docs/site/images/gettingStartedGuideDashboardCols.png b/docs/site/images/gettingStartedGuideDashboardCols.png new file mode 100644 index 00000000000..77ff3c25f59 Binary files /dev/null and b/docs/site/images/gettingStartedGuideDashboardCols.png differ diff --git a/docs/site/images/gettingStartedGuideEnglish.jpg b/docs/site/images/gettingStartedGuideEnglish.jpg new file mode 100644 index 00000000000..7c2a34ef354 Binary files /dev/null and b/docs/site/images/gettingStartedGuideEnglish.jpg differ diff --git a/docs/site/images/gettingStartedGuideForum.jpeg b/docs/site/images/gettingStartedGuideForum.jpeg new file mode 100644 index 00000000000..abb74b6f0b9 Binary files /dev/null and b/docs/site/images/gettingStartedGuideForum.jpeg differ diff --git a/docs/site/images/gettingStartedGuideForumPosts.png b/docs/site/images/gettingStartedGuideForumPosts.png new file mode 100644 index 00000000000..2051e5a065b Binary files /dev/null and b/docs/site/images/gettingStartedGuideForumPosts.png differ diff --git a/docs/site/images/gettingStartedGuideGeneralInfo.png b/docs/site/images/gettingStartedGuideGeneralInfo.png new file mode 100644 index 00000000000..b3ae2a313b1 Binary files /dev/null and b/docs/site/images/gettingStartedGuideGeneralInfo.png differ diff --git a/docs/site/images/gettingStartedGuideICUSyntax.png b/docs/site/images/gettingStartedGuideICUSyntax.png new file mode 100644 index 00000000000..aa38d10ec34 Binary files /dev/null and b/docs/site/images/gettingStartedGuideICUSyntax.png differ diff --git a/docs/site/images/gettingStartedGuideIcon.png b/docs/site/images/gettingStartedGuideIcon.png new file mode 100644 index 00000000000..9d280800fba Binary files /dev/null and b/docs/site/images/gettingStartedGuideIcon.png differ diff --git a/docs/site/images/gettingStartedGuideImportSelectedItems.jpeg b/docs/site/images/gettingStartedGuideImportSelectedItems.jpeg new file mode 100644 index 00000000000..af5e0402172 Binary files /dev/null and b/docs/site/images/gettingStartedGuideImportSelectedItems.jpeg differ diff --git a/docs/site/images/gettingStartedGuideKorean.png b/docs/site/images/gettingStartedGuideKorean.png new file mode 100644 index 00000000000..0761ebf5d0f Binary files /dev/null and b/docs/site/images/gettingStartedGuideKorean.png differ diff --git a/docs/site/images/gettingStartedGuideLocaleSearch.png b/docs/site/images/gettingStartedGuideLocaleSearch.png new file mode 100644 index 00000000000..efdd15b21fa Binary files /dev/null and b/docs/site/images/gettingStartedGuideLocaleSearch.png differ diff --git a/docs/site/images/gettingStartedGuideMissing.png b/docs/site/images/gettingStartedGuideMissing.png new file mode 100644 index 00000000000..f357be95fbb Binary files /dev/null and b/docs/site/images/gettingStartedGuideMissing.png differ diff --git a/docs/site/images/gettingStartedGuideNeedingAction.png b/docs/site/images/gettingStartedGuideNeedingAction.png new file mode 100644 index 00000000000..3893dfe1f3f Binary files /dev/null and b/docs/site/images/gettingStartedGuideNeedingAction.png differ diff --git a/docs/site/images/gettingStartedGuideNotOpenYet.jpeg b/docs/site/images/gettingStartedGuideNotOpenYet.jpeg new file mode 100644 index 00000000000..94798f07ce2 Binary files /dev/null and b/docs/site/images/gettingStartedGuideNotOpenYet.jpeg differ diff --git a/docs/site/images/gettingStartedGuideOldWinningVotes.jpg b/docs/site/images/gettingStartedGuideOldWinningVotes.jpg new file mode 100644 index 00000000000..ead2fb5f936 Binary files /dev/null and b/docs/site/images/gettingStartedGuideOldWinningVotes.jpg differ diff --git a/docs/site/images/gettingStartedGuideOverallProgress.png b/docs/site/images/gettingStartedGuideOverallProgress.png new file mode 100644 index 00000000000..20afa298816 Binary files /dev/null and b/docs/site/images/gettingStartedGuideOverallProgress.png differ diff --git a/docs/site/images/gettingStartedGuidePageProgress.png b/docs/site/images/gettingStartedGuidePageProgress.png new file mode 100644 index 00000000000..3160ac0edaa Binary files /dev/null and b/docs/site/images/gettingStartedGuidePageProgress.png differ diff --git a/docs/site/images/gettingStartedGuidePatterns.jpeg b/docs/site/images/gettingStartedGuidePatterns.jpeg new file mode 100644 index 00000000000..e775ebe8dc7 Binary files /dev/null and b/docs/site/images/gettingStartedGuidePatterns.jpeg differ diff --git a/docs/site/images/gettingStartedGuidePortuguese.png b/docs/site/images/gettingStartedGuidePortuguese.png new file mode 100644 index 00000000000..70959d8f805 Binary files /dev/null and b/docs/site/images/gettingStartedGuidePortuguese.png differ diff --git a/docs/site/images/gettingStartedGuideReasons.png b/docs/site/images/gettingStartedGuideReasons.png new file mode 100644 index 00000000000..c903e2fef1e Binary files /dev/null and b/docs/site/images/gettingStartedGuideReasons.png differ diff --git a/docs/site/images/gettingStartedGuideRequest.png b/docs/site/images/gettingStartedGuideRequest.png new file mode 100644 index 00000000000..6060856345d Binary files /dev/null and b/docs/site/images/gettingStartedGuideRequest.png differ diff --git a/docs/site/images/gettingStartedGuideSideBar.png b/docs/site/images/gettingStartedGuideSideBar.png new file mode 100644 index 00000000000..b04617bf4a2 Binary files /dev/null and b/docs/site/images/gettingStartedGuideSideBar.png differ diff --git a/docs/site/images/gettingStartedGuideSpanish.jpg b/docs/site/images/gettingStartedGuideSpanish.jpg new file mode 100644 index 00000000000..33552a8bd15 Binary files /dev/null and b/docs/site/images/gettingStartedGuideSpanish.jpg differ diff --git a/docs/site/images/gettingStartedGuideVarientDropdown.png b/docs/site/images/gettingStartedGuideVarientDropdown.png new file mode 100644 index 00000000000..6116dc7a0fd Binary files /dev/null and b/docs/site/images/gettingStartedGuideVarientDropdown.png differ diff --git a/docs/site/images/gettingStartedGuideVote.png b/docs/site/images/gettingStartedGuideVote.png new file mode 100644 index 00000000000..a8f34cb478d Binary files /dev/null and b/docs/site/images/gettingStartedGuideVote.png differ diff --git a/docs/site/images/gettingStartedGuideVoteCol.jpeg b/docs/site/images/gettingStartedGuideVoteCol.jpeg new file mode 100644 index 00000000000..cb5f9115030 Binary files /dev/null and b/docs/site/images/gettingStartedGuideVoteCol.jpeg differ diff --git a/docs/site/images/gettingStartedGuideWarning.png b/docs/site/images/gettingStartedGuideWarning.png new file mode 100644 index 00000000000..73da2191940 Binary files /dev/null and b/docs/site/images/gettingStartedGuideWarning.png differ diff --git a/docs/site/translation/getting-started.md b/docs/site/translation/getting-started.md new file mode 100644 index 00000000000..95dfcf1482f --- /dev/null +++ b/docs/site/translation/getting-started.md @@ -0,0 +1,24 @@ +--- +title: @Getting Started +--- + +# @Getting Started + +Before getting started to contribute data in CLDR, and jumping in to using the Survey Tool, it is important that you understand the CLDR process. + +1. Understand the basics about the CLDR process and the community-based model and the Technical Committee. Read: [CLDR Process](https://cldr.unicode.org/index/process) +2. Read the Getting Started topics on the Information Hub: + - [Survey Tool Guide](https://cldr.unicode.org/translation/getting-started/guide) + - [Survey Tool Stages](https://cldr.unicode.org/translation/getting-started/survey-tool-phases) + - [Handling Errors and Warnings](https://cldr.unicode.org/translation/getting-started/errors-and-warnings) + - [Handling Logical Group Errors](https://cldr.unicode.org/translation/getting-started/resolving-errors) + - [Plurals & Units](https://cldr.unicode.org/translation/getting-started/plurals) + - [Review Date & Time](https://cldr.unicode.org/translation/date-time) + - [Review Numbers](https://cldr.unicode.org/translation/number-currency-formats) + - [Review Zones](https://cldr.unicode.org/translation/time-zones-and-city-names) + - [Data stability](https://cldr.unicode.org/translation/getting-started/data-stability) + - [Empty cache](https://cldr.unicode.org/translation/getting-started/empty-cache) + +\*If you (individual or your organization) have not established a connection with the CLDR technical committee, start with [Survey Tool Accounts](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts). + +![Unicode copyright](https://www.unicode.org/img/hb_notice.gif) \ No newline at end of file diff --git a/docs/site/translation/getting-started/errors-and-warnings.md b/docs/site/translation/getting-started/errors-and-warnings.md new file mode 100644 index 00000000000..e77776c7eb3 --- /dev/null +++ b/docs/site/translation/getting-started/errors-and-warnings.md @@ -0,0 +1,61 @@ +--- +title: Handling Errors and Warnings +--- + +# Handling Errors and Warnings + +_\* Note that if the committee finds systematic errors in data, new tests can be added during the submission period, resulting in new Errors or warnings._ + +## Errors + +Errors in the survey tool MUST be fixed for the Winning column. Following are common errors that you may encounter and tips on ways to fixing them. + +- **Can't have same translation as… (Must fix)** + +Exactly the same name can't be used for two different items of the same type. + +For example, it is an error if "Malawi-Kwacha" is used as the translation for two different currency codes: + +- MZN (Mozambican metical), and +- MWK (Malawian Kwachas) + +In the above case, it is a pretty clear mistake. It is not as simple in other cases. Some region names are very similar, for example, and it can be a bit tricky to know how to handle them. Currencies have the problem that a new currency code may have the same name as an obsolete one. + +You can find some guidance under "Unique Names" in the following pages: + +- [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names), +- [City Names](https://cldr.unicode.org/translation/timezones#TOC-City-Names), +- [Currency Symbols & Names](https://cldr.unicode.org/translation/currency-names-and-symbols/currency-names) + +**The characters ‎\[…\]‎ should not be used (Must fix)** + +For what to do, see [Characters](https://cldr.unicode.org/translation/-core-data/exemplars#TOC-Handing-Warnings-in-Exemplar-characters), in the section Handling Warnings. _While these are categorized as warnings, every effort should be made to fix them._ + +**Unquoted special character '.' in pattern (Must fix)** + + +Number patterns can only contain an unquoted . when it is the decimal separator. + +In other cases, such as to finish an abbreviation, it must be quoted, as in: 000 tūkst'.' + +For more information, see [Number Patterns](https://cldr.unicode.org/translation/number-currency-formats/number-and-currency-patterns). + +- Errors in Others column can be ignored. For example, this is an example of an Inheritance value in the Others column where the Language (Country/region) names have a collision issue. Do not vote on values that have errors. + +![alt-text](../../images/errors-and-warnings.png) + +## Warnings + +- **The value is the same as in English** + +Because a common mistake is for people to copy the English values precisely, a warning is provided when this happens. + +This may not be an error, because it is often perfectly legitimate to have an identical string. For example, the word for "France" in French is the same as English, for example. So this warning is just to call your attention to the text in case it needs to be changed. + +- **The value is the same as 'code'** + +Another common mistake is to copy a code value, such as "cs" for Czech, instead of translating it. + +This may not be an error, because it is often perfectly legitimate to have an identical string.For example the script code for "Thai" is "Thai", which matches the English word exactly. So this warning is just to call your attention to the text in case it needs to be changed. + +![Unicode copyright](https://www.unicode.org/img/hb_notice.gif) \ No newline at end of file diff --git a/docs/site/translation/getting-started/guide.md b/docs/site/translation/getting-started/guide.md new file mode 100644 index 00000000000..62e762264cb --- /dev/null +++ b/docs/site/translation/getting-started/guide.md @@ -0,0 +1,447 @@ +--- +title: Survey Tool Guide +--- + +# Survey Tool Guide + +### _News_ + +_2022-11-28 Updated several images and instructions to reflect improvements, such as revised menus, buttons,regional inheritance, and the Dashboard and Forum._ + +[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) + +The Survey tool is a web based tool for collecting CLDR data and includes various features that the contributors (vetters) should know before getting started. + +Note that the exact appearance in screenshots may change as the tool is enhanced over time and based on your vetter level. + +### 💡 Helpful Tips + +- Please read the home page of the [Translation Guidelines](https://cldr.unicode.org/translation) before starting your data contribution. + - If you experience a **Loading...** problem with the Survey Tool, try clearing your browser cache. See [Reloading JavaScript](https://www.filecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XOjGNtMzbuM). +- **Browser support** for Survey Tool includes the latest versions of Edge, Safari, Chrome, and Firefox. +- Use [Reports](https://cldr.unicode.org/translation/getting-started/guide#TOC-Reports) at the beginning to review the data in your language in a holistic manner for Date & time, Zones, and Numbers. + - Capitalization: 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](https://cldr.unicode.org/translation/translation-guide-general/capitalization) for more details. + - Plurals: For important information regarding the use of plural forms for your language, please read [Plurals](https://cldr.unicode.org/translation/getting-started/plurals). + +### Vetting Phase + +At a point towards the end of Survey Tool period, the Technical Committee will change the survey tool to "Vetting Mode". In Vetting Mode, submitting new data/translations is no longer possible, but you can still change your votes and participate in the forum. (The exception is that you can submit new data if the currently winning value has generated an error or a warning.) + +## Login and Import of old votes + +1. Go to http://st.unicode.org/cldr-apps/survey/ and log in. +![alt-text](../../images/gettingStartedGuideNotOpenYet.jpeg) +1. **Import of old votes** is automatically handled when you log in for all your votes **matching** the latest released data. If you have voted previously, upon first log-in, you will see a message showing the number of your votes that matched the currently winning votes that have been auto-imported. +2. Import of your old votes will take some time, but this will be done at 1st log-in only. +![alt-text](../../images/gettingStartedGuideOldWinningVotes.jpg) + +1. **Import old votes manually**. You can still import your old voted data that **DO NOT match** the last released data. + 1. Go to the **☰ Menu**, look under **My Votes**, and choose **Import Old Votes**. + ![alt-text](../../images/GettingStartedGuideImportOldVotes.png) + +![alt-text](../../images/gettingStartedGuideImportSelectedItems.jpeg) + +1. Scroll to the bottom to see the category selection for bulk import. +2. Select the categories that you want to import and click **Import selected items** button at the bottom. +3. Go to the data categories in the Survey tool where you have imported your old votes, these will show up in the Others column with no votes. +4. Review and add your vote. The best practice is to create a forum entry explaining why this is the data that should be changed to and drive to gain consensus with other vetters. + + +### Picking Locales + +1. On the left sidebar, you will see the CLDR locale(s). Your default view will be the languages you have permissions for. All the locales that you have permission to contribute submissions to are marked with PENCIL icon. You can view the others but not submit contributions. For example, if you have permissions to the default language Afrikaans (af), you will not have permissions to Afrikaans (Namibia), and vice versa. + +![alt-text](../../images/gettingStartedGuideLocaleSearch.png) + +1. Each language is followed by a list of regions that represent specific locales. The locale that is grayed out and preceded by an × is the default. The others are considered “sub-locales”. If you are working on the default locale, select the language name. For example, if you work on Spanish in general (default = Spain), you will see that that Spain is grayed out in the list below: choosing Spanish means that you are working on the default (Spanish for Spain). + +![alt-text](../../images/gettingStartedGuideSpanish.jpg) + +1. Only those of you working on a specific variant language (or "sub-locale") will pick a non-default region. If you work on Mexican Spanish, pick **Mexico**. (This should already be pre-selected for you.) + + +_Make sure that you haven't mistakenly turned the Information Panel off! See_ [_**No Information Panel**_](https://cldr.unicode.org/translation/getting-started/guide%23TOC-No-Information-Panel)_**.**_ + +### Voting view + +1. Once you have selected your locale, more options show up in the left sidebar. (You’ll note that the sidebar only shows if you mouse over the **\>** character on the left.) +2. If the locale is relatively new and very complete, start working on the **Core Data** section and go through the rest of the sections. If the locale is mostly complete, then go to [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide) below. +3. Once you have selected a section, you'll see a table to enter votes in. The main table has these columns: + - **Code**: the code CLDR uses to identify this data point. + - **English**: the plain English value of the data point (the text you are to translate). + - **Abstain**: the default vote value for you. Only use abstain if you don't know a good value to be used. + - **A**: The value’s current status. A checkmark means it’s approved and is slated to be used. A cross means it’s a missing value. (Note, for sub-locales, a cross is not necessarily bad. If the parent locale has a good value, the sub-locale will inherit it. Check the **Winning** column.) + - **Winning**: this is the currently winning value. If the survey tool would close now, this is the value we would publish. If the value has a blue star next to it, that means it’s also the value that was published in the previous version. Normally it takes at least two votes from two different organizations to change value: in some locales the bar is lower, and for some items it is higher. + - **Add**: If the winning value is not correct and is not listed under Others, then use the plus button here to enter the correct value. If you enter a new value, your vote will be applied to it automatically. + - If what you want is a variation of what is in Winning or Others, you can cut & paste, and then modify. + - **Others**: other suggested values, not currently winning, but available to vote for. +4. Click on one of the radio buttons to make your vote. The winning status changes in real-time so depending on vote requirements and existing votes, your vote may move your desired value to the winning column right away. + 1. Look at the Regional Variants to see if any should be changed: see **Information Panel** below. +5. Once you are done with all the sections, go to the [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide)**.** +6. Under the English column, look for "**i**" for additional information and "**e**" for an example. +![alt-text](../../images/gettingStartedGuideArabic.png) +![alt-text](../../images/gettingStartedGuideEnglish.jpg) + +### Icons + +The main panel uses icons to indicate important information and possible problems. After clicking on the **Code** cell, look to the right-side info panel for more details. + +![alt-text](../../images/gettingStartedGuideIcon.png) + +(Icons for the **Dashboard** are listed in the [**Dashboard Icons**](https://cldr.unicode.org/translation/getting-started/guide) section below.) + +### Examples + +An example with an ❌ shows a case where the pattern has an inappropriate placeholder substituted. That example should be ungrammatical; if it is grammatical, then either the translated unit or the minimal pair pattern itself is incorrect. The example will show in the Info Panel, and also if you hover over the item. + +### Information Panel + +1. If you hover over an item (including the English item), a tooltip will appear showing a sample value and usage of the item in context. The item itself will have a white background; other text in context will have a gray background. +2. When you select an item (the text, **NOT** the radio button), additional information will show in the right-hand **Information Panel**. See screenshot below. +3. Make sure you use a wide-screen monitor and enlarge your window until you can see it, something like the image below. +4. The box at the top shows information about the code you are translating. _It also has a link that you should click on the first type you encounter that kind of item that will explain any "gotchas"._ +5. If there is an error or warning for the item, you see that in the middle. +6. Below that, you'll see an example. This is the same as you get by hovering over the item in the center section. +7. If there are votes, you'll see a breakdown of them; you also see the number of votes required to change the value. Unicode organization members usually have 4 votes; _vetters which are not representing a Unicode organization usually have 1 vote_. Your vote value and the vote value required for change will show on the right navigation for the selected item as shown in this screenshot (4 and 8 respectively in this case). +8. Near the bottom, you'll see a pulldown menu that shows the values for different regional Variants. Here, you can quickly compare the values and go to different sub-locales to correct inconsistencies. +9. You'll also see the New Forum Post button (as shown in the screenshot _to the right_). This is the easiest way to post discussions for the selected item. Remember that the Forum posts are at language level and not at Sub-locale level. For more information, see [Forum](https://cldr.unicode.org/translation/getting-started/guide). +10. **No Information Panel?** + - If you click on the **Code** cell and there is no **Information Panel**, you may have turned it off accidentally. Click on the **Open Info Panel** button near the top right of the window. + +![alt-text](../../images/gettingStartedGuideSideBar.png) +![alt-text](../../images/gettingStartedGuideCookies.png) + +## Inheritance + +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: + +![alt-text](../../images/gettingStartedGuideColorCode.png) + +You can click on the link in the right sidebar to see the original value. + +**Note:** Voting on inheritance means "always use the inherited value, even if it changes.” An inheritance vote is advised if there are no differences in spelling conventions and political relations between your locale and the parent locale. Voting for inheritance minimizes duplication of data. + +### Regional Variants (also known as Sub-locales) + +Language variants by Region are differentiated as Parent-locale and sub-locales. For example, + +- **Spanish es** is the parent (or the default) locale for all Spanish locales. Its default content is for Spanish (Spain) es\_ES. + +- **Spanish (Latin America) es\_419** is one of the sub-locales for Spanish. Votes on inheritance will ensure that it will only contain content that is different than what is in Spanish. + +- **Spanish (Argentina) es\_AR** is one of the sub-locales for Spanish (Latin America). Votes on inheritance will ensure that it will only contain content that is different than what is in Spanish (Latin America) + + +The regional variants menu for a data point is shown on the right navigation information pane. It will look 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 darker gray as shown in the screenshot on the right. + +![alt-text](../../images/gettingStartedGuideICUSyntax.png) + +![alt-text](../../images/gettingStartedGuideVarientDropdown.png) + +In the example in the screenshot above, Switzerland and Liechtenstein have different regional data than German (=Germany). 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 above as shown in the screenshot above. + +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. + +### Regional Inheritance + +If you are voting in a sub-locale such as en\_AU, es\_MX, fr\_CA etc., you can vote to follow whatever the translation is for the locale you inherit from. You do this by voting for the translation highlighted in blue box. When you do this, you are essentially saying "**always use the inherited value, even if it changes in the source parent value**". In the screenshot below, this is the case for the vote for "inglês". If the parent value eventually changes, the value in your locale will also change. Subsequent voting in your locale could still result in having a different value than the parent locale. + +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, your Abstained vote means that it's not opposed by you; thus, your intention is not known to others. By voting for the blue inheritance value you make your opinion known to other vetters. + +- Inheritance is important, to prevent data duplication. +- Inheritance is not only limited to “sub locales”. Parent locales (or default language locales) also have inheritance from either other fields or the root. +- By default, all data are inherited if there are no contributions. The data are indicated as Missing or Abstain. Sub-locales have inherited values that are generally from the parent locale (e.g. de\_CH will inherit values from de\_DE). +- The inherited values appear in the **Others** column highlighted in blue box (e.g. “embu” and "inglês"). By clicking the radio button in front of those values, you are voting for inheritance. +- If the inherited value is not correct for your locale or it’s likely for your locale to change the data in the future, click the + button, and enter a new suggestion. + +The vote status column will show an orange-up arrow () if the winning item is inherited and it does not have any votes. + +![alt-text](../../images/gettingStartedGuideVoteCol.jpeg) + +### _Progress Widget_ + +_There is a new style for the progress widget that shows your voting progress on the page in the upper right corner of the Survey Tool next to the Info Panel toggle. You will see details of your progress when you hover over the widget, including what progress is being measured, and the total number of items remaining for you to vote on in that category. Your progress is measured based on the coverage level you have set, so make sure that it is set correctly._ + +_**Note:**_ _The total progress widget is currently only visible when the dashboard is open._ + +### _Page progress_ +_Progress bar shows progress of items on page for your coverage level._ +![alt-text](../../images/gettingStartedGuidePageProgress.png) + + +### _Overall progress_ + +_Progress bar shows progress of items overall for your coverage level._ + +![alt-text](../../images/gettingStartedGuideOverallProgress.png) + +## Dashboard + +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.) + +![alt-text](../../images/gettingStartedGuideDashboard.png) + +The goal is that you should work the Dashboard down to show zero items, then review the [**Reports**](https://cldr.unicode.org/index/survey-tool/guide#TOC-Reports), below. + +_The first priority is to fix all the_ _**Missing**_ _items by supplying the correct translations._ + +### Dashboard Reports + +Go through each of the sections to address the problems. These sections are explained below. + +At the top of the Dashboard is a header with a button for each section the title (such as **Missing**) and the number of items. Below that header are a series of rows. + +### Dashboard Columns + +There are six columns in the Dashboard view. + +- **Dashboard category**: The first letter of the section name enclosed in a circle. +- **Data Type**: The section that the item belongs to. +- **Code**: this links to the field in survey tool. Click on it to go to the item in the Survey Tool. +- **English**: The English value is highlighted in blue. +- **Winning** _**XX**_: The currently winning value is highlighted in green. +- **Hide checkbox**: For items that can be hidden a checkbox to hide that option appears on the far right. + +![alt-text](../../images/gettingStartedGuideDashboardCols.png) + +### How to handle different categories + +Following are guidelines on best practices for handling items under each category in Dashboard. + +- **Missing** + - These are items where there is no localization provided by any contributor. Click on the line to be taken to the item in the Survey Tool where items are highlighted and you can add a translation. When you fix a **Missing** item it will turn to **Changed**. + +![alt-text](../../images/gettingStartedGuideMissing.png) + +- **Losing** + - These are items that you already voted on. This indicates that your vote is not for the currently winning value. If you can live with the winning item—if it is reasonable, even if you don't think it is optimal—change your vote to be for the winning item. If not, click the **Forum** button in the **Info Panel** and give reasons for people to change their vote to what you have suggested. If not all users have voted yet, these values may still be approved before the end of the cycle. **Engage with others on the Forum discussions**. Make sure to post the reasons why others should change their votes and **respond to others’ posts**. +- **Disputed** + - This is very similar to **Losing**, except in this case your vote is winning and someone else's is losing. Review all of the items to see if someone else’s item is better and read the forum post, and whether you want to change your vote. Discuss in the forum, then use the Hide button to hide disputes you’ve addressed in the forum. +- **Changed** + - The Changed count is provided in the Dashboard only as a reference. The **Changed** items are either: + - Missing items now have a value. + - The Winning value of the translation has been changed. +- **English Changed** + - These are items where the English source has changed after the last change in your language. Items that are listed in this section indicates that you need to re-check them and assess the impact to your language and update as appropriate. (Some English changes will have no impact to translations.) +- **Warnings** + - These are issues which appear after automatic checks. (For examples, a message could be "_The value is the same as English"_, which 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. + +![alt-text](../../images/gettingStartedGuideWarning.png) + +### Dashboard Summary + +There are two ways to clear items from the **Dashboard** list: + +1. Fix them (such as adding a translation for a missing item) +2. Hide them (such as when the English has changed but the translation doesn’t need to change). + - _**Only**_ _hide items if it really is a false positive,_ _**not**_ _because you gave up on fixing it…_ + - _If you hide an item by mistake:_ + - _Unhide all the lines with the top eye button._ + - _Click on the orange eye button in the line (a “Show" tooltip will appear)._ + - _Hide all the lines again by clicking the top eye button._ + + +## Reports + +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. + +Reports are under the left navigation. + +Reports are a good way to review the data in your language in a wholistic view for the Date and time, Zones, and Numbers. + +![alt-text](../../images/gettingStartedGuideKorean.png) + +_Example:_ + +![alt-text](../../images/gettingStartedGuidePatterns.jpeg) + +## Special cases + +**You may not make changes to this locale** + +You may see a message like the following when trying to modify a regional locale, like pt-BR. + +![alt-text](../../images/gettingStartedGuidePortuguese.png) + +→ + +![alt-text](../../images/gettingStartedGuideBrazil.png) + +The reason that Brazil is grayed out is that it is the default content locale for Portuguese. So to modify pt-BR, you need to simply click on Portuguese. If you do click on Brazil, you will get to a page with the following at the top. Clicking on [default content locale](https://cldr.unicode.org/translation/translation-guide-general/default-content) will explain in more detail. + +![alt-text](../../images/gettingStartedGuideGeneralInfo.png) + +### 20 vote items May not be modified + +Some items have change protection in place that will stop vetters from changing it, but you can still advocate a change. This is indicated by the message "May not be modified-see details" as shown in the screenshot below, or that the threshold for changing the value is 20 votes, instead of the usual 8 or 4. This indicates that the item is particularly sensitive to data instability and has a broad impact. Changes to these items require Technical Committee review. To suggest a change, you have to "flag" the value. + +![alt-text](../../images/gettingStartedGuideCharsInUse.jpeg) + +To change it, you have to flag the item for committee review: + +1. Click on the “**Flag for Review button**”. +2. On the new page, you'll see a message box. +3. Enter the change that you want to make, and add a justification for changing it. +4. Then click **“Post**”. +5. Towards the end of data collection cycle, the Technical Committee will review the change request and either accept it, or reject it with comments. + +Note: The **Flag for Review** button will be available only when the item has a 20 vote value AND there is a suggestion in the **Others** column. + +## Forum + +Forum is the place to discuss and collaborate with other vetters on questions and issues in your language. The forum is at Language level and not at sub-locale level; if you are talking about a translation in a sub-locale, be sure that you are clear about that. + +It's a best practice to **create a Forum post whenever you propose a change to a previously approved value**, and provide an explanation and links to references. + +### Forum Etiquette + +While creating New Posts on Forum or participating in discussions please follow these general etiquette guidelines for best productive outcomes: + +- Be professional. Provide accurate, reasoned answers so that other participants can easily understand what you are talking about. +- Be courteous. Refrain from inappropriate language and derogatory or personal attacks. +- Don’t “SHOUT”; that is don’t use all capitals. +- In case of disagreement, focus on the data and provide evidence to support your position. Avoid challenges that may be interpreted as a personal attack. +- Be prepared to have your own opinions challenged or questioned, but don’t take answers personally. +- It’s possible that participants have different expectations on the intent of the data. Clarify what you think is the intent may help especially if disputes continue. +- Remember that open discussion is an important part of the process; abiding by these guidelines will encourage active participation by all vetters and a better end result. + +### Forum Workflow + +Forum posts work with the following workflow: + +1. Create a new **Request** +2. Responses by other vetters in your language with Agree, Decline, or Comment. +3. Once resolved, the creators of the the initial Request or Discuss closes the post. + + +### How to create a new forum post + +A forum post can be specific to a particular data point or a general issue. In either case, create a new forum post to an item. + +- A post that is specific to a particular data point. +- A general issue that impacts multiple data points. In a general case that impacts multiple data points, you do not need to post new forum posts for every item impacted. The general issue should be flagged to other vetters and once a consensus is reached, it is expected that vetters update their votes on all impacted items. New forum posts can be used to flag to other vetters if others fail to update their votes on all impacted items. ONLY request if others have missed or have not updated consistently. + + +**Create forum posts from the** [**Information pane**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel)**l in the voting window.** + +1. Vote on an item (or add new +) for the item you want to suggest changing. + +![alt-text](../../images/gettingStartedGuideVote.png) + +2. In the Information panel on the right, there are two buttons to indicate the type of forum posts: + 1. **Request** You have voted on a non-winning item, and you want to Request others to change their votes. + 2. **Discuss -** Currently only TC members can make discuss posts. + +3. Click **Request** button and fill out the details of your request. (Note: The **Request** button is disabled unless you have voted) + +![alt-text](../../images/gettingStartedGuideRequest.png) + +**Request** +1. A precomposed text is included to help start your post. **Important!: Request works WITH the item you voted for currently.** +2. _Please consider voting for “{your voted-value}”. My reasons are:_ Complete the text by filling out your reasons and links to references. +3. Then **Submit.** + +![alt-text](../../images/gettingStartedGuideReasons.png) + +### Responding to Request posts + +There are two ways to respond to forum posts: +- Info Panel (This is the recommended option.) +- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) + +**Respond from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** + +In the **Info Panel**, select the **Comment** button +- Each posted response is labeled in Red and its response type: Agree, Decline or Comment. + +![alt-text](../../images/gettingStartedGuideAgree.png) + +**Choosing your Response:** Vote, or Comment + +1. When you make a vote on an item that already has a Request post by another vetter, then an Agree or Decline post will be made for you automatically. If you agree with the reasons for change, you don't need to add more explanations for agreeing. +2. An **Automated** _**Agreement** will be posted if you vote for the requested value. Your agreement will be automatically posed with a precomposed reply_: I voted for “{requested-value}” + +![alt-text](../../images/gettingStartedGuideAutoAgree.png) + +3. **Comment:** Use this option if you do not Agree or Decline, and you have other input to bring to the discussion or if you want to ask for more information. + +### Responding to Discuss posts + +There are two ways to respond to new forum post: +- Info Panel (This is the recommended option.) +- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) + + +**Respond to forum posts from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** +1. In the Info Panel click the **Comment** button and add your input to the open discussion. +2. The label **Discuss** in Red indicates that this is a Discuss post (to distinguish from Request posts) + +![alt-text](../../images/gettingStartedGuideComment.png) + +### Working in the Forum view + +In the Survey Tool [Forum](https://st.unicode.org/cldr-apps/v#forum/fr//) view, there are multiple filtering options available for you to work more effectively. +1. The Forum view can be accessed from the left navigation **Forum.** + +![alt-text](../../images/gettingStartedGuideForum.jpeg) + +2. By default, the filter is for **Needing action**. + +![alt-text](../../images/gettingStartedGuideNeedingAction.png) + +3. Filter options: + - **Needing action**: Forum posts included in this filter are Requests and Discussion posts by someone in your language. You have not yet taken action on either agreed or declined or posted a discussion asking for additional information. For Discussion posts, these are where you are not the last poster. + - **Open requests by you**: Forum posts included in this filter are Requests that you have posted that you have not closed yet. + - **All Open topics**: All posts that are open. This includes both Request and Discussions that have not closed yet. + - **All topics:** All topics, open or closed, including forum posts from previous releases. + - Note that Forum posts that were active in previous releases will be marked as Closed at the start of a new Survey tool cycle. + +**Respond to forum posts in the Forum view** + +In the Forum view, you can respond to Request and Discuss posts. + +For **Request posts**, you can select your decision using the 3 available buttons: **Agree, Decline, Comment.** + +See [Responding to Request posts in Information Pane](https://cldr.unicode.org/translation/getting-started/guide#TOC-Responding-to-Request-posts). + +![alt-text](../../images/gettingStartedGuideForumPosts.png) + +## Reporting Survey Tool issues + +If you run into a problem with the Survey Tool functionalities, please see [FAQ & Known Bugs](https://cldr.unicode.org/index/survey-tool/faq-and-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](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). + +![alt-text](../../images/gettingStartedGuideCoverage.png) + +**Email notification** + +1. Another way to check for posts that may need your attention is to review email notifications to the e-mail account for your locale. You can delete these notifications if they are for changes initiated by you. You can open the post directly from a link in the email. +2. When you make a forum entry, it will be emailed to all other linguists working on locales with the same language, parent or sub-locale (i.e. **forum is at Language level and not at sub-locale level**). If you are talking about a translation in a sub-locale, be sure that you are clear about that. + + +### Forum posts for CLDR ticket feedback + +CLDR users can send in data feedback using [JIRA](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md). Tickets filed in JIRA will be processed as described below. Please expect to see posts by CLDR Technical Committee members (TCs) in Forums, and participate by providing your response to any tickets needing your input. + +The goal is to bring it to the attention to all linguists contributing in a particular language, and gather their input, so an informed decision can be made and/or suggested. + +1. CLDR TC members accept JIRA tickets. +2. For each ticket assigned to them, the TC member will post a forum topic in each language mentioned in the ticket, asking for vetters to look at the issue and either make the requested change, or explain in a forum post why changes should not be made. +3. A reason for not changing could be for example that it is a reasonable change, but doesn't exceed the 'stability' bar in the translation guidelines. +4. TC members will monitor the forum discussion/change during the Submission phase, and will close the JIRA ticket after the forum discussion is concluded. + + +## Advanced Features + +1. Users familiar with CLDR XML format can upload votes (and submissions) for multiple items at once. See [**Bulk Data Upload**](https://cldr.unicode.org/index/survey-tool/bulk-data-upload)**.** +2. Organization managers can manage users for their organization (add, remove, send passwords, set locales, etc.) For more information, see [**Managing Users**](https://cldr.unicode.org/index/survey-tool/managing-users)**.** + 1. Some users may want to reset their Coverage Level, with the menu that looks like the image to the right. + 2. The Coverage Level determines the items that you will see for translation: the minimal level has the highest priority items. You normally start with the level marked "Default" (which will vary by your organization and locale). Each successively higher level adds more items, at successively lower priorities. You will not normally go beyond "Modern", unless you have special instructions for your organization. + 3. _Note that some companies won't use the data until it is complete at a certain coverage level, typically_ _**Modern**._ + +![Unicode copyright](https://www.unicode.org/img/hb_notice.gif) \ No newline at end of file diff --git a/docs/site/translation/getting-started/survey-tool-phases.md b/docs/site/translation/getting-started/survey-tool-phases.md new file mode 100644 index 00000000000..9d3226b326a --- /dev/null +++ b/docs/site/translation/getting-started/survey-tool-phases.md @@ -0,0 +1,75 @@ +--- +title: Survey Tool stages +--- + +# Survey Tool stages + +## Stages + +Data collection in the Survey tool has 4 stages: + +1. Shakedown +2. General submission +3. Vetting +4. Resolution + +## Full vs. Limited Submission  + +There are two types of releases: full, and limited-submission. + +- Full-submission: + - Typically with the even versions (e.g. Version 36). + - All languages and data areas are open for contributions.  +- Limited-submission + - Typically with odd versions (e.g. version 37). + - Selected fields are open for all locales; the voting options will be grayed out for those data points that are not in scope. + - Proceed with Submission (General), but start with the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) and focus on Errors\*, Missing†, Provisional + - Selected locales are open for votes on all fields. + - Proceed with Submission (General).  + +### Survey Tool phase: Shakedown + +_Make sure your coverage level is set correctly at the top of the page._ + +Shakedown is on an invitation basis. If you have not received an invitation to participate in shakedown, your participation is discouraged. + +You should know in this stage: + +- The survey tool is **live and all data that you enter will be saved and used.** +- You can start work +- Expect a churn: there may be additional Tooling fixes and Data additions during this period.  +- Tool may be taken down for updates more frequently during general submission +- You are expected to look for issues with the Survey tool and any other problems you encounter as a vetter. Please [file a ticket](https://cldr.unicode.org/index/bug-reports). + +### Survey Tool phase: General Submission + +_Make sure your coverage level is set correctly at the top of the page._ + +For new locales or ones where the goal is to increase the level, it is best to proceed page-by-page starting with the **Core Data** section. At the top of each page you can see the number of items open on the page. Then scan down the page to see all the places where you need to vote (including adding items). Some  + +Then please focus on the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) view, + +1. Get all **Missing**† items entered +2. Vote for all **Provisional** items (where you haven't already voted) +3. Address any remaining **Errors\*** +4. Review the **English Changed** (where the English value changed, but your locale's value didn't. These may need adjustment.) + - \* Note that if the committee finds systematic errors in data, new tests can be added during the submission period, resulting in new **Errors**. + - † Among the _**Missing**_ are are new items for translation. (On the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u), **New** means winning values that have changed since the last release.) + +If you are working in a sub-locales (such as fr\_CA), coordinate with others on the Forum to work on each section after it is are done in the main locale (fr). That way you avoid additional work and gratuitous differences. See voting for inheritance vs. hard votes in [Survey Tool guide](https://cldr.unicode.org/translation/getting-started/guide).  + +### Survey Tool phase: Vetting + +All contributors are encourage to move their focus to the [Dashboard](https://cldr.unicode.org/translation/getting-started/guide#h.bmzr9ejnlv1u) view. Also see [Dashboard tip](https://cldr.unicode.org/translation/getting-started/vetting-view)s to use during Vetting stage. +1. Any [Flagged entries](https://st.unicode.org/cldr-apps/v#flagged///) in your locale may have questions in the Forum from TC members; please add additional information to help the TC resolve them. + 1. To see the Flagged items, click on the **Menu** icon in the upper left corner, under the **Forum** header see **Flagged items**: +2. Open the Dashboard, and resolve all of the Errors, Provisional Items, Disputed items, and finish Reports + 1. Consider other's opinions, by reviewing the **Disputed** and the **Losing**. See guidelines for handling [Disputed](http://cldr.unicode.org/translation/getting-started/guide#TOC-Disputed) and [Losing](http://cldr.unicode.org/translation/getting-started/guide#TOC-Losing). +3. Review all open Requests and Discussions in the [Forums](https://cldr.unicode.org/translation/getting-started/guide#h.fx4wl2fl31az), and respond. + + +### Resolution (Closed to vetters) + +The vetting is done, and further work is being done by the CLDR committee to resolve problems. You should periodically take a couple of minutes to check your [Forums](https://cldr.unicode.org/translation/getting-started/guide#h.fx4wl2fl31az) to see if there are any questions about language-specific items that came up. + +![Unicode copyright](https://www.unicode.org/img/hb_notice.gif) \ No newline at end of file diff --git a/docs/site/translation/getting-started/vetting-view.md b/docs/site/translation/getting-started/vetting-view.md new file mode 100644 index 00000000000..2c353a936d3 --- /dev/null +++ b/docs/site/translation/getting-started/vetting-view.md @@ -0,0 +1,182 @@ +--- +title: Survey Tool: Dashboard tips +--- + +# Survey Tool: Dashboard tips + +## Dashboard + +Once you have finished entering data, you will need to review the items for accuracy. To assist with this, use the Survey Tool's Dashboard, accessible through the link in the sidebar. + +The Dashboard will show you a list of data items with warnings of different kinds. Some will require action and some may be false positives. The idea here is that you should work the Dashboard down to show zero items. + +### Dashboard Sections + +The Dashboard is divided in these sections. If a section is not visible for you, that means you have no items in that section: + +- **Error**: The currently winning value has caused an error in validation that will have to be resolved before release. (High priority.) + - Fix the error. In some cases there is a conflict among items, and you'll need to fix the conflicting item, not the one showing the error. +- **Losing**: Your vote is losing against the other vetters’ vote. + - Can you live with the winning value? If so, change your vote. + - Otherwise, use the forum to alert the other vetters and reach consensus. +- **Disputed**: Your vote is winning, but other vetters voted differently. + - Use the forum to help reach consensus if possible. +- **Warning**: The winning value has something unexpected in it, perhaps a character that’s not normally used in your language. + - Please review. If it’s an unwarranted warning, you can hide it. +- **English Changed**: The English value changed from last version, but the winning translation in your language remained the same. + - Does the translation need to be updated? If not, you can hide the warning. +- **New**: The winning localized value is different from last year. (Informational.) +- **Missing**: We have no localized value for these values. + - Please provide them. (High priority.) +- **Provisional**: We have a value, but not enough votes to support it and include them in the release. + - Add your vote if you haven’t already and alert other vetters through the forum to support if you have already voted. + + +### Fixing Entries + +Each entry has the following: + +- A blue field which links to the relevant value in the Survey Tool. The link will open in a new window. +- English value +- previous CLDR version’s value +- currently winning value + + +### Clearing Items + +There are two ways to clear items from the list: + +1. The preferred way is to fix them (such as adding a translation for a missing item). Click on the item line to bring up that item in the Survey Tool where you can change or edit your vote, or post a forum vote to try to convince the other vetters to change their vote for losing or disputed items. +2. The other is to hide them (such as when the English has changed but the translation doesn’t need to change). Only hide an item if it really is a false positive, not because you gave up on fixing it. To hide an item from view, click on the checkbox on the far right of the item. Note that this will not make it disappear, just hide it from view. Click on the check box next to 'Hide' on the Dashboard menu to hide or unhide hidden lines. The count on each section will show how many items are showing versus the total. + +The following are legacy tools to review votes, but the Priority Items tool is deprecated in favor of the Dashboard. This information is presented here for reference. + +**Review:** Priority Items |Date/Time | Zones | Numbers + +You can also see a video walkthrough of the review sections on [Walkthrough](https://cldr.unicode.org/index/survey-tool/walkthrough). + +The rest of this page discusses how to do the Priority Items. Once you have done the Priority Items, [Review reports](https://cldr.unicode.org/translation/getting-started/review-formats). + +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](https://cldr.unicode.org/translation/getting-started/guide#TOC-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 https://st.unicode.org/cldr-apps/v#/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: + +| 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](mailto: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. + 1. 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. + +After the data submission phase, any differences in the submitted data will be resolved according to the [data resolution process](https://cldr.unicode.org/index/process#TOC-Data--Resolution). + +### 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](https://cldr.unicode.org/translation/getting-started/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](https://cldr.unicode.org/translation/getting-started/guide#TOC-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*](https://unicode.org/cldr/apps/survey?_=fr&xpath=%2F%2Fldml%2FlocaleDisplayNames%2Fscripts%2Fscript%5B%40type%3D%22Hans%22%5D) | +| 359 | Hant | Traditional
Traditional Han | idéogrammes han traditionnels | = | [Unsync’d*](https://unicode.org/cldr/apps/survey?_=fr&xpath=%2F%2Fldml%2FlocaleDisplayNames%2Fscripts%2Fscript%5B%40type%3D%22Hant%22%5D) | +| 360 | Zzzz | Unknown Script
Unknown or Invalid Script | écriture inconnue ou non valide | = | [Unsync’d*](https://unicode.org/cldr/apps/survey?_=fr&xpath=%2F%2Fldml%2FlocaleDisplayNames%2Fscripts%2Fscript%5B%40type%3D%22Zzzz%22%5D) | + +**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. + +![Unicode copyright](https://www.unicode.org/img/hb_notice.gif) \ No newline at end of file