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

Warning: Display title "" overrides earlier display title "".

i18n docs je lokalizační platforma pro překladatelské komunity, jazykové komunity a projekty svobodného softwaru. Začalo to lokalizací pro MediaWiki. Později byla přidána podpora rozšíření MediaWiki, FreeCol, OpenStreetMap, Etherpad Lite a dalších projektů svobodného softwaru.

Více než 300 lokalizací MediaWiki a jeho rozšíření používá jako pohodlné překladové médium, jakož i pro koordinaci a údržbu. Mantis, FreeCol a Mwlib.rl lze také překládat na Více projektů je vítáno.

Můžete se podílet na překladu do jazyka, který znáte. Tam jsou také překlady rozhraní MediaWiki do nových jazyků pro požadované projekty nadace Wikimedia Foundation.

Tento projekt není součástí Projektů Wikimedia Foundation, ale je podporován týmem Wikimedia Language a dobrovolníky. is an associated project of non-profit fiscal sponsor called Software in the Public Interest. The translation functionality is provided by a MediaWiki extension.

  • Formát odkazu na Interwiki: [[translatewiki:]] 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's not noticed, contact them. If it's 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.

Wikimedia projects and any other wikis can benefit immediately and automatically from localisation work thanks to the LocalisationUpdate extension.[1] This compares the latest English messages to the English messages in production. If they are not the same, the production translations are updated and made available to users.

Once translations are in the version control system, the Wikimedia Foundation has a daily job that updates a checkout or clone of the extension repository. This was first established in September 2009.[2]

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.


  1. Which works through the localisation cache and for instance on Wikimedia projects updates it daily; see also the technical details about the specific implementation.
  2. LocalisationUpdate update; LocalisationUpdate is live