Difference between revisions of "Template:Rp/doc"
Shawndouglas (talk | contribs) (Created as needed.) |
Shawndouglas (talk | contribs) m (Updated to resolve citation issue) |
||
Line 44: | Line 44: | ||
===Missing page numbers=== | ===Missing page numbers=== | ||
If a reference needs a page number but it is missing, use <code>{{tlx|rp|needed=y|<nowiki>{{subst:DATE}}</nowiki>}}</code> or <code>{{tlx|rp|needed=y|date={{CURRENTMONTHNAME}} {{CURRENTYEAR}}}}</code>. This will automatically use the {{tlx|page needed}} template to add the article to [[:Category:LIMSwiki articles needing page number citations|the appropriate category]]. For example, <code><nowiki><ref name=" | If a reference needs a page number but it is missing, use <code>{{tlx|rp|needed=y|<nowiki>{{subst:DATE}}</nowiki>}}</code> or <code>{{tlx|rp|needed=y|date={{CURRENTMONTHNAME}} {{CURRENTYEAR}}}}</code>. This will automatically use the {{tlx|page needed}} template to add the article to [[:Category:LIMSwiki articles needing page number citations|the appropriate category]]. For example, <code><nowiki><ref name="aardvark"/></nowiki>{{tlp|rp|needed{{=}}y|date{{=}}November 2012}}</code> results in: <ref name="aardvark"/><!--(this ref already defined in previous section)-->{{fix|link=LIMSWiki:Citation guidelines|text=page needed}} | ||
This is preferable to something like <code>{{tlx|rp|page number?}}</code> or <code>{{tlx|rp|?}}</code>, since the cleanup categorization takes place. It is preferable to simply using {{tlx|page needed}} in articles that make use of {{tlx|rp}}, since it preserves the use of the {{tlx|rp}} syntax. | This is preferable to something like <code>{{tlx|rp|page number?}}</code> or <code>{{tlx|rp|?}}</code>, since the cleanup categorization takes place. It is preferable to simply using {{tlx|page needed}} in articles that make use of {{tlx|rp}}, since it preserves the use of the {{tlx|rp}} syntax. | ||
Do not nest the {{tlx|page needed}} template inside the {{tlx|rp}} template; doing so introduces a stray colon and the displayed results are too small to be legible to many readers. For instance, <code><nowiki><ref name=" | Do not nest the {{tlx|page needed}} template inside the {{tlx|rp}} template; doing so introduces a stray colon and the displayed results are too small to be legible to many readers. For instance, <code><nowiki><ref name="aardvark"/></nowiki>{{tlp|rp|{{tlp|page needed|date{{=}}November 2012}}}}</code> results in the undesirable: <ref name="aardvark"/>{{rp|{{fix|link=LIMSWiki:Citation guidelines|text=page needed}}}} | ||
===A note on spacing=== | ===A note on spacing=== |
Latest revision as of 20:43, 19 September 2021
This is a documentation subpage for Template:Rp. It contains usage information, categories, interlanguage links, and other content that is not part of the original template page. |
Function
"Rp" stands for "Reference page/s". This is a relatively uncommon method of citing page numbers, usually used when other methods produce undesirable results.
Use this template when you are referring to specific pages within a source which is cited many times in the same article. The following example sentence shows the formatting produced by
<ref name="aardvark">
... details of cited source ...</ref>{{rp|23}}
which would be used to refer to a fact on page 23 of reference [1]:
- Apples should be eaten when they are ripe.[1]:23
This second example sentence shows the formatting produced by
<ref name="aardvark"/>{{rp|56}}
which would be used as citation for a statement supported by a fact on page 56 of the same reference [1], which will appear only once in the list of references:
- Porridge, usually eaten for breakfast, can also serve as a dessert.[1]:56
This template is for appending page numbers to notes. It is an alternative that can be used in articles with one or several sources that must be cited a large number of times, at numerous different pages. It is an alternative to the more common method of using shortened footnotes that does not require the reader to follow two links to see the source.
Notice
This template should not be used unless necessary. In the vast majority of cases, citing page numbers in the <ref>...</ref>
code is just fine. This template is only intended for sources that are used many times in the same article, to such an extent that normal citation would produce a useless line in <references />
or too many individual ones.
Overuse of this template is seen by some editors as making prose harder to read. Used judiciously, however, other editors say that it is less interruptive to the visual flow than complete implementation of the reference citation styles that inspired it, particularly full Harvard referencing and AMA style.
If an article has an established citation style that does not use this template, then do not unilaterally start using this template in the article. Instead, you should discuss options for citation styles with other editors and try to reach a consensus.
How to use
With colon
{{rp|page number(s)}}
"Page number(s)" can be a single page number (287), several (xii, 287, 292, 418) or a range (287–288) or any combination thereof. Do not add "Page", "pp.", etc.—just the numbers. Of course, it can also be used for non-numeric pages, for example: "f. 29", "A7", and "back cover", etc., and can also be used for non-paginated sources, e.g., "0:35:12" for a video source.
This template is for appending page numbers to inline reference citations generated by Cite.php. It is a solution for the problem of a source that is cited many times, at numerous different page numbers, in the same LIMSwiki article. Cite.php's limitations pose two citation problems in such a case:
- Regular use of
<ref ...>...</ref>
to provide a separate citation for each fact/statement sourced from a different page or page range will result in numerous individual lines generated by<references />
in the "Notes" or "References" section. - Using a single
<ref ...>...</ref>
and followup<ref ... />
's with the samename=
and simply listing all of the pages cited, would result in the single, very long<references />
entry for this source giving no way for readers to tell which facts were sourced from which pages in the work.
This template works around both of these problems. Doing so is important, because Featured Article as well as Good Article reviews generally insist upon specific facts being cited with specific page numbers.
{{rp}}
is an alternative to the more common method of using shortened footnotes, that does not require the reader to follow two links to see the source. In cases of numerous citations to the same source, the Cite.php <ref ...>
footnoting system is less tedious to use and more difficult to break with incorrect formatting than the {{ref label}} and {{note label}} system (although, in other situations, those templates are not particularly difficult and may be quite useful).
{{rp}}
may end up being a temporary solution to these problems, as Cite.php may be upgraded to resolve these issues, in which case a bot would be able to convert {{rp}}
to the new code.
Missing page numbers
If a reference needs a page number but it is missing, use {{rp|needed=y|{{subst:DATE}}}}
or {{rp|needed=y|date=November 2024}}
. This will automatically use the {{page needed}} template to add the article to the appropriate category. For example, <ref name="aardvark"/>{{rp|needed=y|date=November 2012}}
results in: [1][page needed]
This is preferable to something like {{rp|page number?}}
or {{rp|?}}
, since the cleanup categorization takes place. It is preferable to simply using {{page needed}} in articles that make use of {{rp}}, since it preserves the use of the {{rp}} syntax.
Do not nest the {{page needed}} template inside the {{rp}} template; doing so introduces a stray colon and the displayed results are too small to be legible to many readers. For instance, <ref name="aardvark"/>{{rp|{{page needed|date=November 2012}}}}
results in the undesirable: [1]:[page needed]
A note on spacing
Where multiple citations occur in series, {{rp}} may result in line breaks between the citations. The "word joiner" (code ⁠
), which prohibits a line break on either side of it, may be used to prevent this.
See also
References