Difference between revisions of "Help:Language translation"

From Team Fortress Wiki
Jump to: navigation, search
(번역을 하는 방법)
(Undo edit by BluSolly (Talk) (2486285) Vietnamese is not supported by the wiki)
(42 intermediate revisions by 26 users not shown)
Line 3: Line 3:
 
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.
 
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.
  
# (지원되는 언어 목록은 아래를 참조.) 이 위키는 공식 게임에 제공되는 모든 언어를 지원합니다.
+
# Check that your language is supported (see [[#List of supported languages|List of supported languages]] below). We support most languages that have official in-game translations.
 
+
# Go to the English version of the article's page and click "Edit this page". Select everything in the box and copy it.
#: 번역할 문서의 영어 버전으로 이동하여 "편집"을 클릭합니다. .
+
# Navigate to the new language by adding "/LANGUAGE" to the end of the article where LANGUAGE is replaced with the ISO code of the language you wish to translate to, found [[#List of supported languages|Here]]
당신이 번역하고자하는 언어의 ISO 코드로 대체되는 문서의 끝에 "/ LANGUAGE"를 추가하여 번역해주십시오.
+
#: Example: <code>[[Scout/fr|http://wiki.teamfortress.com/wiki/Scout/fr]]</code>
#: 예시: <code>http://wiki.teamfortress.com/wiki/Scout/fr</code>
+
# Paste the code of the English page to the new one.
# 새로운 문장 하나에 영어 페이지 주소를 붙여 넣습니다.
+
#: The French version of the article "[[Hats]]" would be {{xt|Hats/fr}}, not {{!xt|Chapeaux}}, {{!xt|Hats/Chapeaux}} or {{!xt|Chapeaux/fr}}
#: 프랑스어 버전의 모자에 대한 문서를 번역할 경우, 이렇게 해주십시오. {{xt|Hats/fr}}, 하지만 이런식으로 해주면 안됩니다. {{!xt|Chapeaux}}, {{!xt|Hats/Chapeaux}} 혹은 {{!xt|Chapeaux/fr}} 등..
+
# Use <code><nowiki>{{DISPLAYTITLE:abcxyz}}</nowiki></code> to translate the page's title.
# 템플릿을 추가하고, {{ 트랜스 }} 페이지의 상단에, 완전히 번역되지 않은 문서는 번역해주시길 바랍니다.
+
#: For example: <code><nowiki>{{DISPLAYTITLE:Handlung}}</nowiki></code> would ''show'' the title "Handlung" while keeping the ''real'' article title as "Storyline/de".
#: 당신은 무언가를 추가할 필요가 없습니다. 단지, 무언가가 요구될 뿐입니다.
+
#: The display title can also be set by the infobox [[#Articles|(see below)]]. Because of this, articles about cosmetic items and weapons should ''not'' use this template to allow dynamic name changes from the [[Template:Dictionary|dictionary]].
#: 이것은 {{code|1=<nowiki>{{DISPLAYTITLE:abcxyz}}</nowiki>}} 번역된 문서의 제목을 표시하는데 쓰이게 됩니다.
+
# Change the categories at the bottom of the page.
#: 예를들어, 저 방법대로하면 제목이 "화염방사기" 로 유지되며 나타내어진다던가...
+
#: For example: <code><nowiki>[[Category:Lists|Weapons]]</nowiki></code> becomes <code><nowiki>[[Category:Lists</nowiki>'''/fr'''<nowiki>|Weapons]]</nowiki></code>. Do this for all categories at the bottom of the page.
#: 디스플레이 제목도 설정할 수 있습니다.
+
# 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.
# 페이지 하단의 카테고리를 변경합니다.
+
#: Whenever possible, make use of [[:Category:Localization files|localization files]] in order to use correct names and descriptions.
#: 예를들어, {{코드 | [[분류 : 목록]]}이런식으로 해 주시고, {{코드 | [[분류 : 목록 / FR]]}}. 페이지의 맨 아래에있는 모든 범주에 대해 작업을 수행하여주십시오.
+
#: In case you need to save an unfinished translation to complete it later on, add {{tl|trans}} to the top of the page. All such incomplete translations will be [[:Category:Pages_in_translation|in the appropriate category]].
 
