View source for Manual:Language/ru

<languages/>
{{i18n navigation}}
{{tocright}}
<div lang="en" dir="ltr" class="mw-content-ltr">
:''See also [[Special:MyLanguage/Manual:MediaWiki architecture#Languages|Manual:MediaWiki architecture#Languages]] (should be merged here?)''
</div>

В MediaWiki есть разные виды языков:

<div lang="en" dir="ltr" class="mw-content-ltr">
* The '''site content language''' (<code>ContentLanguage</code> service in <code>MediaWiki\MediaWikiServices::getContentLanguage</code>, based on <code>{{ll|Manual:$wgLanguageCode|$wgLanguageCode}}</code>), which should generally stay the same as long as the wiki exists.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
** The '''site content language variant''' ({{ll|Manual:$wgDefaultLanguageVariant|$wgDefaultLanguageVariant}}) is the default variant when {{ll|LanguageConverter}} is implemented for that language.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The '''user interface language''' ([[Special:MyLanguage/Manual:RequestContext|$contextSource->getLanguage()]] formerly <code>{{ll|Manual:$wgLang|$wgLang}}</code>), which can be changed in your preferences or with <code>&uselang=xyz</code> in the URL, but also generally remains the same while using the wiki.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* The '''page content language'''. This can be different for each page, even if the site and user language is the same. It is defined in getPageLanguage() in [[Special:MyLanguage/Manual:Title.php|Title]], representing what language the page content (e.g., wikitext) source is written in.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
** The '''page view language''' aka '''user language variant''' which is a language variant of page content language, as preferred by the user.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">It can also be set through <code>&variant</code> (or {{$wg|VariantArticlePath}}) 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.</span> <div lang="en" dir="ltr" class="mw-content-ltr">
It's defined in getPageViewLanguage() in [[Special:MyLanguage/Manual:Title.php|Title]], representing what language the rendered HTML content is written in.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
All three of them are [[Special:MyLanguage/language object|language object]]s.
</div>

<span id="Language_code"></span>
== Код языка ==

<div lang="en" dir="ltr" class="mw-content-ltr">
: ''Not to be confused with [[m:Special:MyLanguage/Special language codes|Wikimedia project code]]; see also [[m:Special:MyLanguage/Language codes|Language codes]] on Meta.''
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">A language code is a valid standard abbreviation for a language supported by MediaWiki,<ref>See [[phab:diffusion/MW/browse/master/includes/languages/data/Names.php|includes/languages/data/Names.php]].</ref> which uses such codes as standard identifiers for languages (mostly in accordance with [[w:ISO 639|ISO 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.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Despite this, as of 2012 language codes validation is not yet a solved problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See Niklas Laxström, ''[http://laxstrom.name/blag/2012/08/28/language-validation-in-mediawiki/ Language validation in MediaWiki]'', August 28th, 2012.</span></ref>

<div lang="en" dir="ltr" class="mw-content-ltr">
In the example below, <code>MediaWiki:Message/ar</code>, <code>ar</code> is the language code for {{#language:ar|{{PAGELANG2}}}}.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Uniformity with Unicode standard is needed to provide a good language support, in particular in cooperation with [[translatewiki:CLDR|CLDR]]; having an ISO 639-3 code is one [[translatewiki:Translatewiki.net_languages#Policy_on_enabling_translation_into_a_language|requirement for a language to be added to MediaWiki locales]].
</div>

== Names.php ==
<span lang="en" dir="ltr" class="mw-content-ltr">{{git file | project = mediawiki/core | file = includes/languages/data/Names.php | text = Names.php}} is the master registry of languages supported by MediaWiki.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is not the same as languages of which MediaWiki will show l10n ([[Special:MyLanguage/Help:System_message#Localisation_file_format|JSON files]]) nor languages of which MediaWiki knows the names (via {{ll|Extension:CLDR|nsp=0}}), mind you!</span>

<span id="Fallback_languages"></span>
== Резервные языки ==
{{See also|Help:System message|ll=1}}
[[File:MediaWiki fallback chains.svg|thumb|Резервные цепочки <span lang="en" dir="ltr" class="mw-content-ltr">(Some of the lines shown are inaccurate due to double languages in the fallback. Check if the connection actually exists in the [[phab:T258492#6490574|text version]])</span>]]
<span lang="en" dir="ltr" class="mw-content-ltr">Some languages in MediaWiki have what is known as a "fallback sequence".</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is where MediaWiki will fall back on a different language if it cannot find what it needs.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">An example of this is the language code <code>frc</code> (Cajun French), which falls back on the language code <code>fr</code> (French).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The reason for this is that sometimes languages don't have all messages defined in them.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">The fallback for a language can be found in its associated <code>languages/messages/MessagesXX.php</code> file.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For instance {{git file|file=languages/messages/MessagesFrc.php|text=MessagesFrc.php}}. You can [https://codesearch.wmcloud.org/search/?q=%5C%24fallback%20%3D&i=nope&files=languages%2Fmessages&excludeFiles=&repos=MediaWiki%20core search the code for all uses].</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is also a plain list from {{ym|2020|09}} in [[phab:T258492#9028038|this Phabricator comment]].</span>

<span id="Site_content_language"></span>
==Язык содержимого сайта==

<div lang="en" dir="ltr" class="mw-content-ltr">
Viewing/getting the site content language
</div>

{{ll|Manual:Interface/JavaScript|JavaScript}}:
<syntaxhighlight lang="javascript">
mw.config.get( 'wgContentLanguage' );
</syntaxhighlight>

<span id="User_interface_language"></span>
== Язык пользовательского интерфейса ==
{{MW 1.18|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
;Default value
:*[[Special:MyLanguage/Manual:RequestContext|$contextSource->getLanguage()]]
</div>

;Установить через

:*Special:Preferences
<div class="mw-translate-fuzzy">
:* <code>&uselang=zxx</code> в URL (см. [[Special:MyLanguage/uselang|uselang]])
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:* <code>&variant=xy</code> (or {{$wg|VariantArticlePath}}) in the URL '''if''' it is a variant of your user language
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
;Problems
:Since interface messages can come from fallback languages but the language is not returned, the actual language of each message is not known.
</div>

<span id="Page_content_language"></span>
== Язык содержимого страницы ==
{{MW 1.18|and after}}
;Значение по умолчанию

<div lang="en" dir="ltr" class="mw-content-ltr">
:*$wgLang on special pages.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*English for CSS and JS pages.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*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 be <code>ContentLanguage</code>.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*All other pages are <code>ContentLanguage</code> by default.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
;Configuration
:Extensions can change all other pages through the {{ll|Manual:Hooks/PageContentLanguage|PageContentLanguage}} hook.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">The value for special pages, CSS, JS, and MediaWiki namespace pages cannot be overridden.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
;Examples
:The [[Special:MyLanguage/Extension:Translate|Translate extension]] uses it for the page translation feature. See [[translatewiki:Project:About/ar|translatewiki:Project:About/ar]] as a translation of [[translatewiki:Project:About|translatewiki:Project:About]]. The directionality of the page is thus correctly set to right-to-left for Arabic.
</div>
{{MW 1.24|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
;Manually changing page language
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:Page language selection is now achievable with help of Special:PageLanguage since MediaWiki 1.24.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:Users can change content language of a page which is by default the default Wiki language (<code>ContentLanguage</code>). Language of pages in the MediaWiki namespace can't be changed.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:The feature needs to be enabled with <code class="mw-highlight">{{ll|Manual:$wgPageLanguageUseDB|$wgPageLanguageUseDB}} = {{#tag:span|true|class=k}}</code> and the <code>pagelang</code> permission must be granted to a wiki user rights group (who can then perform page language changes).
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
: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.
</div> 
<div lang="en" dir="ltr" class="mw-content-ltr">
:Matching API can be found on {{ll|API:SetPageLanguage}}.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
;What does it define?
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
:*In SkinTemplate, it adds a <syntaxhighlight lang=html inline><div lang="xyz" dir="ltr/rtl" class="mw-content-ltr/rtl"></div></syntaxhighlight> around the page text. The dir attribute sets the correct '''[[Special:MyLanguage/Directionality support|writing direction]]'''. The lang attribute will always be the root code, e.g. "de" even when "de-formal" is given.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*:For file pages, it is set in ImagePage.php, because there is a lot of HTML that is in the user language.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*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().
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*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.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
:*Since {{r|94680|1.19}}, it also sets the time and number-formatting '''[[Special:MyLanguage/Help:magic words|magic 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.
</div>

;Несколько языков на одной странице :Несколько языков на одной странице теоретически не поддерживаются, но можно использовать простые теги <syntaxhighlight lang=html inline><div lang="xyz" dir="ltr/rtl" class="mw-content-ltr/rtl"></syntaxhighlight>, чтобы пометить текст как написанный на другом языке. Если используется класс CSS, списки ul/ol и раздел редактирования будут хорошо отображаться, когда тег dir противоположен значению языка содержимого страницы. Однако вещи, определенные в синтаксическом анализаторе, такие как оглавление и волшебные слова, не изменятся.

;Просмотр/получение языка страницы

<div lang="en" dir="ltr" class="mw-content-ltr">
*[[Special:MyLanguage/Manual:Interface/JavaScript|JavaScript]]: <code>mw.config.get( 'wgPageContentLanguage' )</code> - 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".
</div> {{MW version-inline|1.19+}}
<div lang="en" dir="ltr" class="mw-content-ltr">
*The page content language is mentioned on the page info view (<code>action=info</code>, linked in the toolbox)
</div> {{MW version-inline|[[gerrit:30099|1.21+]]}}
<div lang="en" dir="ltr" class="mw-content-ltr">
*The page content language can be retrieved in the [[Special:MyLanguage/API|API]] via [[Special:MyLanguage/API:Properties|api.php?action=query&prop=info]]
</div> {{MW version-inline|[[gerrit:64512|1.22+]]}}

<span id="Code_structure"></span>
==Структура кода== 
<span lang="en" dir="ltr" class="mw-content-ltr">First, you have a Language object in {{ll|Manual:Code#Language.php|Language.php}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This object contains all the localisable [[Special:MyLanguage/Help:System message|message strings]], as well as other important language-specific settings and custom behavior (uppercasing, lowercasing, printing dates, formatting numbers, [[Special:MyLanguage/Directionality support|direction]], [[Special:MyLanguage/Manual:Messages API#…on use context inside sentences via GRAMMAR|custom grammar rules]] ''etc.'').</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The object is constructed from two sources: sub-classed versions of itself (classes) and Message files (messages).
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">There's also the MessageCache class, which handles input of text via the MediaWiki namespace.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Most internationalisation is nowadays done via {{ll|Manual:Messages API}} objects and by using the <code>wfMessage()</code> shortcut function, which is defined in <code>includes/GlobalFunctions.php</code>.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Legacy code might still be using the old <code>wfMsg*()</code> functions, which are now considered deprecated in favor of the above-mentioned Message objects.</span>

См. также {{ll|Manual:Messages API}}.

<span id="Language_objects"></span>
===Языковые объекты===
<span lang="en" dir="ltr" class="mw-content-ltr">There are two ways to get a language object.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can use the globals {{ll|Manual:$wgLang|$wgLang}} and <code>ContentLanguage</code> service (<code>MediaWiki\MediaWikiServices::getContentLanguage</code>) for user interface and content language respectively.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For an arbitrary language you can construct an object by using {{phpi|$languageFactory->getLanguage( 'en' )}} by replacing <code>en</code> with the code of the language.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can get {{phpi|$languageFactory}}, an object of the {{phpi|MediaWiki\Languages\LanguageFactory}} class, using {{ll|Dependency Injection}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can also use <syntaxhighlight lang=php inline>wfGetLangObj( $code );</syntaxhighlight> if <syntaxhighlight lang=php inline>$code</syntaxhighlight> could already be a language object.</span>
Список кодов находится в <code>includes/languages/data/Names.php</code>.

<span lang="en" dir="ltr" class="mw-content-ltr">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.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There are multiple layers of caching and merging with [[#Fallback languages|#Fallback languages]], but the details are irrelevant in normal use.</span>

<span id="Old_local_translation_system"></span>
==Устаревшая локальная система перевода==
<span lang="en" dir="ltr" class="mw-content-ltr">With MediaWiki 1.3.0, a new system was set up for localising MediaWiki.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Instead of editing the language file and asking developers to apply the change, users could edit the interface strings directly from their wikis.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is the system in use as of August 2005.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">People can find the message they want to translate in [[Special:AllMessages]] and then edit the relevant string in the <code>MediaWiki:</code> namespace.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Once edited, these changes are live.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There was no more need to request an update, and wait for developers to check and update the file.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As the default language files do not provide enough translated material, we face two problems:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
#New Wikimedia projects created in a language which has not been updated for a long time, need a total re-translation of the interface.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
#Other users of MediaWiki (including Wikimedia projects in the same language) are left with untranslated interfaces.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">This is especially unfortunate for the smaller languages which don't have many translators.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">This is not such a big issue anymore, because translatewiki.net is advertised prominently and used by almost all translations.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Local translations still do happen sometimes but they're strongly discouraged.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">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, [//toolserver.org/~robin/?tool=cleanuplocalmsgs this tool] helps with cleanup.</span>

<span id="Keeping_messages_centralised_and_in_sync"></span>
==Централизованное хранение и синхронизация сообщений==
<span lang="en" dir="ltr" class="mw-content-ltr">English messages are very rarely out of sync with the code.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Experience has shown that it's convenient to have all the English messages in the same place.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Revising the English text can be done without reference to the code, just like translation can.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Programmers sometimes make very poor choices for the default text.</span>

{{Anchor|what-can-be-localized}}<!-- for links from external pages-->
<span id="What_can_be_localised"></span>
==Что можно локализовать==
<span lang="en" dir="ltr" class="mw-content-ltr">So many things are localisable on MediaWiki that not all of them are directly available on {{ll|translatewiki.net|translatewiki.net}}: see [[translatewiki:Translating:MediaWiki|translatewiki:Translating:MediaWiki]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If something requires a [[Special:MyLanguage/Developers|developer]] intervention on the code, you can [[Special:MyLanguage/How to report a bug|request it on Phabricator]], or ask at [[translatewiki:Support|translatewiki:Support]] if you don't know what to do exactly.</span>

* [[#Namespaces|Пространства имён]] - <span lang="en" dir="ltr" class="mw-content-ltr">both core and extensions, plus [[Special:MyLanguage/Manual:Messages API#Users have grammatical genders|gender]]-dependent user namespaces</span>
* Дни недели (и сокращения)
* Месяцы (и сокращения)
* <span lang="en" dir="ltr" class="mw-content-ltr">Bookstores for [[Special:BookSources]]</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Skin names</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Math names</span>
* {{ll|Manual:Date formatting|2=Настройки даты}} - <code>$datePreferences</code>
* {{ll|Manual:Date formatting|2=Форматы даты}} - <code>$dateFormats</code>
* {{ll|Manual:Date formatting|2=Формат даты по умолчанию}} - <code>$defaultDateFormat</code>
* {{ll|Manual:Date formatting|2=<span lang="en" dir="ltr" class="mw-content-ltr">Date preference migration map</span>}} - <span lang="en" dir="ltr" class="mw-content-ltr">for compatibility with old MediaWiki databases</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Default user option overrides</span>
* Названия языков
* <span lang="en" dir="ltr" class="mw-content-ltr">Country names (via {{ll|Extension:CLDR}})</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Currency names (via {{ll|Extension:CLDR}})</span>
* Часовые пояса
* <span lang="en" dir="ltr" class="mw-content-ltr">Character encoding conversion via [[w:en:Iconv|<code>iconv</code>]]</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">UpperLowerCase first (needs casemaps for some)</span>{{clarify}}
* <span lang="en" dir="ltr" class="mw-content-ltr">UpperLowerCase</span>{{clarify}}
* Слова в верхнем регистре
* Разрывы слов в верхнем регистре{{clarify}}
* <span lang="en" dir="ltr" class="mw-content-ltr">Case folding</span>{{clarify}}
* <span lang="en" dir="ltr" class="mw-content-ltr">Strip punctuation for MySQL search (search optimisation)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Get first character</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Alternate encoding</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Recoding for edit (and then recode input)</span>{{clarify}}

[[Image:MediaWiki fallback chains.svg|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Graph of language fallback</span>]]

* <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Manual:Language|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)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Directionality (left to right or right to left, RTL)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Direction mark character depending on RTL</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Arrow depending on RTL</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Languages where italics cannot be used</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Number formatting (comma-ify, ''i.e.'' adding or not digits separators; transform digits; transform separators)</span><ref>
<span lang="en" dir="ltr" class="mw-content-ltr">These are configured by language in the respective <code>language/classes/LanguageXx.php</code> or <code>language/messages/MessagesXx.php</code> files.</span></ref>
* <span lang="en" dir="ltr" class="mw-content-ltr">Truncate (multibyte)</span>
* [[Special:MyLanguage/Manual:Messages API#…on use context inside sentences via GRAMMAR|<span lang="en" dir="ltr" class="mw-content-ltr">Grammar conversions for inflected languages</span>]]
* [[Special:MyLanguage/Manual:Messages API#Be aware of PLURAL use on all numbers|Множественные преобразования]]
* <span lang="en" dir="ltr" class="mw-content-ltr">Formatting expiry times</span>{{clarify}}
* <span lang="en" dir="ltr" class="mw-content-ltr">Segmenting for diffs (Chinese)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Convert to variants of language (between different orthographies, or scripts)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Language specific user preference options</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Help:Links#linktrail|Link trails]] and link prefix - <code>$linkTrail</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">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.'': <code><nowiki>[[foo]]</nowiki>bar</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Language code (preferably used according to the latest RFC in standard BCP 47, currently {{IETF RFC|5646}}, with its associated IANA database.</span> <span lang="en" dir="ltr" class="mw-content-ltr">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)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Type of emphasising</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:Cite|nsp=0}} extension has a special page file per language, <code>cite_text-''zyx''</code> for language code <code>zyx</code>.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Neat functionality:
</div>

* <span lang="en" dir="ltr" class="mw-content-ltr">I18N <code>sprintfDate</code></span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Roman numeral formatting</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Namespaces===
</div>

:<!-- See [https://translatewiki.net/wiki/Translating:MediaWiki#Translating namespace names how they're translated] and [[#Namespace name aliases]]. -->
<span lang="en" dir="ltr" class="mw-content-ltr">Currently making namespace name translations is disabled on translatewiki.net, so you need to do this yourself in Gerrit, or file a {{ll|Phabricator}} task asking for someone else to do it.</span><ref>
[[gerrit:211677|https://gerrit.wikimedia.org/r/211677]]
</ref>

<div lang="en" dir="ltr" class="mw-content-ltr">
To allow custom namespaces introduced by your extension to be translated, create a <code>''MyExtension''.i18n.namespaces.php</code> file that looks like this:
</div>

<syntaxhighlight lang="php">
<?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',
];
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then load it from the <code>extension.json</code> file using ExtensionMessagesFiles like this:
</div>

<syntaxhighlight lang="json">
{
	"name": "MyExtension",
	"version": "0.0.1",
	"descriptionmsg": "myextension-desc",
    "ExtensionMessagesFiles": {
		"MyExtensionNamespaces": "MyExtension.i18n.namespaces.php"
	}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
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!
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Also remember to register your extension's namespace(s) on the {{ll|extension default namespaces}} page.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Special page aliases===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">See [[Manual:Special pages#The aliases file|the manual page for Special pages]] for up-to-date information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The following does not appear to be valid.</span>

<!--TODO: check what needs to be updated or removed here -->

<div lang="en" dir="ltr" class="mw-content-ltr">
Create a new file for the special page aliases in this format:
</div>

<syntaxhighlight lang="php">
<?php
/**
 * Aliases for the MyExtension extension.
 *
 * @file
 * @ingroup Extensions
 */

$aliases = [];

/** English */
$aliases['en'] = [
	'MyExtension' => [ 'MyExtension' ]
];

/** Finnish (Suomi) */
$aliases['fi'] = [
	'MyExtension' => [ 'Lisäosani' ]
];
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then load it from the <code>extension.json</code> file using ExtensionMessagesFiles like this:
</div>

<syntaxhighlight lang="json">
{
	"name": "MyExtension",
	"version": "0.0.1",
	"descriptionmsg": "myextension-desc",
    "ExtensionMessagesFiles": {
		"MyExtensionAlias": "MyExtension.i18n.alias.php"
	}
}
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
When your special page code uses either {{phpi|SpecialPage::getTitleFor( 'MyExtension' )}} or {{phpi|$this->getTitle()}} (in the class that provides Special:MyExtension), the localised alias will be used, if it's available.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Namespace name aliases===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Namespace name aliases are additional names which can be used to address existing namespaces.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">They are rarely needed, but not having them when they are, usually creates havoc in existing wikis.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
You need namespace name aliases:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# When a language has variants, and these variants spell some namespaces differently, and you want editors to be able to use the variant spellings.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">Variants are selectable in the user preferences.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users always see their selected variant, except in wikitext, but when editing or searching, an arbitrary variant can be used.</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
# When an existing wiki's language, fall back language(s), or localisation is changed, with it are changed some namespace names.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
The generic English namespace names are always present as namespace name aliases in all localisations, so you need not, and should not, add those.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Aliases can't be translated on {{ll|translatewiki.net}}, but can be requested there or on {{ll|bugzilla}}: see [[translatewiki:Translating:MediaWiki#Namespace name aliases|translatewiki:Translating:MediaWiki#Namespace name aliases]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Regional settings===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Some linguistic settings vary across geographies; MediaWiki doesn't have a concept of region, it only has languages and language variants.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
These settings need to be set once as a language's default, then individual wikis can change them as they wish in their configuration.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===== Time and date formats =====
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Time and dates are shown on special pages and alike.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">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.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Also anonymous users see the default format.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Registered users can choose other formats in their preferences.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">If you are familiar with PHP's time() format, you can try to construct formats yourself.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki uses a similar format string, with some extra features.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you don't understand the previous sentence, that's OK.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can provide a list of examples for {{ll|Developers}}.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
See [[Special:MyLanguage/Help:System message#Message sources|Help:System message#Message sources]].
</div>

<span id="Notes"></span>
== Примечания ==
<references/>

<span id="See_also"></span>
== Смотрите также ==

* [[Special:MyLanguage/Multilingual MediaWiki|Мультиязычный MediaWiki]]
<div lang="en" dir="ltr" class="mw-content-ltr">
* Obtaining language names from codes is possible using the core function <nowiki>{{#language:<code>}}</nowiki> documented in [[Special:MyLanguage/Help:magic words|magic words]]
</div>

[[Category:Localisation{{#translation:}}]]