This page is a translated version of the page and the translation is 23% complete.



translatewiki.net是用于翻译社群、语言社群、语言委员会和自由软件项目的本地化平台。它最初用于 MediaWiki 的本地化,后续添加了对 MediaWiki 扩展、FreeCol、OpenStreetMap、Etherpad Lite 及其他自由软件项目的支持。

MediaWiki 及其扩展的 300 多种语言的本地化采用 作为便利的翻译平台,也用于协作和维护。Mantis、FreeCol 和 Mwlib.rl 也在 上翻译,同时欢迎更多的项目。

您可以参与翻译为自己熟悉的语言。维基媒体基金会请求把 MediaWiki 界面翻译成新的语言也是也是在这里完成的。

该计划不是维基媒体基金会项目的一部分,但是它由维基媒体语言团队和志愿者维护。 is an associated project of non-profit fiscal sponsor called Software in the Public Interest. The translation functionality is provided by a MediaWiki extension.

  • 链接格式:[[translatewiki:]] and MediaWiki supports in-wiki translation of all the messages of core MediaWiki, extensions and skins. All translation of MediaWiki user interface messages should go through and not committed directly to code. Only the English messages and their initial documentation must be done in the source code.

Core MediaWiki and extensions must use system messages for any text displayed in the user interface. For an example of how to do this, please see Manual:Special pages. If the extension is well written, it will probably be included in in a few days, after its staff notices it on Gerrit. If it is not noticed, contact them. If it is too unstable to be translated, note so in the code or commit and contact them if necessary.

Handling support requests

Translators may have questions about some of the messages you create. provides a support request system that allows translators the ability to ask you, the project owner, questions regarding messages so that they can be better translated. This short tutorial guides you through the workflow of handling support requests.

Overview of the localisation system

Localisation update workflow

As mentioned above, translation happens on and other systems are discouraged. Here's a high level overview of the localisation update workflow:

  • Developers add or change system messages.
  • Users translate the new or changed system messages on
  • Automated tools export these messages, build new versions of the message files, incorporating the added or updated messages, for both core and extensions, and commit them to git.
  • The wikis then can pull in the updated system messages from the git repository.

Because changes on are pushed to the code daily as well, this means that each change to a message can potentially be applied to all existing MediaWiki installations in a couple days without any manual intervention or traumatic code update.

As you can see this is a multi-step process. Over time, we have found out that many things can go wrong. If you think the process is broken, please make sure to report it on our Support page, or create a new bug in Phabricator. Always be sure to describe a precise observation.