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 too unstable to be translated, note so in the code or commit and contact them if necessary.
See also Overview of the localisation system and What can be localised. This object contains all the localisable message strings, as well as other important language-specific settings and custom behaviour (uppercasing, lowercasing, printing dates, formatting numbers, direction, custom grammar rules etc.).
Most internationalisation is nowadays done via Message objects and by using the functions, which are now considered deprecated in favour of the above-mentioned Message objects. For an arbitrary language you can construct an object by using .
Language objects are needed for doing language-specific functions, most often to do number, time and date formatting, but also to construct lists and other things.
There are multiple layers of caching and merging with fallback languages, but the details are irrelevant in normal use.
This page gives a technical description of Media Wiki's internationalisation and localisation (i18n and L10n) system, and gives hints that coders should be aware of.
Our mantra is that i18n must not be an afterthought: it's an essential component since the earliest phases of your software, as well as one of the core principles of Media Wiki.
supports in-wiki translation of all the messages of core Media Wiki and of the extensions.
If you would like to have nothing to do with all the technicalities in this page about editing files, Git, creating patches, and so forth, go directly to
All translation of Media Wiki 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 Media Wiki 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.