Help:Templates/ko

여러 문서에 포함할 기본 글이 있다면, 미디어위키 틀 기능이 유용하게 쓰입니다. 확장 도구나 미디어 파일과는 다르게 틀에는 중앙 저장소가 없습니다. 틀은 새로 작성하거나, 또는 기존의 작업을 위키피디어와 같은 다른 위키에서 복사하여 목적하는 위키로 불러올 수 있습니다.

만들기
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.

틀을 사용하는 가장 쉬운 방법은 다음과 같다. 당신이 만약 "틀:환영합니다."이라는 페이지를 아래와 같은 내용과 함께 만든다면:

안녕하세요! 위키에 오신 것을 환영합니다.

새로운 템플릿을 만들었다! 이제 아래와 같이 코드를 입력하면:

그 모든 페이지에서 "안녕하세요! 위키에 오신 것을 환영합니다."가  대신 보여진다. 틀의 내용은 다른 페이지에 "포함(transclude: transfer + include)"된다.

이제 다른 사람을 환영하고 싶은 어느 페이지의 어느 부분에나 를 입력하면 된다. 예를 들어 100개의 페이지에서 사용되었다고 치자. 만약 틀의 내용을 다음과 바꾼다면:

안녕하세요! 경이로운 위키에 오신 것을 환영합니다.

그리고 그 틀이 사용된 100개의 페이지를 다시 접속해보면, 기존의 내용이 아닌 새로 작성한 내용을 볼 수 있다. 이 방법을 이용하여 100개 페이지의 내용을 일일이 고치지 않을 수 있다.

이것이 틀의 기본 원리다. 또한 틀을 좀 더 활용할 수 있는 추가적인 기능이 있다.

사용
틀 역시 하나의 위키 문서이며, 세 가지 방법으로 다른 위키 문서에서 사용될 수 있다.


 * 은 이 코드를 포함하고 있는 문서를 웹 브라우저로 열 때, "틀:이름" 문서의 내용을 그 위치에 포함시킨다. (즉, 항상 최신의 "틀:이름" 문서의 내용을 포함하게 된다.)
 * — 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.
 * 은 와 동일하지만,  를 사용한 것 처럼 위키 문서 문법을 처리하지 않고 문서를 포함시킨다.

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


 * includes
 * includes
 * includes
 * replaces itself with the contents of

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


 * includes

변수
To enrich the mechanism of transclusion, MediaWiki allows parameters to be passed to a template when it is transcluded. Parameters allow the template to produce different contents or have different behaviors.

Suppose you wish to insert a little thank you note in the talk page of other users, such as:

The thank you note will have a reason (in this case, "all your effort") and a signature ("Me"). Your objective is that any user be able to thank any other user, for any reason whatsoever.

So that the note will look similar everywhere it is used, you can define a template called Template:Thankyou, 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:

Note: Identifying parameters by order (with, etc) works only with anonymous parameters. Any parameters identified by name, as shown below, will not be accessible to the template using ordinal numbers.

Note: If an equal sign appears inside the argument to an anonymous template parameter, that parameter may be misinterpreted as a named parameter (which is explained below in this document) treating the text before the equal sign as the parameter name and the text after it as the argument 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.

수로 지정된 변수
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:

이름으로 지정된 변수
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:

Order of evaluation
With a few exceptions, 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.

Exceptions to the order of evaluation
In a few circumstance template parameters are not evaluated before being passed to the template.

Parameters to a  expansion are not evaluated, but are passed literally.

Some magic words are not evaluated as parameters. Their evaluation is delayed because they have side-effects. For example, would not instead
 * 1) evaluate
 * 2) change the display title of the page and
 * 3) call   with parameter 1 being blank
 * 1)   would not be evaluated (yet)
 * 2)   would be called with parameter 1 being
 * 3) only if   is evaluated in , would the display title of the page be changed.

Which magic words are evaluated late like this has not been fully documented. Known ones include:
 * DISPLAYTITLE

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 show as "Template:Aaaa".

틀 포함 제어하기
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.

와  의 사이에 있는 내용은 그 문서를 직접 접근할 때만 화면에 표시되며, 다른 문서에 포함되어 나타나지는 않는다. 유용하게 사용될 수 있는 경우는 다음과 같다.


 * 틀 분류를 작성할 때
 * interlanguage links to similar templates in other languages
 * 틀 사용 방법과 같은 내용

반대의 역할을 하는 것이 이다. 와  사이의 문자열은 문서가 다른 문서에 포함될 때에만 화면에 나타난다. 간단한 사용예가 틀을 사용하는 모든 문서들은 category에 포함시키면서, 틀은 그 분류에 포함시키지 않는 경우이다.


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

틀 조직하기
틀을 효과적으로 사용되려면, 사용자가 틀을 찾아서, 사용하는 방법을 찾아야 합니다.

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:

그러면, 사용자는 간단히 예제를 복사해서 사용할 수 있게 된다.

틀에 링크걸기
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 in template documentation, on help pages, and on talk pages when referring to templates. The same effect can be achieved by using, but the tl 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, as shown here. If not, another similarly named template may do so. See, for example, the "See also" section of the documentation of en:Template:Tl at the English Wikipedia.

한 위키에서 다른 위키로 복사하기
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:
 * 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) * Check the box "".
 * 4) * Uncheck the box "".
 * 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 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와 자바스크립트 코드
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.

같이 보기

 * – 틀 특수 사용 사례 예
 * – fancy stuff you may find in some templates
 * - additional fancy control functions such as #if and #switch
 * - guidance on using parser functions in 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 parameter names
 * m:Help:Embed page – embedding pages from namespaces other than.
 * A solution to the lack of template bundling has been proposed at Community Wishlist Survey 2019/Miscellaneous/Shared Multilingual Templates and Modules available to all wikis, please support it.
 * A solution to the lack of template bundling has been proposed at Community Wishlist Survey 2019/Miscellaneous/Shared Multilingual Templates and Modules available to all wikis, please support it.
 * A solution to the lack of template bundling has been proposed at Community Wishlist Survey 2019/Miscellaneous/Shared Multilingual Templates and Modules available to all wikis, please support it.
 * A solution to the lack of template bundling has been proposed at Community Wishlist Survey 2019/Miscellaneous/Shared Multilingual Templates and Modules available to all wikis, please support it.
 * A solution to the lack of template bundling has been proposed at Community Wishlist Survey 2019/Miscellaneous/Shared Multilingual Templates and Modules available to all wikis, please support it.