Help:Translation

is capable of handling multilingual content and providing the reader a user interface in their preferred language. Multilingual editors are encouraged to translate and maintain articles in as many different languages as possible to reach the whole Dota 2 global community. Maintaining up to date translated articles is very important and it should be noted that it is preferential to have an up to date English article, rather than an out of date translated one.

How to translate a page
Follow these guidelines to start translating an article.


 * 1) Check that your language is supported.
 * 2) Go to the English version of the article's page and click "Edit this page". Select everything in the box and copy it.
 * 3) Go to the Language version of the article and click "Create". Paste everything from your clipboard.
 * The German version of the article "Hats" would be .   is no longer valid. Each supported language now has its separate wiki.
 * 1) Add the template Translate to the top of the page. This keeps all uncompleted articles in your language together.
 * 2) Change all the categories at the bottom of the page. Most pages will have localized category names.
 * 3) You can now translate the rest of the article. Note that some text is stored in other pages (called "templates"). To translate these you will have to edit them individually.

Coordination
Please watch the Project:Translation page. Announcements and discussion will take place there. (click the 'watch' tab at the top). This will ensure you stay on top of any changes or announcements.

Rules for the EN wiki:
 * Talk pages
 * It is vital that all discussion based on specific users and articles is in English. This is especially important when discussing the quality or accuracy of any article or translator.
 * Edit summaries
 * All edit summaries should be written in English where practical.

Rules for other languages:
 * Keep the template names in english. Do not move the code away from the page. You can create localized redirects towards the template instead.

Articles

 * Displaying a different title
 * Displaying a title in a different language is possible with the use of the magic word &#123;&#123;DISPLAYTITLE:&#125;&#125;.
 * For example, using &#123;&#123;DISPLAYTITLE:Example&#125;&#125; will display the article name as Example.


 * Infoboxes
 * To display a new name in an infobox, add a new line like this:
 * The infobox template for weapons and hats needs a few lines to stay in English for it to work properly. If a line is listed below, please do not translate it:
 * See Template:Item infobox for further help.
 * The infobox template for weapons and hats needs a few lines to stay in English for it to work properly. If a line is listed below, please do not translate it:
 * See Template:Item infobox for further help.
 * See Template:Item infobox for further help.
 * See Template:Item infobox for further help.


 * Links
 * You can link to translated articles and display different text for the links like this:
 * Механизмы will create Механизмы.
 * You may need to generate  on "Chinese (Simplified)" page for synchronized further page's title changing.
 * If using external links that are in English, you should also use the template lang icon directly after the link to indicate the language of the external link.
 * Google on Chell/fr should look like, which will generate:
 * Google
 * Main and See also – When using these templates you can display a different title using the parameter l1 (lowercase L1):
 * generates
 * Main article: Chapeaux
 * generates
 * Main articles: Chapeaux and Objets divers
 * Note: To change the "Main article:" text, see the individual template pages for main and see also as they use translation switching.


 * Categories
 * Language pages should be kept in separate categories.
 * For example on Repulsion Gel/fr, if you find at the bottom of the page, change it to.


 * Redirects
 * You can create as many language redirects as are needed, as long as they are tagged properly with R lang. See example:
 * Шапочка поджигателя redirecting to Pyro's Beanie/ru will have the following text on the page 'Шапочка поджигателя':
 * : always remember to add (this helps to find these redirects later, as there can be hundreds of them)
 * : always remember to add (this helps to find these redirects later, as there can be hundreds of them)


 * Disambiguation pages
 * Disambiguation pages (i.e. pages that list articles with similar names for convenience) that are specific to one language should not be created. Root pages should always be in English, and much of the wiki page structure relies on this. Lang-specific disambig pages can become too difficult to keep track of.

Templates
Each subwiki has it's own localized version of the EN template. Changes and improvements should be ported upstream to the EN version, where the other downstream languages will notice the changes and can adapt them as well.

Meda files
There are two types of databases: Shared (en) and local (de/pt/ru/zh).

Shared en images can be called as if they were available at the respective wiki. If you use parser functions you can use these two functions to distinguish where the image comes from:


 * returns false on the RU wiki because the file page is not on the RU wiki but the EN wiki.
 * returns true on the RU wiki because the file media is available (shared) to the RU wiki from the EN wiki.

Images
Images have to be uploaded to the English wiki. If there is text within the image that needs to be translated, the new image can be uploaded to the local databases.

Sound files
Should /lang files be available in the shared or local database?

Supported languages
Dota 2 Wiki supports language translation of articles into a number of languages, the majority of which have localization files for Dota 2.

There are no plans to add support for any further languages at this time. Support for the translation of articles into a specific language will now only be considered if there are localization files present in the game. The reasoning for this is that the workload for translators who do not have support from the Steam Translation Server (in the form of word lists, nouns, etc, and proper discussion channels) is significantly higher. The amount of active translators is also less, meaning pages can quickly become out of date.

If you want to maintain a new language in the long term, start a new discussion at Project:Translation and give your reasoning. It's very advantageous to have a good record of edits to show your credibility.