메뉴얼:이름공간
A namespace is a collection of pages which have content with a similar purpose, i.e. pages where the intended use is the same. Namespaces can be thought of as partitions of different types of information within the same wiki, and keep "real" content separate from user profiles, help pages, etc.
The namespace prefix of a page forms part of the title of a page, separated with a colon (:).
기술적 개요
As said, pages exist within a namespace, and this can be distinguished using the namespace prefix of a page, which forms part of the title of a page, separated with a colon (:).
예를 들어:
| 제목 | 이름공간 | 코드 |
|---|---|---|
Foo |
Main | 0 |
Template:Foo |
Template | 10 |
Module:Foo |
Module | 828 |
"일반 이름공간"은 접두어를 가지고 있지 않습니다. 또한, 일반 이름공간 페이지는 콜론 앞에 존재하는 어떠한 이름공간도 가지고 있지 않습니다.
Pages can be moved between namespaces simply by changing the prefix part of their title.
Namespace prefixes can be translated, and aliases can be configured for each (see $wgNamespaceAliases). All namespaces also have a "canonical" prefix, which works on all wikis regardless of configuration. Aliases and canonical names can be used in links, when performing a search, and in the page title with the help of the {{DISPLAYTITLE}} magic word.
Each namespace has a corresponding namespace index. Within the database, the title is split into namespace index and text title, and this is used for storage in the page.page_namespace and page.page_title columns, among others.
과목과 토론 이름공간
- See 도움말:토론 문서 for instructions on how to use talk pages.
Most namespaces have an associated discussion namespace (or "talk" namespace).
All discussion namespaces have odd-integer indices, and the discussion namespace index for a specific namespace with index n is n+1.
The namespaces with even-integer indices are subject namespaces (note that this is a distinct concept from content namespaces).
The subject-talk duality can be explored using the {{SUBJECTPAGENAME}} and {{TALKPAGENAME}} magic words.
The <body> tag of pages in talk namespaces has the "ns-talk" CSS class, which might be useful for styling.
Built-in namespaces
MediaWiki ships with 18 built-in namespaces:
- 16 "real" namespaces, corresponding to actual pages, numbered 0 to 15, and grouped in subject/talk pairs
- 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces.
The full list is presented in the table below.
| ID | 이름 | 목적 | Talk | |
|---|---|---|---|---|
| 0 | (Main) | "Real" content articles.[1] | Talk | 1 |
| 2 | User | User pages.[2] | User talk | 3 |
| 4 | Project | 위키에 대한 안내.[3] | Project talk | 5 |
| 6 | File | Media description pages | File talk | 7 |
| 8 | MediaWiki | 사이타 인터페이스 사용자 지정.[4] | MediaWiki talk | 9 |
| 10 | Template | 틀 문서 | Template talk | 11 |
| 12 | Help | 도움말 문서 | Help talk | 13 |
| 14 | Category | Category description pages | Category talk | 15 |
| -1 | Special | Holds special pages | N/A | |
| -2 | Media | Alias for direct links to media files | ||
Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in Manual:Namespace constants.
- ↑ The subject namespace has no prefix.
- ↑ Editing a User talk page generates a notification for the user.
- ↑ Defined by
$wgMetaNamespace, which unless manually set otherwise, defaults to$wgSitename. - ↑ Only editable by users with the 'editinterface' permission.Some pages in this namespace additionally require
editsitecssandeditesitejspermissions.
사용자 지정 이름공간
Extensions and site administrators can define additional namespaces to group additional classes of pages together. For a thorough overview, see 매뉴얼:사용자 지정 이름 공간.
Functionality
Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace.
Template namespace pages can be transcluded without namespace prefix.
User namespace pages are associated with user accounts or IP addresses. Changes to user talk pages generate an automatic message notification.
Pages in the "MediaWiki" namespace are used to override default messages in language file and can only be edited by administrators or other users with the editinterface permission.
File and Category pages have special functionality, as described in Help:파일 관리 and 도움말:분류. Files can be moved by users with the "movefile" right. Category pages can be moved by users with the "move-categorypages" right.
All pages in discussion namespaces have a "post a comment" feature (see Help:Section#Adding a section at the end on Meta).
같이 보기
- 도움말:이름공간 - user-oriented information.
Site administration
Extensions
- Category:Namespace extensions
- Extension:NamespaceManager - for management of namespaces.
- Extension:BlueSpiceNamespaceManager - lets you create custom namespaces.
- Extension:SpecialNamespaces - a modified version of the 확장기능:인터위키 which changes it to provide a namespace manager as a special page.
- Extension:Lockdown - to control access to namespaces.
- Extension:SkinPerNamespace - to use a different skin in a namespace.
For extension developers
- 매뉴얼:사용자 지정 이름 공간
- List of custom namespaces registered by extensions. If you define a constant for a custom namespace, list it here, too.
- Classes
- Manual:MWNamespace.php, containing the MWNamespace class (1.39 에서 제거됨)
- Hooks
- Manual:Hooks/CanonicalNamespaces - add custom namespaces or alter the defaults.
- Manual:Hooks/NamespaceIsMovable - determine if it is possible to move pages in a namespace.
- Manual:Hooks/SearchableNamespaces - modify which namespaces are searchable.
- Manual:Hooks/LanguageGetNamespaces - provide custom ordering for namespaces or remove namespaces.
- Manual:Hooks/PrefixSearchExtractNamespace - called if core was not able to extract a namespace from the search string so that extensions can attempt it.