See alsoManual:MediaWiki architecture#Languages (should be merged here?)

In MediaWiki, there are various kinds of languages:

• Thesite content language (ContentLanguage service inMediaWiki\MediaWikiServices::getContentLanguage, based on$wgLanguageCode), which should generally stay the same as long as the wiki exists.
  • Thesite content language variant ($wgDefaultLanguageVariant) is the default variant whenLanguageConverter is implemented for that language.
• Theuser interface language ($contextSource->getLanguage() formerly$wgLang), which can be changed in your preferences or with&uselang=xyz in the URL, but also generally remains the same while using the wiki.
• Thepage content language. This can be different for each page, even if the site and user language is the same. It is defined in getPageLanguage() inTitle, representing what language the page content (e.g., wikitext) source is written in.
  • Thepage view language akauser language variant which is a language variant of page content language, as preferred by the user. It can also be set through&variant (or$wgVariantArticlePath) in the URL (e.g. by selecting one of the tabs)if it is a variant of the content language of the page being viewed. It's defined in getPageViewLanguage() inTitle, representing what language the rendered HTML content is written in.

All three of them arelanguage objects.

Not to be confused withWikimedia project code; see alsoLanguage codes on Meta.

A language code is a valid standard abbreviation for a language supported by MediaWiki,^[1] which uses such codes as standard identifiers for languages (mostly in accordance withISO 639-3, except two-letter codes from ISO 639-1 for "established" locales) and exposes or requires them in many points of the interface and code.^[2]

In the example below,MediaWiki:Message/ar,ar is the language code for Arabic.

Uniformity with Unicode standard is needed to provide a good language support, in particular in cooperation withCLDR; having an ISO 639-3 code is onerequirement for a language to be added to MediaWiki locales.

There are some special language codes for internal or development use:

• qqq – for message documentation, does not work withuselang etc.
• qqx – shows message names for debugging
• en-x-rtl – English, but pretends it is a right-to-left language
• en-x-piglatin – when$wgUsePigLatinVariant is enabled, forLanguageConverter testing
• x-xss – when$wgUseXssLanguage is enabled, tests XSS vulnerabilities in messages

Names.php is the master registry of languages supported by MediaWiki.This is not the same as languages of which MediaWiki will show l10n (JSON files) nor languages of which MediaWiki knows the names (viaCLDR), mind you!

Some languages in MediaWiki have what is known as a "fallback sequence".This is where MediaWiki will fall back on a different language if it cannot find what it needs.An example of this is the language codefrc (Cajun French), which falls back on the language codefr (French).The reason for this is that sometimes languages don't have all messages defined in them.

The fallback for a language can be found in its associatedlanguages/messages/MessagesXX.php file.For instanceMessagesFrc.php. You cansearch the code for all uses.There is also a JSON file with fallbacks list from July 2025 inthis page.And you can also see visualisation graph (fromSeptember 2020) byRtnf:https://altilunium.github.io/MediaWiki-Language-Fallback/.

For found language fallback chain for current UI language you can usegetFallbackLanguageChain() method.

Viewing/getting the site content language

JavaScript:

mw.config.get('wgContentLanguage');

Default value

• $contextSource->getLanguage()

Set via

• Special:Preferences
• &uselang=zxx in the URL (seeuselang)
• &variant=xy (or$wgVariantArticlePath) in the URLif it is a variant of your user language

Problems

Since interface messages can come from fallback languages but the language is not returned, the actual language of each message is not known.

Default value

• $wgLang on special pages.
• English for CSS and JS pages.
• For MediaWiki namespace pages, the language depends on the subpage. For example, MediaWiki:Message/ar will be set to Arabic (ar), and MediaWiki:Message will beContentLanguage.
• All other pages areContentLanguage by default.

Configuration

Extensions can change all other pages through thePageContentLanguage hook. The value for special pages, CSS, JS, and MediaWiki namespace pages cannot be overridden.

Examples

