VisualEditor/TranslationCentral

Welcome to VisualEditor Translation Central! VisualEditor is software in development to allow people to edit pages in MediaWiki without needing to learn wikitext syntax (like typing [[ to start a link. We want this software to be useful to people (new and experienced) in every language and need your help to reach that goal. This page talks about how you can help with translation so that people can use VisualEditor and learn about it in their own languages.

In the sections below, we have "To do" lists talking about different translation tasks that need to be done and a section with tips and resources for translators. There is a list of people who have signed up to participate in this effort—you are free to add your name to that list, if you'd like to help out. Finally, there are charts showing the state of translation of various documents in different languages.

Translate the VE interface
To translate the VE user interface, you need to create an account at translatewiki.net. (Translatewiki.net is not a Wikimedia Foundation project, so your universal login will not work there.) Fill in the “Become a Translator” form and press “Create account”. At this point, you will have to translate a few words and phrases. (They will keep coming, but you don't have to keep translating; you can stop after doing just a few.) After that, you will get an email letting you know that you have been approved to translate. Then you can start to translate. There are four groups of messages to translate : Select your language in the pulldown, and you will see what needs translation.
 * the VisualEditor Core
 * the VisualEditor MediaWiki extension
 * the VisualEditor WMF extension
 * the OOjs UI for VisualEditor

View translation progress to date at translatewiki.net: Statistics.

Translate the User Guide and other documents
The User Guide is another important document. To translate this, simply go to Help:VisualEditor/User_guide and select "translate this page". Your language should be available from the drop-down menu on the right. Once you've done this, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify translations (those that may be outdated are marked to the left with a clock).

Beyond the User Guide, there are a few other very useful documents that should be translated. See Localization for the full list and detailed instructions on how to help with this effort (and don't forget to record your progress on the progress page!)

Take screenshots
Some of the help documents, especially the User Guide, have screenshots of VE buttons and dialogs. A fully translated version ideally should have screenshots of VE in its home language. Here are some tips for making screenshots:
 * Help:Screenshots

Direct feedback
The VE development team wants to hear from Wikipedia editors about their experiences with VE, improvements they want, and problems they are having. It's important that the editors of our smaller wikis have their opinions heard, too. Some of the larger wikis have special Feedback pages, like the Italian one, for example, but on smaller wikis comments left there may be overlooked. Please redirect requests about VE to this site's VisualEditor/Feedback page!

Update help pages
Each wiki has its own collection of help pages. It is important that these help pages are updated with information about VE and links to translated user guides as VisualEditor becomes a default option on each wiki. If you've done some of this work for your wiki, please remember to update the Progress page.

Add TemplateData
Most of of our articles use templates in some form. VisualEditor has a template editor, but, for it to be user friendly, it needs to know what parameters the template supports. VE uses TemplateData to discover the supported parameters. However, TemplateData must be added to the template's documentation for this to happen. Every wiki has its own templates; it's very important that each gets TemplateData added to it. For an explanation of TemplateData, see our TemplateData main page, and our tutorial for detailed instructions on how to add it.

Tips and resources for translators

 * Both translatewiki.net and MediaWiki.org can display in your language, if their user interfaces have already been translated. Go to your "preferences" and choose your language from the pulldown menu.
 * You can use any existing translations to help you translate into your own language. To do this, go to “preferences” in MediaWiki.org or on translatewiki.net and select the "edit" tab. Choose an "assistant language" from the drop-down menu or add them manually by typing (separated by a comma) as many languages as you like. When you translate messages, you will see whatever translations exist in those languages as well. You can one-click the message to add it to your translation window, where you can alter it if needed.
 * Detailed Localization Instructions (with list of documents most needed)
 * Iberocoop has generously offered to help with Spanish translations
 * Translators-1, mailing list for translators
 * Category:Translator's Templates, on Meta

Participants

 * , English
 * , Czech
 * User:Kwj2772, Korean
 * , Korean
 *  Ę-oиė   >>>  ™, Indonesian & Minangkabau
 * , Persian (Farsi)
 * , Persian (Farsi)
 * , Hungarian
 * , Turkish
 * , Español
 * , Azerbaijani
 * , Thai
 * , Azerbaijani
 * , Serbian
 * , Greek
 * , Serbian (Српски)
 * , Serbian (Српски)
 * , Georgian
 * , Luxembourgish
 * , Asturian (this user will be merged onto in the future)
 * , Hungarian
 * , Lithuanian
 * , Lithuanian
 * , Faroese
 * , Khmer
 * , Macedonian
 * , Modern Greek
 * , Latvian
 * , Indonesian
 * , Turkish

Progress
Below are some useful tracking tables, showing the current progress on translation tasks: