/2016Album/ but displays as having the correct title W:/2016Album/ (w: is a prefix for the English Wikipedia).
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=:}}
.
In namespaces where the subpage feature is enabled, the forward slash (/) separates a subpage name from its main page name. However subpages are disabled in the main namespace, so article names can contain slashes if appropriate, as in Providence/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. In most such cases DISPLAYTITLE will not work, so {{correct title}} should be used. As a result of this, the abbreviation of Slashdot, /., does not redirect to the page.
A title can normally contain the character %. However it cannot contain % followed by two hexadecimal digits (which would cause it to be converted to a single character, by percent-encoding). Similarly a title cannot contain HTML 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).
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 a query string, and a + in a query string is interpreted as a space. In URLs, ? and + should be replaced by their corresponding escape codes, %3F and %2B. (The same technique is necessary for many other special characters, depending on browser.)
In links, 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 the DISPLAYTITLE 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 in Category:Articles with underscores in the title.
Titles cannot contain three or more consecutive tildes (~~~), 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 at Tilde 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 in UTF-8. Therefore, the full titles of The Boy Bands Have Won, Noisy Outlaws, and When 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 title as 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 (see Forbidden characters above).
It is technically possible to display formatting in titles using DISPLAYTITLE. A template, {{italic title}}, exists to display the title in italics. For guidance on when this technique should be used, see WP:ITALICTITLE.
Titles cannot contain images (which would require forbidden characters in order to be displayed), only Unicode characters. For example, the recycling symbol ♲ is encoded in Unicode as U+2672, so it can be included, but the non-directional beacon symbol is not a Unicode character and cannot appear in a page title.
Use precomposed characters when possible.
Use the text normalization "Normalization Form C" (often abbreviated NFC). For more information, see the W3C's Character Model for the World Wide Web and Unicode's normalization forms.
Usernames are subject to the same technical restrictions as page titles (see Forbidden characters above). In particular, the symbols # < > [ ] | { }
are not allowed. There are also additional restrictions:
/ @ : =
.There are additional restrictions enforced by the AntiSpoof extension, which includes more blacklisted characters (various '/'-lookalikes and characters from unusual scripts such as Runic, Ugaritic, and so on) and checks against mixed scripts. There are also limitations placed by meta:Title blacklist, both the normal blacklisting rules and those tagged by <newaccountonly>
. Among the more notable of these are that accounts containing strings implying advanced permissions (e.g. "admin") or impersonating high-profile users are blocked.