TheTranslate extension uses it for the page translation feature. Seetranslatewiki:Project:About/ar as a translation oftranslatewiki:Project:About. The directionality of the page is thus correctly set to right-to-left for Arabic.

Manually changing page language

Page language selection is now achievable with help of Special:PageLanguage since MediaWiki 1.24.

Users can change content language of a page which is by default the default Wiki language (ContentLanguage). Language of pages in the MediaWiki namespace can't be changed.

The feature needs to be enabled with$wgPageLanguageUseDB =true and thepagelang permission must be granted to a wiki user rights group (who can then perform page language changes).

Changing page language causes the source translation page and its units to be moved to the correct target language. In case the target language translation page already exists, the language change isn't allowed.

Matching API can be found onAPI:SetPageLanguage.

What does it define?

• In SkinTemplate, it adds a<divlang="xyz"dir="ltr/rtl"class="mw-content-ltr/rtl"></div> around the page text. The dir attribute sets the correctwriting direction. The lang attribute will always be the root code, e.g. "de" even when "de-formal" is given.

  For file pages, it is set in ImagePage.php, because there is a lot of HTML that is in the user language.

• In Parser.php, it sets the table of contents (TOC) numberings, and stuff like grammar, although not really relevant mostly. To do that only, use parserOptions->setTargetLanguage().
• The direction of the diff text (DifferenceEngine) is set to the page content language. In some cases this is not identical, in which case $diffEngineObject->setTextLanguage( $code ) can be used.
• Since1.19, it also sets the time and number-formattingmagic words, including DIRECTIONMARK, but not NAMESPACE(E), as that really depends on the site language. Note that including a template marked as language A onto a page with language B, will be parsed with language B on that page.

Multiple languages on a single page

Multiple languages on a single page are in theory not supported, but simple<divlang="xyz"dir="ltr/rtl"class="mw-content-ltr/rtl"> tags can be used to mark text as being written in a different language. If the CSS class is used, the ul/ol lists and editsection will display nicely when the dir tag is opposite to the value of that of the page content language. Things defined in the parser, like TOC and magic words, however, will not change.

Viewing/getting the page language

• JavaScript:mw.config.get( 'wgPageContentLanguage' ) - note that, when e.g. viewing the page history, it will return the page language of the page it is the history of, whereas the history page doesn't have an mw-content-ltr/rtl class. I.e. both "/wiki/Page" and "/w/index.php?title=Page&action=history" will return the language of "Page".1.19+
• The page content language is mentioned on the page info view (action=info, linked in the toolbox)1.21+
• The page content language can be retrieved in theAPI viaapi.php?action=query&prop=info1.22+

First, you have a Language object inLanguage.php.This object contains all the localisablemessage strings, as well as other important language-specific settings and custom behavior (uppercasing, lowercasing, printing dates, formatting numbers,direction,custom grammar rulesetc.).

The object is constructed from two sources: sub-classed versions of itself (classes) and Message files (messages).

There's also the MessageCache class, which handles input of text via the MediaWiki namespace.Most internationalisation is nowadays done viaManual:Messages API objects and by using thewfMessage() shortcut function, which is defined inincludes/GlobalFunctions.php.Legacy code might still be using the oldwfMsg*() functions, which are now considered deprecated in favor of the above-mentioned Message objects.

See alsoManual:Messages API.

There are two ways to get a language object.You can use the globals$wgLang andContentLanguage service (MediaWiki\MediaWikiServices::getContentLanguage) for user interface and content language respectively.For an arbitrary language you can construct an object by using$languageFactory->getLanguage('en') by replacingen with the code of the language.You can get$languageFactory, an object of theMediaWiki\Languages\LanguageFactory class, usingDependency Injection.You can also usewfGetLangObj($code); if$code could already be a language object.The list of codes is inincludes/languages/data/Names.php.

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.

With MediaWiki 1.3.0, a new system was set up for localising MediaWiki.Instead of editing the language file and asking developers to apply the change, users could edit the interface strings directly from their wikis.This is the system in use as of August 2005.People can find the message they want to translate inSpecial:AllMessages and then edit the relevant string in theMediaWiki: namespace.Once edited, these changes are live.There was no more need to request an update, and wait for developers to check and update the file.

