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.

번역을 하는 방법

번역을 시작하시려면 아래 사항을 따라주십시오.

1. (지원되는 언어 목록은 아래를 참조.) 이 위키는 공식 게임에 제공되는 모든 언어를 지원합니다.

1. 번역할 문서의 영어 버전으로 이동하여 "편집"을 클릭합니다. .

당신이 번역하고자하는 언어의 ISO 코드로 대체되는 문서의 끝에 "/ LANGUAGE"를 추가하여 번역해주십시오.

1. 예시: http://wiki.teamfortress.com/wiki/Scout/fr

2. 새로운 문장 하나에 영어 페이지 주소를 붙여 넣습니다.

   프랑스어 버전의 모자에 대한 문서를 번역할 경우, 이렇게 해주십시오. Hats/fr, 하지만 이런식으로 해주면 안됩니다. Chapeaux, Hats/Chapeaux 혹은 Chapeaux/fr 등..

3. 템플릿을 추가하고, Template:트랜스 페이지의 상단에, 완전히 번역되지 않은 문서는 번역해주시길 바랍니다.

   당신은 무언가를 추가할 필요가 없습니다. 단지, 무언가가 요구될 뿐입니다.

   이것은 {{DISPLAYTITLE:abcxyz}} 번역된 문서의 제목을 표시하는데 쓰이게 됩니다.

   예를들어, 저 방법대로하면 제목이 "화염방사기" 로 유지되며 나타내어진다던가...

   디스플레이 제목도 설정할 수 있습니다.

4. 페이지 하단의 카테고리를 변경합니다.

   예를들어, {{코드 | 분류 : 목록}이런식으로 해 주시고, Template:코드. 페이지의 맨 아래에있는 모든 범주에 대해 작업을 수행하여주십시오.

1. 이제 문서의 나머지 부분을 번역 할 수 있습니다. 일부 텍스트 ("템플릿"이라고 함)는 다른 페이지에 저장되어 있습니다. 이것을 번역하려면 개별적으로 편집해야합니다.

1. 올바른 이름 및 설명을 번역하기위해 당신은 [: 카테고리 : 현지화 파일]을 사용하는것이 바람직한 방법일 수도 있습니다.

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 effort here.

Please also join the TF Wiki Translators Steam Group and watch the translators' noticeboard (click the 'watch' tab at the top). This will 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)
• If an international 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 (click the tab at the top of the page), so it is not necessary to sign.

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}} will display the article name as Example.

• Infoboxes
  • To display a new name in an infobox, add a new line like this:

    {{Item infobox

    | name = Name goes here

    | image = ...

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

    | type = ...

    | game = ...

    | slot = ...

    | trade, gift, craft, paint or 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:
    • Armes will create Armes.
  • 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 [http://www.google.com/ Google] {{lang icon|en}}, which will generate:

    Google (English)

  • {{Main}} and {{See also}} – When using these templates you can display a different title using the parameter l1 (lowercase L1):

  {{Main|Hats/fr|l1=Chapeaux}} generates

  Main article: Chapeaux

  {{Main|Hats/fr|l1=Chapeaux|Miscellaneous items/fr|l2=Objets divers}} 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 Wrench/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 Shotgun/ru will have 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. Lang-specific disambig pages can become too difficult to keep track of.

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.

List of supported languages

Team Fortress Wiki supports language translation of articles into 22 languages, the majority of which have localization files for TF2. The languages highlighted in the table below are exceptions to the rule. Czech is being actively translated on STS and may have localization files appear in the game soon, and support for Arabic has been extended due to the amount of existing Arabic content.

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

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

ISO639-1 code	Name in English
–	English
ar	Arabic
cs	Czech
da	Danish
de	German
es	Spanish
fi	Finnish
fr	French
hu	Hungarian
it	Italian
ja	Japanese
ko	Korean
nl	Dutch
no	Norwegian
pl	Polish
pt	Portuguese
pt-br	Portuguese (Brazil)
ro	Romanian
ru	Russian
sv	Swedish
tr	Turkish
zh-hans	Chinese (Simplified)
zh-hant	Chinese (Traditional)