+
#:: You do not need to add {{tlx|trans|French}} (for example), only {{tl|trans}} or {{tl|translate}} is required.
#: 이제 문서의 나머지 부분을 번역 할 수 있습니다. 일부 텍스트 ("템플릿"이라고 함)는 다른 페이지에 저장되어 있습니다. 이것을 번역하려면 개별적으로 편집해야합니다.
 
 
 
#: 올바른 이름 및 설명을 번역하기위해 당신은 [: 카테고리 : 현지화 파일]을 사용하는것이 바람직한 방법일 수도 있습니다.
 
  
 
== Translation community ==
 
== Translation community ==
Line 36: Line 33:
 
* Other languages should be placed in an appropriately named sub-page of the English version.  
 
* 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 [[#List of supported languages|below]])
 
* Language subpages should use the appropriate ISO 639 code (as listed [[#List of supported languages|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.
+
* With few exceptions, pages in the <code>Help, Team Fortress Wiki, Mediawiki</code> 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 {{tl|Languages}} at the bottom of articles is now discouraged, as language links appear in the sidebar.
 
* The use of {{tl|Languages}} at the bottom of articles is now discouraged, as language links appear in the sidebar.
 
* While in the process of translating articles, using {{tlx|Trans}} is encouraged to display to other editors that the article is a work in progress.
 
* While in the process of translating articles, using {{tlx|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 {{tl|update trans}}. Pages with this tag appear in [[:Category:Translations needing updating]], sorted by language.
 
* Pages that are out of date or need updating should be tagged with {{tl|update trans}}. Pages with this tag appear in [[:Category:Translations needing updating]], sorted by language.
* Please do ''not'' sign articles using the 4 tildes ("{{code|&#126;&#126;&#126;&#126;}}"). 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.
+
* Please do ''not'' sign articles using the 4 tildes (<code><nowiki>~~~~</nowiki></code>). 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 ===
 
=== Automated translation tools ===
Line 67: Line 66:
 
* '''Displaying a different title'''
 
* '''Displaying a different title'''
 
** Displaying a title in a different language is possible with the use of the magic word {{code|&#123;&#123;DISPLAYTITLE:&#125;&#125;}}.
 
** Displaying a title in a different language is possible with the use of the magic word {{code|&#123;&#123;DISPLAYTITLE:&#125;&#125;}}.
** For example, using {{code|&#123;&#123;DISPLAYTITLE:Example&#125;&#125;}} will display the article name as ''Example''.
+
** For example, using <code><nowiki>{{DISPLAYTITLE:Example}}</nowiki></code> will display the article name as ''Example''.
  
* '''Infoboxes'''
+
* '''Templates'''
** To display a new name in an infobox, add a new line like this:
+
** Templates use parameters with values to display text. The style is <code>| parameter = text</code>. Translating the text is almost always required, but the parameter should never be translated.
**:<code>{{Item infobox</code>
+
** {{tl|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:
**:<code style="color:#006F00">| name = ''Name goes here''</code>
+
<code>type, game, slot, trade, gift, craft, paint, rename, quality</code>
**:<code>| image = ... </code>
 
** 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:
 
**:<code>| type = ...</code>
 
**:<code>| game = ...</code>
 
**:<code>| slot = ...</code>
 
**:<code>| trade, gift, craft, paint or rename = ...</code>
 
**:<code>| quality = ...</code>
 
 
**:See [[Template:Item infobox]] for further help.
 
**:See [[Template:Item infobox]] for further help.
  
Line 86: Line 78:
 
*** {{code|1=[[Weapons/fr|Armes]]}} will create [[Weapons/fr|Armes]].
 
*** {{code|1=[[Weapons/fr|Armes]]}} will create [[Weapons/fr|Armes]].
 
** If using external links that are in English, you should also use the template {{tl|lang icon}} directly after the link to indicate the language of the external link.
 
** If using external links that are in English, you should also use the template {{tl|lang icon}} directly after the link to indicate the language of the external link.
*** {{code|[http://www.google.com/ Google]}} on [[Soldier/fr]] should look like <code><nowiki>[http://www.google.com/ Google] &#123;&#123;</nowiki>lang icon|en&#125;&#125;</code>, which will generate:
+
*** {{code|[http://www.google.com/ Google]}} on [[Soldier/fr]] should look like <code><nowiki>[http://www.google.com/ Google] {{lang icon|en}}</nowiki></code>, which will generate:
 
**: [http://www.google.com/ Google] {{lang icon|en}}
 
**: [http://www.google.com/ Google] {{lang icon|en}}
 
** {{tl|Main}} and {{tl|See also}} &ndash; When using these templates you can display a different title using the parameter {{code|l1}} (lowercase L1):
 
** {{tl|Main}} and {{tl|See also}} &ndash; When using these templates you can display a different title using the parameter {{code|l1}} (lowercase L1):
Line 97: Line 89:
 
* '''Categories'''
 
* '''Categories'''
 
** Language pages should be kept in separate categories.
 
** Language pages should be kept in separate categories.
** For example on [[Wrench/fr]], if you find {{code|[[Category:Melee weapons]]}} at the bottom of the page, change it to {{code|[[Category:Melee weapons/fr]]}}.
+
** For example on [[Wrench/fr]], if you find <code><nowiki>[[Category:Melee weapons]]</nowiki></code> at the bottom of the page, change it to <code><nowiki>[[Category:Melee weapons/fr]]</nowiki></code>.
  
 
* '''Redirects'''
 
* '''Redirects'''
Line 106: Line 98:
  
 
* '''Disambiguation pages'''
 
* '''Disambiguation pages'''
** [[:Category:Disambiguation|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.
+
** [[:Category:Disambiguation|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. {{code|Demo trade 04.wav}} becomes {{code|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 <code>en-sound=yes</code> parameter to the template.
  
 
== Templates ==
 
== Templates ==
Line 114: Line 112:
 
== List of supported languages ==
 
== 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.
+
Team Fortress Wiki supports language translation of articles into 22 languages, the majority of which have localization files for TF2.
  
 
:{{c|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 [http://translation.steampowered.com/ 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.  
 
:{{c|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 [http://translation.steampowered.com/ 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.  
Line 126: Line 124:
 
|-
 
|-
 
| &ndash; || English
 
| &ndash; || English
|-
 
| style="background:#F9D483;" | ar  || style="background:#F9D483;" | Arabic
 
 
|-
 
|-
| style="background:#F9D483;" | cs || style="background:#F9D483;" | Czech
+
| ar || Arabic
 +
|-
 +
| cs || Czech
 
|-
 
|-
 
| da || Danish
 
| da || Danish
Line 174: Line 172:
  
 
[[Category:Help]]
 
[[Category:Help]]
[[Category:Team Fortress Wiki]]
 
 
[[Category:Team Fortress Wiki translation| ]]
 
[[Category:Team Fortress Wiki translation| ]]

Revision as of 15:29, 21 November 2019

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 ISO code of the language you wish to translate to, found Here
    Example: http://wiki.teamfortress.com/wiki/Scout/fr
  4. Paste the code of the English page to the new one.
    The French version of the article "Hats" would be Hats/fr, not Chapeaux, Hats/Chapeaux or Chapeaux/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 will 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 will be 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 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)
  • 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

Pictogram comment.png 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.
  • 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

  • Links
    • You can link to translated articles and display different text for the links like this:
    • 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 [[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 will have the following text on the page 'Дробовик':
      #REDIRECT [[Shotgun/ru]] {{R lang|ru}}
    • Pictogram comment.png 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.

List of supported languages

Team Fortress Wiki supports language translation of articles into 22 languages, the majority of which have localization files for TF2.

Pictogram comment.png 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)