Help:Templates/be-tarask

Калі Вы маеце стандартны тэкст, які трэба зьмясьціць на некалькі старонак, на дапамогу прыходзяць шаблёны МэдыяВікі. У адрозьненьне ад дапаўненьняў і мэдыяфайлаў, для шаблёнаў няма адмысловага сховішча. Шаблёны могуць быць створаныя з нуля ці скапіюванага з паўторнага тэксту, перанесеныя зь іншай вікі, напрыклад, Вікіпэдыі, пасьля чаго імпартаваныя ў мэтавую вікі.

Стварэньне
Шаблёны — гэта стандартныя вікі-старонкі, зьмест які створаны дзеля ўключэньня (ўбудаваньня) ў іншыя старонкі. Пагадненьне па назвах шаблёнаў раіць пачынаць іх з " ", што дадае іх у адпаведную прастору назваў; апроч гэтага, Вы можаце ствараць іх як любую іншую старонку.

Вось найпрасьцейшы спосаб выкарыстаньня шаблёнаў. Калі Вы ствараеце старонку з назвай «Шаблён:Вітаем» і зьместам:

Вітаем! Запрашаем у Вікіпэдыю.

дык Вы стварылі свой першы шаблён! Калі пасьля гэтага Вы ўставілі код:

на якую-небудзь іншую старонку, пры ейным праглядзе Вы ўбачыце тэкст «Вітаем! Запрашаем у Вікіпэдыю.» замест. Зьмест шаблёну «перадаецца» на іншую старонку, то бок ён уключаны ў яе.

Цяпер Вы можаце ўставіць  у любое месца старонкі, дзе хочаце яго вывесьці. Уявіце, што ён выкарыстоўваецца на 100 старонках. Калі пасьля Вы зьменіце зьмест шаблёну на:

Прывітаньне! Запрашаем у гэтую дзівосную вікі.

і зазірнеце на ўсе гэтыя 100 старонак, дык пабачыце на іх новы тэкст замест першапачатковага. Такім чынам, Вы зьмянілі зьмест 100 старонак, не рэдагуючы іх, проста зьмяніўшы перададзены ў іх шаблён.

Гэта асноўны мэханізм. Ёсьць яшчэ некалькі дадатковых можнасьцяў, якія ўзбагачаюць гэты мэханізм і робяць шаблёны вельмі патрэбнымі.

Выкарыстаньне
Шаблёны можна ўстаўляць на іншыя старонкі наступнымі спосабамі:

Because the template call remains in the pages's source, any subsequent change to Template:Name will be seen on the page containing the template call. Also, the page will be listed among those that "link to" the template. That is, a copy of the contents of Template:Name will be substituted for the template call. No link is maintained between the page and the template, so each can be edited further without affecting the other. In effect, there is little difference between substituting the content in this way and simply typing it into the page's source "manually". See for more information.
 * — як апісана вышэй, гэтая спасылка будзе дынамічна замененая на актуальны зьмест Шаблён:Назва ў той момант, калі загружаецца старонка з шаблёнам. У кодзе старонкі спасылка застанецца нязьменнай.
 * — калі ўжытая такая спасылка на шаблён, яна будзе замененая аднойчы на ўвесь зьмест Шаблён:Назва ў момант, калі захоўваецца старонка са спасылкай: копія зьместу Шаблён:Назва будзе падстаўлены замест спасылкі на шаблён. Ягоны зьмест становіцца неад'емнай часткай мэтавай старонкі і можа быць рэдагаваны звычайна, асобна ад арыгіналу. Заўвага: наступныя зьмены ў зьмесьце шаблёны не адлюструюцца на старонцы са спасылкай на шаблён.
 * — быў уведзены, каб дазволіць падстаноўку, якая не зьмяняе ўключэньне, глядзіце w:en:Help:Substitution.
 * ўключае шаблён у форме, якая адлюстроўвае яго ў выглядзе сырой вікі-разьметкі (як гэта робіць ) пры выкліку старонкі, якая яго ўтрымлівае.

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


 * ўлучае
 * ўлучае
 * ўлючае
 * замяняе сябе на зьмест

