Translation Guidelines

This page was last modified on: Dec 6, 2017.
The pages listed to the left provide guidelines for translation of CLDR strings. For an overview of the tools, please read the Survey Tool Guide before starting.

Data stability

Please be mindful of data stability by carefully reviewing previously Approved data. Fields that are clearly incorrect should be changed, but there are many cases where two different values are both acceptable for a given field. For stability of the data, when contributing, avoid changing from one acceptable value to a different acceptable value, unless the second is much better, and in customary use. It's a best practice to use the forum to bring up discussions when changing Approved values.

Current Survey Tool Contribution Stage

The survey tool is currently open for contribution. CLDR v33 is a *Limited* contribution cycle.  

In milestone 33, CLDR contribution will be focused on the following scope:
  • All locale data for specific locales: Assamese and Odia
  • Emoji for specific locales: en_GB, de, es, ja, ru, ar, and fi
  • CLDR modern locales with missing data.(locales on http://unicode.org/cldr/charts/32/supplemental/locale_coverage.html marked CLDR Target=Modern)
  • We are also collecting feedback on Emoji translation guide, particularly for issues that you may run into handling emoji keywords. Please file a ticket to ask questions or send feedback on emoji translation guides.

Known Issues

Please review this list before getting started and avoid creating duplicate tickets. This list will be updated as fixes are made available in production.



If you hit a problem that is not on this list, please file a ticket.

Resolved Issues

    Previously listed on the known issues that have been resolved:





    Survey Tool Stages 

    Beta

    (There will not be a Beta period for CLDR v33)

    Data that you enter will not be saved at the end of beta. So during Beta, try out the tool to make sure you can log in, enter data in each section without worrying about its correctness, check that errors/warnings show up (eg make 2 countries have the same name, enter an English word when their script is non Latin, etc).

    Shakedown 

    (The Shakedown period for CLDR v33 will begin on Nov 30, 2017) 

    The survey tool is live and data that you enter will be saved and used. You can start work, but there may be can start work but  additional fixes during this period. So the tool may be taken down for updates more frequently than after we exit Shakedown.

    Submission

    (The Submission period for CLDR v33 is planned to be Dec 4 to January 1, 2018) 

    In the submission phase, please focus on getting all Missing items entered. Missing items in sublocales (such as fr_CA) should be done after the main locale (fr) item has been translated, to avoid gratuitous differences.

    Vetting

    (The Vetting period for CLDR v33 is planned to begin on January 1, 2018) 
    . All contributors are encourage to move their focus to the Dashboard view. Consider other's opinions, by reviewing the Disputed and the loosing. See guidelines for handling Disputed and Losing.


    Subpages (38): View All
    Comments