Help:System message

In principle for every language a set of ca. 1800 system messages in that language is provided in the message file languages/Messageslanguagecode.php. In the preferences a logged-in user can select an interface language. For incidental use it can also be specified in the URL with the parameter uselang=language_code. As of October 2007 there are ca. 150 interface languages to choose from. For completeness of the language files see localization statistics.

Each MediaWiki site has a site language. This is the default interface language for that site. As of October 2007 there are ca. 100 languages for which there is a separate wiki.gis.com but not yet a language file. These wiki.gis.coms usually have English as default interface language. However, nowadays creating the language file is a condition for opening a new language edition of wiki.gis.com, see.

Typically the code uses the site language in link targets (function wfMsgForContent), and the user-specified language in other texts, including link labels (function wfMsg).

HTML elements which are not normally passed on to the browser, are when occurring in certain messages.

MediaWiki namespace
The MediaWiki namespace is one of the 16 standard namespaces in the database structure of the MediaWiki software. For all languages this namespace allows administrators to create site-specific deviations from the default system messages. It is enabled by default in recent mediawiki versions, $wgUseDatabaseMessages = true; enables them. For each deviation from the default in the site language $wgLanguageCode there is a page MediaWiki:message_ID, and for each deviation from the default in each other language a page MediaWiki:message_ID/language_code. See e.g. MediaWiki:Aboutpage. However, MediaWiki:Sidebar/language_code does not work (for a sidebar for users with that interface language); instead, the page MediaWiki:Sidebar can refer to message ID's which provides link labels dependent on the user-specified interface language. If the message is neither defined in the message file concerned, nor on the MediaWiki page, the message in the message file for English is used.

When viewing a "non-existing" page of which the name is an existing message name, the page shows the default. A "non-existing" page can be recognized by the lack of a history link. The edit page autofills with the default. Transclusion of a "non-existing" page in the MediaWiki namespace trancludes the default.

For the names of all "existing" pages see [ @] A B C D E F G H &#160; I &#160;  J K L M N O P Q R S T U V W X Y Z

For the interface language set in the preferences, all default messages and current versions can be viewed at Special:Allmessages, with red links to create new deviations from the defaults. When creating a page to override the default it is useful to first save the default version, to allow diffs with it.

Deviating from the default is a bit slower.

An administrator with access to the language files can choose between adapting these and creating pages in the MediaWiki namespace. The latter makes it easier to update to a new version of MediaWiki while keeping the own versions of messages. On the other hand, is easier to transfer a language file to another MediaWiki site than to export and import pages, for the benefit of users who have selected the language concerned as interface language.

An extension can set e.g. message key aaa to bbb by:

global $wgMessageCache; $wgMessageCache->addMessages( array ('aaa' => 'bbb') );

The key has to start with a lowercase letter, even though message files define messages using an ID written with a capital, and even though the corresponding MediaWiki page has a capital after the colon, in this case MediaWiki:Aaa, even on wikis which allow a lowercase first letter in page names. (The default content of MediaWiki:aaa becomes bbb, but changing it has no effect.)

After getting the array $ma of extension messages: $ma = $wgMessageCache->getExtensionMessagesFor( 'en' ); the value can be retrieved with $ma['aaa'], e.g. by: $wgOut->addWikiText( $ma['aaa'] );

The result after possible overriding by the contents of the MediaWiki page can be retrieved by wfMsg('aaa').

This applies not only for a message in the strict sense; for example, an extension can allow the user community, through a sysop, to supply parameters in this way; this can even be the name of an extension tag, see e.g. mw:Extension:PropertyTable, where the tag is the default, but e.g. the tag < pr> can be used after creating the page "MediaWiki:propertyTable tag" with the content "pr" (but note that for portability of wikitext across wikis with the same extension this flexibility has also disadvantages).

All characters of namespace prefixes are case-insensitive, so one can write "mediawiki:".

MediaWiki before version 1.9.x
The concept of messages has changed in release 1.9.x. Before, there existed a page for each message, even if it was the default. On upgrade, all pages with default messages are deleted.

Protection
By default, the whole MediaWiki namespace is protected. This is necessary for a number of reasons:


 * Many messages are in plain HTML, hence users could insert malicious scripts
 * Vandalism of some messages would be extremely disruptive, for example changes to the text of the links in the sidebar would immediately be visible to all users

On the other hand, especially for pages MediaWiki:message_ID/language_code the protection is somewhat impractical because administrators do not know all the languages that can be set for the user interface.

If an administrator wishes to allow general editing of a MediaWiki page, a method is to place the message on a template, and transclude the template onto the MediaWiki page.

A few messages can in theory cause the software to stop working if they are changed, for example "linktrail". Therefore and for processing efficiency the effect of page MediaWiki:Linktrail has been disabled: the software ignores its contents, taking the regular expression straight out of the message files.

Technical details
The namespace number of     messages is 8, with a corresponding      namespace 9 to discuss individual messages. Some MediaWiki wikis offer templates like to propose modifications, others have a page like Meta:Requests for help from a sysop or bureaucrat for this purpose.


 * Links to MediaWiki messages work like links to ordinary pages, examples&#58;
 *  MediaWiki:Edit  MediaWiki:Edit,
 *  w:de:MediaWiki:Edit  w:de:MediaWiki:Edit,
 *  [ demo]  [ demo].

Each message in the  array in Messages.php corresponds to a page in the MediaWiki namespace. For example, there is a line in the php file:

'confirmprotect' =&gt; 'Confirm protection',

To this corresponds the page MediaWiki:Confirmprotect, and. When this page is edited the new message is automatically used for say. Similarly w:fr:MediaWiki:Confirmprotect has the content Confirmer la protection, note that the page name itself is not translated.

Transclusion
Transclusion of a system message, see e.g., can be done with the regular tranclusion syntax for the MediaWiki page, even if the page does not exist and the default is used:
 * , the system message with id "edit" that the site uses in the default interface interlanguage of the site.

Also, parser function int can be used:
 * , the system message with id "edit" that the site uses in the user-specified interface interlanguage.

If there is neither a page nor a default the result of "int" is different from "MediaWiki:" even if the user uses the default interface language of the site:

Messages defined in extensions, even if they are in Special:Allmessages, may or may not be transcluded:

However many messages are not suited for inclusion, because they contain $1 and similar parameters not evaluated by the template parser, or raw CSS and XHTML markup not permitted on normal pages.

Interlanguage links
Interlanguage links in MediaWiki messages typically do not work: noinclude tags and the link syntax may not be interpreted.

Instead, one can use in-page interlanguage links on the talk pages, does this for some major MediaWiki wikis.

Strings exclusive to language file
Some text strings cannot be customised using this feature, and so can only be changed by editing the language file:


 * The namespace titles "User", "wiki.gis.com", "Image", etc. ($namespaceNames)
 * The names of the special pages ($specialPageAliases)
 * $skinNames (shown in Special:Preferences)
 * $bookstoreList
 * $separatorTransformTable
 * $linkTrail
 * $dateFormats