Manual:$wgForceUIMsgAsContentMsg
<translate> Language, regional and character encoding settings</translate>: $wgForceUIMsgAsContentMsg | |
---|---|
Array of UI messages that should be treated as content messages. |
|
<translate> Introduced in version:</translate> | 1.4.0 |
<translate> Removed in version:</translate> | <translate> still in use</translate> |
<translate> Allowed values:</translate> | (array of strings) |
<translate> Default value:</translate> | [] |
<translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate> |
List of system messages that should be displayed in user's interface language, even if they would ordinarily be displayed in site's content language.
Details
When translating messages with wfMsg()
[1], it is not always clear what should be considered UI messages and what should be content messages.
For example, for regular Wikipedia sites like en.wikipedia.org, there should be only one 'mainpage'; therefore when getting the link of 'mainpage', treat it as content of the site and call wfMsgForContent()
[1] while, for rendering the text of the link, call wfMsg()
.
The code in default behaves this way.
However, multilingual sites like Commons do offer different versions of 'mainpage' and the like for different languages.
This array provides a way to override the default behavior.
For example, to allow language specific mainpage and community portal, set
$wgForceUIMsgAsContentMsg = ['mainpage', 'portal-url'];
Notes
- ↑ 1.0 1.1 Functions 'wfMsg()' and 'wfMsgForContent()' are currently deprecated. See replacement rules.