The system is great for Wikipedia projects; however a side effect is that the MediaWiki language files shipped with the software are no longer quite up-to-date, and it is harder for developers to keep the files on meta in sync with the real language files.

As the default language files do not provide enough translated material, we face two problems:

1. New Wikimedia projects created in a language which has not been updated for a long time, need a total re-translation of the interface.
2. Other users of MediaWiki (including Wikimedia projects in the same language) are left with untranslated interfaces. This is especially unfortunate for the smaller languages which don't have many translators.

This is not such a big issue anymore, because translatewiki.net is advertised prominently and used by almost all translations.Local translations still do happen sometimes but they're strongly discouraged.Local messages mostly have to be deleted, moving the relevant translations to translatewiki.net and leaving on the wiki only the site-specific customisation; there's a huge backlog especially in older projects,this tool helps with cleanup.

English messages are very rarely out of sync with the code.Experience has shown that it's convenient to have all the English messages in the same place.Revising the English text can be done without reference to the code, just like translation can.Programmers sometimes make very poor choices for the default text.

So many things are localisable on MediaWiki that not all of them are directly available ontranslatewiki.net: seetranslatewiki:Translating:MediaWiki.If something requires adeveloper intervention on the code, you canrequest it on Phabricator, or ask attranslatewiki:Support if you don't know what to do exactly.

• Namespaces - both core and extensions, plusgender-dependent user namespaces
• Weekdays (and abbreviations)
• Months (and abbreviations)
• Bookstores forSpecial:BookSources
• Skin names
• Math names
• Date preferences -$datePreferences
• Date formats -$dateFormats
• Default date format -$defaultDateFormat
• Date preference migration map - for compatibility with old MediaWiki databases
• Default user option overrides
• Language names
• Country names (viaExtension:CLDR)
• Currency names (viaExtension:CLDR)
• Timezones
• Character encoding conversion viaiconv
• UpperLowerCase first (needs casemaps for some)^{[clarification needed]}
• UpperLowerCase^{[clarification needed]}
• Uppercase words
• Uppercase word breaks^{[clarification needed]}
• Case folding^{[clarification needed]}
• Strip punctuation for MySQL search (search optimisation)
• Get first character
• Alternate encoding
• Recoding for edit (and then recode input)^{[clarification needed]}

• Fallback languages (that is, other more closely related language(s) to use when a translation is not available, instead of the default fallback, which is English)
• Directionality (left to right or right to left, RTL)
• Direction mark character depending on RTL
• Arrow depending on RTL
• Languages where italics cannot be used
• Number formatting (comma-ify,i.e. adding or not digits separators; transform digits; transform separators)^[3]
• Truncate (multibyte)
• Grammar conversions for inflected languages
• Plural transformations
• Formatting expiry times^{[clarification needed]}
• Segmenting for diffs (Chinese)
• Convert to variants of language (between different orthographies, or scripts)
• Language specific user preference options
• Link trails and link prefix -$linkTrail. These are letters that can be glued after/before the closing/opening brackets of a wiki link, but appear rendered on the screen as if part of the link (that is, clickable and in the same colour),e.g.:[[foo]]bar. By default the link trail is "a-z"; you may want to add the accentuated or non-Latin letters used by your language to the list.
• Language code (preferably used according to the latest RFC in standard BCP 47, currentlyRFC 5646, with its associated IANA database. Avoid deprecated, grandfathered and private-use codes: look at what they mean in standard ISO 639, and avoid codes assigned to collections/families of languages in ISO 639-5, and ISO 639 codes which were not imported in the IANA database for BCP 47)
• Type of emphasising
• TheCite extension has a special page file per language,cite_text-zyx for language codezyx.

Neat functionality:

• I18NsprintfDate
• Roman numeral formatting