Калі такая прастора назваў адсутнічае, шаблёнам лічыцца поўная назва:


 * ўлучае

Парамэтры
Дзеля ўзбагачэньня мэханізму ўлучэньня МэдыяВікі дазваляе перадаваць у шаблёне парамэтры. Яны дазваляюць шаблёну выдаваць розны зьмест ці выдаваць розныя паводзіны.

Уявім, што Вы хочаце ўставіць невялічкую падзяку на старонцы гутарак іншых удзельнікаў, кшталту:

Нататка з падзякай мецьме прычыну (у дадзеным выпадку — «усе Вашыя намаганьні») і подпіс («Я»). Вашая мэта — каб кожны ўдзельнік быў здольны падзякаваць любому іншаму зь якой-кольвек прычыны.

So that the note will look similar everywhere it is used, you can define a template called, for example. Although the note should look similar whenever a user thanks another user, its specific contents (i.e. the reason and the signature) will be different. For that reason, you should pass them as parameters. If we ignore the remaining elements to format the box and place the image, the core content of the template will be this:

Notice the use of  and. This is the way to identify, within templates, the parameters that will be passed in when the template is used. Note that, within the template, each parameter is surrounded by three braces:. This is different from normal template name usage.

When using the template on a page, you fill in the parameter values, separated by a "pipe" character. MediaWiki allows parameters to be passed to the template in three ways: Anonymously, Numbered, and Named.



Ананімныя парамэтры
To pass in anonymous parameters, list the values of those parameters sequentially:

In this case, the  template receives parameters   and , producing:

The order in which anonymous parameters are passed in is crucial to its behavior. Reversing the order of the parameters, like so:

would produce this result:



Нумараваныя парамэтры
To pass in parameters by number, identify each parameter when passing it:

This time, template  receives parameters   and , though they have been supplied in inverse order, and produces:


 * Examples:

produces:



Пайменаваныя парамэтры
The third way of passing parameters is by name instead of numbers. In this case, the template contents would be changed to:

A little thank you... for. hugs,

Within the template, we use  and   to identify each parameter, instead of a number. To pass these parameters by name, identify each parameter when passing it:

In this case, template  receives parameters   and   and produces:

Named parameters are case-sensitive, so:

produces:

The advantage of using named parameters in your template, besides also being flexible in the order parameters can be passed, is that it makes the template code much easier to understand if there are many parameters.



Дапомныя значэньні
If you transclude a template that expects parameters, but do not provide their arguments, in this way:

in the numbered parameters example above you would get the following:

Since no arguments were passed in, the template presents the parameters themselves, instead of their respective values. In these cases, it may be useful to define default values for the parameters, i.e. values that will be used if no value is passed in. For example, if the template contents are changed to:

then  defines that if no argument is provided for parameter , then the value   will be used. Similarly,, defaults parameter   to value. Now, transcluding the template again without passing any argument results in the following:

Often default values are used to specify alternate names of parameters. For example, if you have, the template will first look for a parameter named "a". If it is not set, it will use the parameter named "b". If neither "a" nor "b" is set, it will output nothing.

Evaluation
Generally speaking, template parameters are substituted into the template after tokenization, but as is. They are not evaluated until they are used.

This has a few consequences. First of all, if you have a  containing , and a   containing  , and put   on a page, mytemplate isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.

The second consequence of this is dead-code elimination. If you make a template call like, and Template:Foo does not contain  , then the displaytitle is not used, since it is only evaluated when needed, and there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using Extension:ParserFunctions, and can be especially noticed when used in combination with the  magic word that varies by user language.

Template calls starting with the magic word  or   are evaluated in a separate first pass that only happens at save time, along with ~ and links using the pipe trick. If they cannot be evaluated during the first pass,  calls are ignored, and   are treated as if a normal template.

Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker". This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.

