Help:Templates/ja

複数のページに含めたい共通するようなテキストがある場合、MediaWiki のテンプレート機能が役立ちます. Unlike extensions and media files, there is no central repository for templates. Templates can be newly written or to save duplicating work already done, exported from another wiki e.g. Wikipedia, and then imported into the target wiki.

作成
Templates are standard wiki pages whose content is designed to be transcluded (embedded) inside other pages. Templates follow a convention that the name is prefixed with " ", assigning it to that namespace; besides this, you can create them like any other wiki page.

The simplest use of templates is as follows. If you create a page called "Template:Welcome" with contents:

こんにちは! ウィキへようこそ.

you'll have created your first template! If you then insert the code:

in any other page, when that page is viewed the text "Hello! Welcome to the wiki." will appear instead of. The template content is "transcluded" into the other page, i.e. it is integrated in the page.

You can then insert  at any point of any page where you wish to welcome someone. Suppose it is used in 100 pages. If you then change the template contents to:

Hi there! Welcome to this wonderful wiki.

and revisit any of the 100 pages where the template was used, you'll see the new text instead of the original one. In this way, you have changed the content of 100 pages without editing them, because the template is transcluded into these pages.

This is the basic mechanism. There are several additional features of transclusion that enrich this mechanism and make templates very useful.

使用
テンプレートは、他のページ内で以下のように使用できます:


 * — as described above, this link will be dynamically replaced by the current content of Template:Name at the time the page with the template link is loaded. The link will remain unchanged in the page's source.
 * — when this template link is used, it will be replaced once and for all with the content of Template:Name as of the time the page with the link is saved: a copy of the contents of Template:Name will be substituted for the template link. The contents are then a part of the including page, and can be edited normally, separately from the original. Note: later changes to the source template page will not be propagated to the page with the template link.
 * — this was introduced to allow for substitution that doesn't break transclusion, see w:en:Help:Substitution.
 * は、それを含むページが取得されるときに、 のように生のwiki構文として表示する形式でテンプレートを埋め込みます.

In fact, an ordinary wiki page can also be used as a template, simply by specifying the namespace it resides in, so:


 * は  を参照読み込みします
 * は  を参照読み込みします
 * は  を参照読み込みします
 * replaces itself with the contents of

If no such namespace exists, the full title is assumed to be a template:


 * includes

パラメーター
参照読み込みの機能を豊富にするために、MediaWikiはそれが参照読み込みされたときにテンプレートにパラメーターを渡せます. パラメーターによって、テンプレートからさまざまな異なるコンテンツを生成したり、異なる挙動をさせられます.

ちょっとした感謝の言葉を他の利用者のトークページに挿入したい場合は、

The thank you note は、その理由(このケースでは"all your effort")と署名("Me")を持つことになります. あなたの目的は、すべてのユーザーが理由の如何を問わず、他のユーザーに感謝することができるということです.

これによって、たとえばTemplate:Thankyouというテンプレートを定義して使うことで、どの場所でも同じ記述ができるようになります. しかし、ユーザーが誰かに感謝する記述は同じでも、具体的な内容(理由や署名)は違います. このため、それらをパラメータとして渡す必要があります. もしボックスの書式を設定するために残りの要素を無視して画像を配置する場合、テンプレートの主たる記述は、次のようになります:

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:

以下のような出力がなされます:

Note: identifying parameters by order (with, etc) works only with anonymous parameters. If your page identifies any parameter by number or name, as shown below, this method will no longer be available to the template which receives them.

Note: If an equal sign appears inside an anonymous template parameter, it may be interpreted as a named parameter, treating the text before the equal sign as the parameter name and the text after it as the value. This is a common problem when you need to include an external link, or an HTML element with attributes (see Task 16235) The workaround is to use named parameters instead, or even numbered parameters as explained in the following section.

数値のパラメーター
数値によるパラメーターの場合は、パラメーターの値により、識別されます:

この時、template  は、パラメーターの値が1ならば  、2ならば 、と設定されており、パラメーター指定は数値の降順で書きます. 結果、以下のような出力となります.

名前のパラメーター
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:

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 them, in this way:

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

Since no parameters 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 parameter   is provided, then the value   will be used. Similarly,, defaults parameter   to value. Now, transcluding the template again without passing any parameter, results in the following:

Order of evaluation
Template parameters are fully evaluated before they are passed to the template. So if one of your parameters is a call to another template, what is actually passed is the expanded parameter.

becomes before it becomes:

In a few circumstances, this order of evaluation makes a difference from the alternative. (The alternative being to check the results of the template call to see if there are additional templates to be expanded.)

First, the name of the template can be expanded at the same time and in the same way as the parameters.

Thus might expand to So that a template called  could display the thank you in the preferred language (however that was determined.)

Secondly, the template being called can't construct a template from pieces to be called later. A template that took the form would not work if was and was.

Thirdly, the parameter being passed is expanded only once, rather than every place the parameter is used in the template. This is more efficient on the mediawiki server.

Finally, the template being called can't stop the parameter from being expanded altogether. Even if a template only uses a parameter in some circumstances, it will always have been expanded before the call was made.

テンプレートの参照読み込みの制御
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.

と の間にあるものはページが直接閲覧されるときのみ表示され、インクルードされる場合は表示されません. 実行できる応用例は次の通りです:


 * テンプレート自身をカテゴリ化する際に使用するカテゴリ
 * 他言語版の類似したテンプレートへの言語間リンク
 * テンプレートの使用法についての説明文

逆は .です. と の間のテキストはページがインクルードされたときのみ処理され表示されます. 明確な応用例は与えられたテンプレートを含むすべてのページをカテゴリに追加することです.


 * 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.

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

テンプレートの整理
テンプレートを効率的にするために、ユーザがそれらを見つけ利用できることが必要です.

以下の方法で見つけられます:
 * 1)  > 'をクリック
 * 2) '一覧で、Template を選択して'

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

Usage
Welcome users:

それから編集者は同じようなページを作成するために例をコピー＆ペーストします.

Linking to a template
To link to a template instead of including it, use the tl template. The name of the template the editor wants to link to goes after the vertical pipe. 例: links to the navbar template.

別のウィキへのコピー
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.

MediaWiki のコード
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:
 * 2) * 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.
 * 3) * ボックス「」にチェックを入れる.
 * 4) * ボックス「」のチェックを外す.
 * 5) * 「」をクリック.
 * 6) 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. 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.

After sucessfully 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. 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 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.
 * 2) 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.

注記
An experiment shows that if you include a template in itself, it won't put MediaWiki into an infinite recursion. MediaWiki will find out, and stop with the template's name in bold. For example, if the content of "Template:Aaaa" is " ", it'll show as "Template:Aaaa".

関連項目

 * – 特殊なテンプレートの例
 * – fancy stuff you may find in some templates
 * m:Help:Template – contains a 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 variables
 * m:Help:Embed page – embedding pages from namespaces other than.
 * Importing Wikipedia infoboxes tutorial
 * m:Help:Embed page – embedding pages from namespaces other than.
 * Importing Wikipedia infoboxes tutorial