Please do not delete this redirect nor remove this tag unless the need to recreate this article is demonstrated.
When appropriate, protection levels are automatically sensed, described and categorized.
Template {{Redirect category shell}} may be used to add one or more rcat templates, along with their parameters and categories, to a redirect. For more information see the documentation page below.
If you plan to make breaking changes to this template, move it, or nominate it for deletion, please notify Twinkle's users and maintainers at Wikipedia talk:Twinkle as a courtesy, as the standard installation of Twinkle adds and removes this template. Thank you!
This redirect category (rcat) template populates Category:Redirects from duplicated articles and, when the redirect is in main-article namespace (mainspace), Category:Unprintworthy redirects is also populated by default. In 2003, efforts were begun to support the Wikimedia Foundation's goal of increasing access and availability of Wikipedia articles in printed versions. Redirects from duplicated articles are not suitable for a printed version. In other words such redirects are unprintworthy. Some duplicated-article redirects are printworthy, in which case the first parameter may be used as in {{R from duplicated article|printworthy}} – see below.
Please do not alter the printworthy settings of this rcat without first notifying the Version 1.0 Editorial Team, who are responsible for any and all materials, including redirects, that go into a printed version of Wikipedia.
Add this rcat to a redirect page in the following manner:
Template {{Rcat shell}} is an alias for the Redirect category shell template, which may be used to add as many appropriate rcats as needed, usually from one to seven, along with their parameters, to a redirect. For more information see the documentation on its template page. This rcat may also tag a redirect individually:
#REDIRECT [[(target page name)]]
{{R from duplicated article}}
Apply this rcat to a redirected page name that had the same or very similar subject matter as another article or other project page. This must be done in order to preserve the edit-history attributions of the redirect after the content was merged into the target page.
Since these redirects are former articles, they have revision histories of prior edits; however, they should not be history merged with their targets. This is because in most cases they were originally created in good faith as separate distinct articles, without the creator having knowledge of the pre-existence of another article on exactly the same subject. This situation is different from a cut-and-paste move where a history merge would be required.
This page is a redirect:
