text:
Template:Visible anchor/doc

The template ( for short) inserts one or more HTML anchors in a page. Those locations can then be linked to using  syntax. Unlike Anchor, the first parameter will be visible text on the page.

Examples
1.
 * Visible as: foo
 * Linkable as:  from within the same article,    from other articles and from redirects.

2. The template can be used to create up to ten anchors with a single call. For example,
 * Visible as: foo
 * Linkable as:,  and.
 * Linkable as:,  and.

Limitations

 * Anchor names that contain
 * # (hash, &#36;)
 * | (pipe, &#124;)
 * = (equals, &#61;)
 * " (straight double quote, &quot;)
 * will not work as expected. However, any of these characters can be replaced with the "&#" codes shown for them here. Or, the pipe symbol and equals sign can be worked around with undefined and =, respectively. Markup code such as and  (superscript and subscript) cannot be used. Most other characters, including white space and punctuation, are not a problem.

 * The template can create a maximum of 10 anchors. Specifying more than 10 anchors will result in an error message.
 * As with other templates which use positional parameters, putting each anchor name on separate lines, for example
 * will not work as expected.
 * will not work as expected.
 * will not work as expected.

 * Anchor names should be unique on a page, and should not duplicate any heading titles. Duplicate anchors won't work as expected since the #links go to the first anchor with that name. Duplicate anchors also result in invalid HTML; you can check for duplicate anchors by running the page through the W3C Markup Validation Service.
 * If the template is added to a section title then the code will appear in the edit summary when that section is edited, as in "/* Limitations */ New issue" . This can be fixed by replacing the template code with its first parameter in the edit summary before the changes are saved: "/* Limitations */ New issue".

title: Template:Visible anchor/doc


text: Template:Anchored list

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Template:Anchored list


text:
Template:Anchored list/doc

This template can be used to create an ordered list which generates HTML anchors for every bullet point. This makes it much easier to maintain lists where anchors to individual entries are required.

Usage
1. first entry

2. Second entry

3. So on ...

4. Last entry

Up to 99 entries are supported.

title: Template:Anchored list/doc


text: Template:Patent

title: Template:Patent


text:
Template:Patent/doc

Usage
This template is designed for simple citation of patents. Parameters are passed numerically:

 * 1) The prefix of the organization publishing the patent, examples are
 * 2) *US - U.S. Patent Office
 * 3) *EP - European Patent Organisation (under the European Patent Convention)
 * 4) *WO - World Intellectual Property Organisation (under the United Nations)
 * 5) *DE - Deutsches Patent- und Markenamt
 * 6) The patent or patent application number (no punctuation is allowed at this time)
 * 7) string "application" (optional third parameter)
 * 8) Patent publication data such as author name and title (this does not affect the generated URL)

The output is the patent number, and a link pointing to a permalink for the patent chosen. This output should be enclosed within reference tags ( and  ) in the same way as Template:cite.

Note that patent application numbers are generally different from patent numbers. If you need this, please use the Template:Cite patent template with the optional application parameter.

Examples:
 *   results in

 *   results in

 *   results in

 *   results in

title: Template:Patent/doc


text: Template:Cite patent

title: Template:Cite patent


text:
Template:Cite patent/doc

This template identifies a patent or patent application and links to the patents entry in the espacenet database, and also provides some additional information about the cited patent. Suggested uses are within a pair of tags or as part of a (patent) bibliography at the end of the article.

General patent template for citing patents or patent applications from any country is drawn from the espacenet database. This database is more useful than the USPTO database since it highlights related patents/applications in other countries as well as providing current status information and offers a multi-language interface (English/French/German).

Usage
Copy the below into an article to reference a patent

Parameters
The fields should be filled in with the following information

Explanation of fields:

 * 1) The country must be the two letter country code, eg "US" or "WO" (for international patent applications)
 * 2) Do not put commas in patent number
 * 3) Applications must be identified by publication number
 * 4) Add " | title = title " to display the title. Required
 * 5) Add " | status = application " if the citation is a pending application. Preferably include " | status = patent " if a granted patent.
 * 6) Add " | assign1 = assignee " to display the assignee. Increase the numeral for subsequent assignees. Template currently handles two assignees.
 * 7) Add " | inventor = inventor list to provide the inventor names. Displayed by the template but not used to generate COinS meta data.
 * 8) Add " | invent1 = inventor last name, inventor first name " to provide the inventor name. Displayed by the template and also used to generate COinS meta data. Increase the numeral for subsequent inventors. Template currently handles four inventors.
 * 9) Add " | pubdate = YYYY-MM-DD " to provide the publication date of an application. This is only displayed if "status=application" is included. For granted patents, use gdate. Required if "status=application".
 * 10) Add " | gdate = YYYY-MM-DD " to provide the date of grant of a patent. Is displayed unless "status=application" is included. Preferentially include "status=patent" to confirm that the patent is granted, but this is not required. Required unless "status=application".
 * 11) Add " | pridate = YYYY-MM-DD " to provide the (earliest) priority date. Not displayed, but could be useful to include for future reference. Including multiple priorities unnecessarily complicated.
 * 12) Add " | fdate = YYYY-MM-DD " to provide the filing date. Not displayed, but used to generate COinS meta data and may prove useful in future.
 * 13) Add " |class=ECLA classification " to provide the ECLA classification. Not displayed, but could be useful to include for future reference. Might be possible to automatically link to the relevant classification in future, but urls are complex.

Details
The "country" parameter must be a two letter country code without periods (eg US or EP, not U.S. or USA or E.P.)

The number parameter must be the patent number or patent application publication number without any intervening commas (eg 2135432, not 2,135,432). You may need to experiment with the precise form for published US patent applications or PCT applications, which are slightly unusual. Help for getting the right number format can be found here.

Add "|status=applicaton" (without quotes) if you are citing a patent application rather than a patent. Patent applications must be referred to by publication number, not application number.

One (or both) of the publication date or the grant date must be included, as must the title.

Examples
To cite WIPO (aka PCT) patent application WO 2005/083605 A1, use: Results in:

To cite US patent 7,143,445, use: Results in:

To cite US patent 7,143,445, published 2006-11-28, use: Results in:

To cite US patent application 2006265789 use: Results in:

To cite European patent application 1727416, use: Results in:

title: Template:Cite patent/doc


text: Template:Citation/patent

title: Template:Citation/patent


text:
Template:Citation/patent/doc

Usage
This template is called by Citation and (soon) Cite patent and should not be called directly. Rather, use citation or cite patent.

title: Template:Citation/patent/doc


text:
Template:UF-COinS

This template produces COinS metadata; see COinS in Wikipedia for background information.

title: Template:UF-COinS


text:
Template:EPO Register

European Patent Register entry for European patent no.

title: Template:EPO Register


text:
Template:EPO Register/doc

Usage
This template creates an external link to the entry in the European Patent Register for a European patent application or European patent. The minimum information is the application no. for the application using the field "appno=". This is vital as only the application no. will make the link work. The publication no. can be added as well using the field "patno=" and this is displayed by default. Add the field "patent=yes" if the case is a granted patent.

 * Form

 * Examples:
 * leads to:
 * leads to:

title: Template:EPO Register/doc


text: Template:EPO Guidelines

title: Template:EPO Guidelines


text: Template:US patent

title: Template:US patent


text:
Template:US patent/doc

undefined links to the incomplete Google Patents search, by default. With the optional src parameter it will link to the more complete online USPTO patent application with TIFF images for pre-1976 patents and full-text for post 1976 patents. The Google search may provide a PDF transcript of the text extracted from the TIFF images. If your browser has difficulty displaying or downloading TIFF images, consider installing a TIFF capable extension such as AlternaTIFF for Mozilla Firefox, Opera, and Google Chrome, browsers (and Netscape 9.0.0.6), or use a TIFF capable browser such as Links or Safari version 3.2.1 (may display the wrong size but allows full images to be saved).

Because Google patent search does not include all the USPTO patents, please consider providing two template calls, one with the src parameter and the other with no named parameter to default to the Google search

CAUTION: This patent template is not as featured as the generic one (patent), and it should not be used except for older patents and possibly other circumstances. From "Template:Cite patent/doc":

"Simple patent template for citing patents or patent applications from any country in the esp@cenet database. This database is more useful than the USPTO database since it highlights related patents/applications in other countries, provides current status information, and is available in three languages. However, the template is not deprecated because the USPTO database does include items (such as some older US patents) which are not included in the espacenet database."

Parameters

 * 1 (mandatory): The US patent number without commas, commas will be inserted by the template. While the USPTO parser ignores commas other services (notably Google Patents) cannot handle them.  For design or reissued patents prefix with   or , respectively; see Patent Search Help for the full list.

 * 2 (optional): Link title. Use   and   for   and , respectively.

 * src (optional): |src=uspto will cause the template to use the more complete USPTO patent search

title: Template:US patent/doc


text: Template:US patent application

title: Template:US patent application


text: Template:US patent application/doc

title: Template:US patent application/doc


text: Template:US patent reference

title: Template:US patent reference


text:
Template:US patent reference/doc

This template is mostly for inclusion in the "References" section of article, giving detailed description of US patent: the inventor, title, and link to find full text in US patent office database.

Usage

 * number (required) is a patent number, without leading "US" letters, but with leading "D" letter if patent number contains it, and is required.
 * y, m, d (optional) are the year, month and day of issuing (granting). Four digits are required for the year, and two for the month and day even if the first digit is zero.
 * inventor (optional) is a name of inventor; it can be a wiki-link, of course.
 * title (optional) is the title of the patent.

Sample rendering
Preferably, after inclusion of this template in "references", one should give less formal and more reader-friendly explanation of what this patent is all about.

title: Template:US patent reference/doc


text: Template:USPTO Application

title: Template:USPTO Application


text: Template:USPTO Application/doc

title: Template:USPTO Application/doc


text: Template:USPTO Patent

title: Template:USPTO Patent


text: Template:USPTO Patent/doc

title: Template:USPTO Patent/doc


text:
Template:PCT Rule

Rule

title: Template:PCT Rule


text:
Template:PCT Article

Article

title: Template:PCT Article


text:
Template:EPC Rule

Rule

title: Template:EPC Rule


text:
Template:EPC Article

Article

title: Template:EPC Article


text:
Template:EPC 1973 Rule

Rule

title: Template:EPC 1973 Rule


text:
Template:EPC 1973 Article

