Help:Language translation

Team Fortress Wiki 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 TF2 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 (see List of supported languages below). We support most languages that have official in-game translations.
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. Navigate to the new language by adding "/LANGUAGE" to the end of the article where LANGUAGE is replaced with the ISO639-1 code of the language you wish to translate to, found here

   Example: https://wiki.teamfortress.com/wiki/Scout/fr

4. Paste the code of the English page to the new one.

   The French version of the article "Weapons" would be Weapons/fr, not Armes, Weapons/Armes or Armes/fr

5. Use {{DISPLAYTITLE:abcxyz}} to translate the page's title.

   For example: {{DISPLAYTITLE:Handlung}} would show the title "Handlung" while keeping the real article title as "Storyline/de".

   The display title can also be set by the infobox (see below). Because of this, articles about cosmetic items and weapons should not use this template to allow dynamic name changes from the dictionary.

6. Change the categories at the bottom of the page.

   For example: [[Category:Lists|Weapons]] becomes [[Category:Lists/fr|Weapons]]. Do this for all categories at the bottom of the page.

7. You can now translate the rest of the article. Note that some text is stored in other pages (called "templates"). To translate these you have to edit them individually.

   Whenever possible, make use of localization files in order to use correct names and descriptions.

   In case you need to save an unfinished translation to complete it later on, add {{trans}} to the top of the page. All such incomplete translations are placed in the appropriate category.

   You do not need to add {{trans|French}} (for example), only {{trans}} or {{translate}} is required.

Translation community

Each language has its own main discussion page at Team Fortress Wiki:Translation progress. You can also find statistics about your language's translation efforts there.

Keep in mind that translators are also part of the editors, making the translation community a subset of the entire editor community. In addition to translation, participation in the creation and improvement of the original English pages is also encouraged.

Please make sure to watch the main discussion page (click the 'watch' tab at the top) to ensure you stay on top of any changes or announcements.

Multilingual guidelines

• English is the main reference language, and all root pages should be named and written in English.
• Other languages should be placed in an appropriately named sub-page of the English version.
• Language subpages should use the appropriate ISO 639 code (as listed below)
• With few exceptions, pages in the Help, Team Fortress Wiki, Mediawiki namespaces should not be translated. These pages are primarily aimed to be read by Wiki editors, and all Wiki editors should all be capable of reading English. As such, it is not very useful to translate these pages and can cause out-of-date guidelines when compared to the authoritative (English) version. Exceptions include language-specific translation guidelines and problematic guidelines repeatedly ignored by non-English-reading editors.
  • Disambiguation pages do not need to be translated unless they refer to common words, e.g. Shoes.
• If a translated version of a page exists but an English version does not, then please create a stub article for the English version as this aids navigation.
• The use of {{Languages}} at the bottom of articles is now discouraged, as language links appear in the sidebar.
• While in the process of translating articles, using {{Trans}} is encouraged to display to other editors that the article is a work in progress.
• Pages that are out of date or need updating should be tagged with {{update trans}}. Pages with this tag appear in Category:Translations needing updating, sorted by language.
• Please do not sign articles using the 4 tildes (~~~~). The list of people who contributed to the article is always available in the history tab, and it would otherwise clutter the page.

Automated translation tools

 Note: please report any pages that consist of entirely machine-translated text (or any users that appear to repeatedly use these tools) to the translators' noticeboard.

On-Wiki communication

• 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.

These requirements allow staff and fellow editors to keep up to date with every aspect of translation.

Articles

• Displaying a different title
  • Displaying a title in a different language is possible with the use of the magic word {{DISPLAYTITLE:}}.
  • For example, using {{DISPLAYTITLE:Example}} displays the article name as Example.

• Templates
  • Templates use parameters with values to display text. The style is | parameter = text. Translating the text is almost always required, but the parameter should never be translated.
  • {{Item infobox}} needs a few lines to stay in English for it to work properly. If a parameter is listed below, please do not translate the text associated with it:

type, game, slot, trade, gift, craft, paint, rename, quality

• See Template:Item infobox for further help.

