 | Thisguideline documents an English Wikipedianaming convention. Editors should generally follow it, thoughexceptions may apply.Substantive edits to this pageshould reflect consensus. |
| Article titles |
|---|
| All naming conventions |
| Nature |
|
| People |
|
|
| Organizations |
|
|
|
| Language/country-specific |
| Formatting |
Somepage names are not possible because of limitations imposed by theMediaWiki software. In some cases (such as names which should begin with a lowercase letter, likeeBay), a template can be added to the article to cause the title header to be displayed as desired. In other cases (such as names containing restricted characters) it is necessary to adopt and display a different title. This page describes appropriate ways to manage these situations.
Restrictions on page titles are listed atWikipedia:Page name § Technical restrictions and limitations. The most commonly encountered problems are that:
There are two basic ways of handling a situation where the desired title of a page is technically impossible:
These templates should never besubstituted (subst). To see which articles have these naming problems you can click on "What links here" in the toolbox for each template. If the template is substituted, it will no longer be linked.
Before declaring the current title to be "wrong" with the "correct title" template (or one of the more specific templates), please consider whether the title you are proposing as "correct" would really comply with Wikipedia conventions, particularlyWikipedia:Naming conventions (use English),Wikipedia:Manual of Style (capital letters) andWikipedia:Manual of Style (trademarks).
The MediaWiki software is configured so that a page title on the English Wikipedia (as stored in the database) cannot begin with a lower-case letter, and links that begin with a lower-case letter are treated as if capitalized, i.e.[[foo]] is treated the same as[[Foo]].
Examples of articles affected by this problem are:
Examples of categories affected by this problem are:
Example of template affected by this problem:
This also means that the pageLong s, on the characterſ, cannot be moved to (or redirected from)ſ, asſ is a lowercase letter whose uppercase form isS.
To fix this problem, you can place the{{lowercase title}} wiki markup at the top of the article, category or template page (and optionally at the top of their talk/discussion page). This will cause the page title to be displayed with the initial letter in lowercase, as ateBay. Note that it does not fix every occurrence, like Wikipedia search barsearch suggest drop-down list feature and Search results, as well as the page history, edit, log pages, or the browseraddress bar (it only affects the page title on the rendered HTML page and tab/window title bars).
Due to clashes with various elements of theMediaWiki software, some characters (and "characters") arenot allowed to be part of page titles (nor are they supported byDISPLAYTITLE).
The following characters are forbidden due to clashes withwiki markup andHTML syntax:
# < > | [ ] { }For articles about these characters, seenumber sign,less-than sign,greater-than sign,vertical bar, andbracket (covers several characters) respectively.
If the desired title of an article contains any of these characters, then an alternative title must be used instead. Often, you can simply remove the characters (e.g.MARRS instead ofM|A|R|R|S). However, it may be necessary to spell out the character (e.g.C-sharp instead ofC#) or use another substitute. Note that the sharp sign ♯ (different from the keyboard # character)can be used, as inC♯ (musical note).
In any of these cases, a hatnote should be placed at the top of the article informing readers what the correct title is. This is done using one of the following template calls:
{{Correct title|Title|reason=#}} for titles containing #{{Correct title|Title|reason=bracket}} for titles containing < > [ ] { }{{Correct title|Title|reason=vbar}} for titles containing |{{Correct title|Title}} for cases not covered by any one of the above.Examples:
Titles cannot contain invalidUTF-8 sequences (for our purposes, those that would decode toUTF-16unpaired surrogates or code points beyond U+10FFFF). Thus, titles like%ED%A0%80 (contains a UTF-8 sequence decoding to code point U+D800, an unpaired surrogate) or%F6%80%80%80 (contains a UTF-8 sequence decoding to code point U+180000, beyond the U+10FFFF limit) are invalid. (These examples use percent-encoded URLs rather than wikilinks, as the "characters" themselvesshould be impossible to insert into wikitext without percent-encoding.)
This also means that threevalid UTF-8 sequences are forbidden in page titles (how these are displayed may vary depending on your browser and installed fonts):
� � �The first of these characters or "characters", thereplacement character, is forbidden because the MediaWiki software uses the replacement character to represent invalid UTF-8 sequences, and cannot differentiate this use as a placeholder from an actual instance of the replacement character. The other two (the twononcharacters at the end ofUnicode plane 0, theBasic Multilingual Plane) are forbidden because the MediaWiki software uses the replacement character as a placeholder for these, just as it does for invalid UTF-8 sequences. Note, however, that the other 64 Unicode noncharacters (a block of 32 from U+FDD0 through U+FDEF, plus the two at the end of each of planes 1 through 16 [totaling another 32]) arenot forbidden in page titles, as can be seen in the following examples:
In general, article titles containing colons are fine, subject to the following exceptions:
Except in the case of initial colons and the w: and en: prefixes, DISPLAYTITLE will not work in the above situations. Use{{Correct title|Correct title|reason=:}}.
Innamespaces where thesubpage feature is enabled, the forward slash (/) separates a subpage name from its main page name. However subpages aredisabled in themain namespace, so article names can contain slashes if appropriate, as inProvidence/Stoughton Line – there is no need for such titles to be fixed. Be aware of the following side effects, however:
Page names consisting of exactly one or two periods (full stops), or beginning with./ or../, or containing/./ or/../, or ending with/. or/.., are not allowed. As a result of this, the abbreviation ofSlashdot,/., does not redirect to the page. In most such casesDISPLAYTITLE will not work, so{{correct title}} should be used. This is done using one of the following template calls:
{{Correct title|Title}} or{{Correct title|Title|reason=.}} for softer wording when the title used on Wikipedia is not necessarily incorrect.Examples:
A title can normally contain the character %. However it cannot contain % followed by twohexadecimal digits (which would cause it to be converted to a single character, bypercent-encoding). Similarly a title cannot containHTML character entities such as/ and–, even if the character they represent is allowed. In the unlikely event of such sequences appearing in a desired title, an alternative title must be constructed (for example by inserting a space after the %, or omitting a semicolon), and the title with encoding should be redirected to the adjusted title.
There is no reason why titles should not include ? or +. However, with such titles, attention is required when typing URLs into the address bar of a browser. Here ? is interpreted as beginning aquery string, and a + in a query string is interpreted as a space. In URLs, ? and + should be replaced by their correspondingescape codes, %3F and %2B. (The same technique is necessary for many other special characters, depending on browser.)
Inlinks, spaces () and underscores (_) are treated equivalently. Underscores are used in URLs, spaces in displayed titles. Leading and trailing spaces/underscores are stripped, consecutive spaces/underscores are reduced to a single one, and page names consisting of only spaces and underscores are not allowed at all.
Titles affected by this behavior can generally be made to display correctly using theDISPLAYTITLE magic word. However, this does not work for titles consisting of only spaces or underscores, which should use a parenthetical disambiguator e.g._ (album) is located at(album). Articles with underscores in titles are tracked inCategory:Articles with underscores in the title.
Titles cannot contain three or more consecutivetildes (~~~), as four consecutive tildes are used to create standard editors'signatures on talk pages, while three consecutive tildes generates an undated signature. For this reason,~~~ is located atTilde Tilde Tilde. When using{{Correct title}} and in all occurrences throughout the article, add nowiki tags around the sequence of tildes, as the software will otherwise convert these to a user-generated signature.
Titles must be fewer than 256 bytes long when encoded inUTF-8. Therefore, the full titles ofThe Boy Bands Have Won,Noisy Outlaws, andWhen the Pawn... cannot be displayed properly, so they must be located under their common shorthand names. Non-ASCII characters can take up to 4 bytes to encode, so the total number of allowable characters may be lower.
It is not possible for a titleas stored in the database to contain formatting, such as italics or bolding. The double or triple apostrophes normally used to produce these effects in wiki markup are treated just as groups of apostrophes if they appear in titles. Other wiki markup or HTML-based formatting would require characters that are not permissible in titles (seeForbidden characters above).
It is technically possible todisplay formatting in titles usingDISPLAYTITLE. A template,{{italic title}}, exists to display the title in italics. For guidance on when this technique should be used, seeWP:ITALICTITLE.
Titles cannot contain images (which would require forbidden characters in order to be displayed), onlyUnicode characters. For example, the recycling symbol♲ is encoded in Unicode as U+2672, so it can be included, but thenon-directional beacon symbol is not a Unicode character and cannot appear in a page title.
Useprecomposed characters when possible.
Use thetext normalization "Normalization Form C" (often abbreviated NFC). For more information, see theW3C's Character Model for the World Wide Web andUnicode's normalization forms.
Usernames are subject to the same technical restrictions as page titles (seeForbidden characters above). In particular, the symbols# < > [ ] | { } are not allowed. There are also additional restrictions:
/ @ : =.~2, as this is reserved fortemporary accounts.TheAntiSpoof extension also enforces the following restrictions on usernames:
There are also restrictions placed by theglobal title blacklist, both the normal blacklisting rules and those tagged by<newaccountonly>. The title blacklist blocks some usernames deemed inappropriate by the username policy, such as those implying advanced permissions (e.g. "admin") or impersonating high-profile users.