Currently making namespace name translations is disabled on translatewiki.net, so you need to do this yourself in Gerrit, or file aPhabricator task asking for someone else to do it.^[4]

To allow custom namespaces introduced by your extension to be translated, create aMyExtension.i18n.namespaces.php file that looks like this:

<?php/** *  Translations of the namespaces introduced by MyExtension. * * @file */$namespaceNames=[];//  For wikis where the MyExtension extension is not installed.if(!defined('NS_MYEXTENSION')){define('NS_MYEXTENSION',2510);}if(!defined('NS_MYEXTENSION_TALK')){define('NS_MYEXTENSION_TALK',2511);}/** English */$namespaceNames['en']=[NS_MYEXTENSION=>'MyNamespace',NS_MYEXTENSION_TALK=>'MyNamespace_talk',];/** Finnish (Suomi) */$namespaceNames['fi']=[NS_MYEXTENSION=>'Nimiavaruuteni',NS_MYEXTENSION_TALK=>'Keskustelu_nimiavaruudestani',];

Then load it from theextension.json file using ExtensionMessagesFiles like this:

{"name":"MyExtension","version":"0.0.1","descriptionmsg":"myextension-desc","ExtensionMessagesFiles":{"MyExtensionNamespaces":"MyExtension.i18n.namespaces.php"}}

Now, when a user installs MyExtension on their Finnish (fi) wiki, the custom namespace will be translated into Finnish magically, and the user doesn't need to do a thing!

Also remember to register your extension's namespace(s) on theExtension default namespaces page.

Seethe manual page for Special pages for up-to-date information.The following does not appear to be valid.

Create a new file for the special page aliases in this format:

<?php/** * Aliases for the MyExtension extension. * * @file * @ingroup Extensions */$aliases=[];/** English */$aliases['en']=['MyExtension'=>['MyExtension']];/** Finnish (Suomi) */$aliases['fi']=['MyExtension'=>['Lisäosani']];

Then load it from theextension.json file using ExtensionMessagesFiles like this:

{"name":"MyExtension","version":"0.0.1","descriptionmsg":"myextension-desc","ExtensionMessagesFiles":{"MyExtensionAlias":"MyExtension.i18n.alias.php"}}

When your special page code uses eitherSpecialPage::getTitleFor('MyExtension') or$this->getTitle() (in the class that provides Special:MyExtension), the localised alias will be used, if it's available.

Namespace name aliases are additional names which can be used to address existing namespaces.They are rarely needed, but not having them when they are, usually creates havoc in existing wikis.

You need namespace name aliases:

1. When a language has variants, and these variants spell some namespaces differently, and you want editors to be able to use the variant spellings. Variants are selectable in the user preferences. Users always see their selected variant, except in wikitext, but when editing or searching, an arbitrary variant can be used.
2. When an existing wiki's language, fall back language(s), or localisation is changed, with it are changed some namespace names. So as not to break the links already present in the wiki, that are using the old namespace names, you need to add each of the altered previous namespace names to its namespace name aliases, when, or before, the change is made.

The generic English namespace names are always present as namespace name aliases in all localisations, so you need not, and should not, add those.

Aliases can't be translated onTranslatewiki.net, but can be requested there or onBugzilla: seetranslatewiki:Translating:MediaWiki#Namespace name aliases.

Some linguistic settings vary across geographies; MediaWiki doesn't have a concept of region, it only has languages and language variants.

These settings need to be set once as a language's default, then individual wikis can change them as they wish in their configuration.

Time and dates are shown on special pages and alike.The default time and date format is used for signatures, so it should be the most used and most widely understood format for users of that language.Also anonymous users see the default format.Registered users can choose other formats in their preferences.

If you are familiar with PHP's time() format, you can try to construct formats yourself.MediaWiki uses a similar format string, with some extra features.If you don't understand the previous sentence, that's OK.You can provide a list of examples forDevelopers.

SeeHelp:System message#Message sources.

• Multilingual MediaWiki
• Obtaining language names from codes is possible using the core function{{#language:<code>}} documented inmagic words

• Localisation