Article

title: Template:EPC 1973 Article


text: Template:Ifeq

title: Template:Ifeq


text:
Template:Ifeq/doc

This template is like #ifeq, but does not trim the "then" and "else" part.

Usage

 * gives ""

title: Template:Ifeq/doc


text: Template:Xifeq

title: Template:Xifeq


text:
Template:Xifeq/doc

The Template:Xifeq, provides an if-equal function like parser function #ifeq, except that it uses nowiki tags to avoid the trimming of spaces and to avoid the automatic newline feature/bug in the "then" and "else" parts.

 * Usage:
 * →

Parameters:
 * {1} - the 1st value to compare
 * {2} - the 2nd value to compare to 1st
 * {3} - result when true (as then-part of if)
 * {4} - result when false (as else-part of if)

For small results, the processing speed will be similar to #ifeq (see below: Performance and resources).

Examples
Some examples help to show the extended capability to handle cases such as a leading colon or leading-pound sign which triggers indented numbering when used in #ifeq:
 * → ""
 * →
 * → ""
 * →

Because a leading pound# (hash mark) can trigger auto-indentation as a numbered list, treats a leading "#" (or colon ":" or asterisk " " or semicolon ";") as being typical data, rather than indentation markup codes. As other problems arise with #ifeq, then this template can be modified to overcome those glitches and continue to work in a predictable manner.

The coding inside Template:Xifeq has been optimized to use only 2 levels of expansion nesting (see Meta "m:Help:Expansion depth"), and runs very fast.

Limitations
The Template:Xifeq has the following limitations: it requires special coding for equal-sign "="; it performs numeric comparison unless not numbers.

As typical with #ifeq, the 2 values are compared numerically (where "2" equals "2.0") unless the values are not numbers:
 * →

The numeric comparison can be avoided by putting a letter such as "z" in front of both values to compare: {{xifeq|z{{{1}}}|z{{{2}}}|...}} to force an alphanumeric comparison.

Because Template:Xifeq processes the then-clause and else-clause as template parameters, they cannot contain a simple equal-sign as in "x=x" so use either an unnamed parameter "x{{{|=}}}x" or "x{{=}}x" or set parameters by both number 3 and 4: "3=x=x" (then-clause) plus "4=not x" (else-clause).

 * →
 * →
 * →

Note how the parser function #ifeq allows the simple equal-sign "x=x" whereas xifeq needs both "3=x=x" and "4=not x" to allow an equal-sign in parameter 3. For those reasons, using an unnamed parameter "x{{{|=}}}x" is often the easiest method.

The method for allowing spaces in if-logic uses 2 nowiki-slash tags "<nowiki/>" around the then-clause and else-clause: → "". This affects using the result in string comparisons and string functions.

Performance and resources
The Template:Xifeq is designed to run very quickly, with minimal expansion nesting (as 2 levels) and format concise results similar to #ifeq. However, unlike #ifeq, both the then-clause and else-clause will be expanded before the comparison is made. Also, unlike #ifeq, the intermediate expansion sizes of both the then-clause and else-clause are both counted, and counted double, against the resource post-expand size (of 2,000 kb conditional text). If the then-cause and else-clause are roughly equal in size, the post-expand size would be 4x times that size. However, only the actual choice of then-clause or else-clause is formatted into the final page; the post-expand size is just an intermediate limit for the MediaWiki preprocessor.

During intermediate processing, Template:Xifeq requires the formatting of both the then-part and else-part, before choosing between the 2 sets of formatted results. In most cases, there is no significant speed delay because hundreds of templates can be processed very quickly before choosing between 2 if-else branches.

title: Template:Xifeq/doc


text: Template:Xifnoteq

title: Template:Xifnoteq


text:
Template:Xifnoteq/doc

The Template:Xifnoteq provides a quick, extended if-not-equal function, as a reverse check, beyond the parser function #ifeq.
 * Usage:
 * →

Parameters:
 * {1} - the 1st value to compare
 * {2} - the 2nd value to compare to 1st
 * {3} - result when not equal (as then-part of if)
 * {4} - result when equal (as else-part of if)

For small results, the processing speed will be very similar to #ifeq (see below: Performance and resources).

Examples
Some examples help to show the extended capability to handle cases such as a leading colon or leading-pound sign which might trigger indented numbering when used in #ifeq:
 * →

 * "" → ""
 * "" → ""
 * →
 * →

Because a leading pound# (hash mark) can trigger auto-indentation as a numbered list, treats a leading "#" (or colon ":" or asterisk " " or semicolon ";") as being typical data, rather than indentation markup codes. As other problems arise with #ifeq, then this template can be modified to overcome those glitches and continue to work in a predictable manner.

The coding inside Template:Xifnoteq has been optimized to use only 2 levels of expansion nesting (see "m:Help:Expansion depth"), and runs very fast.

Limitations
The Template:Xifnoteq has the following limitations: it requires special coding for equal-sign "="; it performs numeric comparison unless {1} and {2} are not numbers.

As typical with #ifeq, the 2 values are compared numerically (where "2" equals "2.0") unless the values are not numbers:
 * →

The numeric comparison can be avoided by putting a letter such as "z" in front of both values to compare: {{xifnoteq|z{{{1}}}|z{{{2}}}|...}} to force an alphanumeric comparison.

Because Template:Xifnoteq processes the then-clause and else-clause as template parameters, they cannot contain a simple equal-sign as in "x=x" so use either an unnamed parameter "x{{{|=}}}x" or "x{{=}}x" or set parameters by both number 3 and 4: "3=not =x" (then-clause) plus "4=x=x" (else-clause).

 * →
 * →
 * →

Note how the parser function #ifeq allows the simple equal-sign "x=x" whereas xifnoteq needs both "3=not =x" and "4=x=x" to allow an equal-sign in parameter 3. For those reasons, using an unnamed parameter "x{{{|=}}}x" is often the easiest method.

Performance and resources
The Template:Xifnoteq is designed to run very quickly, with minimal expansion nesting (as 2 levels) and format concise results similar to #ifeq. However, unlike #ifeq, both the then-clause and else-clause will be expanded before the comparison is made. Also, unlike #ifeq, the intermediate expansion sizes of both the then-clause and else-clause are both counted, and counted double, against the resource post-expand size (of 2,000 kb conditional text). If the then-cause and else-clause are roughly equal in size, the post-expand size would be 4x times that size. However, only the actual choice of then-clause or else-clause is formatted into the final page; the post-expand size is just an intermediate limit for the MediaWiki preprocessor.

During intermediate processing, Template:Xifnoteq requires the formatting of both the then-part and else-part, before choosing between the 2 sets of formatted results. In most cases, there is no significant speed delay because hundreds of templates can be processed very quickly before choosing between 2 if-else branches.

The method for allowing spaces in if-logic, in January 2011, used 2 nowiki-slash tags "<nowiki/>" around the then-clause and else-clause: → " yes ".

title: Template:Xifnoteq/doc


text: Template:Xifexpr

title: Template:Xifexpr


text:
Template:Xifexpr/doc

The Template:Xifexpr provides a quick, extended if-expression function, to compensate for any performance limitations, beyond the parser function #ifexpr.
 * Usage:
 * →

Parameters:
 * {1} - the expression to evaluate as an if-test
 * {2} - result when expression is true (as then-part of if)
 * {3} - result when expression is false (as else-part of if)

For small results, the processing speed will be similar to #ifexpr (see below: Performance and resources).

Examples
Some examples help to show the extended capability to handle cases such as a leading colon or leading-pound sign which might trigger indented numbering when used in #ifexpr:
 * →

 * "" → ""
 * "" → ""

 * →
 * →

 * →
 * →

 * →

 * text → text
 * text → text

Because a leading pound# (hash mark) can trigger auto-indentation as a numbered list, treats a leading "#" (or colon ":" or asterisk " " or semicolon ";") as being typical data, rather than indentation markup codes. As other problems arise with #ifexpr, then this template can be modified to overcome those glitches and continue to work in a predictable manner.

The coding inside Template:Xifexpr has been optimized to use only 2 levels of expansion nesting (see "m:Help:Expansion depth"), and runs very fast.

