View source for Help:Extension:Translate/Page translation administration/be-tarask

<languages />
{{Extension-Translate}}
{{TOCright}}
'''Што.''' Можнасьць перакладу старонак дазваляе кантраляваны пераклад вікістаронак на іншыя мовы.
<span lang="en" dir="ltr" class="mw-content-ltr">That means that the content of each translation will be, usually, equal to the source page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is opposed to, for example, the different language version of articles in different Wikipedias, which are fully independent of each other.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is assumed that pages are only translated from one primary language to other languages, but translators can take advantage of translations in other languages too if they exist.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Why'''. Without any help, translating more than a few pages into other languages becomes a time-waster at best, an unmaintainable mess at worst.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">With the page translation feature you can avoid the mess and bring structure to the translation process.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The core idea is that the source text is segmented into smaller units, each of which will be translated individually.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">When the source text is segmented into units, all changes can be isolated and translators only need to update the translations of units which have had changes in source text.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This also enables translators to work on units of manageable size and share the work between multiple translators or continue the translation in later sessions, because they don't need to do all at once.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Who'''. This page elaborates on the [[Special:MyLanguage/Help:Extension:Translate/Page_translation_example|page translation tutorial]] by providing deeper insight on how the system works, and suggests best practices for a wide variety of cases.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This page is intended for page translation administrators and generally for everyone who edits the source text of translatable pages, even if they don't have the access to the administrative features of approving changes for translation.</span>

