ਵਿਕੀਪੀਡੀਆ:Hatnote
Hatnotes are short notes placed at the very top of a page or a section. As an example, see the notes in italics immediately preceding the boxes above. The name comes from their placement, as a hat is placed on top of one's head. The purpose of a hatnote is to help readers locate a different article if the one they are at is not the one they're looking for. Readers may have arrived at the article containing the hatnote because:
Hatnotes provide links to the possibly sought article or to a disambiguation page. The five basic rules of hatnotes are:
For more information about methods of disambiguating articles, see Wikipedia:Disambiguation. PlacementPlace hatnotes at the top of the article or section. When used at the top of an article, hatnotes go immediately below a short description template, but strictly above anything else including protection icons or maintenance tags.[1] Text-based web browsers and screen readers present the page sequentially. If a reader has reached the wrong page, they should find that out first. In the Wikipedia iOS app, there is a known bug whereby hatnotes fail to appear anywhere on the page. FormatIn most cases, hatnotes should be created using a standard hatnote template, as illustrated in #Hatnote templates § Notes below. This permits the form and structure of hatnotes to be changed uniformly across the encyclopedia as needed, and the templates to be excluded in print. Current style on the English Wikipedia is to italicize and to indent each note, without a bullet before the item. A horizontal dividing line should not be placed either under a note or after the final item in a list. Links to articles should follow the naming conventions for capitalization – typically sentence case, not all lower case. When determining the content of the hatnote, keep in mind that it forms part of the user interface rather than the article content. Two applicable user interface design principles are clarity and conciseness. The hatnote should not overload the user with extraneous information, and the content should be imparted quickly and accurately. These design goals are conveyed succinctly in the principle less is more. Length and numberAs hatnotes separate the reader from the content they are looking for, hatnotes should generally be as concise as possible. Long explanations are generally discouraged; the article's lead text, not the hatnote, should explain what the article is about. In almost all cases, the hatnote is intended only to direct readers to other articles in case they were actually looking for something they will not find in the article containing the hatnote. If a disambiguation page exists for a given term, then linking to it should be enough. For example, if the article is X then its hatnote will link to X (disambiguation); it should not have entries for other topics known as X, like X (Grafton novel) or X (charge), because they are already listed in the disambiguation page. However, such an article may be linked if it could be expected by a significant number of readers to be at the title in question: for instance, Turkey is about the country, but many readers expect to find the article about the bird at that title; therefore, the hatnote there correctly reads {{about|the country|the bird|Turkey (bird)|other uses}} which renders There should be as few hatnotes as possible. One single hatnote, which can accommodate several links, is greatly preferable to two or more. Multiple hatnotes may however be appropriate when each serves a different purpose, such as disambiguating the title or distinguishing similar terms.[2] Summarize or not?Some hatnote disambiguation templates include a brief summary of the present article's topic; others do not have a summary. For instance, in the article Honey, one might use the template Alternatively, one might use Either of these two styles is acceptable. The choice of style in a given article is based on editors' preferences and on what is likely to be clearer and easier for the reader. (In this particular instance, most English speakers will know what honey is, and the second, more concise hatnote is preferable.) Where an article already has a hatnote in one of these styles, editors should not change it to the other style without good reason. Examples of proper useTwo articles with similar titles
When two articles share the same title, except that one title is disambiguated and the other is not, and it is not appropriate to change the undisambiguated article's title Error: no text specified (help)., the undisambiguated article should include a hatnote with a link to the other article. It is not necessary to create a separate disambiguation page. The Terms that can cause confusion with another topic
However, they are not suitable when the difference is not readily apparent without additional details. In those cases, use Linking to a disambiguation page
When a term has a primary meaning and two or more additional meanings, the hatnote on the primary topic page should link to a disambiguation page. In many cases, the hatnote also includes a brief description of the subject of the present article, for readers' convenience:
The template Ambiguous term that redirects to an unambiguously named article
Hatnotes above maintenance tagsAlways place a hatnote above maintenance tags, but below short description templates. See above for specific details regarding the placement of hatnotes.
Hatnotes with italics in the links
Words or phrases that are italicized within a normal sentence should be unitalicized within a hatnote. Since all words in a hatnote are italicized, the specific text will not stand out if the italics are not disabled. Italics are cancelled by the parameterization:
Many hatnote templates found below section headers, such as
In this instance, the rendered term will stand out unitalicized. Examples of improper useTrivial information, dictionary definitions, and slangWhen notes feature a trivial detail or use of a term, or links to overly specific and tendentious material, they are unwarranted. A previous version of the article Investment showed:
In this case, there is no direct disambiguation, and the note listed is bound to be uninteresting to most readers. The proper disambiguation simply links to a separate Invest (disambiguation) page. Legitimate information about the topicA previous version of the Aisha article showed:
This is an improper use of disambiguating hatnotes. Instead, the information belongs in the body of the article, or in the article about the book, or in a separate article about names, or all three places. Hatnotes are meant to reduce confusion and direct readers to another article they might have been looking for, not for information about the subject of the article itself. Linking to articles that are related to the topicDisambiguation hatnotes are intended to link to separate topics that could be referred to by the same title, of the article or any of its redirects. They are not intended to link to topics that are simply related to each other, or to a specific aspect of a general topic:
Instead of using a disambiguation hatnote in such cases, it is better to summarize the topic Extraterrestrial life in popular culture under a subsection of Extraterrestrial life in conjunction with the Similarly, do not use the This guideline does not discourage the use of disambiguation hatnotes in a situation where separate topics are related, but could nonetheless be referred to by the same title and would thus qualify for disambiguation, such as a book and its film adaptation (e.g. The Lord of the Rings and The Lord of the Rings (film series)). Disambiguating article names that are not ambiguousIt is usually preferable not to have a hatnote when the name of the article is not ambiguous.
Here, the hatnote can be removed. A reader who is following links within Wikipedia is unlikely to end up at Water (wuxing) if they were looking for other meanings of water, since water does not redirect there. A hatnote may still be appropriate when even a more specific name is still ambiguous. For example, Tree (set theory) might still be confused with Tree (descriptive set theory). The presence or absence of hatnotes in articles with disambiguated titles has been a contentious issue. There are cases where some editors strongly believe that such hatnotes should be included, such as the various articles about treaties called Treaty of Paris. A hatnote may be appropriate in an unambiguously named article when an ambiguous term redirects to it, as explained in #Ambiguous term that redirects to an unambiguously named article § Notes above. Extraneous linksEach additional link in the hatnote besides the ambiguous or confusable topic(s) makes it more difficult to find the desired target. For example, in a previous version of the article WTOB (AM) under a former callsign:
In this case, the link to New Orleans, Louisiana, in the hatnote leads to an article that is not ambiguous with the title. Linking only to the possible other destination (WIST (AM)) makes it easier to find the link. External linksA previous version of the Hurricane Katrina article contained:
The use of external help links in Wikipedia cannot reasonably be maintained. In special cases, a link to an "External links" section may be appropriate, but POV favoritism can be obstructive. In this case, the hatnote was removed entirely. Non-existent articlesHatnotes should not contain red links to non-existent articles, since hatnotes are intended to help users navigate to another article they may have intended to find. The exception is if one intends to create the linked article immediately. In that case, consider creating the new article first, before saving the addition of the hatnote. Hatnote templatesGeneric hatnote
Other uses of the same title ("For ..., see ...")Per Wikipedia:Hatnote#Disambiguating article names that are not ambiguous, it is usually preferable not to have a hatnote when the name of the article is not ambiguous. "This page is about ... For other uses, see..."
Note: When used in main namespace (a.k.a. mainspace), the word "page" in the following hatnotes is replaced by "article".
"This page is about ... It is not to be confused with ..."
"For ..., see ..."
For example: However, it is somewhat clearer when using the
"For other uses, see ..."When such a wordy hatnote as
Redirect"... redirects here. For other uses, see ..."
"For technical reasons, ... redirects here. ...
... redirects here. Not to be confused with ...
Similar proper names ("For other people named ...")Other people
Other places/ships/hurricanes
Distinguish"Not to be confused with ..."
"... redirects here. It is not to be confused with ..."
Family namesFamily names can also be clarified using inline footnotes via For use in sections"Main article: ..."
"Further information: ..."
"See also ..."
Article or section transclusions
For category pagesCategory-specific templates:
This is a template for linking categories horizontally. Horizontal linkage is often the right solution when vertical linkage (i.e., as sub-category and parent category) is not appropriate. In most cases, this template should be used on both categories to create reciprocal linkage between the two categories.
Correct titles"The correct title of this article is ... The substitution or omission of the (or, without a reason: "It appears incorrectly here") ... is due to technical restrictions." ListsWhat to do before editing or creating a templateDo not use subst: with these templates, as that will prevent:
These templates are used in thousands of articles; therefore, changing the syntax could break thousands of articles. If you wish to create or edit a disambiguation or redirection template, first ask yourself the following questions:
Before making any changes, see Wikipedia:Template sandbox and test cases. See alsoReferences
|
|||||||||||||||||||||||||||||||||||
Portal di Ensiklopedia Dunia
