Extension:Header Tabs/ko

Header Tabs extension transforms top-level MediaWiki headers into tabs using the jQuery UI JavaScript library.

문법
To enable tabs on a page after you installed the extension, you need to add a tag into the page in place where the last tab should end (everything below this tag will be shown under the tab view). Most of the time, though, you'll want to put it at the bottom of the page.

In addition to that, the page should have top-level headers defined in it like this: = 헤더 제목 = Each such top-level header, if it's anywhere above the &lt;headertabs/&gt; tag, will be displayed as a tab.

탭을 연결
You can link to a tab, both from another page and from within that same page (and, within that same page, both from another tab and from outside the tab view). This is done using the  parser function, which is called like this:

This will create a link to the tab with the name "Tab name", and the text of the link will read "Link text". If you want the link to a point to a tab on another page, you can optionally add the third parameter, "Page name".

Multibyte characters was well as formatting characters e.g. bold is not permitted if you want to link to tabs in any way.

예제
탭보기 위에있는 일부 텍스트

= 첫 번째 섹션 헤더 = 이것은 첫 번째 탭에 표시됩니다.

= 두 번째 섹션 헤더 = 이것은 두 번째 탭에 표시됩니다.

= 세 번째 섹션 헤더 = 탭보기 아래에 항상 표시됩니다. 왜냐하면 태그 아래에 있기 때문입니다.

머리글 제목은 자동으로 탭 제목으로 변환됩니다.

다운로드
You can download the Header Tabs code, in .zip format, here.

You can also download the code directly via Git from the MediaWiki source code repository. From a command line, call the following:

= 세 번째 섹션 헤드 = This will be always displayed under the tab view because it's below the tag.

To view the code online, including the version history for each file, go here.

수정 스킨
To change the tabs' styling, see "Skin modification".

구성 매개 변수
The following parameters can be modified in LocalSettings.php below the.

$wgHeaderTabsUseHistory
defines whether tab navigation should be tracked within the browser history and within the URL, updating the hash value. By default this variable is set to true, i.e. history is used. You can disable it by adding the following:

$wgHeaderTabsRenderSingleTab
The  variable defines if Header Tabs will activate if only a single top-level header is found. By default this variable is set to false, i.e. no tabs will be shown if only one top-level header is found. You can enable this behaviour by adding the following:

$wgHeaderTabsAutomaticNamespaces
The  variable defines the set of namespaces for which you don't need to add the   tag in order to enable tabs. If a namespace ID is defined in this variable, header tabs will activate automatically when you have two top-level headers (or one, if you have  set to true) in an article. By default this variable holds no namespaces. You can add namespaces to this list by adding the following for each namespace:

$wgHeaderTabsDefaultFirstTab
The  variable defines whether Header Tabs puts any content before the first defined header and put it into its own tab. By default this variable is set to false. You can enable this behavior by adding the default name using the following:

If using this setting, be careful not to enable  as it will lead to tabs appearing in other parts of the UI.

$wgHeaderTabsDisableDefaultToc
The  variable defines whether Header Tabs will disable the MediaWiki article's table of contents (TOC) when tabs are enabled for a given article. This saves you the trouble of having to add  to your article. If tabs are not enabled because of a lack of top-level headers, the table of contents will appear as usual. By default this variable is set to true, i.e. the MediaWiki TOC is disabled if header tabs are shown. You can disable this behavior by adding the following:

$wgHeaderTabsGenerateTabTocs
The  variable defines if Header Tabs will try to generate a TOC for each tab. By default this variable is set to false, i.e. no tab TOCs will be generated. You can enable this behavior by adding the following:

$wgHeaderTabsEditTabLink
The  variable defines if Header Tabs will add a edit link to the right of the tabs which let you edit only the tabs' text. By default this variable is set to true, i.e. a edit link for the tab will be shown. You can disable this behavior by adding the following:

$wgHeaderTabsStyle
The  variable defines what visual style is used for the tabs. By default this variable is set to 'large'. You can change the style by adding the following:

Styles included with the extension are:

A wider selection of user-made styles as well as information about how to create your own styles is on our /Skin modification page.

버전 역사
To see a list of changes for each version, see version history. For a list of features planned for future releases, please see roadmap.

Known limitations and issues

 * You cannot use the tag more than once. In other words, a second tag will not produce a second series of tabs.
 * Tabs render on top of infoboxes in Chrome.

Incompatible extensions and skins
Header Tabs does not seem to work when used alongside the following extensions:
 * MathJax - when the two are used together, it leads to faulty HTML, which results in a broken display in at least the Firefox web browser. (Things might have changed as MathJax has been updated.) You can disable MathJax on specific pages by adding __NOMATHJAX__.
 * AddThis (or the Widget or WidgetsFramework versions) - only the first tab is shown
 * FancyBoxThumbs - same as AddThis.
 * MobileFrontend- same as AddThis.
 * SectionHide - incompatible due to both extensions altering section behavior. SectionHide now includes an automatic check that will inform the user that the extension does not work with Header Tabs.
 * Echo - seems to cause display problems with Header Tabs.
 * Lingo - Lingo parser renders HTML page before Header Tabs is called; thus, Header Tabs can't find its keyword anymore
 * Tweeki - Skin Tweeki breaks the layout and hide the text of the tabs

Sections appearing outside the tabbed section
Header Tabs sections which include floated objects (such as infoboxes) may appear outside the tabs container if other content does not force the container to be large enough to hold the floated object. One resolution to this problem is to place a cleared html element at the very end of each section. A simple, but not best-practice, means of doing this is: This forces this element to be considered by the browser after your floated object and thus will grow the container to fit both.

Sites using this extension
See here for a list of wikis. If you use this extension, please add a link to your wiki at the bottom of this list.

Support
The best way to seek help with this extension is to send questions the to mediawiki-l mailing list. The extension maintainers, and active users and contributors, are on this list and will be able to help you.