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.
Contents
Как перевести страницу
Следуйте этим указаниям что бы начать переводить артикли.
- Провертье то что ваш язык поддерживается (see List of supported languages below). Мы поддерживаем большинство языков которые имеют оффициальные внутриигровые переводы.
- Перейдите на Английскую версию артикля страницы и нажмите "Дополнить эту страницу". Выберите всё в окне и скопируйте это.
- Перейдите к функции добавления нового языка "/LANGUAGE" в конец артикля где LANGUAGE заменён ISO639-1 кодом того языка на который вы хотите перевести, найти Here
- Вставьте код Английской страницы в новую.
- Французская версия артикля "Hats" будет Hats/fr, не Chapeaux, Hats/Chapeaux или Chapeaux/fr
- Use
{{DISPLAYTITLE:abcxyz}}
to translate the page's title.- Пример:
{{DISPLAYTITLE:Handlung}}
покажет текст "Handlung" пока вы держите настоящий текст артикля как "Storyline/de". - Отображение текста может ещё быть поставлено infobox (see below). Из-за этого, артикли про акссесуары и оружия должны не использовать этот термин что бы разрешать динамические изменения имён из dictionary.
- Пример:
- Поменяйте категории в верху страницы.
- Пример:
[[Category:Lists|Weapons]]
becomes[[Category:Lists/fr|Weapons]]
. Делайте это для всех категорий в верху страницы.
- Пример:
- Вы можете теперь переводить остатки артикля.Обратите внимание, что некоторый текст хранится на других страницах (называется"templates"). Что бы перевести их вам нужно будет редактировать их вручную.
- Когда возможно,используйте localization files в приказах использовать правильные имена и описания.
- В случае если вам нужно сохранить не законченный перевод что бы закончить его позже, добавьте
{{trans}}
на верх вашей страницы. Все не готовые переводы будут in the appropriate category.
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.
It's worth keeping in mind that translators are also part of editors, thus translation community is a part of the whole editor community. In addition to translation, participation in the creation and improvement of the original English pages is also encouraged.
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}}
will display the article name as Example.
- Displaying a title in a different language is possible with the use of the magic word
- 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:
- Templates use parameters with values to display text. The style is
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]]
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 parameterl1
(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.
- You can link to translated articles and display different text for the links like this:
- 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}}
- Note: always remember to add
{{R lang|xx}}
(this helps to find these redirects later, as there can be hundreds of them)
- You can create as many language redirects as are needed, as long as they are tagged properly with
- 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
becomesDemo 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 won't update themselves. As a result, a translated page which lacks updates will gradually become 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 22 languages, the majority of which have localization files for TF2.
- 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) |