Recursion in templates
Including a template in itself won't throw MediaWiki into infinite recursion. MediaWiki will stop the recursion with the template's name in bold. For example, if the content of Template:Aaaa is, it'll display "a a Template loop detected:  Template:Aaaa z z".

Forbidden idiom
This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example  can either be called   or. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path.



If  is modified to recurse into   and   is an identical manual copy of   this idiom works fine as the self-recursion safeguard operates dynamically and not statically.

A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner.

If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour.

Tables in parameters
Since the pipe character and equality sign  have different meanings in template calls and wikitables, in order to use table markup in the value of a template parameter one generally needs to "escape" those characters (i.e., protect them from interpretation as template markup) using special sequences:


 * the built-in   provides an "escaped" version of   since MediaWiki 1.24
 * the built-in magic word  provides an "escaped" version of   since MediaWiki 1.39

Before the introduction of these magic words, many wikis used templates to accomplish the same things. On such a wiki, the magic words take precendence over the same-named templates.

Example table
 Table code: 

 Escaped table code: 

Note that the first left-brace is interpreted as a literal left-brace character because it is immediately followed by the   magic word. Similarly, the last right-brace is interpreted as a literal right-brace character because it is immediately preceeded by the same magic word. However, in some cases these brace characters do cause problems, so some wikis provide templates for escaping these characters, as well:


 * the template call  might provide an "escaped" version of
 * the template call  might provide an "escaped" version of

Some wikis go even further and provide other convenience templates like and. On such a wiki, the code can be simplified a bit to this form:



Кантроль уключэньня шаблёну
By default, a template's content is displayed in its entirety, both when viewed directly and when included in another page. However, you can control which parts of a template will be seen and included by the use of the, and  tags.

Anything between and  will be seen only when the template's page is being viewed directly, but not when it is included in another page. This is useful when you want to include text or code in a template that you do not want to propagate to any pages which include it, such as:


 * Category links when categorizing the template itself
 * interlanguage links to similar templates in other languages
 * Explanatory text about how to use the template

Likewise, anything between and  will be processed and displayed only when the page is being included, but not when the template page is being viewed directly, and is useful in situations such as:


 * Categorizing pages which include the template. Note: when changing the categories applied by a template in this fashion, the categorization of the pages which include that template may not be updated until some time later: this is handled by the . To force the re-categorization of a particular page, open that page for editing and save it without changes.
 * Ensuring that the template's code is not executed when viewing the template page itself. Typically this is because it expects parameters, and its execution without parameters has an undesired result.

Everything outside and  is processed and displayed normally; that is, both when the template page is being viewed directly and when the template is included in another page. The focus is on what is inside these two tags.

Everything outside tags is discarded in the transclusion. Even sections tagged includeonly are discarded in the transclusion unless they are also tagged as onlyinclude. The focus is on what is outside this tag.

Nesting of these tags is also possible.

The three partial transclusion tags enable all possible combinations of what is processed and rendered. Comments also fill a role.



Парадкаваньне шаблёнаў
For templates to be effective, users need to find them, and find out how to use them.

To find them, users can:
 * 1) Click ' > '
 * 2) In the ' list, choose Template and click '.

To give usage information, include an example like this one on the template page:

Usage
Welcome users:

Then, an editor can simply copy and paste the example to use the template.

While editing a page, a list of all templates used is available under the editing form, in a collapsible section titled "" (also named "", or "" depending on the context). This list provides a convenient link to the template's page, as well as information about its protection status. Redirected templates are shown in italics, with the redirect target added as a separate list item.



Спасылкі на шаблён
A template page can be linked to like any other wiki page. For example, the link Template:Navbar is generated using the wikicode.

On many wikis, Template:Tl can be used to provide a link to a template formatted in a way that shows the "double curly-braces" wikicode necessary to transclude the template without actually doing the tranclusion. For example, the code  may be used to create the link Navbar.