• Links
  • You can link to translated articles and display different text for the links like this:
    • [[Weapons/fr|Armes]] creates Armes.
    • [[Armes]] should be avoided, only linking the English page and adding the language code (as shown above) should be used.
  • 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 Soldier/fr should look like [https://www.google.com/ Google] {{lang icon|en}}, which generates:

    Google (English)

  • You can link to translated Wikipedia articles using [[w:lang:Wikipedia Article Page Title|Displayed text]], replacing lang with the ISO639-1 code of the language you are translating to.
    • [[w:nl:Thompsonpistoolmitrailleur|Thompsonpistoolmitrailleur]] produces Thompsonpistoolmitrailleur (as used on Tomislav/nl).
      • If no translated page exists, either omit entirely or link to the English article and add {{lang icon}}.
  • {{Main}} and {{See also}} – When using these templates you can display a different title using the parameter l1 (lowercase L1):

  {{Main|Weapons/fr|l1=Armes}} generates

  Main article: Armes

  {{Main|Weapons/fr|l1=Armes|Cosmetic items/fr|l2=Objets cosmétiques}} generates

  Main articles: Armes and Objets cosmétiques

  Note: To change the "Main article:" text, see the individual template pages for {{Main}} and {{See also}} as they use translation switching.

• Translation templates
  • You are encouraged to use "name" and "link" templates ({{item name}}, {{item link}}, {{update name}}, {{update link}}, {{achievement name}}, and {{map link}}) to translate names in articles, as they use the official translated names, ensure any pages where they are used will be automatically updated in case of a change in their subject's name, provide a link to the same language as the article they are used in, among other reasons.

• Categories
  • Language pages should be kept in separate categories.
  • For example on Wrench/fr, if you find [[Category:Melee weapons]] at the bottom of the page, change it to [[Category:Melee weapons/fr]].

• 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 Shotgun/ru has the following text on the page 'Дробовик':

    #REDIRECT [[Shotgun/ru]] {{R lang|ru}}

  •  Note: always remember to add {{R lang|xx}} (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. Language-specific disambiguation pages are too difficult to keep track of.

• Quotations
  • The quotation text has to be translated.
  • If your language is one of the few having translated voice lines (German, Spanish, French and Russian), you can check if the sound is localized by adding your language code to the sound (e.g. Demo trade 04.wav becomes Demo trade 04 de.wav) and using "Show preview".
    • If the sound exists, listen to it and add the translated text.
    • If not, translate the quotation on your own, leave the English voice line and add the en-sound=yes parameter to the template.

Templates

The majority of templates should use translation switching, with the exception of some navigational boxes. Previously it was necessary to create a localized version of a template, e.g. Template:Hat infobox/ru. Now localized text is stored in one template, where text for all languages is stored. Please see Help:Translation switching for further information.

Watchlist

The English pages you translate from will be updated in any time, but the translated pages will not update themselves. As a result, a translated page which lacks updates gradually becomes obsolete over time.

If you are willing to keep an eye on your works and keep them highly consistent with the corresponding English pages, you can add the original pages to your watchlist as well. In this way, you can easily learn which translation pages you created need to be updated.

List of supported languages

Team Fortress Wiki supports language translation of articles into 21 languages, all of which have localization files for Team Fortress 2. Arabic is currently deprecated, existing pages may be updated, but new pages should not be created and template support is not guaranteed.

 Note: there are no plans to add support for any further languages at this time. Support for the translation of articles into a specific language is now only considered if there are localization files present in the game and a huge effort behind the initiative. The reasoning for this is that the workload for translators who do not have support from the Valve Crowdin (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.

Please do not make requests to moderators or on the talk page regarding requests, our stance at this time is not changing.

Wiki language code	English name	Steam language code
–	English	english
ar (Deprecated)	Arabic	arabic
bg (Not supported)	Bulgarian	bulgarian
cs	Czech	czech
da	Danish	danish
de	German	german
es	Spanish (Spain)	spanish
es-419 (Not supported)	Spanish (Latin America)	latam
fi	Finnish	finnish
fr	French	french
hu	Hungarian	hungarian
id (Not supported)	Indonesian	indonesian
it	Italian	italian
ja	Japanese	japanese
ko	Korean	koreana
nl	Dutch	dutch
no	Norwegian	norwegian
pl	Polish	polish
pt	Portuguese	portuguese
pt-br	Portuguese (Brazil)	brazilian
ro	Romanian	romanian
ru	Russian	russian
sv	Swedish	swedish
th (Not supported)	Thai	thai
tr	Turkish	turkish
uk (Not supported)	Ukrainian	ukrainian
vi (Not supported)	Vietnamese	vietnamese
zh-hans	Chinese (Simplified)	schinese
zh-hant	Chinese (Traditional)	tchinese