WikiQueer:Naming conventions (technical restrictions)

Some page names are not possible because of limitations imposed by the MediaWiki software. In some cases (such as names which should begin with a lower case letter, like eBay), 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 handle these situations.

Restrictions and workarounds
Restrictions on page titles are listed at WikiQueer:Page name. The most commonly encountered problems are that:
 * titles cannot begin with a lower case letter;
 * titles cannot contain certain restricted characters.

There are two basic ways of handling a situation where the desired title of a page is technically impossible:
 * Use the magic word DISPLAYTITLE to change the way the title header is displayed on the page (although the stored page name is not affected). This is often done through a template, the most common one being lowercase, which causes the title to be displayed with an initial lower case letter, as in iPod.
 * If this is not possible (due to restrictions on DISPLAYTITLE), choose a different title for the page, and use a template such as correct title to place a hatnote stating what the correct title should be. This is normally necessary in the case of restricted characters.

IMPORTANT NOTE: These templates should never be substituted (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.

ANOTHER IMPORTANT NOTE: before declaring the current title to be "wrong" with the "correct title" template or one of the more specific templates please consider if the title you are proposing as "correct" would really comply with WikiQueer conventions, particularly WikiQueer:Naming conventions (use English), WikiQueer:Manual of Style (capital letters) and WikiQueer:Manual of Style (trademarks).

Lower case first letter
The MediaWiki software is configured so that a page title (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:
 * eBay (located at EBay)
 * iPod (located at IPod)
 * s-CRY-ed (located at S-CRY-ed)
 * e (mathematical constant) located at E (mathematical constant).

This also means that the page Long s, on the character ſ, cannot be moved to (or redirected from) ſ, as ſ is a lowercase letter whose uppercase form is S.

To fix this problem, place the tag at the top of the article page (and optionally at the top of its discussion page). This will cause the article title to be displayed with the initial letter in lower case, as at eBay. Note that it does not fix every occurrence, like the history, edit, or log pages.

Forbidden characters
Due to clashes with wikitext syntax, the following characters can never be used in page titles (nor are they supported by DISPLAYTITLE):


 * 1) < > [ ] | { }

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 of M|A|R|R|S). However, it may be necessary to spell out the character (e.g. Gtk Sharp instead of Gtk#) or use another substitute. Note that the sharp sign ♯ (different from the keyboard # character) can be used, as in C♯ (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 templates:
 * for titles containing #
 * for titles containing < > [ ] { }
 * for cases not covered by any one of the above. Use  to represent the | character within the correct title.

Forward slashes and dots
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 – there is no need for such titles to be fixed. Be aware of the following side effects, however:
 * Subpages are still enabled in the talk namespace as they are widely used for archiving old discussion. Therefore if an article has a forward slash in its name, its corresponding talk page may display a redundant subpage level-up link at the top.
 * If / is the first character of the title, then links to it from outside the main namespace will not work as expected (they will prepend the title of the current page); a workaround is to prepend a colon, or to use a html entity as the beginning of the link, e.g. /dev/null, &amp; or &amp; to get to /dev/null.

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.

Spaces and underscores
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/underscores are not allowed at all.

Titles affected by this behaviour (except for the last restriction) can generally be made to display correctly using the DISPLAYTITLE magic word.

Colons
In general, article titles containing colons are fine, subject to the following exceptions:
 * Page names cannot begin with a colon. However, if the initial colon can be dropped to produce a satisfactory title, then this should be done, and the problem fixed with DISPLAYTITLE. For example, at Wumpscut:, the tag is used to display the desired title :wumpscut:. (This will not work with more than one initial colon.)
 * Article titles should not begin with a standard namespace prefix (Talk:, Help: etc.), as this will place them in the wrong namespace, which (among other problems) will exclude them from standard search results. In this case, another title must be found (it won't help to change the capitalization of the prefix or put spaces before or after the colon). For example, Help: a Day in the Life is located at Help!: A Day in the Life. A redirect is created at the original title (in this case at Help:A Day in the Life, which is what the above title resolves to).
 * Article titles cannot begin with an interwiki or interlanguage prefix, or namespace alias. Again, these are case-insensitive, and putting spaces before or after the colon won't help. Examples:
 * Project: Mersh would be located at Project Mersh (Project: is an alias for the WikiQueer namespace);
 * Book: A Novel would be located at Book A Novel (Book: is part of WikiQueer's namespace system for WikiQueer-generated books for PDF-downloading.
 * In the case of aliases a redirect can be created. In the fourth example above this will be at WikiQueer:Mersh, which is what "Project: Mersh" resolves to.

Except in the case of initial colons, DISPLAYTITLE will not work in the above situations. Use.

Percent and encoded characters
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).

Question marks and plus signs
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. When typing 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.)

Three continuous tildes

 * Title cannot contain 3 or more continuous tildes.

Title length
Titles must be less than 256 bytes long when encoded in UTF-8.

Italics and formatting
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 wikitext are treated just as groups of apostrophes if they appear in titles. Other wikitext 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 WQ:ITALICTITLE.

Pictorial names
Titles cannot contain images, only Unicode characters. For example, the peace symbol used in Sign “☮” the Times is a valid Unicode character (U+262E), so it can be included. However the symbol used as a name for many years by the musician Prince (see here) is not a Unicode character and so cannot appear in a page title.

Browser support limitations

 * See also: WikiQueer:Naming conventions (standard letters with diacritics)

Use precomposed characters when possible.

Use the text normalization NFC.