This construct is commonly used when referring to templates in template documentation, on help pages, and on talk pages. The same effect can be achieved by using, but the   approach involves much less typing. On any given wiki the Tl template, if it exists, may or may not render the text in a "code" element or as monospace type. If not (as on this wiki), another similarly named template may do so. See, for example, the "See also" section of our Template:Tl documentation.



Капіяваньне з аднае вікі ў іншую
Templates often require CSS or other templates, so users frequently have trouble copying templates from one wiki to another. The steps below should work for most templates.



Код МэдыяВікі
If you have import rights (specifically importupload) on the new wiki:


 * 1) Go to Special:Export on the original wiki, and download an .xml file with the complete history of all necessary templates, as follows:
 * 1) * Enter the name of the template in the big text box, e.g. "Template:Welcome". Pay special attention to capitalization and special characters — if the template name isn't exactly correct, the export may still occur but the .xml file will not have the expected data.
 * 1) * Select the box "".
 * 1) * Select the box "".
 * 1) * Click "".
 * 1) Go to Special:Import on the new wiki and upload the .xml file.

If you don't have import rights on the new wiki:


 * 1) Go to the template you want to copy from the original wiki. Go to the edit page, and copy all the wikitext
 * 2) On the new wiki, go to the page with the same name as the template you copied. Hit create/edit and paste the wikitext you copied. In the edit summary of each template, link to the original page for attribution.
 * 3) Back in the original wiki at the edit window, below the edit box, look at the list of "Templates used on this page". For each template listed follow these instructions. Also do that for any template used by any of these templates, and so on.

This will copy the entire code necessary, and will suffice for some templates. Note that only page elements parsed in rendering the page get exported, consequently documentation subpages are not exported as part of this process. If it doesn't work also check for red links listed under "Pages transcluded onto the current version of this page:", below the edit box. If there are any repeat the above steps for these as well and also copy the code in the modules.

After successfully importing the template and all its linked templates from the other wiki, edit it to change customisations to suit your wiki. For example to change a logo, remove redundant categories or red links.

Пашырэньні
An extension often used in templates is ParserFunctions. Visit page and check if any of the functions listed there are used in the templates you've copied. If so, you have to install the extension. To install it, you'll need system admin access to the server of your MediaWiki installation.

Another dependency that may be used in templates, especially those on Wikipedia, is Lua. Having   in template code is a good sign for it. In case it's used, you need to install the extension and system admin access is required too. See that page for more instructions about installing and using the extension.



CSS і JavaScript
Besides MediaWiki code, many templates make use of CSS and some rely on JavaScript to work fully. If the copied templates are not behaving as expected, this may be the cause. To copy the required CSS and JavaScript to your wiki you'll normally need to have admin privileges, because you'll be editing system messages in the "MediaWiki:" namespace.


 * 1) Look for the use of CSS classes (text like  ) in the template text. If those classes appear in "MediaWiki:Common.css" or "MediaWiki:Monobook.css" on the original wiki, copy those classes to "MediaWiki:Common.css" on the new wiki and check if the template is now fine.
 * 1) If the copied template is still not working as expected, check if there is code in "MediaWiki:Common.js" or "MediaWiki:Monobook.js" on the original wiki. If so, you can try copying it to "MediaWiki:Common.js" on the new wiki. Normally, it is a good idea to only copy code from trusted sources, and first browsing the code to identify and select the parts that are relevant. You may find comments that can serve as clues to identify the functionality of each part.



General template usage

 * w:Help:Template – a little more detail than here
 * m:Help:Template – much more thorough manual on how exactly templates function
 * m:Help:Advanced templates – describes even more advanced techniques such as dynamic template calls and variable parameter names

Special constructs used in templates

 * – fancy stuff you may find in some templates
 * – additional fancy control functions such as #if and #switch
 * – guidance on using parser functions in templates

Other relevant information

 * – a template special use case example
 * – Using templates as the starting text of a page
 * – embedding pages from namespaces other than
 * – Using templates as the starting text of a page
 * – embedding pages from namespaces other than
 * – embedding pages from namespaces other than