Limitations
The Template:Xifexpr has the following limitations: it requires special coding for equal-sign "="; it performs numeric comparison of parameters unless they are compared using a {#ifeq} test, as nested inside the ifexpr, {ifexpr|{#ifeq:aa|bb|1}|...|...}.

As typical with #ifexpr, the values are compared numerically (where "2" equals "2.00") as in the following comparison:
 * →

The numeric comparison can be avoided by putting a letter such as "z" in front of both values and comparing them, first, within a nested {#ifeq}: {{xifexpr| {{#ifeq: z{{{1}}}|z{{{2}}}|1 }}|<then>|<else>}} to force an alphanumeric comparison of each 2 parameters (resulting as "1" meaning true when equal), within the overall expression.

Because Template:Xifexpr processes the then-clause and else-clause as template parameters, they cannot contain a simple equal-sign as in "x=1" so use either an unnamed parameter containing "=" as in "x{{{|=}}}1" or use Template:= as in "x{{=}}x" or set parameters by both parameter number 2 and 3: "2=x=1" (then-clause) plus "3=not 1" (else-clause).

 * →
 * →
 * →

Note how the parser function #ifexpr allows the then-clause or else-clause to contain a simple equal-sign (as in "x=1"), whereas Xifexpr needs both "2=x=1" and "3=not 1" to allow an equals-sign in parameter 2. For those reasons, using an unnamed parameter "x{{{|=}}}1" is often the easiest method.

Performance and resources
The Template:Xifexpr is designed to run very quickly, with minimal expansion nesting (as 2 levels) and format concise results similar to #ifexpr. However, unlike #ifexpr, both the then-clause and else-clause will be expanded before the expression is evaluated. Also, unlike #ifexpr, the intermediate expansion sizes of both the then-clause and else-clause are both counted, and counted double, against the resource post-expand size (of 2,000 kb of conditional text). If the then-cause and else-clause were roughly equal in size, the post-expand size would be 4x times that size. However, only the actual choice of then-clause or else-clause is formatted into the final page; the post-expand size is just an intermediate limit for the MediaWiki preprocessor.

During intermediate processing, Template:Xifexpr requires the formatting of both the then-part and else-part, before choosing between the 2 sets of formatted results. In most cases, there is no significant speed delay because hundreds of templates can be processed very quickly before choosing between 2 if-else branches.

The method for allowing spaces in if-logic, in January 2011, used 2 nowiki-slash tags "<nowiki/>" around the then-clause and else-clause: → " yes ".

title: Template:Xifexpr/doc


text: Template:Arxiv

title: Template:Arxiv


text:
Template:Arxiv/doc

Purpose
Provides a uniform method of formatting arXiv links, and makes it simpler to update if the format of those links changes in future.

Usage
This template can be used in the following ways:

The first two calling sequence are to be used for old-style identifiers (i.e., those before 1 April 2007), while the latter two are for newer papers (after 31 March 2007).

The parameters have the following meaning:
 * archive specifies the arXiv archive (full list here) using the abbreviated code
 * id specifies the ID of the particular entry

title: Template:Arxiv/doc


text: Template:Cite arXiv

title: Template:Cite arXiv


text:
Template:Cite arXiv/doc

Usage
cite arXiv is for formatting references to preprints at the arXiv. It links to the abstract at http://www.arxiv.org/abs/ eprint.

To use the template, you need only specify the 'eprint' parameter. Once you save the page, a bot will detect the citation and complete it automatically.

 * Common parameters, horizontal format

 * last1, last2, last3...: Surnames of the author(s)
 * first1, first2, first3...: Forenames of the author(s)
 * author1, author2, author3 etc: Name(s) of the author(s) if last-first format is not appropriate (e.g. some east Asian names)
 * authorlink1, authorlink2...: Name of author's Wikiversity page. Will be used to make author name a link, if present.  Optional.
 * eprint (Mandatory): Eprint identifier, without any "arXiv:" prefix. Prior to April 2007, the identifiers included a classification, an optional two-letter subdivision, and a 7-digit YYMMNNN uear, month, and sequence number of submission in that category.  E.g. gr-qc/0610068 or math.GT/0309136.  After April 2007, the format was changed to a simple YYMM.NNNN.
 * class: arXiv classification, e.g. hep-th. Optional.  To be used only with new-style eprint identifiers, that do not include the classification.
 * title: Title of the cited paper.
 * year: Year of publication. Optional.
 * version: arXiv version, including leading "v", e.g. "v1". Optional.

The template also supports most of the parameters supported by cite journal or citation, and uses the style of cite journal. Once a paper is accepted in a peer-reviewed journal, it is recommended to use one of those templates, as the peer-reviewed status of the article is important, while preserving the arXiv link in order to guarantee open access to the article. To preserve the arXiv link, add e.g. gr-qc/0610068 or math.GT/0309136 or YYMM.NNNN (following the above examples) to the citation/cite journal templates.

title: Template:Cite arXiv/doc


text: Template:Citation Style 1

title: Template:Citation Style 1


text: Template:!xt

title: Template:!xt


text: Template:Vancite book

title: Template:Vancite book


text: Template:Vcite news

title: Template:Vcite news


text: Template:Vcite web

title: Template:Vcite web


text:
Template:Cs2

Citation Style 2

title: Template:Cs2


text: Template:Harvard citation no brackets

title: Template:Harvard citation no brackets


text:
Template:Harvard citation no brackets/doc

Template harvnb creates a short author-date citation with a one-directional link to the first matching citation template on the same page.


text: Template:Harvard citation text

title: Template:Harvard citation text


text:
Template:Harvard citation text/doc

Template harvtxt creates a short author–date citation with a one-directional link to the first matching citation template on the same page.

title: Template:Harvard citation text/doc


text: Template:Harvcoltxt

title: Template:Harvcoltxt


text:
Template:Harvcoltxt/doc

Template harvcoltxt creates a short author-date citation with a one-directional link to the first matching citation template on the same page.

title: Template:Harvcoltxt/doc


text: Template:Harvcol

title: Template:Harvcol


text:
Template:Harvcol/doc

Template Harvcol creates a short author-date citation with a one-directional link to the first matching citation template on the same page.

title: Template:Harvcol/doc


text: Template:Harvcolnb

title: Template:Harvcolnb


text:
Template:Harvcolnb/doc

Template harvcolnb creates a short author-date citation with a one-directional link to the first matching citation template on the same page.

title: Template:Harvcolnb/doc


text: Template:Harvard citations

title: Template:Harvard citations


text:
Template:Harvard citations/doc

Purpose
The "Harvard citations" template is for producing more complicated Harvard citations, when one wishes to link several publications by the same author, or add a link to the author's name. For most simple Harvard citations the templates harv, harxtxt, and harvnb are easier to use.

The template name "Harvard citations" can be abbreviated as "harvs".

Parameters (all optional)
Most of the parameters, in particular those for authors, editors, and year, should be the same as for the corresponding citation template. (If these are missing the template will try to guess them by looking for other parameters such as "date", "author" and so on.) In fact one can produce this template just by changing the name "citation" in the corresponding citation template to "harvard citations" and keeping all parameters the same.

Examples
An example with authorlinks:

 * A reference is.

A reference is.

An example with txt

 * The theory was developed by.

The theory was developed by.

An example using nb to list 2 sets of authors, using citationpage to link to the von Neumann algebra page:

 * The theory was developed in a series of papers.

The theory was developed in a series of papers.

title: Template:Harvard citations/doc


text:
Template:Harvard citations/core

#|

title: Template:Harvard citations/core


text: Template:Sfnp

title: Template:Sfnp


text:
Template:Sfnp/doc

The shortened footnote with parentheses template ( creates a short author-date citation in a footnote.  It works exactly like the basic  template, except that it puts parentheses around the year, a bit like the way that full citations appear in (e.g.) APA style.  It is a stylistic alternative to.

title: Template:Sfnp/doc


text: Template:Sfnm

title: Template:Sfnm


text: Template:Sfnm/core

title: Template:Sfnm/core


text:
Template:Sfnm/doc

This is a companion template to Sfn; see there for a more general introduction. Unlike Sfn, however, Sfnm supports the inclusion of multiple sources in a single footnote.

For example, the following code: will produce the following footnote:

The following parameters are used (where n may be 1 through 10):
 * na1 (e.g., 1a1 or 4a1) through na5 – authors of the work cited
 * ny – year
 * nloc – location cited
 * np – page cited
 * npp – pages cited

Instead of using na1 and ny, unnamed parameters may be used, as in the following example: which will produce the following footnote:

title: Template:Sfnm/doc


text:
Template:Sfnote

Help:Shortened footnotes

title: Template:Sfnote


text:
Template:Sfnote/doc

Usage
This template is a typing aid that provides a link to.

title: Template:Sfnote/doc


text: Template:Fake notes and references

title: Template:Fake notes and references


text:
Template:Cite *

 This template can be used on documentation pages to describe the set of templates supported by citation/core.

title: Template:Cite *


text: Template:Cite magazine

title: Template:Cite magazine


text:
Template:Vcite

Citation Style Vancouver

title: Template:Vcite


text: Template:Cite thesis

title: Template:Cite thesis


text:
Template:Cite thesis/doc

Unpublished Doctoral, Masters thesis. Other Higher Research Degrees.
 * These reports are to be published in the Wikiversity sense of verifiability: a University recognised by other Universities as capable of awarding research higher degrees must have accepted and passed the thesis or dissertation, and the dissertation must be available for consultation through abstracting / microfilming / electronic archiving / University Library access.
 * Failed, unsubmitted, or incomplete theses are not Reliable Sources; and should not be used for verification purposes.

Published theses should be cited with cite book. The degree parameter can be used for specifying the degree.

Usage
Horizontal format:

Examples

Title

 * Aliases: type, degree

Identifiers

 * Aliases: id, docket

TemplateData
{ "params": { "last": { "aliases": [ "last1", "surname", "surname1", "author", "author1" ], "label": "Surname of author", "description": "Surname of author. Do not wikilink—use author-link instead. For corporate authors or authors for whom only one name is listed by the source, use last or one of its aliases", "type": "string", "suggested": true }, "first": { "aliases": [ "first1", "given", "given1" ], "label": "First name of author", "description": "Given or first names of author, including title(s). Requires last; first name will not display if last is empty.", "example": "Firstname Middlename or Firstname M. or Dr. Firstname M., Sr.", "suggested": true }, "title": { "label": "Title of source", "description": "Title of source. Can be wikilinked to an existing Wikipedia article or url may be used to add an external link, but not both. Displays in italics. If script-title is defined, title holds romanized transliteration of title in script-title. ", "type": "string", "required": true }, "date": { "label": "Date", "description": "Date of source being referenced. Can be full date (day, month, and year) or partial date (month and year, season and year, or year). Use same format as other publication dates in the citations.", "type": "date", "suggested": true }, "degree": { "label": "Degree", "default": "Thesis", "example": "PhD", "description": "The degree qualification received for the given thesis or dissertation.", "type": "string", "suggested": true }, "publisher": { "label": "Publisher", "description": "Name of awarding institution; may be wikilinked if relevant.", "type": "string", "suggested": true }, "url": { "label": "URL", "description": "URL of an online location where the text of the publication can be found. Cannot be used if title is wikilinked.", "type": "url", "suggested": true }, "url-access": { "label": "URL access level", "description": "Classification of the access restrictions on the URL ('registration', 'subscription' or 'limited')", "type": "string" }, "place": { "label": "Location of publication", "description": "Geographical place of publication; usually not wikilinked; omit when the publication name includes place", "type": "string" }, "isbn": { "label": "ISBN", "description": "International Standard Book Number; use the 13-digit ISBN where possible", "type": "line" }, "doi": { "label": "DOI", "description": "Digital Object Identifier; begins with '10.'", "type": "string", "suggested": true }, "doi-broken-date": { "label": "DOI broken date", "description": "The date that the DOI was determined to be broken", "type": "date" }, "doi-access": { "label": "DOI access level", "description": "If the full text is free to read via the DOI, type 'free'.", "type": "string" }, "language": { "label": "Language", "description": "The language in which the source is written, if not English; use the full language name; do not use icons or templates", "type": "content" }, "format": { "label": "Format", "description": "Format of the work referred to by url; for example: PDF, DOC, or XLS; displayed in parentheses after title. HTML is implied and should not be specified. Automatically added when a PDF icon is displayed.", "type": "string" } }, "description": "A Citation Style 1 template used to create citations for theses or dissertations submitted to and approved by an educational institution recognized as capable of awarding higher degrees.", "format": "inline", "maps": { "citoid": { "title": "title", "url": "url", "university": "publisher", "date": "date", "place": "place", "type": "degree", "thesisType": "degree", "ISBN": [ "isbn" ], "DOI": "doi", "language": "language", "author": [ [ "first", "last" ] ] } } }

title: Template:Cite thesis/doc


text: Template:Citation Style documentation

title: Template:Citation Style documentation


text:
Template:Citation Style documentation/doc

Usage
This template is used to build consistent documentation pages for templates.

 * For example: will show the author documentation.

Where a particular section of documentation is not appropriate for a certain template, simply add the text manually or create a new subtemplate.

Each module of text is a subtemplate that can be edited using the link.

display

 * cs2: When set, changes the separator to "comma "}}


text:
Template:Citation Style documentation/edit

edit subtemplate


text:
Template:Citation Style documentation/syntax

Nested parameters rely on their parent parameters:
 * parent
 * OR: parent2—may be used instead of parent
 * child—may be used with parent (and is ignored if parent is not used)
 * OR: child2—may be used instead of child (and is ignored if parent2 is not used)

 * Where aliases are listed, only one of the parameters may be defined; if multiple aliased parameters are defined, then only one will show.


text:
Template:Citation Style documentation/coins

This template embeds COinS metadata in the HTML output, allowing reference management software to retrieve bibliographic metadata. As a general rule, only one data item per parameter. Do not include explanatory or alternate text:
 * Use 27 September 2007 not 27 September 2007 (print version 25 September)

Use of templates within the citation template is discouraged because many of these templates will add extraneous HTML or CSS that will be included raw in the metadata. Also, HTML entities, for example,  , etc, should not be used in parameters that contribute to the metadata. Do not include Wiki markup  (italic font) or   (bold font) because these markup characters will contaminate the metadata.

COinS metadata is created for these parameters

 * periodical, journal, newspaper, magazine, work, website, encyclopedia, encyclopaedia, dictionary
 * chapter, contribution, entry, article, section
 * title
 * publication-place, publicationplace, place, location
 * date, year, publication-date, publicationdate
 * series, version
 * volume
 * issue, number
 * page, pages, at
 * edition
 * publisher, distributor, institution
 * url
 * chapter-url, chapterurl, contribution-url, contributionurl, section-url, sectionurl
 * author#, author-last#, author#-last, last#, surname#
 * author-first#, author#-first, first#, given#
 * any of the named identifiers (isbn, issn, doi, pmc, etc)


text: Template:Smallcaps

title: Template:Smallcaps


text:
Template:Smallcaps/doc

Smallcaps will display the lowercase part of your text as a soft format of typographical.

This template should be avoided or used sparingly, as the Manual of Style advises that small caps should be avoided and reduced to one of the other title cases or normal case and markup should be kept simple.

Usage
Your source text is not altered in the output, only the way it is displayed on the screen: a copy-paste of the text will give the small caps sections in their original form; similarly, an older or non-CSS browser will only display the original text on screen.

 * Code    :
 * Displayed:
 * Pasted  : Your Text in 4004 BC

This template is therefore intended for the use of caps as a typographic style, such as rendering family names in bibliographies in small caps to distinguish them from given names. It should not be used for acronyms or abbreviations which are supposed to be capitalized regardless of style. For such cases, use Smallcaps all.

Code examples
Note that most of these uses are not sanctioned by the [[WP:Manual of Style] and should be avoided in article prose.

Reasons to use small caps
Small caps are useful for encyclopedical and typographical uses including:

 * To lighten ALL-CAPS surnames mandated by citation styles such as Harvard
 * Piccadilly has been compared to "a Parisian boulevard" ( 1879).
 * , C., Jr (1879). "Piccadilly" in Dickens's Dictionary of London. London: C. Dickens.
 * To disambiguate Western names and surnames at a glance
 * Many Hispanic names are tricky to decompose:
 * Jorge Luis, but Adolfo (both filed under "B")
 * José, Marqués de los Trujillos
 * And many Hispanic names are better known by their second surname:
 * Pablo, Federico , Emir , José Luis
 * Many names (Martín, Miguel, Ramón, Tomás, etc.) can be either forename or surname:
 * Juan Martín vs. Rafael  (two ball players)
 * Hungarian names natively use the surname-first order:
 * Sándor is usually westernized Sándor
 * To disambiguate Eastern surnames and given names at a glance
 * Most Chinese names and Korean names retain their surname-first order:
 * Zedong fought Kai-shek
 * The movie Oldboy by Chan-wook starring  Min-sik was not seen by  Il-sung
 * Especially in Hong Kong and Macao, a Western given name may be added as well:
 * Leslie Kwok-Wing

 * Most Japanese names are reversed in the West, but not all:
 * (Akira or Motojirō  are usually westernized)
 * But Bashō,  no Komachi,  no Chiyo (haiku poets known under their given name)
 * But Ranpo (kept due to wordplay "EdgarA–llanPoe) vs. Ranpo  (some modern uses)
 * Burmese names ignore the concept of forename/surname, but are adapted in the West:
 * Daw Suu Kyi, daughter of General Aung San ("Daw" is honorific, her name take part of his name)
 * And some Burmese names are so short they need to retain an honorific prefix (U for Mister, Daw for Madam, Thakin for Master) which is confusable with a forename or a surname:
 * U ("Mister "), a.k.a. Thakin  ("Master ")

Technical
Technically, the template merely wraps the standard:

(The "font-variant:small-caps;text-transform:lowercase" has not been used because it does not work at least in Internet Explorer 5 and 6, which are still fairly common browsers.)

Suppressing small caps
If you wish to suppress the display of small caps in your browser, as a logged in user, you can make an edit to your common.css reading

span.smallcaps { font-variant: normal !important; }

title: Template:Smallcaps/doc


text: Template:COinS safe

title: Template:COinS safe


text:
Template:COinS safe/doc

Usage
This template is a notice for templates that may be used in citation templates. By default, it indicates the template is safe for use as shown above.

To indicate a template that should not be used in a citation template:

Issue
Citation templates such as and  generate COinS metadata. If a template is used in a citation template field, then it may inject HTML into the metadata.

Compare the rendered HTML for cite book with author using no template and using smallcaps.

The author metadata is in the rft.aulast field. In this case, it is percent-encoded and is rendered as

Reference management software will interpret the entire span as the author name.

title: Template:COinS safe/doc


text: Template:Smallcaps all

title: Template:Smallcaps all


text:
Template:Smallcaps all/doc

Usage
This template shows all text in as a hard format. That is, the caps are permanent, regardless of user preferences. For example:
 * →

The template performs two steps: bare text is changed into uppercase, and it is shown in small caps.

Difference from
The template is for soft formatting, which is more often what is desired. There are three differences between the templates:

1. All input text is shown in , not just the lowercase input. Compare:
 * →
 * →
 * Note that the initial full capitals are gone.

2. The bare, unstyled text is changed into uppercase. This is relevant for non-CSS browsers, and when one copy-pastes the page. Compare:
 * → . Copy-paste produces:
 * → . Copy-paste produces:

3. To maintain initial full capitals, a second parameter is to be used. Doing this has no effect on how text is displayed in non-CSS browsers and with copy-paste. Example:
 * → . Copy-paste produces:

Usage
This template should only be used for words, such as acronyms, that should be capitalized regardless of typographic style. Examples are and, which are stylistic variants of NASA and BC/AD.

It should not be used for things that are not inherently capitalized, such as the use of small caps to distinguish given from family names, because it makes the capitalization permanent, and the reader cannot override it. In such cases, the template smallcaps should be used instead.

To lighten ALL-CAP words, abbreviations, or acronyms, as a matter of typographic style
 * Examples
 * The initialism UNESCO (instead of UNESCO)
 * The trademark Time (magazine) (instead of TIME)
 * Dates such as 625

If the template is placed outside a link, it will capitalize the link itself, so in some cases it needs to be placed inside the link.

title: Template:Smallcaps all/doc


text: Template:Nocaps

title: Template:Nocaps


text:
Template:Nocaps/doc

 will display text in full lower case.

Usage
The source text will not be altered (copying/pasting the text will be presented in its original form), only in its browser display. You can use this template to control the display of the variable output of magic words and of other templates. Instead of HELLO you would have hello

Example

 * Code :
 * Result : thE NaMe oF thE GAME

Note
Substitution of this template is not recommended. The result will not create lower case source text but only an appearance thereof; the original text will wrapped in an HTML tag in the page source. Because of this, it would be more effective to simply edit the original text as lower case.

title: Template:Nocaps/doc


text:
Template:Allcaps/doc

 will display text in all capital letters.

Usage
will display your text in full upper case. Your source text is not altered (a copy-paste will give it in its original form), only the way it is displayed. You can use this template to control the display of the variable output of magic words and of other templates.

 * In:
 * Out:

Preferably do not subst: it because the result will NOT be an uppercase source text but the original text wrapped in HTML code making it appear uppercase, so it is more efficient for this purpose to simply rewrite the text in uppercase once and for all.

title: Template:Allcaps/doc


text: Template:Allcaps

title: Template:Allcaps


text:
Template:Aye/doc

Usage
a simple template to be used in various to-do lists for easier organization of solved and unsolved issues.

title: Template:Aye/doc


text: Template:Green

title: Template:Green


text:
Template:Green/doc

Usage
My  text. Produces:

My text.

title: Template:Green/doc


text: Template:Colors

title: Template:Colors


text:
Template:Colors/doc

Usage
Sets foreground and background colors of a given text. They can be specified by name or in the format #dddddd (RGB hex triplet).

Unless in the case of personal use on a user page, use this template with great caution:
 * a poor contrast may make the text difficult or impossible to read
 * the contrast can be experienced as even poorer in the case of color blindness
 * links have a color according to user settings; they become invisible if this color is equal to the background color.

Examples
gives:

gives:

gives:

gives:

gives:

gives:

gives:

Standard color names
The HTML 4.01 specification defines sixteen named colors, as follows:

title: Template:Colors/doc


text: Template:Hilite

title: Template:Hilite


text: Template:Hilite/core

title: Template:Hilite/core


text:
Template:Hilite/doc

For adding yellow highlight to specified text. The highlight color can be changed, and the highlight can also be set to expire at a certain date. Please keep template usage to talk pages only.

Usage

 * Parameters

 * text (parameter 1): Enter the text to be highlighted.

 * Optional parameters

These parameters are optional, but unused parameters must be separated by a pipe (see examples below):

 * color (parameter 2): Colors may be specified by word (e.g., "red", "blue", "lightgreen") or in hexadecimal format (e.g., "#FF0066", "#C0C0C0"). If no value is given for the color, the template defaults to yellow.

 * expiration (parameter 3): Highlights may be set to expire on a certain date, which leaves the text as-is, but removes the highlight color. The expiration value can be specified in any format.

title: Template:Hilite/doc


text:
Template:Bkg

Template shortcut for displaying some text or other element on a specified background color.

 * Syntax : or         to use default color (beige).

title: Template:Bkg


text: Template:TextColors

title: Template:TextColors


text:
Template:TextColors/doc

Usage
Guts:  {| style="background:;" |  |}

Sets foreground and background colors of a given text. They can be specified by name or in the format #dddddd (RGB hex triplet).

Unless in the case of personal use on a user page, use this template with great caution:
 * a poor contrast may make the text difficult or impossible to read
 * the contrast can be experienced as even poorer in the case of color blindness
 * links have a color according to user settings; they become invisible if this color is equal to the background color

Examples
gives:

gives:

gives:

gives:

gives:

gives:

gives:

Standard color names
The HTML 4.01 specification defines sixteen named colors, as follows:

title: Template:TextColors/doc


text: Template:Bg

title: Template:Bg


text:
Template:Bg/doc

This template can be used to create a background color for a span of text.

Usage
Alternatively, the attributes can be unnamed:

Web colors provides a list of colors which can be used. Simple colors, like black, blue, red, green, etc. can just be spelled out. Alternatively, colors can be specified using either RGB or hex notation.

title: Template:Bg/doc


text:
Template:Citation Style documentation/sep period

By default, sets of fields are terminated with a period (.).


text:
Template:Citation Style documentation/sep comma

By default, sets of fields are terminated with a comma.


text:
Template:Citation Style documentation/required

 * This parameter is required and will generate an error if not defined. On errors, main, help and template pages are placed into Category:Articles with incorrect citation syntax. Set true to disable categorization; mainly used for documentation where the error is demonstrated.


text:
Template:Citation Style documentation/author

 * last: Surname of a single author. Do not wikilink—use author-link instead. For corporate authors or authors for whom only one name is listed by the source, use last or one of its aliases (e.g. Bono). Aliases: surname, author, last1, surname1, author1.
 * author: this parameter is used to hold the complete name of a single author (first and last) or to hold the name of a corporate author. This parameter should never hold the names of more than one author.
 * first: Given or first names of author; for example: Firstname Middlename or Firstname M. or Firstname M., Sr. Do not wikilink—use author-link instead. Aliases: given, first1, given1. Requires last; first name will not display if last is empty.
 * OR: for multiple authors, use last1, first1 through last n , first n , where n is any consecutive number for an unlimited number of authors (each first n  requires a corresponding last n ). Aliases: surname1, given1 through surname n , given n , or author1 through author n .  For an individual author plus an institutional author, you can use ..........
 * author-link: Title of existing Wikipedia article about the author—not the author's website; do not wikilink. Aliases: author-link1, authorlink, authorlink1, author1-link, author1link.
 * OR: for multiple authors, use author-link1 through author-link n . Aliases: authorlink1 through authorlink n , or author1-link through author n -link, or author1link through author n link.
 * name-list-format: displays authors and editors in Vancouver style when set to  and when the list uses  /  parameters for the name list(s).
 * vauthors: comma-separated list of author names in Vancouver style; enclose corporate or institutional author names in doubled parentheses:
 * Smythe JB, ((Megabux Corp.))
 * author-link and author-mask may be used for the individual names in vauthors as described above
 * collaboration: Name of a group of authors or collaborators; requires author, last, or vauthors listing one or more primary authors; follows author name-list; appends "et al." to author name-list.
 * Note: When using or  styles with templates, do not use multiple names in one field, or else the anchor will not match the inline link.


text:
Template:Paren

Parenthetical referencing {{documentation|content=

Optional
For the first letter to be in lower case, use: y }}

title: Template:Paren


text:
Template:Citation Style documentation/coauthors

 * coauthors: Names of of coauthors. Use the same format as the authors.
 * When using or  styles with templates, do not use this parameter else the anchor will not match the inline link.


text:
Template:Citation Style documentation/editor

 * editor-last: Surname of editor. Do not wikilink—use editor-link instead. Where the surname is usually written first—as in Chinese—or for corporate authors, simply use editor-last to include the same format as the source. Aliases: editor-last1, editor1-last, editor-surname, editor-surname1, editor1-surname, editor, editor1.
 * editor: this parameter is used to hold the complete name of a single editor (first and last), or the name of an editorial committee. This parameter should never hold the names of more than one editor.
 * editor-first: Given or first names of editor, including title(s); example: Firstname Middlename or Firstname M. or Dr. Firstname M., Sr. Do not wikilink—use editor-link instead. Aliases: editor-first1, editor1-first, editor-given, editor-given1, editor1-given.
 * OR: for multiple editors, use editor-last1, editor-first1 through editor-last n , editor-first n  (Aliases: editor n -last, editor-surname n  or editor n -surname; editor n -first, editor-given n  or editor n -given; editor n ). For an individual editor plus an institutional editor, you can use ...... ....
 * editor-link: Title of existing Wikipedia article about the editor—not the editor's website; do not wikilink. Aliases: editor-link1.
 * OR: for multiple editors, use editor-link1 through editor-link n  (alias editor n -link).
 * name-list-format: displays authors and editors in Vancouver style when set to  and when the list uses  /  parameters for the name list(s)

 * veditors: comma separated list of editor names in Vancouver style; enclose corporate or institutional names in doubled parentheses:
 * Smythe JB ((Megabux Corp.))
 * editor-linkn and editor-maskn may be used for the individual names in veditors, as described above

 * editors: Free-form list of editor names; use of this parameter is discouraged; not an alias of editor-last
 * Display:
 * Use display-editors to control the length of the displayed editor name list and to specify when "et al." is included.
 * If authors: Authors are first, followed by the included work, then "In" and the editors, then the main work.
 * If no authors: Editors appear before the included work; a single editor is followed by "ed."; multiple editors are followed by "eds."


text:
Template:Citation Style documentation/others

 * others: To record other contributors to the work, such as "Illustrated by Smith" or "Trans. Smith".


text:
Template:Citation Style documentation/title italics

 * title: Title of source. Can be wikilinked to an existing Wikipedia article or url may be used to add an external link, but not both. Formatted in italics.
 * trans_title: If the source cited is in a foreign language, an English translation of the title can be given here. The template will display this in square brackets after the title field and it will link to the url field, if used. Use of the language parameter is recommended.
 * Titles containing certain characters will display and link incorrectly unless those characters are encoded.


text:
Template:Citation Style documentation/title quotes

 * title: Title of source. Can be wikilinked to an existing Wikiversity article or url may be used to add an external link, but not both. Formatted in quotes.
 * trans_title: If the source cited is in a foreign language, an English translation of the title can be given here. The template will display this in square brackets after the title field and it will link to the url field, if used. Use of the language parameter is recommended.
 * Titles containing certain characters will display and link incorrectly unless those characters are encoded.


text:
Template:Citation Style documentation/encyclopedia

 * encyclopedia: Title of source. Can be wikilinked to an existing Wikiversity article or url may be used to add an external link, but not both. Formatted in italics.
 * trans_title: If the source cited is in a foreign language, an English translation of the title can be given here. The template will display this in square brackets after the encyclopedia field and it will link to the url field, if used. Use of the language parameter is recommended.
 * Titles containing certain characters will display and link incorrectly unless those characters are encoded.


text:
Template:Citation Style documentation/work

 * work: Title of website; can be wikilinked to an existing Wikiversity article or url may be used to add an external link, but not both; formatted in italics.
 * trans_title: If the source cited is in a foreign language, an English translation of the title can be given here. The template will display this in square brackets after the work field and it will link to the url field, if used. Use of the language parameter is recommended.
 * title: Title of web page; formatted in quotes.
 * Titles containing certain characters will display and link incorrectly unless those characters are encoded.


text:
Template:Citation Style documentation/type

 * type: Provides additional information about the media type of the source. May alternatively be used to identify the type of manuscript linked to in the title, if this is not the final version of a manuscript (e.g. if a preprint of a manuscript is freely available, but the version of record is behind a paywall). Format in sentence case. Displays in parentheses following the title.  Alias: medium.


text:
Template:Citation Style documentation/opt

 * Options for this display:


text:
Template:Citation Style documentation/chapter

 * : The chapter heading of the source. May be wikilinked or may use chapter-url, but not both..
 * script-chapter: Chapter heading for languages that do not use a Latin-based alphabet (Arabic, Chinese, Cyrillic, Greek, Hebrew, Japanese, Korean, Vietnamese, etc); follows transliteration defined in chapter. Should be prefixed with an ISO 639-1 two-character code to help browsers properly display the script:
 * trans-chapter: English translation of the chapter heading, if the source cited is in a foreign language. Displays in square brackets after the  field; if chapter-url is defined, then trans-chapter is included in the link. Use of the language parameter is recommended.
 * trans-chapter: English translation of the chapter heading, if the source cited is in a foreign language. Displays in square brackets after the  field; if chapter-url is defined, then trans-chapter is included in the link. Use of the language parameter is recommended.


text:
Template:Citation Style documentation/journal

 * work: Name of the source periodical; may be wikilinked if relevant. Displays in italics. Aliases: journal, newspaper, magazine, periodical, website.
 * issue: When the publication is one of a series that is published periodically. Alias: number. When the issue has a special title of its own, this may be given, in italics, along with the issue number, e.g. 2, Modern Canadian Literature. following volume.
 * When set, work changes the formatting of other parameters:
 * title is not italicized and is enclosed in quotes.
 * chapter does not display in this citation template (and will produce an error message).
 * location and publisher are enclosed in parentheses.
 * page and pages do not show p. or pp.
 * edition does not display.


text:
Template:Citation Style documentation/edition

 * edition: When the publication has more than one edition; for example: "2nd", "Revised", and so forth. Appends the string " ed." after the field, so 2nd produces "2nd ed." Does not display if a periodical field is defined.


text:
Template:Citation Style documentation/series

 * series or version: When the source is part of a series, such as a book series or a journal where the issue numbering has restarted.


text:
Template:Citation Style documentation/series episode

 * series: The name of the series the episode belongs to; may be wikilinked.


text:
Template:Citation Style documentation/event

 * event: Event where the speech was given.


text: Wikiversity:Metrics/metrics

title: Wikiversity:Metrics/metrics


text:
Template:Citation Style documentation/agency

 * agency: The news agency (wire service) that provided the content; examples: Associated Press, Reuters, Agence France-Presse.


text:
Template:Citation Style documentation/volume

 * volume: For one publication published in several volumes. Displays after the title and series fields;


text:
Template:Citation Style documentation/date

 * date: Date of source being referenced. Can be full date (day, month, and year) or partial date (month and year, season and year, or year). Use same format as other publication dates in the citations. Required when year is used to disambiguate links to multiple-work citations by the same author in the same year.$[more]$ Do not wikilink. Displays after the authors and is enclosed in parentheses. If there is no author, then displays after publisher.
 * For approximate year, precede with " ", like this: c. 1900.

 * For no date, or "undated", add as n.d.

 * year: Year of source being referenced. Use of date is recommended unless all of the following conditions are met:
 * The template uses harv, or the template is, or cs2
 * The date format is YYYY-MM-DD.
 * The citation requires a  disambiguator.
 * df: date format; sets rendered dates to the specified format; does not support date ranges or seasonal dates. Accepts one value which may be one of these:
 * – set publication dates to day month year format; access- and archive-dates are not modified;
 * – as above for month day, year format
 * – as above for year initial numeric format YYYY-MM-DD
 * – set publication, access-, and archive-dates to day month year format;
 * – as above for month day, year format
 * – as above for year initial numeric format YYYY-MM-DD


text:
Template:Citation Style documentation/publisher

 * publisher: Name of publisher; may be wikilinked if relevant. The publisher is the that publishes the work being cited. Do  use the publisher parameter for the name of a work (e.g. a website, book, encyclopedia, newspaper, magazine, journal, etc.). Corporate designations such as "Ltd", "Inc.", or "GmbH" are not usually included. Not normally used for periodicals. Omit where the publisher's name is substantially the same as the name of the work (for example, The New York Times Co. publishes The New York Times newspaper, so there is no reason to name the publisher). Displays after title.
 *  place: Geographical place of publication; generally not wikilinked; omit when the name of the work includes the location; examples: The Boston Globe, The Times of India. Displays after the title. Alias: location
 * publication-place: If any one of publication-place, place, or location is defined, the location will show after the title; if publication-place and place or location are defined, then place or location is shown before the title prefixed with "written at" and publication-place is shown after the title.
 * publication-date: Date of publication when different from the date the work was written. Displays only if year or date are defined and only if different, else publication-date is used and displayed as date. Use the same format as other dates in the article; do not wikilink. Follows publisher; if work is not defined, then publication-date is preceded by "published" and enclosed in parenthesis.
 * via: Name of the content deliverer (if different from publisher). via is not a replacement for publisher, but provides additional detail. It may be used when the content deliverer presents the source in a format other than the original (e.g. NewsBank), when the URL provided does not make clear the identity of the deliverer, where no URL or DOI is available (EBSCO), or if the deliverer requests attribution.


text:
Template:Para/doc

Usage
This template is for giving examples of template parameter source code (useful in template documentation and talk page discussions of template code). It must have one or two parameters itself. The first is the name of the example parameter to display (this may be empty, but it must be present), and the second (optional) one is a value for the first example parameter, or (if the first parameter is empty) an unnamed example parameter.

Examples

 * renders as
 * name
 * renders as
 * book title
 * renders as
 * section
 * (for unnamed parameters in the example code; note the empty first parameter in the template)
 * renders as
 * value
 * (for unnamed parameters in the example code; note the empty first parameter in the template)
 * renders as
 * value
 * value

When using literal, pre-specified values, simply provide the value (appearance as in example 3). When illustrating hypothetical, variable or user-definable values, use value (appearance as in example 2), and the same should be done for non-literal, example parameters (as in example 4).

title: Template:Para/doc


text:
Template:Citation Style documentation/publisher periodical

 * publisher: Name of publisher; corporate designations such as "Ltd" or "Inc" are not usually included; may be wikilinked if relevant; formatted in parentheses with location.
 * location: Geographical place of publication; generally not wikilinked.
 * publication-date: Date of publication, if different from date written; shows only if year or date are defined and only if different; use the same format as other dates in the article; do not wikilink.


text:
Template:Citation Style documentation/newsgroup

 * newsgroup: Name of newsgroup; a link is automatically created; do not wikilink.


text:
Template:Citation Style documentation/language

 * language: The language in which the source is written. Displays in parentheses with "in" before the language name or names. Use the full language name or ISO 639-1 code. When the source uses more than one language, list them individually, separated by commas, e.g. French, German. The use of language names or language codes recognized by Wikimedia adds the page to the appropriate subcategory of ; do not use templates or wikilinks. Note: When the language is "English" (or "en"), no language is displayed in the citation. Note: When two or more languages are listed there is no need to include "and" before the last language. "and" is inserted automatically by the template.


text:
Template:Citation Style documentation/pages

 * page: The number of a single page in the source that supports the content. Use either page or pages, but not both. Displays preceded by p. unless y.
 * OR: pages: A range of pages in the source that supports the content. Use either page or pages, but not both. Separate using an en dash (–); separate non-sequential pages with a comma ; do not use to indicate the total number of pages in the source. Displays preceded by pp. unless y. Hyphens are automatically converted to en dashes; if hyphens are appropriate, for example: pp. 3-1–3-15, use 31&ndash;315 or pp. 3-1&ndash;3-15.
 * nopp: Set to y, yes , or true to suppress the p. or pp. notations where this is inappropriate; for example, where Front cover or passim.
 * OR: at: For sources where a page number is inappropriate or insufficient. Overridden by page or pages. Use only one of page, pages, or at.
 * Examples: page (p.) or pages (pp.); section (sec.), column (col.), paragraph (para.); track; hours, minutes and seconds; act, scene, canto, book, part, folio, stanza, back cover, liner notes, indicia, colophon, dust jacket, verse.


text:
Template:Citation Style documentation/pages periodical

 * page: Page in the source that supports the content; preceded with p. unless y or journal, periodical, magazine or para are defined.
 * OR: pages: Pages in the source that supports the content; separate page ranges with an en dash (–); separate non-sequential pages with a comma ; do not use to indicate the total number of pages in the source; preceded with pp. unless y or journal, periodical, magazine or para are defined.
 * nopp: Set to y to suppress the p. or pp. notations where this is inappropriate; for example, where Front cover.
 * OR: at: For sources where a page number is inappropriate or insufficient; overridden by page or pages.
 * Examples: page (p.) or pages (pp.); section (sec.), column (col.), paragraph (para.); track; hours, minutes and seconds; act, scene, canto, book, part, folio, stanza, back cover, liner notes, indicia, colophon, dust jacket, verse.


text:
Template:Code/doc

Usage
Wraps a short span of text in  tags (see mw:Extension:SyntaxHighlight GeSHi). This template should be used for short samples; longer content should use  or . See Help:Wiki markup for an explanation of what the various tags do.

If the content includes an equals sign (=), you must specify the parameter explicitly:.

The template uses the  tag with the attribute. This works like the combination of the  and   tags, applied to the expanded wikitext. For example,  will not render the word "wiki" in bold, and will render the tripled-single-quotes:

 * some wiki text

However,  will still invoke the template:

 * a call

Use  around the template name to avoid this problem:

 * a call

When used inline with regular text, generally looks best and is easiest to read when it is explicitly spaced apart from the regular text:
 * foo bar baz quux.

is well spaced:
 * foo bar baz  quux.

versus:
 * foo bar baz quux.

which is going to be visually confusing for many:
 * foo bar baz quux.

because "foo" and "bar" will seem more closely associated than "bar" and "baz"; the width of the space character in a monospaced font is almost always larger than in a proportional font.

Use parameter (unnamed, as 2, or more explicitly as lang) to specify a language for Extension:SyntaxHighlight GeSHi. This option defaults to plain-text, i.e. no highlighting. There is no highlighting option for wikitext as a markup language, though html4strict and html5 are valid values, as are php, perl, css, javascript, mysql and many others. Attempting to use an invalid one causes a list of valid ones to be displayed in place of the template output, when the page is previewed or saved.

This template does not need to be substituted.

Finally, embedded templates do not function inside ; for longer, free-form blocks of code, which can contain templates such as and, use  as a wrapper instead of this template.

title: Template:Code/doc


text:
Template:Semantic templates see also

 * strong – for semantically indicating strong emphasis instead of simple typographical boldfacing
 * strongbad – same as but red like this: Never use  in articles.
 * stronggood – same as but green like this: Only use  on non-article pages.
 * em – similar template for semantically indicating mild emphasis instead of simple typographical italicization
 * var – same as varserif use for all variables other than I (upper-case i) and l (lower-case L), for which use varserif
 * varserif – same as var but uses serif font, especially for distinguishing between I (upper-case i) and l (lower-case L) as variables
 * wikivar – for displaying wikicode variables and magicwords as they would appear in source code, e.g. ,
 * para – for displaying wiki template parameters (title) or parameters and values (2008)
 * tlx and related – for displaying entire templates (with or without parameters and values) as code
 * tag – for using HTML elements ("tags") in prose, e.g. source code examples
 * code – for computer source code ( and other templates cannot be used inside it; in that case use  as the wrapper, not )
 * syntaxhighlight or sxhl – wrapper for , but will wrap overflowing text
 * deprecated code or dc – for deprecated source code in template documentation, articles on HTML specs, etc.
 * pre – for larger blocks of source code and other pre-formatted text
 * bq – for indented blocks of content, such as block quotations, examples, poems, etc.
 * kbd – for indicating user input
 * key press – for indicating the input of specific keystrokes, e.g. CtrlX
 * PlayStation key press – for indicating PS-style gamepad key presses, e.g.
 * samp – for example output

title: Template:Semantic templates see also


text:
Template:Semantic templates see also/doc

Usage
This documentation sub-template is for transclusion in the "See also" sections of the main templates of Category:Semantic markup templates. There are no parameters:


text: Liberté (game)/personalities/metrics

title: Liberté (game)/personalities/metrics


text: Template:Strong

title: Template:Strong


text:
Template:Strong/doc

Purpose
This template make it faster and easier to apply 's  markup to text, and more importantly to indicate to human and bot editors they should not use   or  typographic boldfacing to replace the intentional and semantically meaningful. Strong emphasis is usually rendered visually in a bold (heavy) typeface by default on graphical browsers, but can be parsed and acted upon in customizable ways with style sheets, apps and text-to-speech screen readers. It is said to be semantic markup, i.e. markup that conveys meaning or context, not just visual appearance. Simple boldfacing is purely typographic and is semantically meaningless. It is most often used for headings, but has a few other uses (such as for book or film titles and the like, which are usually italicized, when they appear in an already-italicized passage). The average reader, and average editor, do not and need not care about this distinction most of the time, but it can be important and editors who understand it can use this template as a baseline insurance against accidental or careless replacement by bots and human editors.

Usage

or, if the text to be emphasized contains an equals sign:

These both render as:

This template puts intentional and explicit  (strong emphasis) [X]HTML markup around the text provided as the first parameter. It is safest to always use the 1 syntax.

Optional parameters
Advanced HTML values can be passed through the template to the HTML code:
 * class takes a class name (or multiple class names, separated by commas); adds  to the HTML code
 * style takes inline CSS input; addes  to the HTML code
 * id takes a valid, unique HTML id (must begin with an alphabetic letter); adds  to the HTML code
 * title takes text, which cannot be marked up in any way, and displays it as a pop-up "tooltip" when the cursor hovers over the span

Use cases
This template is made to strongly emphasize important words or phrases in a text, in a way that is (unlike simply boldfacing it) semantically meaningful markup. With this technique, the emphasized text strongly stands out from the rest in most if not all visual browsers and some text-to-speech screen readers (which usually ignore purely typographic boldfacing), and can also be parsed by user agents and other software as definitively indicating emphasis, not just some typographic boldface effect for appearance's sake. It should therefore only be used very sparingly in articles to highlight the most important words or phrases in the entire article (and, rarely in encyclopedic writing, to represent strong vocal emphasis). Use of this template has a strong effect on scannability, drawing the eye from elsewhere on the page to words marked up with the template.

Typical uses on Wikiversity:
 * In the lead section of an article, the article's title and its synonyms be emphasized with . Example: "The, or , or , is the bulbous end of a neuron."  , this is not yet common, but users should not revert it (nor criticize anyone for not using it).
 * After the lead, it be used to highlight crucial terms of importance only slightly secondary to that of the article title and its synonyms. For example, the article on a viral infection might use  to highlight the names of two identified strains of the disease in a "Varieties" section, as an aid to scannability.
 * In unusual cases (most often direct quotations) it is used to represent text that would be strongly emphasized for contextual reasons if the passage were spoken rather than written (e.g., because it indicates shouting).
 * Outside of articles, it be used (but  isn't yet common) in polls, XfD processes, RfX votes, and similar comments and debates where users indicate that they approve of or disagree with a view or proposal. Example: ", because of this and that reasons [...]" or ", because of this and that reasons [...]".

When this template should not be used
Because is strictly for semantic (meaningful) emphasis, it should not be used for layout, typography conventions and such. In these different cases, bold  (which resolves to  in the browser or other user agent) should be used instead. It should also not be used when the text to which it is applied is already boldfaced for some other reason (e.g., it is part of a heading); in such cases use instead. Avoid using in non-quoted sentences that end in an exclamation point. And it is usually excessive to use it on terms that are already wikilinked, since the link markup acts as a form of emphasis itself.

title: Template:Strong/doc


text: Template:Strongbad

title: Template:Strongbad


text:
Template:Strongbad/doc

Usage
This template is used to insert a quick and easy warning or negative notice with high visibility (because it is red) on project and discussion pages (like the following sentence). This template cannot be used in articles. In situations where color is not relevant (color blindness, screen readers, etc.), it renders exactly the same as strong (to which it is a CSS-styled call).

or, if the text to be emphasized contains an equals sign:

These both render as:

 * text to be emphasized

It is safest to always use the 1 syntax.

This template puts intentional and explicit  (strong emphasis) [X]HTML markup around the text provided as the first parameter.

Because some people are color blind, and some use screen readers, this template should not be used in a manner in which only the color indicates the difference between the content being marked up and other content; it's simply a visual aid for those who can use it.

Parameters
See Template:Strong.

title: Template:Strongbad/doc


text: Template:Stronggood

title: Template:Stronggood


text:
Template:Stronggood/doc

Usage
This template is used to insert a quick and easy positive notice with high visibility (because it is green) on project and discussion pages (like the following sentence). Only use this template on non-article pages. (It cannot actually be used in articles; it will generate an error.) In situations where color is not relevant (color blindness, screen readers, etc.), it renders exactly the same as strong (to which it is a CSS-styled call).

or, if the text to be emphasized contains an equals sign:

These both render as:

 * text to be emphasized

It is safest to always use the 1 syntax.

This template puts intentional and explicit  (strong emphasis) [X]HTML markup around the text provided as the first parameter.

Because some people are color blind, and some use screen readers, this template should not be used in a manner in which only the color indicates the difference between the content being marked up and other content; it's simply a visual aid for those who can use it.

Parameters
See Template:Em.

title: Template:Stronggood/doc


text: Template:Em

title: Template:Em


text:
Template:Em/doc

Purpose
This template makes it faster and easier to apply [X]HTML's  markup to text, and more importantly to indicate to human and bot editors they should not use   or  typographic italicization to replace the intentional and semantically meaningful. Strong emphasis is usually rendered visually in an italic (oblique a.k.a. slanted) typeface by default on graphical browsers, but can be parsed and acted upon in customizable ways with style sheets, apps and text-to-speech screen readers. It is said to be semantic markup, i.e. markup that conveys meaning or context, not just visual appearance. Simple italicizing is purely typographic and is semantically meaningless. It is most often used for titles publications (books, films, albums, etc.), foreign words and phrases, words as words (when quotation marks are not used for that purpose), names of ships, scientific names of organisms and other cases where stylistic conventions demand italics, but they convey no sense of emphasis. The average reader, and average editor, do not and need not care about this distinction most of the time, but it can be important and editors who understand it can use this template as a baseline insurance against accidental or careless replacement by bots and human editors.

Usage

or, if the text to be emphasized contains an equals sign:

These both render as:

This template puts intentional and explicit  (emphasis) [X]HTML markup around the text provided as the first parameter. It is safest to always use the 1 syntax.

Optional parameters
Advanced HTML values can be passed through the template to the HTML code:
 * class takes a class name (or multiple class names, separated by commas); adds  to the HTML code
 * style takes inline CSS input; addes  to the HTML code
 * id takes a valid, unique HTML id (must begin with an alphabetic letter); adds  to the HTML code
 * title takes text, which cannot be marked up in any way, and displays it as a pop-up "tooltip" (in most browsers) when the cursor hovers over the span

Use cases
This template is made to mildly emphasize an important word or phrase in a passage, in a way that is (unlike simply italicizing it) semantically meaningful markup. With this technique, the emphasized text stands out from the rest of the nearby text in most if not all visual browsers and some text-to-speech screen readers (which usually ignore purely typographic italicization), without strongly affecting scannability. It can also be parsed by user agents and other software as definitively indicating emphasis, not just some typographic boldface effect for appearance's sake. It should therefore only be used sparingly in articles, to highlight something being stressed (e.g., to represent strong vocal emphasis). Example:

"Contrary to reports, she was dead after all."

It is also occasionally used for disambiguation, e.g. between two adjacent but different uses of the same word or homonym ("What it is a kind of custard.), but this usage is not often encyclopedic and can (when not found in a direct quotation) usually be rewritten to avoid the awkward construction.

When this template should not be used
Because is strictly for semantic (meaningful) emphasis, it should not be used for layout, typography conventions (titles, foreign words, etc.), and other cases that are not true emphasis. In these different cases, italics wikicode  (which resolves to  in the browser or other user agent) should be used instead (or special markup for a particular case, such as   or  for variables in computer science and mathematics). It should also not be used when the text to which it is applied is already italicized for some other reason (e.g., it is part of a book title); in such cases use instead. Usually avoid using in non-quoted sentences that end in an exclamation point. And it is usually excessive to use it on terms that are already wikilinked, since the link markup acts as a form of emphasis itself.

But careful, Em is strictly for emphasis. It should not be used for layout, typography conventions, books and such. In these different cases, italics  or  should be used instead:
 * "The New York Times is an American daily newspaper." This example should use  or an equivalent.

title: Template:Em/doc


text: Template:Var

title: Template:Var


text:
Template:Var/doc

Usage
This template is to help facilitate the displaying of variable names (in mathematics, computer source code, etc.) with the semantically correct, which also renders the variable in italics, as is customary. This method is preferred to simply italicizing, for accessibility, content/presentation separation, semantic Web, and metadata reasons; [X]HTML's  element has semantic meaning, while simple italicization does not.

Example:

outputs

which renders as:

 * username

compare to simple  italicization:

 * username

When used alone as variables, the letters "I" (upper-case "i") and "l" (lower-case "L") should be rendered with instead of, to make them more distinguishable: ,.

title: Template:Var/doc


text:
User:Lull3rSkat3r

Social Media
Facebook Twitter Google+

title: User:Lull3rSkat3r


text: Template:Varserif

title: Template:Varserif


text:
Template:Varserif/doc

Usage
This template is to help facilitate the displaying of variable names (in mathematics, computer source code, etc.) with the semantically correct, which also renders the variable in italics, as is customary, and to do so in a serif font. This is specifically for the use of the characters "I" (upper-case i) and "l" (lower-case L), which in many sans-serif fonts can be difficult to distinguish. The template also very slightly adjusts the font size of the enclosed variable, to account for typical difference in x-height between non-fancy serif (e.g., Times and Times New Roman) and sans-serif (e.g. Arial and Helvetica) typefaces. The template should not be used generally, but only for "I" and "l", and perhaps other cases where a known visual ambiguity can be shown to exist in common sans-serif fonts for readers without acute vision. It is recommended to use rather than  for "1" (numeral one), as it is usually more clearly distinguishable from "I" and "l" in sans-serif than serif fonts.

need not be used for variables that simply contain "I" or "l", only for cases in which readers are likely to be unable to distinguish them visually.

The method is preferred to simply italicizing and using inline style to specify the font, for accessibility, content/presentation separation, semantic Web, and metadata reasons; XHTML's   element has semantic meaning, while simple italicization does not.

Because the font styling in the template is done entirely with CSS, it has no effect at all upon content semantics, nor does it change the output for users of screen reader software.

Example:

outputs

which renders as:

 * Comparisons:

 * = I
 * = l
 * = 1

Please note that is not a panacea – it's treatment of the numeral "1" is easily mistaken for the letter "l" (lower-case "L") in many serif fonts.

 * Recommended usage:

 * = 1
 * for any other variable
 * = 1
 * for any other variable

title: Template:Varserif/doc


text:
Template:Wikivar

Usage
This template is to help facilitate the displaying of Wikiversity variables and built-in "magicword" (pseudo-template) names, and optionally their  as well. The variable/magicword names are automatically put into all-upper-case.

 * Examples:

and

displays as:

A second parameter can be added; this is the part followed by a colon in some usages:

displays as:

title: Template:Wikivar


text: Template:Syntaxhighlight

title: Template:Syntaxhighlight


text:
Template:Syntaxhighlight/doc

Simple wrapper around the  tag to show syntax-highlighted text. Unlike, text that does not fit on the screen will be wrapped.

Usage
undefined

For example:

undefined

undefined

Parameters

 * lang:

Examples
undefined

title: Template:Syntaxhighlight/doc


text: Template:Template redirects

title: Template:Template redirects


text: Template:Deprecated code

title: Template:Deprecated code


text:
Template:Deprecated code/doc

Usage
This template (easiest used from its dc redirect) can be used to indicate, e.g. in template documentation or Wikipedia articles on things like HTML specifications, code that has been deprecated and should not normally be used. On the technical level it is a CSS-styled  that greys out the text (the near-universal sign in computing and computing documentation for "doesn't work", "don't do this", "bad code", "ignore", "option not available", etc.), and removes that element's usual strikethrough (CSS: "line-through") rendering, which makes the content hard to read. If you really want that line-through, use the dc2 variant ; it is otherwise identical.

Parameters

 * 1  the content to be marked as deprecated
 * 2 or title a mouse-over "tooltip" (in some browsers, anyway), e.g. for briefly explaining the deprecation, e.g. "Deprecated since HTML 3.0" or "Breaks infobox formatting"
 * y  make the text red instead of grey, for indicating dangerous/error/forbidden things
 * class  assign a CSS class
 * id  assign an HTML ID for #linking and other purposes (must be unique on the page and start with an alphabetic letter)
 * style  add additional CSS styling (can be used to add   back in if you want that formatting; a shortcut for this is )

title: Template:Deprecated code/doc


text: Template:Documentation/preload

title: Template:Documentation/preload


title: Template:Dc2


text: Template:Xtd

title: Template:Xtd


text:
Template:Pre

pre

title: Template:Pre


text:
Template:Pre/doc

This template implements a version of the functionality provided by the HTML    tag.

Usage
This Pre-format

can look

like this.

Main differences include:

 * It wraps text that overflows the page.
 * It allows mid-line-breaks (but not always consistently).

Main limitations include:

 * If the text is a single long word, it won't be wrapped and will still break out to the right hand of the page.
 * HTML and wikimarkup aren't disabled as in pre and are rendered as usual (thus if a parameter contains any wikitext, enclose it in     tags); similarly, multiple spaces are treated as a single one.
 * If there are only two lines, they will be stuck together, even if the source has a blank line between them.

As with, , and ,  displays text in the font specified as the monospace font in the user's browser options, or specified in the user's CSS pages.

Example

 * Code

First line, markup working: and HTML comment hidden.

Second line, long text wrapping: all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy.

'''Third line with raw

 * Result

First line, markup working: and HTML comment hidden.

Second line, long text wrapping: all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy all work and no play make jack a dull boy.

'''Third line with raw

Alternatives

 * The <source> tag extension documented at MediaWiki Extension:ASHighlight.
 * The {{#tag:}} functionality documented at MediaWiki Help:Magic words.

title: Template:Pre/doc


text: Template:Table

title: Template:Table


text:
Template:Table/doc

Usage
content

title: Template:Table/doc


text: Template:Bq

title: Template:Bq


text:
Template:Bq/doc

Usage
This template is to help facilitate the indentation of blocks of content (quotations, computer source code, etc.) with the semantically correct  element, which can also be further styled and given metadata. This method is often preferred to using wikimarkup's ";" indentation (actually an abuse of  code), and other means that can cause problems or which are complicated and error-prone, and for accessibility, content/presentation separation, semantic Web, and metadata reasons; [X]HTML's element has semantic meaning, while many tricks for indenting do not, or even have incorrect semantics.

Example:

which renders as:

compare to the longwinded  markup:

""

Parameters

 * text or quote or 1 (required) the content of the indented block; it is always safest to specify this parameter explicitly, as it will otherwise break if the content ever contains the "=" character, and can also fail under other technical circumstances
 * class an additional CSS class; it already uses  by default
 * id an identifier, which can be used as a link target or for other purposes, e.g. custom user scripts; it must begin with a letter, not a number or symbol, and be unique on a page
 * style inline CSS directives for custom styling, like background color
 * title metadata that indicates a title or label for the element; different browsers handle this differently, most often as a pop-up "tooltip" on mouseover.

Cited quotations
For use with cited quotations, supports the sourcing parameters (and their aliases) of the older and simpler  templates and the frequently abused, so  can be used as a drop-in replacement for them that provides the above additional features. Conversion from several other templates, including and, even , is trivially easy. Converting from requires deletion of its first parameter, which is always   or   and then the rest of its data will just work without modification. Such conversions of course lose features (decoration, etc.) of many of those templates, but sometimes that is precisely what is desired.

 * 2 or sign or cite or author or by author/speaker of the quotation; this is free-form text and can including a link to the author's article.
 * 3 or source or ts source from which the quotation is drawn; this is free-form text and can including links, styling, etc.; if converting from, the author would also be included in source, but should really be moved manually to the above parameter.
 * 4 or diff optionally, you can divide the citation up further, e.g. Lastname, Firstname"Article Title"Book Title, but this is not really necessary, and is mainly to make conversion from a little easier. Parameter 4 is automatically italicized, since it is only used for larger works like books, albums, magazines, or TV shows. It also maps to diff for conversion of.

Examples:

Working around display problems
Complex markup may require a simple trick to work around a longstanding MediaWiki bug; this is the inclusion of the code  immediately after the 1 (or text if the content following the   begins with a linebreak:
 * Lists and other complexities

This tweak unfortunately cannot be put into the template code itself, as the nowiki markup doesn't pass through the transclusion process.

 * Multiple paragraphs

Make sure that all the parameters are named (e.g. 1, etc. or with word names like source). Many URLs, and plenty of other things, contain the "=" character, which due to MediaWiki limitations, will cause the template to malfunction if used in an unnamed parameter.
 * URLs and other breakage

title: Template:Bq/doc


text: Template:Quote box

title: Template:Quote box


text:
Template:Quote box/doc

Usage
The  template allows you to easily put a quote (and its source) inside a box, with flexible control over bordering, background color, alignment, and other features. The box itself is floating div, which (like images) can appear on the right or left or across the entire page. Article text will wrap around the div in the first two cases. This is useful in articles that are short on images and need some graphic-like element, or where an important or interesting quote wants to be presented in a way that sets it off from the surrounding text.

Caution: this is a div-based template, and may break if indented using wikitext syntax. This is a current limitation of the Wikiversity HTML parsing software.

Parameters
Basic parameters
 * title = Optional title to appear at the top of the quote box
 * quote = The quote or text to be displayed in the box
 * source = Optional source of the quote (author, publication, etc.)

Main box styling
 * align - Alignment of the quote box on the page - left/right/center/none. Defaults to right alignment.
 * width - The width of the quote box. Defaults to the width of the quote included, unless center where the width will default to 100%.
 * border - The width of the quote box border. Defaults to 1px.  Remember to include 'px' or 'em' to specify the correct width.
 * fontsize - The fontsize of the quote box text. Defaults to 88%.
 * bgcolor - The RGB background color of the box. Defaults to #F9F9F9 (light gray)
 * style - A generic CSS style parameter. Entries in this parameter supersede any duplicates in the preceding parameters

Title styling
 * title_bg - The RGB background color of the title. Defaults to #F9F9F9 (light gray)
 * title_fnt - The title font color. Defaults to black
 * tstyle - A generic CSS style parameter. Entries in this parameter supersede any duplicates in the preceding title parameters

Quote styling
 * qalign - Alignment of the quote element - left/right/center. Defaults to left
 * qstyle - A generic CSS style parameter. Entries in this parameter supersede any duplicates in the preceding quote parameters
 * quoted - If this parameter evaluates to true (is not 0, false, or empty) the quote box will enclose the quote in fat-quotes. Use judiciously, and read the Manual of Style.

Source styling
 * salign - Alignment of the source element - left/right/center. Defaults to the value of qalign.
 * sstyle - A generic CSS style parameter. Entries in this parameter supersede any duplicates in the preceding source parameters

Full syntax

Examples
Various example codes and their results. For more intricate examples see Template:Quote_box/examples

Floating and wrapping
Minimal code, defaults to floating right and minimal width:

Floating right:

Floating left:

Centered (but not floating any more):

Fat-quotes
Using fat-quotes:

quote alignment

title: Template:Quote box/doc


text:
Template:Quotation templates see also

 * Template:Bq – quote without border, page-wide; like (and compatible with parameters of) the older Quote but with more features; conversion from all others listed here is trivially easy (retaining key data, losing decoration, etc.)
 * Template:Quote – quote without border, page-wide, smaller-sized attribution
 * Template:Quotation – quote with border, page-wide
 * Template:Quote box – quote with border, in a reduced floating box
 * Template:Cquote – pull-quote between large quotation marks, page-wide; should rarely be used in articles and is not for block quotations, only pull quotes
 * Template:Rquote – pull-quote between large quotation marks, in a reduced floating area; also rarely appropriate in articles
 * Template:Talkquote – for quoting other editors (or guidelines, etc.) on talk pages (in a block)
 * Template:Tq - for quoting on talk pages, inline
 * Category:Quotation templates

title: Template:Quotation templates see also


text:
Template:Quotation templates see also/doc

Usage
This documentation sub-template is for transclusion in the "See also" sections of the main templates of Category:Quotation templates. There are no parameters:


text: Template:Quote box/sandbox

title: Template:Quote box/sandbox