Каб атрымаць пашыраныя правы адміністратара перакладаў на '''MediaWiki.org''', перайдзіце на [[Project:Requests|Праект:Запыты]].
Наконт запытаў на '''Мэце''' глядзіце [[m:Meta:Requests for adminship#Requests for translation adminship|Мэта:Запыты]].
Наконт '''Вікісховішча''' — [[c:Commons:Bureaucrats' noticeboard|Вікісховішча:Дошка абвестак]].

{{anchor|overview}}
<span id="Life_of_a_translatable_page"></span>
== Жыцьцё перакладальнай старонкі ==
<span lang="en" dir="ltr" class="mw-content-ltr">'''Roles'''. Multiple people are involved in the process of writing and translating a wiki page: the initial writer creates a page, someone corrects spelling errors, a page translation administrator marks the page for translation, translators translate, someone makes changes to the page, a page translation administrator marks those changes for translation and translators update translations.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Those roles may overlap more or less, but the ultimate responsibility for a hassle-free translation is left for the page translation administrator.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The administrator decides when the page is ready for translation the first time, ensures that the segmentation serves a purpose and approves (or corrects) changes.</span>

'''Падрыхтоўка'''. Каб нешта перакладаць, сьпярша трэба гэта напісаць.
<span lang="en" dir="ltr" class="mw-content-ltr">If you already have done translation without the Translate extension, see below the [[#migration|section about migrating translations]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you want lots of translations quickly, it is crucial for the source text to be in good shape.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Before marking a page for translation, ask someone else to proofread it and if possible ask a language specialist to make the text clearer and more concise.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Difficult vocabulary and hard to understand sentences are a show stopper to many volunteer translations.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Markup, too, can cause problems for translators, but as a translation administrator you can avoid those issues, see the [[#segmentation|section about handling markup]] below.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Naturally the changes you make to the source text of translations require updates of all existing translations, so it is better to wait until the contents of the page have stabilized.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">On the other hand, changes do happen, and the system handles that well, so check out the [[#changes|section about handling changes]] below.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Tagging'''. When the text is otherwise ready for translation, anyone can mark the translatable parts by enclosing them in {{tag|translate|open}} tags and adding the {{tag|languages|single}} bar to the page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The latter adds a list of all translations of the page, with their completion and up-to-date percentages.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There is no other indication that translations exist.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See below [[#markup|how to actually do the tagging]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The system will detect when the tags are placed on the translatable page, and the page will have a link to mark it for translation.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It will also complain and prevent saving if you for example forgot to add a closing tag.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The translatable page will also be listed on Special:PageTranslation as ''ready for marking''.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Marking'''. After the tagging, a translation administrator marks the page for translation.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The interface is explained in [[Special:MyLanguage/Help:Extension:Translate/Page translation example|Page translation example]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The translation administrator's responsibility is to make sure that the segmentation makes sense and that tagging has been proper.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The page can be marked again if it has changed in the meanwhile.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See below [[#changes|how to make changes that cause minimal disruptions]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The marking of the page starts a background process that uses MediaWiki's [[Special:MyLanguage/Manual:Job queue|job queue]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This process goes over each translation page and regenerates it: changes in the translation page template will be reflected and outdated translations will highlighted with a pink background.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">On the contrary, the translation interface is updated immediately.</span>

'''Зьмены.''' Удзельнікі могуць працягваць унясеньня зьмяненьняў у крынічную перакладальную старонку. Зьмены будуць бачныя наведнікам старонкі крынічнай мовай, але гэтыя пераклады робяцца ва ўжо існых адзінках перакладу, узятых з апошняй вэрсіі перакладальнай старонкі, пазначанай для перакладу: перакладзеныя старонкі будуць лічыцца перакладзенымі на 100 %, калі перакладзеныя ўсе адзінкі перакладу, нават калі крынічная старонка мае новыя зьмены. Пабачыць, ці існуюць непазначаныя для перакладу зьмены, можна вельмі проста на перакладальнай старонцы крынічнай мовай: уверсе старонкі будзе паведамленьне пра тое, што гэтую старонку можна перакласьці, а таксама пра наяўнасьць спасылкі на няўлічаныя зьмены.

<span lang="en" dir="ltr" class="mw-content-ltr">'''Invalidation'''. If changes are made to the translatable page source, the translation administrator will be given the option to "{{int|tpt-action-nofuzzy}}" for each section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If a section is invalidated, then the translated languages will get a pink background color for those sections, and a clock icon will be shown to translators in the translation interface.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If a section is not invalidated, then no changes will be visible to readers of the translated pages, and translators will have to examine the section within the translation interface in order to see the changes.</span>

'''Крынічная мова'''. Існуе таксама старонка перакладу з кодам мовы, які адпавядае коду мовы арыгінальнай старонкі: гэтая старонка ня мае дадатковых цэтлікаў ды іншай разьметкі, патрэбнай для перакладу, якія мае арыгінальная старонка. На гэтую старонку адсутнічае спасылка з інтэрфэйсу, аднак яна зручная ў якасьці прыкладу, калі вам патрэбна спаслацца на старонку (звычайна ў перакладальных шаблёнах) ці пры экспарце.
Прыкладам, старонка, на якой вы знаходзіцеся, без разьметкі даступная на [[Help:Extension:Translate/Page translation administration/en]].

'''Зьмяненьне крынічнай мовы'''. Пашырэньне стандартна лічыць, што мова перакладальнай крынічнай старонкі адпавядае дапомнай мове вікіпраекту. Адміністратары могуць зьмяніць мову на старонцы Special:PageLanguage, каб яна стала дапомнай мовай перакладу. Падрабязьней глядзіце [[Special:MyLanguage/Manual:Language#Page content language|мову зьместу старонкі]].

'''Мова перакладу'''. Перакладзеныя старонкі могуць мець тэкст некалькімі мовамі, калі яны не перакладзеныя цалкам.
На перакладзеных старонках неперакладзены тэкст будзе выведзены адпаведнай мовай і напрамкам тэксту, каб правільна працавалі правілы CSS.
Аднак MediaWiki цяпер не дазваляе заданьне іншай мовы для разбору старонкі іншым чынам, акрамя на ўзроўні старонкі.
Усе магічныя словы і функцыі разбору тэксту выкарыстоўваюць мову перакладзенай старонкі, нават калі вакольны тэкст не перакладзены.
Гэта можа спрычыніць непажаданае разыходжаньне, напрыклад, пры фарматаваньні лікаў ці датаў.
Некаторыя магічныя функцыі і тэгі разбору тэксту дазваляюць заданьне выходнай мовы; у такім разе можна скарыстацца магічным словам <code><nowiki>{{</nowiki>[[#TRANSLATIONLANGUAGE|TRANSLATIONLANGUAGE]]<nowiki>}}</nowiki></code>, якое вяртае альбо крынічную мову для неперакладзеных адзінак, альбо крынічную мову для перакладзеных адзінак.

<span lang="en" dir="ltr" class="mw-content-ltr">'''Closed translation requests'''. Some translatable pages have a content that is only interesting for a certain period of time. For example announcements and regular status updates, like the Wikimedia monthly highlights. You can keep those pages around with translations, but hide them from the translation interface. This does not prevent further translations to the pages, but it greatly reduces the chance that a user accidentally starts translating the page. Discouraging and its reversion are done from Special:PageTranslation.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Prioritizing languages'''. You can also define a list of languages that you specifically want translations into; leaving the language list empty is interpreted as all languages allowed. The page will behave like a discouraged page (see previous paragraph) for the languages not in the priority list and, when translating into them, translators will be given a notice. You can also prevent the translation in other languages, say if translations are actually used elsewhere and you won't be able to use them but in some languages.</span> 

<span lang="en" dir="ltr" class="mw-content-ltr">'''Grouping.'''</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is possible to group related pages together.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">These groups work like all the other message groups.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">They have their own statistics and contain all the messages of the subgroups: in this case translatable pages.</span>
Цяпер гэты функцыянал знаходзіцца ў Special:AggregateGroups.
<span lang="en" dir="ltr" class="mw-content-ltr">Aggregate message groups are collapsed by default in Special:LanguageStats in the group selector at Special:Translate.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Moving'''. You can move translatable pages as you would move any other page. When moving you can choose whether you want to move any non-translation subpages too. The move uses a background job to move the many related pages. While the move is in progress, it is not possible to translate the page. Completion is noted in the page translation log.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Deleting'''. Like move, deletion is accessed from the normal place. You can [[Special:PageTranslationDeletePage|delete]] either the whole translatable page, or just one translation page, from the delete button on it. Deletion will also delete all the related translation unit pages. As in move, a background process will delete the pages over time and completion is noted in the page translation log. Deletion requires "delete" and "pagetranslation" permission, but individual translation unit pages can always be deleted with standard "delete".</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Reverting'''. Similarly, reverting incorrect edits works as usual (including the rollback button): you only have to edit the affected translation unit and the translation page will be updated as well. To find the edit to the translation unit from the edit to the translation page, just click the "{{int|contribslink}}" link for the editor and look for an edit at a similar time. Within the translation system, you can mark an existing translation as outdated by adding <code>!!FUZZY!!</code> at the start of the translation unit's translated message box.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Protecting'''. It is possible to [[Special:MyLanguage/Help:Protected_pages|protect]] the translatable page. Translation pages cannot be protected, nor does the protection of the translatable page extend to them. To prevent further edits to translations, you should add the source language as only priority language and disable translations to other languages, see ''prioritizing languages'' above. Together these two actions effectively prevent changes to both the source page and translation pages with its translation unit pages. It is possible to protect individual translation unit pages, though it is not advisable.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Removal from translation'''. It is also possible to unmark a page for translation. You can use Special:PageTranslation or follow the link in the top of translatable page to remove it from translation. This will remove any structure related to page translation, but leave all the existing pages in place, freely editable. This action is not recommended.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Language aware transclusion'''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is possible to transclude a translatable page into another page as a template.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In such a case, the translatable page will be loaded in the language of the target page if it has been translated to that language.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If that translation does not exist, the translatable page will be loaded in the source language.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This behavior of a translatable page is controlled by the ''Enable translation aware transclusion for this page'' option when marking the page for translation.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">New translatable pages will have this behavior turned on by default.</span>

<span id="Anatomy_of_a_translatable_page"></span>
== Анатомія перакладальнай старонкі ==

<div lang="en" dir="ltr" class="mw-content-ltr">
The translation of a translatable page will produce many pages, which all together compose the translatable page in the broadest sense: their title is determined by the title of the translatable <code>Page</code>:
</div>

* <code><span lang="en" dir="ltr" class="mw-content-ltr">Page</span></code> - <span lang="en" dir="ltr" class="mw-content-ltr">the source page</span>
* <code><span lang="en" dir="ltr" class="mw-content-ltr">Page</span>/&lt;<span lang="en" dir="ltr" class="mw-content-ltr">language code</span>></code> - <span lang="en" dir="ltr" class="mw-content-ltr">the translation pages, plus a copy of the source page without markup</span>
* <code>Translations:Старонка/&lt;ідэнтыфікатар адзінкі перакладу>/&lt;код мовы></code> - усе старонкі адзінак перакладу

<div lang="en" dir="ltr" class="mw-content-ltr">
In addition to this, there are the translation page template and the sources of translation units, extracted from the source page and stored in the database. The system keeps track of which versions of the source page contain translation tags and which version of them have been marked for translation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Every time a translation unit page is updated, the system will also regenerate the corresponding translation page. This will result in two edits. The translation unit page edit is hidden by default in recent changes and can be shown by choosing ''show translations'' from the translation filter. Any action other than editing (like deleting and moving) the translation unit pages will not trigger the regeneration of the corresponding translation page.
</div>

Калі вам патрэбная копія крынічнай старонкі без разьметкі, напр. для капіяваньня ў іншую вікі безь перакладу,

<div lang="en" dir="ltr" class="mw-content-ltr">
* identify the source language code (for English, <kbd>en</kbd>) and visit <code>Page/&lt;language code></code>
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* click the "{{int|vector-view-history}}" button to reach an address like [https://www.mediawiki.org/w/index.php?title=Help:Extension:Translate/Page_translation_administration/en&action=history this] and replace <code>action=history</code> with <code>action=raw</code> in the address bar, press enter
</div>
* <span lang="en" dir="ltr" class="mw-content-ltr">the text will be displayed or saved.</span>

{{anchor|segmentation}}
<span id="Segmentation"></span>
== Сэгмэнтацыя ==

Агульныя прынцыпы:

# <span lang="en" dir="ltr" class="mw-content-ltr">All text intended for translation must be wrapped in {{tag|translate|open}} tags. There can be multiple pairs of tags in one page.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Everything outside those tags will not change in any translation page. This static text, together with the placeholders which mark the place where the translation of each translation unit will be substituted, is called the translation page template.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Too much markup in the text makes it difficult for translators to translate. Use more fine grained placing of {{tag|translate|open}} tags when there are lots of markup.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">The text inside {{tag|translate|open}} tags is split into translation units where there is one or more empty lines between them (two or more newlines).</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Restrictions'''. The page translation feature places some restrictions on the text.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">There should not be any markup that spans over two or more translation units.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In other words, each paragraph should be self-contained.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This is currently not enforced in the software, but violating it will cause invalid rendering of the page, the severity depending on whether MediaWiki itself is able to fix the resulting HTML output or not.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Parsing order'''. Beware, the {{tag|translate|open}} tags work differently from other tags, because they do not go through the parser.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This should not cause problems usually, but may if you are trying something fancy.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In more detail, they are parsed before any other tags like {{tag|pre|open}} or {{tag|source|open}}, except for {{tag|nowiki|open}} which is recognized by the Translate extension.</span>

{{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Before Translate version 2020.10, {{tag|nowiki|open}} was not handled consistently and pages would still appear in Special:PageTranslation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Escape it like "<syntaxhighlight inline lang="html">&lt;translate>...&lt;/translate></syntaxhighlight>" as a workaround.</span>}}

<span lang="en" dir="ltr" class="mw-content-ltr">'''Tag placing'''. If possible, try to put the tags on their own lines, with no empty lines between the content and the tags. Sometimes this is not possible, for example if you want to translate some content surrounded by the markup, but not the markup itself. This is fine too, for example:</span>

{{#tag:syntaxhighlight|
<nowiki>{{</nowiki>Template{{!}}1={{^(}}translate{{)^}}Some localised parameter{{^(}}/translate{{)^}}<nowiki>}}</nowiki>
|lang=html}}

<span lang="en" dir="ltr" class="mw-content-ltr">To make this work, the extension has a simple whitespace handling: whitespace is preserved, except if an opening or closing {{tag|translate|content=}} tag is the only thing on a line. In that case the newline after the opening tag or before the closing tag is eaten. This means that they don't cause extra space in the rendered version of the page.</span>

{{anchor|Variables|tvar|&lt;tvar&gt;|.3Ctvar.3E}}
<span lang="en" dir="ltr" class="mw-content-ltr">'''Variables'''. It is possible to use variables similar to template variables.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The syntax for this is {{tmpl|0=<code class=mw-highlight>{{tag|tvar|plain=1|params={{attr|name|"''name''"}}|content=''$1''}}</code>|contents}} (quotes are optional if the value contains no spaces or any of <code>" ' ` = < ></code>).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">For translators these will show up only as <code>$''name''</code>, and in translation pages will automatically be replaced by the value defined in the translatable page (so they are global "constants" across all its translation pages).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Variables can be used to hide untranslatable content in the middle of a translation unit.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It also works for things like numbers that need to be updated often.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can update the number in all translations by changing the number in the translatable page source and re-marking the page.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You do not need to invalidate translations, because the number is not part of the translation unit pages.</span>

<!-- This can't use <syntaxhighlight>, as it's using custom syntax. -->
{{Note|1=Да вэрсіі Translate 2021.04 сынтакс быў {{tmpl|0=<code class="mw-highlight">{{#tag:span|&lt;|class="p"}}{{#tag:span|tvar|class="nt"}}{{#tag:span|&#124;|class="o"}}{{#tag:span|''name''|class="s"}}{{#tag:span|&gt;|class="p"}}''$1''{{#tag:span|&lt;/&gt;|class="p"}}</code>|contents}} ([[phab:T274881|T274881]]). Гэты сынтаксіс яшчэ падтрымліваецца, але ўжо састарэлы.}}

{{anchor|Comma-separated values}}
<span lang="en" dir="ltr" class="mw-content-ltr">'''Comma-separated values'''. For content such as Graph data, that needs to be parsed by the software as comma-separated values, you should separate the translation units between each comma, so that the translating editors don't use localized commas which will confuse the software.</span>

{{anchor|Plain-text values|nowrap}}
<span lang="en" dir="ltr" class="mw-content-ltr">'''Plain-text values.'''</span>
<span lang="en" dir="ltr" class="mw-content-ltr">To prevent any kind of modification of the translation value, use <code>nowrap</code> attribute like this: {{inline-code|lang=html|{{^(}}translate nowrap{{)^}}...{{^(}}/translate{{)^}}}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">By default outdated and untranslated values are modified in order to support highlighting and language tagging.</span>

{{anchor|markup}}
<span id="Markup_examples"></span>
== Прыклады разьметкі ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Below are listed some alternatives and suggested ways to handle different kinds of wiki markup.
</div>

{| class=wikitable
|- style="visibility:collapse"
| colspan="3" | {{anchor|#translation|.23translation}}
|- id=categories
| '''Катэгорыі'''
| width=40% | Катэгорыі можна дадаваць двума спосабамі: на старонцы шаблёну перакладу ці ў адным з модуляў перакладу.

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have the categories in the translation page template, all translations will end up in the same category.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have categories inside translation units, you should teach the users a naming scheme.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
On the right we show two possible schemes which are independent of the technical means to adopt them.
</div>
|
<span lang="en" dir="ltr" class="mw-content-ltr">'''Translation by adding language suffix''': Category:Cars/fi (recommended)</span>

{{#tag:syntaxhighlight|
[...]
{{^(}}/translate{{)^}}

<nowiki>[[Category:MediaWiki{{#translation:}}]]</nowiki>
|lang="html"}}

* <span lang="en" dir="ltr" class="mw-content-ltr">Category page name not translated (just like the page names).</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">One category for each language.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Page translation could be used for the category itself: the categories would be linked together and the headings would be translated (but not the name of the category in links and such).</span>

'''<span lang="en" dir="ltr" class="mw-content-ltr">No translation</span>''': Category:Cars

* <span lang="en" dir="ltr" class="mw-content-ltr">All translations in same category (good if only few languages, bad if many).</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Category name not translated (can be put as is in the translation template).</span>
|-
| '''Загалоўкі'''
| <span lang="en" dir="ltr" class="mw-content-ltr">Headings should be separated with an empty line. This way someone can quickly translate the table of contents before going into the contents, and an anchor in source language is added on translation pages.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">When tagging headings, it is important to include the heading markup inside the tags and insert a newline between the opening translate tag and the heading markup, or MediaWiki will no longer identify them properly. For example, section editing only works with the recommended mark-up given in the example. The markup also immediately gives translators a context: they are translating a heading.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Additionally, it ensures that linkable anchors are generated for the heading.</span>
|
'''<span lang="en" dir="ltr" class="mw-content-ltr">Wrong:</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">(no newline after {{tag|translate|open}} tag, heading out of translate tags)</span>
{{#tag:syntaxhighlight|
{{=}}= {{^(}}translate{{)^}}Culture{{^(}}/translate{{)^}} ==
|lang="html"}}

'''<span lang="en" dir="ltr" class="mw-content-ltr">Wrong:</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">(no newline)</span>
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}{{#if:1|
{{=}}= Culture ==
}}{{^(}}/translate{{)^}}
|lang="html"}}

'''<span lang="en" dir="ltr" class="mw-content-ltr">Recommended segmentation:</span>'''
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
{{=}}= Culture == 

Lorem ipsum dolor.
{{^(}}/translate{{)^}}
|lang="html"}}

|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Images</span>'''
| <span lang="en" dir="ltr" class="mw-content-ltr">Images that do contain language specific content like text should include the full image syntax in an unit. Other images can only tag the description with optional hint in message documentation of the page after it has been marked.</span>
|
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
<nowiki>[[File:Europe.png|thumb|</nowiki>Map of Europe with capital cities]]
{{^(}}/translate{{)^}}
|lang="html"}}
{{#tag:syntaxhighlight|
<nowiki>[[File:Ball.png|50px|</nowiki>{{^(}}translate{{)^}}Ball icon{{^(}}/translate{{)^}}]]
|lang="html"}}

|-
|'''<span lang="en" dir="ltr" class="mw-content-ltr">Links</span>'''
| <span lang="en" dir="ltr" class="mw-content-ltr">Links can be included in the paragraph they are inside. This allows changing the link label, but also changing the link target to a localized version if one exists.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the target page is (or should be) also translatable, you should link to it by prepending <code>Special:MyLanguage/</code> to its title. Only the link label will need to be translated, because this automatically redirects users to the translation page in their own interface language, as selected for instance via the [[Special:MyLanguage/Extension:UniversalLanguageSelector|UniversalLanguageSelector]]. However, to achieve a constant behavior the syntax must be used for all links.
</div>
|
'''<span lang="en" dir="ltr" class="mw-content-ltr">Internal links:</span>'''
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
Helsinki is capital of [[Finland (country)|Finland]].
{{^(}}/translate{{)^}}
|lang="html"}}

{{anchor|MyLanguage}}
'''<span lang="en" dir="ltr" class="mw-content-ltr">Links to translatable pages:</span>'''
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
It has marvelous beaches with a lot of [[Special:MyLanguage/Seagull|seagulls]].
{{^(}}/translate{{)^}}
|lang="html"}}

'''<span lang="en" dir="ltr" class="mw-content-ltr">External links:</span>'''
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
PHP ([http://php.net website]) is a programming language.
{{^(}}/translate{{)^}}
|lang="html"}}

|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Lists</span>'''
| <span lang="en" dir="ltr" class="mw-content-ltr">Lists can get long, so might want to split them into multiple parts with one item in each unit.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Do so only if the items are sufficiently independent to be translated separately in all languages: don't create "lego messages". For instance, you must avoid to split a single sentence in multiple units, or to separate logically dependent parts which may affect each other (with regard to punctuation or style of the list, for instance).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">To split a list, use {{tag|translate|open}}-tags for each item without including leading asterisks/hashes/semicolons.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Do not insert blank lines as this will break the HTML output.</span>
|
{{#tag:syntaxhighlight|
* {{^(}}translate{{)^}}General principles{{^(}}/translate{{)^}}
* {{^(}}translate{{)^}}Headings{{^(}}/translate{{)^}}
* {{^(}}translate{{)^}}Images{{^(}}/translate{{)^}}
* {{^(}}translate{{)^}}Tables{{^(}}/translate{{)^}}
|lang="html"}}

<span lang="en" dir="ltr" class="mw-content-ltr">or</span>

{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
Please visit:
* our main page
* then the FAQ page.
{{^(}}/translate{{)^}}
|lang="html"}}

|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Numbers</span>'''
| <span lang="en" dir="ltr" class="mw-content-ltr">With numbers and other non-linguistic elements you may want to pull the actual number out of translation and make it a variable. This has multiple benefits:</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You can update the number without invalidating translations.
* Translation memory can work better when the changing number is ignored.
</div>
|
{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
Income this month {{^(}}tvar name=income{{)^}}<nowiki>{{FORMATNUM:3567800}}</nowiki>{{^(}}/tvar{{)^}} EUR
{{^(}}/translate{{)^}}
|lang="html"}}
<span lang="en" dir="ltr" class="mw-content-ltr">Note that this prevents the translators from localising the number by doing currency conversion. The <code>FORMATNUM</code> call makes sure the number is formatted correctly in the target language.</span>

|-
| '''Шаблёны'''
| <span lang="en" dir="ltr" class="mw-content-ltr">Templates have varying functions and purposes, so the best solution depends on what the template is for. If the template is not a part of longer paragraph, it should be left out, unless it has parameters that need to be translated. If the template has no linguistic content itself, you don't need to do anything for the template itself.</span>
| <span lang="en" dir="ltr" class="mw-content-ltr">For an example of templates translated with page translation, see {{ll|Template:Extension-Translate}}. To use this template, you need to have another template similar to {{tl|Translatable navigation template}}, because you cannot include the template by <code><nowiki>{{TemplateName}}</nowiki></code> anymore. This is not ''yet'' provided by the Translate extension itself, but that is in the plans.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Another way is to use the [[Special:MyLanguage/Help:Extension:Translate/Unstructured element translation|unstructured element translation]] to translate the template, but then the language of the template will follow the user's interface language, not the language of the page they are viewing.
</div>

|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Attributes</span>'''
| <span lang="en" dir="ltr" class="mw-content-ltr">By default the Translate extension may wrap outdated translation units to highlight them and untranslated units to set proper language metadata.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In some circumstances the additional markup added by this wrapping is not suitable.</span>
|
{{#tag:syntaxhighlight|
{{^(}}abbr title="{{^(}}translate nowrap{{)^}}Frequently asked questions{{^(}}/translate{{)^}}"{{)^}}{{^(}}translate{{)^}}FAQ{{^(}}/translate{{)^}}{{^(}}/abbr{{)^}}
|lang="html"}}
{{Table-AnchorRow|colspan=3|TRANSLATIONLANGUAGE}}
|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Translation language</span>''' {{introduced-inline|[[phab:rETRA5e8106cdc353|5e8106cdc353]]}}
| <span lang="en" dir="ltr" class="mw-content-ltr">When text is using language-dependent formatting methods, a mismatch may appear for untranslated sections.</span>
<span lang="en" dir="ltr" class="mw-content-ltr"><code><nowiki>{{</nowiki>TRANSLATIONLANGUAGE}}</code> can be used to avoid that.</span>
|
<syntaxhighlight lang="wikitext">
2020-09-15 is {{#time:l|2020-09-15|be-tarask}}
</syntaxhighlight>
<span lang="en" dir="ltr" class="mw-content-ltr">The above input may render as:</span>
* {{#language:en|{{PAGELANGUAGE}}}}: 2020-09-15 is Tuesday.
* {{#language:fi|{{PAGELANGUAGE}}}}: 2020-09-15 on tiistai.

<span lang="en" dir="ltr" class="mw-content-ltr">Without the magic word, untranslated text on a Finnish translation page would render as:</span>
* 2020-09-15 is tiistai
|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Translated page language</span>''' {{introduced-inline|[[phab:rETRA98b6958a2471|98b6958a2471]]}}
| <span lang="en" dir="ltr" class="mw-content-ltr">Translated templates may want to set the language they are actually in (e.g. on a wrapper HTML element). When used outside of {{tag|translate|open}} tags, <code><nowiki>{{</nowiki>TRANSLATIONLANGUAGE}}</code> returns the language of the page it’s directly in (as opposed to the language of the page on which the reader sees it).</span>
| <span lang="en" dir="ltr" class="mw-content-ltr">Suppose <code><nowiki>{{1/en}}</nowiki></code> is transcluded in the page titled <code>2/de</code>.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">If <code>[[Special:MyLanguage/Help:Magic words#PAGELANGUAGE|<nowiki>{{PAGELANGUAGE}}</nowiki>]]</code> is used in the text of <code><nowiki>{{1/en}}</nowiki></code>, it returns <code>de</code>.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">If <code><nowiki>{{</nowiki>TRANSLATIONLANGUAGE}}</code> is used in the text of <code><nowiki>{{1/en}}</nowiki></code> (outside of {{tag|translate|open}} tags), it returns <code>en</code>.</span>
{{Table-AnchorRow|colspan=3|TRANSLATABLEPAGE}}
|-
| '''<span lang="en" dir="ltr" class="mw-content-ltr">Translatable page</span>''' {{introduced-inline|[[phab:rETRAa582f3ad21bd|a582f3ad21bd]]}}
| <span lang="en" dir="ltr" class="mw-content-ltr">It can be used in templates that are transcluded on both translatable and non-translatable pages, and should behave differently depending on whether the page is translatable (e.g. use user language on non-translatable pages).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It returns the title of the translation page (the page other languages are translated from) if a page is translatable (including translated pages), and nothing if the page is not translatable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Similarly to the {{tag|languages|open}} parser tag, it returns nothing if the page contains translation markup but hasn’t been marked for translation yet.</span>
| <syntaxhighlight lang="wikitext">{{#if:{{TRANSLATABLEPAGE}}|{{Some template}}|{{Some template/{{int:lang}}}}}}</syntaxhighlight>
<span lang="en" dir="ltr" class="mw-content-ltr">Assuming {{tmpl|0=<code>Template:$1</code>|Some template}} is a translatable template with language-aware transclusion (see above) enabled, and [[MediaWiki:lang]] and its translations are set up on the given wiki similarly to mediawiki.org, the above code transcludes it in the page language on translatable pages, and in the UI language on other pages.</span>
|}

{{anchor|changes}}
<span id="Changing_the_source_text"></span>
== Зьмена крынічнага тэксту ==

<div lang="en" dir="ltr" class="mw-content-ltr">
General principles:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Avoid changes
* Make the changes as isolated as possible
* Do not add translation unit markers yourself
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">'''Unit markers'''. When a page is marked for translation, the system will update the translatable page source and add unique identifiers, called "unit markers", for each translation unit.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">See example below.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">An example of a unit marker is {{#tag:syntaxhighlight|{{^(}}!--T:1--{{)^}}|lang=html|inline=1}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">These unit markers are crucial for the system, which uses them to track changes to each translation unit.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You should never add unit markers yourself.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The unit markers are always on the line before the unit; or, if it starts with a heading, after the first heading on the same line.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The different placement for headings is needed to keep section editing working as expected.</span>

{{#tag:syntaxhighlight|
{{^(}}translate{{)^}}
== Birds == {{^(}}!--T:1--{{)^}}
Birds are animals which....

{{^(}}!--T:2--{{)^}}
Birds can fly and...
{{^(}}/translate{{)^}}
|lang=html}}

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Changing unit text'''. Changing is the most common operation for translation units. You can fix spelling mistakes, correct grammar or do other changes to the unit. When re-marking the page for translation, you will see the difference in the unit text. The same difference is also shown to translators when they update their translations. For simple spelling fixes and other cases where you don't want the existing translations to be highlighted on the translated pages, you can avoid invalidating them: translators will still see the difference if they ever update the translation for any reason.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Adding new text'''. You can freely add new text inside {{tag|translate|open}} tags. Make sure that there is one empty line between adjacent units, so that the system will see it as a new unit. You can also add {{tag|translate|open}} tags around the new text, if it is not inside existing {{tag|translate|open}} tags. Again, do not add unit markers yourself, the system will do it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Deleting text'''. You can delete whole units. If you do so, also remove the unit marker.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Splitting units'''. You can split existing units by adding an empty line in the middle of a unit, or by placing {{tag|translate|open}} tags so that they split the unit. You can either keep the unit marker with the first unit or remove it altogether. In the first case, translators see the old text when updating the old translation. If you removed the unit marker, both units will behave as if no translation ever existed, after the page is re-marked for translation.
</div>

{| class=wikitable
! <span lang="en" dir="ltr" class="mw-content-ltr">Original state</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Keeping the marker</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Removing the marker</span>
|- style="vertical-align:top"

|
<syntaxhighlight lang=html>
<!--T:1-->
Cat purrs. Dog barks.
</syntaxhighlight>
|
<div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr">
 {{#tag:span|&lt;!--T:1--&gt;|class=c}}
 Cat purrs.
 
 {{#tag:span|&lt;!--T:2--&gt;|class=c}} ''<span lang="en" dir="ltr" class="mw-content-ltr">(Added after remarking)</span>''
 Dog barks.
</div>
|
<div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr">
 {{#tag:span|&lt;!--T:2--&gt;|class=c}} ''<span lang="en" dir="ltr" class="mw-content-ltr">(Added after remarking)</span>''
 Cat purrs.
 
 {{#tag:span|&lt;!--T:3--&gt;|class=c}} ''<span lang="en" dir="ltr" class="mw-content-ltr">(Added after remarking)</span>''
 Dog barks.
</div>
|- style="vertical-align:top"

| <span class="mw-content-ltr" dir="ltr" lang="fi">Kissa kehrää. Koira haukkuu.</span>
| <span class="mw-content-ltr" dir="ltr" lang="fi">Kissa kehrää. Koira haukkuu.</span>

<span class="mw-content-ltr" dir="ltr" lang="en">Dog barks.</span>
| <span class="mw-content-ltr" dir="ltr" lang="en">Cat purrs.</span>

<span class="mw-content-ltr" dir="ltr" lang="en">Dog barks.</span>
|}

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Merging units'''. If you merge units, you have to remove at least all but one unit marker.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Moving units'''. You can move units around without invalidating translations: just move the unit marker together with the rest of the unit.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Before marking the new version of the page for translation, ensure that the best practices are followed, especially that translators get a new translation unit if the content has changed. Also make sure that there are no unnecessary changes to prevent wasting translators' time. If the source page is getting many changes, it may be worthwhile to wait for it to stabilize, and push the work for translators only after that.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Unused unit translations are not deleted automatically, but that should not cause trouble.
</div>

{{anchor|migration}}
<span id="Migrating_to_page_translation"></span>
== Міграцыя на пераклад старонкі ==

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have been translating pages before using the page translation system, you might want to migrate the pages to the new system, at least the ones you expect to have new translations and want statistics for. You will probably have existing templates for language switching and maybe different page naming conventions.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can start migration by cleaning up, tagging and marking the source page. You can keep the existing language-switching templates while you migrate the old translations. If your pages follow the language code subpages naming convention, they will be replaced with the source text after marking the source page for translation, but you'll still be able to access translations from history.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This manual task has been partly automated by [[Special:PageMigration]] (available to translation administrators only), which shows the source and target units besides each other and allows the user to adjust the units by providing a set of features mentioned later in this page.
</div>

<span id="How_to_use?"></span>
=== Як карыстацца? ===
[[{{LM|Page migration screenshot|png}}|thumb|500px|Здымак экрану з прыкладам выкарыстаньня Special:PageMigration для „Help:Special pages“ ў якасьці назвы старонкі і „fr“ ў якасьці коду мовы.]]
# <span lang="en" dir="ltr" class="mw-content-ltr">Go to [[Special:PageMigration]]</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Enter the title of the page and the language code. For example, "Help:Special pages" & "fr"</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">The source text which was divided into units by Translate and the imported translations will be shown besides each other with some initial alignment.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Use the [[#actions|actions available]] for each unit to manually do the remaining alignment</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">As translated units are editable, do required manual improvements (for add translation variables, fix links and markup, etc.)</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Click on the "{{int|pm-savepages-button-label}}" button. This will create pages under the Translations namespace of the form <code>Translations:Page/&lt;translation unit identifier>/&lt;language code></code>. The old translations have been imported into Translate.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Else, if you wish to abort the importing, click on the 'Cancel' button.</span>

{{anchor|actions}}
<span id="Actions_available"></span>
=== Даступныя дзеяньні ===

<div lang="en" dir="ltr" class="mw-content-ltr">
Each row consisting of source and target unit has a set of action icons. They are used as follows:
</div>

# <span lang="en" dir="ltr" class="mw-content-ltr">'''Add''': Clicking on this action icon adds a new empty unit below the current one. Use this feature if you want to split the current unit and need a unit below.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">'''Swap''': Clicking on this action icon swaps the content of the current unit with the unit below it. You can use this feature when the units get aligned improperly due to different ordering of sections. Or when you need to drag a unit below or above. In either case, remember it swaps with the unit ''below'' and does not create any additional units.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">'''Delete''': Clicking on this action icon completely removes the corresponding target unit from the page and shifts the remaining target units up by one unit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use this to remove unwanted content like code or imported translations which are present completely in the source language.</span> <span lang="en" dir="ltr" class="mw-content-ltr">''Note:'' this irrevocable action (in the current session).</span>

<span id="Troubleshooting"></span>
=== Разьвязаньне праблемаў ===
# <span lang="en" dir="ltr" class="mw-content-ltr">If you mark a page for translation and immediately go to the special page and try to import translations, you may get an error message like "{{tmpl|0={{int|pm-old-translations-missing|&lt;$1>/&lt;$2>}}|page-name|language-name}}". This is because FuzzyBot didn't fuzzy the messages on the old page yet: the tool won't find an edit by FuzzyBot on the translation page. In this case, simply wait for FuzzyBot to do its job. Once an edit is seen, you can proceed with the imports.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Please wait for some time after pressing the "{{int|pm-savepages-button-label}}" button. While the button background remains gray, there is an ongoing process of importing non-empty units. Once the button becomes colored again, the import is completed.</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Within the translation system, you can mark an existing translation as outdated by adding <code>!!FUZZY!!</code> at the start of the translation unit's translated message box.</span>

<span id="Tips"></span>
=== Парады ===
# <span lang="en" dir="ltr" class="mw-content-ltr">Migration will be easier if you first (before the mark to translation) check whether existing translations are similar to the original English text, and manually edit the structure of pages: break paragraphs and lists, add the missing headings (even if empty).</span>
# <span lang="en" dir="ltr" class="mw-content-ltr">Will be useful to check the result in the core translation interface - some of the units may be immediately marked as obsolete because of errors markup or if not all of the translation variables was added.</span>
# Пераклад назвы старонкі трэба дадаваць уручную. Калі вы ня надта добра валодаеце мовай імпартаванай старонкі, можаце паспрабаваць пашукаць пераклад назвы старонкі ў „спасылках сюды“ ці дзе-небудзь у перанакіраваньнях.

[[Category:Extension:Translate{{#translation:}}|Page translation administration]]